IPv6 Node Information Queries Update Bob Hinden Vienna IETF

Bob Hinden / VRRP Working GroupVienna IETF NEW DRAFT Goals for Draft –Resolve the issues raised by the IESG, and –Maintain comparability with current shipping code. Shipping in the KAME and USAGI distributions. Found to be very useful for deploying IPv6 service and debugging operational problems.

Bob Hinden / VRRP Working GroupVienna IETF CHANGES Moved applicability statement to start of document and update introduction. Removed Qtypes query capabilities Limit returned TTL in node name to zero and removed text describing non-zero TTLs. Remove text about A6 records Change to have all new Qtypes require IETF approval Updated security considerations

Bob Hinden / VRRP Working GroupVienna IETF LAST CALL ISSUES (1) Handling of RFC 3041 (privacy enhanced) addresses –Should Not reveal RFC3041 addresses to general Node Address query –Should Not reveal global name to Node Name query made to RFC3041 address –May respond with temporary name to Node Name query made to RFC3041 address

Bob Hinden / VRRP Working GroupVienna IETF LAST CALL ISSUES (2) Limit to responses to link-local queries –Not as default. Administrator “may want to filter” at administrative boundary. Remove IPv4 address query (Qtype=4) –Yes/No?

Bob Hinden / VRRP Working GroupVienna IETF EDITORIAL Qtype 3 A bit handling is a little bit complicated. how about moving the description to the top? (right after the first paragraph of 6.3) without understanding A bit, readers cannot understand theinterpretation of other bits. on page 3, text for NI query code 1 refers to "Supported Qtypes” which is no longer there (Qtype=1). suggestion: remove text starting from "as in....".

Bob Hinden / VRRP Working GroupVienna IETF NEXT STEPS New draft to resolve issues Resubmit to IESG for Proposed Standard?