Little Problem
Matteo Tescione
wizard@italiansky.com
Thu, 10 Jan 2002 20:39:27 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_003E_01C19A16.E5A79E10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello Bob, thanks a lot for your quick answer.
Now everything is just most clear but in rfc2772 i can't see why a site
without their own asn cannot use the upstream provider's asn to request =
a
pTLA. Can you explain me this?
Best Regards,
Matteo
> ----- Original Message -----
> From: "Bob Fink" <fink@es.net>
> To: "Matteo Tescione" <wizard@italiansky.com>
> Cc: "6BONE List" <6bone@isi.edu>
> Sent: Thursday, January 10, 2002 7:48 PM
> Subject: Re: Little question
>
>
> > Matteo,
> >
> > At 05:48 PM 1/10/2002 +0100, Matteo Tescione wrote:
> > >Hi to all, i have a little question:
> > >while reading rfc 2546 regarding 6bone routing practice, i don't
> > >understand very well what does it means when says "Site border =
router
> MUST
> > >NOT advertise prefixes more specific than the /48 ones allocated by
their
> > >ISP."
> >
> > RFC2546 is obsolete and replaced by RFC2772. You should read section =
4
and
> > then ask me specific questions you may have.
> >
> >
> > >I was looking in several rfcs regarding ipv6 about the possibility =
for
> > >request a pTla using a private As number or the AS from the =
upstream
> > >provider (reference to rfc2270, "Using a Dedicated AS for Sites =
Homed
to
> > >a Single Provider").
> >
> > We do not allocate pTLAs unless the requester has their own AS =
number
for
> > their exclusive IPv6 use (their IPv4 ASN will do).
> >
> >
> > Bob
> >
>
------=_NextPart_000_003E_01C19A16.E5A79E10
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>Hello Bob,=20
thanks a lot for your quick answer.<BR>Now everything is just most clear =
but in=20
rfc2772 i can't see why a site<BR>without their own asn cannot use the =
upstream=20
provider's asn to request a<BR>pTLA. Can you explain me this?<BR>Best=20
Regards,<BR>Matteo<BR><BR>> ----- Original Message -----<BR>> =
From: "Bob=20
Fink" <</FONT><A href=3D"mailto:fink@es.net"><FONT face=3D"Times New =
Roman"=20
size=3D3>fink@es.net</FONT></A><FONT face=3D"Times New Roman" =
size=3D3>><BR>>=20
To: "Matteo Tescione" <</FONT><A =
href=3D"mailto:wizard@italiansky.com"><FONT=20
face=3D"Times New Roman" size=3D3>wizard@italiansky.com</FONT></A><FONT=20
face=3D"Times New Roman" size=3D3>><BR>> Cc: "6BONE List" =
<</FONT><A=20
href=3D"mailto:6bone@isi.edu"><FONT face=3D"Times New Roman"=20
size=3D3>6bone@isi.edu</FONT></A><FONT face=3D"Times New Roman" =
size=3D3>><BR>>=20
Sent: Thursday, January 10, 2002 7:48 PM<BR>> Subject: Re: Little=20
question<BR>><BR>><BR>> > Matteo,<BR>> ><BR>> > =
At 05:48=20
PM 1/10/2002 +0100, Matteo Tescione wrote:<BR>> > >Hi to all, i =
have a=20
little question:<BR>> > >while reading rfc 2546 regarding 6bone =
routing=20
practice, i don't<BR>> > >understand very well what does it =
means when=20
says "Site border router<BR>> MUST<BR>> > >NOT advertise =
prefixes=20
more specific than the /48 ones allocated by<BR>their<BR>> >=20
>ISP."<BR>> ><BR>> > RFC2546 is obsolete and replaced by =
RFC2772.=20
You should read section 4<BR>and<BR>> > then ask me specific =
questions you=20
may have.<BR>> ><BR>> ><BR>> > >I was looking in =
several=20
rfcs regarding ipv6 about the possibility for<BR>> > >request a =
pTla=20
using a private As number or the AS from the upstream<BR>> > =
>provider=20
(reference to rfc2270, "Using a Dedicated AS for Sites =
Homed<BR>to<BR>>=20
> >a Single Provider").<BR>> ><BR>> > We do not =
allocate pTLAs=20
unless the requester has their own AS number<BR>for<BR>> > their =
exclusive=20
IPv6 use (their IPv4 ASN will do).<BR>> ><BR>> ><BR>> =
>=20
Bob<BR>> ><BR>></FONT><BR></FONT></DIV></BODY></HTML>
------=_NextPart_000_003E_01C19A16.E5A79E10--