On Thu, 4 Mar 2004, JINMEI Tatuya / [ISO-2022-JP] [EMAIL PROTECTED]@C#:H wrote: [...] > The easiest solution to them would be to list RFC3315 as an > informative reference. I don't know whether this is acceptable. > According to Section 2.7 of draft-rfc-editor-rfc2223bis-07.txt, > Normative references specify > > - documents that must be read to understand or implement the > technology in the new RFC > - documents whose technology must be present for the technology > in the new RFC to work > > But the first condition seems to me a bit subjective. Under which > requirement can we decide a document must be read for a different > document?
I don't think this is a problem. You don't have to understand DHCPv6 to ignore M/O bits -- which you only act upon IF you have implemented DHCPv6 -- and then you understand it already :). IMHO, putting the reference as Informative seems just fine. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
