RE: Node requirements: draft-ietf-6man-node-req-bis-03.txt

2009-07-20 Thread Greg.Rabil
Thomas, raises an intersting point. This document (and RFC 4294) mandate (MUST) that hosts implement stateless autoconfiguration. This despite that this document is only informational, and no where in standards track RFCs is stateless autoconf mandated. This takes us How about RFC

RE: [dhcwg] Brokenness of specs w.r.t. client behavior with MO bits

2008-10-13 Thread Greg.Rabil
A DHCPv6 server will answer all Solicits, even if it has no addresses to provide, with an Advertise. The difference is in the status code in each IA. I don't believe that is an accurate statement. According to RFC 3736 section 5.1, clients and servers implement the following messages for

RFC 4293 - ipAddressTable

2007-10-10 Thread Greg.Rabil
It is my understanding that the ipAddressTable roughly replaces the ipAddrTable. However, the ipAdEntAddr OID is read-only in RFC2011, whereas the ipAddressAddrType and ipAddressAddr OIDs defined in RFC 4293 are not-accessible. Similarly, the pertinent OIDs of the ipAddressPrefixTable are