> This is OK for me. I will plan add it to the next version of the > draft. Would you like to be listed as an author?
I don't have a problem with that, but I suspect my wording can benefit from some editorial tweaks. > > > What did you have in mind that might further clarify this issue? > > > >Remove "for the 2000::/3 Prefix" from the title and remove > >the mention of the specific prefix from the text. > > OK, that is clearer. It wouldn't be too hard to make this change, but > there doesn't seem to be complete agreement on the list for this change. > > >Apart from the restriction to 2000::/3 I don't see how section 2.0 adds > >anything beyond what is in addr-arch. Perhaps I'm missing something. > > I think it provides a summary of what the resulting address format for this > prefix (and other prefixes if the above change is made). Since we now seem > to heading toward a non-standards track document, what is the harm? Hmm - based on Brian's comment it might make sense to say that the document explicitly redefines the structure in 2000::/3 to be the god'ol basic addr-arch structure of "bits+subnet+iid". Thus having section 2.0 to explicitly point out that this is the replacement for the format in 2374 makes sense to me. But the "replacement" part needs to be made very clear. > I now agree that it can be non-standards track. What was your objection to > making it a BCP? In some ways this is the best current practice. I don't see any "practise" in the document. Perhaps I'm missing something. If there is practise, for instance suggesting that the same address format can be useful for both providers and exchanges, then BCP might make more sense. But it isn't clear to me whether the WG sees the benefits of restating that aspect of 2374 in this document. Erik -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
