rfc3315bis - updated DHCPv6 protocol ====================================== This is a repository that for storing notes, comments and hopefully a draft text of replacement for RFC3315, which is commonly referred to as RFC3315bis or just 3315bis. This is NOT an official IETF repository, but rather a personal scratchpad for people, who are potentially interested in pariticipating in this behavior. If you are interested in joining this effort, please ask on DHCPv6bis mailing list: https://www.ietf.org/mailman/listinfo/dhcpv6bis We have an issue tracker here: http://tools.ietf.org/group/dhcpv6bis/ This work is being done as part of the DHC working group. We plan to discuss details to the dhcpv6bis list, but we will occasionally discuss or report progress on DHC mailing list here: https://www.ietf.org/mailman/listinfo/dhcwg Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: * The IETF plenary session * The IESG, or any member thereof on behalf of the IESG * Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices * Any IETF working group or portion thereof * The IAB or any member thereof on behalf of the IAB * The RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.