Re: Unique local & DNS (was: AD Evaluation of draft-ietf-ipv6-unique-local-addr-03.txt+

2004-03-17 Thread Stephen Sprunk
Thus spake "Mark Andrews" <[EMAIL PROTECTED]> > > At a minimum, being present in the global DNS should be at the option > > of the allocatee. Until a viable solution is found for non-registered > > prefixes, this might be given as an advantage of using a registered prefix. > > Well non-registered

Re: Unique local & DNS (was: AD Evaluation of draft-ietf-ipv6-unique-local-addr-03.txt+

2004-03-17 Thread Mark Andrews
> Thus spake "Christian Huitema" <[EMAIL PROTECTED]> > > In her review of "draft-ietf-ipv6-unique-local-addr-03.txt", Margaret > > raises an excellent point: > > > > > (1) This draft doesn't mention the reverse DNS tree. Is it expected > > > that whatever registry assigns these values will

Re: ASN-based prefixes for leaf ASes

2004-03-17 Thread Pekka Savola
On Wed, 17 Mar 2004, Stephen Sprunk wrote: > Thoughts? Been there, done that, gotten flamed about it :-). draft-savola-multi6-asn-pi-01.txt (Well, I don't like that proposition either..) p.s. the correct forum may be multi6. -- Pekka Savola "You each name yourselves king, yet

Re: Unique local & DNS (was: AD Evaluation of draft-ietf-ipv6-unique-local-addr-03.txt+

2004-03-17 Thread Stephen Sprunk
Thus spake "Christian Huitema" <[EMAIL PROTECTED]> > In her review of "draft-ietf-ipv6-unique-local-addr-03.txt", Margaret > raises an excellent point: > > > (1) This draft doesn't mention the reverse DNS tree. Is it expected > > that whatever registry assigns these values will also populate

ASN-based prefixes for leaf ASes

2004-03-17 Thread Stephen Sprunk
I'm starting here with the posit that the global routing table will contain at least one prefix (/48 or shorter in the case of IPv6) from each ASN. Obviously if this doesn't hold, the following discussion isn't valid... Leaf ASes in the IPv6 world are expected to get a /48 prefix allocation (from

RE: [nemo] FW: Multiple DRs on a link

2004-03-17 Thread Pascal Thubert \(pthubert\)
> > -Original Message- > From: Soliman Hesham [mailto:[EMAIL PROTECTED] > Sent: mercredi 17 mars 2004 09:38 > To: Pascal Thubert (pthubert); Jari Arkko > Cc: [EMAIL PROTECTED] > Subject: RE: Multiple DRs on a link > > > > => There are many different reasons. I sent a verly long > > emai

RE: Multiple DRs on a link

2004-03-17 Thread Soliman Hesham
> > => There are many different reasons. I sent a verly long > > email about this to nemo (monet back then). One simple > > scenario is that you might be walking around with a PAN > > that happens to have 2 MRs on a single link (e.g. a laptop > > and a mobile phone). The two MRs could share t

RE: Multiple DRs on a link

2004-03-17 Thread Pascal Thubert \(pthubert\)
MRs on different links? > > => There are many different reasons. I sent a verly long > email about this to nemo (monet back then). One simple > scenario is that you might be walking around with a PAN > that happens to have 2 MRs on a single link (e.g. a laptop > and a mobile phone). The two MRs c

Re: Unique local & DNS (was: AD Evaluation of draft-ietf-ipv6-unique-local-addr-03.txt+

2004-03-17 Thread Ignatios Souvatzis
Hi Fred, > Also, what about other non-DNS naming services that can be deployed > within a site/organization? E.g., the Sun Yellow Pages (I guess it's called > NIS now?) We don't confess it in public, and we block all RPC requests at our border routers, but some of us do. > and the naming service

RE: Multiple DRs on a link

2004-03-17 Thread Pascal Thubert \(pthubert\)
Hi Hesham: In case that helps, we've found practical in some experimentations to allow a MR to autoconf addresses on its ingress interfaces, and install the associated connected routes. Note that if a MR listens to itself from a different interface, it will not install the prefix. Anyway, once th