Re: [GLOBAL-V6] Re: I-D ACTION:draft-narten-ipv6-3177bis-48boundary-00.txt

2005-07-19 Thread Randy Bush
We agree to go more liberal when we set the current policy. But I still believe that starting of allocating /2x size to requesting ISPs who has nothing but only because they have IPv4 customer is, I think, too far liberal. Is this the sound model that ISP never come back to RIR for

Re: [GLOBAL-V6] Re: I-D ACTION:draft-narten-ipv6-3177bis-48boundary-00.txt

2005-07-19 Thread marcelo bagnulo braun
Is it practical to change in other regions? We had a discussion about IPv6 address management in the LACNIC VIII meeting in Lima (30 of june 2005) and my reading of the comments of the meeting is that they are pretty much in line with the considerations expressed by Thomas in his drafts.

Re: IPv6 WG Last Call: draft-ietf-ipngwg-icmp-name-lookups-12.txt

2005-07-19 Thread Elwyn Davies
Some comments: Substantive: s4: Code 1 bullet point: The 'Supported Qtypes' query disappeared from the rest of the memo some time ago. s5: para 5: Is the intended effect of the last sentence (defaulting to accepting all link-local multicast addresses that have been joined) that sending a

Re: New Version Notification - draft-ietf-ipngwg-icmp-v3-07.txt - IANA Considerations for ICMP specifications (esp. 2461bis)

2005-07-19 Thread Elwyn Davies
I have just been reviewing the latest version of the name lookups draft and checking the IANA considerations for that draft triggered me to look across the IANA considerations for all the ICMPv6 stuff we have in progress at present. The conclusions are: - icmp-v3 supersedes section 7 in

RE: Comments on draft-ietf-ipngwg-icmp-name-lookups-12.txt

2005-07-19 Thread Pashby, Ronald W CTR NSWCDD-B35
- I disagree that RFC3307 was only for Layer 3. It is clearly stated in the Abstract and Introduction that: The purpose of these guidelines is to reduce the probability of IPv6 multicast address collision, not only at the IPv6 layer, but also at the link-layer of media that encode

I-D ACTION:draft-ietf-ipv6-2461bis-04.txt

2005-07-19 Thread Internet-Drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Version 6 Working Group Working Group of the IETF. Title : Neighbor Discovery for IP version 6 (IPv6) Author(s) : T. Narten, et al. Filename

Re: I-D ACTION:draft-narten-ipv6-3177bis-48boundary-00.txt

2005-07-19 Thread Bob Hinden
Jordi, I see situations for assigning a /128 when a unique device is connected, which is not going to route anything else, but once it has other interfaces (which is the most common case and will become more and more often) ... A /128 breaks IPv6 Privacy Addresses (RFC3041). Every device

RE: I-D ACTION:draft-narten-ipv6-3177bis-48boundary-00.txt

2005-07-19 Thread Manfredi, Albert E
A /128 breaks IPv6 Privacy Addresses (RFC3041). Every device needs a /64 to allow this mechanism to be used. Bob Alternative mechanisms could permit interface IDs to be shorter than 64 bits, for example 48 bits or far fewer than that. Interface IDs only need to be unique within a given