draft-ietf-ngtrans-ipv4survey-02.txt

[Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>]

proposed modification to draft-ietf-ngtrans-ipv4survey-02.txt


<currenttext>
3.12 RFC 1305 Network Time Protocol (Version 3)
...
There are numerous places in sample code and algorithms use the above
mentioned variables.  It seems that there is no reason to modify the
actual protocol.  A small number of text changes and an update to
implementations to understand both IPv4 and IPv6 addresses can achieve
an NTP that works on both network layer protocols.
</currenttext>

my colleague Jean-Francois did the port. There is a problem which is the 
refid. Without changes, NTPv6 does not scale well without a fix.

Here is a suggested text to replace the quoted text to this draft section:

<newtext>
The refid field identifies uniquely the reference clock a ntp is based on. 
This refid is a 32-bit field in the NTP packet. So it cannot carry an IPv6 
address without a protocol change. The discussions in the ntp dev team and 
ntp author around how to resolve this issue went to put a "compressed" ipv6 
address in this refid field. This in fact changes the current protocol.

Other than the refid change, there is no other changes needed to support 
IPv6 in NTP.
</newtext>


------------------------------------------
Marc Blanchet
Viagénie
tel: +1-418-656-9254x225

------------------------------------------
http://www.freenet6.net: IPv6 connectivity
------------------------------------------
http://www.normos.org: IETF(RFC,draft),
 IANA,W3C,... standards.
------------------------------------------