arcmedia appsawg hybi calext core dmarc eppext httpbis json precis paws scim tzdist urnbis uta weirds websec ianaplan ancp dmm dprive dhc dnssd homenet hip intarea 6man 6lo 6tisch l2tpext lwig lisp mip4 mif ntp netext pcp softwire savi sunset4 tictoc trill anima bmwg dime dnsop eman grow v6ops lmap lime mboned netmod netconf opsec opsawg radext wpkops avtcore avtext payload bfcpbis clue drinks dispatch ecrit xmpp insipid codec xrblock mmusic p2psip rtcweb stir sipcore siprec straw stox webpush bess bfd bier ccamp forces idr i2rs isis manet mpls nvo3 ospf pce pim pals rtgwg roll sidr sfc spring teas abfab ace kitten dane dice httpauth ipsecme jose mile trans sacm tokbind tls oauth aqm alto conex cdni dtn ippm mptcp nfsv4 ppsp rmcat storm tcpinc tcpm tsvwg taps tram 'Archive' Top-Level Media Type (arcmedia) ----------------------------------------- Charter Last Modified: 2015-02-09 Current Status: Active Chair: Dave Crocker Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Barry Leiba Mailing Lists: General Discussion: arcmedia@ietf.org To Subscribe: http://www.ietf.org/mailman/listinfo/arcmedia Archive: http://www.ietf.org/mail-archive/web/arcmedia Description of Working Group: Archive formats are used to aggregate multiple files and other data into a single object, often with data compression and/or confidentiality protection (encryption). This working group will create an "archive" top-level media type. There has been recent work to register media types for archive formats such as .tar (a POSIX standard format). There are already several similar media types for archive formats, such as .gzip. and .zip. (see, for example, RFC6713), all of which are registered under the top-level media type "application". We create top-level media types only rarely, only with Standards Track RFCs, and only when one or more media types get special (or common, in the case of more than one) handling that does not fit under an existing top-level media type. RFC6838 defines this process. The working group will use draft-seantek-kerwin-arcmedia-type as its initial input for a Standards Track document that creates a top-level media type for archive formats. The document will specify rules for registering subtypes under that new top-level type, considering at a minimum the issue of type suffixes, fragment identifiers, and internationalization. The W3C TAG work on packaging and archives, currently in progress, will also be considered. Either in that same document or in one of more follow-on documents, it will produce an initial set of registrations under the new top-level media type. The main document will include an Implementation Status section, described by RFC6982, to record known projects that will either produce or consume content using the new media type. If by the first milestone there appears to be no implementations of the new media type expected, the working group will conclude, without having produced any RFCs. No other work is in scope for this working group. Goals and Milestones: Jun 2015 - Base document Dec 2015 - Registrations document(s) (if separate from the base) Internet-Drafts: No Requests for Comments Applications Area Working Group (appsawg) ----------------------------------------- Charter Last Modified: 2014-07-29 Current Status: Active Chairs: Murray Kucherawy Alexey Melnikov Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Barry Leiba Mailing Lists: General Discussion: apps-discuss@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/apps-discuss Archive: http://www.ietf.org/mail-archive/web/apps-discuss/ Description of Working Group: The Applications Area sometimes receives proposals for the development of specifications dealing with application-related topics that are not in scope for an existing working group and do not justify the formation of a new working group. The Applications Area Working Group (APPSAWG) can serve as a forum for such work in the IETF. The APPSAWG accepts work items in accordance with the consensus of the Working Group and the best judgment of the Applications Area Directors, who are responsible for updating the working group milestones as needed. The working group meets if there are active proposals that require intensive discussion. Work items that are appropriate for the APPSAWG mostly fall under the following topics: (A) Well-defined security issues that are relevant to multiple application technologies (e.g., draft-saintandre-tls-server-id-check). (B) Small-scale additions to the protocol stack for HTTP and other application technologies, mostly related to service discovery and meta-data (e.g., RFC 5785, draft-nottingham-http-link-header, and draft-hammer-hostmeta). (C) Selected other work items addressing topics that historically fall within the Applications Area, such as calendaring, date and time formats, HTTP, internationalization, language tags, MIME, URIs and XML. When considering whether to accept a proposed work item, the APPSAWG and the Applications Area Directors shall take into account the following factors, among others: * There is no existing related Working Group that is willing to recharter to take on this work, and the document doesn't justify the formation of a new working group. * Whether the WG has consensus on the suitability, importance, and projected quality of the proposed work item. * Whether there is a core team of WG participants with sufficient energy and expertise to advance the proposed work item according to the proposed schedule. * Whether there are enough WG participants who are willing to review the work produced by the document authors or editors. * Whether the Area Directors judge that wider input is needed before accepting the proposed work item (e.g., from the IESG, IAB, or another standards development organization). Goals and Milestones: Done - Publication requested for draft-ietf-appsawg-media-type-suffix-regs Done - Publication requested for draft-ietf-appsawg-json-patch Done - Publication requested for draft-ietf-appsawg-json-pointer Done - Publication requested for draft-ietf-appsawg-acct-uri Done - Publication requested for draft-ietf-appsawg-webfinger Done - Publication requested for draft-ietf-appsawg-rfc5451bis Done - Publication requested for draft-ietf-appsawg-malformed-mail Done - Publication requested for draft-ietf-appsawg-rrvs-header-field Done - Publication requested for draft-ietf-appsawg-xml-mediatypes Done - Publication requested for draft-ietf-appsawg-sieve-duplicate Done - Publication requested for draft-ietf-appsawg-uri-get-off-my-lawn Done - Publication requested for draft-ietf-appsawg-multimailbox-search Done - Publication requested for draft-ietf-appsawg-nullmx Done - Publication requested for draft-ietf-appsawg-email-auth-codes Done - Publication requested for draft-ietf-appsawg-json-merge-patch Done - Publication requested for draft-ietf-appsawg-authres-ptypes-registry Done - Publication requested for draft-ietf-appsawg-multipart-form-data Done - Publication requested for draft-ietf-appsawg-uri-scheme-reg Apr 2015 - Publication requested for draft-ietf-appsawg-text-markdown Apr 2015 - Publication requested for draft-ietf-appsawg-http-problem Apr 2015 - Publication requested for draft-ietf-appsawg-rfc7001bis Apr 2015 - Publication requested for draft-ietf-appsawg-text-markdown-use-cases Jul 2015 - Publication requested for draft-ietf-appsawg-file-scheme Jul 2015 - Publication requested for draft-ietf-appsawg-mdn-3798bis Internet-Drafts: - Guidelines and Registration Procedures for New URI Schemes [draft-appsawg-uri-scheme-reg-00] (18 pages) - Sieve Email Filtering: Detecting Duplicate Deliveries [draft-bosch-sieve-duplicate-02] (10 pages) - A NULL MX Resource Record for Domains that Accept No Mail [draft-delany-nullmx-02] (5 pages) - The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) - Unicode 6.0 [draft-faltstrom-5892bis-05] (4 pages) - Message Disposition Notification [draft-hansen-mdn-3798bis-02] (32 pages) - Additional Media Type Structured Syntax Suffixes [draft-hansen-media-type-suffix-regs-02] (7 pages) - The "about" URI Scheme [draft-ietf-appsawg-about-uri-scheme-07] (7 pages) - The 'acct' URI Scheme [draft-ietf-appsawg-acct-uri-07] (8 pages) - A Property Types Registry for the Authentication-Results Header Field [draft-ietf-appsawg-authres-ptypes-registry-04] (5 pages) - Email Authentication Status Codes [draft-ietf-appsawg-email-auth-codes-07] (8 pages) - The file URI Scheme [draft-ietf-appsawg-file-scheme-00] (16 pages) - Email Greylisting: An Applicability Statement for SMTP [draft-ietf-appsawg-greylisting-09] (17 pages) - Forwarded HTTP Extension [draft-ietf-appsawg-http-forwarded-10] (16 pages) - Problem Details for HTTP APIs [draft-ietf-appsawg-http-problem-00] (13 pages) - JSON Merge Patch [draft-ietf-appsawg-json-merge-patch-07] (9 pages) - JavaScript Object Notation (JSON) Patch [draft-ietf-appsawg-json-patch-10] (18 pages) - JavaScript Object Notation (JSON) Pointer [draft-ietf-appsawg-json-pointer-09] (8 pages) - Advice for Safe Handling of Malformed Messages [draft-ietf-appsawg-malformed-mail-11] (24 pages) - Message Disposition Notification [draft-ietf-appsawg-mdn-3798bis-02] (32 pages) - Media Type Specifications and Registration Procedures [draft-ietf-appsawg-media-type-regs-14] (32 pages) - Additional Media Type Structured Syntax Suffixes [draft-ietf-appsawg-media-type-suffix-regs-08] (14 pages) - Update to MIME regarding "charset" Parameter Handling in Textual Media Types [draft-ietf-appsawg-mime-default-charset-04] (6 pages) - IMAP4 Multimailbox SEARCH Extension [draft-ietf-appsawg-multimailbox-search-04] (11 pages) - Returning Values from Forms: multipart/form-data [draft-ietf-appsawg-multipart-form-data-08] (13 pages) - A "Null MX" No Service Resource Record for Domains that Accept No Mail [draft-ietf-appsawg-nullmx-10] (8 pages) - Indicating Email Handling States in Trace Fields [draft-ietf-appsawg-received-state-04] (12 pages) - The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages [draft-ietf-appsawg-rfc3462bis-04] (9 pages) - Terminology Used in Internationalization in the IETF [draft-ietf-appsawg-rfc3536bis-06] (47 pages) - Message Header Field for Indicating Message Authentication Status [draft-ietf-appsawg-rfc5451bis-10] (43 pages) - Message Header Field for Indicating Message Authentication Status [draft-ietf-appsawg-rfc7001bis-03] (46 pages) - The Require-Recipient-Valid-Since Header Field and SMTP Service Extension [draft-ietf-appsawg-rrvs-header-field-11] (24 pages) - Sieve Email Filtering: Detecting Duplicate Deliveries [draft-ietf-appsawg-sieve-duplicate-09] (15 pages) - The text/markdown Media Type [draft-ietf-appsawg-text-markdown-06] (13 pages) - text/markdown Use Cases [draft-ietf-appsawg-text-markdown-use-cases-01] (25 pages) - URI Design and Ownership [draft-ietf-appsawg-uri-get-off-my-lawn-05] (9 pages) - Guidelines and Registration Procedures for URI Schemes [draft-ietf-appsawg-uri-scheme-reg-04] (18 pages) - WebFinger [draft-ietf-appsawg-webfinger-18] (28 pages) - Deprecating the "X-" Prefix and Similar Constructs in Application Protocols [draft-ietf-appsawg-xdash-05] (13 pages) - XML Media Types [draft-ietf-appsawg-xml-mediatypes-10] (35 pages) - WebFinger [draft-jones-appsawg-webfinger-06] (24 pages) - Simple Web Discovery (SWD) [draft-jones-simple-web-discovery-04] (8 pages) - The file URI Scheme [draft-kerwin-file-scheme-13] (16 pages) - A Property Types Registry for the Authentication-Results Header Field [draft-kucherawy-authres-ptypes-registry-00] (5 pages) - Email Authentication Status Codes [draft-kucherawy-email-auth-codes-00] (5 pages) - Indicating Email Handling States in Trace Fields [draft-kucherawy-received-state-02] (10 pages) - XML Media Types [draft-lilley-xml-mediatypes-00] (35 pages) - Returning Values from Forms: multipart/form-data [draft-masinter-multipart-form-data-03] (9 pages) - Problem Details for HTTP APIs [draft-nottingham-http-problem-07] (13 pages) - Standardising Structure in URIs [draft-nottingham-uri-get-off-my-lawn-02] (8 pages) - Spam reporting using IMAP: SREP [draft-ordogh-spam-reporting-using-imap-04] (16 pages) - The 'acct' URI Scheme [draft-saintandre-acct-uri-01] (7 pages) - The text/markdown Media Type [draft-seantek-text-markdown-media-type-00] (9 pages) - text/markdown Use Cases [draft-seantek-text-markdown-use-cases-01] (18 pages) - Windows Image Media Types [draft-seantek-windows-image-00] (12 pages) - The application/json-merge-patch Media Type [draft-snell-merge-patch-08] (9 pages) - Guidelines and Registration Procedures for New URI Schemes [draft-thaler-appsawg-uri-scheme-reg-00] (18 pages) - The Require-Recipient-Valid-Since Header Field [draft-wmills-rrvs-header-field-01] (10 pages) Requests for Comments: BCP166: Terminology Used in Internationalization in the IETF (47 pages) * Obsoletes RFC3536 * Informative Reference RFC3629 * Informative Reference RFC4647 * Informative Reference RFC3536 * Informative Reference RFC4013 * Informative Reference RFC952 * Informative Reference RFC5198 * Informative Reference RFC1123 * Informative Reference BCP14 * Informative Reference BCP19 * Informative Reference BCP18 * Normative Reference RFC2047 * Informative Reference RFC2045 * Informative Reference RFC3454 * Possible Reference RFC5741 * Informative Reference RFC1034 * Informative Reference RFC6055 * Informative Reference RFC2781 * Informative Reference BCP137 * Informative Reference RFC2277 * Informative Reference STD13 * Informative Reference RFC3492 * Informative Reference RFC3490 * Informative Reference RFC3491 * Informative Reference RFC5890 * Informative Reference RFC5892 * Informative Reference RFC5895 * Informative Reference RFC5646 * Informative Reference RFC2119 * Informative Reference STD3 * Informative Reference RFC2978 * Informative Reference BCP47 * Informative Reference STD63 * Informative Reference RFC4713 * Informative Reference RFC5322 * Informative Reference RFC5137 * Informative Reference RFC3743 * Informative Reference DRAFT-SAINTANDRE-USERNAME-INTEROP * Normative Reference RFC6570 * Informative Reference DRAFT-IETF-IRI-3987BIS * Normative Reference RFC7231 * Informative Reference DRAFT-IETF-PRECIS-SASLPREPBIS * Informative Reference DRAFT-IETF-NFSV4-RFC3530BIS * Informative Reference RFC6885 * Informative Reference DRAFT-IETF-PRECIS-FRAMEWORK * Informative Reference DRAFT-IETF-SALUD-ALERT-INFO-URNS * Informative Reference DRAFT-RESCHKE-RFC5987BIS * Informative Reference DRAFT-YEVSTIFEYEV-FTP-URI-SCHEME * Informative Reference DRAFT-IETF-XMPP-6122BIS * Informative Reference DRAFT-IUCG-INTERNET-PLUS * Informative Reference DRAFT-MELNIKOV-PRECIS-SASLPREPBIS * Informative Reference DRAFT-SAINTANDRE-PRECIS-NICKNAME * Informative Reference DRAFT-SULLIVAN-DNS-ZONE-CODEPOINT-PPLES * Informative Reference RFC6912 * Informative Reference DRAFT-IETF-PRECIS-NICKNAME * Normative Reference DRAFT-IETF-HTTPAUTH-BASICAUTH-ENC * Informative Reference DRAFT-SULLIVAN-RFC2277-BIS * Informative Reference DRAFT-RESCHKE-HTTP-JFV * Normative Reference DRAFT-IETF-HTTPAUTH-BASICAUTH-UPDATE * Informative Reference DRAFT-SULLIVAN-LUCID-PROB-STMT BCP178: Deprecating the "X-" Prefix and Similar Constructs in Application Protocols (13 pages) * Replaces DRAFT-SAINTANDRE-XDASH * Replaces DRAFT-SAINTANDRE-XDASH-CONSIDERED-HARMFUL * Informative Reference BCP9 * Informative Reference RFC2046 * Informative Reference RFC2047 * Informative Reference RFC2045 * Informative Reference RFC4288 * Informative Reference RFC2616 * Informative Reference RFC1123 * Informative Reference RFC2068 * Informative Reference RFC4566 * Informative Reference BCP13 * Normative Reference BCP14 * Informative Reference RFC5451 * Informative Reference BCP35 * Informative Reference RFC2426 * Informative Reference RFC3864 * Possible Reference RFC5741 * Informative Reference RFC5545 * Informative Reference RFC4395 * Informative Reference RFC5727 * Informative Reference STD3 * Informative Reference RFC1154 * Informative Reference STD11 * Informative Reference RFC2822 * Informative Reference RFC4512 * Informative Reference BCP90 * Informative Reference RFC775 * Informative Reference RFC4122 * Informative Reference RFC822 * Informative Reference RFC5064 * Informative Reference BCP66 * Informative Reference BCP67 * Informative Reference RFC5646 * Informative Reference RFC737 * Informative Reference RFC743 * Normative Reference RFC2119 * Informative Reference BCP26 * Informative Reference BCP47 * Informative Reference RFC691 * Informative Reference BCP43 * Informative Reference STD66 * Informative Reference RFC2939 * Informative Reference RFC3427 * Informative Reference RFC3986 * Informative Reference BCP82 * Informative Reference RFC3406 * Normative Reference DRAFT-DULAUNOY-KAPLAN-PASSIVE-DNS-COF * Informative Reference RFC7001 * Informative Reference RFC7231 * Informative Reference RFC6709 * Informative Reference DRAFT-BORMANN-COAP-MISC * Informative Reference DRAFT-IETF-URNBIS-RFC3406BIS-URN-NS-REG * Informative Reference RFC6838 * Informative Reference RFC7208 * Informative Reference DRAFT-KUCHERAWY-RFC5451BIS * Informative Reference RFC7034 * Informative Reference RFC6963 * Informative Reference DRAFT-SAINTANDRE-URNBIS-3406BIS * Normative Reference DRAFT-BROWN-DEVICE-STOCK-UA * Informative Reference DRAFT-STROEDER-HASHED-USERPASSWORD-VALUES * Normative Reference DRAFT-DULAUNOY-DNSOP-PASSIVE-DNS-COF * Informative Reference DRAFT-IETF-URNBIS-RFC2141BIS-URN * Informative Reference DRAFT-PECHANEC-PKCS11URI BCP190: URI Design and Ownership (9 pages) * Replaces DRAFT-NOTTINGHAM-URI-GET-OFF-MY-LAWN * Updates RFC3986 * Normative Reference RFC2119 * Normative Reference RFC6838 * Normative Reference RFC3986 * Normative Reference BCP14 * Informative Reference RFC5988 * Possible Reference RFC5741 * Informative Reference RFC4395 * Normative Reference STD66 * Normative Reference BCP13 * Informative Reference RFC6570 * Informative Reference RFC6943 * Informative Reference RFC5785 RFC6365: Terminology Used in Internationalization in the IETF (47 pages) * Obsoletes RFC3536 * Informative Reference RFC3629 * Informative Reference RFC4647 * Informative Reference RFC3536 * Informative Reference RFC4013 * Informative Reference RFC952 * Informative Reference RFC5198 * Informative Reference RFC1123 * Informative Reference BCP14 * Informative Reference BCP19 * Informative Reference BCP18 * Normative Reference RFC2047 * Informative Reference RFC2045 * Informative Reference RFC3454 * Possible Reference RFC5741 * Informative Reference RFC1034 * Informative Reference RFC6055 * Informative Reference RFC2781 * Informative Reference BCP137 * Informative Reference RFC2277 * Informative Reference STD13 * Informative Reference RFC3492 * Informative Reference RFC3490 * Informative Reference RFC3491 * Informative Reference RFC5890 * Informative Reference RFC5892 * Informative Reference RFC5895 * Informative Reference RFC5646 * Informative Reference RFC2119 * Informative Reference STD3 * Informative Reference RFC2978 * Informative Reference BCP47 * Informative Reference STD63 * Informative Reference RFC4713 * Informative Reference RFC5322 * Informative Reference RFC5137 * Informative Reference RFC3743 * Informative Reference DRAFT-SAINTANDRE-USERNAME-INTEROP * Normative Reference DRAFT-IETF-HTTPAUTH-DIGEST-UPDATE * Normative Reference RFC6570 * Informative Reference DRAFT-IETF-IRI-3987BIS * Normative Reference RFC7231 * Informative Reference DRAFT-IETF-NFSV4-RFC3530BIS * Informative Reference DRAFT-IETF-PRECIS-FRAMEWORK * Informative Reference RFC6885 * Informative Reference DRAFT-RESCHKE-BASICAUTH-ENC * Informative Reference DRAFT-IETF-SALUD-ALERT-INFO-URNS * Informative Reference DRAFT-RESCHKE-RFC5987BIS * Informative Reference DRAFT-YEVSTIFEYEV-FTP-URI-SCHEME * Informative Reference DRAFT-IETF-XMPP-6122BIS * Informative Reference DRAFT-IUCG-INTERNET-PLUS * Informative Reference DRAFT-MELNIKOV-PRECIS-SASLPREPBIS * Informative Reference DRAFT-SAINTANDRE-PRECIS-NICKNAME * Informative Reference DRAFT-SULLIVAN-DNS-ZONE-CODEPOINT-PPLES * Informative Reference RFC6912 * Informative Reference DRAFT-IETF-PRECIS-NICKNAME * Informative Reference DRAFT-IETF-PRECIS-SASLPREPBIS * Normative Reference DRAFT-IETF-HTTPAUTH-BASICAUTH-UPDATE * Normative Reference DRAFT-IETF-RADEXT-NAI * Informative Reference DRAFT-IETF-HTTPAUTH-BASICAUTH-ENC * Normative Reference DRAFT-IETF-HTTPAUTH-DIGEST-ENCODING * Informative Reference DRAFT-SULLIVAN-RFC2277-BIS * Informative Reference DRAFT-RESCHKE-HTTP-JFV * Informative Reference DRAFT-SULLIVAN-LUCID-PROB-STMT RFC6452: The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) - Unicode 6.0 (4 pages) * Possible Reference RFC5741 * Normative Reference RFC5892 * Informative Reference DRAFT-IETF-PRECIS-FRAMEWORK * Informative Reference RFC6885 * Normative Reference DRAFT-NEMOTO-IDNA2008-IMPLEMENTATION-REPORT * Informative Reference DRAFT-KLENSIN-IDNA-5892UPD-UNICODE70 RFC6522: The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages (9 pages) * Replaces DRAFT-KUCHERAWY-RFC3462BIS * Obsoletes RFC3462 * Informative Reference RFC3464 * Normative Reference RFC2046 * Possible Reference RFC822 * Normative Reference RFC2045 * Informative Reference RFC3462 * Informative Reference RFC3461 * Normative Reference RFC5322 * Possible Reference RFC5741 * Normative Reference BCP13 * Normative Reference BCP14 * Updates RFC6533 * Normative Reference RFC6533 * Informative Reference DRAFT-ORDOGH-SPAM-REPORTING-USING-IMAP * Normative Reference DRAFT-MELNIKOV-MMHS-PROFILE RFC6647: Email Greylisting: An Applicability Statement for SMTP (17 pages) * Replaces DRAFT-KUCHERAWY-GREYLISTING-BCP * Normative Reference RFC5598 * Informative Reference RFC5782 * Normative Reference STD72 * Informative Reference RFC5322 * Possible Reference RFC5741 * Normative Reference RFC5321 * Normative Reference BCP14 * Informative Reference BCP122 * Informative Reference RFC2131 * Informative Reference RFC3022 * Informative Reference STD13 * Informative Reference RFC6710 * Informative Reference RFC7208 RFC6648: Deprecating the "X-" Prefix and Similar Constructs in Application Protocols (13 pages) * Replaces DRAFT-SAINTANDRE-XDASH * Replaces DRAFT-SAINTANDRE-XDASH-CONSIDERED-HARMFUL * Informative Reference BCP9 * Informative Reference RFC2046 * Informative Reference RFC2047 * Informative Reference RFC2045 * Informative Reference RFC4288 * Informative Reference RFC2616 * Informative Reference RFC1123 * Informative Reference RFC2068 * Informative Reference RFC4566 * Informative Reference BCP13 * Normative Reference BCP14 * Informative Reference RFC5451 * Informative Reference BCP35 * Informative Reference RFC2426 * Informative Reference RFC3864 * Possible Reference RFC5741 * Informative Reference RFC5545 * Informative Reference RFC4395 * Informative Reference RFC5727 * Informative Reference STD3 * Informative Reference RFC1154 * Informative Reference STD11 * Informative Reference RFC2822 * Informative Reference RFC4512 * Informative Reference BCP90 * Informative Reference RFC775 * Informative Reference RFC4122 * Informative Reference RFC822 * Informative Reference RFC5064 * Informative Reference BCP66 * Informative Reference BCP67 * Informative Reference RFC5646 * Informative Reference RFC737 * Informative Reference RFC743 * Normative Reference RFC2119 * Informative Reference BCP26 * Informative Reference BCP47 * Informative Reference RFC691 * Informative Reference BCP43 * Informative Reference STD66 * Informative Reference RFC2939 * Informative Reference RFC3427 * Informative Reference RFC3986 * Informative Reference BCP82 * Informative Reference RFC3406 * Normative Reference DRAFT-DULAUNOY-KAPLAN-PASSIVE-DNS-COF * Informative Reference RFC6709 * Informative Reference RFC7143 * Informative Reference DRAFT-PECHANEC-PKCS11URI * Informative Reference DRAFT-IETF-URNBIS-RFC2141BIS-URN * Informative Reference DRAFT-BORMANN-COAP-MISC * Informative Reference DRAFT-IETF-URNBIS-RFC3406BIS-URN-NS-REG * Normative Reference DRAFT-ORDOGH-SPAM-REPORTING-USING-IMAP * Informative Reference RFC6838 * Informative Reference RFC7208 * Informative Reference RFC7034 * Informative Reference RFC6963 * Informative Reference DRAFT-SAINTANDRE-URNBIS-3406BIS * Normative Reference DRAFT-BROWN-DEVICE-STOCK-UA * Informative Reference DRAFT-STROEDER-HASHED-USERPASSWORD-VALUES * Informative Reference DRAFT-RIJSMAN-SFC-METADATA-CONSIDERATIONS * Normative Reference DRAFT-DULAUNOY-DNSOP-PASSIVE-DNS-COF RFC6657: Update to MIME regarding "charset" Parameter Handling in Textual Media Types (6 pages) * Replaces DRAFT-MELNIKOV-MIME-DEFAULT-CHARSET * Updates RFC2046 * Normative Reference RFC3629 * Normative Reference RFC2046 * Informative Reference RFC2854 * Normative Reference STD63 * Informative Reference RFC2616 * Possible Reference RFC5741 * Normative Reference BCP14 * Informative Reference RFC3023 * Normative Reference RFC2119 * Informative Reference RFC7103 * Normative Reference RFC7111 * Informative Reference RFC6838 * Normative Reference RFC7303 * Normative Reference DRAFT-LILLEY-XML-MEDIATYPES RFC6694: The "about" URI Scheme (7 pages) * Replaces DRAFT-HOLSTEN-ABOUT-URI-SCHEME * Normative Reference RFC5234 * Normative Reference RFC5226 * Normative Reference STD68 * Normative Reference STD66 * Possible Reference RFC5741 * Normative Reference RFC3986 * Informative Reference BCP35 * Informative Reference RFC4395 * Normative Reference BCP26 * Normative Reference RFC7413 * Informative Reference DRAFT-NOTTINGHAM-HTTP-PROBLEM * Informative Reference DRAFT-IETF-APPSAWG-HTTP-PROBLEM RFC6729: Indicating Email Handling States in Trace Fields (12 pages) * Replaces DRAFT-KUCHERAWY-RECEIVED-STATE * Normative Reference RFC2045 * Normative Reference RFC5322 * Possible Reference RFC5741 * Normative Reference RFC5321 * Normative Reference BCP14 * Informative Reference RFC4865 * Normative Reference BCP26 RFC6838: Media Type Specifications and Registration Procedures (32 pages) * Replaces DRAFT-FREED-MEDIA-TYPE-REGS * Obsoletes RFC4288 * Normative Reference RFC3629 * Normative Reference RFC5226 * Normative Reference RFC2046 * Normative Reference RFC2045 * Informative Reference RFC4288 * Informative Reference RFC2616 * Informative Reference RFC2026 * Normative Reference BCP14 * Normative Reference BCP19 * Informative Reference RFC5987 * Normative Reference BCP79 * Normative Reference BCP78 * Normative Reference RFC4855 * Possible Reference RFC5741 * Normative Reference RFC6839 * Normative Reference RFC3023 * Informative Reference RFC2048 * Normative Reference RFC5234 * Informative Reference BCP178 * Informative Reference RFC2231 * Normative Reference RFC5378 * Normative Reference RFC3979 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference STD68 * Normative Reference RFC2978 * Normative Reference RFC6532 * Informative Reference RFC6657 * Normative Reference STD63 * Informative Reference BCP13 * Normative Reference STD66 * Informative Reference RFC6648 * Informative Reference BCP9 * Normative Reference RFC3986 * Informative Reference RFC7069 * Normative Reference DRAFT-IETF-PAYLOAD-G7110 * Possible Reference DRAFT-TURNER-APPLICATION-FIRMWARE-MEDIA-TYPES * Normative Reference RFC7193 * Informative Reference RFC7049 * Normative Reference DRAFT-IETF-MMUSIC-RFC2326BIS * Informative Reference DRAFT-SCHMERTMANN-DICE-CODTLS * Informative Reference DRAFT-HOFFMAN-XML2RFC * Informative Reference RFC7310 * Informative Reference DRAFT-IETF-PAYLOAD-RTP-HOWTO * Informative Reference DRAFT-IETF-MMUSIC-RFC4566BIS * Informative Reference RFC7230 * Informative Reference RFC7231 * Informative Reference RFC7233 * Normative Reference DRAFT-IETF-AVT-RTP-ISAC * Possible Reference RFC6884 * Informative Reference RFC7111 * Normative Reference DRAFT-IETF-ECRIT-ADDITIONAL-DATA * Normative Reference RFC7200 * Normative Reference RFC7030 * Informative Reference DRAFT-IETF-JOSE-JSON-WEB-SIGNATURE * Informative Reference DRAFT-IETF-JOSE-JSON-WEB-KEY * Reference DRAFT-IETF-PAYLOAD-VP8 * Informative Reference RFC6901 * Normative Reference DRAFT-IETF-PAYLOAD-RTP-SBC * Normative Reference RFC7061 * Informative Reference DRAFT-NOTTINGHAM-JSON-HOME * Normative Reference DRAFT-IETF-MMUSIC-SCTP-SDP * Normative Reference RFC6920 * Normative Reference DRAFT-WILDE-HOME-XML * Informative Reference DRAFT-ALIMI-PROTOCOL * Informative Reference RFC6839 * Informative Reference DRAFT-IETF-OAUTH-JSON-WEB-TOKEN * Possible Reference RFC7033 * Informative Reference DRAFT-NOTTINGHAM-HTTP-PROBLEM * Informative Reference RFC7303 * Normative Reference RFC6922 * Normative Reference DRAFT-IETF-PAYLOAD-RTP-OPUS * Normative Reference RFC7351 * Normative Reference RFC7320 * Normative Reference DRAFT-BRAY-I-JSON * Normative Reference DRAFT-GERDES-CORE-DCAF-AUTHORIZE * Normative Reference DRAFT-NOTTINGHAM-URI-GET-OFF-MY-LAWN * Informative Reference DRAFT-WILDE-LINK-DESC * Informative Reference DRAFT-RESCHKE-XML2RFC * Normative Reference DRAFT-GERDES-ACE-DCAF-AUTHORIZE * Normative Reference DRAFT-SEANTEK-TEXT-MARKDOWN-MEDIA-TYPE * Normative Reference DRAFT-IETF-ECRIT-ECALL * Informative Reference DRAFT-IETF-APPSAWG-HTTP-PROBLEM * Normative Reference DRAFT-SEANTEK-IMAGE-WMF-EMF * Normative Reference DRAFT-SEANTEK-IMAGE-BMP * Informative Reference DRAFT-SEANTEK-TEXT-MARKDOWN-USE-CASES * Normative Reference DRAFT-IETF-APPSAWG-TEXT-MARKDOWN * Normative Reference DRAFT-SEANTEK-TEXT-NFO * Reference DRAFT-UBERTI-PAYLOAD-VP9 * Normative Reference DRAFT-SEANTEK-WINDOWS-IMAGE * Informative Reference DRAFT-IAB-XML2RFCV2 * Normative Reference DRAFT-IETF-PAYLOAD-FLEXIBLE-FEC-SCHEME * Informative Reference DRAFT-IETF-APPSAWG-TEXT-MARKDOWN-USE-CASES * Informative Reference DRAFT-IETF-APPSAWG-MULTIPART-FORM-DATA RFC6839: Additional Media Type Structured Syntax Suffixes (14 pages) * Replaces DRAFT-HANSEN-MEDIA-TYPE-SUFFIX-REGS * Updates RFC3023 * Normative Reference RFC2045 * Possible Reference RFC5741 * Informative Reference BCP13 * Normative Reference RFC4627 * Normative Reference BCP14 * Informative Reference RFC6838 * Normative Reference RFC3023 * Normative Reference RFC2119 * Updates RFC7303 * Normative Reference RFC6838 * Informative Reference DRAFT-IETF-WEIRDS-JSON-RESPONSE * Possible Reference RFC7033 * Normative Reference RFC7303 * Informative Reference DRAFT-IETF-WEIRDS-USING-HTTP * Informative Reference DRAFT-WILDE-LINK-DESC RFC6901: JavaScript Object Notation (JSON) Pointer (8 pages) * Replaces DRAFT-PBRYAN-ZYP-JSON-POINTER * Normative Reference RFC5234 * Normative Reference RFC3629 * Normative Reference STD68 * Normative Reference STD63 * Informative Reference BCP13 * Normative Reference STD66 * Possible Reference RFC5741 * Normative Reference RFC4627 * Normative Reference BCP14 * Normative Reference RFC3986 * Informative Reference RFC6838 * Normative Reference RFC2119 * Normative Reference DRAFT-LUFF-RELATIVE-JSON-POINTER * Normative Reference RFC6902 * Normative Reference DRAFT-SNELL-JSON-TEST RFC6902: JavaScript Object Notation (JSON) Patch (18 pages) * Replaces DRAFT-PBRYAN-JSON-PATCH * Informative Reference RFC5261 * Informative Reference RFC2616 * Normative Reference RFC2119 * Possible Reference RFC5741 * Normative Reference RFC6901 * Normative Reference RFC4627 * Normative Reference BCP14 * Informative Reference RFC5789 * Informative Reference DRAFT-IETF-SCIM-API * Informative Reference DRAFT-SNELL-JSON-TEST * Informative Reference DRAFT-BIERMAN-NETCONF-RESTCONF * Reference DRAFT-ROOME-ALTO-INCR-UPDATES * Reference DRAFT-ROOME-ALTO-INCR-UPDATE-SSE RFC7001: Message Header Field for Indicating Message Authentication Status (43 pages) * Replaces DRAFT-KUCHERAWY-RFC5451BIS * Obsoletes RFC5451 * Obsoletes RFC6577 * Informative Reference RFC5598 * Informative Reference RFC4408 * Informative Reference RFC5617 * Normative Reference RFC2045 * Informative Reference RFC4406 * Informative Reference RFC3464 * Informative Reference RFC6212 * Normative Reference BCP14 * Informative Reference RFC5518 * Informative Reference RFC5451 * Informative Reference BCP72 * Informative Reference RFC4954 * Informative Reference RFC6541 * Informative Reference STD76 * Informative Reference BCP178 * Possible Reference RFC5741 * Normative Reference BCP90 * Informative Reference STD13 * Informative Reference RFC3501 * Possible Reference RFC822 * Informative Reference STD53 * Informative Reference RFC2119 * Informative Reference BCP26 * Normative Reference STD68 * Informative Reference RFC6577 * Normative Reference RFC5322 * Normative Reference RFC5321 * Informative Reference RFC4870 * Informative Reference RFC3596 * Normative Reference DRAFT-KUCHERAWY-AUTHRES-PTYPES-REGISTRY * Normative Reference RFC7281 * Informative Reference DRAFT-MELNIKOV-MMHS-AUTHORIZING-USERS * Informative Reference RFC7293 * Normative Reference DRAFT-MARTIN-AUTHENTICATION-RESULTS-TLS * Normative Reference RFC7372 * Normative Reference DRAFT-OTIS-TPA-LABEL * Normative Reference RFC7410 * Updates RFC7410 * Informative Reference DRAFT-KUCHERAWY-RFC7001BIS * Informative Reference DRAFT-IETF-APPSAWG-RFC7001BIS * Normative Reference DRAFT-OTIS-DMARC-AUTHOR-ALIGN * Normative Reference DRAFT-MELNIKOV-SMTP-METADATA * Informative Reference RFC7489 RFC7033: WebFinger (28 pages) * Replaces DRAFT-JONES-APPSAWG-WEBFINGER * Possible Reference RFC5226 * Informative Reference RFC6350 * Normative Reference BCP26 * Normative Reference RFC5785 * Normative Reference BCP47 * Normative Reference RFC2616 * Normative Reference STD66 * Normative Reference RFC2818 * Possible Reference RFC5741 * Normative Reference RFC5988 * Normative Reference RFC4627 * Normative Reference BCP14 * Possible Reference RFC3986 * Possible Reference RFC6839 * Possible Reference RFC6838 * Informative Reference RFC6415 * Possible Reference RFC2119 * Normative Reference BCP13 * Informative Reference RFC6068 * Informative Reference DRAFT-IETF-KITTEN-SASL-OAUTH * Informative Reference RFC7081 * Informative Reference DRAFT-SAKIMURA-JSON-META * Normative Reference DRAFT-DEJONG-REMOTESTORAGE RFC7103: Advice for Safe Handling of Malformed Messages (24 pages) * Replaces DRAFT-KUCHERAWY-MTA-MALFORMED * Informative Reference RFC5321 * Normative Reference RFC5322 * Informative Reference RFC1922 * Informative Reference RFC6532 * Informative Reference RFC733 * Informative Reference RFC1113 * Informative Reference RFC3030 * Informative Reference RFC3986 * Informative Reference RFC1468 * Informative Reference RFC2822 * Informative Reference RFC6657 * Informative Reference RFC1421 * Possible Reference RFC5741 * Informative Reference RFC6376 * Informative Reference RFC1122 * Informative Reference RFC3464 * Normative Reference RFC2045 * Informative Reference RFC1557 * Informative Reference RFC2047 * Informative Reference RFC3629 * Normative Reference RFC5598 * Informative Reference DRAFT-KUCHERAWY-EMAIL-CAPS RFC7239: Forwarded HTTP Extension (16 pages) * Replaces DRAFT-PETERSSON-FORWARDED-FOR * Normative Reference RFC3986 * Normative Reference RFC5952 * Normative Reference STD66 * Normative Reference RFC4193 * Normative Reference STD68 * Informative Reference RFC6269 * Normative Reference BCP26 * Normative Reference RFC4395 * Normative Reference RFC2119 * Normative Reference RFC5234 * Normative Reference BCP90 * Possible Reference RFC5741 * Normative Reference RFC1918 * Normative Reference RFC7230 * Normative Reference RFC7232 * Normative Reference RFC3864 * Normative Reference BCP35 * Normative Reference BCP14 * Normative Reference BCP5 * Normative Reference RFC5226 * Informative Reference DRAFT-BOUCADAIR-INTAREA-HOST-IDENTIFIER-SCENARIOS RFC7293: The Require-Recipient-Valid-Since Header Field and SMTP Service Extension (24 pages) * Replaces DRAFT-WMILLS-RRVS-HEADER-FIELD * Normative Reference BCP14 * Normative Reference RFC5321 * Normative Reference RFC5322 * Informative Reference RFC3461 * Possible Reference RFC5741 * Normative Reference BCP90 * Normative Reference RFC2142 * Informative Reference RFC7001 * Normative Reference RFC5905 * Informative Reference RFC3463 * Informative Reference RFC3464 * Normative Reference RFC3339 * Normative Reference STD68 * Informative Reference RFC5598 * Informative Reference DRAFT-IETF-APPSAWG-RFC7001BIS RFC7303: XML Media Types (35 pages) * Replaces DRAFT-LILLEY-XML-MEDIATYPES * Updates RFC6839 * Obsoletes RFC3023 * Normative Reference RFC2046 * Informative Reference RFC1557 * Normative Reference RFC2045 * Informative Reference RFC2616 * Normative Reference BCP13 * Normative Reference BCP14 * Informative Reference RFC6152 * Normative Reference RFC2781 * Normative Reference RFC6839 * Informative Reference RFC6838 * Normative Reference RFC6657 * Informative Reference RFC2376 * Informative Reference RFC3977 * Informative Reference RFC3023 * Normative Reference RFC2119 * Normative Reference RFC2978 * Normative Reference DRAFT-IETF-HTTPBIS-P1-MESSAGING * Informative Reference RFC5321 * Informative Reference RFC3030 * Normative Reference RFC3987 * Normative Reference RFC3986 * Informative Reference DRAFT-HOFFMAN-XML2RFC * Normative Reference DRAFT-IETF-ECRIT-ADDITIONAL-DATA * Informative Reference DRAFT-RESCHKE-XML2RFC * Normative Reference DRAFT-IETF-ECRIT-ECALL * Informative Reference DRAFT-IETF-APPSAWG-HTTP-PROBLEM * Normative Reference DRAFT-POT-WEBDAV-NOTIFICATIONS * Normative Reference DRAFT-POT-WEBDAV-RESOURCE-SHARING * Informative Reference DRAFT-IAB-XML2RFCV2 RFC7320: URI Design and Ownership (9 pages) * Replaces DRAFT-NOTTINGHAM-URI-GET-OFF-MY-LAWN * Updates RFC3986 * Normative Reference RFC2119 * Normative Reference RFC6838 * Normative Reference RFC3986 * Normative Reference BCP14 * Informative Reference RFC5988 * Possible Reference RFC5741 * Informative Reference RFC4395 * Normative Reference STD66 * Normative Reference BCP13 * Informative Reference RFC6570 * Informative Reference RFC6943 * Informative Reference RFC5785 * Normative Reference RFC7390 * Informative Reference DRAFT-AMUNDSEN-RICHARDSON-FOSTER-ALPS * Normative Reference DRAFT-IETF-NETCONF-RESTCONF * Informative Reference DRAFT-IETF-URNBIS-RFC2141BIS-URN RFC7352: Sieve Email Filtering: Detecting Duplicate Deliveries (15 pages) * Replaces DRAFT-BOSCH-SIEVE-DUPLICATE * Informative Reference RFC5232 * Normative Reference RFC5260 * Informative Reference RFC5490 * Normative Reference RFC5229 * Normative Reference RFC5228 * Normative Reference RFC6785 * Normative Reference BCP14 * Informative Reference RFC5437 * Normative Reference RFC5703 * Informative Reference RFC5230 * Informative Reference RFC3501 * Informative Reference RFC5435 * Normative Reference RFC6609 RFC7372: Email Authentication Status Codes (8 pages) * Replaces DRAFT-KUCHERAWY-EMAIL-AUTH-CODES * Normative Reference RFC2119 * Normative Reference BCP138 * Normative Reference RFC7208 * Normative Reference RFC6376 * Normative Reference BCP14 * Normative Reference RFC5248 * Normative Reference RFC7001 * Normative Reference RFC3463 * Normative Reference STD76 * Updates RFC7208 RFC7377: IMAP4 Multimailbox SEARCH Extension (11 pages) * Normative Reference RFC4731 * Normative Reference RFC2119 * Normative Reference RFC4466 * Possible Reference RFC6237 * Possible Reference RFC6982 * Normative Reference BCP19 * Normative Reference RFC5530 * Normative Reference BCP14 * Normative Reference RFC4314 * Informative Reference RFC6203 * Normative Reference RFC5267 * Normative Reference STD68 * Normative Reference RFC3501 * Normative Reference RFC5234 * Normative Reference RFC2978 * Normative Reference RFC5465 * Normative Reference RFC5182 * Obsoletes RFC6237 * Updates RFC4466 * Normative Reference DRAFT-JAYANTHEESH-IMAP-APPENDLIMIT-EXTENSION RFC7386: JSON Merge Patch (9 pages) * Replaces DRAFT-SNELL-MERGE-PATCH * Informative Reference RFC5789 * Normative Reference RFC7159 * Obsoletes RFC7396 * Normative Reference DRAFT-BARNES-ACME * Reference DRAFT-ROOME-ALTO-INCR-UPDATE-SSE RFC7396: JSON Merge Patch (9 pages) * Obsoletes RFC7386 RFC7410: A Property Types Registry for the Authentication-Results Header Field (5 pages) * Normative Reference RFC5321 * Possible Reference RFC5741 * Normative Reference RFC7001 * Normative Reference STD68 * Replaces DRAFT-KUCHERAWY-AUTHRES-PTYPES-REGISTRY * Normative Reference RFC5226 * Normative Reference RFC5234 * Updates RFC7001 * Normative Reference BCP26 * Informative Reference DRAFT-KUCHERAWY-RFC7001BIS * Informative Reference DRAFT-IETF-APPSAWG-RFC7001BIS STD73: The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages (9 pages) * Replaces DRAFT-KUCHERAWY-RFC3462BIS * Obsoletes RFC3462 * Informative Reference RFC3464 * Normative Reference RFC2046 * Possible Reference RFC822 * Normative Reference RFC2045 * Informative Reference RFC3462 * Informative Reference RFC3461 * Normative Reference RFC5322 * Possible Reference RFC5741 * Normative Reference BCP13 * Normative Reference BCP14 * Normative Reference RFC6533 * Normative Reference RFC6591 * Normative Reference DRAFT-MELNIKOV-MMHS-PROFILE BiDirectional or Server-Initiated HTTP (hybi) --------------------------------------------- Charter Last Modified: 2011-12-09 Current Status: Active Chairs: Salvatore Loreto Gabriel Montenegro Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Barry Leiba Secretary: S Moonesamy Mailing Lists: General Discussion: hybi@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/hybi Archive: http://www.ietf.org/mail-archive/web/hybi/ Description of Working Group: The BiDirectional or Server-Initiated HTTP (HyBi) working group defines the WebSocket Protocol, a technology for bidirectional communication between an HTTP client and an HTTP server that provides greater efficiency than previous approaches (e.g., use of hanging requests or long polling). Having completed work on the core protocol (RFC 6455), the group continues to define extensions for use by WebSocket implementations. The following extensions and optimizations are currently in scope: 1. A per-frame compression extension to improve bandwidth usage (draft-tyoshino-hybi-websocket-perframe-deflate is a likely starting point). 2. A multiplexing extension to improve the scalability of the WebSocket protocol (draft-tamplin-hybi-google-mux is a likely starting point). 3. Timeout-handling capabilities to reduce the chattiness of the protocol (draft-thomson-hybi-http-timeout is a likely starting point). The working group will also serve as a discussion venue for subprotocols. However, no subprotocol is currently chartered as a deliverable, and the WG must be rechartered to work on any subprotocols. The group will not work on an updated version of the WebSocket protocol, unless it is specifically rechartered to do so. The group will continue coordinating with the W3C WepApps working group with respect to the above deliverables and to ensure the best match possible between the WebSocket protocol and the WebSocket API. The group will also continue coordinating with other working groups within the IETF (e.g., HTTPBIS) as appropriate. Goals and Milestones: Done - Adopt a WG item for the per-frame compression extension Done - Issue WG last call on the per-frame compression extension Done - Adopt a WG for the multiplexing extension Nov 2012 - Send per-frame compression extension to IESG for consideration as a Proposed Standard Mar 2013 - Adopt a WG item for timeout handling Apr 2013 - Issue WG last call on the multiplexing extension May 2013 - Send multiplexing extension to IESG for consideration as a Proposed Standard Nov 2013 - Issue WG last call on timeout handling Dec 2013 - Send timeout handling to IESG for consideration as a Proposed Standard Internet-Drafts: - Design Space for Bidirectional Protocols [draft-ietf-hybi-design-space-00] (9 pages) - Compression Extensions for WebSocket [draft-ietf-hybi-permessage-compression-19] (32 pages) - The WebSocket Protocol [draft-ietf-hybi-thewebsocketprotocol-17] (71 pages) - A Multiplexing Extension for WebSockets [draft-ietf-hybi-websocket-multiplexing-11] (42 pages) - HyBi WebSocket Requirements and Features [draft-ietf-hybi-websocket-requirements-02] (9 pages) Requests for Comments: RFC6455: The WebSocket Protocol (71 pages) * Replaces DRAFT-HIXIE-THEWEBSOCKETPROTOCOL * Normative Reference RFC3629 * Normative Reference RFC5226 * Normative Reference RFC4648 * Normative Reference BCP106 * Normative Reference RFC2616 * Normative Reference BCP14 * Normative Reference RFC3864 * Normative Reference RFC4086 * Possible Reference RFC5741 * Normative Reference RFC5246 * Normative Reference BCP90 * Normative Reference RFC5234 * Informative Reference RFC4122 * Informative Reference RFC4270 * Informative Reference RFC6202 * Informative Reference RFC6265 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference STD68 * Normative Reference RFC6454 * Normative Reference STD63 * Normative Reference RFC1928 * Normative Reference STD66 * Normative Reference RFC2818 * Normative Reference RFC6066 * Informative Reference RFC5321 * Normative Reference RFC3986 * Normative Reference RFC3987 * Normative Reference RFC2817 * Informative Reference DRAFT-PARTHA-RTCWEB-JSEP-SIP * Normative Reference DRAFT-GARNERO-RFB-WEBSOCKET * Informative Reference RFC7288 * Informative Reference DRAFT-CHENXIN-BEHAVE-TURN-WEBSOCKET * Informative Reference DRAFT-HUTTON-RTCWEB-NAT-FIREWALL-CONSIDERATIONS * Informative Reference RFC7339 * Informative Reference DRAFT-MOFFITT-XMPP-OVER-WEBSOCKET * Informative Reference RFC6454 * Normative Reference DRAFT-IIJIMA-NETCONF-WEBSOCKET-PS * Informative Reference DRAFT-THOMSON-HYBI-HTTP-TIMEOUT * Normative Reference DRAFT-TYOSHINO-HYBI-WEBSOCKET-PERFRAME-DEFLATE * Informative Reference DRAFT-IETF-RTCWEB-SECURITY * Normative Reference DRAFT-IBC-SIPCORE-SIP-WEBSOCKET * Normative Reference DRAFT-TAMPLIN-HYBI-GOOGLE-MUX * Normative Reference DRAFT-BARNES-ATOCA-META * Normative Reference DRAFT-PD-DISPATCH-MSRP-WEBSOCKET * Informative Reference DRAFT-STEPHAN-CDNI-ALTO-SESSION-EXT * Normative Reference DRAFT-MONTENEGRO-HTTPBIS-SPEED-MOBILITY * Normative Reference DRAFT-IETF-HYBI-WEBSOCKET-PERFRAME-COMPRESSION * Normative Reference DRAFT-IETF-HYBI-WEBSOCKET-MULTIPLEXING * Informative Reference RFC7118 * Informative Reference DRAFT-ABOBA-RTCWEB-ECRIT * Normative Reference DRAFT-TYOSHINO-HYBI-PERMESSAGE-COMPRESSION * Informative Reference DRAFT-BLANCHET-IAB-INTERNETOVERPORT443 * Normative Reference DRAFT-MAROCCO-ALTO-WS * Informative Reference DRAFT-THOMSON-RTCWEB-API-REQS * Informative Reference DRAFT-MINIERO-RTCWEB-HTTP-FALLBACK * Normative Reference DRAFT-IETF-HYBI-PERMESSAGE-COMPRESSION * Normative Reference DRAFT-PD-MSRP-WEBSOCKET * Informative Reference DRAFT-MONTENEGRO-HTTPBIS-HTTP2-NEGOTIATION * Informative Reference DRAFT-MONTENEGRO-HTTPBIS-HTTP2-FC-PRINCIPLES * Normative Reference DRAFT-PASCUAL-DISPATCH-BFCP-WEBSOCKET * Informative Reference DRAFT-THOMSON-RTCWEB-DATA * Informative Reference DRAFT-SILVERAJAN-CORE-COAP-ALTERNATIVE-TRANSPORTS * Normative Reference DRAFT-SAVOLAINEN-CORE-COAP-WEBSOCKETS * Normative Reference RFC7395 * Informative Reference DRAFT-IETF-RTCWEB-DATA-PROTOCOL * Normative Reference DRAFT-REALVNC-WEBSOCKET * Informative Reference DRAFT-IETF-PCP-OPTIMIZE-KEEPALIVES * Informative Reference DRAFT-NOTTINGHAM-HTTP-PROXY-PROBLEM * Informative Reference DRAFT-LORETO-HTTPBIS-TRUSTED-PROXY20 * Normative Reference RFC7355 * Normative Reference DRAFT-PASCUAL-BFCPBIS-BFCP-WEBSOCKET * Reference DRAFT-ROOME-ALTO-INCR-UPDATES * Normative Reference DRAFT-HIRANO-HTTPBIS-WEBSOCKET-OVER-HTTP2 * Normative Reference DRAFT-IETF-BFCPBIS-BFCP-WEBSOCKET * Informative Reference DRAFT-LORETO-HTTPBIS-EXPLICITLY-AUTH-PROXY * Normative Reference DRAFT-VANREIN-6BED4 * Informative Reference DRAFT-MMUSIC-DATA-CHANNEL-SDPNEG * Informative Reference DRAFT-IETF-MMUSIC-DATA-CHANNEL-SDPNEG * Normative Reference DRAFT-TSUZAKI-NETCONFIG-WEBAPI * Informative Reference DRAFT-IETF-TAPS-TRANSPORTS * Informative Reference DRAFT-IETF-RTCWEB-SECURITY-ARCH * Informative Reference DRAFT-MM-WG-EFFECT-ENCRYPT * Normative Reference DRAFT-HUITEMA-TLS-TLSOVERHTTP * Normative Reference DRAFT-RAM-BFCPBIS-SDP-WS-URI Calendaring Extensions (calext) ------------------------------- Charter Last Modified: 2014-08-28 Current Status: Active Chairs: Amanda Anganes Donald E. Eastlake 3rd Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Barry Leiba Mailing Lists: General Discussion: calsify@ietf.org To Subscribe: http://www.ietf.org/mailman/listinfo/calsify Archive: http://www.ietf.org/mail-archive/web/calsify/ Description of Working Group: The Calendaring Extensions working group is chartered to develop extensions to the iCalendar (RFC 5545), iTIP (RFC 5546), and CalDAV (RFC 4791) standards. This working group will do the following: - Develop an extension to iCalendar to support non-Gregorian recurrence rules, without the need to support new calendar scale values in iCalendar as a whole. This will allow for easy implementation of the primary use case for non-Gregorian support in calendar systems, without the need for significant changes to the iCalendar format. The non-Gregorian calendar system should be based on the International Components for Unicode work by the Unicode Consortium (http://site.icu-project.org). - Develop an extension to iCalendar to support a new component type that allows users to express arbitrary, possibly repeating, periods of "available" time. The primary use case for this is for users to express their "office hours" (e.g., Monday-Friday, 9am-5pm) in a standard way to ensure free busy lookups show the correct periods of availability. - Define a set of new iCalendar properties and parameters to standardise some existing experimental X- properties in common use, based on a survey of existing implementations. - Define a set of new iCalendar properties and parameters to cover key uses cases that implementers have identified, including, but not limited to, a new "IMAGE" property (to allow embedding/linking of images tied to a specific event), and a "CONFERENCE" property (to allow embedding information about dial-in numbers and similar multi-party communication options for an event). The working group will work under the following parameters: - The extensions developed are expected to be backwards-compatible with the existing calendar standards. Incompatibilities must be identified, minimized, and justified. - For each set of extensions, examine their impact on the iTIP protocol (RFC 5546), and define any necessary extensions to iTIP to accommodate such impact. - For each set of extensions, examine their impact on the CalDAV protocol (RFC 4791), and define any necessary extensions to CalDAV to accommodate such impact. Interface with the httpbis working group to ensure that any CalDAV changes are consistent with good http practices. The working group will use the following drafts as initial input for its work: draft-daboo-icalendar-rscale-03 draft-daboo-calendar-availability-05 draft-daboo-icalendar-extensions-08 The following are out of scope for the working group: - Any change that impacts backwards compatibility with existing deployed iCalendar/iTIP/CalDAV clients and servers will be discussed by the working group with a view to minimizing disruption to deployed implementations without compromising desirable new function. - Any attempt to develop non-Gregorian calendar systems/calculations. Goals and Milestones: Dec 2014 - Submit non-Gregorian recurrence rule draft to IESG for publication Jan 2015 - WG adoption of an availability draft Jan 2015 - WG adoption of an extensions draft Mar 2015 - Submit availability draft to IESG for publication Mar 2015 - Submit extensions draft to IESG for publication Internet-Drafts: - Calendar Availability [draft-daboo-calendar-availability-05] (22 pages) - New Properties for iCalendar [draft-daboo-icalendar-extensions-09] (21 pages) - Non-Gregorian Recurrence Rules in iCalendar [draft-daboo-icalendar-rscale-04] (15 pages) - Non-Gregorian Recurrence Rules in iCalendar [draft-ietf-calext-rscale-04] (22 pages) No Requests for Comments Constrained RESTful Environments (core) --------------------------------------- Charter Last Modified: 2012-09-10 Current Status: Active Chairs: Dr. Carsten Bormann Andrew McGregor Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Barry Leiba Mailing Lists: General Discussion: core@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/core Archive: http://www.ietf.org/mail-archive/web/core/ Description of Working Group: CoRE is providing a framework for resource-oriented applications intended to run on constrained IP networks. A constrained IP network has limited packet sizes, may exhibit a high degree of packet loss, and may have a substantial number of devices that may be powered off at any point in time but periodically "wake up" for brief periods of time. These networks and the nodes within them are characterized by severe limits on throughput, available power, and particularly on the complexity that can be supported with limited code size and limited RAM per node. More generally, we speak of constrained networks whenever at least some of the nodes and networks involved exhibit these characteristics. Low-Power Wireless Personal Area Networks (LoWPANs) are an example of this type of network. Constrained networks can occur as part of home and building automation, energy management, and the Internet of Things. The CoRE working group will define a framework for a limited class of applications: those that deal with the manipulation of simple resources on constrained networks. This includes applications to monitor simple sensors (e.g. temperature sensors, light switches, and power meters), to control actuators (e.g. light switches, heating controllers, and door locks), and to manage devices. The general architecture consists of nodes on the constrained network, called Devices, that are responsible for one or more Resources that may represent sensors, actuators, combinations of values or other information. Devices send messages to change and query resources on other Devices. Devices can send notifications about changed resource values to Devices that have subscribed to receive notification about changes. A Device can also publish or be queried about its resources. (Typically a single physical host on the network would have just one Device but a host might represent multiple logical Devices. The specific terminology to be used here is to be decided by the WG.) As part of the framework for building these applications, the WG will define a Constrained Application Protocol (CoAP) for the manipulation of Resources on a Device. CoAP will be designed for use between Devices on the same constrained network, between Devices and general nodes on the Internet, and between Devices on different constrained networks both joined by an internet. CoAP targets the type of operating environments defined in the ROLL and 6LOWPAN working groups which have additional constraints compared to normal IP networks, but the CoAP protocol will also operate over traditional IP networks. There also may be proxies that interconnect between other Internet protocols and the Devices using the CoAP protocol. The WG will define a mapping from CoAP to an HTTP REST API; this mapping will not depend on a specific application. It is worth noting that proxy does not have to occur at the boundary between the constrained network and the more general network, but can be deployed at various locations in the unconstrained network. CoAP will support various forms of "caching". For example, if a temperature sensor is normally asleep but wakes up every five minutes and sends the current temperature to a proxy that has subscribed, when the proxy receives a request over HTTP for that temperature resource, it can respond with the last seen value instead of trying to query the Device which is currently asleep. The initial work item of the WG is to define a protocol specification for CoAP that includes: 1) The ability to create, read, update and delete a Resource on a Device. 2) The ability to allow a Device to publish a value or event to another Device that has subscribed to be notified of changes, as well as the way for a Device to subscribe to receive publishes from another Device. 3) The ability to support a non-reliable multicast message to be sent to a group of Devices to manipulate a resource on all the Devices in the group. 4) The core CoAP functionality MUST operate well over UDP and UDP MUST be implemented on CoAP Devices. There may be OPTIONAL functions in CoAP (e.g. delivery of larger chunks of data) which if implemented are implemented over TCP. Applications which require the optional TCP features will limit themselves to a narrower subset of deployment cases. 5) A definition of how to use CoAP to advertise about or query for a Device's description. This description may include the device name and a list of its Resources, each with a URL, an interface description URI (pointing e.g. to a Web Application Description Language (WADL) document) and an optional name or identifier. The name taxonomy used for this description will be consistent with other IETF work, e.g. draft-cheshire-dnsext-dns-sd. 6) Specification for the HTTP REST based API and translation to communicate with Devices. Translation should make use of Device description information and should not need code updates to deal with new Devices. 7) Consider operational and manageability aspects of the protocol and at a minimum provide a way to tell if a Device is powered on or not. The working group will not develop a reliable multicast solution, and will not develop a general service discovery solution. There is a desire for discovery and configuration features, but the working group has not yet closed in on an specific approach. Thus, the WG may explore these topics and adopt drafts that define requirements or set problem statements, but will not adopt implementable specifications without a recharter. Security, particularly keying of new Devices, is very challenging for these applications. The WG will work to select approaches to security bootstrapping which are realistic given the constraints and requirements of the network. To ensure that any two nodes can join together, all nodes must implement at least one universal bootstrapping method. Security can be achieved using either session security or object security. For both object and session security, the WG will work with the security area to select appropriate security framework and protocol as well as selecting a minimal required to implement cipher suite. CoAP will initially look at CMS (RFC 5652), TLS/DTLS, and EAP. The WG will coordinate on requirements from many organizations including OpenSG/NIST, ZigBee/HomePlug, IPSO Alliance, OASIS, SENSEI, ASHRAE/BACnet; other SDOs and organizations. The WG will closely coordinate with other IETF WGs including ROLL, 6LoWPAN, and appropriate groups in the IETF OPS and Security areas. Goals and Milestones: Done - Select WG document for basis of the CoAP protocol Done - CoAP protocol specification with mapping to HTTP Rest API submitted to IESG as PS Done - Group Communication for CoAP submitted to IESG Done - Observing Resources in CoAP submitted to IESG Oct 2013 - Blockwise transfers in CoAP submitted to IESG Jan 2014 - Best Practices for HTTP-CoAP Mapping Implementation submitted to IESG Jan 2014 - Representing CoRE Link Collections in JSON submitted to IESG May 2014 - CoRE Interfaces submitted to IESG Dec 2099 - HOLD (date TBD) Constrained security bootstrapping specification submitted to IESG Internet-Drafts: - Block-wise transfers in CoAP [draft-ietf-core-block-17] (33 pages) - The Constrained Application Protocol (CoAP) [draft-ietf-core-coap-18] (112 pages) - Group Communication for the Constrained Application Protocol (CoAP) [draft-ietf-core-groupcomm-25] (46 pages) - Guidelines for HTTP-CoAP Mapping Implementations [draft-ietf-core-http-mapping-06] (32 pages) - CoRE Interfaces [draft-ietf-core-interfaces-02] (24 pages) - Constrained RESTful Environments (CoRE) Link Format [draft-ietf-core-link-format-14] (22 pages) - Representing CoRE Link Collections in JSON [draft-ietf-core-links-json-02] (7 pages) - Observing Resources in CoAP [draft-ietf-core-observe-16] (34 pages) - CoRE Resource Directory [draft-ietf-core-resource-directory-02] (37 pages) Requests for Comments: RFC6690: Constrained RESTful Environments (CoRE) Link Format (22 pages) * Replaces DRAFT-SHELBY-CORE-LINK-FORMAT * Normative Reference RFC3629 * Normative Reference RFC5226 * Informative Reference RFC4287 * Informative Reference RFC2045 * Normative Reference RFC4288 * Normative Reference RFC2616 * Normative Reference RFC5988 * Normative Reference BCP14 * Normative Reference RFC5987 * Informative Reference RFC4919 * Possible Reference RFC5741 * Informative Reference RFC1034 * Informative Reference RFC1035 * Informative Reference STD13 * Normative Reference RFC5234 * Informative Reference RFC2231 * Informative Reference RFC5785 * Normative Reference RFC5646 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference STD68 * Normative Reference BCP47 * Normative Reference RFC6570 * Normative Reference STD63 * Normative Reference BCP13 * Normative Reference STD66 * Normative Reference RFC3986 * Informative Reference RFC6454 * Normative Reference DRAFT-IETF-CORE-LINKS-JSON * Informative Reference DRAFT-VANDERSTOK-CORE-COMI * Normative Reference DRAFT-IETF-CORE-RESOURCE-DIRECTORY * Normative Reference DRAFT-ISHAQ-CORE-ENTITIES * Normative Reference DRAFT-DIJK-CORE-SLEEPY-SOLUTIONS * Normative Reference DRAFT-IETF-CORE-HTTP-MAPPING * Normative Reference DRAFT-IETF-CORE-INTERFACES * Normative Reference RFC7252 * Informative Reference DRAFT-IETF-CORE-OBSERVE * Informative Reference DRAFT-IETF-CORE-BLOCK * Normative Reference RFC7089 * Normative Reference DRAFT-SHELBY-CORE-RESOURCE-DIRECTORY * Normative Reference DRAFT-LYNN-CORE-DISCOVERY-MAPPING * Normative Reference DRAFT-DIJK-CORE-GROUPCOMM-MISC * Normative Reference DRAFT-BORMANN-CORE-LINKS-JSON * Normative Reference DRAFT-JIMENEZ-P2PSIP-COAP-RELOAD * Normative Reference DRAFT-BORMANN-CORE-ROADMAP * Normative Reference DRAFT-GREEVENBOSCH-CORE-PROFILE-DESCRIPTION * Normative Reference DRAFT-RAHMAN-CORE-SLEEPY * Normative Reference DRAFT-FOSSATI-CORE-PUBLISH-OPTION * Normative Reference DRAFT-SUZNJEVIC-TSVWG-MTD-TCMTF * Informative Reference DRAFT-GREEVENBOSCH-COMAN-CANDIDATE-TECH * Normative Reference DRAFT-ARKKO-LWIG-CELLULAR * Normative Reference DRAFT-JIMENEZ-DISTRIBUTED-RESOURCE-DIRECTORY * Informative Reference DRAFT-GERDES-CORE-DCAF-AUTHORIZE * Normative Reference DRAFT-IETF-LWIG-CELLULAR * Normative Reference DRAFT-FOSSATI-CORE-GEO-LINK-FORMAT-ATTRIBUTE * Informative Reference DRAFT-RAHMAN-CORE-SLEEPY-NODES-DO-WE-NEED * Informative Reference DRAFT-VANDERSTOK-DNSSD-BUILDING-REQUIREMENTS * Informative Reference DRAFT-IETF-LWIG-ENERGY-EFFICIENT * Normative Reference DRAFT-HONG-CORE-COAP-ENDPOINT-UNIT-ID * Informative Reference DRAFT-GERDES-ACE-DCAF-AUTHORIZE * Normative Reference DRAFT-KOSTER-CORE-COAPMQ * Normative Reference DRAFT-LI-CORE-LINKS-CBOR * Normative Reference RFC7390 * Informative Reference DRAFT-IETF-DICE-PROFILE * Normative Reference DRAFT-KOSTER-CORE-COAP-PUBSUB * Informative Reference DRAFT-JENNINGS-CORE-SENML * Informative Reference DRAFT-KUMAR-6LO-SELECTIVE-BOOTSTRAP * Normative Reference DRAFT-ZOTTI-CORE-SLEEPY-NODES * Normative Reference DRAFT-LI-CORE-CBOR-EQUIVALENTS RFC7252: The Constrained Application Protocol (CoAP) (112 pages) * Replaces DRAFT-SHELBY-CORE-COAP * Normative Reference RFC3629 * Normative Reference RFC5226 * Informative Reference BCP145 * Normative Reference RFC2046 * Informative Reference BCP165 * Informative Reference DRAFT-IETF-LWIG-TERMINOLOGY * Normative Reference RFC2045 * Informative Reference DRAFT-ALLMAN-TCPM-RTO-CONSIDER * Informative Reference RFC2560 * Normative Reference RFC768 * Informative Reference BCP106 * Informative Reference RFC2616 * Normative Reference RFC5988 * Informative Reference RFC4627 * Normative Reference BCP14 * Informative Reference DRAFT-IETF-CORE-BLOCK * Normative Reference BCP35 * Informative Reference RFC6090 * Informative Reference RFC3828 * Informative Reference DRAFT-IETF-CORE-GROUPCOMM * Informative Reference RFC5489 * Informative Reference RFC4086 * Informative Reference RFC6335 * Normative Reference RFC4395 * Informative Reference DRAFT-IETF-TLS-MULTIPLE-CERT-STATUS-EXTENSION * Normative Reference RFC6690 * Normative Reference RFC5147 * Informative Reference RFC4443 * Possible Reference RFC3307 * Informative Reference DRAFT-IETF-CORE-OBSERVE * Normative Reference DRAFT-MCGREW-TLS-AES-CCM-ECC * Informative Reference DRAFT-KIVINEN-IPSECME-IKEV2-MINIMAL * Normative Reference RFC3023 * Informative Reference RFC6655 * Normative Reference RFC5234 * Informative Reference DRAFT-IETF-TLS-OOB-PUBKEY * Normative Reference RFC5480 * Informative Reference RFC3264 * Normative Reference RFC4279 * Informative Reference RFC6936 * Informative Reference RFC3542 * Normative Reference RFC5198 * Normative Reference RFC5785 * Informative Reference RFC5405 * Informative Reference RFC4492 * Informative Reference RFC4944 * Normative Reference RFC6347 * Informative Reference RFC4821 * Informative Reference RFC2119 * Normative Reference BCP26 * Normative Reference STD68 * Informative Reference RFC6120 * Informative Reference DRAFT-BORMANN-COAP-MISC * Normative Reference RFC3676 * Normative Reference STD63 * Informative Reference RFC793 * Informative Reference RFC792 * Normative Reference STD66 * Informative Reference RFC2818 * Normative Reference RFC6066 * Normative Reference RFC5952 * Informative Reference RFC20 * Normative Reference RFC3986 * Informative Reference DRAFT-CASTELLANI-CORE-HTTP-MAPPING * Informative Reference RFC5280 * Informative Reference RFC6282 * Normative Reference RFC5246 * Possible Reference RFC5771 * Normative Reference RFC6920 * Informative Reference DRAFT-BORMANN-CORE-IPSEC-FOR-COAP * Informative Reference DRAFT-IETF-CORE-RESOURCE-DIRECTORY * Informative Reference DRAFT-IETF-CORE-INTERFACES * Normative Reference DRAFT-IETF-6TISCH-TERMINOLOGY * Informative Reference DRAFT-IETF-6TISCH-TSCH * Normative Reference DRAFT-SCHMERTMANN-DICE-CODTLS * Informative Reference DRAFT-WANG-6TISCH-6TOP-COAPIE * Normative Reference DRAFT-BORMANN-CORE-ACE-AIF * Informative Reference DRAFT-BORMANN-COAP-MISC * Informative Reference DRAFT-BECKER-CORE-COAP-SMS-GPRS * Normative Reference DRAFT-LI-CORE-COAP-NODE-ID-OPTION * Informative Reference DRAFT-CLAUSEN-LLN-RPL-EXPERIENCES * Normative Reference DRAFT-LI-CORE-CONDITIONAL-OBSERVE * Normative Reference DRAFT-SALDANA-TSVWG-TCMTF * Normative Reference DRAFT-JIMENEZ-P2PSIP-COAP-RELOAD * Normative Reference DRAFT-LI-CORE-COAP-PATIENCE-OPTION * Normative Reference DRAFT-LI-CORE-COAP-PAYLOAD-LENGTH-OPTION * Normative Reference DRAFT-SUZNJEVIC-TSVWG-MTD-TCMTF * Informative Reference DRAFT-SILVERAJAN-CORE-COAP-ALTERNATIVE-TRANSPORTS * Normative Reference DRAFT-IETF-LWIG-CELLULAR * Informative Reference DRAFT-THOMSON-HTTP-NICE * Informative Reference DRAFT-KUMAR-DICE-DTLS-RELAY * Informative Reference DRAFT-SEITZ-ACE-USECASES * Informative Reference DRAFT-SCHMERTMANN-DICE-CCM-PSK-PFS * Normative Reference DRAFT-IETF-LWIG-COAP * Normative Reference DRAFT-KLEINE-CORE-COAP-ENDPOINT-ID * Informative Reference DRAFT-IETF-6TISCH-COAP * Informative Reference DRAFT-SEITZ-ACE-PROBLEM-DESCRIPTION * Informative Reference DRAFT-GERDES-ACE-ACTORS * Informative Reference DRAFT-RICHARDSON-6TISCH--SECURITY-6TOP * Normative Reference DRAFT-TSCHOFENIG-ACE-OAUTH-IOT * Normative Reference DRAFT-TSCHOFENIG-ACE-OAUTH-BT * Normative Reference DRAFT-HONG-CORE-COAP-ENDPOINT-UNIT-ID * Normative Reference DRAFT-GERDES-ACE-DCAF-AUTHORIZE * Normative Reference DRAFT-KOSTER-CORE-COAPMQ * Normative Reference DRAFT-IETF-CORE-OBSERVE * Normative Reference DRAFT-BORMANN-CORE-CC-QQ * Normative Reference DRAFT-TCS-COAP-NO-RESPONSE-OPTION * Possible Reference DRAFT-LI-CORE-LINKS-CBOR * Normative Reference RFC7390 * Normative Reference DRAFT-TSCHOFENIG-CORE-COAP-TCP-TLS * Informative Reference RFC7388 * Normative Reference DRAFT-KANG-ACE-SECURE-CONFIGURATION * Normative Reference DRAFT-IETF-CORE-HTTP-MAPPING * Normative Reference DRAFT-GREEVENBOSCH-ACE-PULL-MODEL * Normative Reference DRAFT-CHOI-DICE-FINEGRAINED-DTLS-SECURITY * Informative Reference DRAFT-IETF-LWIG-ENERGY-EFFICIENT * Normative Reference DRAFT-IETF-CORE-BLOCK * Informative Reference DRAFT-SELANDER-ACE-OBJECT-SECURITY * Informative Reference DRAFT-IETF-OPSAWG-COMAN-PROBSTATE-REQS * Normative Reference DRAFT-KOSTER-CORE-COAP-PUBSUB * Informative Reference DRAFT-BORMANN-JOSE-COSE * Normative Reference DRAFT-VANDERSTOK-CORE-COMI * Informative Reference DRAFT-JENNINGS-CORE-SENML * Informative Reference DRAFT-IETF-ACE-USECASES * Informative Reference DRAFT-IETF-DICE-PROFILE * Informative Reference DRAFT-KUMAR-6LO-SELECTIVE-BOOTSTRAP * Normative Reference DRAFT-VANDERSTOK-CORE-PATCH * Normative Reference DRAFT-FOSSATI-CORE-CERTMODE-RD-NAMES * Normative Reference DRAFT-ZOTTI-CORE-SLEEPY-NODES * Possible Reference DRAFT-LI-CORE-CBOR-EQUIVALENTS * Normative Reference DRAFT-HE-6LO-ANALYSIS-IOT-SBOOTSTRAPPING * Normative Reference DRAFT-MALER-ACE-OAUTH-UMA * Normative Reference DRAFT-KUMAR-DICE-MULTICAST-SECURITY * Normative Reference DRAFT-SILVERAJAN-CORE-COAP-PROTOCOL-NEGOTIATION * Normative Reference DRAFT-WAHLSTROEM-ACE-OAUTH-INTROSPECTION RFC7390: Group Communication for the Constrained Application Protocol (CoAP) (46 pages) * Replaces DRAFT-RAHMAN-CORE-GROUPCOMM * Normative Reference RFC5110 * Normative Reference RFC7320 * Normative Reference RFC6775 * Normative Reference RFC3986 * Normative Reference RFC5952 * Normative Reference RFC7159 * Normative Reference RFC6092 * Normative Reference STD66 * Informative Reference RFC7346 * Informative Reference DRAFT-IETF-ROLL-TRICKLE-MCAST * Normative Reference BCP188 * Normative Reference RFC5771 * Informative Reference DRAFT-IETF-CORE-RESOURCE-DIRECTORY * Normative Reference RFC6550 * Informative Reference RFC3810 * Normative Reference RFC2119 * Normative Reference RFC4944 * Informative Reference DRAFT-MGLT-DICE-IPSEC-FOR-APPLICATION-PAYLOAD * Normative Reference RFC3542 * Normative Reference RFC4291 * Normative Reference RFC6763 * Normative Reference RFC2782 * Informative Reference RFC6636 * Informative Reference DRAFT-IETF-CORE-OBSERVE * Informative Reference RFC1033 * Normative Reference RFC3433 * Possible Reference RFC5741 * Informative Reference RFC5740 * Normative Reference RFC6690 * Informative Reference DRAFT-KEOH-DICE-MULTICAST-SECURITY * Normative Reference RFC4919 * Normative Reference RFC7258 * Normative Reference RFC7230 * Normative Reference RFC7252 * Normative Reference RFC4601 * Informative Reference RFC4605 * Informative Reference DRAFT-IETF-CORE-BLOCK * Normative Reference BCP14 * Normative Reference BCP51 * Normative Reference RFC3376 * Informative Reference DRAFT-VANDERSTOK-CORE-COMI * Informative Reference DRAFT-SILVERAJAN-CORE-COAP-ALTERNATIVE-TRANSPORTS * Informative Reference DRAFT-IETF-DICE-PROFILE * Informative Reference DRAFT-IETF-CORE-HTTP-MAPPING * Informative Reference DRAFT-IETF-ROLL-APPLICABILITY-HOME-BUILDING * Normative Reference DRAFT-TCS-COAP-NO-RESPONSE-OPTION * Informative Reference DRAFT-KUMAR-6LO-SELECTIVE-BOOTSTRAP * Normative Reference DRAFT-ZOTTI-CORE-SLEEPY-NODES * Normative Reference DRAFT-LI-CORE-CBOR-EQUIVALENTS * Normative Reference DRAFT-KUMAR-DICE-MULTICAST-SECURITY Domain-based Message Authentication, Reporting & Conformance (dmarc) -------------------------------------------------------------------- Charter Last Modified: 2014-08-11 Current Status: Active Chairs: Ned Freed Tim Draegen Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Pete Resnick Mailing Lists: General Discussion: dmarc@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/dmarc Archive: http://www.ietf.org/mail-archive/web/dmarc/ Description of Working Group: Domain-based Message Authentication, Reporting & Conformance (DMARC) uses existing mail authentication technologies (SPF and DKIM) to extend validation to the RFC5322.From field. DMARC uses DNS records to add policy-related requests for receivers and defines a feedback mechanism from receivers back to domain owners. This allows a domain owner to advertise that mail can safely receive differential handling, such as rejection, when the use of the domain name in the From field is not authenticated. Existing deployment of DMARC has demonstrated utility at internet scale, in dealing with significant email abuse, and has permitted simplifying some mail handling processes. However, DMARC is problematic for mail that does not flow from operators having a relationship with the domain owner, directly to receivers operating the destination mailbox (for example, mailing lists, publish-to-friend functionality, mailbox forwarding via ".forward", and third-party services that send on behalf of clients). The working group will explore possible updates and extensions to the specifications in order to address limitations and/or add capabilities. It will also provide technical implementation guidance and review possible enhancements elsewhere in the mail handling sequence that could improve DMARC compatibility. The existing DMARC base specification has been submitted as an Independent Submission to become an Informational RFC. Specifications produced by the working group will ensure preservation of DMARC utility for detecting unauthorized use of domain names, while improving the identification of legitimate sources that do not currently conform to DMARC requirements. Issues based on operational experience and/or data aggregated from multiple sources will be given priority. The working group will seek to preserve interoperability with the installed base of DMARC systems, and provide detailed justification for any non-interoperability. As the working group develops solutions to deal with indirect mail flows, it will seek to maintain the end-to-end nature of existing identifier fields in mail, in particular avoiding solutions that require rewriting of originator fields. Working group activities will pursue three tracks: 1. Addressing the issues with indirect mail flows The working group will specify mechanisms for reducing or eliminating the DMARC's effects on indirect mail flows, including deployed behaviors of many different intermediaries, such as mailing list managers, automated mailbox forwarding services, and MTAs that perform enhanced message handling that results in message modification. Among the choices for addressing these issues are: - A form of DKIM signature that is better able to survive transit through intermediaries. - Collaborative or passive transitive mechanisms that enable an intermediary to participate in the trust sequence, propagating authentication directly or reporting its results. - Message modification by an intermediary, to avoid authentication failures, such as by using specified conventions for changing the aligned identity. Consideration also will be given to survivable authentication through sequences of multiple intermediaries. 2. Reviewing and improving the base DMARC specification The working group will not develop additional mail authentication technologies, but may document authentication requirements that are desirable. The base specification relies on the ability of an email receiver to determine the organizational domain responsible for sending mail. An organizational domain is the 'base' name that is allocated from a public registry; examples of registries include ".com" or ".co.uk". While the common practice is to use a "public suffix" list to determine organizational domain, it is widely recognized that this solution will not scale, and that the current list often is inaccurate. The task of defining a standard mechanism for identifying organizational domain is out of scope for this working group. However the working group can consider extending the base DMARC specification to accommodate such a standard, should it be developed during the life of this working group. Improvements in DMARC features (identifier alignment, reporting, policy preferences) will be considered, such as: - Enumeration of data elements required in "Failure" reports (specifically to address privacy issues) - Handling potential reporting abuse - Aggregate reporting to support additional reporting scenarios - Alternate reporting channels - Utility of arbitrary identifier alignment - Utility of a formalized policy exception mechanism 3. DMARC Usage The working group will document operational practices in terms of configuration, installation, monitoring, diagnosis and reporting. It will catalog currently prevailing guidelines as well as developing advice on practices that are not yet well-established but which are believed to be appropriate. The group will consider separating configuration and other deployment information that needs to be in the base spec, from information that should be in a separate guide. Among the topics anticipated to be included in the document are: - Identifier alignment configuration options - Implementation decisions regarding "pct" - Determining effective RUA sending frequency - Leveraging policy caching - Various options for integrating within an existing flow - Defining a useful, common set of options for the addresses to which feedback reports are to be sent - When and how to use local policy override options Work Items ---------- Phase I: Draft description of interoperability issues for indirect mail flows and plausible methods for reducing them. Phase II: Specification of DMARC improvements to support indirect mail flows Draft Guide on DMARC Usage Phase III: Review and refinement of the DMARC specification Completion of Guide on DMARC Usage References ---------- DMARC - http://dmarc.org SPF - RFC7208 Authentication-Results Header Field - RFC7001 DKIM - RFC6376 Internet Message Format - RFC5322 OAR / Original Authentication Results - draft-kucherawy-original-authres Using DMARC - draft-crocker-dmarc-bcp-03 Delegating DKIM Signing Authority - draft-kucherawy-dkim-delegate-00 DKIM Third-Party Authorization Label - draft-otis-dkim-tpa-label-03 Goals and Milestones: Feb 2015 - Complete draft on DMARC interop issues + possible methods to address Mar 2015 - Complete draft specification of DMARC improvements to better support indirect email flows May 2015 - Complete draft DMARC Usage Guide May 2015 - Complete draft on changes to DMARC base spec Internet-Drafts: - Interoperability Issues Between DMARC and Indirect Email Flows [draft-dmarc-interoperability-00] (16 pages) - Interoperability Issues Between DMARC and Indirect Email Flows [draft-ietf-dmarc-interoperability-00] (16 pages) No Requests for Comments Extensible Provisioning Protocol Extensions (eppext) ---------------------------------------------------- Charter Last Modified: 2013-12-18 Current Status: Active Chairs: Antoin Verschuren Dr. James M. Galvin Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Pete Resnick Mailing Lists: General Discussion: eppext@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/eppext Archive: http://www.ietf.org/mail-archive/web/eppext/ Description of Working Group: The Extensible Provisioning Protocol (EPP) was a work product of the IETF Provisioning Registry Protocol (provreg) working group. EPP was published as a Proposed Standard (RFCs 3730, 3731, 3732, 3733, and 3734) in March 2004. It became a Draft Standard (RFCs 4930, 4931, 4932, 4933, and 4934) in May 2007, and a Standard (Standard 69; RFCs 5730, 5731, 5732, 5733, and 5734) in August 2009. It is the standard domain name provisioning protocol for generic top-level domain name registries that operate under the auspices of the Internet Corporation for Assigned Names and Numbers (ICANN). It is also used by a number of country code top-level domain registries. Domain name registries implement a variety of business models. The difference in these models made it very difficult to come up with a "one size fits all" provisioning protocol, so the provreg working group made a conscious decision to focus on a minimal set of common functionality. EPP was designed to be extensible to allow additional features to be specified on an "as needed" basis. Guidelines for extending EPP were published as Informational RFC 3735 in March 2004. The provreg working group was chartered to develop EPP, but not these additional extensions. The working group was closed in 2004 after producing a number of Proposed Standard specifications. As registries began to implement and deploy EPP the need for extensions became real, and the user community found itself facing a situation in which multiple extensions were being developed by different registries to solve the same basic problems, such as registering additional contact information. EPP is widely implemented by generic top-level domain name registry operators. It is also used by multiple country-code top-level domain name registry operators. The Internet Corporation for Assigned Names and Numbers (ICANN) has an active program to delegate a large number of new generic top-level domains. EPP will be used to provision those domains, and new registry operators are expected to develop additional protocol extensions. With no way to coordinate the development of these extensions, the problem of non-standard extension duplication by multiple operators is only expected to become worse. The goal of the EPP Extensions (eppext) working group is to create an IANA registry of EPP extensions and to review specifications of extensions for inclusion in the registry. It will accomplish this goal in two steps: 1. Develop a specification for a registry of and corresponding registration procedures for EPP extensions. One proposal is documented in https://datatracker.ietf.org/doc/draft-hollenbeck-epp-ext-reg/. 2. Produce a small number of extensions based on existing Internet Draft documents and use the IANA registration process as developed in 1 to register those extensions, as follows: DNSSEC key relay: draft-gieben-epp-keyrelay (http://datatracker.ietf.org/doc/draft-gieben-epp-keyrelay/) Internationalized domain names: draft-obispo-epp-idn (http://datatracker.ietf.org/doc/draft-obispo-epp-idn/) New TLD launch phases: draft-tan-epp-launchphase (http://datatracker.ietf.org/doc/draft-tan-epp-launchphase/) Trademark Clearinghouse: draft-lozano-tmch-smd (https://datatracker.ietf.org/doc/draft-lozano-tmch-smd/) Note: draft-tan-epp-launchphase has a normative dependency on draft-lozano-tmch-smd. Only the development of the registration process and the publication/registration of the four extensions noted above are in scope for the working group. The working group can choose not to publish or register one or more of the extensions noted above, but it is out of scope to work on other extensions. Goals and Milestones: May 2014 - Extensions registry document to IESG Jul 2014 - DNSSEC key relay extension to IESG Jul 2014 - New TLD launch phases extension to IESG Sep 2014 - Internationalized domain names extension to IESG Internet-Drafts: - Internationalized Domain Name Mapping Extension for the Extensible Provisioning Protocol (EPP) [draft-ietf-eppext-idnmap-02] (10 pages) - Relay Extension for the Extensible Provisioning Protocol [draft-ietf-eppext-keyrelay-01] (15 pages) - Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) [draft-ietf-eppext-launchphase-04] (60 pages) - Extension Registry for the Extensible Provisioning Protocol [draft-ietf-eppext-reg-10] (12 pages) - Mark and Signed Mark Objects Mapping [draft-ietf-eppext-tmch-smd-01] (29 pages) Requests for Comments: RFC7451: Extension Registry for the Extensible Provisioning Protocol (12 pages) * Possible Reference RFC3915 * Possible Reference RFC4114 * Normative Reference RFC3979 * Normative Reference BCP26 * Possible Reference RFC5076 * Normative Reference RFC5890 * Informative Reference RFC3735 * Normative Reference RFC5730 * Normative Reference STD69 * Possible Reference RFC5910 * Normative Reference BCP79 * Normative Reference RFC5226 * Normative Reference RFC4879 * Normative Reference DRAFT-BROWN-EPP-FEES * Normative Reference DRAFT-IETF-EPPEXT-LAUNCHPHASE * Normative Reference DRAFT-GOULD-CHANGE-POLL * Normative Reference DRAFT-GOULD-IDN-TABLE * Normative Reference DRAFT-GOULD-ALLOCATION-TOKEN * Informative Reference DRAFT-WILCOX-CIRA-IDN-EPPEXT Hypertext Transfer Protocol (httpbis) ------------------------------------- Charter Last Modified: 2014-06-18 Current Status: Active Chair: Mark Nottingham Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Barry Leiba Tech Advisor: Allison Mankin Mailing Lists: General Discussion: ietf-http-wg@w3.org To Subscribe: ietf-http-wg-request@w3.org Archive: http://lists.w3.org/Archives/Public/ietf-http-wg/ Description of Working Group: This Working Group is charged with maintaining and developing the "core" specifications for HTTP. The Working Group's specification deliverables are: * A document (or set of documents) that is suitable to supersede RFC 2616 as the definition of HTTP/1.1 and move RFC 2817 to Historic status * A document cataloguing the security properties of HTTP/1.1 * A document (or set of documents) that specifies HTTP/2.0, an improved binding of HTTP's semantics to an underlying transport. HTTP/1.1 -------- HTTP/1.1 is one of the most successful and widely-used protocols on the Internet today. However, its specification has several editorial issues. Additionally, after years of implementation and extension, several ambiguities have become evident, impairing interoperability and the ability to easily implement and use HTTP. The working group will refine RFC2616 to: * Incorporate errata and updates (e.g., references, IANA registries, ABNF) * Fix editorial problems which have led to misunderstandings of the specification * Clarify conformance requirements * Remove known ambiguities where they affect interoperability * Clarify existing methods of extensibility * Remove or deprecate those features that are not widely implemented and also unduly affect interoperability * Where necessary, add implementation advice * Document the security properties of HTTP and its associated mechanisms (e.g., Basic and Digest authentication, cookies, TLS) for common applications It will also incorporate the generic authentication framework from RFC 2617, without obsoleting or updating that specification's definition of the Basic and Digest schemes. Finally, it will incorporate relevant portions of RFC 2817 (in particular, the CONNECT method and advice on the use of Upgrade), so that that specification can be moved to Historic status. In doing so, it should consider: * Implementer experience * Demonstrated use of HTTP * Impact on existing implementations and deployments HTTP/2.0 -------- There is emerging implementation experience and interest in a protocol that retains the semantics of HTTP without the legacy of HTTP/1.x message framing and syntax, which have been identified as hampering performance and encouraging misuse of the underlying transport. The Working Group will produce a specification of a new expression of HTTP's current semantics in ordered, bi-directional streams. As with HTTP/1.x, the primary target transport is TCP, but it should be possible to use other transports. Work will begin using draft-mbelshe-httpbis-spdy-00 as a starting point; proposals are to be expressed in terms of changes to that document. Note that consensus is required both for changes to the document and anything that remains in the document. In particular, because something is in the initial document does not imply that there is consensus around the feature or how it is specified. The deliverable of the WG is HTTP/2.0, and there is no consideration of preserving backwards compatibility with the initial starting point. As part of the HTTP/2.0 work, the following issues are explicitly called out for consideration: * A negotiation mechanism that is capable of not only choosing between HTTP/1.x and HTTP/2.x, but also for bindings of HTTP URLs to other transports (for example). * Header compression (which may encompass header encoding or tokenisation) * Server push (which may encompass pull or other techniques) It is expected that HTTP/2.0 will: * Substantially and measurably improve end-user perceived latency in most cases, over HTTP/1.1 using TCP. * Address the "head of line blocking" problem in HTTP. * Not require multiple connections to a server to enable parallelism, thus improving its use of TCP, especially regarding congestion control. * Retain the semantics of HTTP/1.1, leveraging existing documentation (see above), including (but not limited to) HTTP methods, status codes, URIs, and where appropriate, header fields. * Clearly define how HTTP/2.0 interacts with HTTP/1.x, especially in intermediaries (both 2->1 and 1->2). * Clearly identify any new extensibility points and policy for their appropriate use. The resulting specification(s) are expected to meet these goals for common existing deployments of HTTP; in particular, Web browsing (desktop and mobile), non-browsers ("HTTP APIs"), Web serving (at a variety of scales), and intermediation (by proxies, corporate firewalls, "reverse" proxies and Content Delivery Networks). Likewise, current and future semantic extensions to HTTP/1.x (e.g., headers, methods, status codes, cache directives) should be supported in the new protocol. Note that this does not include uses of HTTP where non-specified behaviours are relied upon (e.g., connection state such as timeouts or client affinity, and "interception" proxies); these uses may or may not be enabled by the final product. Explicitly out-of-scope items include: * Specifying the use of alternate transport-layer protocols. Note that it is expected that the Working Group will work with the TLS working group to define how the protocol is used with the TLS Protocol; any revisions to RFC 2818 will be done in the TLS working group. * Specifying how the HTTP protocol is to be used or presented in a specific use case (e.g., in Web browsers). The Working Group will coordinate this item with: * The TLS Working Group, regarding use of TLS. * The Transport Area, regarding impact on and interaction with transport protocols. * The HYBI Working Group, regarding the possible future extension of HTTP/2.0 to carry WebSockets semantics. The Working Group will give priority to HTTP/1.1 work until that work is complete. Other HTTP-Related Work ----------------------- The Working Group may define additional extensions to HTTP as work items, provided that: * The Working Group Chairs judge that there is consensus to take on the item and believe that it will not interfere with the work described above, and * The Area Directors approve the addition and add corresponding milestones. Additionally, the Working Group will not start work on any extensions that are specific to HTTP/2.0 until the HTTP/2.0 work is completed. Goals and Milestones: Done - First HTTP/1.1 Revision Internet Draft Done - First HTTP Security Properties Internet Draft Done - Call for Proposals for HTTP/2.0 Done - Working Group Last Call for HTTP/1.1 Revision Done - First WG draft of HTTP/2.0, based upon draft-mbelshe-httpbis-spdy-00 Held / eliminated - Working Group Last Call for HTTP Security Properties Done - Submit HTTP/1.1 Revision to IESG for consideration as a Proposed Standard Jun 2014 - Working Group Last call for HTTP/2.0 Nov 2014 - Submit HTTP/2.0 to IESG for consideration as a Proposed Standard Internet-Drafts: - HTTP Alternative Services [draft-ietf-httpbis-alt-svc-06] (18 pages) - The Hypertext Transfer Protocol (HTTP) Authentication-Info and Proxy-Authentication-Info Response Header Fields [draft-ietf-httpbis-auth-info-04] (7 pages) - Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme Registrations [draft-ietf-httpbis-authscheme-registrations-10] (3 pages) - Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) [draft-ietf-httpbis-content-disp-09] (14 pages) - HPACK - Header Compression for HTTP/2 [draft-ietf-httpbis-header-compression-12] (58 pages) - Hypertext Transfer Protocol version 2 [draft-ietf-httpbis-http2-17] (92 pages) - Opportunistic Security for HTTP [draft-ietf-httpbis-http2-encryption-01] (9 pages) - Initial Hypertext Transfer Protocol (HTTP) Method Registrations [draft-ietf-httpbis-method-registrations-15] (5 pages) - Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing [draft-ietf-httpbis-p1-messaging-26] (89 pages) - Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content [draft-ietf-httpbis-p2-semantics-26] (101 pages) - HTTP/1.1, part 3: Message Payload and Content Negotiation [draft-ietf-httpbis-p3-payload-20] (3 pages) - Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests [draft-ietf-httpbis-p4-conditional-26] (28 pages) - Hypertext Transfer Protocol (HTTP/1.1): Range Requests [draft-ietf-httpbis-p5-range-26] (25 pages) - Hypertext Transfer Protocol (HTTP/1.1): Caching [draft-ietf-httpbis-p6-cache-26] (43 pages) - Hypertext Transfer Protocol (HTTP/1.1): Authentication [draft-ietf-httpbis-p7-auth-26] (19 pages) - The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect) [draft-ietf-httpbis-rfc7238bis-03] (7 pages) - Security Requirements for HTTP [draft-ietf-httpbis-security-properties-05] (14 pages) - The Tunnel-Protocol HTTP Request Header Field [draft-ietf-httpbis-tunnel-protocol-01] (6 pages) Requests for Comments: RFC6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) (14 pages) * Replaces DRAFT-RESCHKE-RFC2183-IN-HTTP * Updates RFC2616 * Informative Reference RFC2046 * Informative Reference RFC2047 * Informative Reference RFC2231 * Informative Reference RFC2183 * Informative Reference RFC2616 * Informative Reference STD66 * Informative Reference RFC5987 * Possible Reference RFC5741 * Informative Reference RFC2388 * Informative Reference RFC3986 * Normative Reference BCP14 * Informative Reference BCP90 * Normative Reference RFC2119 * Informative Reference RFC3864 * Informative Reference DRAFT-HOFFMAN-XML2RFC * Informative Reference RFC7231 * Informative Reference DRAFT-RESCHKE-RFC5987BIS * Informative Reference DRAFT-RESCHKE-XML2RFC * Normative Reference DRAFT-DABOO-CALDAV-ATTACHMENTS * Informative Reference DRAFT-BRYAN-METALINK-CLIENT * Informative Reference DRAFT-RESCHKE-HTTP-JFV * Informative Reference DRAFT-IAB-XML2RFCV2 RFC7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing (89 pages) * Normative Reference BCP14 * Updates RFC2818 * Updates RFC2817 * Obsoletes RFC2616 * Obsoletes RFC2145 * Informative Reference RFC2817 * Informative Reference RFC3986 * Informative Reference RFC5246 * Informative Reference RFC2818 * Informative Reference RFC5322 * Informative Reference RFC1808 * Normative Reference STD66 * Normative Reference RFC793 * Normative Reference STD68 * Informative Reference BCP26 * Normative Reference RFC2119 * Informative Reference RFC1945 * Normative Reference RFC7235 * Informative Reference RFC4033 * Informative Reference RFC6585 * Normative Reference RFC5234 * Informative Reference RFC6265 * Informative Reference RFC6838 * Informative Reference BCP90 * Possible Reference RFC5741 * Informative Reference RFC3040 * Informative Reference RFC1919 * Normative Reference RFC7231 * Normative Reference RFC7233 * Normative Reference RFC7232 * Normative Reference RFC7234 * Informative Reference RFC3864 * Normative Reference RFC1952 * Informative Reference RFC2145 * Normative Reference RFC1950 * Normative Reference RFC1951 * Informative Reference BCP13 * Informative Reference RFC2068 * Informative Reference RFC2616 * Informative Reference RFC4559 * Informative Reference RFC2045 * Informative Reference RFC5226 * Informative Reference RFC2047 * Normative Reference DRAFT-IETF-HTTPAUTH-EXTENSION * Possible Reference RFC7486 * Normative Reference DRAFT-IETF-HTTPAUTH-MUTUAL * Informative Reference DRAFT-IETF-CORE-RESOURCE-DIRECTORY * Normative Reference DRAFT-IETF-CORE-HTTP-MAPPING * Informative Reference DRAFT-CAVAGE-HTTP-SIGNATURES * Normative Reference DRAFT-NOTTINGHAM-GIN * Normative Reference RFC7240 * Informative Reference RFC7231 * Informative Reference RFC7233 * Informative Reference RFC7234 * Informative Reference RFC7235 * Normative Reference DRAFT-PANTOS-HTTP-LIVE-STREAMING * Informative Reference DRAFT-BORMANN-COAP-MISC * Informative Reference DRAFT-IETF-CORE-OBSERVE * Informative Reference DRAFT-IETF-DRINKS-SPP-FRAMEWORK * Normative Reference DRAFT-IETF-WEBSEC-KEY-PINNING * Normative Reference RFC7238 * Reference DRAFT-KARCZ-UUAS * Normative Reference RFC7239 * Normative Reference DRAFT-GRIGORIK-HTTP-CLIENT-HINTS * Informative Reference DRAFT-IETF-TSVWG-PORT-USE * Normative Reference DRAFT-IETF-WEIRDS-RDAP-QUERY * Informative Reference DRAFT-IETF-WEIRDS-USING-HTTP * Informative Reference DRAFT-IETF-CDNI-METADATA * Normative Reference DRAFT-IETF-HTTPBIS-HTTP2 * Normative Reference DRAFT-IETF-CDNI-LOGGING * Normative Reference DRAFT-BAGNULO-LMAP-HTTP * Normative Reference DRAFT-THOMSON-HTTP-NICE * Normative Reference DRAFT-IETF-XMPP-POSH * Informative Reference RFC7355 * Normative Reference DRAFT-IETF-HTTPBIS-ALT-SVC * Normative Reference DRAFT-IETF-NETCONF-RESTCONF * Normative Reference DRAFT-IETF-LWIG-COAP * Normative Reference DRAFT-RESCHKE-HTTP-CICE * Normative Reference DRAFT-THOMSON-WEBPUSH-HTTP2 * Informative Reference DRAFT-GERDES-ACE-ACTORS * Normative Reference DRAFT-POEHN-DAME * Normative Reference DRAFT-NOTTINGHAM-HTTP-OVER-VERSION * Informative Reference DRAFT-KERWIN-HTTP2-ENCODED-DATA * Normative Reference DRAFT-HUTTON-HTTPBIS-CONNECT-PROTOCOL * Normative Reference DRAFT-RESCHKE-HTTP-JFV * Normative Reference DRAFT-JOHNDOE-HTTP2-LARGE-HEADER-BLOCKS * Informative Reference DRAFT-NAKAJIMA-HTTPBIS-HTTP2-INTEROP-SURVEY * Informative Reference DRAFT-KRISHNAN-NFVRG-OPEN-NFV-VIRALITY * Informative Reference DRAFT-IETF-SCIM-CORE-SCHEMA * Normative Reference DRAFT-IETF-SCIM-API * Normative Reference DRAFT-IETF-HTTPBIS-TUNNEL-PROTOCOL * Normative Reference DRAFT-IETF-HTTPBIS-RFC7238BIS * Normative Reference DRAFT-IETF-HTTPAUTH-DIGEST * Normative Reference RFC7390 * Normative Reference DRAFT-IETF-TZDIST-SERVICE * Informative Reference DRAFT-SPORNY-HTTP-PROOFS * Normative Reference DRAFT-NOTTINGHAM-WEB-PROXY-DESC * Normative Reference DRAFT-IETF-APPSAWG-HTTP-PROBLEM * Normative Reference DRAFT-DICKINSON-DNSOP-5966-BIS * Informative Reference DRAFT-DORIA-HRPC-PROPOSAL * Informative Reference DRAFT-IETF-CORE-BLOCK * Informative Reference DRAFT-NOTTINGHAM-STAKEHOLDER-RIGHTS * Informative Reference RFC7472 * Normative Reference DRAFT-NEWTON-LINK-RR * Normative Reference DRAFT-CEM-DANE-ASSERTION * Normative Reference DRAFT-IETF-DNSOP-5966BIS * Normative Reference DRAFT-IETF-NETCONF-CALL-HOME * Normative Reference DRAFT-IETF-CDNI-REDIRECTION * Informative Reference DRAFT-IETF-V6OPS-SIIT-DC * Normative Reference DRAFT-RESCHKE-HTTPAUTH-AUTH-INFO * Normative Reference DRAFT-IETF-NETCONF-RESTCONF-COLLECTION * Normative Reference DRAFT-IETF-HTTPBIS-AUTH-INFO * Normative Reference DRAFT-IETF-HTTPBIS-HEADER-COMPRESSION * Informative Reference DRAFT-CAMPBELL-OAUTH-DST4JWT * Normative Reference DRAFT-NOTTINGHAM-HTTP-ENCRYPTION-ENCODING * Normative Reference DRAFT-DAMAGGIO-WEBPUSH-HTTP2 * Informative Reference DRAFT-APPELBAUM-DNSOP-ONION-TLD * Informative Reference DRAFT-THOMSON-POSTEL-WAS-WRONG * Informative Reference DRAFT-DECCIO-DOMAIN-NAME-RELATIONSHIPS * Informative Reference DRAFT-THOMSON-WEBPUSH-ENCRYPTION RFC7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content (101 pages) * Updates RFC2817 * Obsoletes RFC2616 * Informative Reference RFC2817 * Normative Reference RFC3986 * Informative Reference RFC2388 * Informative Reference RFC850 * Informative Reference RFC5246 * Informative Reference RFC5322 * Normative Reference STD66 * Informative Reference RFC5988 * Informative Reference RFC5905 * Normative Reference BCP47 * Informative Reference RFC2978 * Normative Reference STD68 * Informative Reference BCP26 * Informative Reference RFC5789 * Normative Reference RFC6365 * Informative Reference RFC5646 * Normative Reference RFC7235 * Informative Reference RFC2295 * Informative Reference RFC6266 * Informative Reference RFC2557 * Informative Reference BCP178 * Informative Reference RFC2049 * Informative Reference RFC5234 * Informative Reference RFC6265 * Informative Reference RFC6838 * Informative Reference BCP90 * Possible Reference RFC5741 * Normative Reference RFC2119 * Informative Reference RFC7238 * Informative Reference RFC7230 * Informative Reference RFC7233 * Normative Reference RFC7232 * Normative Reference RFC7234 * Informative Reference RFC5987 * Informative Reference BCP19 * Normative Reference BCP14 * Informative Reference BCP13 * Informative Reference RFC2068 * Informative Reference RFC2616 * Informative Reference RFC2774 * Informative Reference RFC1945 * Informative Reference RFC2045 * Normative Reference BCP166 * Informative Reference RFC4647 * Informative Reference RFC2046 * Informative Reference RFC5226 * Normative Reference RFC7486 * Normative Reference DRAFT-IETF-CORE-HTTP-MAPPING * Normative Reference RFC7240 * Normative Reference RFC7230 * Informative Reference RFC7233 * Informative Reference RFC7234 * Normative Reference RFC7235 * Normative Reference RFC7237 * Normative Reference RFC7472 * Normative Reference RFC7238 * Reference DRAFT-KARCZ-UUAS * Normative Reference DRAFT-GRIGORIK-HTTP-CLIENT-HINTS * Normative Reference DRAFT-IETF-WEIRDS-RDAP-QUERY * Normative Reference DRAFT-IETF-WEIRDS-RDAP-SEC * Normative Reference DRAFT-IETF-WEIRDS-USING-HTTP * Normative Reference DRAFT-MURCHISON-WEBDAV-PREFER * Normative Reference DRAFT-SNELL-LINK-METHOD * Normative Reference DRAFT-IETF-PAWS-PROTOCOL * Normative Reference DRAFT-IETF-HTTPBIS-HTTP2 * Informative Reference DRAFT-DEJONG-REMOTESTORAGE * Normative Reference DRAFT-IETF-CDNI-LOGGING * Normative Reference DRAFT-BAGNULO-LMAP-HTTP * Informative Reference DRAFT-WILDE-ACCEPT-POST * Informative Reference RFC7302 * Normative Reference DRAFT-IETF-OAUTH-DYN-REG-MANAGEMENT * Normative Reference DRAFT-IETF-NETCONF-RESTCONF * Normative Reference DRAFT-RESCHKE-HTTP-CICE * Normative Reference DRAFT-THOMSON-WEBPUSH-HTTP2 * Informative Reference DRAFT-SEITZ-ACE-PROBLEM-DESCRIPTION * Normative Reference DRAFT-NOTTINGHAM-HTTP-OVER-VERSION * Normative Reference DRAFT-HUTTON-HTTPBIS-CONNECT-PROTOCOL * Informative Reference DRAFT-PRUDHOMMEAUX-HTTP-STATUS-2NN * Normative Reference DRAFT-RESCHKE-HTTP-JFV * Normative Reference DRAFT-IETF-SCIM-CORE-SCHEMA * Normative Reference DRAFT-IETF-SCIM-API * Normative Reference DRAFT-IETF-HTTPBIS-TUNNEL-PROTOCOL * Normative Reference DRAFT-IETF-HTTPBIS-RFC7238BIS * Normative Reference DRAFT-IETF-HTTPAUTH-DIGEST * Normative Reference DRAFT-IETF-TZDIST-SERVICE * Normative Reference DRAFT-IETF-OAUTH-INTROSPECTION * Informative Reference DRAFT-NOTTINGHAM-WEB-PROXY-DESC * Normative Reference DRAFT-IETF-CDNI-CONTROL-TRIGGERS * Normative Reference DRAFT-IETF-APPSAWG-HTTP-PROBLEM * Informative Reference DRAFT-DORIA-HRPC-PROPOSAL * Informative Reference DRAFT-IETF-HTTPAUTH-BASICAUTH-UPDATE * Informative Reference DRAFT-SELANDER-ACE-OBJECT-SECURITY * Normative Reference DRAFT-ABIGGS-SAAG-KEY-MANAGEMENT-SERVICE * Informative Reference DRAFT-IETF-APPSAWG-FILE-SCHEME * Normative Reference DRAFT-IETF-NETCONF-RESTCONF-COLLECTION * Normative Reference DRAFT-NOTTINGHAM-HTTP-ENCRYPTION-ENCODING * Informative Reference DRAFT-DECCIO-DOMAIN-NAME-RELATIONSHIPS RFC7232: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests (28 pages) * Obsoletes RFC2616 * Informative Reference RFC4918 * Normative Reference RFC2119 * Informative Reference BCP90 * Normative Reference BCP14 * Normative Reference STD68 * Normative Reference DRAFT-IETF-HTTPBIS-P6-CACHE * Informative Reference RFC2616 * Normative Reference DRAFT-IETF-HTTPBIS-P5-RANGE * Normative Reference DRAFT-IETF-HTTPBIS-P1-MESSAGING * Normative Reference DRAFT-IETF-HTTPBIS-P2-SEMANTICS * Informative Reference RFC5234 * Possible Reference DRAFT-IETF-CORE-HTTP-MAPPING * Normative Reference RFC7230 * Normative Reference RFC7231 * Informative Reference RFC7233 * Normative Reference RFC7234 * Informative Reference DRAFT-BORMANN-COAP-MISC * Normative Reference RFC7239 * Normative Reference DRAFT-MURCHISON-WEBDAV-PREFER * Normative Reference DRAFT-SNELL-LINK-METHOD * Normative Reference DRAFT-IETF-HTTPBIS-HTTP2 * Informative Reference DRAFT-DEJONG-REMOTESTORAGE * Normative Reference DRAFT-BAGNULO-LMAP-HTTP * Normative Reference DRAFT-IETF-NETCONF-RESTCONF * Normative Reference DRAFT-IETF-NETCONF-RESTCONF-COLLECTION * Normative Reference DRAFT-THOMSON-WEBPUSH-HTTP2 * Informative Reference DRAFT-KRISHNAN-NFVRG-OPEN-NFV-VIRALITY * Normative Reference DRAFT-IETF-TZDIST-SERVICE * Normative Reference DRAFT-IETF-CDNI-CONTROL-TRIGGERS * Normative Reference DRAFT-IETF-CDNI-LOGGING * Informative Reference DRAFT-DORIA-HRPC-PROPOSAL * Normative Reference DRAFT-DAMAGGIO-WEBPUSH-HTTP2 * Possible Reference DRAFT-NISHIDA-TCPM-MAXWIN RFC7233: Hypertext Transfer Protocol (HTTP/1.1): Range Requests (25 pages) * Informative Reference BCP26 * Obsoletes RFC2616 * Normative Reference RFC2119 * Informative Reference RFC6838 * Informative Reference RFC2046 * Normative Reference BCP14 * Informative Reference BCP90 * Informative Reference BCP13 * Possible Reference RFC5741 * Informative Reference RFC2616 * Normative Reference STD68 * Informative Reference RFC7231 * Informative Reference RFC7230 * Informative Reference RFC7232 * Normative Reference RFC7234 * Informative Reference RFC5226 * Informative Reference RFC5234 * Normative Reference RFC7230 * Informative Reference RFC7231 * Normative Reference RFC7234 * Normative Reference DRAFT-IETF-HTTPBIS-HTTP2 * Informative Reference DRAFT-DEJONG-REMOTESTORAGE * Normative Reference DRAFT-IETF-CDNI-LOGGING * Normative Reference DRAFT-IETF-SCIM-API * Normative Reference DRAFT-BAGNULO-LMAP-HTTP * Informative Reference DRAFT-DORIA-HRPC-PROPOSAL * Informative Reference DRAFT-IETF-CORE-BLOCK RFC7234: Hypertext Transfer Protocol (HTTP/1.1): Caching (43 pages) * Obsoletes RFC2616 * Informative Reference RFC2047 * Informative Reference RFC6265 * Normative Reference RFC2119 * Informative Reference BCP26 * Informative Reference BCP90 * Normative Reference BCP14 * Normative Reference RFC7235 * Possible Reference RFC5741 * Informative Reference RFC2616 * Informative Reference RFC5861 * Informative Reference RFC5905 * Normative Reference STD68 * Informative Reference RFC7231 * Informative Reference RFC7230 * Normative Reference RFC7233 * Normative Reference RFC7232 * Informative Reference RFC5226 * Informative Reference RFC5234 * Normative Reference RFC7230 * Normative Reference RFC7231 * Normative Reference RFC7233 * Normative Reference RFC7235 * Informative Reference DRAFT-BORMANN-COAP-MISC * Informative Reference DRAFT-CASTELLANI-CORE-ADVANCED-HTTP-MAPPING * Normative Reference DRAFT-IETF-WEBSEC-KEY-PINNING * Normative Reference RFC7238 * Normative Reference DRAFT-SNELL-LINK-METHOD * Normative Reference DRAFT-IETF-HTTPBIS-HTTP2 * Normative Reference DRAFT-BAGNULO-LMAP-HTTP * Informative Reference DRAFT-IETF-WEIRDS-BOOTSTRAP * Normative Reference DRAFT-IETF-HTTPBIS-ALT-SVC * Normative Reference DRAFT-THOMSON-WEBPUSH-HTTP2 * Normative Reference DRAFT-IETF-HTTPBIS-HTTP2-ENCRYPTION * Informative Reference DRAFT-NOTTINGHAM-SAFE-HINT * Normative Reference DRAFT-IETF-HTTPBIS-RFC7238BIS * Normative Reference DRAFT-IETF-TZDIST-SERVICE * Normative Reference DRAFT-NOTTINGHAM-WEB-PROXY-DESC * Normative Reference DRAFT-IETF-CDNI-LOGGING * Informative Reference DRAFT-DORIA-HRPC-PROPOSAL * Normative Reference DRAFT-CEM-DANE-ASSERTION * Normative Reference DRAFT-IETF-HTTPAUTH-DIGEST * Normative Reference DRAFT-DAMAGGIO-WEBPUSH-HTTP2 RFC7235: Hypertext Transfer Protocol (HTTP/1.1): Authentication (19 pages) * Informative Reference BCP26 * Normative Reference RFC2119 * Updates RFC2617 * Obsoletes RFC2616 * Informative Reference RFC5246 * Informative Reference BCP90 * Informative Reference RFC3986 * Normative Reference BCP14 * Possible Reference RFC5741 * Informative Reference STD66 * Informative Reference RFC2616 * Informative Reference RFC2617 * Informative Reference RFC4648 * Normative Reference STD68 * Informative Reference RFC7230 * Normative Reference RFC7231 * Normative Reference RFC7234 * Informative Reference RFC5226 * Informative Reference RFC5234 * Normative Reference DRAFT-IETF-HTTPAUTH-SCRAM-AUTH * Informative Reference DRAFT-IETF-HTTPAUTH-EXTENSION * Normative Reference RFC7486 * Normative Reference DRAFT-IETF-HTTPAUTH-MUTUAL * Normative Reference DRAFT-IETF-CORE-HTTP-MAPPING * Informative Reference DRAFT-CAVAGE-HTTP-SIGNATURES * Normative Reference RFC7230 * Normative Reference RFC7231 * Normative Reference RFC7234 * Normative Reference RFC7236 * Informative Reference DRAFT-MCDONALD-LDAP-PRINTER-SCHEMA * Informative Reference DRAFT-IETF-HTTPAUTH-BASICAUTH-UPDATE * Normative Reference DRAFT-MELNIKOV-HTTPBIS-SCRAM-AUTH * Normative Reference DRAFT-IETF-WEIRDS-RDAP-SEC * Normative Reference DRAFT-IETF-HTTPBIS-HTTP2 * Normative Reference DRAFT-IETF-CDNI-LOGGING * Normative Reference DRAFT-IETF-NETCONF-RESTCONF * Informative Reference DRAFT-RESCHKE-HTTP-JFV * Normative Reference DRAFT-IETF-SCIM-API * Normative Reference DRAFT-IETF-HTTPAUTH-DIGEST * Normative Reference DRAFT-IETF-TZDIST-SERVICE * Informative Reference DRAFT-SPORNY-HTTP-PROOFS * Normative Reference DRAFT-BAGNULO-LMAP-HTTP * Informative Reference DRAFT-DORIA-HRPC-PROPOSAL * Normative Reference DRAFT-RESCHKE-HTTPAUTH-AUTH-INFO * Informative Reference DRAFT-IETF-HTTPBIS-AUTH-INFO * Informative Reference DRAFT-NOTTINGHAM-HTTP-ENCRYPTION-ENCODING RFC7236: Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme Registrations (3 pages) * Normative Reference RFC7235 * Normative Reference RFC4559 * Normative Reference RFC5849 * Possible Reference RFC5741 * Normative Reference RFC2617 * Normative Reference RFC6750 * Informative Reference DRAFT-DORIA-HRPC-PROPOSAL RFC7237: Initial Hypertext Transfer Protocol (HTTP) Method Registrations (5 pages) * Normative Reference RFC3744 * Normative Reference RFC5789 * Normative Reference RFC3648 * Normative Reference RFC5842 * Normative Reference RFC2068 * Possible Reference RFC5741 * Normative Reference RFC4918 * Normative Reference RFC4791 * Normative Reference RFC4437 * Normative Reference RFC7231 * Normative Reference RFC3253 * Normative Reference RFC5323 * Informative Reference DRAFT-DORIA-HRPC-PROPOSAL JavaScript Object Notation (json) --------------------------------- Charter Last Modified: 2013-05-31 Current Status: Active Chairs: Matthew Miller Paul E. Hoffman Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Pete Resnick Mailing Lists: General Discussion: json@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/json Archive: http://www.ietf.org/mail-archive/web/json/ Description of Working Group: Javascript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard, and is published in RFC 7159. The WG will work on an restricted profile of JSON designed to maximize interoperability. The work will start from draft-bray-i-json-01. The WG will work on a format for a streamable sequence of JSON texts. The work will start from draft-williams-json-text-sequence-00. Goals and Milestones: Jun 2014 - IETF Last Call for restricted profile Jun 2014 - IETF Last Call for text sequences Internet-Drafts: - The I-JSON Message Format [draft-ietf-json-i-json-06] (6 pages) - The JavaScript Object Notation (JSON) Data Interchange Format [draft-ietf-json-rfc4627bis-10] (16 pages) - JavaScript Object Notation (JSON) Text Sequences [draft-ietf-json-text-sequence-13] (8 pages) Requests for Comments: RFC7158: The JavaScript Object Notation (JSON) Data Interchange Format (16 pages) * Obsoletes RFC4627 * Informative Reference RFC4627 * Possible Reference RFC5741 * Normative Reference RFC2119 * Normative Reference BCP14 * Informative Reference RFC3607 * Informative Reference RFC607 * Normative Reference RFC5234 * Normative Reference STD68 * Obsoletes RFC7159 * Normative Reference DRAFT-IETF-NETCONF-YANG-PATCH * Normative Reference DRAFT-IETF-NETCONF-RESTCONF RFC7159: The JavaScript Object Notation (JSON) Data Interchange Format (16 pages) * Normative Reference RFC5234 * Informative Reference RFC3607 * Informative Reference RFC607 * Normative Reference STD68 * Normative Reference RFC2119 * Normative Reference BCP14 * Informative Reference RFC4627 * Possible Reference RFC5741 * Obsoletes RFC7158 * Obsoletes RFC4627 * Normative Reference DRAFT-VANDERSTOK-CORE-COMI * Normative Reference DRAFT-GREEVENBOSCH-APPSAWG-CBOR-CDDL * Normative Reference DRAFT-BUTLER-GEOJSON * Normative Reference DRAFT-IETF-CDNI-REDIRECTION * Informative Reference DRAFT-BORMANN-CORE-ACE-AIF * Normative Reference DRAFT-JONES-JOSE-JWK-THUMBPRINT * Normative Reference RFC7386 * Normative Reference DRAFT-PANTOS-HTTP-LIVE-STREAMING * Normative Reference DRAFT-IETF-KITTEN-SASL-OAUTH * Informative Reference DRAFT-IETF-JOSE-JSON-WEB-SIGNATURE * Informative Reference DRAFT-IETF-JOSE-JSON-WEB-KEY * Normative Reference DRAFT-HARDJONO-OAUTH-UMACORE * Informative Reference DRAFT-IETF-JOSE-JSON-WEB-ENCRYPTION * Normative Reference RFC7390 * Informative Reference DRAFT-IETF-JOSE-JSON-WEB-ALGORITHMS * Informative Reference DRAFT-IETF-WEIRDS-JSON-RESPONSE * Normative Reference DRAFT-IETF-CDNI-CONTROL-TRIGGERS * Informative Reference DRAFT-IETF-OAUTH-JWT-BEARER * Informative Reference DRAFT-IETF-OAUTH-JSON-WEB-TOKEN * Normative Reference DRAFT-IETF-SCIM-API * Normative Reference DRAFT-IETF-SCIM-CORE-SCHEMA * Informative Reference DRAFT-IETF-WEIRDS-USING-HTTP * Normative Reference DRAFT-IETF-PAWS-PROTOCOL * Normative Reference DRAFT-HARDJONO-OAUTH-RESOURCE-REG * Possible Reference DRAFT-IETF-PPSP-BASE-TRACKER-PROTOCOL * Reference DRAFT-SHI-ALTO-YANG-MODEL * Reference DRAFT-ROOME-ALTO-PID-PROPERTIES * Normative Reference DRAFT-IETF-WEIRDS-BOOTSTRAP * Informative Reference RFC7373 * Normative Reference DRAFT-IETF-XMPP-POSH * Normative Reference DRAFT-IETF-OAUTH-DYN-REG-MANAGEMENT * Normative Reference DRAFT-WILLIAMS-JSON-TEXT-SEQUENCE * Normative Reference DRAFT-IETF-NETMOD-YANG-JSON * Normative Reference RFC7464 * Normative Reference DRAFT-IETF-JSON-I-JSON * Normative Reference DRAFT-HALLAMBAKER-JSONL * Normative Reference DRAFT-RESCHKE-HTTP-JFV * Informative Reference DRAFT-RODRIGUEZNATAL-LISP-OAM * Normative Reference DRAFT-LIU-LMAP-REST * Informative Reference DRAFT-IETF-TRAM-TURN-THIRD-PARTY-AUTHZ * Possible Reference DRAFT-LI-CORE-LINKS-CBOR * Normative Reference DRAFT-HOFFMAN-DNS-IN-JSON * Normative Reference DRAFT-IETF-OAUTH-INTROSPECTION * Normative Reference DRAFT-LABER-SMTP-IMPT * Normative Reference DRAFT-BAGNULO-LMAP-HTTP * Normative Reference DRAFT-LHOTKA-NETMOD-YANG-METADATA * Normative Reference DRAFT-IETF-APPSAWG-HTTP-PROBLEM * Normative Reference DRAFT-NOTTINGHAM-WEB-PROXY-DESC * Reference DRAFT-SHI-MODEL-JSON-MSG-YANG * Reference DRAFT-SHI-ALTO-YANG-JSON * Reference DRAFT-ROOME-ALTO-INCR-UPDATE-SSE * Informative Reference DRAFT-BORMANN-JOSE-COSE * Normative Reference DRAFT-LINUS-TRANS-GOSSIP-CT * Normative Reference DRAFT-LINUS-TRANS-GOSSIP * Normative Reference DRAFT-IETF-JOSE-JWK-THUMBPRINT * Informative Reference DRAFT-IETF-BESS-VIRTUAL-PE * Normative Reference DRAFT-ABIGGS-SAAG-KEY-MANAGEMENT-SERVICE * Normative Reference DRAFT-BARNES-ACME * Informative Reference DRAFT-SCHAAD-COSE * Normative Reference DRAFT-IETF-OAUTH-DYN-REG * Normative Reference DRAFT-JONES-JOSE-KEY-MANAGED-JSON-WEB-SIGNATURE * Normative Reference DRAFT-DAMAGGIO-WEBPUSH-HTTP2 * Normative Reference DRAFT-LI-CORE-CBOR-EQUIVALENTS * Normative Reference DRAFT-IETF-TZDIST-SERVICE * Normative Reference DRAFT-OSKARSSON-JSOND RFC7464: JavaScript Object Notation (JSON) Text Sequences (8 pages) * Normative Reference RFC2119 * Normative Reference BCP14 * Normative Reference RFC20 * Normative Reference RFC7159 * Normative Reference STD63 * Normative Reference STD68 * Normative Reference RFC3629 * Normative Reference RFC5234 Preparation and Comparison of Internationalized Strings (precis) ---------------------------------------------------------------- Charter Last Modified: 2011-12-09 Current Status: Active Chairs: Marc Blanchet Yoshiro Yoneya Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Pete Resnick Mailing Lists: General Discussion: precis@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/precis Archive: http://www.ietf.org/mail-archive/web/precis/ Description of Working Group: Problem Statement The use of non-ASCII strings in Internet protocols requires additional processing to be handled properly. As part of the Internationalized Domain Names (idn) work in 2003, a method for preparation and comparison of internationalized strings was defined and generalized to be re-used by other protocols. This "stringprep" method [RFC 3454] defines the overall framework whereas specific protocols define their own profiles. Known existing IETF profiles are: - The Nameprep profile [RFC 3490] for use in Internationalized Domain Names in Applications (IDNA) - The iSCSI profile [RFC 3722] for use in Internet Small Computer Systems Interface (iSCSI) Names - The Nodeprep and Resourceprep profiles [RFC 3920] for use in the Extensible Messaging and Presence Protocol (XMPP) - The Policy MIB profile [RFC 4011] for use in the Simple Network Management Protocol (SNMP) - The SASLprep profile [RFC 4013] for use in the Simple Authentication and Security Layer (SASL) - The trace profile [RFC 4505] for use with the SASL ANONYMOUS mechanism - The LDAP profile (RFC 4518] for use with LDAP The IAB completed a review of IDN and made recommendations for change [RFC 4690], which triggered a new version of the IDNA protocol called IDNA2008. Whereas IDNA2003 was tied to Unicode 3.2 via stringprep, IDNA2008 does not use the stringprep method, but instead uses an algorithm based on the properties of Unicode characters, which makes it agile to the Unicode database version. The protocols using stringprep need Unicode version agility and therefore need to investigate whether and how to move away from the current stringprep approach, with the associated challenges of backward compatibility and migration. Objectives The goal of this group is to assess whether a new method based on the new IDNA2008 algorithmic approach is the appropriate path forward for existing stringprep protocols as well as for other application protocols requiring internationalized strings. The group will evaluate if a new generalized framework based on the algorithmic approach is appropriate and, if so, define it. The group will analyze existing stringprep profiles and will do one of the following with regard to each profile: 1. Develop a replacement for the profile in close collaboration with the related protocol working group (if any). 2. Collaborate with another active working group which will be developing the new profile as part of its charter. 3. Advise the authors of profiles for which there is no active working group how to proceed. The group will also define a set of best current practices for preparation and comparison of internationalized strings. Because the framework, profile replacements, and guidelines are very much interrelated, work on them will proceed in parallel as much as possible. Based on normal working group processes for achieving consensus, the group will attempt to gather input from, and may provide advice to, "customers" working on IETF technologies other than those listed above, including but not limited to Network Address Identifiers (RFC 4282) and Kerberos (RFC 4120). However, the group will prioritize work on the listed stringprep profiles higher than work on other technologies, and will formally accept additional tasks as official milestones only after rechartering. In completing its tasks, the working group should collaborate with other teams involved in internationalized identifiers, such as the IETF's IRI and EAI working groups as well as other relevant standards development organizations (e.g., the Unicode Consortium). Deliverables 1. Problem statement / analysis of existing stringprep profiles (Informational). 2. Possible new framework to replace stringprep (Standards Track). 3. Possible replacements for the existing IETF stringprep profiles as listed earlier in this charter (Standards Track). 4. String preparation and comparison guidelines (BCP). Goals and Milestones: Done - Accept problem statement document as a WG item Done - Accept framework document as a WG item Done - Accept new profile documents as WG items Done - Start Working Group Last Call on problem statement document Done - Submit problem statement document to the IESG Done - Start Working Group Last Call on framework document Done - Start Working Group Last Call on new profile documents Dec 2013 - Submit new profile documents to the IESG Jan 2014 - Submit framework document to the IESG Apr 2014 - Accept guidelines document as a WG item Oct 2014 - Start Working Group Last Call on guidelines document Dec 2014 - Submit guidelines document to the IESG Internet-Drafts: - PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols [draft-ietf-precis-framework-23] (39 pages) - Mapping characters for PRECIS classes [draft-ietf-precis-mappings-08] (11 pages) - Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames [draft-ietf-precis-nickname-16] (10 pages) - Stringprep Revision and Problem Statement for the Preparation and Comparison of Internationalized Strings (PRECIS) [draft-ietf-precis-problem-statement-09] (34 pages) - Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords [draft-ietf-precis-saslprepbis-14] (22 pages) Requests for Comments: RFC6885: Stringprep Revision and Problem Statement for the Preparation and Comparison of Internationalized Strings (PRECIS) (34 pages) * Replaces DRAFT-BLANCHET-PRECIS-PROBLEM-STATEMENT * Informative Reference RFC4505 * Informative Reference RFC5738 * Informative Reference RFC3920 * Informative Reference RFC5661 * Informative Reference BCP166 * Informative Reference RFC4013 * Informative Reference RFC4011 * Informative Reference RFC952 * Informative Reference RFC3720 * Informative Reference RFC5051 * Informative Reference RFC3722 * Informative Reference RFC4511 * Informative Reference BCP14 * Informative Reference RFC5456 * Informative Reference RFC5122 * Possible Reference RFC5741 * Informative Reference RFC3454 * Informative Reference RFC4314 * Informative Reference RFC4954 * Informative Reference RFC5802 * Informative Reference RFC5804 * Informative Reference RFC3492 * Informative Reference RFC4513 * Informative Reference RFC3490 * Informative Reference RFC3491 * Informative Reference RFC3501 * Informative Reference RFC4279 * Informative Reference RFC4690 * Informative Reference RFC4518 * Informative Reference RFC4790 * Informative Reference RFC5890 * Informative Reference RFC5891 * Informative Reference RFC5892 * Informative Reference RFC5893 * Informative Reference RFC5894 * Informative Reference RFC5895 * Informative Reference RFC6365 * Informative Reference RFC4616 * Informative Reference RFC5054 * Informative Reference RFC2119 * Informative Reference RFC3530 * Informative Reference RFC4643 * Informative Reference RFC6120 * Informative Reference RFC3922 * Informative Reference RFC6452 * Informative Reference RFC3748 * Informative Reference RFC4422 * Informative Reference RFC4683 * Informative Reference RFC5280 * Informative Reference RFC3629 * Informative Reference RFC5034 * Informative Reference DRAFT-IETF-PRECIS-FRAMEWORK * Informative Reference RFC6943 * Informative Reference DRAFT-IETF-XMPP-6122BIS * Informative Reference DRAFT-IETF-PRECIS-MAPPINGS * Informative Reference RFC7373 Protocol to Access WS database (paws) ------------------------------------- Charter Last Modified: 2014-02-14 Current Status: Active Chairs: Gabor Bajko Brian Rosen Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Pete Resnick Mailing Lists: General Discussion: paws@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/paws Archive: http://www.ietf.org/mail-archive/web/paws/ Description of Working Group: Background Radio spectrum is a limited resource. National and international bodies assign different frequencies for specific uses, and in most cases license the rights to use these frequencies. Locally unused spectrum is commonly called "white space" and may be made available to other services on a basis of non-interference with the primary user of the frequencies concerned (if any). This technique can help "unlock" existing spectrum, for example to enable the wireless communications industry to provide more services over frequencies associated with unused television channels. An obvious requirement is that white space uses must not interfere with the primary use of the spectrum. This is achieved through spatial and/or temporal separation of the primary user and whitespace user with due consideration made to the radio characteristics of the two uses. Problem Statement The fundamental problem is enabling a radio device to determine, in a specific location and at specific time, if any white space is available for secondary use. There are two parties to such an interaction: 1. A database containing records about the protected contours (in space and time) of primary spectrum users. Typically, such databases will be populated by information provided by the appropriate spectrum regulation bodies and by spectrum licensees. 2. A radio device that wishes to query such a database. Typically, the nature of the query will depend on the needs of the device. The contents of white space databases, and the needs of radio devices, are being defined elsewhere. However, these parties need a protocol for communication that will enable radio devices to find out what white space is available at a given time in a given location. It is expected that white space databases will be reachable via the Internet, and that radio devices too will have some form of Internet connectivity, directly or indirectly. Therefore, it is appropriate to define an Internet-based protocol for querying white space databases and receiving responses from such databases. In rough outline, such a protocol would enable a radio device that knows its location and the current time to complete the following tasks: 1. Determine the relevant white space database to query. 2. Connect to the database using a well-defined communication method. 3. Provide its geolocation and perhaps other data to the database using a well-defined format for querying the database. 4. Receive in return a list of available white space spectrum with their characteristics, using a well-defined format for returning information. 5. Report to the white space database anticipated spectrum usage at a suitable granularity. Once the device learns of the available white space (e.g., in a TV white space implementation, the list of available channels at that location), it can then select one of the bands from the list and begin to transmit and receive on the selected band. If the device's parameters have changed (e.g., if some amount of time has passed or if the device has changed location beyond a specified threshold), it might need to query the database again to determine what white space is still available. Objectives The overall goals of this working group are to: 1. Standardize a mechanism for discovering a white space database. 2. Standardize a method for communicating with a white space database. 3. Standardize the data formats to be carried over the defined database communication method. 4. Ensure that the discovery mechanism, database access method, and query/response formats have appropriate security levels in place. By "standardize" is not meant that the working group will necessarily develop new technologies. In completing its work, the group will: - Evaluate existing discovery mechanisms to determine if one of them provides the necessary application features and security properties (or can be extended to do so) for discovering a white space database. Examples might include DNS. - Evaluate existing application-layer transport protocols to determine if one of them provides the necessary application features and security properties (or can be extended to do so) for use as a building block for communication between location- aware devices and white space databases. If such a method exists, the group will reuse it; if not, the group will develop one. Examples might include HTTP. - Develop a method for querying a white space database. Such a method will utilize, so far as possible, the features of the application-layer transport protocol and not re-implement them in the new protocol. It will include mechanisms to verify that the requests and responses come from authorized sources, and that they have not been modified in transit. Examples might include LDAP. - Define extensible formats for both location-specific queries and location-specific responses for interaction with radio white space databases. The group will consider whether existing data formats can be reused. The protocol must protect both the channel enablement process and the privacy of users. Robust privacy and security mechanisms are needed to prevent: device identity spoofing, modification of device requests, modification of channel enablement information, impersonation of registered database services, and unauthorized disclosure of a device's location. The group will consider whether existing privacy and security mechanisms can be reused. The task of defining the structure and contents of the databases themselves is out of scope. The group will standardize formats for communication between devices and databases, but not the information models for the databases, since those models are likely to be country-specific or application-specific. In addition, the particular data exchanged between a device and a database might depend on the ranges of radio spectrum that are to be used, the requirements of the database operators and their governing regulations, and other factors. Therefore, the database access method and the query/response data formats that are exchanged using that method need to be designed for extensibility rather than being tied to any specific spectrum, country, or phy/mac/air interface. For example, the working group should define extension points for the database access method and the query/response formats, so that use cases other than those currently envisioned can be addressed in the future if a community of interest wishes to do so. However, the access method and query/response formats will incorporate relevant aspects of the parameters needed for the currently envisioned use cases to ensure proper operation. In accordance with existing IETF processes, the group will communicate and invite participation with other relevant standards bodies and groups, and if necessary reuse existing liaison relationships or request the establishment of new liaison relationships, including but not limited to IEEE 802.11af and IEEE 802.22. In order to ensure that it takes into account a broad range of possible use cases and requirements, the group should also reach out to other potential "customers" for a white space database access method and consider input from regulatory entities that are involved in the specification of the rules for secondary use of spectrum in specific radio bands. Deliverables 1. A description of the relevant use cases and requirements. This document shall be Informational. Subject to working group consensus, draft-probasco-paws-overview-usecases and draft-patil-paws-problem-stmt might be used as a starting point. 2. A specification of the mechanism for discovering a white space database, the method for accessing a white space database, and the query/response formats for interacting with a white space database. This document shall be Standards Track. Goals and Milestones: Aug 2012 - Submit 'Use Cases and Requirements for Accessing a Radio White Space Database' to the IESG for publication as Informational Apr 2013 - Submit 'Accessing a Radio White Space Database' to the IESG for publication as Proposed Standard Internet-Drafts: - Protocol to Access White-Space (PAWS) Databases: Use Cases and Requirements [draft-ietf-paws-problem-stmt-usecases-rqmts-15] (23 pages) - Protocol to Access White-Space (PAWS) Databases [draft-ietf-paws-protocol-20] (92 pages) Requests for Comments: RFC6953: Protocol to Access White-Space (PAWS) Databases: Use Cases and Requirements (23 pages) * Normative Reference BCP14 * Possible Reference RFC5741 * Normative Reference RFC2119 * Informative Reference DRAFT-IETF-PAWS-PROTOCOL * Informative Reference DRAFT-WEI-PAWS-DATABASE-DISCOVERY System for Cross-domain Identity Management (scim) -------------------------------------------------- Charter Last Modified: 2012-02-23 Current Status: Active Chairs: Morteza Ansari Leif Johansson Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Barry Leiba Mailing Lists: General Discussion: scim@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/scim Archive: http://www.ietf.org/mail-archive/web/scim/ Description of Working Group: The System for Cross-domain Identity Management (SCIM) working group will standardize methods for creating, reading, searching, modifying, and deleting user identities and identity-related objects across administrative domains, with the goal of simplifying common tasks related to user identity management in services and applications. "Standardize" does not necessarily mean that the working group will develop new technologies. The existing specifications for "SCIM 1.0" provide RESTful interfaces on top of HTTP rather than defining a new application protocol. That will be the basis for the new work. Today, distributed identity management across administrative domains is complicated by a lack of protocol and schema standardization between consumers and producers of identities. This has led to a number of approaches, including error-prone manual administration and bulk file uploads, as well as proprietary protocols and mediation devices that must be adapted to each service for each organization. While there is existing work in the field, it has not been widely adopted for a variety of reasons, including a lack of common artifacts such as schema, toolsets, and libraries. The SCIM working group will develop the core schema and interfaces based on HTTP and REST to address these problems. Initially, the group will focus on - a schema definition - a set of operations for creation, modification, and deletion of users - schema discovery - read and search - bulk operations - mapping between the inetOrgPerson LDAP object class (RFC 2798) and the SCIM schema It will follow that by considering extensions for client targeting of specific SCIM endpoints and SAML binding. The approach will be extensible. The group will use, as starting points, the following drafts in the following ways: draft-scim-use-cases-00 as the initial use cases for SCIM draft-scim-core-schema-00 as the schema specification draft-scim-api-00 as the protocol specification These drafts are based on existing specifications, which together are commonly known as SCIM 1.0. Because there is existing work with existing implementations, some consideration should be given to backward compatibility, though getting it right takes priority. This group will consider the operational experience gathered from the existing work, as well as experiences with work done by other bodies, including the OASIS Provisioning TC. The use cases document will be a "living document", guiding the working group during its development of the standards. The group may take snapshots of that document for Informational publication, to serve as documentation of the motivation for the work in progress and to similarly guide planning and implementation. The group will produce Proposed Standards for a schema, a REST-based protocol, and a SAML binding, as well as an Informational document defining an LDAP mapping. In doing so, the group will make the terminology consistent, identify any functional gaps that would be useful for future work, address internationalization, and provide guidelines and mechanisms for extensibility. In addition, the working group will ensure that the SCIM protocol embodies good security practices. Given both the sensitivity of the information being conveyed in SCIM messages and the regulatory requirements regarding the privacy of personally identifiable information, the working group will pay particular attention to issues around authorization, authenticity, and privacy. The group considers the following out of scope for this group: Defining new authentication schemes Defining new policy/authorization schemes Goals and Milestones: Done - Initial adoption of SCIM core schema Done - Initial adoption of SCIM restful interface draft Nov 2012 - Initial adoption of SCIM LDAP inetOrgPerson mapping draft Dec 2012 - Proposal for client targeting of SCIM endpoints Feb 2013 - SCIM core schema to IESG as Proposed Standard Mar 2013 - Initial adoption of SCIM use cases, as a living document May 2013 - SCIM restful interface to IESG as Proposed Standard Jun 2013 - SCIM LDAP inetOrgPerson mapping to IESG as Informational Jul 2013 - Initial adoption of SCIM SAML bindings draft Aug 2013 - Client targeting of SCIM endpoints to IESG as Proposed Standard Sep 2013 - Snapshot update of SCIM use cases as Informational (possibly) Nov 2013 - SCIM SAML bindings to IESG as Proposed Standard Jan 2014 - Work completed; discuss re-charter Internet-Drafts: - System for Cross-Domain Identity Management: Protocol [draft-ietf-scim-api-16] (84 pages) - System for Cross-Domain Identity Management: Core Schema [draft-ietf-scim-core-schema-17] (86 pages) - SCIM Use Cases [draft-ietf-scim-use-cases-04] (18 pages) No Requests for Comments Time Zone Data Distribution Service (tzdist) -------------------------------------------- Charter Last Modified: 2014-08-08 Current Status: Active Chairs: Eliot Lear Daniel Migault Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Barry Leiba Mailing Lists: General Discussion: tzdist@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/tzdist Archive: http://www.ietf.org/mail-archive/web/tzdist/ Description of Working Group: The tzdist working group will define a time zone data distribution protocol that allows for efficient, timely updates of time zone data to be delivered to clients. The protocol must scale to vast numbers of clients, such as the potential "internet of things" devices, as well as to today's desktop computers and servers. A time zone is a region that has a uniform local time for legal, commercial, and social purposes, with some regions using daylight saving time (DST) rules for part of the year. A local time is defined as a standard offset from Coordinated Universal Time (UTC), and a set of DST rules. Time zone data represents the history, current, and future local time rules for these regions, together with an associated time zone identifier. Time zone data is a critical element of computer systems and devices that make use of local time. In particular, it is critical to any calendaring and scheduling system, such as iCalendar (RFC 5545). Daylight saving time rules, which affect local UTC offsets, can change - sometimes at very short notice (just a few days) - as those rules are typically defined by political processes. Currently, there is no efficient, fast way to ensure that time zone data is updated in a timely and reliable manner on devices that need it. Time zone changes are often delivered as operating system updates, and are thus tied to release schedules that can trail the actual time zone changes by a significant period of time. A service is needed that can provide timely, reliable updates. One added benefit of such a service for iCalendar is the ability for calendaring clients and servers to agree on common, standard definitions of time zone data, removing the need to pass time zone data directly "by value" in iCalendar data. By allowing clients and servers to use time zones "by reference" significant network bandwidth and storage savings can be achieved. This working group will: - Define a time zone data distribution protocol that allows for efficient, timely updates of time zone data to be delivered to clients. This protocol must scale to vast numbers of clients, such as the potential "internet of things" devices, as well as to today's desktop computers and servers. - Define an extension to CalDAV (RFC 4791) to allow clients and servers to use time zones "by reference" to improve the efficiency of the overall protocol. The working group will use the following drafts as initial input for its work: draft-douglass-timezone-service-11 draft-daboo-caldav-timezone-ref-01 The working group will work under the following parameters: - The time zone data distribution protocol will initially be targeted at iCalendar-based clients, but should be flexible enough to deliver time zone data in other formats. - The time zone data will be based on the Time Zone Database (http://www.iana.org/time-zones) but must be able to include any source of time zone data. - The time zone data distribution protocol should also offer an API to allow thin clients to easily make use of time zone data by querying for UTC offsets, offloading the sometimes complex work of expanding recurrence rules to the service. This API should be extensible to support other types of time zone operations in the future. - The time zone data distribution protocol will use current security protocols to protect the integrity and confidentiality of the data as it is distributed, and may also address these issues with respect to retrieval of data from its original source (such as the Time Zone Database). Even public time zone data can represent a significant privacy exposure when it is associated with the user or endpoint that is retrieving it. The following are Out of scope for the working group: - Any changes to the Time Zone Database process or infrastructure, as documented in RFC 6557. However, the WG may work with IANA in order to make integrity checking information, such as public keys, readily accessible for protocol use. - The naming process for time zone identifiers. The working group can consider adding a mechanism, such as a "namespace" prefix, to differentiate different time zone sources, but the nature of the time zone identifiers used will be controlled by the sources themselves. - Lookup protocols or APIs to map a location to a time zone. Goals and Milestones: Done - Adopt time zone data distribution protocol as WG document Done - Adopt a CalDAV extension draft as WG document Jan 2015 - WGLC for time zone data distribution protocol draft Jan 2015 - WGLC for CalDAV extension draft Mar 2015 - Request publication of time zone data distribution protocol draft as Standards Track RFC Mar 2015 - Request publication of CalDAV extension draft as Standards Track RFC Internet-Drafts: - CalDAV: Time Zones by Reference [draft-ietf-tzdist-caldav-timezone-ref-01] (10 pages) - Time Zone Data Distribution Service [draft-ietf-tzdist-service-06] (54 pages) No Requests for Comments Uniform Resource Names, Revised (urnbis) ---------------------------------------- Charter Last Modified: 2014-12-09 Current Status: Active Chairs: Melinda Shore Andrew Newton Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Barry Leiba Mailing Lists: General Discussion: urn@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/urn Archive: http://www.ietf.org/mail-archive/web/urn/ Description of Working Group: * * * Problem Statement * * * Uniform Resource Names (URNs) are location-independent, persistent identifiers for information resources. The RFCs defining URNs were published in 1997-2001. They rely on old (or even provisional) basic documents on the concepts of URI and URL. At that time there was almost no URN implementation experience. Since then, the URN system has gained significant popularity, and roughly 40 formal URN Namespaces have been defined and registered with IANA. Hundreds of millions of resources have been assigned URNs; this enables searching of and persistent linking to these documents, artifacts, and other objects. However, the URN system lacks a foundation that is consistent in terminology and formal description with present (Full) Internet Standards. The core URN RFCs -- RFC 2141 (URN Syntax), RFC 3406 (Namespace Definition Mechanisms) -- are based on outdated framework documents and understanding of digital archiving. All references in RFC 2141 point to "work in progress" or documents that have been superseded at least once. The lack of a standard definition of the 'urn' URI scheme fosters recurring discussions on what URNs are and IETF commitment to them. There is a need to clarify that URNs are specific URIs (namely those using the 'urn' URI scheme) and hence all general URI rules apply to URNs. There also is a need to update some namespace registrations for at least two reasons: the standards specifying the relevant underlying namespaces (such as International Standard Book Number (ISBN)) have been amended/expanded since the original specification of the related URN namespace and the WG's update of the basic URN-related RFCs might introduce or identify inconsistencies. * * * Objectives for the Working Group * * * This working group is chartered to update the key RFCs describing the URN system, including RFC 2141 (URN Syntax), RFC 3406 (Namespace Definition Mechanisms), and review and update selected URN namespace specifications including those for ISBN, National Bibliography Numbers (NBN) and International Serial Standard Number (ISSN). For all document revisions, backward compatibility with previous URN-related RFCs will be retained. The WG will produce an updated set of URN-related RFCs. All documents will be on the Standards-Track or BCP. These updates will provide a normative foundation for URNs and assure uniformity of the URN assignment and resolution concepts and procedures at the abstract level. Details and tasks (the WG will approach these tasks in roughly this order): a) Core URN specifications For RFC 2141, this revision will include in particular: - an update of the formal syntax specification in the light of the URI Standard (STD 66, RFC 3986) using the ABNF from STD 68 (RFC 5234); - a formal IANA registration for the 'urn' URI scheme using the current template from BCP 35 (RFC 4395); - a revised set of URN examples and - an update of the sections describing how URNs are resolved in the Internet, based on the current practices. RFC 3406 (BCP 33) will be aligned with the current IANA procedures and terminology as defined in BCP 26 (RFC 5226). b) URN Namespace specifications The WG will focus on updating the RFCs related to the key bibliographic identifier systems: - RFC 3187 (URN Namespace for International Standard Book Numbers), - RFC 3188 (URN Namespace for National Bibliography Numbers), and - RFC 3044 (URN Namespace for International Serial Standard Number). All these identifier systems have been updated since these RFCs were written in a way that makes revision of the namespace registration necessary. c) Further work The WG will support the current registrants of URN namespaces. It will review the legacy URN namespace definition documents and if needed, provide advice to their registrants on how to bring these registrations in line with the upcoming URN-related RFCs. However any work on updating such specifications beyond giving an advice would require rechartering of the WG. WG Output: +++++++++++++++++ Revision of RFC 2141 based on draft-ah-rfc2141bis-urn Revision of RFC 3406 Revision of RFC 3187 based on draft-hakala-rfc3187bis-isbn-urn Revision of RFC 3188 based on draft-hakala-rfc3188bis-nbn-urn Revision of RFC 3044 Goals and Milestones: Dec 2013 - Update URN Namespace Definition (3406bis) Dec 2013 - Collect and settle fragment/query requirements Jan 2014 - WGLC on URN Namespace Definition (3406bis) Jan 2014 - WGLC on URN Namespace Registration Transition Feb 2014 - Update URN Syntax (2141bis) based on resolution of requirements Mar 2014 - WGLC on URN Syntax (2141bis) Internet-Drafts: - Uniform Resource Name (URN) Namespace Registration Transition [draft-ietf-urnbis-ns-reg-transition-04] (8 pages) - Uniform Resource Names (URNs) [draft-ietf-urnbis-rfc2141bis-urn-10] (27 pages) - Using International Standard Serial Numbers as Uniform Resource Names [draft-ietf-urnbis-rfc3044bis-issn-urn-01] (20 pages) - Using International Standard Book Numbers as Uniform Resource Names [draft-ietf-urnbis-rfc3187bis-isbn-urn-03] (22 pages) - Using National Bibliography Numbers as Uniform Resource Names [draft-ietf-urnbis-rfc3188bis-nbn-urn-04] (20 pages) - Uniform Resource Name (URN) Namespace Definition Mechanisms [draft-ietf-urnbis-rfc3406bis-urn-ns-reg-09] (14 pages) - URN Semantics Clarification [draft-ietf-urnbis-semantics-clarif-01] (10 pages) - Names are Not Locators and URNs are Not URIs [draft-ietf-urnbis-urns-are-not-uris-01] (12 pages) No Requests for Comments Using TLS in Applications (uta) ------------------------------- Charter Last Modified: 2013-12-11 Current Status: Active Chairs: Leif Johansson Orit Levin Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Pete Resnick Mailing Lists: General Discussion: uta@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/uta Archive: http://www.ietf.org/mail-archive/web/uta/ Description of Working Group: There is a renewed and urgent interest in the IETF to increase the security of transmissions over the Internet. Many application protocols have defined methods for using TLS to authenticate the server (and sometimes the client), and to encrypt the connection between the client and server. However, there is a diversity of definitions and requirements, and that diversity has caused confusion for application developers and also has led to lack of interoperability or lack of deployment. Implementers and deployers are faced with multiple security issues in real-world usage of TLS, which currently does not preclude insecure ciphers and modes of operation. This WG has the following tasks: - Update the definitions for using TLS over a set of representative application protocols. This includes communication with proxies, between servers, and between peers, where appropriate, in addition to client/server communication. - Specify a set of best practices for TLS clients and servers, including but not limited to recommended versions of TLS, using forward secrecy, and one or more ciphersuites and extensions that are mandatory to implement. - Consider, and possibly define, a standard way for an application client and server to use unauthenticated encryption through TLS when server and/or client authentication cannot be achieved. - Create a document that helps application protocol developers use TLS in future application definitions. The initial set of representative application protocols is SMTP, POP, IMAP, XMPP, and HTTP 1.1. It is expected that other protocols that use TLS might later be updated using the guidelines from this WG, and that those updates will happen through other WGs or through individual submissions. The WG will make the fewest changes needed to achieve good interoperable security for the applications using TLS. No changes to TLS itself will be made in this WG, and the WG will ensure that changes to current versions of popular TLS libaries will not be required to conform to the WG's specifications. This WG will collaborate with other IETF WGs, in particular with the TLS and DANE WGs. Goals and Milestones: Internet-Drafts: - Deployable Enhanced Email Privacy (DEEP) [draft-ietf-uta-email-deep-00] (35 pages) - Updated TLS Server Identity Check Procedure for Email Related Protocols [draft-ietf-uta-email-tls-certs-01] (7 pages) - Summarizing Known Attacks on Transport Layer Security (TLS) and Datagram TLS (DTLS) [draft-ietf-uta-tls-attacks-05] (13 pages) - Recommendations for Secure Use of TLS and DTLS [draft-ietf-uta-tls-bcp-11] (28 pages) - Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP) [draft-ietf-uta-xmpp-05] (7 pages) - Deployable Enhanced Email Privacy (DEEP) [draft-newman-email-deep-02] (35 pages) Requests for Comments: RFC7457: Summarizing Known Attacks on Transport Layer Security (TLS) and Datagram TLS (DTLS) (13 pages) * Replaces DRAFT-SHEFFER-UTA-TLS-ATTACKS * Informative Reference RFC6347 * Informative Reference RFC5246 * Informative Reference DRAFT-IETF-UTA-TLS-BCP * Informative Reference RFC5746 * Informative Reference RFC6797 * Informative Reference RFC6989 * Informative Reference RFC5288 * Informative Reference DRAFT-IETF-TLS-PROHIBITING-RC4 * Informative Reference DRAFT-IETF-WEBSEC-KEY-PINNING * Informative Reference DRAFT-IETF-TLS-NEGOTIATED-FF-DHE * Informative Reference BCP5 * Informative Reference DRAFT-SHEFFER-TLS-BCP * Informative Reference RFC4347 * Informative Reference RFC5705 * Informative Reference RFC7258 * Informative Reference RFC5929 * Informative Reference DRAFT-IETF-TLS-ENCRYPT-THEN-MAC * Informative Reference BCP188 * Informative Reference DRAFT-IETF-TRILL-CHANNEL-TUNNEL * Informative Reference DRAFT-IETF-UTA-TLS-BCP Web Extensible Internet Registration Data Service (weirds) ---------------------------------------------------------- Charter Last Modified: 2012-02-23 Current Status: Active Chairs: Olaf M. Kolkman Murray Kucherawy Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Pete Resnick Mailing Lists: General Discussion: weirds@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/weirds Archive: http://www.ietf.org/mail-archive/web/weirds/ Description of Working Group: Internet registries for both number resources and names have historically maintained a lookup service to permit public access to some portion of the registry database. Most registries offer the service via WHOIS (RFC 3912), with additional services being offered via world wide web pages, bulk downloads, and other services, such as RPSL (RFC 2622). WHOIS has never been internationalized. In the absence of formal specification, ad hoc solutions to signal internationalized registration data have been adopted and deployed. Providing a standards-based solution that scales well could minimize further proliferation of ad hoc solutions. WHOIS also has no data model: replies are basically just free-form text. This means that processing of WHOIS output amounts to "screen scraping", with specialized handlers for every service. While many of the domain name registries share a basic common output format, the addition of data elements changes the output and causes problems for parsers of the data. The WHOIS protocol does not offer any differential service; it cannot differentiate among clients to offer different subsets of information or to allow different access rates to it. Various attempts to solve the limitations of WHOIS have met with mixed success. The most recent of these was IRIS (RFC 3981). IRIS has not been a successful replacement for WHOIS. The primary technical reason for this appears to be the complexity of IRIS, the fact that it builds upon many available technologies that in the aggregate form a complex system. There may also exist non-technical reasons, but they lie in areas upon which the IETF does not pass judgement. In recent years, ARIN and RIPE NCC have fielded production RESTful web services to serve WHOIS data, and each has met with success. It is widely believed that this simpler re-use of Web technologies familiar to modern web developers has enabled this success. The purpose of this working group is to broaden the use of RESTful web services by achieving simple and common URI patterns and responses amenable to all number resource and domain name registries. This Working Group shall determine the general needs of such a service, and standardize a single data framework. That framework shall be used to encapsulate objects that could form part of an answer. The framework shall be for data to be delivered via a RESTful data service using HTTP (optionally using TLS), and may use standard features of HTTP to support differential service levels to different classes of user. The data shall have one mandatory format, though the working group may consider other optional formats. The overall effort will be broadly aligned with a subset of the Cross Registry Internet Service Protocol (CRISP) Requirements (RFC 3707), but with the explicit additional goals of producing a simple, easy-to-implement protocol, supporting internationalized registration data and, specifically for name registries, capturing the needs of internationalized domain names in the data model. As the number registries have more experience with these services and have found common ground, with their dissimilarities resulting in more complete working group input documents, the goals of the working group are to produce standards-track specifications for both number and name registries using the fashion and pattern of the number registry input documents, draft-newton-et-al-weirds-rir-query and draft-newton-et-al-weirds-rir-json-response, as an initial basis. Work to specify the query for domain name registration data will be based on draft-sheng-weirds-icann-rws-dnrd. The Working Group shall determine the general requirements of such a service, using draft-kucherawy-weirds-requirements as an input document, and standardize a single data framework. The working group will likely not seek publication of this draft. Should the Working Group reach a point where it determines that the problem of producing a grand unified specification for both numbers and names appears to be intractable, it will be permitted to divide the problem into separate tasks and amend its milestones accordingly. Goals and Milestones: Sep 2014 - draft-ietf-weirds-redirects to the IESG Done - draft-ietf-weirds-rdap-query to the IESG Sep 2014 - draft-ietf-weirds-json-response to the IESG Sep 2014 - draft-ietf-weirds-using-http to the IESG Sep 2014 - draft-ietf-weirds-rdap-sec to the IESG Done - draft-ietf-weirds-object-inventory to the IESG Sep 2014 - Draft describing bootstrapping protocol to the IESG Internet-Drafts: - Finding the Authoritative Registration Data (RDAP) Service [draft-blanchet-weirds-bootstrap-ianaregistries-01] (7 pages) - Using HTTP for RESTful Whois Services by Internet Registries [draft-designteam-weirds-using-http-01] (26 pages) - Domain Name Registration Data Access Protocol Query Format [draft-hollenbeck-dnrd-ap-query-01] (14 pages) - Security Services for the Registration Data Access Protocol [draft-hollenbeck-weirds-rdap-sec-00] (7 pages) - Unified Registration Data Access Protocol Query Format [draft-hollenbeck-weirds-unified-rdap-query-00] (10 pages) - Finding the Authoritative Registration Data (RDAP) Service [draft-ietf-weirds-bootstrap-11] (17 pages) - JSON Responses for the Registration Data Access Protocol (RDAP) [draft-ietf-weirds-json-response-14] (91 pages) - Registration Data Access Protocol Object Inventory Analysis [draft-ietf-weirds-object-inventory-06] (32 pages) - Registration Data Access Protocol Query Format [draft-ietf-weirds-rdap-query-18] (20 pages) - Security Services for the Registration Data Access Protocol [draft-ietf-weirds-rdap-sec-12] (13 pages) - Redirection Service for Registration Data Access Protocol [draft-ietf-weirds-redirects-04] (7 pages) - HTTP usage in the Registration Data Access Protocol (RDAP) [draft-ietf-weirds-using-http-15] (20 pages) - Domain Name Registration Data Access Protocol Response Format defined in JSON [draft-kong-dnrd-ap-response-json-00] (21 pages) - Requirements For Internet Registry Services [draft-kucherawy-weirds-requirements-04] (7 pages) - LACNIC's Redirection Service for Number Resource RESTful WHOIS Queries [draft-lacnic-weirds-restwhois-redirects-00] (15 pages) - JSON Responses to RESTful URL Queries for RIRs [draft-newton-et-al-weirds-rir-json-response-02] (17 pages) - A Uniform RESTful URL Query Pattern for RIRs [draft-newton-et-al-weirds-rir-query-02] (10 pages) - JSON Responses to RESTful URL Queries for RIRs and DNRs [draft-newton-weirds-unified-json-response-00] (33 pages) - A RESTful Web Service for Domain Name Registration Data (RWS-DNRD) [draft-sheng-weirds-icann-rws-dnrd-01] (22 pages) No Requests for Comments Web Security (websec) --------------------- Charter Last Modified: 2012-07-30 Current Status: Active Chairs: Tobias Gondrom Yoav Nir Applications Area Directors: Barry Leiba Pete Resnick Applications Area Advisor: Barry Leiba Tech Advisor: spt Mailing Lists: General Discussion: websec@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/websec Archive: http://www.ietf.org/mail-archive/web/websec/ Description of Working Group: Problem Statement Although modern Web applications are built on top of HTTP, they provide rich functionality and have requirements beyond the original vision of static web pages. HTTP, and the applications built on it, have evolved organically. Over the past few years, we have seen a proliferation of AJAX-based web applications (AJAX being shorthand for asynchronous JavaScript and XML), as well as Rich Internet Applications (RIAs), based on so-called Web 2.0 technologies. These applications bring both luscious eye-candy and convenient functionality, e.g. social networking, to their users, making them quite compelling. At the same time, we are seeing an increase in attacks against these applications and their underlying technologies. The list of attacks is long and includes Cross-Site-Request Forgery (CSRF)-based attacks, content-sniffing, cross-site-scripting (XSS) attacks, attacks against browsers supporting anti-XSS policies, clickjacking attacks, malvertising attacks, as well as man-in-the-middle (MITM) attacks against "secure" (e.g. Transport Layer Security (TLS/SSL)-based) web sites along with distribution of the tools to carry out such attacks (e.g. sslstrip). Objectives and Scope With the arrival of new attacks the introduction of new web security indicators, security techniques, and policy communication mechanisms have sprinkled throughout the various layers of the Web and HTTP. The goal of this working group is to compose an overall "problem statement and requirements" document derived from surveying the issues outlined in the above section ([1] provides a starting point). The requirements guiding the work will be taken from the Web application and Web security communities. The scope of this document is HTTP applications security, but does not include HTTP authentication, nor internals of transport security which are addressed by other working groups (although it may make reference to transport security as an available security "primitive"). See the "Out of Scope" section, below. Additionally, the WG will standardize a small number of selected specifications that have proven to improve security of Internet Web applications. Initial work will be the following topics: - Same origin policy, as discussed in draft-abarth-origin (see also Appendices A and B, below) - HTTP Strict transport security, as discussed in draft-hodges-strict-transport-sec - Media type sniffing, as discussed in draft-abarth-mime-sniff This working group will work closely with IETF Apps Area WGs (such as HYBI, HTTPstate, and HTTPbis), as well as appropriate W3C working group(s) (e.g. HTML, WebApps). Out of Scope As noted in the objectives and scope (above), this working group's scope does not include working on HTTP Authentication nor underlying transport (secure or not) topics. So, for example, these items are out-of-scope for this WG: - Replacements for BASIC and DIGEST authentication - New transports (e.g. SCTP and the like) Deliverables 1. A document illustrating the security problems Web applications are facing and listing design requirements. This document shall be Informational. 2. A selected set of technical specifications documenting deployed HTTP-based Web security solutions. These documents shall be Standards Track. References [1] Hodges and Steingruebl, "The Need for a Coherent Web Security Policy Framework", W2SP position paper, 2010. http://w2spconf.com/2010/papers/p11.pdf Appendices A. Relationship between origin work in IETF WebSec and W3C HTML WG draft-abarth-origin defines the nuts-and-bolts of working with origins (computing them from URIs, comparing them to each other, etc). HTML5 defines HTML-specific usage of origins. For example, when making an HTTP request, HTML5 defines how to compute which origin among all the origins rendering HTML is the one responsible for making the request. draft-abarth-origin then takes that origin, serializes it to a string, and shoves it in a header. B. Origin work may yield two specifications There also seems to be demand for a document that describes the same-origin security model overall. However, it seems like that document ought to be more informative rather than normative. The working group may split draft-abarth-origin into separate informative and standards track specifications, the former describing same-origin security model, and the latter specifying the nuts-and-bolts of working with origins (computing them from URLs, comparing them to each other, etc). Goals and Milestones: Done - Submit 'HTTP Application Security Problem Statement and Requirements' as initial WG item. Done - Submit 'Media Type Sniffing' as initial WG item. Done - Submit 'Web Origin Concept' as initial WG item. Done - Submit 'Strict Transport Security' as initial WG item. Done - Submit 'Web Origin Concept' to the IESG for consideration as a Standards Track RFC. Done - Submit 'Strict Transport Security' to the IESG for consideration as a Standards Track RFC. Done - Adopt 'Frame-Options' as initial WG item. Done - Adopt 'X-Frame-Options' as initial WG item. Done - Submit 'X-Frame-Options' to the IESG for consideration as a Informational Track RFC. Done - Adopt 'HTTP Application Security Problem Statement and Requirements' as initial WG item. May 2013 - Submit 'Public Key Pinning Extension for HTTP' to the IESG for consideration as a Standards Track RFC. Jul 2013 - Submit 'HTTP Application Security Problem Statement and Requirements' to the IESG for consideration as an Informational RFC. Internet-Drafts: - HTTP Header Frame Options [draft-gondrom-frame-options-02] (9 pages) - HTTP Header X-Frame-Options [draft-gondrom-x-frame-options-00] (9 pages) - HTTP Header Frame Options [draft-ietf-websec-frame-options-00] (9 pages) - Web Security Framework: Problem Statement and Requirements [draft-ietf-websec-framework-reqs-00] (28 pages) - Public Key Pinning Extension for HTTP [draft-ietf-websec-key-pinning-21] (28 pages) - Media Type Sniffing [draft-ietf-websec-mime-sniff-03] (24 pages) - The Web Origin Concept [draft-ietf-websec-origin-06] (20 pages) - Hypertext Transport Protocol (HTTP) Session Continuation: Problem Statement [draft-ietf-websec-session-continue-prob-00] (13 pages) - HTTP Strict Transport Security (HSTS) [draft-ietf-websec-strict-transport-sec-14] (46 pages) - HTTP Header Field X-Frame-Options [draft-ietf-websec-x-frame-options-12] (14 pages) Requests for Comments: RFC6454: The Web Origin Concept (20 pages) * Normative Reference RFC2616 * Normative Reference BCP14 * Normative Reference RFC3864 * Possible Reference RFC5741 * Normative Reference BCP90 * Informative Reference RFC2397 * Normative Reference RFC5234 * Informative Reference RFC3490 * Normative Reference RFC4790 * Normative Reference RFC5890 * Normative Reference RFC5891 * Informative Reference RFC6265 * Normative Reference RFC2119 * Normative Reference STD68 * Informative Reference RFC6455 * Normative Reference STD66 * Informative Reference RFC5246 * Normative Reference RFC20 * Normative Reference RFC3986 * Informative Reference RFC2817 * Informative Reference DRAFT-CHENXIN-BEHAVE-TURN-WEBSOCKET * Normative Reference RFC7486 * Informative Reference DRAFT-IETF-HTTPAUTH-MUTUAL * Normative Reference DRAFT-JOHNSTON-TRAM-STUN-ORIGIN * Informative Reference RFC6787 * Normative Reference RFC6455 * Informative Reference RFC6797 * Informative Reference RFC6690 * Informative Reference RFC6555 * Informative Reference DRAFT-GONDROM-FRAME-OPTIONS * Normative Reference RFC7030 * Normative Reference DRAFT-NOTTINGHAM-HTTP-BROWSER-HINTS * Informative Reference DRAFT-IETF-RTCWEB-SECURITY * Informative Reference RFC6920 * Informative Reference DRAFT-PD-DISPATCH-MSRP-WEBSOCKET * Informative Reference DRAFT-RESCORLA-RTCWEB-GENERIC-IDP * Normative Reference DRAFT-NIR-WEBSEC-EXTENDED-ORIGIN * Normative Reference DRAFT-MBELSHE-HTTPBIS-SPDY * Informative Reference DRAFT-GONDROM-X-FRAME-OPTIONS * Informative Reference DRAFT-GONDROM-WEBSEC-CSP-HEADER * Normative Reference DRAFT-MONTENEGRO-HTTPBIS-SPEED-MOBILITY * Normative Reference DRAFT-RPEON-HTTPBIS-EXPROXY * Normative Reference DRAFT-FARRELL-HTTPBIS-HOBA * Normative Reference RFC7034 * Informative Reference DRAFT-IETF-WEBSEC-FRAME-OPTIONS * Normative Reference DRAFT-SNELL-HTTPBIS-KEYNEGO * Informative Reference DRAFT-IETF-WEBSEC-FRAMEWORK-REQS * Normative Reference DRAFT-UNICORN-HTTPBIS-HTTP2 * Informative Reference DRAFT-SAVOLAINEN-CORE-COAP-WEBSOCKETS * Informative Reference RFC7395 * Normative Reference DRAFT-IETF-HTTPAUTH-DIGEST * Informative Reference DRAFT-THOMSON-MMUSIC-ICE-WEBRTC * Normative Reference DRAFT-NOTTINGHAM-HTTPBIS-ALT-SVC * Possible Reference DRAFT-VIDYA-HTTPBIS-EXPLICIT-PROXY-PS * Normative Reference DRAFT-IETF-HTTPBIS-ALT-SVC * Normative Reference DRAFT-THOMSON-HTTPBIS-CATCH * Normative Reference DRAFT-THOMSON-HTTPBIS-HTTP-TLS * Normative Reference DRAFT-IETF-HTTPBIS-HTTP2-ENCRYPTION * Normative Reference DRAFT-IETF-TRAM-STUN-ORIGIN * Normative Reference DRAFT-WEST-ORIGIN-COOKIES * Normative Reference DRAFT-WEST-FIRST-PARTY-COOKIES * Informative Reference DRAFT-IETF-HTTPBIS-HEADER-COMPRESSION * Informative Reference DRAFT-RUBY-URL-PROBLEM * Normative Reference DRAFT-IETF-RTCWEB-SECURITY-ARCH RFC6797: HTTP Strict Transport Security (HSTS) (46 pages) * Replaces DRAFT-HODGES-STRICT-TRANSPORT-SEC * Informative Reference RFC5226 * Informative Reference RFC2560 * Informative Reference RFC2616 * Normative Reference BCP14 * Normative Reference RFC3864 * Normative Reference RFC6698 * Possible Reference RFC5741 * Informative Reference RFC1035 * Normative Reference BCP90 * Informative Reference STD13 * Normative Reference RFC3490 * Informative Reference RFC4033 * Normative Reference RFC5890 * Normative Reference RFC5891 * Informative Reference RFC6265 * Informative Reference RFC4949 * Normative Reference RFC5895 * Informative Reference RFC4732 * Normative Reference RFC2119 * Informative Reference BCP26 * Informative Reference RFC6125 * Informative Reference RFC6454 * Informative Reference RFC5905 * Normative Reference STD66 * Normative Reference RFC2818 * Informative Reference RFC6066 * Normative Reference RFC5246 * Normative Reference RFC3986 * Informative Reference RFC5894 * Informative Reference RFC5280 * Informative Reference RFC6101 * Informative Reference DRAFT-MILLER-POSH * Normative Reference DRAFT-NYGREN-SERVICE-BINDINGS * Informative Reference DRAFT-IETF-UTA-TLS-BCP * Informative Reference RFC6920 * Normative Reference DRAFT-IETF-WEBSEC-KEY-PINNING * Informative Reference DRAFT-IETF-WEBSEC-FRAMEWORK-REQS * Normative Reference DRAFT-WILSON-WPKOPS-BROWSER-PROCESSING * Normative Reference DRAFT-BARREIRA-TRUSTMODEL * Reference DRAFT-WCHUANG-MSMD * Normative Reference DRAFT-IETF-WPKOPS-TRUSTMODEL * Informative Reference DRAFT-IETF-XMPP-POSH * Informative Reference RFC7457 * Reference DRAFT-KENT-OPPORTUNISTIC-SECURITY * Normative Reference DRAFT-THOMSON-HTTPBIS-HTTP-TLS * Informative Reference DRAFT-NEWMAN-EMAIL-DEEP * Normative Reference DRAFT-CEM-DANE-ASSERTION * Informative Reference DRAFT-IETF-UTA-EMAIL-DEEP RFC7034: HTTP Header Field X-Frame-Options (14 pages) * Replaces DRAFT-GONDROM-X-FRAME-OPTIONS * Normative Reference RFC5234 * Normative Reference STD68 * Informative Reference BCP178 * Normative Reference RFC6454 * Informative Reference RFC2616 * Normative Reference STD66 * Informative Reference RFC6648 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC3986 * Informative Reference BCP90 * Normative Reference RFC2119 * Informative Reference RFC3864 Planning for the IANA/NTIA Transition (ianaplan) ------------------------------------------------ Charter Last Modified: 2014-09-08 Current Status: Active Chairs: Marc Blanchet Leslie Daigle General Area Directors: Jari Arkko General Area Advisor: Jari Arkko Mailing Lists: General Discussion: ianaplan@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/ianaplan Archive: http://www.ietf.org/mail-archive/web/ianaplan/ Description of Working Group: Background ========== Registries of parameter values for use in IETF protocols are stored and maintainted for the IETF by the Internet Assigned Numbers Authority (IANA), and are the subject of the "IANA Considerations" section in many RFCs. For a number of years, this IANA function has been provided by the Internet Corporation for Assigned Names and Numbers (ICANN). The IETF's relationship with IANA was formalized through a Memorandum of Understanding between the IETF and ICANN codified in 2000 with the publication of RFC 2860. Over time, processes and role definitions have evolved, and have been documented in supplemental agreements. ICANN has had a contract with the US Department of Commerce (DoC) to provide the IANA function, undertaken through the National Telecommunications and Information Administration (NTIA). In March of 2014, NTIA announced its intention to transition out of its current role, meaning that NTIA would not need to renew its contract with ICANN when that contract expires 30 September 2015. NTIA requested a transition proposal be prepared to outline the necessary arrangements. In the case of the elements of the IANA function concerning the IETF protocol registries, it is likely that the existing well-documented practices will continue and no or little new activity will be required. Tasks ===== The IANAPLAN working group is chartered to produce an IETF consensus document that describes the expected interaction between the IETF and the operator of IETF protocol parameters registries. The system in place today for oversight of the IETF protocol registries component of the IANA function works well. As a result, minimal change in the oversight of the IETF protocol parameters registries is preferred in all cases and no change is preferred when possible. The working group will address the implications of moving the NTIA out of its current role with respect to IANA on the IETF protocol parameters registry function in a way that focuses on continuation of the current arrangements. The working group will assume the following documents continue to be in effect: - RFC 2850 - RFC 3777 and its updates - RFC 2860 - RFC 6220 - IETF-ICANN-MOU_2000 (http://iaoc.ietf.org/documents/IETF-ICANN-MOU_2000.pdf) - ICANN-IETF Supplemental Agreements (updated yearly since 2007, the 2014 version is available at http://iaoc.ietf.org/documents/ 2014-ICANN-IETF-MoU-Supplemental-Agreement-Executed.pdf) This working group is chartered solely with respect to the planning needed for the transition, and is not meant to cover other topics related to IANA. Possible improvements outside that scope will be set aside for future consideration. However, the mechanisms required to address the removal of the overarching NTIA contract may require additional documentation or agreements. The WG will identify, but not create, such required agreements. Should proposals made by other communities regarding the transition of other IANA functions affect the IETF protocol parameter registries or the IETF, the WG may also review and comment on them. Fully documenting the interaction between the IETF and the operator of IETF protocol parameters registries may require detailed terms of agreements or other details of procedures that are normally delegated to and handled by the IAB or IAOC. The working group will not attempt to produce or discuss documentation for these details, but will request the IAB or IAOC to provide them separately. The WG shall seek the expertise of the IAB IANA Evolution Program to formulate its output. It is expected that members of the IAB IANA Evolution Program will actively participate in the WG. Goals and Milestones: Jan 2015 - complete protocol parameters registries document May 2015 - review of other transition proposals, if needed Sep 2015 - close Internet-Drafts: - Draft Response to the Internet Coordination Group Request for Proposals on the IANA protocol parameters registries [draft-ietf-ianaplan-icg-response-09] (33 pages) No Requests for Comments Access Node Control Protocol (ancp) ----------------------------------- Charter Last Modified: 2013-03-13 Current Status: Active Chairs: Wojciech Dec Matthew Bocci Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Tech Advisor: Dan Romascanu Mailing Lists: General Discussion: ancp@ietf.org To Subscribe: ancp-request@ietf.org Archive: http://www.ietf.org/mail-archive/web/ancp/ Description of Working Group: Purpose: The purpose of the ANCP WG is to standardize an IP-based Access Node Control Protocol (ANCP) for use in service provider Digital Subscriber Line (DSL) and Passive Optical Network (PON) access and aggregation networks. ANCP operates between an Access Node (AN) and Network Access Server (NAS). Necessary Terminology: Access Node (AN) - Network device, usually located at a service provider central office or street cabinet, that terminates access loop connections from Subscribers. In DSL, this is often referred to as a Digital Subscriber Line Access Multiplexer (DSLAM). In PON, this is usually comprised of an Optical Network Termination (ONT) / Optical Network Unit (ONU) and an Optical Line Termination (OLT). Network Access Server (NAS) - Network device which aggregates multiplexed Subscriber traffic from a number of Access Nodes. The NAS plays a central role in per-subscriber policy enforcement and QoS. This is often referred to as a Broadband Network Gateway (BNG) or Broadband Remote Access Server (BRAS). A detailed definition of the NAS is given in RFC2881. Goals: ANCP is intended to address the requirement for a bidirectional, IP- based, control protocol that operates across multiple types (i.e., Ethernet, ATM) of DSL and PON access and aggregation networks. The goal of an ANCP message exchange is to convey status and control information between one or more ANs and one or more NASs without going through intermediate element managers. The ANCP WG will address the following four use-cases: 1. Dynamic Access Loop Attributes Various queuing and scheduling mechanisms are used in access networks to avoid congestion while dealing with multiple flows and distinct QoS profiles. Communicating the access-loop status, attributes and current DSL synchronization rate between the AN and Subscriber up to the NAS is desirable, particularly when the NAS is providing QoS for individual flows and subscribers. ANCP will provide a mechanism to communicate dynamic access-loop attributes from the AN to the NAS. 2. Access Loop Configuration In additional to reporting Access Loop characteristics from the AN to the NAS, ANCP will allow a NAS to send loop-specific configuration information to an AN based on the results of subscriber authentication and authorization (e.g., after AAA responses have been received at the NAS). 3. Remote Connectivity Test Traditional DSL access and aggregation networks employ point-to-point ATM circuits between the AN and NAS for each subscriber, allowing troubleshooting of the local loop from the NAS via ATM OAM tools. With the increasing deployment of Ethernet in the access and aggregation network, operators require consistent methods to test and troubleshoot connectivity for mixed Ethernet and ATM access networks (including the local loop). ANCP will allow a remote procedure for a local loop connectivity test to be triggered from the NAS with results communicated back to the NAS. 4. Multicast When multicast replication for subscriber-bound traffic is performed at the AN, it offloads the network between the AN and NAS. However, a subscriber's policy and configuration for multicast traffic may only be known at the NAS. ANCP will provide a mechanism to communicate the necessary information exchange between the AN and NAS so as to allow the AN to perform subscriber bound multicast group replication in line with the subscriber's policy and configuration, and also allow the NAS to follow each subscriber's multicast group membership. Non-Goals: ANCP is an IP-based protocol that operates between the AN and NAS. It will not address setup or configuration of circuits or connections in the access and aggregation network itself. The focus of this WG is on one very specific application space. While the design of the protocol must be general as to not preclude other uses in the future should a need arise, it is not a goal of this WG to address specific requirements outside of service provider broadband (such as xDSL, xPON) access and aggregation networks. Security: The ANCP working group will provide a threat analysis and address the associated security aspects of the control protocol. Resiliency and Scalability: A graceful restart mechanism will be defined to enable the protocol to be resilient to network failures between the AN and NAS. Scalability at the NAS is of primary concern, as it may be aggregating traffic from a large number of ANs, which in turn may be serving a large number of Subscribers. ANCP traffic should not become a denial of service attack on the NAS control plane. Format of messages, pacing, transport over UDP or TCP, etc. will be considered with this in mind. For reasons of aggregation network scalability, some use cases require that aspects of NAS or AN functionality may be distributed in nodes in the aggregation network. In these cases, ANCP can run between these nodes. Deliverables: The working group will define a basic framework and requirements document intended for Informational publication, focusing on the four use-cases outlined in this charter. This document will include a security threat analysis and associated requirements. The WG will then investigate and define a solution for an IP based control protocol meeting these requirements. There are early interoperable implementations of an ANCP-like protocol which are based on an extended subset of the GSMPv3 protocol. This running code will be the the starting point for the working group solution, and will be abandoned only if the WG determines it is not adequate to meet requirements going forward. Coordination with other Working Groups or Organizations: The working group will coordinate with the ADSL MIB working group so the management framework and MIB modules are consistent for DSL access environments. The working group will re-use, as far as possible, standard MIB modules that have already been defined. The remote connectivity test use case may require coordination with ITU-T Ethernet OAM and PON work and with IEEE 802.1ag. Goals and Milestones: Done - Accept WG I-D for ANCP Framework and Requirements Done - Accept WG I-D for Access Node Control Protocol (ANCP) Done - Accept WG ID for Security Threats analysis Done - Accept WG I-D for ANCP MIB Done - Security Threats Analysis last call Done - Framework and Requirements last call Done - Accept WG I-D for ANCP Multicast Extensions Done - Accept WG I-D for ANCP applicability to PON Sep 2010 - Access Node Control Protocol (ANCP) Last Call Dec 2010 - ANCP MIB Last Call Dec 2010 - ANCP Multicast Extensions last call Jan 2011 - ANCP applicability to PON last call Mar 2011 - Re-charter or conclude Working Group Internet-Drafts: - Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks [draft-ietf-ancp-framework-13] (47 pages) - Multicast Control Extensions for the Access Node Control Protocol (ANCP) [draft-ietf-ancp-mc-extensions-16] (99 pages) - Access Node Control Protocol (ANCP) MIB module for Access Nodes [draft-ietf-ancp-mib-an-12] (39 pages) - Applicability of the Access Node Control Mechanism to Broadband Networks Based on Passive Optical Networks (PONs) [draft-ietf-ancp-pon-05] (39 pages) - Protocol for Access Node Control Mechanism in Broadband Networks [draft-ietf-ancp-protocol-17] (82 pages) - Security Threats and Security Requirements for the Access Node Control Protocol (ANCP) [draft-ietf-ancp-security-threats-08] (18 pages) Requests for Comments: RFC5713: Security Threats and Security Requirements for the Access Node Control Protocol (ANCP) (18 pages) * Replaces DRAFT-MOUSTAFA-ANCP-SECURITY-THREATS * Normative Reference RFC3365 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference BCP61 * Normative Reference RFC5851 * Informative Reference RFC6320 * Informative Reference RFC7256 * Informative Reference RFC6934 * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference RFC6632 * Informative Reference DRAFT-GARCIA-CORE-SECURITY * Informative Reference DRAFT-XQ-ANCP-WLAN RFC5851: Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks (47 pages) * Replaces DRAFT-OOGHE-ANCP-FRAMEWORK * Informative Reference RFC3376 * Normative Reference STD41 * Normative Reference RFC2684 * Normative Reference RFC5713 * Informative Reference RFC2881 * Possible Reference RFC5741 * Informative Reference RFC2225 * Informative Reference RFC2364 * Informative Reference RFC2516 * Informative Reference RFC4607 * Normative Reference RFC894 * Normative Reference RFC2119 * Normative Reference BCP14 * Informative Reference RFC7256 * Informative Reference DRAFT-IETF-ANCP-MIB-AN * Informative Reference RFC6320 * Informative Reference RFC6934 * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference RFC6632 * Informative Reference DRAFT-DEC-6MAN-RS-ACCESS-HARMFUL * Informative Reference DRAFT-XQ-ANCP-WLAN RFC6320: Protocol for Access Node Control Mechanism in Broadband Networks (82 pages) * Normative Reference RFC3629 * Informative Reference RFC5226 * Informative Reference RFC4649 * Informative Reference RFC5713 * Normative Reference BCP14 * Informative Reference RFC3315 * Informative Reference RFC3046 * Possible Reference RFC5741 * Informative Reference RFC5925 * Possible Reference RFC1987 * Possible Reference RFC2297 * Normative Reference RFC5646 * Normative Reference RFC5996 * Normative Reference RFC2119 * Informative Reference BCP26 * Informative Reference RFC2131 * Normative Reference RFC3292 * Normative Reference BCP47 * Normative Reference STD63 * Normative Reference RFC4303 * Normative Reference RFC4301 * Informative Reference RFC5246 * Informative Reference RFC5851 * Informative Reference RFC7256 * Updates RFC7256 * Normative Reference DRAFT-IETF-ANCP-MIB-AN * Informative Reference RFC6934 * Informative Reference RFC6632 * Normative Reference DRAFT-XQ-ANCP-WLAN RFC6934: Applicability of the Access Node Control Mechanism to Broadband Networks Based on Passive Optical Networks (PONs) (39 pages) * Normative Reference RFC3376 * Normative Reference RFC2684 * Informative Reference RFC3046 * Informative Reference RFC5713 * Informative Reference RFC2881 * Possible Reference RFC5741 * Informative Reference RFC6320 * Informative Reference RFC5851 * Normative Reference RFC2516 * Normative Reference RFC4605 RFC7256: Multicast Control Extensions for the Access Node Control Protocol (ANCP) (99 pages) * Normative Reference RFC5790 * Normative Reference BCP14 * Informative Reference RFC5851 * Informative Reference RFC4601 * Normative Reference RFC3810 * Normative Reference RFC2119 * Informative Reference RFC6320 * Updates RFC6320 * Informative Reference RFC6733 * Possible Reference RFC5741 * Informative Reference RFC2236 * Normative Reference RFC2710 * Informative Reference RFC5713 * Informative Reference RFC6614 * Normative Reference RFC3376 Distributed Mobility Management (dmm) ------------------------------------- Charter Last Modified: 2013-12-23 Current Status: Active Chairs: Dapeng Liu Jouni Korhonen Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Brian Haberman Mailing Lists: General Discussion: dmm@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/dmm Archive: http://www.ietf.org/mail-archive/web/dmm Description of Working Group: Mobility management solutions lie at the center of the wireless Internet and enable mobile devices to partake in IP networks anytime and anywhere. The IETF Distributed Mobility Management (DMM) working group (WG) specifies solutions for IP networks so that traffic between mobile and correspondent nodes can take an optimal route. DMM solutions aim for transparency above the IP layer, including maintenance of active transport level sessions when mobile hosts or mobile networks change their point of attachment to the Internet. Wireless network deployments have traditionally relied on hierarchical schemes that often lead to centralized deployment models, where a small number of mobility anchors manage both mobility and reachability for a mobile node. The DMM WG will consider the latest developments in mobile networking research and operational practice (i.e. flattening network architectures, the impact of virtualization, new deployment needs as wireless access technologies evolve in the coming years) and will describe how distributed mobility management addresses the new needs in this area better than previously standardized solutions. A topic of particular focus will be mobility anchoring in this new context, and the DMM working group is chartered to work on maintenance-oriented extensions of the Mobile IPv6 protocol family (RFC 5213, RFC 5844, RFC 5555, RFC 5568, and RFC 6275) as well as new approaches which capitalize on other protocols specified by the IETF. For example, mobility management in a limited area, such as within an autonomous system, is not strictly limited to mentioned IP mobility protocols but can be any existing or a new protocol solution enabling the movement of a mobile node such as routing protocols. When extending protocols that are not based on Mobile IP, DMM solutions will have to be reviewed by the corresponding WGs. IPv6 is assumed to be present in both the mobile host/router and the access networks. DMM solutions are primarily targeted at IPv6 deployments and are not required to support IPv4, in particular for the case where private IPv4 addresses and/or NATs are used. DMM solutions must maintain backward compatibility: If the network or the mobile host/router does not support the distributed mobility management protocol that should not prevent the mobile host/router gaining basic access (i.e., nomadic) to the network. Contrary to earlier IP mobility protocols, mobility management signaling paths and end-user traffic forwarding paths may differ. Further, mobility-related functions may be located in separate network nodes. DMM solutions should not distinguish between physical or virtualized networking functions. Whenever applicable, clarifications and additional features/capabilities for specific networking function deployment models, e.g. in virtualized environments, are in-scope and encouraged. Solutions may also specify the selection between the care-of addresses and home address(es)/prefix(es) for different application use cases. The working group will produce one or more documents on the following work item topics. o Distributed mobility management deployment models and scenarios: describe the target high-level network architectures and deployment models where distributed mobility management protocol solutions would apply. o Enhanced mobility anchoring: define protocol solutions for a gateway and mobility anchor assignment and mid-session mobility anchor switching that go beyond what has been specified, for example, in RFC 6097, 6463, and 5142. Traffic steering associated with the anchor switch is also in-scope if deemed appropriate. o Forwarding path and signaling management: the function that handles mobility management signaling interacts with the DMM network elements for managing the forwarding state associated with a mobile node's IP traffic. These two functions may or may not be collocated. Furthermore, the forwarding state may also be distributed into multiple network elements instead of a single network element (e.g., anchor). Protocol extensions or new protocols will be specified to allow the above mentioned forwarding path and signalling management. o Exposing mobility state to mobile nodes and network nodes: define solutions that allow, for example, mobile nodes to select either a care-of address or a home address depending on an application' mobility needs. In order to enable this functionality, the network-side control functions and other networking nodes must also be able to exchange appropriate control information, as well as to the mobile nodes and their applications. The working group may decide to extend the current milestones based on the new information and knowledge gained during working on other documents listed in the initial milestones. Possible new documents and milestones must still fit into the overall DMM charter scope as outlined above. Goals and Milestones: Feb 2015 - Submit 'Enhanced mobility anchoring' as a working group document. Feb 2015 - Submit 'Forwarding path and signaling management' as a working group document. May 2015 - Submit 'Exposing mobility state to mobile nodes and network nodes' as a working group document(s). Nov 2015 - Submit 'Enhanced mobility anchoring' submitted to the IESG. Nov 2015 - Submit 'Forwarding path and signaling management' submitted to the IESG. Feb 2016 - Submit 'Exposing mobility state to mobile nodes and network nodes' submitted to the IESG. Internet-Drafts: - Distributed Mobility Management: Current Practices and Gap Analysis [draft-ietf-dmm-best-practices-gap-analysis-09] (34 pages) - Requirements for Distributed Mobility Management [draft-ietf-dmm-requirements-17] (24 pages) Requests for Comments: RFC7333: Requirements for Distributed Mobility Management (24 pages) * Replaces DRAFT-CHAN-DMM-REQUIREMENTS * Normative Reference BCP14 * Informative Reference RFC3753 * Normative Reference RFC2119 * Informative Reference RFC5380 * Informative Reference DRAFT-YOKOTA-DMM-SCENARIO * Informative Reference RFC6705 * Informative Reference RFC6275 * Informative Reference RFC5213 * Informative Reference RFC5944 * Informative Reference DRAFT-WAKIKAWA-NETEXT-PMIP-CP-UP-SEPARATION * Informative Reference RFC6301 * Informative Reference RFC6224 * Informative Reference DRAFT-BHANDARI-DHC-CLASS-BASED-PREFIX * Informative Reference DRAFT-KORHONEN-6MAN-PREFIX-PROPERTIES * Informative Reference RFC6909 * Informative Reference DRAFT-BERNARDOS-DMM-CMIP * Informative Reference DRAFT-BERNARDOS-DMM-PMIP * Informative Reference DRAFT-BERNARDOS-DMM-DISTRIBUTED-ANCHORING * Normative Reference RFC7429 * Informative Reference DRAFT-VONHUGO-EACP-HETNET * Normative Reference DRAFT-XUAN-DMM-NEMO-DMM * Informative Reference DRAFT-SUN-DMM-USE-CASE-ANALYSIS-FLOWMOB-DMM * Normative Reference DRAFT-WEI-DMM-ADDRESS-MANAGEMENT * Normative Reference DRAFT-YHKIM-DMM-ENHANCED-ANCHORING * Normative Reference DRAFT-WT-DMM-FPC-CPDP RFC7429: Distributed Mobility Management: Current Practices and Gap Analysis (34 pages) * Replaces DRAFT-LIU-DMM-BEST-PRACTICES-GAP-ANALYSIS * Informative Reference RFC5380 * Informative Reference RFC4555 * Informative Reference RFC5996 * Informative Reference RFC4960 * Informative Reference RFC5568 * Informative Reference RFC5213 * Informative Reference RFC4067 * Informative Reference RFC4066 * Informative Reference DRAFT-IETF-NETEXT-PMIP-CP-UP-SEPARATION * Informative Reference RFC4295 * Normative Reference RFC7333 * Informative Reference RFC5026 * Informative Reference RFC6611 * Informative Reference RFC6224 * Informative Reference RFC5142 * Informative Reference RFC5844 * Informative Reference RFC6275 * Informative Reference RFC6705 * Informative Reference RFC6724 * Informative Reference RFC6463 * Informative Reference RFC3963 * Informative Reference RFC6097 * Informative Reference DRAFT-KORHONEN-6MAN-PREFIX-PROPERTIES * Informative Reference RFC4640 * Informative Reference RFC5555 * Informative Reference DRAFT-GUNDAVELLI-V6OPS-COMMUNITY-WIFI-SVCS * Informative Reference DRAFT-ANIPKO-MIF-MPVD-ARCH * Informative Reference RFC6475 * Informative Reference RFC6697 * Informative Reference RFC7028 * Informative Reference RFC6241 * Informative Reference RFC4889 * Informative Reference RFC5014 * Informative Reference RFC4225 * Informative Reference DRAFT-BHANDARI-DHC-CLASS-BASED-PREFIX * Informative Reference RFC6020 * Informative Reference DRAFT-BERNARDOS-DMM-PMIP * Informative Reference DRAFT-BERNARDOS-DMM-DISTRIBUTED-ANCHORING * Informative Reference DRAFT-BERNARDOS-DMM-CMIP * Normative Reference DRAFT-CHAN-DMM-DISTRIBUTED-MOBILITY-ANCHORING * Normative Reference DRAFT-WT-DMM-FPC-CPDP DNS PRIVate Exchange (dprive) ----------------------------- Charter Last Modified: 2014-10-17 Current Status: Active Chairs: Tim Wicinski Warren Kumari Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Brian Haberman Mailing Lists: General Discussion: dns-privacy@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/dns-privacy Archive: http://www.ietf.org/mail-archive/web/dns-privacy/ Description of Working Group: The DNS PRIVate Exchange (DPRIVE) Working Group develops mechanisms to provide confidentiality to DNS transactions, to address concerns surrounding pervasive monitoring (RFC 7258). The set of DNS requests that an individual makes can provide an attacker with a large amount of information about that individual. DPRIVE aims to deprive the attacker of this information. (The IETF defines pervasive monitoring as an attack [RFC7258]) The primary focus of this Working Group is to develop mechanisms that provide confidentiality between DNS Clients and Iterative Resolvers, but it may also later consider mechanisms that provide confidentiality between Iterative Resolvers and Authoritative Servers, or provide end-to-end confidentiality of DNS transactions. Some of the results of this working group may be experimental. The Working Group will also develop an evaluation document to provide methods for measuring the performance against pervasive monitoring; and how well the goal is met. The Working Group will also develop a document providing example assessments for common use cases. DPRIVE is chartered to work on mechanisms that add confidentiality to the DNS. While it may be tempting to solve other DNS issues while adding confidentiality, DPRIVE is not the working group to do this. DPRIVE will not work on any integrity-only mechanisms. Examples of the sorts of risks that DPRIVE will address can be found in [draft-bortzmeyer-dnsop-dns-privacy], and include both passive wiretapping and more active attacks, such as MITM attacks. DPRIVE will address risks to end-users' privacy (for example, which websites an end user is accessing). Some of the main design goals (in no particular order) are: - Provide confidentiality to DNS transactions (for the querier). - Maintain backwards compatibility with legacy DNS implementations. - Require minimal application-level changes. - Require minimal additional configuration or effort from applications or users Goals and Milestones: Dec 2014 - WG LC on an problem statement document Mar 2015 - WG selects one or more primary protocol directions Jul 2015 - WG LC on primary protocol directions Internet-Drafts: - DNS privacy considerations [draft-bortzmeyer-dnsop-dns-privacy-02] (12 pages) - DNS privacy considerations [draft-ietf-dprive-problem-statement-03] (16 pages) No Requests for Comments Dynamic Host Configuration (dhc) -------------------------------- Charter Last Modified: 2014-05-21 Current Status: Active Chairs: Bernie Volz Tomek Mrugalski Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Secretary: Sheng Jiang Mailing Lists: General Discussion: dhcwg@ietf.org To Subscribe: http://www.ietf.org/mailman/listinfo/dhcwg Archive: http://www.ietf.org/mail-archive/web/dhcwg/ Description of Working Group: The Dynamic Host Configuration working group (DHC WG) has developed DHCP for automated allocation, configuration and management of IP addresses and TCP/IP protocol stack parameters. DHCPv4 is currently a Draft Standard and is documented in RFC 2131 and RFC 2132. DHCPv6 is currently a Proposed Standard and is documented in RFC 3315. Subsequent RFCs document additional options and other enhancements to the specifications. The DHC WG is responsible for defining DHCP protocol extensions. Definitions of new DHCP options that are delivered using standard mechanisms with documented semantics are not considered a protocol extension and thus are outside of scope for the DHC WG. Such options should be defined within their respective WGs and reviewed by DHCP experts in the Internet Area Directorate. However, if such options require protocol extensions or new semantics, the protocol extension work must be done in the DHC WG. The DHC WG has the following main objectives: 1. Develop extensions to the DHCPv6 infrastructure as required to meet new applications and deployments of DHCP. The topics currently in development are: - DHCPv6 Stateful issues - DHCPv6 Failover - DHCPv6 Load Balancing - Extending DHCPv6 to work with multiple provisioning domains - DHCP provisioning of IPv4 clients over IPv6 networks - Access Network Identifier options - DNS registration for SLAAC - Active leasequery - Secure DHCPv6 with Public Key - Dynamic Allocation of Shared IPv4 Addresses Additional topics may only be added with approval from the responsible Area Director or by re-chartering. 2. Develop documents that help explain operational considerations for the wider community. 3. Issue updated versions of the DHCP base specifications-- RFC 3315 (DHCPv6), RFC 3633 (DHCPv6 Prefix Delegation) and RFC 3736 (Stateless DHCPv6) so as to fix errata and bring the documents to the point where they can advance along the IETF Standards Track. 4. In the process of updating the DHCP base specifications, in cases where time is of the essence, issue corrections and clarifications of the specifications in order to quickly address interoperability problems. 5. Write analyses and interoperability reports on existing DHC documents, including base specs. 6. When serious interoperability problems are found in other DHCP specifications, issue updated versions of those specifications to address the interoperability problems. Goals and Milestones: Done - WG last call draft-ietf-dhc-dhcpv6-stateful-issues Done - WG last call on access-network-identifier Done - Submit stateful issues draft to IESG Jan 2015 - WG last calll on draft-ietf-dhc-addr-registration Jan 2015 - Submit dhc-sedhcpv6 draft to IESG Feb 2015 - Submit access-network-identifier to IESG Done - Adopt 3315bis draft Mar 2015 - Submit draft-ietf-dhc-addr-registration to IESG Mar 2015 - WG last call revised draft-ietf-dhc-dhcpv6-failover-design Mar 2015 - WG last call draft-ietf-dhc-stable-privacy-addresses Apr 2015 - WG last call draft-ietf-dhc-topo-conf May 2015 - Submit dhcpv6-failover-design to IESG May 2015 - Submit draft-ietf-dhc-topo-conf to IESG Jun 2015 - Submit stable-privacy-addresses to IESG Jul 2015 - Recharter, if needed Jan 2016 - WG last call on 331bis draft Apr 2016 - Submit 3315bis draft to IESG Internet-Drafts: - Access-Network-Identifier Option in DHCP [draft-bhandari-dhc-access-network-identifier-04] (17 pages) - Dynamic Allocation of Shared IPv4 Addresses [draft-csf-dhc-dynamic-shared-v4allocation-00] (13 pages) - Handling Unknown DHCPv6 Messages [draft-csl-dhc-dhcpv6-unknown-msg-3315update-00] (4 pages) - Dynamic Host Configuration Protocol for IPv6 (DHCPv6) bis [draft-dhcwg-dhc-rfc3315bis-04] (126 pages) - A Method for Generating Semantically Opaque Interface Identifiers with Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [draft-gont-dhc-stable-privacy-addresses-01] (8 pages) - Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4) [draft-ietf-dhc-3315id-for-v4-05] (12 pages) - IEEE 802.11 parameters DHCP Option [draft-ietf-dhc-80211-option-01] (5 pages) - Triggering AAA from DHCP Relay Agents [draft-ietf-dhc-aaa-ra-00] (7 pages) - Authentication, Authorization, and Accounting Requirements for Roaming Nodes using DHCP [draft-ietf-dhc-aaa-requirements-00] (8 pages) - Access Network Identifier Option in DHCP [draft-ietf-dhc-access-network-identifier-06] (19 pages) - Registering Self-generated IPv6 Addresses in DNS using DHCPv6 [draft-ietf-dhc-addr-registration-07] (10 pages) - DHCP Relay Agent Information Option [draft-ietf-dhc-agent-options-11] (14 pages) - Link Selection sub-option for the Relay Agent Information Option for DHCPv4 [draft-ietf-dhc-agent-subnet-selection-04] (9 pages) - Virtual Subnet Selection Sub-Option for the Relay Agent Information Option for DHCPv4 [draft-ietf-dhc-agent-vpn-id-06] (11 pages) - Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option [draft-ietf-dhc-agentopt-radius-08] (8 pages) - The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-option [draft-ietf-dhc-agentoptions-device-class-04] (5 pages) - The Autonomous System Option for DHCP [draft-ietf-dhc-asnum-00] (5 pages) - DHCP RSA/DSA Authentication using DNS KEY records [draft-ietf-dhc-auth-sigzero-00] (0 pages) - The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option [draft-ietf-dhc-auth-suboption-05] (15 pages) - Authentication for DHCP Messages [draft-ietf-dhc-authentication-16] (17 pages) - DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients [draft-ietf-dhc-autoconfig-04] (9 pages) - Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers [draft-ietf-dhc-bcmc-options-05] (11 pages) - DHCPv4 Options for Broadcast and Multicast Control Servers [draft-ietf-dhc-bcmcv4-option-00] (12 pages) - DHCPv6 Options for Broadcast and Multicast Control Servers [draft-ietf-dhc-bcmcv6-option-00] (14 pages) - Interoperation Between DHCP and BOOTP [draft-ietf-dhc-between-bootp-02] (4 pages) - Clarifications and Extensions for the Bootstrap Protocol [draft-ietf-dhc-bootp-01] (22 pages) - DHCP Options for Call Control Servers [draft-ietf-dhc-callcontrolserv-00] (4 pages) - Configuring Cryptographically Generated Addresses (CGA) using DHCPv6 [draft-ietf-dhc-cga-config-dhcpv6-04] (10 pages) - Client Identifier Option in DHCP Server Replies [draft-ietf-dhc-client-id-07] (5 pages) - Interpreting Client Options for the Dynamic Host Configuration Protocol [draft-ietf-dhc-client-options-00] (24 pages) - Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4) [draft-ietf-dhc-concat-05] (9 pages) - IP Connectivity Status Notifications for DHCPv6 [draft-ietf-dhc-conn-status-00] (10 pages) - Container Option for Server Configuration [draft-ietf-dhc-container-opt-07] (9 pages) - The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4 [draft-ietf-dhc-csr-07] (9 pages) - Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients [draft-ietf-dhc-ddns-resolution-12] (13 pages) - Dynamic Host Configuration Protocol [draft-ietf-dhc-dhcp-08] (45 pages) - Interaction between DHCP and DNS [draft-ietf-dhc-dhcp-dns-12] (19 pages) - Privacy considerations for DHCP [draft-ietf-dhc-dhcp-privacy-00] (13 pages) - Dynamic Host Configuration Protocol DHCPINFORM Message Clarifications [draft-ietf-dhc-dhcpinform-clarify-06] (9 pages) - Extensions to DHCP for Roaming Users [draft-ietf-dhc-dhcproam-00] (15 pages) - Active DHCPv4 Lease Query [draft-ietf-dhc-dhcpv4-active-leasequery-02] (24 pages) - DHCPv4 Bulk Leasequery [draft-ietf-dhc-dhcpv4-bulk-leasequery-07] (41 pages) - DHCPv4-over-DHCPv6 (DHCP 4o6) Transport [draft-ietf-dhc-dhcpv4-over-dhcpv6-09] (16 pages) - DHCPv4 over IPv6 Transport [draft-ietf-dhc-dhcpv4-over-ipv6-09] (14 pages) - DHCPv4 Vendor-specific Message [draft-ietf-dhc-dhcpv4-vendor-message-01] (7 pages) - Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [draft-ietf-dhc-dhcpv6-28] (101 pages) - DHCPv6 Active Leasequery [draft-ietf-dhc-dhcpv6-active-leasequery-02] (28 pages) - DHCPv6 Relay Agent Assignment Notification (RAAN) Option [draft-ietf-dhc-dhcpv6-agentopt-delegate-04] (8 pages) - DHCPv6 Bulk Leasequery [draft-ietf-dhc-dhcpv6-bulk-leasequery-06] (18 pages) - Clarifications on DHCPv6 Authentication [draft-ietf-dhc-dhcpv6-clarify-auth-01] (14 pages) - Client Link-Layer Address Option in DHCPv6 [draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-05] (7 pages) - Configured Tunnel End Point Option for DHCPv6 [draft-ietf-dhc-dhcpv6-ctep-opt-02] (6 pages) - DHCPv6 Relay Agent Echo Request Option [draft-ietf-dhc-dhcpv6-ero-01] (6 pages) - DHCPv6 Failover Design [draft-ietf-dhc-dhcpv6-failover-design-04] (59 pages) - DHCPv6 Failover Requirements [draft-ietf-dhc-dhcpv6-failover-requirements-07] (17 pages) - The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option [draft-ietf-dhc-dhcpv6-fqdn-05] (15 pages) - Results from Interoperability Tests of DHCPv6 Implementations [draft-ietf-dhc-dhcpv6-interop-01] (12 pages) - Lightweight DHCPv6 Relay Agent [draft-ietf-dhc-dhcpv6-ldra-03] (17 pages) - DHCPv6 Leasequery [draft-ietf-dhc-dhcpv6-leasequery-01] (23 pages) - Load Balancing for DHCPv6 [draft-ietf-dhc-dhcpv6-load-balancing-02] (6 pages) - Load Balancing for DHCPv6 [draft-ietf-dhc-dhcpv6-loadb-02] (6 pages) - Client Preferred Prefix option for DHCPv6 [draft-ietf-dhc-dhcpv6-opt-cliprefprefix-01] (6 pages) - DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [draft-ietf-dhc-dhcpv6-opt-dnsconfig-04] (7 pages) - Domain Suffix Option for DHCPv6 [draft-ietf-dhc-dhcpv6-opt-dnsdomain-04] (7 pages) - DSTM Options for DHCPv6 [draft-ietf-dhc-dhcpv6-opt-dstm-01] (7 pages) - DSTM Ports Option for DHCPv6 [draft-ietf-dhc-dhcpv6-opt-dstm-ports-01] (4 pages) - DHCPv6 Options for Network Boot [draft-ietf-dhc-dhcpv6-opt-netboot-10] (11 pages) - Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [draft-ietf-dhc-dhcpv6-opt-nisconfig-05] (7 pages) - The Name Service Search Option for DHCPv6 [draft-ietf-dhc-dhcpv6-opt-nss-00] (6 pages) - IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6 [draft-ietf-dhc-dhcpv6-opt-prefix-delegation-05] (19 pages) - DHCPv6 Support for Remote Boot [draft-ietf-dhc-dhcpv6-opt-rboot-00] (6 pages) - Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6 [draft-ietf-dhc-dhcpv6-opt-sntp-01] (5 pages) - Time Configuration Options for DHCPv6 [draft-ietf-dhc-dhcpv6-opt-timeconfig-03] (8 pages) - Timezone Specifier Option for DHCPv6 [draft-ietf-dhc-dhcpv6-opt-tz-00] (6 pages) - Prefix Pool Option for DHCPv6 Relay Agent on the Provider Edge Routers [draft-ietf-dhc-dhcpv6-prefix-pool-opt-03] (13 pages) - Privacy considerations for DHCPv6 [draft-ietf-dhc-dhcpv6-privacy-00] (14 pages) - RADIUS Option for the DHCPv6 Relay Agent [draft-ietf-dhc-dhcpv6-radius-opt-14] (10 pages) - Rebind Capability in DHCPv6 Reconfigure Messages [draft-ietf-dhc-dhcpv6-reconfigure-rebind-10] (10 pages) - DHCPv6 Redundancy Deployment Considerations [draft-ietf-dhc-dhcpv6-redundancy-consider-03] (16 pages) - Relay-Supplied DHCP Options [draft-ietf-dhc-dhcpv6-relay-supplied-options-09] (8 pages) - Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option [draft-ietf-dhc-dhcpv6-remoteid-01] (6 pages) - Time Protocol Servers and Time Offset Options for IPv6 DHCP [draft-ietf-dhc-dhcpv6-rfc868-servers-00] (6 pages) - Modification to Default Values of SOL_MAX_RT and INF_MAX_RT [draft-ietf-dhc-dhcpv6-solmaxrt-update-05] (7 pages) - DHCPv6 Server Reply Sequence Number Option [draft-ietf-dhc-dhcpv6-srsn-option-02] (7 pages) - Issues and Recommendations with Multiple Stateful DHCPv6 Options [draft-ietf-dhc-dhcpv6-stateful-issues-11] (23 pages) - Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6 [draft-ietf-dhc-dhcpv6-stateless-04] (9 pages) - Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option [draft-ietf-dhc-dhcpv6-subid-01] (6 pages) - DHCPv6 through Tunnels [draft-ietf-dhc-dhcpv6-tunnel-01] (5 pages) - Handling Unknown DHCPv6 Messages [draft-ietf-dhc-dhcpv6-unknown-msg-08] (7 pages) - DHCPv6 Vendor-specific Message [draft-ietf-dhc-dhcpv6-vendor-message-01] (6 pages) - Extensions for the Dynamic Host Configuration Protocol for IPv6 [draft-ietf-dhc-dhcpv6exts-12] (39 pages) - DHCPv6 Leasequery [draft-ietf-dhc-dhcvp6-leasequery-01] (21 pages) - Detecting Network Attachment in IPv4 (DNAv4) [draft-ietf-dhc-dna-ipv4-18] (15 pages) - Populating the DNS Reverse Tree for DHCP Delegated Prefixes [draft-ietf-dhc-dns-pd-01] (13 pages) - The Domain Search Option for DHCP [draft-ietf-dhc-domsrch-02] (4 pages) - Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack Issues [draft-ietf-dhc-dual-stack-04] (14 pages) - Dual-stack clients and merging of data from DHCPv4 and DHCPv6 [draft-ietf-dhc-dual-stack-merge-01] (8 pages) - Definition of the UUID-Based DHCPv6 Unique Identifier (DUID-UUID) [draft-ietf-dhc-duid-uuid-03] (5 pages) - Subnet Configuration Option Set for DHCP [draft-ietf-dhc-dyn-subnet-conf-02] (14 pages) - Dynamic Allocation of Shared IPv4 Addresses [draft-ietf-dhc-dynamic-shared-v4allocation-05] (13 pages) - Requirements for Extending DHCP into New Environments [draft-ietf-dhc-enhance-requirements-00] (15 pages) - Extending DHCP Options Codes [draft-ietf-dhc-extended-optioncodes-00] (9 pages) - DHCP Failover Protocol [draft-ietf-dhc-failover-12] (133 pages) - Forcerenew Nonce Authentication [draft-ietf-dhc-forcerenew-nonce-07] (12 pages) - An option for FQDNs in DHCP options [draft-ietf-dhc-fqdn-opt-03] (4 pages) - The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option [draft-ietf-dhc-fqdn-option-13] (17 pages) - Prefix Assignment in DHCPv6 [draft-ietf-dhc-host-gen-id-05] (11 pages) - Considerations for the use of the Host Name option [draft-ietf-dhc-host-option-considerations-02] (8 pages) - Implementation Issues with RFC 2131, "Dynamic Host Configuration Protocol (DHCPv4)" [draft-ietf-dhc-implementation-02] (41 pages) - An Inter-server Protocol for DHCP [draft-ietf-dhc-interserver-02] (89 pages) - An Inter-server Protocol for DHCP [draft-ietf-dhc-interserver-alt-00] (53 pages) - Automatically Choosing an IP Address in an Ad-Hoc IPv4 Network [draft-ietf-dhc-ipv4-autoconfig-05] (8 pages) - The IPv4 Dynamic Host Configuration Protocol (DHCP) Option for the Internet Storage Name Service [draft-ietf-dhc-isnsoption-13] (13 pages) - Wireless Key Management using DHCP [draft-ietf-dhc-key-management-00] (0 pages) - Layer 2 Relay Agent Information [draft-ietf-dhc-l2ra-06] (13 pages) - Extensions to Layer 2 Relay Agent [draft-ietf-dhc-l2ra-extensions-01] (22 pages) - LDAP Schema for DHCP [draft-ietf-dhc-ldap-schema-00] (18 pages) - Dynamic Host Configuration Protocol (DHCP) Leasequery [draft-ietf-dhc-leasequery-09] (27 pages) - DHCPv4 Lease Query by Relay Agent Remote ID [draft-ietf-dhc-leasequery-by-remote-id-09] (13 pages) - Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [draft-ietf-dhc-lifetime-03] (8 pages) - DHC Load Balancing Algorithm [draft-ietf-dhc-loadb-03] (10 pages) - Multicast address allocation extensions to the Dynamic Host Configuration Protocol [draft-ietf-dhc-mdhcp-03] (14 pages) - The Migration Agent List Option for DHCP [draft-ietf-dhc-migagntlist-00] (4 pages) - DHCP Option for Mobile IP Mobility Agents [draft-ietf-dhc-mipadvert-opt-02] (15 pages) - Multicast Address Allocation Configuration Options [draft-ietf-dhc-multopt-03] (5 pages) - The Named Pool Request Option for DHCP [draft-ietf-dhc-namedpool-00] (4 pages) - NetWare/IP Domain Name and Information [draft-ietf-dhc-netware-options-00] (6 pages) - Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types [draft-ietf-dhc-new-opt-msg-02] (7 pages) - New Option Review Guidelines for DHCP [draft-ietf-dhc-new-opt-review-00] (8 pages) - Procedure for Defining New DHCP Options [draft-ietf-dhc-new-options-05] (5 pages) - DHCP Next Server Option [draft-ietf-dhc-nextserver-02] (0 pages) - The Name Service Search Option for DHCP [draft-ietf-dhc-nsso-05] (5 pages) - The Extended Remote Boot Option for DHCPv4 [draft-ietf-dhc-opt-extrboot-00] (7 pages) - Guidelines for Creating New DHCPv6 Options [draft-ietf-dhc-option-guidelines-17] (35 pages) - New Option Review Guidelines and Additional Option Namespace [draft-ietf-dhc-option-review-and-namespace-02] (14 pages) - DHCP Options and BOOTP Vendor Extensions [draft-ietf-dhc-options-03] (30 pages) - DHCP Options and BOOTP Vendor Extensions [draft-ietf-dhc-options-1533update-05] (34 pages) - DHCP Continuation Option Code [draft-ietf-dhc-options-cont-01] (3 pages) - An Extension to the DHCP Option Codes [draft-ietf-dhc-options-opt127-03] (3 pages) - DHCP Option for The Open Group's User Authentication Protocol [draft-ietf-dhc-options-uap-02] (4 pages) - DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication Agents [draft-ietf-dhc-paa-option-05] (8 pages) - Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration [draft-ietf-dhc-packetcable-06] (13 pages) - Prefix Exclude Option for DHCPv6-based Prefix Delegation [draft-ietf-dhc-pd-exclude-04] (10 pages) - PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) Option [draft-ietf-dhc-pktc-kerb-tckt-03] (7 pages) - Dynamic Configuration of Internet Hosts [draft-ietf-dhc-problem-stmt-00] (0 pages) - Dynamic Host Configuration Protocol [draft-ietf-dhc-protocol-06] (39 pages) - DHCP Option for Proxy Server Configuration [draft-ietf-dhc-proxyserver-opt-05] (8 pages) - DHCP reconfigure extension [draft-ietf-dhc-pv4-reconfigure-06] (6 pages) - Dynamic Host Configuration Protocol (DHCP) Options for the Intel Preboot eXecution Environment (PXE) [draft-ietf-dhc-pxe-options-03] (7 pages) - Dynamic Host Configuration Protocol Options Used by PXELINUX [draft-ietf-dhc-pxelinux-03] (14 pages) - The Server Range Option for DHCP [draft-ietf-dhc-range-00] (2 pages) - Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4) [draft-ietf-dhc-rapid-commit-opt-05] (10 pages) - Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options [draft-ietf-dhc-reclassify-options-01] (7 pages) - The Authentication Suboption for the DHCP Relay Agent Option [draft-ietf-dhc-relay-agent-auth-01] (16 pages) - The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption [draft-ietf-dhc-relay-agent-flags-03] (7 pages) - Authentication of DHCP Relay Agent Options Using IPsec [draft-ietf-dhc-relay-agent-ipsec-02] (10 pages) - The DHCPv4 Relay Agent Identifier Sub-Option [draft-ietf-dhc-relay-id-suboption-13] (8 pages) - Graceful renumbering of networks with DHCP [draft-ietf-dhc-renumbering-00] (8 pages) - DHCP Safe Failover Protocol [draft-ietf-dhc-safe-failover-proto-00] (29 pages) - DHCP Schema for LDAP [draft-ietf-dhc-schema-02] (23 pages) - Secure DHCPv6 Using CGAs [draft-ietf-dhc-secure-dhcpv6-07] (18 pages) - Securing DHCP [draft-ietf-dhc-securing-dhc-00] (5 pages) - Security Architecture for DHCP [draft-ietf-dhc-security-arch-01] (14 pages) - Security Requirements for the DHCP protocol [draft-ietf-dhc-security-requirements-00] (12 pages) - Secure DHCPv6 [draft-ietf-dhc-sedhcpv6-06] (23 pages) - Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Server MIB [draft-ietf-dhc-server-mib-10] (37 pages) - DHCP Server Identifier Override Suboption [draft-ietf-dhc-server-override-05] (7 pages) - The Server Identification Option for DHCP [draft-ietf-dhc-sio-00] (6 pages) - DHCP Options for Service Location Protocol [draft-ietf-dhc-slp-07] (6 pages) - Service-Oriented Address Assignment using DHCPv6 [draft-ietf-dhc-soa-option-00] (9 pages) - The Server Selection Option for DHCP [draft-ietf-dhc-sso-03] (14 pages) - A Method for Generating Semantically Opaque Interface Identifiers with Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [draft-ietf-dhc-stable-privacy-addresses-01] (9 pages) - Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [draft-ietf-dhc-stateless-dhcpv6-renumbering-02] (8 pages) - Description of Cisco Systems' Subnet Allocation Option for DHCPv4 [draft-ietf-dhc-subnet-alloc-13] (24 pages) - The IPv4 Subnet Selection Option for DHCP [draft-ietf-dhc-subnet-option-07] (7 pages) - Key Distribution Center (KDC) Server Address Sub-option for the Dynamic Host Configuration Protocol (DHCP) CableLabs Client Configuration (CCC) Option [draft-ietf-dhc-suboptions-kdc-serveraddress-04] (7 pages) - Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option [draft-ietf-dhc-subscriber-id-07] (7 pages) - Subnet Selection Option for DHCP [draft-ietf-dhc-subsel-00] (5 pages) - DHCP Option for IEEE 1003.1 POSIX Timezone Specifications [draft-ietf-dhc-timezone-03] (3 pages) - Timezone Options for DHCP [draft-ietf-dhc-timezone-option-05] (10 pages) - Customizing DHCP Configuration on the Basis of Network Topology [draft-ietf-dhc-topo-conf-04] (17 pages) - Triggering DHCPv6 Reconfiguration from Relay Agents [draft-ietf-dhc-triggered-reconfigure-07] (13 pages) - Unused Dynamic Host Configuration Protocol (DHCP) Option Codes [draft-ietf-dhc-unused-optioncodes-07] (8 pages) - DHCP Use of the User Class Option for Address Assignment [draft-ietf-dhc-useraddr-00] (5 pages) - The User Class Option for DHCP [draft-ietf-dhc-userclass-10] (6 pages) - Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Threat Analysis [draft-ietf-dhc-v4-threat-analysis-03] (20 pages) - Provisioning IPv4 Configuration Over IPv6 Only Networks [draft-ietf-dhc-v4configuration-06] (17 pages) - DHCPv6 Relay agent RADIUS Attribute Option [draft-ietf-dhc-v6-relay-radius-02] (12 pages) - Options for DHCPv6 [draft-ietf-dhc-v6opts-00] (15 pages) - Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4) [draft-ietf-dhc-vendor-03] (9 pages) - Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option [draft-ietf-dhc-vendor-suboption-00] (7 pages) - Virtual Subnet Selection Options for DHCPv4 and DHCPv6 [draft-ietf-dhc-vpn-option-15] (26 pages) - Privacy considerations for DHCP [draft-jiang-dhc-dhcp-privacy-00] (12 pages) - Secure DHCPv6 with Public Key [draft-jiang-dhc-sedhcpv6-02] (16 pages) - Privacy considerations for DHCPv6 [draft-krishnan-dhc-dhcpv6-privacy-00] (14 pages) - Customizing DHCP Configuration on the Basis of Network Topology [draft-lemon-dhc-topo-conf-01] (9 pages) - DHCP Options for Novell Directory Services [draft-provan-dhcp-options-dir-serv-01] (5 pages) - Provisioning IPv4 Configuration Over IPv6 Only Networks [draft-rajtar-dhc-v4configuration-02] (13 pages) - DHCPv4 over DHCPv6 Transport [draft-scskf-dhc-dhcpv4-over-dhcpv6-01] (8 pages) - DHCPv6 Dynamic Reconfiguration [draft-wing-dhc-dns-reconfigure-02] (9 pages) Requests for Comments: BCP180: DHCPv6 Redundancy Deployment Considerations (16 pages) * Replaces DRAFT-JJMB-DHC-DHCPV6-REDUNDANCY-CONSIDER * Normative Reference RFC5460 * Normative Reference RFC3736 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference RFC4704 * Normative Reference RFC5007 * Normative Reference RFC3633 * Normative Reference RFC4701 * Normative Reference RFC5970 * Normative Reference RFC2136 * Normative Reference RFC4703 * Informative Reference RFC7031 * Informative Reference DRAFT-ZHANG-DHC-DHCPV6-FAILURE-DETECTION BCP187: Guidelines for Creating New DHCPv6 Options (35 pages) * Informative Reference RFC6440 * Informative Reference RFC5970 * Informative Reference RFC3319 * Informative Reference RFC3986 * Informative Reference RFC3646 * Informative Reference RFC4242 * Normative Reference RFC3315 * Informative Reference STD66 * Informative Reference STD63 * Informative Reference RFC6644 * Normative Reference RFC2119 * Informative Reference RFC4436 * Informative Reference RFC6603 * Informative Reference RFC5460 * Informative Reference RFC3898 * Informative Reference RFC6059 * Informative Reference RFC6610 * Informative Reference RFC3633 * Informative Reference RFC5007 * Possible Reference RFC5741 * Informative Reference RFC3046 * Informative Reference RFC5908 * Informative Reference RFC6334 * Informative Reference RFC4085 * Informative Reference RFC4303 * Informative Reference RFC4833 * Informative Reference RFC4957 * Informative Reference RFC5986 * Informative Reference RFC5223 * Normative Reference BCP14 * Informative Reference RFC4704 * Informative Reference BCP105 * Informative Reference RFC5198 * Informative Reference RFC4075 * Informative Reference RFC2460 * Informative Reference RFC6422 * Informative Reference RFC4280 * Informative Reference RFC3629 * Updates RFC3315 * Normative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Normative Reference DRAFT-WKUMARI-DHC-CAPPORT * Normative Reference DRAFT-XUE-DHC-DYNAMIC-GRE * Informative Reference DRAFT-IETF-ROLL-MPL-PARAMETER-CONFIGURATION * Informative Reference DRAFT-IETF-DHC-DHCPV6-STATEFUL-ISSUES * Informative Reference DRAFT-IETF-SOFTWIRE-MAP-DHCP * Reference DRAFT-CROCKER-RFC2418BIS-WGGUIDELINES BCP29: Procedure for Defining New DHCP Options (5 pages) * Reference RFC2434 * Reference RFC2142 * Reference RFC2132 * Reference BCP26 * Reference RFC2131 BCP43: Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types (7 pages) * Obsoletes RFC2489 * Reference RFC2489 * Reference RFC2434 * Reference RFC2142 * Reference RFC2132 * Reference BCP26 * Reference RFC2131 * Informative Reference DRAFT-LEVKOWETZ-DHC-MIP-FA * Informative Reference DRAFT-IETF-DHC-MIPADVERT-OPT * Reference DRAFT-HUSTON-IANA * Informative Reference RFC3679 * Reference DRAFT-LITTLEFIELD-DHCP-VENDOR * Normative Reference RFC4578 * Informative Reference RFC3925 * Informative Reference DRAFT-SENTHIL-DHC-PROXYSERVER-OPT * Informative Reference RFC4039 * Normative Reference RFC3942 * Normative Reference DRAFT-DANIEL-DHC-IPV6IN4-OPT * Informative Reference DRAFT-IETF-DHC-PROXYSERVER-OPT * Informative Reference DRAFT-CADAR-DHC-OPT-IMAP * Informative Reference RFC5226 * Informative Reference DRAFT-KLENSIN-IANA-REG-POLICY * Normative Reference DRAFT-LEAR-DHC-TIMEZONE-OPTION * Normative Reference RFC4833 * Normative Reference DRAFT-DANIEL-DHC-MIHIS-OPT * Normative Reference RFC5071 * Normative Reference RFC6225 * Normative Reference DRAFT-SHEFFER-DHC-INITIAL-RANDOM * Normative Reference RFC6011 * Informative Reference DRAFT-SAINTANDRE-XDASH * Informative Reference RFC6648 * Normative Reference DRAFT-BHANDARI-DHC-ACCESS-NETWORK-IDENTIFIER * Informative Reference DRAFT-LEIBA-COTTON-IANA-5226BIS * Normative Reference DRAFT-HALWASIA-DHC-INFORM-REFRESH-TIME-OPT * Informative Reference DRAFT-IETF-DHC-ACCESS-NETWORK-IDENTIFIER * Normative Reference DRAFT-ORR-DHCP-DNS-SD-OPTIONS RFC1531: Dynamic Host Configuration Protocol (39 pages) * Reference RFC887 * Reference RFC1191 * Reference RFC783 * Reference RFC903 * Reference RFC1497 * Reference RFC951 * Reference RFC1532 * Reference RFC1534 * Reference RFC1256 * Reference RFC1533 * Reference RFC1034 * Reference STD13 * Reference STD5 * Possible Reference RFC1395 * Reference RFC894 * Reference STD3 * Obsoletes RFC1541 * Reference RFC1532 * Reference RFC1533 * Reference RFC1534 * Reference DRAFT-IETF-SIPP-IPAE-TRANSITION * Possible Reference DRAFT-IETF-TUBA-TRANSITION * Reference DRAFT-IETF-IPSEC-SKIP * Reference DRAFT-IETF-DHC-RENUMBERING * Reference DRAFT-IETF-IPCDN-IPCABLEDATA-SPEC * Reference DRAFT-IETF-DHC-SECURING-DHC * Reference DRAFT-IETF-SEAMOBY-CARDISCOVERY-ISSUES * Reference DRAFT-SCHWARTZ-ANTACID-SERVICE * Possible Reference DRAFT-BAKKE-DHC-SNMP-TRAP * Reference DRAFT-RICHARDSON-IPSEC-DHCP-OVER-IKE * Possible Reference DRAFT-VOLZ-DHC-EXTENDED-OPTIONCODES * Possible Reference DRAFT-IETF-DHC-EXTENDED-OPTIONCODES * Possible Reference DRAFT-WOLLMAN-SLBRP * Normative Reference DRAFT-ZAITSEV-E6-NETWORK * Informative Reference DRAFT-TSOU-OPSAWG-NETWORK-CONFIGURATION * Reference RFC1700 * Possible Reference RFC1541 RFC1532: Clarifications and Extensions for the Bootstrap Protocol (22 pages) * Updates RFC951 * Reference RFC826 * Reference RFC1497 * Reference RFC951 * Reference RFC1531 * Reference RFC1256 * Reference STD37 * Obsoletes RFC1542 * Reference RFC1531 * Reference RFC1534 * Possible Reference RFC1542 RFC1533: DHCP Options and BOOTP Vendor Extensions (30 pages) * Obsoletes RFC1048 * Obsoletes RFC1084 * Obsoletes RFC1395 * Obsoletes RFC1497 * Reference RFC1305 * Possible Reference RFC950 * Reference RFC1531 * Possible Reference RFC1122 * Reference RFC887 * Reference RFC1256 * Reference RFC951 * Possible Reference RFC1035 * Reference STD19 * Reference RFC1179 * Reference STD13 * Possible Reference RFC868 * Possible Reference RFC865 * Reference RFC1191 * Possible Reference RFC1001 * Reference STD5 * Reference STD3 * Reference STD26 * Reference RFC1497 * Reference FYI6 * Reference STD23 * Reference RFC1042 * Reference RFC893 * Reference RFC894 * Obsoletes RFC2132 * Reference RFC1531 * Reference RFC1534 * Reference RFC2131 * Reference RFC1812 * Possible Reference RFC2132 * Reference DRAFT-IETF-DHC-V6OPTS * Possible Reference DRAFT-IETF-DHC-OPTIONS-OPT127 * Possible Reference DRAFT-IETF-DHC-DHCPV6EXTS * Reference DRAFT-IETF-DHC-MDHCP * Reference DRAFT-IETF-DHC-SIO * Reference DRAFT-ANDERSON-DOCS-RF-MIB * Possible Reference RFC2626 * Reference DRAFT-RFCED-INFO-MADAN * Reference DRAFT-IETF-DHC-ASNUM * Reference DRAFT-IETF-DHC-RANGE * Normative Reference DRAFT-IETF-DHC-HOST-OPTION-CONSIDERATIONS * Possible Reference DRAFT-IETF-DHC-IMPLEMENTATION * Informative Reference DRAFT-IETF-IPSEC-DHCP-OVER-IKE * Informative Reference DRAFT-IETF-IPSEC-DHCP-OVER-IKE-DHCPD * Normative Reference DRAFT-MELIA-MIPSHOP-MSTP-SOLUTION * Reference RFC1700 * Reference RFC1541 RFC1534: Interoperation Between DHCP and BOOTP (4 pages) * Reference RFC1533 * Reference RFC1532 * Reference RFC1531 * Reference RFC1531 * Reference RFC2131 * Possible Reference RFC2626 * Reference DRAFT-IETF-DHC-FAILOVER * Reference DRAFT-IETF-DHC-ENHANCE-REQUIREMENTS * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Normative Reference RFC4173 * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Possible Reference DRAFT-IETF-DHC-IMPLEMENTATION * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Reference RFC1541 RFC2131: Dynamic Host Configuration Protocol (45 pages) * Obsoletes RFC1541 * Reference RFC887 * Reference RFC1191 * Reference RFC783 * Reference RFC903 * Reference RFC1497 * Reference RFC951 * Reference RFC1542 * Possible Reference RFC1122 * Possible Reference RFC1541 * Reference RFC1256 * Reference RFC1533 * Reference RFC1034 * Reference STD13 * Reference STD5 * Reference RFC1534 * Reference RFC894 * Reference STD3 * Updates RFC3396 * Updates RFC4361 * Updates RFC5494 * Updates RFC6842 * Reference RFC2165 * Informative Reference RFC3315 * Reference RFC2132 * Reference RFC2489 * Reference DRAFT-IETF-DHC-DHCP-DNS * Reference RFC3118 * Reference DRAFT-IETF-DHC-OPTIONS-OPT127 * Reference DRAFT-IETF-DHC-FQDN-OPT * Normative Reference DRAFT-TROAN-DHC-DHCPV4OSW * Reference RFC2610 * Reference RFC3004 * Reference RFC2241 * Reference DRAFT-IETF-DHC-TIMEZONE * Reference DRAFT-IETF-DHC-INTERSERVER * Reference RFC2338 * Reference RFC3046 * Reference DRAFT-IETF-DHC-MULTOPT * Normative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Possible Reference DRAFT-IETF-DHC-DYN-SUBNET-CONF * Reference DRAFT-IETF-DHC-SSO * Reference DRAFT-IETF-DHC-SECURITY-ARCH * Reference DRAFT-DITTERT-HOST-SYS-CHAR * Reference DRAFT-IETF-DHC-NAMEDPOOL * Reference RFC2242 * Reference DRAFT-IETF-IDR-AGGREGATION-TUTORIAL * Reference DRAFT-HARRINGTON-NGTRANS-DHCP-OPTION * Reference DRAFT-HEDSTROM-DHC-LDAP * Reference DRAFT-WATSON-DHC-SERV-VERIFY * Reference DRAFT-IETF-DHC-DOMSRCH * Reference DRAFT-IETF-DHC-SUBSEL * Reference DRAFT-IETF-IPSEC-ISAKMP-MODE-CFG * Reference DRAFT-IETF-MOBILEIP-V2 * Reference DRAFT-IETF-NGTRANS-NNAT * Reference DRAFT-IETF-DHC-FAILOVER * Reference DRAFT-IETF-DHC-OPTIONS-CONT * Reference DRAFT-OHARA-IPSECPARAM * Informative Reference RFC3456 * Reference DRAFT-IETF-IPSEC-POLICY-MODEL * Reference DRAFT-IETF-NGTRANS-ASSGN-IPV4-ADDRS * Reference DRAFT-IETF-IPP-DHCP-OPTION * Reference DRAFT-IETF-DHC-SAFE-FAILOVER-PROTO * Reference DRAFT-IETF-DHC-SECURITY-REQUIREMENTS * Informative Reference RFC4728 * Reference DRAFT-BORELLA-AATN-DNAT * Normative Reference DRAFT-IETF-DHC-SERVER-MIB * Reference RFC2855 * Reference DRAFT-MILLER-DHCP-LDAP-SCHEMA * Reference RFC2916 * Possible Reference RFC2871 * Reference RFC2563 * Possible Reference DRAFT-MILLER-DNS-LDAP-SCHEMA * Reference DRAFT-IETF-MALLOC-MDHCP * Reference DRAFT-GU-DHCP-LDAP-SCHEMA * Reference RFC2485 * Reference DRAFT-IETF-DHC-IPV4-AUTOCONFIG * Reference RFC2764 * Reference DRAFT-IETF-DHC-USERADDR * Reference DRAFT-JAWANDA-SDOW * Reference DRAFT-KHARE-NOTIFICATION * Reference DRAFT-HENRY-DHCP-OPT61-UUID-TYPE * Normative Reference DRAFT-LEMON-DHC-TOPO-CONF * Reference RFC2730 * Informative Reference RFC3768 * Reference RFC3011 * Reference DRAFT-IETF-DHC-CALLCONTROLSERV * Possible Reference DRAFT-MILLER-HOMEDISC-REQ * Possible Reference DRAFT-IETF-DNSIND-DDDD * Informative Reference DRAFT-LEMON-DHC-INVENTORY * Reference DRAFT-TOUTAIN-NGTRANS-DSTM * Reference DRAFT-TOUTAIN-DSTM * Reference DRAFT-YMBK-TERMROOM-OP * Reference RFC2937 * Reference DRAFT-MOATS-LDAP-TAXONOMY * Reference DRAFT-GUTTMAN-NITS-REQTS * Reference DRAFT-IETF-DHC-OPTION-REVIEW-AND-NAMESPACE * Reference DRAFT-IETF-WREC-WPAD * Reference DRAFT-GUPTA-DHCP-AUTH * Reference RFC3041 * Reference DRAFT-IETF-DHC-SCHEMA * Normative Reference DRAFT-SARIKAYA-DHC-VXLAN-MULTICAST * Reference DRAFT-HENRY-REMOTE-BOOT-PROTOCOL * Reference DRAFT-PRIVAT-DHC-DOUBLEPHASE * Informative Reference RFC3819 * Normative Reference DRAFT-SCSKF-DHC-DHCPV4-OVER-DHCPV6 * Reference DRAFT-ABOBA-ZEROCONF-MULTI * Possible Reference DRAFT-SCHRIJVP-DHCPV4-RECONFIGURE * Normative Reference DRAFT-IETF-NGTRANS-DSTM * Reference RFC3220 * Reference DRAFT-IETF-DHC-CLIENT-OPTIONS * Reference DRAFT-GONCZI-DHC-LOADB * Reference DRAFT-HORNSTEIN-DHC-KERBAUTH * Reference DRAFT-BORELLA-UID * Reference RFC3074 * Reference DRAFT-IETF-DNSIND-DHCP-RR * Informative Reference DRAFT-IETF-ZEROCONF-REQTS * Reference DRAFT-ITSUMO-HMMP * Reference DRAFT-ABOBA-IPSRA-REQ * Reference DRAFT-IETF-DHC-MIGAGNTLIST * Reference DRAFT-IETF-DHC-NEXTSERVER * Normative Reference RFC3442 * Reference RFC3105 * Reference DRAFT-ABOBA-DHC-MDNS-CONF * Possible Reference RFC3361 * Normative Reference DRAFT-CLEMM-NETMOD-MOUNT * Reference RFC3203 * Normative Reference RFC3495 * Reference DRAFT-SMEDVINSKY-DHC-KERBAUTH * Reference DRAFT-CHESHIRE-IPV4-LINKLOCAL * Informative Reference RFC3927 * Informative Reference RFC4795 * Reference DRAFT-ITSUMO-SIP-MOBILITY-REQ * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Reference DRAFT-ABOBA-DHC-MINI * Reference RFC2939 * Reference DRAFT-GLASS-MOBILEIP-AGENT-DHCP-PROXY * Possible Reference RFC3002 * Reference DRAFT-THUEL-MOBILEIP-TT * Reference DRAFT-MAHY-SIP-MESSAGE-WAITING * Informative Reference RFC4485 * Normative Reference RFC4702 * Normative Reference RFC4703 * Reference DRAFT-ITSUMO-WIRELESS-DIFFSERV * Informative Reference RFC4701 * Reference DRAFT-IETF-DHC-NEW-OPT-REVIEW * Reference DRAFT-MUKHERJEE-DHC-DHCPROAM * Reference DRAFT-DUKES-IKE-MODE-CFG * Normative Reference RFC3397 * Reference DRAFT-YEOH-TLDHERE * Reference DRAFT-COOPER-WEBI-WPAD * Reference DRAFT-ITSUMO-SIP-MOBILITY-MULTIMEDIA * Normative Reference RFC4388 * Normative Reference RFC4173 * Reference DRAFT-SUBBARAO-MOBILEIP-BINDINGID * Reference DRAFT-LEAR-MIDDLEBOX-ARCH * Informative Reference RFC4171 * Reference DRAFT-AIELLO-DHC-APPLIANCE-CLASS * Reference DRAFT-IETF-NGTRANS-DSTMEXT1-AIIH * Normative Reference RFC3396 * Reference DRAFT-KINNEAR-AGENT-VPN-ID * Reference DRAFT-KINNEAR-AGENT-SUBNET-SELECTION * Reference DRAFT-JOHNSON-VPN-ID-OPTION * Reference DRAFT-PENNO-ISP-SELECTION * Possible Reference DRAFT-RENKER-PAGING-IPV6 * Reference DRAFT-IETF-DHC-DHCPROAM * Reference DRAFT-DOMMETY-E212-DNS * Reference DRAFT-GUTTMAN-DHC-MDNS-ENABLE * Reference DRAFT-IETF-DHC-LDAP-SCHEMA * Reference DRAFT-ITSUMO-SIPPING-MOBILITY-REQ * Reference DRAFT-ITSUMO-SIPPING-MOBILITY-MULTIMEDIA * Reference DRAFT-ADRANGI-MIPV4-MIDBOX-TRAVERSAL * Normative Reference RFC3527 * Normative Reference DRAFT-IETF-DHC-AGENT-VPN-ID * Normative Reference RFC6607 * Reference DRAFT-IETF-IPNGWG-TEMP-ADDRESSES-V2 * Informative Reference DRAFT-SCHULZRINNE-SIPPING-SOS * Reference DRAFT-ITSUMO-DSNP * Reference DRAFT-IETF-DHC-KEY-MANAGEMENT * Reference DRAFT-SARKAR-DHC-ISCSI-BOOT * Reference DRAFT-GUTTMAN-SVRLOC-RFC2610BIS * Normative Reference RFC3723 * Reference DRAFT-WILLIAMS-RFC2937BIS * Informative Reference RFC6760 * Normative Reference DRAFT-GUTTMAN-SVRLOC-RFC2608BIS * Informative Reference RFC5227 * Reference DRAFT-ADRANGI-MOBILEIP-VPN-TRAVERSAL * Reference DRAFT-MAHY-SIPPING-MESSAGE-WAITING * Informative Reference RFC4306 * Reference DRAFT-DROMS-AGENTOPT-8021X * Reference DRAFT-DROMS-DNSCONFIG-DHCPV6 * Reference DRAFT-VANDERSTOK-ZEROCONF-ISSUES * Normative Reference RFC4392 * Reference DRAFT-IRTF-NSRG-REPORT * Reference DRAFT-IETF-IPOIB-LINK-MULTICAST * Reference DRAFT-ENGELSTAD-PANA-PAA-DISCOVERY * Informative Reference RFC4058 * Reference DRAFT-CARON-PUBLIC-WLAN-ROAMING-ISSUES * Normative Reference RFC4014 * Reference DRAFT-ADRANGI-MOBILEIP-NAT-VPN-PROBLEM-STAT-REQ * Reference DRAFT-TSENG-DHC-ISNSOPTION * Normative Reference DRAFT-LEVKOWETZ-DHC-MIP-FA * Normative Reference DRAFT-IETF-DHC-MIPADVERT-OPT * Informative Reference RFC3761 * Reference DRAFT-ALEXIOU-SIPPING-ALLOCATE * Reference DRAFT-LEE-PPVPN-CE-AUTO-CONFIG * Reference DRAFT-ESTRELA-TIMIP * Reference DRAFT-KASHYAP-IPOIB-DHCP-OVER-INFINIBAND * Normative Reference RFC4390 * Normative Reference RFC4174 * Reference DRAFT-FANGMAN-RYON-DHC-HQOS * Reference DRAFT-IETF-MOBILEIP-VPN-PROBLEM-STATEMENT * Reference DRAFT-DROMS-RFC2563-DEPRECATE * Reference DRAFT-TERRELL-IPTX-DHCP-REQ-IPTX-IP-ADD-SPEC * Reference DRAFT-MICKLES-V6OPS-ISP-CASES * Informative Reference RFC4030 * Informative Reference DRAFT-TEMPLIN-AEROLINK * Informative Reference DRAFT-IETF-MOBILEIP-VPN-PROBLEM-STATEMENT-REQ * Informative Reference RFC4093 * Normative Reference DRAFT-BAKKE-DHC-SNMP-TRAP * Possible Reference DRAFT-SCHULZRINNE-NSIS-CASP * Reference DRAFT-LEAR-CONFIG-ISSUES * Normative Reference RFC3634 * Reference DRAFT-ALLEN-LAP-IPV6 * Reference DRAFT-LINTON-ARCP * Reference DRAFT-DROMS-DHCP-RELAY-AGENT-IPSEC * Normative Reference RFC4682 * Reference DRAFT-JOHNSON-DHC-SERVER-OVERRIDE * Reference DRAFT-JOHNSON-DHC-SUBSCRIBER-ID * Reference DRAFT-JOHNSON-DHC-SUBNET-ALLOC * Normative Reference RFC6656 * Reference DRAFT-ERIKSSON-RABBIT * Reference DRAFT-JONES-CABLE-GATEWAY-ADDRESSING-MIB * Normative Reference DRAFT-IETF-UDLR-EXPERIMENTS * Possible Reference DRAFT-JONES-CABLE-GATEWAY-ADDRESSING * Reference DRAFT-JONES-CABLE-GATEWAY-CONFIG-MIB * Reference DRAFT-JONES-CABLE-GATEWAY-DEVICE-MIB * Reference DRAFT-JONES-CABLE-GATEWAY-SECURITY-MIB * Reference DRAFT-JONES-CABLE-GATEWAY-TOOLS-MIB * Normative Reference DRAFT-SCHULZRINNE-GEOPRIV-DHCP-CIVIL * Reference DRAFT-DUKES-IKEV2-CONFIG-PAYLOAD * Informative Reference DRAFT-IESG-VENDOR-EXTENSIONS * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Normative Reference RFC3993 * Reference DRAFT-JONES-CABLE-GATEWAY-QOS-MIB * Informative Reference RFC3594 * Normative Reference RFC5107 * Possible Reference RFC3790 * Reference DRAFT-VOLZ-DHC-EXTENDED-OPTIONCODES * Normative Reference DRAFT-RICHARDSON-DHC-AUTH-SIG0 * Normative Reference DRAFT-TEMPLIN-ISATAP-DHCP * Informative Reference DRAFT-IETF-DHC-IMPLEMENTATION * Normative Reference DRAFT-IETF-IPSEC-DHCP-OVER-IKE * Normative Reference DRAFT-IETF-IPSEC-DHCP-OVER-IKE-DHCPD * Normative Reference DRAFT-IETF-IPSEC-DHCP-OVER-IKE-RADIUS * Informative Reference DRAFT-IETF-DHC-RELAY-AGENT-AUTH * Normative Reference RFC3825 * Reference DRAFT-IETF-DHC-EXTENDED-OPTIONCODES * Normative Reference DRAFT-THALER-IPV6-NDPROXY * Normative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Normative Reference DRAFT-ABOBA-DHC-NAD-IPV4 * Informative Reference DRAFT-HALL-SUBMIT-SRV * Reference DRAFT-JOHNSTON-PXE-OPTIONS * Reference DRAFT-TSCHOFENIG-PANA-BOOTSTRAP-RFC3118 * Informative Reference DRAFT-IETF-IPCDN-CABLE-GATEWAY-ADDRESSING-MIB * Informative Reference DRAFT-IETF-IPCDN-CABLE-GATEWAY-DEVICE-MIB * Informative Reference DRAFT-IETF-IPCDN-CABLE-GATEWAY-QOS-MIB * Informative Reference DRAFT-IETF-IPCDN-CABLE-GATEWAY-CONFIG-MIB * Informative Reference DRAFT-IETF-IPCDN-CABLE-GATEWAY-SECURITY-MIB * Informative Reference DRAFT-IETF-IPCDN-CABLE-GATEWAY-TOOLS-MIB * Informative Reference DRAFT-FAIR-IPDVB-AR * Reference DRAFT-CARLBERG-ETS-STUB-FRAME * Normative Reference DRAFT-IETF-DHC-AUTH-SIGZERO * Normative Reference RFC4676 * Reference DRAFT-SWAMY-DHC-CLIENT-ID * Normative Reference RFC4436 * Normative Reference DRAFT-BOUND-DSTM-EXP * Informative Reference DRAFT-IETF-DHC-RELAY-AGENT-IPSEC * Normative Reference RFC4578 * Normative Reference RFC3925 * Informative Reference DRAFT-IETF-PANA-IPSEC * Reference DRAFT-KUMAR-DNA-RQMNT-IPV4 * Reference DRAFT-VOLZ-DHC-RAPIDREPLY-OPT * Reference DRAFT-ADRANGI-RADIUS-EXTENSION-FOR-PWLAN * Normative Reference RFC4361 * Reference DRAFT-RENTSCHLER-DHC-DISCOVERY * Reference DRAFT-RENTSCHLER-DHC-INTERFACE-OPT * Normative Reference DRAFT-VIJAY-DHC-OPT-EXTRBOOT * Normative Reference DRAFT-SENTHIL-DHC-PROXYSERVER-OPT * Informative Reference DRAFT-HALL-EMAIL-SRV * Informative Reference DRAFT-VIJAY-DHC-DHCPV6-MCAST-RECONF * Normative Reference RFC4039 * Normative Reference DRAFT-HIBBS-DHC-CHANGES * Reference DRAFT-SHEN-DHC-BLOCK-ALLOC * Normative Reference DRAFT-LEMON-DHCPV4-TO-V6-ID-TRANS * Informative Reference RFC4958 * Normative Reference RFC4562 * Normative Reference RFC3942 * Normative Reference DRAFT-STAPP-DHC-VENDOR-SUBOPTION * Normative Reference RFC6842 * Normative Reference DRAFT-DANIEL-DHC-IPV6IN4-OPT * Normative Reference DRAFT-OHBA-PANA-FRAMEWORK * Normative Reference DRAFT-IETF-DHC-PROXYSERVER-OPT * Normative Reference DRAFT-IETF-DHC-OPT-EXTRBOOT * Normative Reference DRAFT-YEGIN-EAP-BOOT-RFC3118 * Normative Reference DRAFT-CHOWN-DHC-DUAL-STACK * Reference DRAFT-CADAR-DHC-DHCPV6-V4OPTIONS * Normative Reference DRAFT-SENTHIL-DHC-V4RELAY-MIB * Reference DRAFT-TACSIK-DHC-DHCP-IPV6-SIP-PROXY * Informative Reference RFC4477 * Reference DRAFT-TSCHUDIN-MANET-LUNAR * Reference DRAFT-URUENA-XSDF-COMMON * Normative Reference DRAFT-TRAN-MIDCOM-DHCP-OPTION * Reference DRAFT-EDDY-TCP-MOBILITY * Normative Reference DRAFT-DANIEL-DHC-DHCPV4-TEP-CONF * Normative Reference DRAFT-CADAR-DHC-OPT-IMAP * Normative Reference DRAFT-CHOWDHURY-DHC-BCMCV4-OPTION * Informative Reference DRAFT-DALEY-MAGMA-SMLD-PROB * Informative Reference DRAFT-TEMPLIN-V6V4INET * Informative Reference DRAFT-EGGERT-TCPM-TCP-RETRANSMIT-NOW * Informative Reference DRAFT-HARDIE-EMERGENCY-CALL-ROUTING * Informative Reference RFC5944 * Informative Reference DRAFT-MOHANP-MOBIKE-NAT * Normative Reference DRAFT-DEMERJIAN-SERHROUCHNI-ACHMELAL-EDHCP * Reference DRAFT-EDDY-TLMARCH * Informative Reference DRAFT-TEMPLIN-IPVLX * Informative Reference DRAFT-IRTF-NMRG-AN-GAP-ANALYSIS * Normative Reference RFC4243 * Normative Reference RFC4852 * Informative Reference DRAFT-SAVOLA-MBONED-ADDRARCH * Informative Reference RFC4941 * Informative Reference RFC4907 * Informative Reference DRAFT-WING-BEHAVE-MULTICAST * Informative Reference RFC5626 * Informative Reference DRAFT-EGGERT-HIPRG-RR-PROB-DESC * Informative Reference RFC6308 * Normative Reference DRAFT-IETF-DHC-BCMCV4-OPTION * Normative Reference RFC4280 * Reference DRAFT-CLAUSEN-MANET-ADDRESS-AUTOCONF * Normative Reference DRAFT-SYAM-DHC-SOAV4-OPTION * Normative Reference RFC5859 * Reference DRAFT-LEUNG-MIP4-HOST-CONFIG-VSE * Informative Reference RFC5684 * Informative Reference DRAFT-STIEMERLING-IPDVB-CONFIG * Informative Reference RFC4332 * Informative Reference RFC4580 * Informative Reference RFC4632 * Normative Reference DRAFT-POLK-GEOPRIV-DHC-GEO-LCI-UPSTREAM * Normative Reference DRAFT-SURAJ-DHCPV4-PAA-OPTION * Reference DRAFT-ACHANTA-DHC-AP-OPTIONS * Normative Reference DRAFT-LIJUN-DHC-CLF-NASS-OPTION * Normative Reference RFC4947 * Normative Reference DRAFT-SCHULZRINNE-ECRIT-LUMP * Informative Reference RFC6886 * Normative Reference DRAFT-MGLT-DNSOP-SEARCH-LIST-PROCESSING * Informative Reference DRAFT-FACCIN-MIH-INFOSERV * Reference DRAFT-BHARATIA-MIP4-GEN-EXT * Normative Reference DRAFT-IETF-MIP4-GEN-EXT * Informative Reference DRAFT-MASSAR-DNSOP-SERVICE * Normative Reference DRAFT-OGAWA-MOBOPTS-DHCPV4-FHO * Informative Reference DRAFT-VENAAS-DHC-DUAL-STACK-MERGE * Informative Reference DRAFT-MAHY-EAP-ENROLLMENT * Normative Reference DRAFT-DROMS-DHC-DHCPV6-RFC868-SERVERS * Normative Reference DRAFT-POLK-DHC-URI * Informative Reference DRAFT-IETF-DHC-DUAL-STACK-MERGE * Normative Reference RFC5192 * Normative Reference DRAFT-SCHULZRINNE-ECRIT-MAPPING-ARCH * Possible Reference DRAFT-ZI-DHC-AGENT-REQUEST-MULTI-POOL * Normative Reference DRAFT-BOURDAIS-DHCP-CLUSTER * Informative Reference RFC5508 * Reference DRAFT-DECNODDER-DHC-RAI-UNICAST * Informative Reference RFC4925 * Informative Reference DRAFT-HOFFMAN-IKEV2-1 * Normative Reference DRAFT-LEAR-DHC-TIMEZONE-OPTION * Normative Reference RFC4833 * Informative Reference DRAFT-DANIEL-DHC-MIHIS-OPT * Informative Reference DRAFT-WENIGER-AUTOCONF-PDAD-OLSR * Normative Reference DRAFT-IETF-DHC-DHCPV6-RFC868-SERVERS * Informative Reference RFC4988 * Normative Reference DRAFT-CHOWDHURY-NETMIP4 * Normative Reference RFC5563 * Informative Reference DRAFT-POLK-ECRIT-MAPPING-EVENTS * Informative Reference DRAFT-JEE-16NG-PS-GOALS * Informative Reference DRAFT-ASAEDA-MMUSIC-IMG-ARCH * Normative Reference DRAFT-JANG-MIPSHOP-NHDISC * Normative Reference DRAFT-ROSEN-SOS-PHONEBCP * Normative Reference DRAFT-MINABURO-HC-TUNNELING * Normative Reference DRAFT-POLK-DHC-EMERGENCY-DIALSTRING-OPTION * Informative Reference DRAFT-HOFFMAN-IKEV2BIS * Reference DRAFT-DHANKINS-PXELINUX * Normative Reference DRAFT-MULE-CABLELABS-DOCSIS3-IPV6 * Normative Reference DRAFT-TEMPLIN-AUTOCONF-NETLMM-DHCP * Informative Reference DRAFT-SCHUETZ-TCPM-TCP-RLCI * Normative Reference RFC5558 * Normative Reference DRAFT-KINNEAR-DHC-RELAY-AGENT-FLAGS * Normative Reference RFC5010 * Reference DRAFT-JOSHI-DHCP-LEASE-QUERY-EXT * Reference DRAFT-MAGLIONE-PANA-ACCT-TIME * Informative Reference DRAFT-BRZOZOWSKI-DHC-DHCVP6-LEASEQUERY * Informative Reference DRAFT-IETF-DHC-DHCVP6-LEASEQUERY * Normative Reference DRAFT-POLK-ECRIT-DHC-EMERGENCY-DIALSTRING-OPTION * Normative Reference DRAFT-POLK-DHC-ECRIT-LOST-SERVER-URI * Normative Reference DRAFT-POLK-DHC-ECRIT-URI-PSAP-ESRP * Reference DRAFT-LAI-MIP4-PROXY-NAT-TRAVERSAL * Informative Reference RFC5571 * Informative Reference DRAFT-HANCOCK-MIPSHOP-GIST-FOR-MIH * Reference DRAFT-HEPWORTH-MIPSHOP-MIH-DESIGN-CONSIDERATIONS * Reference DRAFT-GPATERNO-DHCP-LDAP * Normative Reference RFC5071 * Normative Reference DRAFT-BUXMANN-ATCP * Informative Reference RFC5007 * Normative Reference DRAFT-TSCHOFENIG-DHC-LOST-DISCOVERY * Normative Reference DRAFT-POLK-ECRIT-DHC-LOST-DISCOVERY * Normative Reference RFC5223 * Informative Reference RFC4903 * Normative Reference DRAFT-MORAND-PANA-PANAOVERDSL * Normative Reference DRAFT-IETF-PANA-PANAOVERDSL * Normative Reference DRAFT-ZHAO-DHC-USER-AUTHENTICATION * Reference DRAFT-DHANKINS-ATOMIC-DHCP * Normative Reference DRAFT-SARIKAYA-DHC-PROXYAGENT * Normative Reference DRAFT-WINTERBOTTOM-GEOPRIV-HELD-DHCP-DISCOVERY * Normative Reference DRAFT-THOMSON-GEOPRIV-HELD-UNAPTR * Informative Reference DRAFT-YACINE-MIP4-TUNNEL-EXT * Informative Reference RFC6116 * Possible Reference DRAFT-SGUNDAVE-MIP6-PROXYMIP6 * Normative Reference DRAFT-THOMSON-GEOPRIV-3825BIS * Normative Reference RFC5692 * Normative Reference DRAFT-MADANAPALLI-16NG-IPV4-OVER-802-DOT-16-IPCS * Normative Reference RFC5948 * Reference DRAFT-KURAPATI-DHC-RELAY-CHAINING-DHCPV4 * Reference DRAFT-JOSHI-DHC-LAYER2-RELAY-AGENT * Informative Reference DRAFT-KUKEC-IKEV2-TUTORIAL-ADDITIONS * Normative Reference DRAFT-DROMS-DHC-CONTAINER-OPT * Normative Reference DRAFT-IETF-DHC-CONTAINER-OPT * Normative Reference DRAFT-THOMSON-GEOPRIV-LIS-DISCOVERY * Normative Reference RFC5986 * Normative Reference DRAFT-TEMPLIN-AUTOCONF-MULTILINK * Normative Reference DRAFT-TEMPLIN-AUTOCONF-VIRTUAL * Normative Reference DRAFT-RUSSERT-NETLMM-HMAP * Informative Reference DRAFT-ABOBA-IP-CONFIG * Informative Reference DRAFT-PRUSS-DHCP-AUTH-DSL * Normative Reference DRAFT-ZHAO-DHC-MIPTYPE * Informative Reference RFC6320 * Normative Reference RFC5214 * Informative Reference DRAFT-VOLZ-DHC-3942-STATUS * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Normative Reference DRAFT-CALHOUN-DHC-CAPWAP-AC-OPTION * Normative Reference RFC5844 * Informative Reference DRAFT-LEAR-IETF-SYSLOG-URI * Normative Reference DRAFT-POLK-GEOPRIV-DHCP-LBYR-URI-OPTION * Normative Reference DRAFT-IETF-GEOPRIV-DHCP-LBYR-URI-OPTION * Informative Reference DRAFT-BAKER-SAVA-OPERATIONAL * Informative Reference RFC5779 * Normative Reference DRAFT-VEIKKOLAINEN-SIPPING-APP-CONFIG * Normative Reference RFC5417 * Informative Reference DRAFT-NADAS-VRRP-UNIFIED-SPEC * Informative Reference RFC5798 * Normative Reference DRAFT-BAJKO-MOS-DHCP-OPTIONS * Possible Reference DRAFT-MELIA-MIPSHOP-MSTP-SOLUTION * Informative Reference RFC5677 * Informative Reference RFC5505 * Informative Reference DRAFT-BAKER-SAVA-IMPLEMENTATION * Informative Reference RFC5218 * Informative Reference DRAFT-MUHANNA-NETLMM-MULTIHOMING-SUPPORT * Reference DRAFT-JOSHI-DHC-L2RA * Normative Reference DRAFT-IETF-DHC-L2RA * Reference DRAFT-LI-MIPSHOP-FBU-SEC * Normative Reference DRAFT-DENG-DHC-SERVICE-IDENTIFIERS * Normative Reference DRAFT-TEMPLIN-DHCPMTU * Normative Reference DRAFT-DESPRES-V6OPS-6RD-IPV6-RAPID-DEPLOYMENT * Normative Reference DRAFT-STAPP-DHC-RELAY-ID * Reference DRAFT-KURAPATI-DHC-L2RA-EXTENSIONS * Reference DRAFT-IETF-DHC-L2RA-EXTENSIONS * Normative Reference DRAFT-GONDI-NETLMM-PMIP-AAAM * Normative Reference DRAFT-MA-SOFTWIRE-IPSEC-GRE-DEMULTIPLEXING-PS * Reference DRAFT-KURAPATI-DHC-LEASEQUERY-BY-REMOTE-ID * Normative Reference RFC6148 * Normative Reference DRAFT-VINOKOUR-BFD-DHCP * Informative Reference DRAFT-MCPHERSON-SAVI-THREAT-SCOPE * Normative Reference RFC5678 * Normative Reference DRAFT-VINOKOUR-DHCP-RECONFIGURE-OPTION * Normative Reference RFC6925 * Reference DRAFT-DTV-DHC-DHCPV4-BULK-LEASEQUERY * Normative Reference RFC6926 * Informative Reference DRAFT-DENG-GMMP * Normative Reference DRAFT-DENG-MIP4-HOST-CONFIGURATION * Normative Reference DRAFT-SAVOLAINEN-INDICATING-240-ADDRESSES * Normative Reference DRAFT-VOLZ-DHC-DHCPV4-VENDOR-MESSAGE * Normative Reference DRAFT-IETF-DHC-DHCPV4-VENDOR-MESSAGE * Normative Reference DRAFT-KINNEAR-DHC-DHCPV4-BULK-LEASEQUERY * Normative Reference DRAFT-DHANKINS-SOFTWIRE-TUNNEL-OPTION * Normative Reference DRAFT-DHANKINS-DHCPINFORM-CLARIFY * Normative Reference DRAFT-BAJKO-V6OPS-PORT-RESTRICTED-IPADDR-ASSIGN * Normative Reference DRAFT-TOLLE-CAP * Normative Reference RFC5494 * Normative Reference DRAFT-BOUCADAIR-PORT-RANGE * Informative Reference RFC5887 * Normative Reference DRAFT-BELLIS-DNSEXT-DNSPROXY * Normative Reference RFC5625 * Informative Reference DRAFT-CLAUSEN-MANET-LINKTYPE * Normative Reference DRAFT-BOUCADAIR-DHC-PORT-RANGE * Informative Reference DRAFT-GONT-BEHAVE-NAT-SECURITY * Informative Reference DRAFT-PATIL-DHC-APN-ATTACHTYPE-OPTIONS * Normative Reference DRAFT-ZIMMER-DHC-DHCPV6-REMOTE-BOOT-OPTIONS * Informative Reference DRAFT-BLANCHET-MIF-PROBLEM-STATEMENT * Informative Reference RFC6418 * Informative Reference RFC5579 * Normative Reference DRAFT-BAJKO-PRIPADDRASSIGN * Informative Reference DRAFT-THOMSON-GEOPRIV-RES-GW-LIS-DISCOVERY * Informative Reference RFC7216 * Normative Reference DRAFT-IETF-DHC-DHCPINFORM-CLARIFY * Normative Reference DRAFT-MELIA-DHC-PCO * Normative Reference DRAFT-YANG-MIF-REQ * Normative Reference RFC6153 * Informative Reference DRAFT-WANG-ALTO-DISCOVERY * Reference DRAFT-HUANG-DHCP-SU * Normative Reference DRAFT-MILES-DHC-FORCERENEW-KEY * Normative Reference DRAFT-POLK-GEOPRIV-DHC-GEOELEMENT-SHAPE-OPTION * Informative Reference DRAFT-BRZOZOWSKI-DHCP-EAP-ANALYSIS * Informative Reference DRAFT-WAKIKAWA-NETEXT-PMIP6-NEMO-SUPPORT * Informative Reference DRAFT-LI-DHC-SIMPLE-DSL-AUTH * Possible Reference DRAFT-BI-SAVI-CPS * Informative Reference RFC6139 * Normative Reference DRAFT-XIA-MEXT-HIOPTV4 * Normative Reference RFC6225 * Normative Reference DRAFT-LIU-MULTIMOB-MULTICAST-RECEIVER-MOBILITY * Normative Reference DRAFT-GUO-SOFTWIRE-SC-DISCOVERY * Normative Reference DRAFT-TEMPLIN-INTAREA-VET * Normative Reference DRAFT-MEYER-LISP-MN * Normative Reference DRAFT-HUANG-DHC-RELAY-PS * Normative Reference DRAFT-WANG-DHC-LDN-OPTION * Normative Reference DRAFT-LIVINGOOD-DNS-REDIRECT * Informative Reference DRAFT-WILLIAMS-MIF-PROBLEM-SCENARIOS * Informative Reference DRAFT-KO-MIF-SECURITY-CONSIDERATIONS * Normative Reference DRAFT-BAJKO-ARCBAND-SHAPE * Informative Reference DRAFT-AXU-ADDR-SEL * Informative Reference RFC6272 * Normative Reference DRAFT-TSOU-NETWORK-CONFIGURATION-PROBLEM-STATEMENT * Normative Reference DRAFT-GUO-SOFTWIRE-AUTO-GRE * Informative Reference DRAFT-HUANG-DHC-MULTIPLE-RELAY-AGENTS-OPTION * Informative Reference DRAFT-KO-MIF-THREAT-ANALYSIS * Normative Reference DRAFT-DESPRES-SOFTWIRE-MESH-SAM * Normative Reference DRAFT-BERNARDOS-AUTOCONF-ADDRESSING-MODEL * Normative Reference RFC7039 * Possible Reference DRAFT-BI-SAVI-DHCP * Normative Reference DRAFT-IETF-SAVI-DHCP * Informative Reference DRAFT-JJMB-DHC-EAP-AUTH-ANALYSIS * Informative Reference DRAFT-WING-BEHAVE-DNS64-CONFIG * Informative Reference DRAFT-KORHONEN-V6OPS-3GPP-EPS * Informative Reference RFC6459 * Informative Reference DRAFT-IETF-DHC-V4CONFIGURATION * Normative Reference DRAFT-KINNEAR-DHC-DHCPV4-ACTIVE-LEASEQUERY * Informative Reference DRAFT-YEGIN-PANA-UNSPECIFIED-ADDR * Normative Reference DRAFT-DESPRES-SOFTWIRE-SAM * Normative Reference RFC6011 * Normative Reference DRAFT-BPW-SOFTWIRE-PCP-DHCP * Normative Reference DRAFT-BPW-PCP-DHCP * Informative Reference DRAFT-XIAOYU-APLUSP-LITE * Normative Reference DRAFT-BALDWIN-DHC-SOFTWIRE-ANYCAST-DHCP * Informative Reference DRAFT-TSOU-OPSAWG-NETWORK-CONFIGURATION * Informative Reference DRAFT-IETF-OPSAWG-AUTOMATED-NETWORK-CONFIGURATION * Informative Reference DRAFT-AZINGER-CIDRV6 * Normative Reference DRAFT-LIYZ-TRILL-REQS-MLT2UNI-OPT * Informative Reference DRAFT-CHROBOCZEK-AHCP * Normative Reference DRAFT-LEMON-DHCPV4-RELAY-ENCAPSULATION * Normative Reference DRAFT-SHEFFER-DHC-INITIAL-RANDOM * Normative Reference DRAFT-IETF-DHC-80211-OPTION * Normative Reference DRAFT-GROCHLA-80211-DHCP-OPTION * Normative Reference DRAFT-LIVINGOOD-DNS-MALWAREPROTECT * Informative Reference DRAFT-AZINGER-SCALABLE-ADDRESSING * Normative Reference DRAFT-ASATI-DHC-RELAY-AGENT-CONFIG * Normative Reference DRAFT-MONGAZON-EMU-IP-MODES-EAP * Normative Reference DRAFT-IETF-DHC-DHCPV4-RELAY-ENCAPSULATION * Informative Reference DRAFT-LIN-SAVI-ROAMING-ND * Normative Reference DRAFT-MRW-DVNE-FW * Normative Reference DRAFT-DESPRES-SOFTWIRE-4RD * Normative Reference DRAFT-SCHOENW-OPSAWG-NM-DHC * Informative Reference DRAFT-MALC-ARMD-MOOSE * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Normative Reference RFC6930 * Informative Reference DRAFT-FARRER-DHC-SHARED-ADDRESS-LEASE * Normative Reference DRAFT-AN-SAVI-MIB * Normative Reference RFC7084 * Informative Reference RFC6632 * Informative Reference RFC6706 * Reference DRAFT-LONVICK-PRIVATE-TAX * Normative Reference DRAFT-CUI-SOFTWIRE-DHCP-OVER-TUNNEL * Informative Reference DRAFT-KO-DVN-PROBLEM-STATEMENT * Normative Reference DRAFT-BI-DHC-OPEXTENSIONS * Normative Reference DRAFT-XU-DHC-CADHCP * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-REQUIREMENTS * Informative Reference DRAFT-ARKKO-CORE-SLEEPY-SENSORS * Informative Reference DRAFT-VANREIN-V6OPS-6BED4 * Informative Reference DRAFT-FREEDMAN-PPPEXT-IPV6-6RD * Normative Reference DRAFT-DESPRES-SOFTWIRE-4RD-U * Normative Reference DRAFT-BI-DHC-SEC-OPTION * Normative Reference DRAFT-HALWASIA-DHC-DHCPV6-HARDWARE-ADDR-OPT * Normative Reference DRAFT-LIU-DHC-3GPP-OPTION * Normative Reference DRAFT-LIU-DHC-HO * Informative Reference DRAFT-BAKER-HOMENET-PREFIX-ASSIGNMENT * Informative Reference DRAFT-KO-DSI-PROBLEM-STATEMENT * Informative Reference RFC6647 * Normative Reference DRAFT-CUI-DHC-DHCPV4-OVER-IPV6 * Informative Reference DRAFT-NIEMINEN-CORE-SERVICE-DISCOVERY * Informative Reference DRAFT-HAZEYAMA-WIDECAMP-IPV6-ONLY-EXPERIENCE * Normative Reference DRAFT-MA-CORE-DHCP-PD * Informative Reference DRAFT-CAO-CORE-PD * Informative Reference DRAFT-KO-VAAS-PROBLEM-STATEMENT * Informative Reference DRAFT-ZHU-ROLL-ADDR-AUTOCONF * Normative Reference RFC7291 * Normative Reference DRAFT-IETF-DHC-DHCPV4-OVER-IPV6 * Normative Reference DRAFT-TOWNSLEY-TROAN-IPV6-CE-TRANSITIONING * Informative Reference RFC6994 * Possible Reference RFC3099 * Reference RFC3344 * Normative Reference RFC4776 * Possible Reference DRAFT-YANG-DHC-IPV4-DIS * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-DESIGN * Informative Reference DRAFT-VYNCKE-OPSEC-V6 * Normative Reference DRAFT-MRUGALSKI-SOFTWIRE-DHCPV4-OVER-V6-OPTION * Normative Reference DRAFT-WU-DHC-PORT-SET-OPTION * Normative Reference DRAFT-IETF-SOFTWIRE-4RD * Informative Reference DRAFT-GEORGE-DHC-REQUEST-RETRANSMISSION * Informative Reference RFC6939 * Normative Reference DRAFT-CHEN-SOFTWIRE-CE-NON-PD * Normative Reference DRAFT-BHANDARI-NETEXT-PMIPV6-DHCP-OPTIONS * Normative Reference DRAFT-YASUDA-CACHE-SERVER-SELECTION * Informative Reference DRAFT-PERREAULT-SUNSET4-NOIPV4 * Normative Reference DRAFT-BHANDARI-DHC-ACCESS-NETWORK-IDENTIFIER * Informative Reference DRAFT-IETF-SOFTWIRE-MAP-DHCP * Informative Reference DRAFT-IETF-OPSEC-V6 * Normative Reference DRAFT-BOUCADAIR-DHC-ADDRESS-NAME-ENCODING * Normative Reference DRAFT-HALWASIA-DHC-INFORM-REFRESH-TIME-OPT * Normative Reference DRAFT-SUN-DHC-PORT-SET-OPTION * Normative Reference DRAFT-ZHOU-DHC-GRE-OPTION * Normative Reference DRAFT-ZHU-DHC-VLAN-ID-OPTION * Possible Reference DRAFT-YANG-SUNSET4-WEAKEN-DHCP * Possible Reference DRAFT-YANG-V6OPS-IPV6TRAN-SELECT * Normative Reference DRAFT-OGUD-DHC-UDP-TIME-OPTION * Informative Reference DRAFT-BAKER-6RENUM-OSS-RENUMBERING * Informative Reference RFC6918 * Normative Reference DRAFT-ORR-DHCP-DNS-SD-OPTIONS * Informative Reference DRAFT-GRUNDEMANN-HOMENET-HIPNET * Normative Reference DRAFT-XUE-DHC-LOCATION-OPTION * Normative Reference DRAFT-XUE-DHCP-LOCATION-OPTION * Informative Reference DRAFT-JVKJJMB-HOME-NETWORKING-INCREMENTAL * Informative Reference DRAFT-HAZEYAMA-SUNSET4-DNS-A-FILTER * Informative Reference DRAFT-GRUNDEMANN-HIPNET * Normative Reference DRAFT-SARIKAYA-PROXY-VXLAN * Normative Reference DRAFT-BOUCADAIR-RFC6153-UPDATE * Normative Reference DRAFT-JOSYULA-DHC-MULTICAST * Normative Reference DRAFT-JIANG-INTAREA-CONET-GAP-ANALYSIS * Normative Reference DRAFT-PFISTER-HOMENET-PREFIX-ASSIGNMENT * Reference DRAFT-OTIS-DNSSD-MDNS-XLINK * Informative Reference DRAFT-OSTERWEIL-DANE-IPSEC * Informative Reference DRAFT-JIANG-NMRG-AN-GAP-ANALYSIS * Informative Reference DRAFT-FSC-DHC-DHCP4O6-SADDR-OPT * Normative Reference DRAFT-SARIKAYA-NVO3-DHC-VXLAN-MULTICAST * Normative Reference DRAFT-SARIKAYA-NVO3-DHC-VXLAN-CENTRALDIR-MAPPING * Informative Reference DRAFT-HZHWM-START-TLS-FOR-DNS * Normative Reference DRAFT-TAHT-KELLEY-HUNT-DHCPV4-TO-SLAAC-NAMING * Normative Reference DRAFT-HUITEMA-PERPASS-DHCP-IDENTIFIERS * Normative Reference DRAFT-IETF-DHC-DYNAMIC-SHARED-V4ALLOCATION * Informative Reference DRAFT-IETF-HOMENET-HNCP * Normative Reference DRAFT-CONET-AEON-GAP-ANALYSIS * Informative Reference DRAFT-FSC-SOFTWIRE-DHCP4O6-SADDR-OPT * Normative Reference RFC7341 * Informative Reference DRAFT-IETF-TZDIST-SERVICE * Informative Reference DRAFT-HZHWM-DPRIVE-START-TLS-FOR-DNS * Normative Reference DRAFT-SARIKAYA-NVO3-PROXY-VXLAN * Normative Reference DRAFT-XUE-DHC-DYNAMIC-GRE * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-ACTIVE-LEASEQUERY * Informative Reference DRAFT-CHESHIRE-HOMENET-DOT-HOME * Informative Reference DRAFT-IETF-SUNSET4-NOIPV4 * Normative Reference DRAFT-LIU-DHC-DHCP-YANG-MODEL * Normative Reference DRAFT-IETF-DHC-TOPO-CONF * Normative Reference DRAFT-CUI-DHC-DHCP4O6-BULK-ACTIVE-LEASEQUERY * Reference DRAFT-SBOYAPATI-DHCP-RELAY-CHAINING-DHCPV4 * Normative Reference DRAFT-JIANG-DHC-SEDHCPV4 * Normative Reference DRAFT-IETF-DHC-ACCESS-NETWORK-IDENTIFIER * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY * Normative Reference DRAFT-IETF-DHC-DHCPV4-ACTIVE-LEASEQUERY * Normative Reference DRAFT-HUITEMA-DHC-ANONYMITY-PROFILE * Normative Reference DRAFT-WKUMARI-DHC-CAPPORT * Informative Reference DRAFT-HUITEMA-PRIVSEC-HARMFULNAME RFC2132: DHCP Options and BOOTP Vendor Extensions (34 pages) * Obsoletes RFC1533 * Reference RFC1305 * Possible Reference RFC1533 * Possible Reference RFC950 * Possible Reference RFC1122 * Reference RFC887 * Reference RFC1256 * Reference RFC951 * Possible Reference RFC1035 * Reference STD19 * Reference RFC1179 * Reference RFC2131 * Reference STD13 * Possible Reference RFC868 * Possible Reference RFC865 * Reference RFC1191 * Possible Reference RFC1001 * Reference STD5 * Possible Reference STD1 * Reference STD3 * Reference STD26 * Reference RFC1497 * Reference FYI6 * Reference STD23 * Reference RFC1042 * Reference RFC893 * Reference RFC894 * Updates RFC3442 * Updates RFC3942 * Updates RFC4361 * Updates RFC4833 * Updates RFC5494 * Informative Reference DRAFT-IETF-DHC-DHCPV4-ACTIVE-LEASEQUERY * Informative Reference RFC3315 * Reference RFC2489 * Reference RFC3118 * Reference DRAFT-IETF-DHC-OPTIONS-OPT127 * Reference RFC3004 * Reference RFC2241 * Reference DRAFT-IETF-DHC-TIMEZONE * Reference DRAFT-IETF-DHC-INTERSERVER * Reference RFC3046 * Reference DRAFT-IETF-DHC-MULTOPT * Possible Reference DRAFT-IETF-DHC-DYN-SUBNET-CONF * Reference DRAFT-IETF-DHC-SSO * Reference DRAFT-IETF-DHC-SECURITY-ARCH * Normative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Reference DRAFT-DITTERT-HOST-SYS-CHAR * Reference DRAFT-IETF-DHC-NAMEDPOOL * Reference RFC2242 * Reference DRAFT-HEDSTROM-DHC-LDAP * Reference DRAFT-IETF-DHC-DOMSRCH * Reference DRAFT-IETF-DHC-SUBSEL * Reference DRAFT-MONTENEGRO-TSP * Reference RFC2434 * Reference DRAFT-IETF-DHC-FAILOVER * Reference DRAFT-IETF-DHC-OPTIONS-CONT * Reference DRAFT-OHARA-IPSECPARAM * Reference DRAFT-IETF-MOBILEIP-CALHOUN-TEP * Normative Reference RFC3456 * Reference DRAFT-IETF-IPP-DHCP-OPTION * Reference DRAFT-IETF-DHC-SAFE-FAILOVER-PROTO * Normative Reference DRAFT-IETF-DHC-SERVER-MIB * Reference RFC2855 * Reference DRAFT-MILLER-DHCP-LDAP-SCHEMA * Reference RFC2563 * Reference DRAFT-IETF-MALLOC-MDHCP * Reference DRAFT-GU-DHCP-LDAP-SCHEMA * Reference RFC2485 * Reference DRAFT-IETF-DHC-IPV4-AUTOCONFIG * Reference DRAFT-IETF-DHC-USERADDR * Reference DRAFT-HENRY-DHCP-OPT61-UUID-TYPE * Reference RFC2730 * Reference RFC3011 * Reference DRAFT-IETF-DHC-CALLCONTROLSERV * Reference DRAFT-YMBK-TERMROOM-OP * Reference RFC2937 * Reference DRAFT-GUTTMAN-NITS-REQTS * Reference DRAFT-IETF-DHC-OPTION-REVIEW-AND-NAMESPACE * Reference DRAFT-IETF-WREC-WPAD * Reference DRAFT-GUPTA-DHCP-AUTH * Reference DRAFT-IETF-DHC-SCHEMA * Normative Reference DRAFT-SARIKAYA-DHC-VXLAN-MULTICAST * Reference DRAFT-HENRY-REMOTE-BOOT-PROTOCOL * Reference DRAFT-PRIVAT-DHC-DOUBLEPHASE * Possible Reference RFC3196 * Reference DRAFT-ABOBA-ZEROCONF-MULTI * Reference DRAFT-IETF-DHC-CLIENT-OPTIONS * Reference DRAFT-HORNSTEIN-DHC-KERBAUTH * Reference DRAFT-ABOBA-IPSRA-REQ * Reference DRAFT-IETF-DHC-MIGAGNTLIST * Normative Reference RFC3442 * Possible Reference DRAFT-NAIR-SIP-DHCP * Reference DRAFT-ABOBA-DHC-MDNS-CONF * Possible Reference RFC3361 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Reference DRAFT-ABOBA-DHC-MINI * Reference RFC2939 * Reference DRAFT-GLASS-MOBILEIP-AGENT-DHCP-PROXY * Reference DRAFT-THUEL-MOBILEIP-TT * Informative Reference RFC4702 * Informative Reference RFC4703 * Informative Reference RFC4701 * Reference DRAFT-IETF-DHC-NEW-OPT-REVIEW * Normative Reference DRAFT-OTIS-FC-SCTP-IP * Informative Reference RFC3397 * Reference DRAFT-COOPER-WEBI-WPAD * Informative Reference RFC4388 * Normative Reference RFC4173 * Reference DRAFT-AIELLO-DHC-APPLIANCE-CLASS * Normative Reference RFC3396 * Reference DRAFT-KINNEAR-AGENT-VPN-ID * Reference DRAFT-KINNEAR-AGENT-SUBNET-SELECTION * Reference DRAFT-JOHNSON-VPN-ID-OPTION * Reference DRAFT-GUTTMAN-DHC-MDNS-ENABLE * Reference DRAFT-IETF-DHC-LDAP-SCHEMA * Normative Reference RFC6607 * Informative Reference RFC6763 * Informative Reference RFC6762 * Reference DRAFT-SARKAR-DHC-ISCSI-BOOT * Reference DRAFT-WILLIAMS-RFC2937BIS * Normative Reference DRAFT-LEVKOWETZ-DHC-MIP-FA * Normative Reference DRAFT-IETF-DHC-MIPADVERT-OPT * Informative Reference RFC3898 * Normative Reference DRAFT-IETF-DHC-HOST-OPTION-CONSIDERATIONS * Reference DRAFT-KASHYAP-IPOIB-DHCP-OVER-INFINIBAND * Normative Reference RFC4390 * Reference DRAFT-FANGMAN-RYON-DHC-HQOS * Informative Reference DRAFT-BAKKE-DHC-SNMP-TRAP * Normative Reference RFC4682 * Reference DRAFT-JOHNSON-DHC-SERVER-OVERRIDE * Reference DRAFT-JOHNSON-DHC-SUBNET-ALLOC * Normative Reference RFC6656 * Normative Reference DRAFT-IETF-UDLR-EXPERIMENTS * Possible Reference DRAFT-JONES-CABLE-GATEWAY-CONFIG-MIB * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Reference DRAFT-KULKARNI-MOBILEIP-DYNAMIC-ASSIGNMENT * Informative Reference RFC5107 * Possible Reference RFC3790 * Reference DRAFT-VOLZ-DHC-EXTENDED-OPTIONCODES * Normative Reference DRAFT-RICHARDSON-DHC-AUTH-SIG0 * Normative Reference DRAFT-TEMPLIN-ISATAP-DHCP * Informative Reference RFC6080 * Normative Reference DRAFT-IETF-DHC-IMPLEMENTATION * Reference DRAFT-VOLZ-DHC-DHCPV6-SITE-OPTIONS * Reference DRAFT-IETF-DHC-EXTENDED-OPTIONCODES * Normative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Normative Reference DRAFT-ABOBA-DHC-NAD-IPV4 * Reference DRAFT-JOHNSTON-PXE-OPTIONS * Reference DRAFT-TSCHOFENIG-PANA-BOOTSTRAP-RFC3118 * Reference DRAFT-LITTLEFIELD-DHCP-VENDOR * Informative Reference DRAFT-IETF-IPCDN-CABLE-GATEWAY-CONFIG-MIB * Normative Reference DRAFT-IETF-DHC-AUTH-SIGZERO * Reference DRAFT-SWAMY-DHC-CLIENT-ID * Normative Reference RFC4578 * Informative Reference RFC3925 * Reference DRAFT-PLONKA-EMBED-ADDR * Normative Reference RFC4361 * Reference DRAFT-RENTSCHLER-DHC-INTERFACE-OPT * Informative Reference DRAFT-VIJAY-DHC-OPT-EXTRBOOT * Normative Reference DRAFT-SENTHIL-DHC-PROXYSERVER-OPT * Informative Reference RFC4075 * Informative Reference RFC4039 * Informative Reference RFC4085 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Normative Reference DRAFT-LEMON-DHCPV4-TO-V6-ID-TRANS * Normative Reference RFC4433 * Normative Reference RFC4562 * Normative Reference RFC3942 * Informative Reference DRAFT-IETF-DHC-OPT-EXTRBOOT * Normative Reference DRAFT-SENTHIL-DHC-V4RELAY-MIB * Reference DRAFT-URUENA-XSDF-COMMON * Informative Reference DRAFT-CADAR-DHC-OPT-IMAP * Informative Reference RFC5226 * Normative Reference DRAFT-DEMERJIAN-SERHROUCHNI-ACHMELAL-EDHCP * Informative Reference DRAFT-CADAR-DHC-DHCPV6-OPT-SMTP * Normative Reference RFC4280 * Normative Reference DRAFT-SYAM-DHC-SOAV4-OPTION * Normative Reference RFC5859 * Reference DRAFT-LEUNG-MIP4-HOST-CONFIG-VSE * Informative Reference RFC4332 * Normative Reference DRAFT-SURAJ-DHCPV4-PAA-OPTION * Normative Reference DRAFT-BLATHERWICK-DHC-MITEL-SITE-OPTIONS-USAGE * Normative Reference DRAFT-MGLT-DNSOP-SEARCH-LIST-PROCESSING * Reference DRAFT-BHARATIA-MIP4-GEN-EXT * Normative Reference DRAFT-IETF-MIP4-GEN-EXT * Normative Reference DRAFT-OGAWA-MOBOPTS-DHCPV4-FHO * Normative Reference DRAFT-DROMS-DHC-DHCPV6-RFC868-SERVERS * Normative Reference RFC5192 * Reference DRAFT-DECNODDER-DHC-RAI-UNICAST * Normative Reference DRAFT-LEAR-DHC-TIMEZONE-OPTION * Normative Reference RFC4833 * Informative Reference DRAFT-DANIEL-DHC-MIHIS-OPT * Normative Reference DRAFT-IETF-DHC-DHCPV6-RFC868-SERVERS * Normative Reference DRAFT-CHOWDHURY-NETMIP6 * Reference DRAFT-DHANKINS-PXELINUX * Normative Reference DRAFT-KINNEAR-DHC-RELAY-AGENT-FLAGS * Normative Reference RFC5010 * Reference DRAFT-JOSHI-DHCP-LEASE-QUERY-EXT * Informative Reference RFC5571 * Reference DRAFT-GPATERNO-DHCP-LDAP * Normative Reference RFC5071 * Normative Reference DRAFT-TSCHOFENIG-DHC-LOST-DISCOVERY * Normative Reference DRAFT-POLK-ECRIT-DHC-LOST-DISCOVERY * Normative Reference RFC5223 * Reference DRAFT-DHANKINS-ATOMIC-DHCP * Informative Reference RFC5948 * Reference DRAFT-KURAPATI-DHC-RELAY-CHAINING-DHCPV4 * Reference DRAFT-JOSHI-DHC-LAYER2-RELAY-AGENT * Normative Reference DRAFT-DROMS-DHC-CONTAINER-OPT * Normative Reference RFC5986 * Normative Reference DRAFT-TEMPLIN-AUTOCONF-MULTILINK * Normative Reference DRAFT-TEMPLIN-AUTOCONF-VIRTUAL * Informative Reference DRAFT-PRUSS-DHCP-AUTH-DSL * Normative Reference RFC5214 * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Normative Reference DRAFT-CALHOUN-DHC-CAPWAP-AC-OPTION * Normative Reference RFC5844 * Normative Reference RFC5417 * Normative Reference DRAFT-MELIA-MIPSHOP-MSTP-SOLUTION * Reference DRAFT-JOSHI-DHC-L2RA * Normative Reference DRAFT-TEMPLIN-DHCPMTU * Normative Reference DRAFT-DESPRES-V6OPS-6RD-IPV6-RAPID-DEPLOYMENT * Reference DRAFT-KURAPATI-DHC-L2RA-EXTENSIONS * Reference DRAFT-IETF-DHC-L2RA-EXTENSIONS * Possible Reference DRAFT-BJORKLUND-YANG-REQUIREMENTS * Reference DRAFT-KURAPATI-DHC-LEASEQUERY-BY-REMOTE-ID * Normative Reference RFC6148 * Informative Reference DRAFT-THOMSON-HELD-GRIP * Normative Reference RFC6926 * Informative Reference DRAFT-THOMSON-GEOPRIV-HELD-GRIP * Reference DRAFT-LHOTKA-YANG-DSDL-MAP * Informative Reference DRAFT-VOLZ-DHC-DHCPV4-VENDOR-MESSAGE * Informative Reference DRAFT-IETF-DHC-DHCPV4-VENDOR-MESSAGE * Normative Reference DRAFT-KINNEAR-DHC-DHCPV4-BULK-LEASEQUERY * Normative Reference DRAFT-DHANKINS-DHCPINFORM-CLARIFY * Normative Reference RFC5494 * Normative Reference DRAFT-HUI-IP-MULTIPLE-CONNECTIONS * Normative Reference DRAFT-BELLIS-DNSEXT-DNSPROXY * Normative Reference RFC5625 * Normative Reference DRAFT-BOUCADAIR-DHC-PORT-RANGE * Informative Reference DRAFT-PATIL-DHC-APN-ATTACHTYPE-OPTIONS * Possible Reference DRAFT-ZIMMER-DHC-DHCPV6-REMOTE-BOOT-OPTIONS * Informative Reference RFC6110 * Normative Reference DRAFT-IETF-DHC-DHCPINFORM-CLARIFY * Normative Reference RFC6731 * Normative Reference DRAFT-HUI-MIF-DHCPV4-ROUTING * Normative Reference RFC6153 * Reference DRAFT-HUANG-DHCP-SU * Informative Reference DRAFT-BRZOZOWSKI-DHCP-EAP-ANALYSIS * Informative Reference DRAFT-LI-DHC-SIMPLE-DSL-AUTH * Normative Reference DRAFT-XIA-MEXT-HIOPTV4 * Normative Reference RFC6225 * Informative Reference DRAFT-TEMPLIN-INTAREA-VET * Informative Reference RFC6709 * Normative Reference DRAFT-HUANG-DHC-RELAY-PS * Normative Reference DRAFT-WANG-DHC-LDN-OPTION * Normative Reference RFC5969 * Informative Reference DRAFT-LEE-SOFTWIRE-6RD-UDP * Informative Reference DRAFT-HUANG-DHC-MULTIPLE-RELAY-AGENTS-OPTION * Informative Reference DRAFT-JJMB-DHC-EAP-AUTH-ANALYSIS * Informative Reference DRAFT-KINNEAR-DHC-DHCPV4-ACTIVE-LEASEQUERY * Normative Reference RFC6011 * Normative Reference DRAFT-BPW-PCP-DHCP * Normative Reference RFC6355 * Normative Reference DRAFT-IETF-DHC-80211-OPTION * Normative Reference DRAFT-GROCHLA-80211-DHCP-OPTION * Informative Reference DRAFT-LEE-6MAN-RA-DSLITE * Normative Reference DRAFT-SCHOENW-OPSAWG-NM-DHC * Normative Reference RFC6930 * Informative Reference RFC6788 * Normative Reference RFC7286 * Reference DRAFT-LONVICK-PRIVATE-TAX * Normative Reference DRAFT-BI-DHC-OPEXTENSIONS * Normative Reference DRAFT-XU-DHC-CADHCP * Normative Reference DRAFT-MOUTON-MIF-DHCPV6-DRLO * Normative Reference DRAFT-BI-DHC-SEC-OPTION * Normative Reference DRAFT-MA-CORE-DHCP-PD * Normative Reference RFC7291 * Normative Reference DRAFT-IETF-DHC-DHCPV4-OVER-IPV6 * Informative Reference DRAFT-IETF-PPSP-PEER-PROTOCOL * Possible Reference RFC3099 * Possible Reference DRAFT-YANG-DHC-IPV4-DIS * Informative Reference DRAFT-SUN-FMC-USE-CASE * Normative Reference DRAFT-BHANDARI-NETEXT-PMIPV6-DHCP-OPTIONS * Possible Reference DRAFT-LEIBA-COTTON-IANA-5226BIS * Normative Reference DRAFT-ZHOU-DHC-GRE-OPTION * Informative Reference DRAFT-SUN-SEMANTIC-USECASE * Informative Reference DRAFT-SUN-V6OPS-SEMANTIC-USECASE * Normative Reference DRAFT-XUE-DHC-LOCATION-OPTION * Normative Reference DRAFT-XUE-DHCP-LOCATION-OPTION * Normative Reference DRAFT-JOSYULA-DHC-MULTICAST * Normative Reference DRAFT-SARIKAYA-PROXY-VXLAN * Normative Reference DRAFT-SARIKAYA-NVO3-DHC-VXLAN-MULTICAST * Normative Reference DRAFT-SARIKAYA-NVO3-DHC-VXLAN-CENTRALDIR-MAPPING * Normative Reference DRAFT-HUITEMA-PERPASS-DHCP-IDENTIFIERS * Normative Reference DRAFT-IETF-DHC-DYNAMIC-SHARED-V4ALLOCATION * Informative Reference DRAFT-IETF-HOMENET-HNCP * Normative Reference DRAFT-IETF-TRAM-TURN-SERVER-DISCOVERY * Normative Reference DRAFT-SARIKAYA-NVO3-PROXY-VXLAN * Informative Reference DRAFT-CHESHIRE-HOMENET-DOT-HOME * Normative Reference DRAFT-CUI-DHC-DHCP4O6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-BULK-ACTIVE-LEASEQUERY * Informative Reference DRAFT-IETF-V6OPS-SIIT-DC-2XLAT * Reference DRAFT-SBOYAPATI-DHCP-RELAY-CHAINING-DHCPV4 * Normative Reference DRAFT-HUITEMA-DHC-ANONYMITY-PROFILE * Informative Reference DRAFT-HUITEMA-PRIVSEC-HARMFULNAME RFC2241: DHCP Options for Novell Directory Services (5 pages) * Reference RFC2132 * Reference RFC2119 * Reference RFC2044 * Reference RFC2131 * Reference DRAFT-MILLER-DHCP-LDAP-SCHEMA * Possible Reference DRAFT-IETF-DHC-CLIENT-OPTIONS * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES RFC2242: NetWare/IP Domain Name and Information (6 pages) * Possible Reference STD1 * Reference RFC854 * Reference RFC2132 * Reference RFC2119 * Reference RFC2131 * Reference DRAFT-MILLER-DHCP-LDAP-SCHEMA * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Reference DRAFT-DHANKINS-ATOMIC-DHCP * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES RFC2485: DHCP Option for The Open Group's User Authentication Protocol (4 pages) * Reference RFC2068 * Reference RFC2131 * Reference RFC2132 * Reference RFC1738 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Possible Reference DRAFT-GIARETTA-MIP6-AMSK * Normative Reference DRAFT-XU-DHC-CADHCP RFC2489: Procedure for Defining New DHCP Options (5 pages) * Reference RFC2434 * Reference RFC2142 * Reference RFC2132 * Reference BCP26 * Reference RFC2131 * Obsoletes RFC2939 * Reference DRAFT-IETF-DHC-NEXTSERVER * Reference RFC2939 * Reference DRAFT-GLASS-MOBILEIP-AGENT-DHCP-PROXY * Possible Reference RFC3679 * Possible Reference DRAFT-VOLZ-DHC-EXTENDED-OPTIONCODES * Possible Reference DRAFT-IETF-DHC-EXTENDED-OPTIONCODES RFC2563: DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients (9 pages) * Reference RFC2132 * Reference BCP14 * Reference RFC2462 * Reference RFC2131 * Reference DRAFT-IETF-DHC-IPV4-AUTOCONFIG * Reference DRAFT-ABOBA-ZEROCONF-MULTI * Reference DRAFT-ABOBA-DNSEXT-MDNS * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Reference DRAFT-DROMS-RFC2563-DEPRECATE * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference DRAFT-DIONNE-SUNSET4-V4GAPANALYSIS * Informative Reference DRAFT-IETF-SUNSET4-GAPANALYSIS RFC2610: DHCP Options for Service Location Protocol (6 pages) * Reference RFC2165 * Reference RFC2279 * Reference BCP14 * Reference RFC2131 * Reference RFC2608 * Informative Reference RFC3528 * Reference DRAFT-KEMPF-SIP-FINDSRV * Reference RFC3105 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Reference DRAFT-GUTTMAN-SVRLOC-SLPV2BIS * Informative Reference DRAFT-ZHAO-IPTEL-GWLOC-SLP * Possible Reference DRAFT-GUTTMAN-SVRLOC-RFC2610BIS * Informative Reference DRAFT-MCDONALD-SVRLOC-MIB * Possible Reference DRAFT-GUTTMAN-SVRLOC-RFC2608BIS * Reference DRAFT-GUTTMAN-SVRLOC-AS * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Reference DRAFT-URUENA-XSDF-COMMON * Normative Reference DRAFT-MOREAU-SRVLOC-DNSSEC-PRIMING * Informative Reference RFC5887 * Normative Reference DRAFT-ZIMMER-DHC-DHCPV6-REMOTE-BOOT-OPTIONS * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference RFC6632 RFC2937: The Name Service Search Option for DHCP (5 pages) * Reference BCP14 * Reference RFC2132 * Possible Reference RFC2119 * Reference RFC2131 * Informative Reference RFC4795 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Informative Reference RFC3397 * Reference DRAFT-WILLIAMS-RFC2937BIS * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Informative Reference DRAFT-IETF-DHC-DHCPV6-OPT-NSS * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Normative Reference DRAFT-IETF-DNSEXT-DNS-PROTOCOL-PROFILE RFC2939: Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types (7 pages) * Obsoletes RFC2489 * Reference RFC2489 * Reference RFC2434 * Reference RFC2142 * Reference RFC2132 * Reference BCP26 * Reference RFC2131 * Reference DRAFT-GUTTMAN-DHC-MDNS-ENABLE * Possible Reference DRAFT-LEVKOWETZ-DHC-MIP-FA * Informative Reference DRAFT-IETF-DHC-MIPADVERT-OPT * Possible Reference DRAFT-FANGMAN-RYON-DHC-HQOS * Informative Reference DRAFT-BAKKE-DHC-SNMP-TRAP * Reference DRAFT-HUSTON-IANA * Possible Reference RFC3679 * Possible Reference DRAFT-VOLZ-DHC-EXTENDED-OPTIONCODES * Possible Reference DRAFT-IETF-DHC-EXTENDED-OPTIONCODES * Possible Reference DRAFT-WKUMARI-DHC-CAPPORT * Possible Reference DRAFT-LITTLEFIELD-DHCP-VENDOR * Possible Reference RFC3925 * Reference DRAFT-VOLZ-DHC-RAPIDREPLY-OPT * Reference DRAFT-RENTSCHLER-DHC-DISCOVERY * Reference DRAFT-RENTSCHLER-DHC-INTERFACE-OPT * Informative Reference DRAFT-VIJAY-DHC-OPT-EXTRBOOT * Possible Reference DRAFT-SENTHIL-DHC-PROXYSERVER-OPT * Informative Reference RFC4039 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Normative Reference RFC3942 * Normative Reference DRAFT-DANIEL-DHC-IPV6IN4-OPT * Informative Reference DRAFT-IETF-DHC-PROXYSERVER-OPT * Informative Reference DRAFT-IETF-DHC-OPT-EXTRBOOT * Reference DRAFT-TACSIK-DHC-DHCP-IPV6-SIP-PROXY * Normative Reference DRAFT-DANIEL-DHC-DHCPV4-TEP-CONF * Informative Reference DRAFT-CADAR-DHC-OPT-IMAP * Normative Reference DRAFT-DEMERJIAN-SERHROUCHNI-ACHMELAL-EDHCP * Informative Reference DRAFT-KLENSIN-IANA-REG-POLICY * Possible Reference DRAFT-LEAR-DHC-TIMEZONE-OPTION * Possible Reference RFC4833 * Normative Reference DRAFT-DANIEL-DHC-MIHIS-OPT * Normative Reference DRAFT-SHEFFER-DHC-INITIAL-RANDOM * Informative Reference DRAFT-WANG-ALTO-DISCOVERY * Normative Reference RFC6225 * Normative Reference RFC6011 * Informative Reference DRAFT-SAINTANDRE-XDASH * Informative Reference RFC6648 * Normative Reference DRAFT-BHANDARI-DHC-ACCESS-NETWORK-IDENTIFIER * Informative Reference DRAFT-LEIBA-COTTON-IANA-5226BIS * Normative Reference DRAFT-HALWASIA-DHC-INFORM-REFRESH-TIME-OPT * Informative Reference DRAFT-IETF-DHC-ACCESS-NETWORK-IDENTIFIER * Normative Reference DRAFT-ORR-DHCP-DNS-SD-OPTIONS * Possible Reference DRAFT-IETF-NETCONF-ZEROTOUCH RFC3004: The User Class Option for DHCP (6 pages) * Possible Reference STD1 * Possible Reference RFC2119 * Reference BCP14 * Reference RFC2132 * Reference RFC2131 * Reference DRAFT-IETF-DHC-FAILOVER * Informative Reference RFC3456 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Reference DRAFT-AIELLO-DHC-APPLIANCE-CLASS * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Normative Reference DRAFT-ZHAO-DHC-USER-AUTHENTICATION * Informative Reference DRAFT-IETF-HOMENET-HNCP RFC3011: The IPv4 Subnet Selection Option for DHCP (7 pages) * Possible Reference BCP11 * Reference BCP14 * Reference RFC2132 * Reference RFC2119 * Reference RFC2131 * Reference DRAFT-IETF-DHC-FAILOVER * Informative Reference RFC3456 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Reference DRAFT-AIELLO-DHC-APPLIANCE-CLASS * Normative Reference RFC3527 * Reference DRAFT-LINTON-ARCP * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Normative Reference DRAFT-ZI-DHC-AGENT-REQUEST-MULTI-POOL * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Normative Reference DRAFT-DHANKINS-DHCPINFORM-CLARIFY * Normative Reference DRAFT-IETF-DHC-DHCPINFORM-CLARIFY * Normative Reference DRAFT-LEMON-DHCPV4-RELAY-ENCAPSULATION * Normative Reference DRAFT-IETF-DHC-DHCPV4-RELAY-ENCAPSULATION * Informative Reference DRAFT-IETF-DHC-TOPO-CONF RFC3046: DHCP Relay Agent Information Option (14 pages) * Reference BCP9 * Possible Reference BCP11 * Reference RFC2026 * Reference BCP14 * Possible Reference RFC2434 * Reference RFC2401 * Reference RFC2132 * Reference BCP26 * Reference RFC2131 * Updates RFC6607 * Reference RFC3118 * Reference DRAFT-IETF-DHC-FAILOVER * Informative Reference RFC3456 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Reference RFC3256 * Normative Reference RFC4388 * Reference DRAFT-KINNEAR-AGENT-VPN-ID * Reference DRAFT-KINNEAR-AGENT-SUBNET-SELECTION * Normative Reference RFC3527 * Normative Reference DRAFT-IETF-DHC-AGENT-VPN-ID * Normative Reference RFC6607 * Informative Reference DRAFT-SCHULZRINNE-SIPPING-SOS * Reference DRAFT-DROMS-AGENTOPT-8021X * Normative Reference RFC4014 * Normative Reference RFC4030 * Reference DRAFT-POLK-DHCP-LOC-INSERTION * Reference DRAFT-LINTON-ARCP * Reference DRAFT-POLK-DHCP-GEO-LOC-OPTION * Reference DRAFT-DROMS-DHCP-RELAY-AGENT-IPSEC * Reference DRAFT-POLK-GEOPRIV-LOC-OBJECT-SEMANTICS * Reference DRAFT-JOHNSON-DHC-SERVER-OVERRIDE * Reference DRAFT-JOHNSON-DHC-SUBSCRIBER-ID * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Normative Reference RFC3993 * Normative Reference RFC5107 * Possible Reference RFC3790 * Informative Reference RFC3679 * Normative Reference DRAFT-IETF-IPSEC-DHCP-OVER-IKE-DHCPD * Normative Reference DRAFT-IETF-DHC-RELAY-AGENT-AUTH * Normative Reference RFC3825 * Informative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Normative Reference DRAFT-IETF-DHC-RELAY-AGENT-IPSEC * Reference DRAFT-RENTSCHLER-DHC-DISCOVERY * Reference DRAFT-RENTSCHLER-DHC-INTERFACE-OPT * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Reference DRAFT-SHEN-DHC-BLOCK-ALLOC * Normative Reference RFC4562 * Informative Reference RFC3942 * Normative Reference DRAFT-STAPP-DHC-VENDOR-SUBOPTION * Informative Reference DRAFT-SENTHIL-DHC-V4RELAY-MIB * Normative Reference RFC4243 * Informative Reference DRAFT-DROMS-DHC-V6-RELAYOPT * Normative Reference DRAFT-VOLZ-DHC-DHCPV6-REMOTEID * Reference DRAFT-CLAUSEN-MANET-ADDRESS-AUTOCONF * Informative Reference DRAFT-OHBA-MOBOPTS-MPA-FRAMEWORK * Informative Reference DRAFT-IETF-DHC-V6-RELAY-RADIUS * Normative Reference RFC4649 * Normative Reference DRAFT-POLK-GEOPRIV-DHC-GEO-LCI-UPSTREAM * Informative Reference RFC4947 * Informative Reference DRAFT-OHBA-MOBOPTS-MPA-IMPLEMENTATION * Normative Reference DRAFT-ZI-DHC-AGENT-REQUEST-MULTI-POOL * Normative Reference DRAFT-BOURDAIS-DHCP-CLUSTER * Reference DRAFT-DECNODDER-DHC-RAI-UNICAST * Reference DRAFT-WADHWA-GSMP-L2CONTROL-CONFIGURATION * Informative Reference RFC4679 * Normative Reference DRAFT-ROSEN-SOS-PHONEBCP * Normative Reference DRAFT-SZENG-DHC-DHCPV6-ERO * Normative Reference RFC4994 * Normative Reference DRAFT-KINNEAR-DHC-RELAY-AGENT-FLAGS * Normative Reference RFC5010 * Reference DRAFT-JOSHI-DHCP-LEASE-QUERY-EXT * Reference DRAFT-LAI-MIP4-PROXY-NAT-TRAVERSAL * Informative Reference DRAFT-IETF-AUTOCONF-STATEMENT * Normative Reference DRAFT-IETF-PANA-PANAOVERDSL * Informative Reference DRAFT-THOMSON-GEOPRIV-3825BIS * Informative Reference RFC5692 * Reference DRAFT-KURAPATI-DHC-RELAY-CHAINING-DHCPV4 * Reference DRAFT-JOSHI-DHC-LAYER2-RELAY-AGENT * Informative Reference DRAFT-PRUSS-DHCP-AUTH-DSL * Informative Reference RFC6320 * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Normative Reference RFC5844 * Normative Reference DRAFT-POLK-GEOPRIV-DHCP-LBYR-URI-OPTION * Normative Reference DRAFT-IETF-GEOPRIV-DHCP-LBYR-URI-OPTION * Informative Reference RFC5515 * Informative Reference RFC6252 * Informative Reference RFC7227 * Informative Reference DRAFT-THOMSON-GEOPRIV-HELD-MEASUREMENTS * Normative Reference RFC7105 * Reference DRAFT-JOSHI-DHC-L2RA * Normative Reference DRAFT-IETF-DHC-L2RA * Normative Reference DRAFT-STAPP-DHC-RELAY-ID * Reference DRAFT-KURAPATI-DHC-L2RA-EXTENSIONS * Reference DRAFT-IETF-DHC-L2RA-EXTENSIONS * Reference DRAFT-KURAPATI-DHC-LEASEQUERY-BY-REMOTE-ID * Normative Reference RFC6148 * Normative Reference DRAFT-VINOKOUR-BFD-DHCP * Normative Reference RFC6925 * Reference DRAFT-DTV-DHC-DHCPV4-BULK-LEASEQUERY * Normative Reference RFC6926 * Informative Reference DRAFT-MILES-DHC-DHCPV6-LDRA * Normative Reference DRAFT-KINNEAR-DHC-DHCPV4-BULK-LEASEQUERY * Normative Reference DRAFT-DHANKINS-DHCPINFORM-CLARIFY * Normative Reference DRAFT-IETF-DHC-DHCPINFORM-CLARIFY * Reference DRAFT-HUANG-DHCP-SU * Normative Reference DRAFT-POLK-GEOPRIV-DHC-GEOELEMENT-SHAPE-OPTION * Informative Reference DRAFT-LI-DHC-SIMPLE-DSL-AUTH * Informative Reference RFC6225 * Informative Reference RFC6221 * Normative Reference DRAFT-HUANG-DHC-RELAY-PS * Normative Reference DRAFT-WANG-DHC-LDN-OPTION * Normative Reference DRAFT-BAJKO-ARCBAND-SHAPE * Informative Reference DRAFT-ZHENG-DHC-RELAY-AGENT-STACKING * Informative Reference DRAFT-HUANG-DHC-MULTIPLE-RELAY-AGENTS-OPTION * Normative Reference DRAFT-SARIKAYA-INT-AREA-PREFIX-DELEGATION * Normative Reference DRAFT-SARIKAYA-INTAREA-PREFIX-DELEGATION * Normative Reference DRAFT-LIYZ-TRILL-REQS-MLT2UNI-OPT * Normative Reference DRAFT-LEMON-DHCPV4-RELAY-ENCAPSULATION * Normative Reference DRAFT-ASATI-DHC-RELAY-AGENT-CONFIG * Informative Reference DRAFT-CUI-PCP-SUBSCRIBER-IDENTIFICATION * Normative Reference DRAFT-IETF-DHC-DHCPV4-RELAY-ENCAPSULATION * Informative Reference RFC6934 * Informative Reference RFC6788 * Informative Reference DRAFT-GUNDAVELLI-NETEXT-ACCESS-NETWORK-OPTION * Informative Reference RFC6757 * Normative Reference DRAFT-HU-DHC-DHCPV6-FOR-DUAL-STACK-HOSTS * Informative Reference RFC6632 * Normative Reference DRAFT-CUI-SOFTWIRE-DHCP-OVER-TUNNEL * Normative Reference DRAFT-BI-DHC-OPEXTENSIONS * Informative Reference DRAFT-BI-DHC-SEC-OPTION * Normative Reference DRAFT-CUI-DHC-DHCPV4-OVER-IPV6 * Normative Reference DRAFT-IETF-DHC-DHCPV4-OVER-IPV6 * Normative Reference DRAFT-RPCW-PCP-PMIPV6-SERV-DISCOVERY * Informative Reference DRAFT-MCCANN-DMM-FLATARCH * Normative Reference DRAFT-WU-DHC-PORT-SET-OPTION * Normative Reference DRAFT-IETF-DHC-ACCESS-NETWORK-IDENTIFIER * Normative Reference DRAFT-SUN-DHC-DHCPV6-OPT-V4CONFIG * Normative Reference DRAFT-CHEN-PCP-SIPTO-SERV-DISCOVERY * Informative Reference DRAFT-GUNDAVELLI-NETEXT-RFC6757BIS * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Reference DRAFT-SBOYAPATI-DHCP-RELAY-CHAINING-DHCPV4 * Normative Reference DRAFT-JIANG-DHC-SEDHCPV4 * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY RFC3074: DHC Load Balancing Algorithm (10 pages) * Reference BCP14 * Possible Reference STD1 * Reference RFC2119 * Reference RFC2131 * Reference DRAFT-IETF-DHC-FAILOVER * Informative Reference RFC3456 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Normative Reference RFC3539 * Reference DRAFT-IETF-DHC-LDAP-SCHEMA * Reference DRAFT-IETF-DHC-DHCPV6-LOADB * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Normative Reference DRAFT-BOURDAIS-DHCP-CLUSTER * Informative Reference DRAFT-KINNEAR-DHC-RELAY-AGENT-FLAGS * Informative Reference RFC5010 * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-REQUIREMENTS * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-DESIGN * Normative Reference DRAFT-KOSTUR-DHC-LOADBV6 * Normative Reference DRAFT-IETF-DHC-DHCPV6-LOAD-BALANCING RFC3118: Authentication for DHCP Messages (17 pages) * Reference RFC1305 * Reference RFC2219 * Reference RFC3046 * Reference RFC1321 * Reference RFC2104 * Possible Reference RFC2434 * Reference RFC2132 * Possible Reference RFC2119 * Reference BCP26 * Reference RFC2131 * Normative Reference RFC3315 * Normative Reference RFC3456 * Reference DRAFT-GUPTA-DHCP-AUTH * Reference DRAFT-HORNSTEIN-DHC-KERBAUTH * Informative Reference RFC3442 * Reference RFC3203 * Informative Reference RFC3495 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Reference DRAFT-ABOBA-DHC-MINI * Informative Reference RFC4702 * Informative Reference RFC4703 * Normative Reference RFC3397 * Normative Reference RFC4388 * Normative Reference RFC4173 * Normative Reference DRAFT-DUPONT-MIPV6-AAA * Informative Reference RFC3396 * Reference DRAFT-GUTTMAN-DHC-MDNS-ENABLE * Possible Reference RFC3527 * Informative Reference RFC6607 * Reference DRAFT-GUTTMAN-SVRLOC-RFC2610BIS * Informative Reference RFC4014 * Normative Reference DRAFT-LEVKOWETZ-DHC-MIP-FA * Normative Reference DRAFT-IETF-DHC-MIPADVERT-OPT * Reference DRAFT-LEE-PPVPN-CE-AUTO-CONFIG * Normative Reference DRAFT-IETF-DHC-HOST-OPTION-CONSIDERATIONS * Normative Reference RFC4174 * Informative Reference RFC4030 * Informative Reference DRAFT-BAKKE-DHC-SNMP-TRAP * Reference DRAFT-OHBA-PANA-POTLS * Normative Reference RFC3634 * Reference DRAFT-LINTON-ARCP * Reference DRAFT-DROMS-DHCP-RELAY-AGENT-IPSEC * Reference DRAFT-JOHNSON-DHC-SERVER-OVERRIDE * Reference DRAFT-JOHNSON-DHC-SUBSCRIBER-ID * Reference DRAFT-JOHNSON-DHC-SUBNET-ALLOC * Informative Reference RFC6656 * Normative Reference DRAFT-SCHULZRINNE-GEOPRIV-DHCP-CIVIL * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Informative Reference RFC3993 * Informative Reference RFC3594 * Informative Reference RFC5107 * Possible Reference RFC3792 * Normative Reference DRAFT-RICHARDSON-DHC-AUTH-SIG0 * Informative Reference DRAFT-IETF-DHC-RELAY-AGENT-AUTH * Normative Reference RFC3825 * Informative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Informative Reference DRAFT-ABOBA-DHC-NAD-IPV4 * Reference DRAFT-TSCHOFENIG-PANA-BOOTSTRAP-RFC3118 * Reference DRAFT-LITTLEFIELD-DHCP-VENDOR * Normative Reference DRAFT-IETF-DHC-AUTH-SIGZERO * Normative Reference RFC4676 * Informative Reference RFC4436 * Informative Reference DRAFT-IETF-DHC-RELAY-AGENT-IPSEC * Informative Reference RFC3925 * Reference DRAFT-VOLZ-DHC-RAPIDREPLY-OPT * Informative Reference RFC4361 * Reference DRAFT-RENTSCHLER-DHC-DISCOVERY * Informative Reference DRAFT-VIJAY-DHC-OPT-EXTRBOOT * Normative Reference DRAFT-SENTHIL-DHC-PROXYSERVER-OPT * Informative Reference RFC4039 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference DRAFT-LEMON-DHCPV4-TO-V6-ID-TRANS * Informative Reference DRAFT-STAPP-DHC-VENDOR-SUBOPTION * Normative Reference DRAFT-DANIEL-DHC-IPV6IN4-OPT * Informative Reference DRAFT-OHBA-PANA-FRAMEWORK * Informative Reference DRAFT-IETF-DHC-PROXYSERVER-OPT * Informative Reference DRAFT-IETF-DHC-OPT-EXTRBOOT * Normative Reference DRAFT-YEGIN-EAP-BOOT-RFC3118 * Normative Reference DRAFT-CHOWN-DHC-DUAL-STACK * Informative Reference RFC4477 * Informative Reference DRAFT-IAB-IDENTITIES * Informative Reference DRAFT-DANIEL-DHC-DHCPV4-TEP-CONF * Informative Reference RFC4339 * Informative Reference DRAFT-CADAR-DHC-OPT-IMAP * Informative Reference RFC4243 * Informative Reference RFC4907 * Informative Reference DRAFT-IETF-DHC-DHCPV6-CLARIFY-AUTH * Informative Reference DRAFT-OHBA-MIP6-BOOT-ARCH-DHCP * Normative Reference DRAFT-PARENT-V6TC-PROTOCOL-EXPLORATION * Informative Reference RFC5859 * Informative Reference DRAFT-TSCHOFENIG-ENROLL-BOOTSTRAPPING-SAML * Informative Reference DRAFT-YANAGIYA-APL-BOOT * Normative Reference DRAFT-POLK-GEOPRIV-DHC-GEO-LCI-UPSTREAM * Normative Reference DRAFT-POLK-NEWTON-ECRIT-ARCH-CONSIDERATIONS * Normative Reference DRAFT-POLK-DHC-URI * Reference DRAFT-FORTE-DHC-PASSIVE-DAD * Normative Reference DRAFT-BOURDAIS-DHCP-CLUSTER * Informative Reference DRAFT-DANIEL-DHC-MIHIS-OPT * Normative Reference DRAFT-POLK-DHC-EMERGENCY-DIALSTRING-OPTION * Informative Reference DRAFT-TEMPLIN-AUTOCONF-NETLMM-DHCP * Normative Reference DRAFT-KINNEAR-DHC-RELAY-AGENT-FLAGS * Normative Reference RFC5010 * Reference DRAFT-JOSHI-DHCP-LEASE-QUERY-EXT * Normative Reference DRAFT-POLK-ECRIT-DHC-EMERGENCY-DIALSTRING-OPTION * Normative Reference DRAFT-POLK-DHC-ECRIT-LOST-SERVER-URI * Normative Reference DRAFT-POLK-DHC-ECRIT-URI-PSAP-ESRP * Normative Reference DRAFT-ROSEN-ECRIT-FRAMEWORK * Normative Reference DRAFT-RAM-DHC-DHCPV6-DIAM-APP * Normative Reference DRAFT-RAM-DHC-DHCPV6-AAKEY * Informative Reference RFC5071 * Normative Reference DRAFT-ZHAO-DHC-USER-AUTHENTICATION * Normative Reference DRAFT-WINTERBOTTOM-GEOPRIV-HELD-DHCP-DISCOVERY * Informative Reference DRAFT-THOMSON-GEOPRIV-HELD-UNAPTR * Normative Reference RFC6881 * Normative Reference DRAFT-THOMSON-GEOPRIV-3825BIS * Reference DRAFT-KURAPATI-DHC-RELAY-CHAINING-DHCPV4 * Reference DRAFT-JOSHI-DHC-LAYER2-RELAY-AGENT * Normative Reference DRAFT-DROMS-DHC-CONTAINER-OPT * Normative Reference DRAFT-IETF-DHC-CONTAINER-OPT * Informative Reference DRAFT-THOMSON-GEOPRIV-LIS-DISCOVERY * Informative Reference RFC5986 * Informative Reference DRAFT-ABOBA-IP-CONFIG * Informative Reference DRAFT-PRUSS-DHCP-AUTH-DSL * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Normative Reference DRAFT-POLK-GEOPRIV-DHCP-LBYR-URI-OPTION * Normative Reference DRAFT-IETF-GEOPRIV-DHCP-LBYR-URI-OPTION * Possible Reference DRAFT-BAJKO-MOS-DHCP-OPTIONS * Normative Reference DRAFT-KRISHNAN-DHC-NDC-OPTION * Normative Reference DRAFT-MELIA-MIPSHOP-MSTP-SOLUTION * Normative Reference RFC5677 * Informative Reference RFC5505 * Reference DRAFT-JOSHI-DHC-L2RA * Reference DRAFT-KURAPATI-DHC-L2RA-EXTENSIONS * Reference DRAFT-IETF-DHC-L2RA-EXTENSIONS * Normative Reference RFC6148 * Normative Reference DRAFT-VINOKOUR-BFD-DHCP * Normative Reference RFC5678 * Informative Reference DRAFT-DUPONT-MEXT-DHAADHARMFUL * Normative Reference DRAFT-VINOKOUR-DHCP-RECONFIGURE-OPTION * Normative Reference RFC6926 * Informative Reference DRAFT-SALOWEY-DHC-EAPKEY-3118 * Informative Reference DRAFT-VOLZ-DHC-DHCPV4-VENDOR-MESSAGE * Informative Reference DRAFT-IETF-DHC-DHCPV4-VENDOR-MESSAGE * Informative Reference DRAFT-DHANKINS-DHCPINFORM-CLARIFY * Informative Reference DRAFT-MIYATA-BEHAVE-PREFIX64 * Informative Reference RFC5887 * Informative Reference DRAFT-IETF-DHC-DHCPINFORM-CLARIFY * Normative Reference DRAFT-MELIA-DHC-PCO * Normative Reference RFC6153 * Normative Reference DRAFT-MILES-DHC-FORCERENEW-KEY * Normative Reference DRAFT-SUN-MIF-ROUTE-CONFIG-DHCP6 * Possible Reference DRAFT-BRZOZOWSKI-DHCP-EAP-ANALYSIS * Informative Reference DRAFT-LI-DHC-SIMPLE-DSL-AUTH * Normative Reference RFC6225 * Normative Reference RFC6704 * Normative Reference DRAFT-TEMPLIN-INTAREA-VET * Informative Reference DRAFT-WU-HOKEY-LDN-DISCOVERY * Possible Reference DRAFT-WANG-DHC-LDN-OPTION * Informative Reference DRAFT-LI-SAVI-SKEY * Normative Reference DRAFT-BAJKO-ARCBAND-SHAPE * Normative Reference DRAFT-TSOU-NETWORK-CONFIGURATION-PROBLEM-STATEMENT * Normative Reference DRAFT-GUO-SOFTWIRE-AUTO-GRE * Informative Reference DRAFT-JJMB-DHC-EAP-AUTH-ANALYSIS * Informative Reference DRAFT-TSOU-OPSAWG-NETWORK-CONFIGURATION * Informative Reference DRAFT-IETF-OPSAWG-AUTOMATED-NETWORK-CONFIGURATION * Normative Reference DRAFT-LEMON-DHCPV4-RELAY-ENCAPSULATION * Normative Reference DRAFT-IETF-DHC-DHCPV4-RELAY-ENCAPSULATION * Normative Reference DRAFT-SCHOENW-OPSAWG-NM-DHC * Normative Reference DRAFT-BI-DHC-OPEXTENSIONS * Normative Reference DRAFT-XU-DHC-CADHCP * Normative Reference DRAFT-BI-DHC-SEC-OPTION * Possible Reference DRAFT-LIU-DHC-3GPP-OPTION * Possible Reference DRAFT-LIU-DHC-HO * Normative Reference RFC4776 * Informative Reference DRAFT-ZHOU-DHC-IBC * Informative Reference DRAFT-CAO-DHC-ANQP-OPTION * Normative Reference DRAFT-BHANDARI-DHC-ACCESS-NETWORK-IDENTIFIER * Informative Reference DRAFT-CAO-CAPWAP-EAP * Informative Reference DRAFT-IETF-DHC-ACCESS-NETWORK-IDENTIFIER * Normative Reference DRAFT-ORR-DHCP-DNS-SD-OPTIONS * Informative Reference DRAFT-ZHANG-OPSAWG-CAPWAP-EAP * Informative Reference DRAFT-ZHANG-OPSAWG-CAPWAP-CDS * Informative Reference DRAFT-CAO-NSC-RTG-UPDATE * Informative Reference DRAFT-CAO-SFC-CONTROL-ORCHESTRATION * Informative Reference DRAFT-HZHWM-START-TLS-FOR-DNS * Informative Reference DRAFT-IETF-HOMENET-HNCP * Informative Reference DRAFT-HZHWM-DPRIVE-START-TLS-FOR-DNS * Normative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Reference DRAFT-SBOYAPATI-DHCP-RELAY-CHAINING-DHCPV4 * Normative Reference DRAFT-JIANG-DHC-SEDHCPV4 RFC3203: DHCP reconfigure extension (6 pages) * Reference RFC3118 * Reference BCP14 * Possible Reference STD1 * Reference RFC2119 * Reference RFC2131 * Updates RFC6704 * Informative Reference RFC3456 * Normative Reference DRAFT-IETF-DHC-SERVER-MIB * Reference DRAFT-SHOCKEY-IPP2IFAX * Reference DRAFT-SHOCKEY-IPP2IFAX-GOALS * Informative Reference RFC5227 * Informative Reference RFC6656 * Reference DRAFT-DIMITRI-ZOSPF * Informative Reference DRAFT-IETF-DHC-IMPLEMENTATION * Informative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Reference DRAFT-RENTSCHLER-DHC-DISCOVERY * Reference DRAFT-RENTSCHLER-DHC-INTERFACE-OPT * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Reference DRAFT-FORTE-DHC-PASSIVE-DAD * Normative Reference DRAFT-TEMPLIN-AUTOCONF-NETLMM-DHCP * Normative Reference DRAFT-VINOKOUR-DHCP-RECONFIGURE-OPTION * Normative Reference DRAFT-BOULTON-DISPATCH-CONFERENCE-CONTROL-PACKAGE * Informative Reference RFC5887 * Normative Reference DRAFT-MILES-DHC-FORCERENEW-KEY * Informative Reference DRAFT-LI-DHC-SIMPLE-DSL-AUTH * Normative Reference RFC6704 * Normative Reference DRAFT-PFISTER-HOMENET-PREFIX-ASSIGNMENT RFC3256: The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-option (5 pages) * Reference RFC3046 * Possible Reference STD1 * Possible Reference RFC2119 * Reference BCP14 * Informative Reference DRAFT-FAIR-IPDVB-AR * Informative Reference DRAFT-IETF-DHC-RELAY-AGENT-IPSEC * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference DRAFT-SENTHIL-DHC-V4RELAY-MIB * Informative Reference RFC4947 * Normative Reference DRAFT-ROSEN-SIMPLE-WATCHER-COUNT RFC3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (101 pages) * Normative Reference RFC2464 * Normative Reference RFC2460 * Normative Reference RFC2461 * Normative Reference RFC2462 * Normative Reference RFC2104 * Normative Reference BCP14 * Possible Reference STD1 * Normative Reference RFC3041 * Normative Reference RFC1035 * Possible Reference RFC2434 * Normative Reference STD37 * Normative Reference RFC1305 * Possible Reference RFC826 * Normative Reference RFC1321 * Normative Reference RFC2373 * Informative Reference RFC2136 * Normative Reference STD6 * Informative Reference RFC2132 * Normative Reference BCP26 * Informative Reference RFC2131 * Possible Reference RFC2526 * Normative Reference RFC3118 * Normative Reference RFC2401 * Updates RFC4361 * Updates RFC5494 * Updates RFC6221 * Updates RFC6422 * Updates RFC6644 * Updates RFC7083 * Normative Reference DRAFT-JIANG-DHC-SEDHCPV6 * Informative Reference DRAFT-LIU-V6OPS-DHCPV6-SLAAC-GUIDANCE * Normative Reference DRAFT-LIU-RUNNING-MULTIPLE-PREFIXES * Informative Reference DRAFT-IETF-DHC-V4CONFIGURATION * Informative Reference DRAFT-JIANG-CONFIG-NEGOTIATION-PS * Normative Reference DRAFT-LIU-OPSAREA-IPV6-RENUMBERING-GUIDELINES * Normative Reference DRAFT-IETF-SOFTWIRE-MAP-RADIUS * Informative Reference RFC3775 * Informative Reference DRAFT-WING-DHC-DNS-RECONFIGURE * Informative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Informative Reference DRAFT-IETF-6LO-BTLE * Normative Reference RFC7283 * Normative Reference RFC7341 * Normative Reference DRAFT-LEMON-DHC-TOPO-CONF * Normative Reference DRAFT-LEMON-DHC-INVENTORY * Normative Reference DRAFT-CSL-DHC-DHCPV6-UNKNOWN-MSG-3315UPDATE * Normative Reference DRAFT-SARIKAYA-DHC-VXLAN-MULTICAST * Normative Reference DRAFT-SCSKF-DHC-DHCPV4-OVER-DHCPV6 * Informative Reference RFC4795 * Normative Reference RFC4703 * Informative Reference RFC4701 * Informative Reference RFC4388 * Normative Reference RFC4173 * Normative Reference DRAFT-IETF-DHC-SEDHCPV6 * Informative Reference RFC7428 * Informative Reference DRAFT-IETF-V6OPS-DHCPV6-SLAAC-PROBLEM * Normative Reference RFC7217 * Normative Reference RFC6607 * Normative Reference RFC3723 * Normative Reference RFC3646 * Informative Reference RFC4058 * Normative Reference DRAFT-DUPONT-IPV6-IMEI * Normative Reference RFC3898 * Normative Reference DRAFT-IETF-DHC-DHCPV6-OPT-TIMECONFIG * Normative Reference RFC3319 * Normative Reference RFC4294 * Normative Reference RFC4472 * Normative Reference DRAFT-TEMPLIN-AEROLINK * Informative Reference RFC3776 * Normative Reference RFC3633 * Informative Reference RFC4215 * Informative Reference RFC5107 * Possible Reference RFC3790 * Possible Reference RFC3792 * Normative Reference RFC4241 * Informative Reference RFC5191 * Normative Reference RFC3736 * Normative Reference DRAFT-WKUMARI-DHC-CAPPORT * Informative Reference DRAFT-THALER-IPV6-NDPROXY * Informative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Informative Reference RFC4942 * Reference DRAFT-OHIRA-ASSIGN-SELECT-E2E-MULTIHOME * Normative Reference DRAFT-DROMS-NEMO-DHCPV6-PD * Normative Reference DRAFT-IETF-NEMO-DHCPV6-PD * Normative Reference RFC3904 * Normative Reference RFC4676 * Informative Reference RFC5006 * Normative Reference DRAFT-BOUND-DSTM-EXP * Informative Reference RFC4193 * Reference DRAFT-JUNG-MIPSHOP-STATEFUL-FMIPV6 * Informative Reference RFC3925 * Informative Reference DRAFT-IETF-PANA-IPSEC * Normative Reference RFC4057 * Informative Reference RFC3971 * Reference DRAFT-VOLZ-DHC-RAPIDREPLY-OPT * Informative Reference DRAFT-CHOWN-V6OPS-PORT-SCANNING-IMPLICATIONS * Reference DRAFT-CHA-MANET-EXTENDED-SUPPORT-GLOBALV6 * Normative Reference DRAFT-IETF-DHC-DHCPV6-OPT-NSS * Normative Reference RFC4361 * Informative Reference DRAFT-JINMEI-IPV6-RFC2462BIS * Normative Reference DRAFT-JANG-MIPV6-SMREG * Normative Reference DRAFT-VIJAY-DHC-DHCPV6-OPT-RBOOT * Normative Reference DRAFT-CHOWN-DHC-STATELESS-DHCPV6-RENUMBERING * Normative Reference DRAFT-VENAAS-DHC-LIFETIME * Normative Reference DRAFT-SAVOLA-V6OPS-CONFTUN-SETUP * Normative Reference DRAFT-LIUMIN-V6OPS-SILKROAD * Normative Reference DRAFT-IETF-DHC-DHCPV6-OPT-TZ * Normative Reference RFC4075 * Informative Reference DRAFT-VIJAY-IPV6-ICMP-REFRESH-OTHERCONF * Normative Reference DRAFT-VIJAY-DHC-DHCPV6-MCAST-RECONF * Informative Reference RFC4039 * Normative Reference DRAFT-VIJAY-DHC-DHCPV6-IPV6TRANS * Possible Reference DRAFT-HIBBS-DHC-CHANGES * Reference DRAFT-PAAKKONEN-ADDRESSING-HTR-MANET * Normative Reference DRAFT-DANIEL-DHC-DHCPV6-CTEP-OPT * Normative Reference DRAFT-LEMON-DHCPV4-TO-V6-ID-TRANS * Normative Reference DRAFT-RAFIEE-6MAN-SSAS * Reference DRAFT-OHIRA-MULTI6-MULTILINK-AUTO-PREFIX-ASSIGN * Normative Reference RFC6842 * Normative Reference DRAFT-OHBA-PANA-FRAMEWORK * Normative Reference DRAFT-IETF-DHC-DHCPV6-CTEP-OPT * Normative Reference DRAFT-IETF-DHC-DHCPV6-OPT-RBOOT * Normative Reference DRAFT-CHOWN-DHC-DUAL-STACK * Reference DRAFT-CADAR-DHC-DHCPV6-V4OPTIONS * Normative Reference RFC4192 * Informative Reference RFC4862 * Informative Reference RFC4477 * Informative Reference DRAFT-KEMPF-MIP6-BOOTSTRAP * Normative Reference RFC4242 * Normative Reference RFC4076 * Informative Reference RFC4429 * Normative Reference DRAFT-TRAN-MIDCOM-DHCPV6-OPTION * Informative Reference DRAFT-PAULKANDASAMY-MOBILEIP-NAI-BASED-HOME-ADDRES * Informative Reference DRAFT-TEMPLIN-V6OPS-IEMMEI * Informative Reference DRAFT-PALET-V6OPS-AUTO-TRANS * Reference DRAFT-YAN-DHC-DHCPV6-OPT-DNSZONE * Normative Reference DRAFT-IETF-DHC-DHCPV6-OPT-DNSDOMAIN * Normative Reference DRAFT-JANG-DHC-HAOPT * Normative Reference RFC4339 * Informative Reference RFC5072 * Normative Reference DRAFT-SHIN-DHC-DHCPV6-OPT-IPV4-PREFIX * Normative Reference DRAFT-JDURAND-ASSIGN-ADDR-IPV6-MULTICAST-DHCPV6 * Normative Reference DRAFT-CADAR-DHC-DHCPV6-OPT-EMAIL * Informative Reference DRAFT-NARAYANAN-DNA-BCP * Normative Reference DRAFT-CHOWDHURY-DHC-BCMCV6-OPTION * Informative Reference DRAFT-DALEY-MAGMA-SMLD-PROB * Normative Reference DRAFT-DANIEL-IPV6-RA-MO-FLAGS * Informative Reference DRAFT-TEMPLIN-V6V4INET * Normative Reference DRAFT-JINMEI-DHC-DHCPV6-CLARIFY-AUTH * Informative Reference RFC4980 * Informative Reference DRAFT-CHOWN-V6OPS-CAMPUS-TRANSITION * Informative Reference DRAFT-IETF-V6OPS-CAMPUS-TRANSITION * Informative Reference DRAFT-HARDIE-EMERGENCY-CALL-ROUTING * Informative Reference RFC4861 * Normative Reference DRAFT-VOLZ-DHC-DHCPV6-FQDN * Possible Reference RFC5226 * Reference DRAFT-EDDY-TLMARCH * Informative Reference DRAFT-TEMPLIN-IPVLX * Normative Reference DRAFT-ASADULLAH-V6OPS-BB-DEPLOYMENT-SCENARIOS * Normative Reference RFC4779 * Informative Reference DRAFT-IRTF-NMRG-AN-GAP-ANALYSIS * Normative Reference RFC4852 * Informative Reference DRAFT-SAVOLA-MBONED-ADDRARCH * Informative Reference RFC4941 * Normative Reference RFC4957 * Normative Reference RFC4704 * Informative Reference DRAFT-VANDEVELDE-V6OPS-NAP * Reference DRAFT-BORST-MIP6API * Informative Reference RFC4907 * Reference DRAFT-HIROTAKA-DHC-SOURCE-ADDRESS-SELECTION-OPT * Normative Reference DRAFT-ARIFUMI-IPV6-ND-SOURCE-ADDRESS-SELECT * Normative Reference DRAFT-CHOWDHURY-DHC-MIP6-AGENTOP * Normative Reference DRAFT-IETF-DHC-DHCPV6-CLARIFY-AUTH * Normative Reference DRAFT-DROMS-DHC-V6-RELAYOPT * Normative Reference DRAFT-OHBA-MIP6-BOOT-ARCH-DHCP * Informative Reference DRAFT-CHOWN-V6OPS-RENUMBER-THINKABOUT * Normative Reference DRAFT-ARKKO-MULTI6DT-FAILURE-DETECTION * Normative Reference DRAFT-ARIFUMI-MULTI6-SAS-POLICY-DIST * Normative Reference DRAFT-MADANAPALLI-DHCPV6-ANYCAST * Informative Reference RFC6308 * Normative Reference DRAFT-IETF-IPV6-RA-MO-FLAGS * Informative Reference RFC4389 * Normative Reference DRAFT-PARENT-V6TC-PROTOCOL-EXPLORATION * Normative Reference DRAFT-VOLZ-DHC-DHCPV6-REMOTEID * Normative Reference DRAFT-VOLZ-DHC-DHCPV6-SUBID * Normative Reference DRAFT-CADAR-DHC-DHCPV6-OPT-SMTP * Normative Reference RFC4280 * Normative Reference DRAFT-IETF-DHC-BCMCV6-OPTION * Normative Reference DRAFT-IETF-DHC-SOA-OPTION * Normative Reference RFC7421 * Normative Reference DRAFT-ARIFUMI-IPV6-SAS-POLICY-DIST * Normative Reference DRAFT-IETF-MULTI6-FAILURE-DETECTION * Informative Reference DRAFT-JDURAND-IPV6-MULTICAST-RA * Informative Reference DRAFT-NARAYANAN-DNA-HOSTS-BCP * Normative Reference DRAFT-IETF-DHC-V6-RELAY-RADIUS * Informative Reference DRAFT-YANAGIYA-IATYPE-MIP6BOOT * Normative Reference DRAFT-RAFIEE-6MAN-RA-PRIVACY * Normative Reference DRAFT-JDURAND-ALL-DRS-ARE-RPS * Normative Reference DRAFT-OGAWA-FHOPT * Informative Reference DRAFT-LAOUITI-MANET-OLSR-ADDRESS-AUTOCONF * Informative Reference DRAFT-STIEMERLING-IPDVB-CONFIG * Informative Reference RFC4864 * Normative Reference RFC4580 * Normative Reference RFC4649 * Normative Reference DRAFT-REDDY-DHCPV6-OPT-DSTM-EXP * Informative Reference DRAFT-IETF-DNA-HOSTS * Informative Reference DRAFT-PENTLAND-DNA-PROTOCOL * Normative Reference DRAFT-SURAJ-DHCPV4-PAA-OPTION * Reference DRAFT-MILOUCHEVA-UDLR-MIPV6 * Informative Reference DRAFT-RUFFINO-MANET-AUTOCONF-MULTIGW * Normative Reference DRAFT-FUJISAKI-DHC-ADDR-SELECT-OPT * Normative Reference DRAFT-FUJISAKI-6MAN-ADDR-SELECT-OPT * Normative Reference RFC4947 * Informative Reference DRAFT-FACCIN-MIH-INFOSERV * Informative Reference DRAFT-SHIN-DSTM-PORTS * Possible Reference DRAFT-OTA-DHC-AUTH-CHAP * Normative Reference DRAFT-MGLT-DNSOP-SEARCH-LIST-PROCESSING * Informative Reference RFC5080 * Informative Reference DRAFT-VENAAS-DHC-DUAL-STACK-MERGE * Normative Reference RFC5534 * Normative Reference DRAFT-IETF-SHIM6-APPLICABILITY * Normative Reference DRAFT-DROMS-DHC-DHCPV6-RFC868-SERVERS * Updates RFC7283 * Reference DRAFT-FORTE-DHC-PASSIVE-DAD * Informative Reference DRAFT-IETF-DHC-DUAL-STACK-MERGE * Normative Reference RFC5192 * Normative Reference DRAFT-YUCHI-DHC-HOMEAGENT-OPTION * Informative Reference DRAFT-MOHAN-NFLM-PROTO * Informative Reference DRAFT-GIARETTA-NETLMM-PROTOCOL * Normative Reference DRAFT-DEVARAPALLI-MIP6-IKEV1-BOOTSTRAP * Informative Reference DRAFT-LEE-DNSOP-RESOLVER-WELLKNOWN-IPV6ADDR * Informative Reference DRAFT-PENTLAND-DNA-PROTOCOL3 * Normative Reference DRAFT-BOURDAIS-DHCP-CLUSTER * Normative Reference RFC6611 * Informative Reference DRAFT-IETF-MIP6-RADIUS * Reference DRAFT-AKIYOSHI-NETLMM-PROTOCOL * Normative Reference DRAFT-DROMS-DHC-DHCPV6-AGENTOPT-DELEGATE * Informative Reference DRAFT-ARIFUMI-IPV6-POLICY-DIST * Normative Reference DRAFT-DANIEL-6LOWPAN-SECURITY-ANALYSIS * Informative Reference RFC4925 * Normative Reference DRAFT-IETF-DHC-DHCPV6-AGENTOPT-DELEGATE * Normative Reference DRAFT-TOUTAIN-SOFTWIRE-POINT6BOX * Normative Reference DRAFT-LEAR-DHC-TIMEZONE-OPTION * Normative Reference RFC4833 * Informative Reference DRAFT-DANIEL-DHC-MIHIS-OPT * Informative Reference DRAFT-VANDEVELDE-V6OPS-ADDCON * Informative Reference RFC5375 * Informative Reference RFC6775 * Informative Reference DRAFT-WENIGER-AUTOCONF-PDAD-OLSR * Normative Reference DRAFT-IETF-DHC-DHCPV6-RFC868-SERVERS * Informative Reference DRAFT-IETF-DNA-PROTOCOL * Normative Reference DRAFT-NAVALI-IP6-OVER-NETMIP4 * Informative Reference DRAFT-NORDMARK-SHIM6-ESD * Normative Reference DRAFT-CHOWDHURY-NETMIP6 * Informative Reference DRAFT-JEE-16NG-PS-GOALS * Informative Reference DRAFT-ASAEDA-MMUSIC-IMG-ARCH * Normative Reference DRAFT-JANG-MIPSHOP-NHDISC * Reference DRAFT-PSKIM-LINK-SPECIFIED-COA * Normative Reference DRAFT-MINABURO-HC-TUNNELING * Normative Reference DRAFT-IETF-NETLMM-MN-AR-IF * Reference DRAFT-WANGHUI-NETLMM-PROTOCOL * Normative Reference DRAFT-EVANS-DHC-DHCPV6-RECONFIGURE-REBIND * Normative Reference RFC6644 * Normative Reference DRAFT-SZENG-DHC-DHCPV6-ERO * Normative Reference RFC4994 * Normative Reference DRAFT-MULE-CABLELABS-DOCSIS3-IPV6 * Reference DRAFT-MENZEL-UDLR-MIPV6 * Normative Reference DRAFT-TEMPLIN-AUTOCONF-NETLMM-DHCP * Normative Reference RFC5268 * Normative Reference RFC5558 * Normative Reference DRAFT-JANG-MIP6-HIOPT * Normative Reference RFC6610 * Reference DRAFT-MADANAPALLI-IPV6-OVER-802.16-IPV6CS * Normative Reference DRAFT-BRZOZOWSKI-DHC-DHCVP6-LEASEQUERY * Normative Reference DRAFT-IETF-DHC-DHCVP6-LEASEQUERY * Normative Reference DRAFT-KUWABARA-SOFTWIRE-IPV6-VIA-L2TPV2 * Normative Reference DRAFT-BHARATIA-MIP6-GEN-EXT * Normative Reference RFC5571 * Informative Reference RFC5157 * Possible Reference DRAFT-RIEGEL-16NG-IP-OVER-ETH-OVER-80216 * Informative Reference DRAFT-HANCOCK-MIPSHOP-GIST-FOR-MIH * Reference DRAFT-HEPWORTH-MIPSHOP-MIH-DESIGN-CONSIDERATIONS * Normative Reference DRAFT-RAM-DHC-DHCPV6-DIAM-APP * Normative Reference DRAFT-RAM-DHC-DHCPV6-AAKEY * Informative Reference DRAFT-BACCELLI-AUTOCONF-STATEMENT * Informative Reference DRAFT-IETF-AUTOCONF-STATEMENT * Normative Reference DRAFT-VOLZ-DHC-DHCPV6-SRSN-OPTION * Normative Reference DRAFT-IETF-DHC-DHCPV6-SRSN-OPTION * Normative Reference RFC5007 * Normative Reference DRAFT-TSCHOFENIG-DHC-LOST-DISCOVERY * Normative Reference DRAFT-POLK-ECRIT-DHC-LOST-DISCOVERY * Normative Reference RFC5223 * Reference DRAFT-MADANAPALLI-16NG-SUBNET-MODEL-ANALYSIS * Normative Reference DRAFT-ZHAO-DHC-DHCPV6-RELAY-LINK-SELECTION * Informative Reference RFC4903 * Normative Reference DRAFT-MORAND-PANA-PANAOVERDSL * Normative Reference DRAFT-IETF-PANA-PANAOVERDSL * Reference DRAFT-DHANKINS-ATOMIC-DHCP * Reference DRAFT-STENBERG-PD-ROUTE-MAINTENANCE * Normative Reference RFC4968 * Normative Reference DRAFT-SAUMYA-MIP6-BOOTSTRAP * Normative Reference DRAFT-SARIKAYA-DHC-PROXYAGENT * Normative Reference DRAFT-HUANG-NEMO-MN-RO * Informative Reference DRAFT-BAKER-V6OPS-L3-MULTIHOMING-ANALYSIS * Informative Reference RFC5121 * Normative Reference DRAFT-SARIKAYA-16NG-PREFIX-DELEGATION * Normative Reference DRAFT-WINTERBOTTOM-GEOPRIV-HELD-DHCP-DISCOVERY * Normative Reference DRAFT-WINTERBOTTOM-GEOPRIV-HELD-IDENTITY-EXTENSIONS * Normative Reference RFC6155 * Normative Reference RFC6881 * Reference DRAFT-QIU-MIP6-FRIENDLY-FIREWALL * Normative Reference DRAFT-SGUNDAVE-MIP6-PROXYMIP6 * Normative Reference RFC5213 * Normative Reference DRAFT-THOMSON-GEOPRIV-3825BIS * Normative Reference RFC5692 * Normative Reference DRAFT-DROMS-DHC-CONTAINER-OPT * Normative Reference DRAFT-IETF-DHC-CONTAINER-OPT * Normative Reference DRAFT-VOLZ-DHC-DHCPV6-VENDOR-MESSAGE * Normative Reference DRAFT-IETF-DHC-DHCPV6-VENDOR-MESSAGE * Normative Reference DRAFT-THOMSON-GEOPRIV-LIS-DISCOVERY * Normative Reference RFC5986 * Normative Reference DRAFT-TEMPLIN-AUTOCONF-MULTILINK * Normative Reference DRAFT-TEMPLIN-AUTOCONF-VIRTUAL * Normative Reference DRAFT-RUSSERT-NETLMM-HMAP * Reference DRAFT-MUNAKATA-SIP-PRIVACY-CLARIFIED * Informative Reference DRAFT-ABOBA-IP-CONFIG * Normative Reference DRAFT-BAGNULO-PSHIM6 * Informative Reference DRAFT-PRUSS-DHCP-AUTH-DSL * Informative Reference RFC6320 * Informative Reference DRAFT-KRISHNAN-IPV6-RESERVED-IIDS * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Normative Reference DRAFT-CALHOUN-DHC-CAPWAP-AC-OPTION * Normative Reference DRAFT-SARIKAYA-NETLMM-PREFIX-DELEGATION * Normative Reference DRAFT-IETF-GEOPRIV-DHCP-LBYR-URI-OPTION * Informative Reference DRAFT-ERONEN-IPSEC-IKEV2-IPV6-CONFIG * Informative Reference RFC5739 * Normative Reference DRAFT-DAMIC-NETLMM-PMIP6-IND-DISCOVER * Normative Reference RFC6092 * Informative Reference DRAFT-BAKER-SAVA-OPERATIONAL * Informative Reference RFC5379 * Informative Reference RFC5779 * Normative Reference DRAFT-VEIKKOLAINEN-SIPPING-APP-CONFIG * Normative Reference DRAFT-JIANG-SENDCGAEXT-CGA-CONFIG * Normative Reference RFC5417 * Normative Reference DRAFT-BAJKO-MOS-DHCP-OPTIONS * Normative Reference DRAFT-KRISHNAN-DHC-NDC-OPTION * Informative Reference DRAFT-WBEEBEE-ON-LINK-AND-OFF-LINK-DETERMINATION * Normative Reference RFC7227 * Normative Reference DRAFT-MELIA-MIPSHOP-MSTP-SOLUTION * Normative Reference RFC5677 * Informative Reference RFC5505 * Normative Reference DRAFT-STAPP-DHC-DHCPV6-BULK-LEASEQUERY * Normative Reference RFC5460 * Normative Reference RFC6059 * Normative Reference RFC7105 * Normative Reference DRAFT-GAYRAUD-DHCPV6-NTP-OPT * Informative Reference DRAFT-BAKER-6MAN-MULTIPREFIX-DEFAULT-ROUTE * Normative Reference DRAFT-BAKER-SAVA-IMPLEMENTATION * Normative Reference DRAFT-POPOVICIU-DHC-CERTIFICATE-OPT * Possible Reference DRAFT-VAN-BEIJNUM-CGA-DHCP-INTERACTION * Informative Reference DRAFT-BERNARDOS-AUTOCONF-SOLUTION-SPACE * Informative Reference DRAFT-MUHANNA-NETLMM-MULTIHOMING-SUPPORT * Normative Reference DRAFT-KRISHNAN-INTAREA-RA-DHCP * Informative Reference DRAFT-CHOWN-V6OPS-ROGUE-RA * Informative Reference RFC6104 * Normative Reference RFC7051 * Normative Reference DRAFT-DENG-DHC-SERVICE-IDENTIFIERS * Informative Reference DRAFT-STENBERG-V6OPS-PD-ROUTE-MAINTENANCE * Normative Reference RFC6434 * Informative Reference RFC5453 * Normative Reference DRAFT-STAPP-DHC-RELAY-ID * Normative Reference DRAFT-XIA-DHC-HOST-GEN-ID * Normative Reference DRAFT-SARIKAYA-MEXT-HOMELINK-PREFIX-DELEGATION * Informative Reference DRAFT-DENG-GMP-PS * Normative Reference DRAFT-DUPONT-MEXT-DHCRELAY * Normative Reference DRAFT-VINOKOUR-BFD-DHCP * Normative Reference RFC6784 * Informative Reference RFC6282 * Informative Reference DRAFT-SARIKAYA-MEXT-RELAY-DHCPV6PD * Informative Reference DRAFT-SARIKAYA-MEXT-PREFIX-DELEGATION * Informative Reference DRAFT-MCPHERSON-SAVI-THREAT-SCOPE * Informative Reference DRAFT-DESPRES-V6OPS-APBP * Normative Reference RFC5678 * Informative Reference RFC5942 * Normative Reference RFC5908 * Informative Reference DRAFT-ZHOU-DIME-4OVER6-PROVISIONING * Normative Reference DRAFT-DROMS-MEXT-NEMO-PD * Normative Reference RFC6276 * Informative Reference DRAFT-CHA-IPV6-RA-MO * Informative Reference RFC6275 * Normative Reference DRAFT-LOURDELET-RADEXT-IPV6-DHCP * Informative Reference DRAFT-THOMSON-HELD-GRIP * Normative Reference DRAFT-SHEFFER-DHC-INITIAL-RANDOM * Informative Reference DRAFT-WBEEBEE-IPV6-CPE-ROUTER * Normative Reference RFC6204 * Informative Reference DRAFT-THOMSON-GEOPRIV-HELD-GRIP * Normative Reference DRAFT-V6OPS-KAIPPALLIMALIL-IPV6-BBNET * Normative Reference DRAFT-KAIPPALLIMALIL-V6OPS-IPV6-BBNET * Reference DRAFT-ZHAO-MEXT-MNP-IKEV2 * Informative Reference DRAFT-NEUMANN-NETLMM-INTER-DOMAIN * Normative Reference DRAFT-MILES-DHC-DHCPV6-LDRA * Normative Reference DRAFT-JIANG-DHC-SECURE-DHCPV6 * Normative Reference DRAFT-IETF-DHC-SECURE-DHCPV6 * Normative Reference DRAFT-IETF-PKIX-PRQP * Reference DRAFT-BI-SAVI-CSA * Reference DRAFT-BOOT-AUTOCONF-BRDP * Normative Reference DRAFT-DHANKINS-SOFTWIRE-TUNNEL-OPTION * Normative Reference RFC6334 * Reference DRAFT-YOUSAF-IETF-NEMO-NERON * Normative Reference RFC5970 * Normative Reference DRAFT-SARIKAYA-MEXT-BU-PREFIXDELEGATION * Informative Reference DRAFT-DESPRES-SAM * Normative Reference RFC5494 * Informative Reference RFC5887 * Normative Reference DRAFT-SAVOLAINEN-MIF-DNS-SERVER-SELECTION * Normative Reference DRAFT-XIA-NETLMM-LMA-DISCOVERY * Normative Reference DRAFT-JIANG-CSI-DHCPV6-CGA-PS * Informative Reference DRAFT-CHOWN-ADDR-SELECT-CONSIDERATIONS * Informative Reference DRAFT-PATIL-DHC-APN-ATTACHTYPE-OPTIONS * Normative Reference DRAFT-ZIMMER-DHC-DHCPV6-REMOTE-BOOT-OPTIONS * Informative Reference DRAFT-BLANCHET-MIF-PROBLEM-STATEMENT * Informative Reference RFC6418 * Normative Reference DRAFT-THALER-IPV6-SAF * Informative Reference DRAFT-THOMSON-GEOPRIV-RES-GW-LIS-DISCOVERY * Informative Reference RFC7216 * Informative Reference DRAFT-HUNT-DHCPV6-CLARIFY-MRC * Normative Reference RFC5568 * Normative Reference DRAFT-DEC-DHCPV6-ROUTE-OPTION * Normative Reference RFC6731 * Normative Reference DRAFT-MELIA-DHC-PCO * Informative Reference RFC7298 * Normative Reference DRAFT-BOUCADAIR-BEHAVE-IPV6-PORTRANGE * Normative Reference DRAFT-YANG-MIF-REQ * Normative Reference DRAFT-DROMS-DHC-DHCPV6-DEFAULT-ROUTER * Informative Reference DRAFT-LOURDELET-RADEXT-IPV6-ACCESS * Normative Reference RFC6153 * Informative Reference DRAFT-MILES-DHC-FORCERENEW-KEY * Normative Reference DRAFT-SUN-MIF-ADDRESS-POLICY-DHCP6 * Normative Reference DRAFT-SUN-MIF-ROUTE-CONFIG-DHCP6 * Normative Reference DRAFT-SARIKAYA-MIF-DHCPV6SOLUTION * Informative Reference DRAFT-BRZOZOWSKI-DHCP-EAP-ANALYSIS * Possible Reference DRAFT-WAKIKAWA-NETEXT-PMIP6-NEMO-SUPPORT * Possible Reference DRAFT-BI-SAVI-CPS * Normative Reference DRAFT-XU-V6OPS-HYBRID-PLATFORM-PS * Normative Reference DRAFT-JIANG-CSI-CGA-CONFIG-DHCPV6 * Informative Reference RFC6139 * Normative Reference DRAFT-BOUCADAIR-DHCPV6-SHARED-ADDRESS-OPTION * Normative Reference DRAFT-RABIL-DHC-DHCPV6-XMLCONFIG * Normative Reference DRAFT-XIA-MEXT-HIOPTV4 * Normative Reference RFC6225 * Informative Reference DRAFT-KAIPPALLIMALIL-SAVI-DHCP-PD * Normative Reference DRAFT-LIU-MULTIMOB-MULTICAST-RECEIVER-MOBILITY * Normative Reference DRAFT-GUO-SOFTWIRE-SC-DISCOVERY * Normative Reference RFC6704 * Normative Reference DRAFT-TEMPLIN-INTAREA-VET * Normative Reference DRAFT-XU-V6OPS-HYBRID-FRAMEWORK * Normative Reference DRAFT-SARIKAYA-NETEXT-PREFIX-DELEGATION * Normative Reference RFC6221 * Normative Reference DRAFT-DONLEY-IPV6-CPE-RTR-USE-CASES-AND-REQS * Normative Reference DRAFT-WU-HOKEY-LDN-DISCOVERY * Normative Reference RFC6440 * Normative Reference DRAFT-WANG-DHC-LDN-OPTION * Possible Reference DRAFT-YOURTCHENKO-RA-DHCPV6-COMPARISON * Informative Reference DRAFT-WILLIAMS-MIF-PROBLEM-SCENARIOS * Informative Reference DRAFT-KO-MIF-SECURITY-CONSIDERATIONS * Normative Reference DRAFT-TOWNSLEY-IPV6-6RD * Normative Reference DRAFT-DALEY-IPV6-NONAT6 * Informative Reference DRAFT-AXU-ADDR-SEL * Normative Reference DRAFT-WBEEBEE-V6OPS-IPV6-CPE-ROUTER-BIS * Informative Reference RFC6272 * Normative Reference DRAFT-SARIKAYA-APLUSP-DSMIP * Normative Reference DRAFT-IETF-CSI-DHCPV6-CGA-PS * Normative Reference DRAFT-JIANG-DHC-ADDR-REGISTRATION * Informative Reference DRAFT-LEE-SOFTWIRE-6RD-UDP * Normative Reference DRAFT-TSOU-NETWORK-CONFIGURATION-PROBLEM-STATEMENT * Informative Reference DRAFT-IETF-6MAN-ADDR-SELECT-CONSIDERATIONS * Normative Reference DRAFT-GUO-SOFTWIRE-AUTO-GRE * Informative Reference DRAFT-KO-MIF-THREAT-ANALYSIS * Normative Reference RFC6324 * Normative Reference DRAFT-BERNARDOS-AUTOCONF-ADDRESSING-MODEL * Normative Reference RFC7039 * Normative Reference DRAFT-JJMB-DHC-DHCPV6-REDUNDANCY-CONSIDER * Possible Reference DRAFT-BI-SAVI-DHCP * Normative Reference DRAFT-IETF-SAVI-DHCP * Informative Reference DRAFT-JJMB-DHC-EAP-AUTH-ANALYSIS * Reference DRAFT-AHN-AUTOCONF-ADDRESSPOOL * Normative Reference DRAFT-SARIKAYA-INT-AREA-PREFIX-DELEGATION * Informative Reference DRAFT-WING-BEHAVE-DNS64-CONFIG * Normative Reference RFC6630 * Normative Reference DRAFT-JIANG-DHC-CGA-CONFIG-DHCPV6 * Possible Reference DRAFT-XU-IPV6-RA-DHCP-SERVER-OPTION * Normative Reference DRAFT-SARIKAYA-INTAREA-PREFIX-DELEGATION * Informative Reference DRAFT-KORHONEN-V6OPS-3GPP-EPS * Informative Reference RFC6459 * Informative Reference DRAFT-GUNDAVELLI-6MAN-IPV6-ND-VENDOR-SPEC-OPTIONS * Informative Reference RFC6653 * Informative Reference DRAFT-CHEN-NTPS-RA-OPT * Normative Reference DRAFT-JIANG-6MAN-ADDR-REGISTRATION-REQ * Normative Reference DRAFT-GUO-SOFTWIRE-6RD-IPV6-CONFIG * Possible Reference DRAFT-BAGNULO-SAVI-ANALYSIS * Normative Reference DRAFT-DESPRES-SOFTWIRE-SAM * Informative Reference RFC6911 * Normative Reference DRAFT-HUI-6LOWPAN-DHCP * Normative Reference RFC6011 * Normative Reference DRAFT-ESPI-IETF-MIPSHOP-PROFMIPV6 * Normative Reference DRAFT-LEMON-DHCPV6-RELAY-SUPPLIED-OPTIONS * Informative Reference RFC6106 * Normative Reference DRAFT-BPW-SOFTWIRE-PCP-DHCP * Normative Reference DRAFT-BPW-PCP-DHCP * Normative Reference DRAFT-BAKER-SAVI-ONE-IMPLEMENTATION-APPROACH * Normative Reference DRAFT-NARTEN-DHC-DUID-UUID * Normative Reference RFC6355 * Normative Reference DRAFT-IETF-DHC-DHCPV6-ACTIVE-LEASEQUERY * Informative Reference DRAFT-TSOU-OPSAWG-NETWORK-CONFIGURATION * Informative Reference DRAFT-IETF-OPSAWG-AUTOMATED-NETWORK-CONFIGURATION * Normative Reference DRAFT-KORHONEN-DHC-PD-EXCLUDE * Normative Reference RFC6603 * Normative Reference DRAFT-DROMS-DHC-DHCPV6-IANA * Normative Reference DRAFT-HERBERG-AUTOCONF-YAAP * Normative Reference DRAFT-MRUGALSKI-REMOTE-DHCPV6 * Normative Reference DRAFT-MRUGALSKI-SERVER-DAD-DHCPV6 * Informative Reference DRAFT-CHROBOCZEK-AHCP * Informative Reference DRAFT-LEMON-DHCPV4-RELAY-ENCAPSULATION * Informative Reference DRAFT-LEE-V4V6TRAN-PROBLEM * Normative Reference RFC6422 * Possible Reference DRAFT-JANKIEWICZ-V6OPS-V4V6BIBLIO * Normative Reference DRAFT-ASATI-DHC-RELAY-AGENT-CONFIG * Normative Reference DRAFT-MONGAZON-EMU-IP-MODES-EAP * Normative Reference RFC6519 * Normative Reference DRAFT-YEH-DHC-DHCPV6-PREFIX-POOL-OPT * Normative Reference DRAFT-MADI-DHC-DHCPV6-PSAC * Informative Reference DRAFT-IETF-DHC-DHCPV4-RELAY-ENCAPSULATION * Informative Reference DRAFT-KORHONEN-BEHAVE-NAT64-LEARN-ANALYSIS * Normative Reference DRAFT-HU-PPPEXT-IPV6CP-REQUIREMENTS * Informative Reference DRAFT-LIN-SAVI-ROAMING-ND * Normative Reference DRAFT-MRW-DVNE-FW * Normative Reference DRAFT-DESPRES-SOFTWIRE-4RD * Normative Reference DRAFT-SCHOENW-OPSAWG-NM-DHC * Normative Reference DRAFT-PERKINS-AUTOCONF-LEGHOST * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference DRAFT-BI-SAVI-MIX * Normative Reference RFC7078 * Informative Reference DRAFT-FARRER-DHC-SHARED-ADDRESS-LEASE * Normative Reference RFC6788 * Normative Reference DRAFT-AN-SAVI-MIB * Normative Reference DRAFT-IETF-MIF-DHCPV6-ROUTE-OPTION * Normative Reference DRAFT-JIANG-IPV6-SITE-RENUM-GUIDELINE * Informative Reference DRAFT-BOOT-BRDP-FRAMEWORK * Normative Reference DRAFT-ZHOU-NETEXT-PD-PMIP * Normative Reference DRAFT-HU-DHC-DHCPV6-FOR-DUAL-STACK-HOSTS * Normative Reference DRAFT-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-IETF-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference RFC7084 * Normative Reference DRAFT-JOSHI-DHC-DHCPV6-AGGR-ROUTE-OPT * Normative Reference DRAFT-LIU-IPV6-RENUM-CONFLICTS * Informative Reference DRAFT-KORHONEN-MIF-RA-OFFLOAD * Informative Reference RFC6632 * Normative Reference DRAFT-DESPRES-INTAREA-4RD * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-SUBOPTIONS * Possible Reference DRAFT-JJMB-V6OPS-COMCAST-IPV6-EXPERIENCES * Informative Reference RFC6706 * Normative Reference DRAFT-BI-SAVI-WLAN * Informative Reference DRAFT-FLING-V6OPS-HYBRID-BRIDGED-ROUTED * Normative Reference RFC6853 * Normative Reference DRAFT-IETF-DHC-CGA-CONFIG-DHCPV6 * Normative Reference RFC6964 * Normative Reference DRAFT-IETF-DHC-HOST-GEN-ID * Informative Reference DRAFT-DEC-6MAN-RS-ACCESS-HARMFUL * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-REQUIREMENTS * Normative Reference DRAFT-TEMPLIN-ISUPDATE * Informative Reference DRAFT-BAKER-FUN-MULTI-ROUTER * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-4RD * Normative Reference DRAFT-JIANG-6RENUM-ENTERPRISE * Normative Reference RFC6879 * Normative Reference DRAFT-LIU-6RENUM-GAP-ANALYSIS * Normative Reference RFC7010 * Informative Reference DRAFT-CHOWN-6MAN-TOKENISED-IPV6-IDENTIFIERS * Normative Reference DRAFT-MURAKAMI-SOFTWIRE-4RD * Normative Reference DRAFT-CHOWN-HOMENET-ARCH * Normative Reference DRAFT-MOUTON-MIF-DHCPV6-DRLO * Normative Reference DRAFT-DESPRES-SOFTWIRE-4RD-U * Normative Reference RFC7148 * Normative Reference RFC6629 * Normative Reference DRAFT-HALWASIA-DHC-DHCPV6-HARDWARE-ADDR-OPT * Normative Reference DRAFT-LIU-DHC-3GPP-OPTION * Normative Reference DRAFT-LIU-DHC-HO * Informative Reference DRAFT-KELSEY-INTAREA-MESH-LINK-ESTABLISHMENT * Informative Reference DRAFT-BAKER-HOMENET-PREFIX-ASSIGNMENT * Informative Reference DRAFT-CHAKRABARTI-HOMENET-PREFIX-ALLOC * Normative Reference DRAFT-REDDY-MIF-DHCPV6-PRECEDENCE-OPS * Informative Reference DRAFT-CARPENTER-6RENUM-STATIC-PROBLEM * Normative Reference DRAFT-WING-BEHAVE-DHCPV6-RECONFIGURE * Normative Reference DRAFT-QIN-SOFTWIRE-MULTICAST-PREFIX-OPTION * Normative Reference DRAFT-BHANDARI-DHC-CLASS-BASED-PREFIX * Normative Reference DRAFT-CARPENTER-V6OPS-ICP-GUIDANCE * Normative Reference DRAFT-XLI-SOFTWIRE-DIVI-PD * Normative Reference DRAFT-BCX-BEHAVE-ADDRESS-FMT-EXTENSION * Informative Reference DRAFT-HAZEYAMA-WIDECAMP-IPV6-ONLY-EXPERIENCE * Reference DRAFT-YAN-MEXT-DNSMIP * Informative Reference DRAFT-LI-SOFTWIRE-DSLITE-INTRA-DOMAIN * Normative Reference RFC7031 * Normative Reference DRAFT-HADDAD-HOMENET-GATEWAY-VISIBILITY * Normative Reference DRAFT-MDT-SOFTWIRE-MAP-DHCP-OPTION * Normative Reference DRAFT-MA-NETEXT-PMIP-HANDOVER * Normative Reference RFC7291 * Normative Reference DRAFT-DROMS-DHC-DHCPV6-MAXSOLRT-UPDATE * Normative Reference DRAFT-TOWNSLEY-V6OPS-6RD-SUNSETTING * Normative Reference DRAFT-IETF-DHC-DHCPV6-TUNNEL * Normative Reference DRAFT-DROMS-DHC-DHCPV6-SOLMAXRT-UPDATE * Informative Reference DRAFT-GONT-6MAN-MANAGING-SLAAC-POLICY * Normative Reference DRAFT-MA-NETEXT-PDHMIP * Informative Reference DRAFT-BCD-6MAN-NTP-SERVER-RA-OPT * Normative Reference RFC7113 * Normative Reference DRAFT-JIANG-SOFTWIRE-MAP-RADIUS * Updates RFC7227 * Normative Reference DRAFT-MDT-SOFTWIRE-MAP-ENCAPSULATION * Normative Reference RFC4776 * Informative Reference DRAFT-CHKPVC-ENTERPRISE-INCREMENTAL-IPV6 * Normative Reference DRAFT-RPCW-PCP-PMIPV6-SERV-DISCOVERY * Reference DRAFT-JAEHWOON-DMM-PMIPV6 * Normative Reference DRAFT-CUI-INTAREA-464XLAT-PREFIX-DHCP * Normative Reference DRAFT-KORHONEN-DMM-LOCAL-PREFIX * Possible Reference DRAFT-YANG-DHC-IPV4-DIS * Normative Reference DRAFT-YEH-DHC-DHCPV6-AUTHORIZATION-OPT * Informative Reference DRAFT-CHEN-PCP-MOBILE-DEPLOYMENT * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-DESIGN * Informative Reference DRAFT-VYNCKE-OPSEC-V6 * Normative Reference DRAFT-GMANN-HOMENET-RELAY-AUTOCONF * Normative Reference DRAFT-TROAN-DHC-DHCPV6-STATEFUL-ISSUES * Normative Reference DRAFT-IETF-SOFTWIRE-MULTICAST-PREFIX-OPTION * Informative Reference DRAFT-DONLEY-V6OPS-CE-ROUTER-DESIGN * Normative Reference DRAFT-YEH-RADEXT-EXT-DUAL-STACK-ACCESS * Normative Reference DRAFT-MRUGALSKI-SOFTWIRE-DHCPV4-OVER-V6-OPTION * Normative Reference RFC6883 * Normative Reference DRAFT-GONT-OPSEC-IPV6-HOST-SCANNING * Normative Reference RFC7037 * Normative Reference DRAFT-IETF-DHC-ADDR-REGISTRATION * Normative Reference DRAFT-GONT-OPSEC-DHCPV6-SHIELD * Normative Reference DRAFT-IETF-SOFTWIRE-4RD * Normative Reference DRAFT-ZHOU-DHC-IBC * Informative Reference DRAFT-GEORGE-DHC-REQUEST-RETRANSMISSION * Informative Reference DRAFT-RIBIERE-SAVI-PREFIX-GUARD * Normative Reference DRAFT-MGLT-NAMING-DELEGATION * Normative Reference RFC6939 * Normative Reference DRAFT-IETF-DHC-DHCPV6-FAILOVER-DESIGN * Normative Reference DRAFT-JIANG-SEMANTIC-PREFIX * Normative Reference DRAFT-JIANG-SOFTWIRE-4RD-RADIUS * Informative Reference DRAFT-CAO-DHC-ANQP-OPTION * Normative Reference DRAFT-HU-SOFTWIRE-MULTICAST-RADIUS-EXT * Normative Reference DRAFT-LIU-6RENUM-DHCPV6-SLAAC-SWITCHING * Informative Reference DRAFT-SUN-FMC-USE-CASE * Normative Reference DRAFT-CHEN-SOFTWIRE-CE-NON-PD * Normative Reference DRAFT-YASUDA-CACHE-SERVER-SELECTION * Informative Reference DRAFT-PERREAULT-SUNSET4-NOIPV4 * Normative Reference DRAFT-BHANDARI-DHC-ACCESS-NETWORK-IDENTIFIER * Normative Reference DRAFT-KRISHNAN-6MAN-RESILIENT-RS * Normative Reference DRAFT-MGLT-HOMENET-NAMING-DELEGATION * Informative Reference RFC6866 * Normative Reference DRAFT-MGLT-HOMENET-NAMING-ARCHITECTURE-DHC-OPTIONS * Possible Reference DRAFT-LEIBA-COTTON-IANA-5226BIS * Normative Reference DRAFT-IETF-SOFTWIRE-MAP-DHCP * Informative Reference RFC7381 * Normative Reference DRAFT-BOUCADAIR-DHC-TRIGGERED-RECONFIGURE * Informative Reference DRAFT-IETF-OPSEC-V6 * Normative Reference DRAFT-KOSTUR-DHC-LOADBV6 * Informative Reference DRAFT-NCNIPC-SAVI-SIP * Normative Reference DRAFT-IETF-DHC-DHCPV6-LOAD-BALANCING * Normative Reference DRAFT-BOUCADAIR-DHC-ADDRESS-NAME-ENCODING * Normative Reference DRAFT-IETF-DHC-DHCPV6-PREFIX-POOL-OPT * Normative Reference RFC6977 * Normative Reference DRAFT-PENTIKOUSIS-DECADE-DISCOVERY * Normative Reference DRAFT-ZHOU-DHC-GRE-OPTION * Informative Reference DRAFT-CHAKRABARTI-NORDMARK-6MAN-EFFICIENT-ND * Informative Reference DRAFT-KORHONEN-V6OPS-RFC3316BIS * Normative Reference DRAFT-ZHU-DHC-VLAN-ID-OPTION * Normative Reference DRAFT-JIANG-V6OPS-SEMANTIC-PREFIX * Possible Reference DRAFT-YANG-SUNSET4-WEAKEN-DHCP * Normative Reference DRAFT-OGUD-DHC-UDP-TIME-OPTION * Informative Reference DRAFT-SUN-SEMANTIC-USECASE * Normative Reference DRAFT-CHEN-SUNSET4-TRAFFIC-MIGRATION * Informative Reference DRAFT-BOOT-HOMENET-BRDP * Informative Reference DRAFT-BAKER-6RENUM-OSS-RENUMBERING * Normative Reference DRAFT-IETF-6MAN-RESILIENT-RS * Informative Reference DRAFT-CARPENTER-6RENUM-NEXT-STEPS * Informative Reference RFC7066 * Normative Reference DRAFT-IETF-OPSEC-DHCPV6-SHIELD * Normative Reference DRAFT-IETF-OPSEC-IPV6-HOST-SCANNING * Normative Reference RFC7083 * Normative Reference DRAFT-WINTERS-HOMENET-SPER-INTERACTION * Normative Reference DRAFT-ASATI-DHC-IPV6-AUTOCONFIG-ADDRESS-TRACKING * Normative Reference DRAFT-IETF-DHC-ACCESS-NETWORK-IDENTIFIER * Normative Reference DRAFT-ORR-DHCP-DNS-SD-OPTIONS * Normative Reference DRAFT-GRUNDEMANN-HOMENET-HIPNET * Informative Reference DRAFT-SUN-V6OPS-SEMANTIC-USECASE * Informative Reference DRAFT-LIU-BONICA-DHCPV6-SLAAC-PROBLEM * Normative Reference DRAFT-XUE-DHC-LOCATION-OPTION * Normative Reference DRAFT-SUN-DHC-DHCPV6-OPT-V4CONFIG * Normative Reference DRAFT-PETRESCU-RELAY-ROUTE-PD-PROBLEM * Informative Reference DRAFT-IETF-HOMENET-HNCP * Informative Reference DRAFT-LEE-SOFTWIRE-LW4OVER6-FAILOVER * Normative Reference DRAFT-DOI-ROLL-MPL-PARAMETER-CONFIGURATION * Normative Reference DRAFT-MGLT-DHC-PUBLIC-AUTHORITATIVE-SERVER-OPTION * Informative Reference DRAFT-HAZEYAMA-SUNSET4-DNS-A-FILTER * Normative Reference DRAFT-GRUNDEMANN-HIPNET * Informative Reference DRAFT-ANIPKO-MIF-MPVD-ARCH * Normative Reference DRAFT-LIU-V6OPS-RUNNING-MULTIPLE-PREFIXES * Normative Reference DRAFT-LIU-SOFTWIRE-LW4OVER6-DHCP-DEPLOYMENT * Informative Reference DRAFT-COOPER-6MAN-IPV6-ADDRESS-GENERATION-PRIVACY * Informative Reference DRAFT-SMITH-V6OPS-CE-DHCPV6-TRANSPARENCY * Normative Reference DRAFT-BOUCADAIR-RFC6153-UPDATE * Informative Reference DRAFT-IETF-SUNSET4-NOIPV4 * Normative Reference DRAFT-SARIKAYA-PROXY-VXLAN * Normative Reference DRAFT-RAGHUVANSHI-DHC-DHCPV6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-JIANG-DHC-STATELESS-RECONFIGURATION * Normative Reference DRAFT-IETF-6MAN-IPV6-ADDRESS-GENERATION-PRIVACY * Normative Reference DRAFT-MA-V6OPS-ROUTER-TEST * Normative Reference DRAFT-MGLT-HOMENET-DNSSEC-VALIDATOR-DHC-OPTIONS * Normative Reference DRAFT-FA-NETCONF-DHCPV6-OPTION * Informative Reference DRAFT-LIU-BONICA-V6OPS-DHCPV6-SLAAC-PROBLEM * Informative Reference DRAFT-CAO-NSC-RTG-UPDATE * Normative Reference DRAFT-KKB-MPVD-DHCP-SUPPORT * Normative Reference DRAFT-IETF-DHC-TOPO-CONF * Normative Reference DRAFT-JIANG-INTAREA-CONET-GAP-ANALYSIS * Informative Reference DRAFT-IETF-MIF-MPVD-ARCH * Normative Reference DRAFT-IETF-DHC-CONN-STATUS * Normative Reference DRAFT-PFISTER-HOMENET-PREFIX-ASSIGNMENT * Reference DRAFT-OTIS-DNSSD-MDNS-XLINK * Normative Reference DRAFT-CUI-V6OPS-LTE-LW4OVER6 * Informative Reference DRAFT-JIANG-NMRG-AN-GAP-ANALYSIS * Informative Reference DRAFT-FSC-DHC-DHCP4O6-SADDR-OPT * Informative Reference DRAFT-CAO-SFC-CONTROL-ORCHESTRATION * Informative Reference DRAFT-LIU-6MAN-DHCPV6-SLAAC-IMPLEMENTATION-GUIDE * Normative Reference DRAFT-SUN-SOFTWIRE-LW4OVER6-RADIUS * Normative Reference DRAFT-SARIKAYA-NVO3-DHC-VXLAN-MULTICAST * Normative Reference DRAFT-SARIKAYA-NVO3-DHC-VXLAN-CENTRALDIR-MAPPING * Normative Reference DRAFT-YOURTCHENKO-COLITTI-ND-REDUCE-MULTICAST * Normative Reference DRAFT-KKBG-MPVD-ID * Normative Reference DRAFT-TAHT-KELLEY-HUNT-DHCPV4-TO-SLAAC-NAMING * Normative Reference DRAFT-IETF-ROLL-MPL-PARAMETER-CONFIGURATION * Normative Reference DRAFT-SARIKAYA-DHC-DHCPV6-RAOPTIONS-SADR * Normative Reference DRAFT-CONET-AEON-GAP-ANALYSIS * Informative Reference DRAFT-FSC-SOFTWIRE-DHCP4O6-SADDR-OPT * Normative Reference DRAFT-DONLEY-DHC-CER-ID-OPTION * Normative Reference DRAFT-IETF-MIF-MPVD-DHCP-SUPPORT * Normative Reference DRAFT-IETF-MIF-MPVD-ID * Normative Reference DRAFT-JEONG-HOMENET-DEVICE-NAME-AUTOCONF * Normative Reference DRAFT-TEMPLIN-AEROENT * Normative Reference DRAFT-GONT-DHC-STABLE-PRIVACY-ADDRESSES * Informative Reference DRAFT-QUE-DHC-DNS-MULTI-DHCP-SERVERS * Informative Reference DRAFT-WANG-V6OPS-XLAT-PREFIX-DISCOVERY * Normative Reference DRAFT-IETF-HOMENET-NAMING-ARCHITECTURE-DHC-OPTIONS * Informative Reference DRAFT-CARPENTER-ANIMA-GDN-PROTOCOL * Informative Reference DRAFT-BARTH-HOMENET-HNCP-SECURITY-TRUST * Normative Reference DRAFT-IETF-DHC-DHCPV6-STATEFUL-ISSUES * Normative Reference DRAFT-SARIKAYA-NVO3-PROXY-VXLAN * Normative Reference DRAFT-KRISHNAN-DHC-DHCPV6-PRIVACY * Possible Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-ACTIVE-LEASEQUERY * Informative Reference DRAFT-CHEN-V6OPS-NFV-IPV6 * Normative Reference DRAFT-PERKINS-DMM-PRIVACY * Normative Reference DRAFT-PERKINS-DMM-4283MNIDS * Normative Reference DRAFT-SARIKAYA-DHC-6MAN-DHCPV6-SADR * Informative Reference DRAFT-IETF-V6OPS-CIDR-PREFIX * Normative Reference DRAFT-TEMPLIN-CLIENT-CLLAO * Possible Reference DRAFT-IETF-DHC-DHCP-PRIVACY * Normative Reference DRAFT-IETF-DHC-DHCPV6-PRIVACY * Informative Reference DRAFT-THALER-6LO-PRIVACY-ADDRS * Normative Reference DRAFT-IETF-DHC-STABLE-PRIVACY-ADDRESSES * Normative Reference DRAFT-HUITEMA-DHC-ANONYMITY-PROFILE * Normative Reference DRAFT-TEMPLIN-DHC-CLLAO-UPDATES * Normative Reference DRAFT-CUI-DHC-DHCPV6-YANG * Normative Reference DRAFT-MCCANN-DMM-PREFIXCOST * Informative Reference DRAFT-MOSES-DMM-DHCP-ONDEMAND-MOBILITY * Normative Reference DRAFT-YIU-DHC-DHCPV6-SA * Informative Reference DRAFT-HUITEMA-PRIVSEC-HARMFULNAME * Reference DRAFT-ZHANG-6MAN-SCALE-LARGE-DATACENTER * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-PRIVACY-MITIGATION RFC3396: Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4) (9 pages) * Updates RFC2131 * Informative Reference RFC3118 * Normative Reference RFC951 * Possible Reference STD1 * Informative Reference BCP11 * Normative Reference BCP14 * Normative Reference RFC2132 * Normative Reference RFC2131 * Reference DRAFT-GUPTA-DHCP-AUTH * Normative Reference RFC3442 * Normative Reference RFC3495 * Normative Reference RFC4702 * Normative Reference RFC3397 * Informative Reference RFC6656 * Informative Reference RFC4504 * Normative Reference DRAFT-SCHULZRINNE-GEOPRIV-DHCP-CIVIL * Reference DRAFT-VOLZ-DHC-EXTENDED-OPTIONCODES * Normative Reference DRAFT-TEMPLIN-ISATAP-DHCP * Reference DRAFT-IETF-DHC-EXTENDED-OPTIONCODES * Normative Reference RFC4676 * Normative Reference RFC3925 * Normative Reference DRAFT-VIJAY-DHC-OPT-EXTRBOOT * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Normative Reference DRAFT-IETF-DHC-PROXYSERVER-OPT * Normative Reference DRAFT-IETF-DHC-OPT-EXTRBOOT * Normative Reference DRAFT-TRAN-MIDCOM-DHCP-OPTION * Normative Reference DRAFT-CHOWDHURY-DHC-BCMCV4-OPTION * Normative Reference DRAFT-IETF-DHC-BCMCV4-OPTION * Normative Reference RFC4280 * Normative Reference DRAFT-SURAJ-DHCPV4-PAA-OPTION * Normative Reference DRAFT-MGLT-DNSOP-SEARCH-LIST-PROCESSING * Normative Reference DRAFT-POLK-DHC-URI * Informative Reference DRAFT-POLK-ECRIT-DHC-LOST-DISCOVERY * Normative Reference DRAFT-THOMSON-GEOPRIV-LIS-DISCOVERY * Informative Reference DRAFT-PRUSS-DHCP-AUTH-DSL * Possible Reference DRAFT-POLK-GEOPRIV-DHCP-LBYR-URI-OPTION * Normative Reference DRAFT-IETF-GEOPRIV-DHCP-LBYR-URI-OPTION * Normative Reference DRAFT-BAJKO-MOS-DHCP-OPTIONS * Normative Reference RFC5678 * Informative Reference DRAFT-VOLZ-DHC-DHCPV4-VENDOR-MESSAGE * Informative Reference DRAFT-IETF-DHC-DHCPV4-VENDOR-MESSAGE * Normative Reference RFC6731 * Possible Reference DRAFT-POLK-GEOPRIV-DHC-GEOELEMENT-SHAPE-OPTION * Informative Reference DRAFT-BRZOZOWSKI-DHCP-EAP-ANALYSIS * Normative Reference RFC6011 * Normative Reference DRAFT-BPW-PCP-DHCP * Normative Reference DRAFT-BI-DHC-OPEXTENSIONS * Informative Reference DRAFT-XU-DHC-CADHCP * Informative Reference DRAFT-BI-DHC-SEC-OPTION * Normative Reference RFC4776 RFC3442: The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4 (9 pages) * Updates RFC2132 * Informative Reference BCP11 * Normative Reference RFC3396 * Possible Reference STD1 * Informative Reference RFC1256 * Informative Reference RFC1058 * Normative Reference BCP14 * Possible Reference RFC950 * Informative Reference STD5 * Informative Reference RFC1878 * Informative Reference RFC3118 * Normative Reference RFC2132 * Normative Reference RFC2131 * Informative Reference RFC3456 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Normative Reference RFC4562 * Normative Reference DRAFT-TEMPLIN-AUTOCONF-NETLMM-DHCP * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference DRAFT-DEC-DHCPV6-ROUTE-OPTION * Informative Reference RFC6731 * Normative Reference DRAFT-AXU-ADDR-SEL * Informative Reference DRAFT-TROAN-MULTIHOMING-WITHOUT-NAT66 * Informative Reference DRAFT-IETF-V6OPS-MULTIHOMING-WITHOUT-NAT66 * Informative Reference DRAFT-V6OPS-MULTIHOMING-WITHOUT-NAT66 * Informative Reference RFC7157 * Informative Reference DRAFT-IETF-MIF-DHCPV6-ROUTE-OPTION * Normative Reference DRAFT-KORHONEN-MIF-RA-OFFLOAD * Informative Reference DRAFT-V6OPS-MULTIHOMING-WITHOUT-IPV6NAT * Informative Reference DRAFT-SARIKAYA-DHC-DHCPV6-RAOPTIONS-SADR * Informative Reference DRAFT-SARIKAYA-DHC-6MAN-DHCPV6-SADR * Informative Reference DRAFT-IETF-HOMENET-HNCP RFC3495: Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration (13 pages) * Informative Reference RFC3118 * Normative Reference RFC3396 * Normative Reference STD13 * Possible Reference RFC1035 * Normative Reference RFC1510 * Possible Reference RFC2434 * Normative Reference RFC2131 * Possible Reference STD1 * Normative Reference BCP26 * Normative Reference BCP14 * Normative Reference RFC3634 * Normative Reference RFC4682 * Normative Reference RFC3594 * Informative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Possible Reference DRAFT-SHIOMOTO-CCAMP-MPLS-GMPLS-INTERWORK-FMWK * Informative Reference DRAFT-FEDYK-GMPLS-ETHERNET-IVL * Informative Reference DRAFT-FEDYK-GMPLS-ETHERNET-PBT * Informative Reference DRAFT-VOLZ-DHC-3942-STATUS * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference DRAFT-GMPLS-ETHERNET-ARCH RFC3527: Link Selection sub-option for the Relay Agent Information Option for DHCPv4 (9 pages) * Normative Reference RFC3046 * Normative Reference RFC3011 * Informative Reference RFC951 * Possible Reference RFC3118 * Informative Reference RFC1542 * Informative Reference BCP11 * Normative Reference BCP14 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference RFC2131 * Informative Reference DRAFT-IETF-DHC-RELAY-AGENT-IPSEC * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference DRAFT-SENTHIL-DHC-V4RELAY-MIB * Informative Reference DRAFT-TEMPLIN-AUTOCONF-MULTILINK * Informative Reference DRAFT-TEMPLIN-AUTOCONF-VIRTUAL * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Normative Reference DRAFT-IETF-DHC-DHCPINFORM-CLARIFY * Normative Reference DRAFT-LEMON-DHCPV4-RELAY-ENCAPSULATION * Normative Reference DRAFT-IETF-DHC-DHCPV4-RELAY-ENCAPSULATION * Normative Reference DRAFT-CUI-DHC-DHCPV4-OVER-IPV6 * Normative Reference DRAFT-IETF-DHC-DHCPV4-OVER-IPV6 * Normative Reference DRAFT-WU-DHC-PORT-SET-OPTION * Normative Reference DRAFT-SUN-DHC-DHCPV6-OPT-V4CONFIG * Informative Reference DRAFT-IETF-DHC-TOPO-CONF * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY RFC3594: PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) Option (7 pages) * Informative Reference RFC2131 * Normative Reference RFC3495 * Informative Reference RFC3118 * Possible Reference BCP11 * Informative Reference RFC1510 * Normative Reference RFC2434 * Normative Reference BCP14 * Normative Reference RFC4682 * Informative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference DRAFT-SERVIN-V6OPS-MONITOR-DS-IPV6 * Informative Reference DRAFT-IETF-V6OPS-MONITOR-DS-IPV6 RFC3633: IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6 (19 pages) * Possible Reference BCP11 * Normative Reference RFC3162 * Normative Reference RFC2460 * Normative Reference RFC2461 * Normative Reference RFC3315 * Normative Reference BCP14 * Updates RFC6603 * Informative Reference DRAFT-STENBERG-HOMENET-DNSSDEXT-HYBRID-PROXY-OSPF * Normative Reference DRAFT-LIU-OPSAREA-IPV6-RENUMBERING-GUIDELINES * Informative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Informative Reference DRAFT-IETF-6LO-BTLE * Normative Reference RFC6607 * Informative Reference RFC6656 * Normative Reference RFC4241 * Informative Reference DRAFT-THALER-IPV6-NDPROXY * Reference DRAFT-OHIRA-ASSIGN-SELECT-E2E-MULTIHOME * Normative Reference DRAFT-DROMS-NEMO-DHCPV6-PD * Normative Reference DRAFT-IETF-NEMO-DHCPV6-PD * Normative Reference RFC3904 * Normative Reference DRAFT-SAVOLA-V6OPS-CONFTUN-SETUP * Normative Reference DRAFT-LIUMIN-V6OPS-SILKROAD * Reference DRAFT-OHIRA-MULTI6-MULTILINK-AUTO-PREFIX-ASSIGN * Informative Reference RFC4192 * Informative Reference DRAFT-TEMPLIN-V6OPS-IEMMEI * Normative Reference DRAFT-IETF-DHC-DHCPV6-OPT-DNSDOMAIN * Informative Reference RFC4339 * Normative Reference DRAFT-SHIN-DHC-DHCPV6-OPT-IPV4-PREFIX * Normative Reference DRAFT-JDURAND-ASSIGN-ADDR-IPV6-MULTICAST-DHCPV6 * Informative Reference DRAFT-TEMPLIN-V6V4INET * Possible Reference DRAFT-SANTESSON-SMIME-SCEXT * Informative Reference DRAFT-TEMPLIN-IPVLX * Normative Reference DRAFT-ASADULLAH-V6OPS-BB-DEPLOYMENT-SCENARIOS * Informative Reference DRAFT-IRTF-NMRG-AN-GAP-ANALYSIS * Reference DRAFT-THUBERT-NEMO-GLOBAL-HAHA * Informative Reference DRAFT-VANDEVELDE-V6OPS-NAP * Reference DRAFT-HIROTAKA-DHC-SOURCE-ADDRESS-SELECTION-OPT * Normative Reference DRAFT-ARIFUMI-IPV6-ND-SOURCE-ADDRESS-SELECT * Reference DRAFT-HUITEMA-MULTI6-ADDR-SELECTION * Reference DRAFT-RUFFINO-MANET-AUTOCONF-SCENARIOS * Informative Reference DRAFT-CHOWN-V6OPS-RENUMBER-THINKABOUT * Normative Reference DRAFT-ARIFUMI-MULTI6-SAS-POLICY-DIST * Reference DRAFT-KNIVETON-NEMO-PREFIX-DELEGATION * Informative Reference RFC4389 * Normative Reference DRAFT-PARENT-V6TC-PROTOCOL-EXPLORATION * Informative Reference DRAFT-VOLZ-DHC-DHCPV6-REMOTEID * Informative Reference DRAFT-VOLZ-DHC-DHCPV6-SUBID * Normative Reference DRAFT-ARIFUMI-IPV6-SAS-POLICY-DIST * Reference DRAFT-RUFFINO-CONN-SCENARIOS * Normative Reference DRAFT-JDURAND-ALL-DRS-ARE-RPS * Informative Reference RFC4864 * Informative Reference RFC4580 * Informative Reference RFC4649 * Normative Reference DRAFT-RUFFINO-MANET-AUTOCONF-MULTIGW * Reference DRAFT-IETF-NEMO-PREFIX-DELEGATION * Informative Reference RFC4889 * Normative Reference DRAFT-SALOWEY-RADEXT-DELEGATED-PREFIX * Reference DRAFT-BAGNULO-SHIM6-ADDR-SELECTION * Normative Reference DRAFT-DROMS-DHC-DHCPV6-AGENTOPT-DELEGATE * Informative Reference RFC4925 * Normative Reference DRAFT-IETF-DHC-DHCPV6-AGENTOPT-DELEGATE * Normative Reference DRAFT-TOUTAIN-SOFTWIRE-POINT6BOX * Informative Reference DRAFT-VANDEVELDE-V6OPS-ADDCON * Informative Reference RFC5375 * Normative Reference DRAFT-IETF-DHC-DNS-PD * Informative Reference RFC6775 * Reference DRAFT-RUFFINO-AUTOCONF-CONN-SCENARIOS * Informative Reference DRAFT-PALET-V6OPS-POINT2POINT * Normative Reference RFC4818 * Normative Reference DRAFT-MULE-CABLELABS-DOCSIS3-IPV6 * Informative Reference DRAFT-TEMPLIN-AUTOCONF-NETLMM-DHCP * Normative Reference RFC5558 * Normative Reference DRAFT-BRZOZOWSKI-DHC-DHCVP6-LEASEQUERY * Normative Reference DRAFT-IETF-DHC-DHCVP6-LEASEQUERY * Normative Reference DRAFT-KUWABARA-SOFTWIRE-IPV6-VIA-L2TPV2 * Normative Reference RFC5571 * Informative Reference DRAFT-IETF-AUTOCONF-STATEMENT * Normative Reference DRAFT-VOLZ-DHC-DHCPV6-SRSN-OPTION * Normative Reference DRAFT-IETF-DHC-DHCPV6-SRSN-OPTION * Normative Reference RFC5454 * Reference DRAFT-RAO-IPV6-PREFIX-DELEGATION * Normative Reference RFC5007 * Informative Reference DRAFT-ZHAO-DHC-DHCPV6-RELAY-LINK-SELECTION * Normative Reference RFC4903 * Reference DRAFT-STENBERG-PD-ROUTE-MAINTENANCE * Normative Reference DRAFT-SARIKAYA-16NG-PREFIX-DELEGATION * Informative Reference RFC4924 * Normative Reference DRAFT-TEMPLIN-AUTOCONF-MULTILINK * Normative Reference DRAFT-TEMPLIN-AUTOCONF-VIRTUAL * Informative Reference DRAFT-RUSSERT-NETLMM-HMAP * Normative Reference DRAFT-THUBERT-NINA * Normative Reference DRAFT-SARIKAYA-NETLMM-PREFIX-DELEGATION * Informative Reference DRAFT-ERONEN-IPSEC-IKEV2-IPV6-CONFIG * Informative Reference RFC5739 * Informative Reference RFC7227 * Normative Reference DRAFT-STAPP-DHC-DHCPV6-BULK-LEASEQUERY * Normative Reference RFC5460 * Normative Reference DRAFT-SARIKAYA-DIME-PREFIX-DELEGATION-PS * Informative Reference DRAFT-BAKER-SAVA-IMPLEMENTATION * Normative Reference DRAFT-POPOVICIU-DHC-CERTIFICATE-OPT * Informative Reference DRAFT-STENBERG-V6OPS-PD-ROUTE-MAINTENANCE * Informative Reference DRAFT-VANDEVELDE-V6OPS-CPE-DEFAULT-ROUTE-DETECTION * Normative Reference DRAFT-XIA-DHC-HOST-GEN-ID * Normative Reference DRAFT-SARIKAYA-MEXT-HOMELINK-PREFIX-DELEGATION * Normative Reference DRAFT-DUPONT-MEXT-DHCRELAY * Normative Reference DRAFT-SARIKAYA-MEXT-RELAY-DHCPV6PD * Normative Reference DRAFT-SARIKAYA-MEXT-PREFIX-DELEGATION * Normative Reference DRAFT-DROMS-MEXT-NEMO-PD * Normative Reference RFC6276 * Informative Reference DRAFT-WBEEBEE-IPV6-CPE-ROUTER * Normative Reference RFC6204 * Normative Reference DRAFT-V6OPS-KAIPPALLIMALIL-IPV6-BBNET * Normative Reference DRAFT-KAIPPALLIMALIL-V6OPS-IPV6-BBNET * Reference DRAFT-ZHAO-MEXT-MNP-IKEV2 * Normative Reference DRAFT-SARIKAYA-DIMERADEXT-PREFIX-AUTH-PS * Reference DRAFT-CHROBOCZEK-CONFIGURATION-SEPARATE * Reference DRAFT-BOOT-AUTOCONF-BRDP * Normative Reference DRAFT-SARIKAYA-MEXT-BU-PREFIXDELEGATION * Informative Reference RFC5720 * Normative Reference DRAFT-SARIKAYA-RADEXT-PREFIX-AUTHORIZATION * Reference DRAFT-KAISER-ND-PD * Informative Reference RFC5887 * Normative Reference DRAFT-IETF-V6OPS-MOBILE-DEVICE-PROFILE * Normative Reference DRAFT-DEC-DHCPV6-ROUTE-OPTION * Reference DRAFT-JAEHWOON-AUTOCONF-DHCPOPTION * Informative Reference DRAFT-SARIKAYA-MIF-DHCPV6SOLUTION * Possible Reference DRAFT-WAKIKAWA-NETEXT-PMIP6-NEMO-SUPPORT * Normative Reference DRAFT-RABIL-DHC-DHCPV6-XMLCONFIG * Informative Reference DRAFT-KAIPPALLIMALIL-SAVI-DHCP-PD * Normative Reference DRAFT-TEMPLIN-INTAREA-VET * Normative Reference DRAFT-SARIKAYA-NETEXT-PREFIX-DELEGATION * Normative Reference DRAFT-DONLEY-IPV6-CPE-RTR-USE-CASES-AND-REQS * Normative Reference DRAFT-TOWNSLEY-IPV6-6RD * Normative Reference DRAFT-DALEY-IPV6-NONAT6 * Informative Reference DRAFT-BAKER-IPV6-PREFIX-SUBDELEGATION * Normative Reference DRAFT-WBEEBEE-V6OPS-IPV6-CPE-ROUTER-BIS * Informative Reference RFC5969 * Informative Reference DRAFT-SAVOLAINEN-STATELESS-PD * Normative Reference RFC6324 * Normative Reference DRAFT-JJMB-DHC-DHCPV6-REDUNDANCY-CONSIDER * Normative Reference DRAFT-SARIKAYA-INT-AREA-PREFIX-DELEGATION * Normative Reference DRAFT-JIANG-DHC-CGA-CONFIG-DHCPV6 * Normative Reference DRAFT-SARIKAYA-INTAREA-PREFIX-DELEGATION * Informative Reference DRAFT-KORHONEN-V6OPS-3GPP-EPS * Informative Reference RFC6459 * Informative Reference RFC6653 * Normative Reference DRAFT-KRISHNAN-INTAREA-PD-EPC * Informative Reference RFC6911 * Normative Reference DRAFT-KORHONEN-DHC-PD-EXCLUDE * Normative Reference RFC6603 * Informative Reference DRAFT-DING-SAVI-PANA-WITH-SLACC * Normative Reference DRAFT-YEH-DHC-DHCPV6-PREFIX-POOL-OPT * Normative Reference DRAFT-HU-PPPEXT-IPV6CP-REQUIREMENTS * Informative Reference DRAFT-HERBST-V6OPS-CPEENHANCEMENTS * Normative Reference DRAFT-IETF-MIF-DHCPV6-ROUTE-OPTION * Informative Reference DRAFT-BOOT-BRDP-FRAMEWORK * Normative Reference DRAFT-ZHOU-NETEXT-PD-PMIP * Normative Reference DRAFT-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-IETF-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference RFC7084 * Normative Reference DRAFT-JOSHI-DHC-DHCPV6-AGGR-ROUTE-OPT * Informative Reference RFC6632 * Informative Reference DRAFT-IETF-6LOWPAN-BTLE * Possible Reference DRAFT-JJMB-V6OPS-COMCAST-IPV6-EXPERIENCES * Normative Reference RFC7148 * Informative Reference RFC6706 * Normative Reference DRAFT-FLING-V6OPS-HYBRID-BRIDGED-ROUTED * Normative Reference RFC6853 * Normative Reference DRAFT-IETF-DHC-CGA-CONFIG-DHCPV6 * Normative Reference DRAFT-IETF-DHC-HOST-GEN-ID * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-REQUIREMENTS * Normative Reference DRAFT-TEMPLIN-ISUPDATE * Informative Reference DRAFT-BAKER-FUN-MULTI-ROUTER * Normative Reference DRAFT-JIANG-6RENUM-ENTERPRISE * Normative Reference RFC6879 * Normative Reference DRAFT-LIU-6RENUM-GAP-ANALYSIS * Normative Reference RFC7010 * Normative Reference DRAFT-FREEDMAN-PPPEXT-IPV6-6RD * Normative Reference RFC7368 * Normative Reference DRAFT-CHAKRABARTI-HOMENET-PREFIX-ALLOC * Informative Reference DRAFT-REDDY-MIF-DHCPV6-PRECEDENCE-OPS * Informative Reference DRAFT-WING-BEHAVE-DHCPV6-RECONFIGURE * Normative Reference DRAFT-BHANDARI-DHC-CLASS-BASED-PREFIX * Normative Reference DRAFT-XLI-SOFTWIRE-DIVI-PD * Normative Reference DRAFT-BCX-BEHAVE-ADDRESS-FMT-EXTENSION * Informative Reference DRAFT-HAZEYAMA-WIDECAMP-IPV6-ONLY-EXPERIENCE * Normative Reference RFC7031 * Normative Reference DRAFT-HADDAD-HOMENET-GATEWAY-VISIBILITY * Informative Reference DRAFT-ARKKO-HOMENET-PREFIX-ASSIGNMENT * Normative Reference DRAFT-MDT-SOFTWIRE-MAP-DHCP-OPTION * Informative Reference DRAFT-MDT-SOFTWIRE-MAPPING-ADDRESS-AND-PORT * Normative Reference DRAFT-TOWNSLEY-V6OPS-6RD-SUNSETTING * Informative Reference DRAFT-HOWARD-UP-PIO * Normative Reference DRAFT-DROMS-DHC-DHCPV6-SOLMAXRT-UPDATE * Normative Reference DRAFT-MA-NETEXT-PDHMIP * Informative Reference RFC6877 * Informative Reference DRAFT-YEH-DHC-DHCPV6-AUTHORIZATION-OPT * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-DESIGN * Normative Reference DRAFT-LEMON-DHC-DNS-PD * Normative Reference DRAFT-GMANN-HOMENET-RELAY-AUTOCONF * Normative Reference DRAFT-TROAN-DHC-DHCPV6-STATEFUL-ISSUES * Normative Reference DRAFT-YEH-RADEXT-EXT-DUAL-STACK-ACCESS * Informative Reference RFC7037 * Informative Reference DRAFT-IETF-SOFTWIRE-MAP * Informative Reference DRAFT-RIBIERE-SAVI-PREFIX-GUARD * Normative Reference DRAFT-MGLT-NAMING-DELEGATION * Normative Reference DRAFT-IETF-DHC-DHCPV6-FAILOVER-DESIGN * Normative Reference DRAFT-JIANG-SEMANTIC-PREFIX * Informative Reference DRAFT-CHEN-SOFTWIRE-CE-NON-PD * Normative Reference DRAFT-MGLT-HOMENET-NAMING-DELEGATION * Normative Reference DRAFT-IETF-DHC-DHCPV6-PREFIX-POOL-OPT * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQS-RFC3316UPDATE * Informative Reference DRAFT-BYRNE-V6OPS-64SHARE * Informative Reference DRAFT-BOUCADAIR-INTAREA-HOST-IDENTIFIER-SCENARIOS * Informative Reference DRAFT-IETF-SOFTWIRE-MAP-T * Informative Reference DRAFT-KORHONEN-V6OPS-RFC3316BIS * Normative Reference DRAFT-JIANG-V6OPS-SEMANTIC-PREFIX * Possible Reference DRAFT-MA-SOFTWIRE-DSLITE-TEST * Informative Reference DRAFT-BOOT-HOMENET-BRDP * Informative Reference DRAFT-CARPENTER-6RENUM-NEXT-STEPS * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQUIREMENTS * Informative Reference RFC7066 * Informative Reference RFC7083 * Informative Reference RFC7278 * Normative Reference DRAFT-WINTERS-HOMENET-SPER-INTERACTION * Normative Reference DRAFT-SARIKAYA-FMC-PREFIX-SHARING-USECASE * Normative Reference DRAFT-GRUNDEMANN-HOMENET-HIPNET * Normative Reference DRAFT-SHISHIO-V6OPS-DPVT * Informative Reference DRAFT-BAKER-IPV6-ISIS-AUTOMATIC-PREFIX * Normative Reference DRAFT-PETRESCU-RELAY-ROUTE-PD-PROBLEM * Reference DRAFT-CHROBOCZEK-HOMENET-CONFIGURATION-SEPARATE * Informative Reference DRAFT-JVKJJMB-HOME-NETWORKING-INCREMENTAL * Informative Reference DRAFT-HAZEYAMA-SUNSET4-DNS-A-FILTER * Normative Reference DRAFT-GRUNDEMANN-HIPNET * Normative Reference DRAFT-SCHOTT-FMC-PREFIX-SHARING-PROTOCOL * Informative Reference DRAFT-LEPAPE-6MAN-PREFIX-METADATA * Normative Reference DRAFT-XU-HOMENET-TRAFFIC-CLASS * Normative Reference DRAFT-RAGHUVANSHI-DHC-DHCPV6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-ANDREWS-DNSOP-PD-REVERSE * Normative Reference DRAFT-MA-V6OPS-ROUTER-TEST * Normative Reference DRAFT-XUE-APS-SERVICE-CHAINING-USECASE * Normative Reference DRAFT-SARIKAYA-APS-PREFIX-SHARING-USECASE * Normative Reference DRAFT-KKB-MPVD-DHCP-SUPPORT * Informative Reference DRAFT-STENBERG-HOMENET-DNSSD-HYBRID-PROXY-ZEROCONF * Normative Reference DRAFT-PFISTER-HOMENET-PREFIX-ASSIGNMENT * Normative Reference DRAFT-MARIAGER-6LO-V6OVER-DECT-ULE * Informative Reference DRAFT-JIANG-NMRG-AN-GAP-ANALYSIS * Normative Reference DRAFT-HONG-6LO-IPV6-OVER-NFC * Normative Reference DRAFT-TAHT-KELLEY-HUNT-DHCPV4-TO-SLAAC-NAMING * Normative Reference DRAFT-XUE-SFC-ADDRESS-SHARING-IN-SFC-USE-CASES * Informative Reference DRAFT-IETF-HOMENET-HNCP * Reference DRAFT-JIANG-AUTO-ADDR-MANAGEMENT * Normative Reference DRAFT-SARIKAYA-SFC-ADDRESS-SHARING-IN-SFC * Normative Reference DRAFT-SARIKAYA-DHC-DHCPV6-RAOPTIONS-SADR * Normative Reference DRAFT-IETF-6LO-DECT-ULE * Normative Reference DRAFT-SARIKAYA-DMM-FOR-WIFI * Normative Reference DRAFT-TEMPLIN-AEROLINK * Normative Reference DRAFT-TEMPLIN-AEROENT * Normative Reference DRAFT-IETF-DHC-DHCPV6-STATEFUL-ISSUES * Informative Reference DRAFT-IETF-HOMENET-PREFIX-ASSIGNMENT * Reference DRAFT-JIANG-ANIMA-PREFIX-MANAGEMENT * Informative Reference DRAFT-KRISHNAN-DHC-DHCPV6-PRIVACY * Normative Reference DRAFT-SARIKAYA-DHC-6MAN-DHCPV6-SADR * Informative Reference DRAFT-IETF-DHC-DHCPV6-PRIVACY * Normative Reference DRAFT-IETF-DHC-DHCPV6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-IETF-MIF-MPVD-DHCP-SUPPORT * Normative Reference DRAFT-XIE-HIAPS-HOSTID-IN-SFC * Informative Reference DRAFT-IETF-HOMENET-HYBRID-PROXY-ZEROCONF * Normative Reference DRAFT-CUI-DHC-DHCPV6-YANG * Informative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-PRIVACY-MITIGATION RFC3634: Key Distribution Center (KDC) Server Address Sub-option for the Dynamic Host Configuration Protocol (DHCP) CableLabs Client Configuration (CCC) Option (7 pages) * Normative Reference RFC3495 * Normative Reference RFC3118 * Possible Reference BCP11 * Normative Reference BCP14 * Possible Reference STD1 * Normative Reference RFC2131 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference RFC6784 RFC3646: DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (7 pages) * Informative Reference BCP11 * Informative Reference RFC3397 * Normative Reference RFC1536 * Informative Reference RFC1535 * Normative Reference RFC3315 * Informative Reference RFC1034 * Possible Reference RFC1035 * Normative Reference BCP14 * Normative Reference RFC2535 * Informative Reference STD13 * Informative Reference DRAFT-STENBERG-HOMENET-DNSSDEXT-HYBRID-PROXY-OSPF * Informative Reference DRAFT-WING-DHC-DNS-RECONFIGURE * Normative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Normative Reference RFC4472 * Informative Reference RFC4215 * Normative Reference RFC4241 * Informative Reference RFC3736 * Normative Reference RFC3904 * Informative Reference RFC5006 * Reference DRAFT-CADAR-DHC-DHCPV6-V4OPTIONS * Normative Reference RFC4339 * Normative Reference DRAFT-ASADULLAH-V6OPS-BB-DEPLOYMENT-SCENARIOS * Informative Reference RFC5026 * Normative Reference DRAFT-MGLT-DNSOP-SEARCH-LIST-PROCESSING * Informative Reference DRAFT-LEE-DNSOP-RESOLVER-WELLKNOWN-IPV6ADDR * Normative Reference DRAFT-KUWABARA-SOFTWIRE-IPV6-VIA-L2TPV2 * Normative Reference DRAFT-BHARATIA-MIP6-GEN-EXT * Informative Reference RFC5571 * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference RFC7227 * Normative Reference DRAFT-IETF-DNSEXT-DNS-PROTOCOL-PROFILE * Normative Reference RFC5679 * Normative Reference RFC6276 * Normative Reference DRAFT-LOURDELET-RADEXT-IPV6-DHCP * Informative Reference DRAFT-WBEEBEE-IPV6-CPE-ROUTER * Normative Reference RFC6204 * Normative Reference DRAFT-DHANKINS-SOFTWIRE-TUNNEL-OPTION * Normative Reference RFC6334 * Normative Reference DRAFT-SAVOLAINEN-6MAN-FQDN-BASED-IF-SELECTION * Informative Reference DRAFT-SAVOLAINEN-MIF-DNS-SERVER-SELECTION * Informative Reference RFC6731 * Informative Reference DRAFT-LOURDELET-RADEXT-IPV6-ACCESS * Normative Reference DRAFT-DONLEY-IPV6-CPE-RTR-USE-CASES-AND-REQS * Normative Reference DRAFT-HOWARD-ISP-IP6RDNS * Informative Reference RFC6055 * Normative Reference DRAFT-WBEEBEE-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-BOUCADAIR-BEHAVE-DNS64-DISCOVERY * Informative Reference RFC7157 * Informative Reference DRAFT-WING-BEHAVE-DNS64-CONFIG * Informative Reference RFC6911 * Informative Reference RFC6106 * Normative Reference DRAFT-HU-PPPEXT-IPV6CP-REQUIREMENTS * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Normative Reference DRAFT-JIANG-IPV6-SITE-RENUM-GUIDELINE * Normative Reference DRAFT-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-IETF-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference RFC7084 * Informative Reference RFC6632 * Normative Reference DRAFT-JIANG-6RENUM-ENTERPRISE * Normative Reference RFC6879 * Informative Reference DRAFT-CHOWN-HOMENET-ARCH * Normative Reference DRAFT-WING-BEHAVE-DHCPV6-RECONFIGURE * Normative Reference DRAFT-ARKKO-HOMENET-PREFIX-ASSIGNMENT * Informative Reference DRAFT-YEH-DHC-DHCPV6-AUTHORIZATION-OPT * Informative Reference RFC7037 * Normative Reference DRAFT-WU-PCE-DNS-PCE-DISCOVERY * Informative Reference DRAFT-IETF-DHC-CONN-STATUS * Informative Reference DRAFT-STENBERG-HOMENET-DNSSD-HYBRID-PROXY-ZEROCONF * Normative Reference DRAFT-PFISTER-HOMENET-PREFIX-ASSIGNMENT * Normative Reference DRAFT-HOWARD-DNSOP-IP6RDNS * Normative Reference DRAFT-JEONG-HOMENET-DEVICE-NAME-AUTOCONF * Informative Reference DRAFT-IETF-HOMENET-HYBRID-PROXY-ZEROCONF RFC3679: Unused Dynamic Host Configuration Protocol (DHCP) Option Codes (8 pages) * Informative Reference RFC3046 * Possible Reference RFC2489 * Informative Reference BCP43 * Possible Reference RFC2939 * Informative Reference BCP11 * Normative Reference RFC4578 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference RFC3942 * Reference DRAFT-GPATERNO-DHCP-LDAP RFC3736: Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6 (9 pages) * Informative Reference BCP78 * Normative Reference RFC2460 * Informative Reference RFC2461 * Informative Reference RFC2462 * Normative Reference RFC3315 * Informative Reference RFC1034 * Informative Reference RFC3646 * Informative Reference RFC3319 * Informative Reference STD13 * Informative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Informative Reference DRAFT-IETF-V6OPS-DHCPV6-SLAAC-PROBLEM * Informative Reference RFC4294 * Normative Reference RFC4472 * Informative Reference RFC4215 * Normative Reference RFC4241 * Informative Reference RFC5006 * Normative Reference DRAFT-VIJAY-DHC-DHCPV6-MCAST-RECONF * Informative Reference RFC4477 * Normative Reference RFC4242 * Normative Reference RFC4076 * Informative Reference DRAFT-TEMPLIN-V6OPS-IEMMEI * Reference DRAFT-YAN-DHC-DHCPV6-OPT-DNSZONE * Normative Reference RFC4339 * Normative Reference DRAFT-DANIEL-IPV6-RA-MO-FLAGS * Informative Reference DRAFT-TEMPLIN-V6V4INET * Normative Reference DRAFT-JINMEI-DHC-DHCPV6-CLARIFY-AUTH * Informative Reference DRAFT-CHOWN-V6OPS-CAMPUS-TRANSITION * Informative Reference DRAFT-IETF-V6OPS-CAMPUS-TRANSITION * Normative Reference DRAFT-ASADULLAH-V6OPS-BB-DEPLOYMENT-SCENARIOS * Normative Reference RFC4779 * Possible Reference DRAFT-PATIL-MIP6-WHYAUTHDATAOPTION * Normative Reference DRAFT-IETF-DHC-DHCPV6-CLARIFY-AUTH * Normative Reference DRAFT-DROMS-DHC-V6-RELAYOPT * Normative Reference DRAFT-IETF-IPV6-RA-MO-FLAGS * Normative Reference DRAFT-IETF-DHC-V6-RELAY-RADIUS * Normative Reference RFC4947 * Informative Reference DRAFT-FACCIN-MIH-INFOSERV * Informative Reference DRAFT-VENAAS-DHC-DUAL-STACK-MERGE * Normative Reference RFC5419 * Informative Reference DRAFT-IETF-DHC-DUAL-STACK-MERGE * Informative Reference DRAFT-IETF-MIP6-RADIUS * Informative Reference DRAFT-VANDEVELDE-V6OPS-ADDCON * Informative Reference RFC5375 * Normative Reference RFC6610 * Normative Reference DRAFT-KUWABARA-SOFTWIRE-IPV6-VIA-L2TPV2 * Normative Reference RFC5571 * Normative Reference DRAFT-SARIKAYA-DHC-PROXYAGENT * Informative Reference DRAFT-ABOBA-IP-CONFIG * Informative Reference RFC5505 * Informative Reference DRAFT-CHOWN-V6OPS-ROGUE-RA * Informative Reference RFC6104 * Normative Reference RFC6434 * Informative Reference DRAFT-CHA-IPV6-RA-MO * Informative Reference DRAFT-WBEEBEE-IPV6-CPE-ROUTER * Normative Reference RFC6204 * Informative Reference RFC5887 * Normative Reference DRAFT-XIA-NETLMM-LMA-DISCOVERY * Informative Reference DRAFT-CHOWN-ADDR-SELECT-CONSIDERATIONS * Normative Reference DRAFT-RABIL-DHC-DHCPV6-XMLCONFIG * Normative Reference DRAFT-DONLEY-IPV6-CPE-RTR-USE-CASES-AND-REQS * Normative Reference DRAFT-DALEY-IPV6-NONAT6 * Normative Reference DRAFT-WBEEBEE-V6OPS-IPV6-CPE-ROUTER-BIS * Informative Reference DRAFT-IETF-6MAN-ADDR-SELECT-CONSIDERATIONS * Normative Reference DRAFT-DESPRES-SOFTWIRE-MESH-SAM * Normative Reference DRAFT-JJMB-DHC-DHCPV6-REDUNDANCY-CONSIDER * Informative Reference DRAFT-IETF-SAVI-DHCP * Possible Reference DRAFT-XU-IPV6-RA-DHCP-SERVER-OPTION * Informative Reference DRAFT-KORHONEN-V6OPS-3GPP-EPS * Informative Reference RFC6459 * Informative Reference DRAFT-CHEN-NTPS-RA-OPT * Normative Reference DRAFT-GUO-SOFTWIRE-6RD-IPV6-CONFIG * Normative Reference DRAFT-DESPRES-SOFTWIRE-SAM * Normative Reference DRAFT-HUI-6LOWPAN-DHCP * Informative Reference RFC6106 * Informative Reference DRAFT-TSOU-OPSAWG-NETWORK-CONFIGURATION * Informative Reference DRAFT-IETF-OPSAWG-AUTOMATED-NETWORK-CONFIGURATION * Normative Reference DRAFT-XU-IDR-BEST-EXTERNAL-LOOP-AVOIDANCE * Normative Reference RFC6586 * Normative Reference DRAFT-JIANG-IPV6-SITE-RENUM-GUIDELINE * Normative Reference DRAFT-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-IETF-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference RFC7084 * Normative Reference DRAFT-FLING-V6OPS-HYBRID-BRIDGED-ROUTED * Normative Reference RFC6853 * Normative Reference RFC6964 * Informative Reference DRAFT-CHOWN-HOMENET-ARCH * Informative Reference DRAFT-DESPRES-SOFTWIRE-4RD-ADDMAPPING * Normative Reference DRAFT-HAZEYAMA-WIDECAMP-IPV6-ONLY-EXPERIENCE * Normative Reference DRAFT-ARKKO-HOMENET-PREFIX-ASSIGNMENT * Normative Reference DRAFT-YEH-DHC-DHCPV6-AUTHORIZATION-OPT * Normative Reference DRAFT-CHEN-PCP-MOBILE-DEPLOYMENT * Informative Reference RFC7037 * Normative Reference DRAFT-CHEN-SOFTWIRE-CE-NON-PD * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQS-RFC3316UPDATE * Informative Reference DRAFT-KORHONEN-V6OPS-RFC3316BIS * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQUIREMENTS * Informative Reference RFC7066 * Informative Reference DRAFT-LIU-BONICA-DHCPV6-SLAAC-PROBLEM * Normative Reference DRAFT-HAZEYAMA-SUNSET4-DNS-A-FILTER * Informative Reference DRAFT-SMITH-V6OPS-CE-DHCPV6-TRANSPARENCY * Normative Reference DRAFT-JIANG-DHC-STATELESS-RECONFIGURATION * Informative Reference DRAFT-LIU-BONICA-V6OPS-DHCPV6-SLAAC-PROBLEM * Normative Reference DRAFT-JEONG-HOMENET-DEVICE-NAME-AUTOCONF * Informative Reference DRAFT-CHEN-V6OPS-NFV-IPV6 RFC3898: Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (7 pages) * Normative Reference RFC3315 * Informative Reference BCP78 * Informative Reference RFC2132 * Normative Reference BCP14 * Normative Reference RFC4852 * Normative Reference DRAFT-BHARATIA-MIP6-GEN-EXT * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference RFC7227 * Informative Reference RFC5505 RFC3925: Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4) (9 pages) * Informative Reference RFC3118 * Normative Reference RFC3396 * Informative Reference BCP43 * Possible Reference RFC2939 * Informative Reference RFC3315 * Informative Reference BCP78 * Normative Reference BCP14 * Informative Reference RFC2132 * Normative Reference RFC2131 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference RFC4243 * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference DRAFT-VOLZ-DHC-DHCPV4-VENDOR-MESSAGE * Informative Reference DRAFT-IETF-DHC-DHCPV4-VENDOR-MESSAGE * Informative Reference RFC5612 * Reference DRAFT-LONVICK-PRIVATE-TAX * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY * Normative Reference DRAFT-HUITEMA-DHC-ANONYMITY-PROFILE RFC3942: Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options (7 pages) * Updates RFC2132 * Informative Reference BCP78 * Informative Reference RFC3046 * Normative Reference BCP43 * Normative Reference RFC2939 * Informative Reference RFC3679 * Normative Reference BCP14 * Normative Reference RFC2132 * Normative Reference RFC2119 * Normative Reference RFC2131 * Normative Reference DRAFT-IETF-DHC-AGENT-VPN-ID * Informative Reference RFC6607 * Normative Reference RFC6656 * Normative Reference RFC4578 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference RFC5226 * Normative Reference RFC5859 * Normative Reference DRAFT-BLATHERWICK-DHC-MITEL-SITE-OPTIONS-USAGE * Reference DRAFT-DHANKINS-PXELINUX * Informative Reference RFC5071 * Reference DRAFT-DHANKINS-ATOMIC-DHCP * Normative Reference DRAFT-VOLZ-DHC-3942-STATUS * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference DRAFT-LEIBA-COTTON-IANA-5226BIS RFC3993: Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option (7 pages) * Normative Reference STD8 * Normative Reference RFC3046 * Informative Reference RFC3118 * Normative Reference RFC854 * Informative Reference BCP78 * Normative Reference BCP14 * Possible Reference STD1 * Possible Reference RFC2119 * Normative Reference RFC2131 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference RFC4580 * Informative Reference DRAFT-THOMSON-GEOPRIV-HELD-MEASUREMENTS * Normative Reference RFC7105 * Normative Reference DRAFT-HU-DHC-DHCPV6-FOR-DUAL-STACK-HOSTS * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY RFC4014: Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option (8 pages) * Normative Reference RFC3046 * Informative Reference RFC3162 * Normative Reference RFC2865 * Possible Reference STD1 * Informative Reference RFC3118 * Informative Reference BCP78 * Normative Reference BCP14 * Possible Reference RFC2869 * Informative Reference RFC3580 * Possible Reference RFC2119 * Normative Reference RFC2131 * Informative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Normative Reference DRAFT-YEGIN-EAP-BOOT-RFC3118 * Normative Reference DRAFT-ZHAO-DHC-USER-AUTHENTICATION * Informative Reference DRAFT-PRUSS-DHCP-AUTH-DSL * Possible Reference DRAFT-BRZOZOWSKI-DHCP-EAP-ANALYSIS * Informative Reference DRAFT-LI-DHC-SIMPLE-DSL-AUTH * Informative Reference DRAFT-JJMB-DHC-EAP-AUTH-ANALYSIS * Informative Reference DRAFT-HU-V6OPS-RADIUS-ISSUES-IPV6 * Normative Reference DRAFT-YEH-DHC-DHCPV6-AUTHORIZATION-OPT RFC4030: The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option (15 pages) * Normative Reference RFC3046 * Informative Reference RFC951 * Informative Reference RFC3118 * Informative Reference RFC1542 * Normative Reference RFC3174 * Normative Reference RFC2104 * Normative Reference BCP14 * Possible Reference RFC2434 * Informative Reference BCP78 * Informative Reference RFC2845 * Possible Reference STD1 * Possible Reference RFC2119 * Normative Reference BCP26 * Informative Reference RFC2131 * Normative Reference DRAFT-IETF-DHC-AGENT-VPN-ID * Informative Reference RFC6607 * Informative Reference RFC5107 * Informative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference RFC4243 * Informative Reference DRAFT-TEMPLIN-AUTOCONF-NETLMM-DHCP * Normative Reference DRAFT-KINNEAR-DHC-RELAY-AGENT-FLAGS * Normative Reference RFC5010 * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Normative Reference DRAFT-STAPP-DHC-RELAY-ID * Normative Reference RFC6925 * Informative Reference DRAFT-DHANKINS-DHCPINFORM-CLARIFY * Informative Reference DRAFT-IETF-DHC-DHCPINFORM-CLARIFY * Informative Reference RFC7298 * Informative Reference DRAFT-TEMPLIN-INTAREA-VET * Normative Reference DRAFT-LEMON-DHCPV4-RELAY-ENCAPSULATION * Normative Reference DRAFT-IETF-DHC-DHCPV4-RELAY-ENCAPSULATION * Normative Reference DRAFT-BI-DHC-OPEXTENSIONS * Informative Reference DRAFT-BI-DHC-SEC-OPTION * Informative Reference DRAFT-IETF-DHC-ACCESS-NETWORK-IDENTIFIER RFC4039: Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4) (10 pages) * Informative Reference BCP78 * Possible Reference STD1 * Informative Reference RFC3118 * Informative Reference BCP43 * Informative Reference RFC2939 * Informative Reference RFC3315 * Normative Reference BCP14 * Informative Reference RFC2132 * Normative Reference RFC2119 * Normative Reference RFC2131 * Informative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Informative Reference RFC4436 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference DRAFT-OHBA-MOBOPTS-MPA-FRAMEWORK * Informative Reference DRAFT-TEMPLIN-AUTOCONF-NETLMM-DHCP * Informative Reference DRAFT-ZHAO-DHC-USER-AUTHENTICATION * Informative Reference RFC6252 * Possible Reference DRAFT-LIU-WIFI-FAST-RECOVERY RFC4075: Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6 (5 pages) * Informative Reference BCP78 * Normative Reference RFC3315 * Normative Reference BCP14 * Informative Reference RFC2030 * Informative Reference RFC2132 * Possible Reference RFC2119 * Normative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Normative Reference RFC4241 * Normative Reference DRAFT-KUWABARA-SOFTWIRE-IPV6-VIA-L2TPV2 * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference DRAFT-GAYRAUD-DHCPV6-NTP-OPT * Informative Reference RFC5908 * Informative Reference DRAFT-THOMSON-HELD-GRIP * Normative Reference RFC6204 * Informative Reference DRAFT-THOMSON-GEOPRIV-HELD-GRIP * Normative Reference DRAFT-DONLEY-IPV6-CPE-RTR-USE-CASES-AND-REQS * Normative Reference DRAFT-WBEEBEE-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-IETF-V6OPS-IPV6-CPE-ROUTER-BIS * Informative Reference RFC7227 RFC4076: Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (8 pages) * Normative Reference RFC3315 * Normative Reference RFC3736 * Informative Reference BCP78 * Normative Reference RFC2461 * Normative Reference RFC2462 * Informative Reference RFC4242 * Informative Reference RFC4339 * Informative Reference DRAFT-BAKER-V6OPS-L3-MULTIHOMING-ANALYSIS * Informative Reference RFC5887 * Informative Reference DRAFT-JIANG-IPV6-SITE-RENUM-GUIDELINE * Informative Reference DRAFT-BAKER-6RENUM-OSS-RENUMBERING * Informative Reference DRAFT-SMITH-V6OPS-CE-DHCPV6-TRANSPARENCY RFC4174: The IPv4 Dynamic Host Configuration Protocol (DHCP) Option for the Internet Storage Name Service (13 pages) * Normative Reference RFC4171 * Informative Reference BCP78 * Normative Reference RFC3720 * Informative Reference RFC4172 * Normative Reference RFC3118 * Normative Reference RFC3723 * Normative Reference BCP14 * Informative Reference RFC3833 * Informative Reference BCP38 * Informative Reference RFC2827 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference RFC2131 * Normative Reference RFC7146 * Normative Reference RFC4171 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Updates RFC7146 * Informative Reference RFC5505 * Normative Reference DRAFT-ZIMMER-DHC-DHCPV6-REMOTE-BOOT-OPTIONS RFC4242: Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (8 pages) * Informative Reference BCP78 * Informative Reference RFC4076 * Normative Reference RFC3736 * Normative Reference RFC2462 * Normative Reference RFC3315 * Normative Reference BCP14 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference RFC7341 * Informative Reference RFC4339 * Informative Reference DRAFT-IETF-DHC-DHCPV6-CLARIFY-AUTH * Informative Reference RFC7227 * Normative Reference RFC6204 * Informative Reference DRAFT-CHOWN-ADDR-SELECT-CONSIDERATIONS * Informative Reference DRAFT-DEC-DHCPV6-ROUTE-OPTION * Normative Reference RFC6731 * Normative Reference DRAFT-DONLEY-IPV6-CPE-RTR-USE-CASES-AND-REQS * Possible Reference DRAFT-YOURTCHENKO-RA-DHCPV6-COMPARISON * Normative Reference DRAFT-WBEEBEE-V6OPS-IPV6-CPE-ROUTER-BIS * Informative Reference DRAFT-IETF-6MAN-ADDR-SELECT-CONSIDERATIONS * Informative Reference DRAFT-WING-BEHAVE-DNS64-CONFIG * Informative Reference DRAFT-IETF-MIF-DHCPV6-ROUTE-OPTION * Normative Reference DRAFT-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-IETF-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference RFC7084 * Normative Reference DRAFT-HALWASIA-DHC-INFORM-REFRESH-TIME-OPT * Informative Reference DRAFT-SMITH-V6OPS-CE-DHCPV6-TRANSPARENCY * Normative Reference DRAFT-IETF-ROLL-MPL-PARAMETER-CONFIGURATION * Informative Reference DRAFT-SARIKAYA-DHC-DHCPV6-RAOPTIONS-SADR * Informative Reference DRAFT-SARIKAYA-DHC-6MAN-DHCPV6-SADR RFC4243: Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option (7 pages) * Normative Reference RFC3046 * Informative Reference RFC3925 * Informative Reference RFC3118 * Informative Reference RFC4030 * Informative Reference BCP78 * Normative Reference BCP14 * Possible Reference STD1 * Possible Reference RFC2119 * Normative Reference RFC2131 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference RFC4679 * Informative Reference RFC5515 RFC4280: Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers (11 pages) * Replaces DRAFT-IETF-DHC-BCMCV4-OPTION * Replaces DRAFT-IETF-DHC-BCMCV6-OPTION * Normative Reference BCP78 * Possible Reference STD1 * Normative Reference RFC3396 * Normative Reference RFC3315 * Normative Reference RFC1035 * Normative Reference BCP14 * Normative Reference RFC2132 * Normative Reference RFC2119 * Normative Reference STD13 * Normative Reference RFC2131 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Possible Reference DRAFT-GUDMUNDSSON-DNS-SRV-IANA-REGISTRY * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference RFC6632 * Informative Reference RFC7227 * Informative Reference DRAFT-BOUCADAIR-DHC-ADDRESS-NAME-ENCODING RFC4361: Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4) (12 pages) * Updates RFC2131 * Updates RFC2132 * Updates RFC3315 * Informative Reference BCP78 * Possible Reference STD1 * Informative Reference RFC3118 * Normative Reference RFC3315 * Normative Reference BCP14 * Normative Reference RFC2132 * Normative Reference RFC2119 * Normative Reference RFC2131 * Updates RFC5494 * Normative Reference DRAFT-TROAN-DHC-DHCPV4OSW * Normative Reference RFC7341 * Normative Reference DRAFT-SCSKF-DHC-DHCPV4-OVER-DHCPV6 * Informative Reference RFC4703 * Normative Reference RFC4701 * Normative Reference RFC4390 * Informative Reference DRAFT-IETF-DHC-IMPLEMENTATION * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference RFC4477 * Informative Reference DRAFT-TSCHOFENIG-GEOPRIV-L7-LCP-PS * Informative Reference RFC5687 * Normative Reference DRAFT-WINTERBOTTOM-GEOPRIV-HELD-IDENTITY-EXTENSIONS * Normative Reference RFC6155 * Normative Reference RFC5844 * Normative Reference RFC5494 * Informative Reference DRAFT-DONLEY-IPV6-CPE-RTR-USE-CASES-AND-REQS * Informative Reference DRAFT-WING-BEHAVE-DNS64-CONFIG * Informative Reference DRAFT-FARRER-DHC-SHARED-ADDRESS-LEASE * Normative Reference DRAFT-BI-DHC-SEC-OPTION * Informative Reference DRAFT-IETF-DHC-DHCPV4-OVER-IPV6 * Normative Reference RFC6939 * Informative Reference DRAFT-FSC-DHC-DHCP4O6-SADDR-OPT * Normative Reference DRAFT-HUITEMA-PERPASS-DHCP-IDENTIFIERS * Normative Reference DRAFT-IETF-DHC-DYNAMIC-SHARED-V4ALLOCATION * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY * Normative Reference DRAFT-HUITEMA-DHC-ANONYMITY-PROFILE RFC4388: Dynamic Host Configuration Protocol (DHCP) Leasequery (27 pages) * Informative Reference RFC826 * Informative Reference RFC951 * Informative Reference STD37 * Normative Reference RFC3046 * Informative Reference RFC1542 * Informative Reference RFC3315 * Normative Reference BCP14 * Informative Reference BCP78 * Normative Reference RFC3118 * Informative Reference RFC2132 * Normative Reference RFC2119 * Normative Reference RFC2131 * Updates RFC6148 * Normative Reference DRAFT-IETF-DHC-DHCPV4-ACTIVE-LEASEQUERY * Informative Reference RFC6607 * Informative Reference DRAFT-IETF-DHC-IMPLEMENTATION * Informative Reference DRAFT-IETF-DHC-V4-THREAT-ANALYSIS * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Reference DRAFT-JOSHI-DHCP-LEASE-QUERY-EXT * Normative Reference DRAFT-BRZOZOWSKI-DHC-DHCVP6-LEASEQUERY * Normative Reference DRAFT-IETF-DHC-DHCVP6-LEASEQUERY * Normative Reference RFC5007 * Informative Reference DRAFT-WINTERBOTTOM-GEOPRIV-HELD-IDENTITY-EXTENSIONS * Reference DRAFT-JOSHI-DHC-LAYER2-RELAY-AGENT * Reference DRAFT-KURAPATI-DHC-L2RA-EXTENSIONS * Reference DRAFT-IETF-DHC-L2RA-EXTENSIONS * Reference DRAFT-KURAPATI-DHC-LEASEQUERY-BY-REMOTE-ID * Normative Reference RFC6148 * Informative Reference RFC5942 * Informative Reference RFC6925 * Reference DRAFT-DTV-DHC-DHCPV4-BULK-LEASEQUERY * Normative Reference RFC6926 * Informative Reference DRAFT-KINNEAR-DHC-DHCPV4-BULK-LEASEQUERY * Normative Reference DRAFT-IETF-SAVI-DHCP * Normative Reference DRAFT-KINNEAR-DHC-DHCPV4-ACTIVE-LEASEQUERY * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-BULK-ACTIVE-LEASEQUERY * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY RFC4436: Detecting Network Attachment in IPv4 (DNAv4) (15 pages) * Informative Reference RFC4039 * Normative Reference RFC826 * Informative Reference RFC3927 * Informative Reference RFC1918 * Informative Reference RFC3118 * Informative Reference BCP5 * Informative Reference RFC792 * Informative Reference BCP78 * Normative Reference BCP14 * Normative Reference STD37 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference RFC2131 * Informative Reference DRAFT-HIBBS-DHC-CHANGES * Informative Reference RFC4555 * Informative Reference RFC4907 * Informative Reference DRAFT-IETF-DNA-FRD * Normative Reference RFC5555 * Informative Reference RFC5563 * Normative Reference DRAFT-SHEFFER-IPSEC-SECURE-BEACON * Reference DRAFT-JEONG-NETLMM-DUAL-STACK-MOVING * Informative Reference RFC5844 * Informative Reference RFC7227 * Informative Reference RFC6059 * Informative Reference RFC5218 * Normative Reference DRAFT-SHEFFER-IPSECME-SECURE-BEACON * Normative Reference DRAFT-IETF-SAVI-DHCP * Informative Reference RFC6555 * Informative Reference RFC6574 RFC4477: Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack Issues (14 pages) * Informative Reference BCP78 * Informative Reference RFC4361 * Informative Reference RFC3736 * Informative Reference RFC3118 * Informative Reference RFC2462 * Informative Reference RFC3315 * Informative Reference RFC2131 * Informative Reference DRAFT-CHOWN-V6OPS-CAMPUS-TRANSITION * Informative Reference DRAFT-IETF-V6OPS-CAMPUS-TRANSITION * Informative Reference RFC4852 * Informative Reference RFC5375 * Informative Reference RFC5505 * Informative Reference DRAFT-BLANCHET-MIF-PROBLEM-STATEMENT * Normative Reference DRAFT-HU-DHC-DHCPV6-FOR-DUAL-STACK-HOSTS RFC4578: Dynamic Host Configuration Protocol (DHCP) Options for the Intel Preboot eXecution Environment (PXE) (7 pages) * Normative Reference BCP78 * Normative Reference BCP43 * Normative Reference RFC3679 * Normative Reference BCP14 * Normative Reference RFC3942 * Normative Reference RFC2132 * Possible Reference RFC2119 * Normative Reference RFC2131 * Informative Reference DRAFT-ABOBA-IP-CONFIG * Informative Reference DRAFT-VOLZ-DHC-3942-STATUS * Informative Reference RFC5505 * Normative Reference RFC5970 * Normative Reference DRAFT-ZIMMER-DHC-DHCPV6-REMOTE-BOOT-OPTIONS * Normative Reference RFC6355 * Normative Reference DRAFT-HUITEMA-PERPASS-DHCP-IDENTIFIERS * Informative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Informative Reference DRAFT-IETF-DHC-DHCP-PRIVACY * Normative Reference DRAFT-HUITEMA-DHC-ANONYMITY-PROFILE RFC4580: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option (6 pages) * Informative Reference RFC3993 * Informative Reference STD8 * Informative Reference BCP78 * Normative Reference RFC3315 * Informative Reference RFC854 * Informative Reference RFC3633 * Informative Reference RFC2131 * Informative Reference DRAFT-SZENG-DHC-DHCPV6-ERO * Informative Reference DRAFT-THOMSON-GEOPRIV-HELD-MEASUREMENTS * Informative Reference DRAFT-DUPONT-MEXT-DHCRELAY * Normative Reference RFC7105 * Normative Reference DRAFT-HU-DHC-DHCPV6-FOR-DUAL-STACK-HOSTS * Informative Reference DRAFT-KRISHNAN-DHC-DHCPV6-PRIVACY * Informative Reference DRAFT-IETF-DHC-DHCPV6-PRIVACY * Informative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-PRIVACY-MITIGATION RFC4649: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option (6 pages) * Informative Reference BCP78 * Normative Reference RFC3046 * Normative Reference RFC3315 * Normative Reference BCP14 * Informative Reference RFC3633 * Informative Reference DRAFT-SZENG-DHC-DHCPV6-ERO * Informative Reference RFC6320 * Normative Reference DRAFT-STAPP-DHC-DHCPV6-BULK-LEASEQUERY * Normative Reference RFC5460 * Informative Reference DRAFT-THOMSON-GEOPRIV-HELD-MEASUREMENTS * Normative Reference RFC7105 * Informative Reference DRAFT-DUPONT-MEXT-DHCRELAY * Informative Reference RFC6788 * Normative Reference DRAFT-HU-DHC-DHCPV6-FOR-DUAL-STACK-HOSTS * Informative Reference DRAFT-CHOWN-V6OPS-ADDRESS-ACCOUNTABILITY * Normative Reference RFC7148 * Informative Reference DRAFT-KRISHNAN-DHC-DHCPV6-PRIVACY * Informative Reference DRAFT-IETF-DHC-DHCPV6-PRIVACY * Informative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-PRIVACY-MITIGATION RFC4702: The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option (17 pages) * Informative Reference RFC2671 * Normative Reference RFC3396 * Informative Reference RFC2132 * Informative Reference RFC3007 * Informative Reference FYI4 * Normative Reference RFC1918 * Normative Reference RFC952 * Normative Reference BCP5 * Informative Reference RFC1996 * Normative Reference STD3 * Informative Reference RFC1995 * Informative Reference BCP78 * Normative Reference RFC4703 * Normative Reference RFC2136 * Informative Reference RFC3118 * Normative Reference BCP14 * Possible Reference STD1 * Normative Reference STD13 * Normative Reference RFC2131 * Informative Reference RFC4703 * Informative Reference RFC4704 * Normative Reference DRAFT-THOMSON-GEOPRIV-LIS-DISCOVERY * Normative Reference RFC5986 * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference DRAFT-WANG-ALTO-DISCOVERY * Informative Reference RFC6939 * Normative Reference DRAFT-HUITEMA-PERPASS-DHCP-IDENTIFIERS * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY * Normative Reference DRAFT-HUITEMA-DHC-ANONYMITY-PROFILE RFC4703: Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients (13 pages) * Informative Reference BCP78 * Informative Reference FYI18 * Informative Reference RFC4702 * Informative Reference RFC3118 * Informative Reference RFC2845 * Normative Reference RFC3315 * Informative Reference RFC4361 * Informative Reference RFC4704 * Normative Reference BCP14 * Normative Reference RFC4701 * Normative Reference RFC2136 * Informative Reference RFC3007 * Informative Reference RFC2132 * Informative Reference STD13 * Normative Reference RFC2131 * Possible Reference DRAFT-LIU-OPSAREA-IPV6-RENUMBERING-GUIDELINES * Normative Reference RFC4702 * Normative Reference RFC4701 * Normative Reference RFC4704 * Normative Reference DRAFT-JJMB-DHC-DHCPV6-REDUNDANCY-CONSIDER * Normative Reference RFC6853 * Normative Reference DRAFT-IETF-DHC-ADDR-REGISTRATION * Normative Reference DRAFT-IETF-DHC-DHCPV6-FAILOVER-DESIGN * Possible Reference DRAFT-XIONG-DMM-IP-REACHABILITY RFC4704: The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option (15 pages) * Informative Reference BCP78 * Normative Reference RFC4291 * Informative Reference FYI4 * Normative Reference RFC3041 * Normative Reference RFC3315 * Informative Reference RFC1996 * Normative Reference RFC4703 * Normative Reference BCP14 * Normative Reference RFC2136 * Informative Reference RFC3596 * Informative Reference RFC3007 * Informative Reference RFC1995 * Normative Reference STD13 * Informative Reference RFC4702 * Informative Reference DRAFT-LIU-OPSAREA-IPV6-RENUMBERING-GUIDELINES * Informative Reference RFC4703 * Normative Reference RFC6080 * Normative Reference DRAFT-MGLT-DNSOP-SEARCH-LIST-PROCESSING * Normative Reference DRAFT-THOMSON-GEOPRIV-LIS-DISCOVERY * Normative Reference RFC5986 * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference RFC7227 * Informative Reference DRAFT-WANG-ALTO-DISCOVERY * Normative Reference DRAFT-HOWARD-ISP-IP6RDNS * Normative Reference RFC6853 * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-REQUIREMENTS * Normative Reference DRAFT-JIANG-6RENUM-ENTERPRISE * Normative Reference RFC6879 * Informative Reference RFC7010 * Reference DRAFT-YAN-MEXT-DNSMIP * Normative Reference RFC7031 * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-DESIGN * Normative Reference DRAFT-IETF-DHC-ADDR-REGISTRATION * Informative Reference RFC6939 * Normative Reference DRAFT-IETF-DHC-DHCPV6-FAILOVER-DESIGN * Normative Reference DRAFT-HOWARD-DNSOP-IP6RDNS * Possible Reference DRAFT-QUE-DHC-DNS-MULTI-DHCP-SERVERS * Informative Reference DRAFT-KRISHNAN-DHC-DHCPV6-PRIVACY * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY * Informative Reference DRAFT-IETF-DHC-DHCPV6-PRIVACY * Normative Reference DRAFT-HUITEMA-DHC-ANONYMITY-PROFILE * Informative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-PRIVACY-MITIGATION RFC4833: Timezone Options for DHCP (10 pages) * Replaces DRAFT-LEAR-DHC-TIMEZONE-OPTION * Updates RFC2132 * Informative Reference BCP78 * Normative Reference BCP43 * Possible Reference RFC2939 * Normative Reference RFC3315 * Informative Reference RFC2445 * Normative Reference BCP14 * Normative Reference RFC2132 * Possible Reference RFC2119 * Normative Reference RFC2131 * Informative Reference DRAFT-DHANKINS-DHCP-OPTION-GUIDELINES * Informative Reference RFC7227 * Informative Reference RFC6557 RFC4994: DHCPv6 Relay Agent Echo Request Option (6 pages) * Replaces DRAFT-SZENG-DHC-DHCPV6-ERO * Informative Reference BCP78 * Normative Reference RFC3046 * Normative Reference RFC3315 * Normative Reference BCP14 * Possible Reference STD1 * Normative Reference RFC6607 * Informative Reference DRAFT-TEMPLIN-AEROLINK * Normative Reference DRAFT-PATIL-6LOWPAN-V6OVER-BTLE * Possible Reference DRAFT-MAQUEDA-6LOWPAN-PGW * Normative Reference DRAFT-NIEMINEN-6LOWPAN-SERVICE-DISCOVERY RFC5007: DHCPv6 Leasequery (23 pages) * Replaces DRAFT-IETF-DHC-DHCVP6-LEASEQUERY * Informative Reference RFC826 * Informative Reference STD37 * Informative Reference RFC2461 * Normative Reference RFC3315 * Informative Reference RFC4301 * Normative Reference RFC4388 * Normative Reference BCP14 * Informative Reference BCP78 * Informative Reference RFC2131 * Possible Reference STD1 * Informative Reference BCP26 * Normative Reference RFC3633 * Informative Reference RFC6607 * Informative Reference RFC7227 * Normative Reference DRAFT-STAPP-DHC-DHCPV6-BULK-LEASEQUERY * Normative Reference RFC5460 * Possible Reference DRAFT-RABIL-DHC-DHCPV6-XMLCONFIG * Normative Reference DRAFT-JJMB-DHC-DHCPV6-REDUNDANCY-CONSIDER * Normative Reference DRAFT-IETF-SAVI-DHCP * Normative Reference DRAFT-IETF-DHC-DHCPV6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-DROMS-DHC-DHCPV6-IANA * Normative Reference DRAFT-YEH-DHC-DHCPV6-PREFIX-POOL-OPT * Possible Reference DRAFT-MADI-DHC-DHCPV6-PSAC * Normative Reference DRAFT-LEE-SOFTWIRE-DSLITE-DEPLOYMENT * Normative Reference RFC6853 * Normative Reference DRAFT-IEFT-SOFTWIRE-DSLITE-DEPLOYMENT * Normative Reference DRAFT-REDDY-MIF-DHCPV6-PRECEDENCE-OPS * Informative Reference DRAFT-WING-BEHAVE-DHCPV6-RECONFIGURE * Informative Reference DRAFT-RIBIERE-SAVI-PREFIX-GUARD * Normative Reference DRAFT-IETF-DHC-DHCPV6-FAILOVER-DESIGN * Informative Reference DRAFT-BOUCADAIR-DHC-TRIGGERED-RECONFIGURE * Normative Reference DRAFT-IETF-DHC-DHCPV6-PREFIX-POOL-OPT * Informative Reference RFC6977 * Normative Reference DRAFT-RAGHUVANSHI-DHC-DHCPV6-ACTIVE-LEASEQUERY * Informative Reference DRAFT-KRISHNAN-DHC-DHCPV6-PRIVACY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-BULK-ACTIVE-LEASEQUERY * Informative Reference DRAFT-IETF-DHC-DHCPV6-PRIVACY * Informative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-PRIVACY-MITIGATION RFC5010: The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption (7 pages) * Replaces DRAFT-KINNEAR-DHC-RELAY-AGENT-FLAGS * Normative Reference RFC3118 * Informative Reference RFC3074 * Normative Reference RFC2132 * Normative Reference RFC3046 * Informative Reference BCP78 * Normative Reference RFC4030 * Normative Reference BCP14 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference RFC2131 * Normative Reference RFC5107 RFC5071: Dynamic Host Configuration Protocol Options Used by PXELINUX (14 pages) * Informative Reference BCP78 * Informative Reference RFC3118 * Normative Reference BCP43 * Normative Reference BCP14 * Informative Reference RFC3942 * Informative Reference STD33 * Normative Reference RFC2131 * Normative Reference RFC2132 * Possible Reference RFC2119 * Normative Reference STD8 RFC5107: DHCP Server Identifier Override Suboption (7 pages) * Informative Reference RFC3315 * Informative Reference RFC3118 * Informative Reference RFC2132 * Normative Reference RFC3046 * Informative Reference RFC4030 * Normative Reference RFC5010 * Informative Reference BCP78 * Normative Reference BCP14 * Possible Reference STD1 * Normative Reference RFC2131 * Informative Reference DRAFT-IETF-DHC-V4CONFIGURATION * Normative Reference RFC5844 * Informative Reference RFC6925 RFC5192: DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication Agents (8 pages) * Informative Reference BCP78 * Normative Reference RFC5191 * Possible Reference STD1 * Normative Reference RFC3315 * Informative Reference RFC3748 * Normative Reference BCP14 * Normative Reference RFC2132 * Normative Reference RFC2119 * Normative Reference RFC2131 * Normative Reference RFC5191 * Normative Reference DRAFT-IETF-PANA-PANAOVERDSL * Normative Reference RFC6345 RFC5460: DHCPv6 Bulk Leasequery (18 pages) * Replaces DRAFT-STAPP-DHC-DHCPV6-BULK-LEASEQUERY * Normative Reference RFC4649 * Normative Reference RFC3315 * Informative Reference RFC4301 * Normative Reference RFC5007 * Informative Reference RFC4614 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference RFC3633 * Informative Reference RFC7227 * Informative Reference RFC6926 * Normative Reference DRAFT-JJMB-DHC-DHCPV6-REDUNDANCY-CONSIDER * Normative Reference DRAFT-IETF-DHC-DHCPV6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-YEH-DHC-DHCPV6-PREFIX-POOL-OPT * Normative Reference RFC6853 * Normative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-DESIGN * Informative Reference DRAFT-RIBIERE-SAVI-PREFIX-GUARD * Informative Reference DRAFT-IETF-DHC-DHCPV6-FAILOVER-DESIGN * Normative Reference DRAFT-IETF-DHC-DHCPV6-PREFIX-POOL-OPT * Informative Reference RFC6977 * Normative Reference DRAFT-RAGHUVANSHI-DHC-DHCPV6-ACTIVE-LEASEQUERY * Informative Reference DRAFT-KRISHNAN-DHC-DHCPV6-PRIVACY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-BULK-ACTIVE-LEASEQUERY * Informative Reference DRAFT-IETF-DHC-DHCPV6-PRIVACY * Informative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-PRIVACY-MITIGATION RFC5970: DHCPv6 Options for Network Boot (11 pages) * Normative Reference RFC3629 * Informative Reference RFC906 * Normative Reference RFC5226 * Informative Reference RFC2817 * Informative Reference RFC3617 * Informative Reference RFC1350 * Informative Reference RFC2616 * Normative Reference STD66 * Normative Reference RFC3315 * Possible Reference RFC5741 * Informative Reference RFC2818 * Normative Reference STD63 * Normative Reference BCP14 * Normative Reference RFC3986 * Normative Reference RFC4173 * Normative Reference RFC4578 * Normative Reference RFC2119 * Normative Reference BCP26 * Informative Reference RFC7227 * Informative Reference DRAFT-IETF-OPSAWG-AUTOMATED-NETWORK-CONFIGURATION * Normative Reference RFC6853 * Informative Reference RFC7031 * Informative Reference DRAFT-KRISHNAN-DHC-DHCPV6-PRIVACY * Informative Reference DRAFT-IETF-DHC-DHCPV6-PRIVACY * Informative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-PRIVACY-MITIGATION RFC6148: DHCPv4 Lease Query by Relay Agent Remote ID (13 pages) * Replaces DRAFT-KURAPATI-DHC-LEASEQUERY-BY-REMOTE-ID * Updates RFC4388 * Informative Reference RFC951 * Normative Reference RFC3046 * Informative Reference RFC1542 * Possible Reference RFC5741 * Normative Reference RFC4388 * Normative Reference BCP14 * Normative Reference RFC3118 * Normative Reference RFC2131 * Normative Reference RFC2132 * Normative Reference RFC2119 * Informative Reference DRAFT-FARRER-DHC-SHARED-ADDRESS-LEASE * Informative Reference DRAFT-FSC-DHC-DHCP4O6-SADDR-OPT * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY RFC6221: Lightweight DHCPv6 Relay Agent (17 pages) * Updates RFC3315 * Replaces DRAFT-MILES-DHC-DHCPV6-LDRA * Informative Reference RFC3046 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Informative Reference DRAFT-LEMON-DHC-TOPO-CONF * Informative Reference DRAFT-TEMPLIN-AEROLINK * Informative Reference DRAFT-DEC-6MAN-RS-ACCESS-HARMFUL * Normative Reference DRAFT-HALWASIA-DHC-DHCPV6-HARDWARE-ADDR-OPT * Informative Reference DRAFT-IETF-OPSEC-V6 * Informative Reference DRAFT-IETF-DHC-TOPO-CONF RFC6355: Definition of the UUID-Based DHCPv6 Unique Identifier (DUID-UUID) (5 pages) * Replaces DRAFT-NARTEN-DHC-DUID-UUID * Normative Reference RFC4122 * Normative Reference RFC2132 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference RFC4578 * Informative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Informative Reference DRAFT-TEMPLIN-AEROLINK * Informative Reference DRAFT-IETF-OPSAWG-AUTOMATED-NETWORK-CONFIGURATION * Informative Reference DRAFT-SMITH-V6OPS-CE-DHCPV6-TRANSPARENCY * Informative Reference DRAFT-KRISHNAN-DHC-DHCPV6-PRIVACY * Normative Reference DRAFT-PERKINS-DMM-4283MNIDS * Informative Reference DRAFT-IETF-DHC-DHCPV6-PRIVACY * Informative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-PRIVACY-MITIGATION RFC6422: Relay-Supplied DHCP Options (8 pages) * Updates RFC3315 * Informative Reference RFC5296 * Normative Reference RFC5226 * Informative Reference RFC6440 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference BCP26 * Normative Reference RFC2119 * Normative Reference DRAFT-IETF-MIF-MPVD-DHCP-SUPPORT * Informative Reference DRAFT-TEMPLIN-AEROLINK * Normative Reference RFC6610 * Normative Reference DRAFT-IETF-DHC-SECURE-DHCPV6 * Normative Reference RFC6440 * Informative Reference RFC7227 * Normative Reference DRAFT-BOUCADAIR-DHC-TRIGGERED-RECONFIGURE * Normative Reference RFC6977 * Normative Reference DRAFT-ORR-DHCP-DNS-SD-OPTIONS * Normative Reference DRAFT-TEMPLIN-DHC-CLLAO-UPDATES RFC6603: Prefix Exclude Option for DHCPv6-based Prefix Delegation (10 pages) * Replaces DRAFT-KORHONEN-DHC-PD-EXCLUDE * Updates RFC3633 * Normative Reference RFC3315 * Possible Reference RFC5741 * Informative Reference RFC4862 * Normative Reference RFC3633 * Normative Reference RFC2119 * Normative Reference BCP14 * Informative Reference RFC7227 * Normative Reference DRAFT-IETF-V6OPS-MOBILE-DEVICE-PROFILE * Normative Reference RFC7084 * Normative Reference RFC7148 * Normative Reference DRAFT-IETF-DHC-HOST-GEN-ID * Informative Reference RFC6879 * Informative Reference DRAFT-HAZEYAMA-WIDECAMP-IPV6-ONLY-EXPERIENCE * Normative Reference DRAFT-IETF-HOMENET-HNCP * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQS-RFC3316UPDATE * Informative Reference DRAFT-KORHONEN-V6OPS-RFC3316BIS * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQUIREMENTS * Informative Reference RFC7066 * Informative Reference DRAFT-HAZEYAMA-SUNSET4-DNS-A-FILTER * Normative Reference DRAFT-PFISTER-HOMENET-PREFIX-ASSIGNMENT RFC6607: Virtual Subnet Selection Options for DHCPv4 and DHCPv6 (26 pages) * Updates RFC3046 * Informative Reference RFC5226 * Normative Reference RFC2685 * Informative Reference RFC951 * Informative Reference RFC1542 * Normative Reference RFC3046 * Informative Reference RFC4388 * Informative Reference RFC5198 * Informative Reference RFC4030 * Normative Reference RFC3315 * Possible Reference RFC5741 * Informative Reference RFC5007 * Normative Reference RFC3633 * Informative Reference RFC3942 * Normative Reference RFC4994 * Informative Reference RFC3118 * Normative Reference RFC2132 * Normative Reference RFC2119 * Informative Reference BCP26 * Normative Reference RFC2131 * Normative Reference RFC6926 * Informative Reference DRAFT-IETF-DHC-TOPO-CONF RFC6644: Rebind Capability in DHCPv6 Reconfigure Messages (10 pages) * Replaces DRAFT-EVANS-DHC-DHCPV6-RECONFIGURE-REBIND * Updates RFC3315 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference RFC3972 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference RFC7227 * Normative Reference DRAFT-MGLT-HOMENET-FRONT-END-NAMING-DELEGATION * Normative Reference DRAFT-IETF-HOMENET-FRONT-END-NAMING-DELEGATION * Informative Reference DRAFT-DHCWG-DHC-RFC3315BIS RFC6656: Description of Cisco Systems' Subnet Allocation Option for DHCPv4 (24 pages) * Replaces DRAFT-JOHNSON-DHC-SUBNET-ALLOC * Normative Reference RFC3629 * Normative Reference RFC5226 * Informative Reference RFC3633 * Informative Reference RFC3203 * Informative Reference RFC3396 * Informative Reference BCP122 * Normative Reference RFC2119 * Possible Reference RFC5741 * Normative Reference STD63 * Informative Reference RFC4632 * Normative Reference RFC3942 * Normative Reference BCP14 * Informative Reference RFC3118 * Normative Reference RFC2132 * Normative Reference BCP26 * Normative Reference RFC2131 * Informative Reference DRAFT-TEMPLIN-INTAREA-VET * Informative Reference RFC7148 RFC6704: Forcerenew Nonce Authentication (12 pages) * Updates RFC3203 * Normative Reference RFC3203 * Normative Reference RFC3118 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC2119 RFC6842: Client Identifier Option in DHCP Server Replies (5 pages) * Updates RFC2131 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference RFC2131 * Normative Reference DRAFT-TROAN-DHC-DHCPV4OSW * Informative Reference DRAFT-IETF-DHC-DHCPV4-OVER-IPV6 * Informative Reference DRAFT-SUN-DHC-PORT-SET-OPTION RFC6853: DHCPv6 Redundancy Deployment Considerations (16 pages) * Replaces DRAFT-JJMB-DHC-DHCPV6-REDUNDANCY-CONSIDER * Normative Reference RFC5460 * Normative Reference RFC3736 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference RFC4704 * Normative Reference RFC5007 * Normative Reference RFC3633 * Normative Reference RFC4701 * Normative Reference RFC5970 * Normative Reference RFC2136 * Normative Reference RFC4703 * Informative Reference RFC7031 * Informative Reference DRAFT-ZHANG-DHC-DHCPV6-FAILURE-DETECTION RFC6925: The DHCPv4 Relay Agent Identifier Sub-Option (8 pages) * Informative Reference RFC4122 * Normative Reference RFC3046 * Normative Reference BCP14 * Informative Reference RFC5107 * Possible Reference RFC5741 * Informative Reference RFC4388 * Normative Reference RFC4030 * Informative Reference RFC6926 * Normative Reference RFC2119 * Normative Reference RFC2131 * Normative Reference RFC6926 RFC6926: DHCPv4 Bulk Leasequery (41 pages) * Replaces DRAFT-DTV-DHC-DHCPV4-BULK-LEASEQUERY * Replaces DRAFT-KINNEAR-DHC-DHCPV4-BULK-LEASEQUERY * Normative Reference RFC5226 * Possible Reference RFC2685 * Informative Reference RFC5460 * Normative Reference BCP153 * Informative Reference RFC951 * Informative Reference RFC1542 * Normative Reference RFC3046 * Normative Reference RFC5735 * Normative Reference BCP14 * Normative Reference RFC6607 * Possible Reference RFC5741 * Normative Reference RFC4388 * Informative Reference RFC4614 * Normative Reference RFC6925 * Normative Reference RFC3118 * Normative Reference RFC2132 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC2131 * Normative Reference DRAFT-IETF-DHC-DHCPV4-ACTIVE-LEASEQUERY * Informative Reference RFC6925 * Normative Reference DRAFT-KINNEAR-DHC-DHCPV4-ACTIVE-LEASEQUERY * Normative Reference DRAFT-JIANG-DHC-DHCP-PRIVACY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-BULK-ACTIVE-LEASEQUERY * Normative Reference DRAFT-IETF-DHC-DHCP-PRIVACY RFC6939: Client Link-Layer Address Option in DHCPv6 (7 pages) * Normative Reference RFC4361 * Informative Reference RFC4704 * Normative Reference RFC826 * Normative Reference RFC3315 * Possible Reference RFC5741 * Informative Reference RFC4702 * Normative Reference BCP14 * Normative Reference STD37 * Normative Reference RFC2119 * Informative Reference RFC2131 * Normative Reference DRAFT-LEMON-DHC-INVENTORY * Normative Reference DRAFT-SARIKAYA-DHC-VXLAN-MULTICAST * Informative Reference DRAFT-TEMPLIN-AEROLINK * Normative Reference DRAFT-SARIKAYA-NVO3-DHC-VXLAN-MULTICAST * Informative Reference DRAFT-KRISHNAN-DHC-DHCPV6-PRIVACY * Normative Reference DRAFT-TEMPLIN-CLIENT-CLLAO * Informative Reference DRAFT-IETF-DHC-DHCPV6-PRIVACY * Normative Reference DRAFT-TEMPLIN-DHC-CLLAO-UPDATES * Informative Reference DRAFT-MRUGALSKI-DHC-DHCPV6-PRIVACY-MITIGATION RFC6977: Triggering DHCPv6 Reconfiguration from Relay Agents (13 pages) * Replaces DRAFT-BOUCADAIR-DHC-TRIGGERED-RECONFIGURE * Informative Reference RFC5460 * Informative Reference RFC5176 * Normative Reference RFC3315 * Possible Reference RFC5741 * Informative Reference RFC4301 * Informative Reference RFC5007 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference RFC6422 * Normative Reference DRAFT-WING-DHC-DNS-RECONFIGURE * Informative Reference DRAFT-IETF-DHC-TOPO-CONF * Normative Reference DRAFT-IETF-DHC-CONN-STATUS RFC7031: DHCPv6 Failover Requirements (17 pages) * Replaces DRAFT-MRUGALSKI-DHC-DHCPV6-FAILOVER-REQUIREMENTS * Informative Reference BCP180 * Informative Reference RFC6853 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference RFC4704 * Normative Reference RFC3633 * Informative Reference RFC5970 * Informative Reference RFC2136 * Informative Reference DRAFT-GONT-DHC-STABLE-PRIVACY-ADDRESSES * Normative Reference DRAFT-ZHANG-DHC-DHCPV6-FAILURE-DETECTION * Informative Reference DRAFT-IETF-DHC-STABLE-PRIVACY-ADDRESSES RFC7037: RADIUS Option for the DHCPv6 Relay Agent (10 pages) * Normative Reference RFC5226 * Informative Reference RFC3162 * Normative Reference RFC2865 * Informative Reference RFC6334 * Informative Reference RFC3736 * Normative Reference RFC4303 * Normative Reference RFC3315 * Possible Reference RFC5741 * Informative Reference RFC3633 * Normative Reference RFC6929 * Informative Reference RFC3646 * Normative Reference BCP14 * Normative Reference RFC6911 * Normative Reference RFC4818 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC6519 RFC7083: Modification to Default Values of SOL_MAX_RT and INF_MAX_RT (7 pages) * Replaces DRAFT-DROMS-DHC-DHCPV6-SOLMAXRT-UPDATE * Updates RFC3315 * Informative Reference RFC3633 * Normative Reference RFC2119 * Normative Reference BCP14 * Possible Reference RFC5741 * Normative Reference RFC3315 * Informative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Normative Reference RFC7084 * Normative Reference DRAFT-IETF-DHC-DHCPV6-STATEFUL-ISSUES * Normative Reference DRAFT-IETF-6MAN-RESILIENT-RS * Informative Reference DRAFT-IETF-SUNSET4-NOIPV4 RFC7227: Guidelines for Creating New DHCPv6 Options (35 pages) * Informative Reference RFC6440 * Informative Reference RFC5970 * Informative Reference RFC3319 * Informative Reference RFC3986 * Informative Reference RFC3646 * Informative Reference RFC4242 * Normative Reference RFC3315 * Informative Reference STD66 * Informative Reference STD63 * Informative Reference RFC6644 * Normative Reference RFC2119 * Informative Reference RFC4436 * Informative Reference RFC6603 * Informative Reference RFC5460 * Informative Reference RFC3898 * Informative Reference RFC6059 * Informative Reference RFC6610 * Informative Reference RFC3633 * Informative Reference RFC5007 * Possible Reference RFC5741 * Informative Reference RFC3046 * Informative Reference RFC5908 * Informative Reference RFC6334 * Informative Reference RFC4085 * Informative Reference RFC4303 * Informative Reference RFC4833 * Informative Reference RFC4957 * Informative Reference RFC5986 * Informative Reference RFC5223 * Normative Reference BCP14 * Informative Reference RFC4704 * Informative Reference BCP105 * Informative Reference RFC5198 * Informative Reference RFC4075 * Informative Reference RFC2460 * Informative Reference RFC6422 * Informative Reference RFC4280 * Informative Reference RFC3629 * Updates RFC3315 * Informative Reference DRAFT-IETF-DHC-DHCPV6-STATEFUL-ISSUES * Informative Reference DRAFT-IETF-SOFTWIRE-MAP-DHCP * Normative Reference DRAFT-XUE-DHC-DYNAMIC-GRE * Informative Reference DRAFT-IETF-ROLL-MPL-PARAMETER-CONFIGURATION * Informative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Normative Reference DRAFT-WKUMARI-DHC-CAPPORT * Reference DRAFT-CROCKER-RFC2418BIS-WGGUIDELINES RFC7283: Handling Unknown DHCPv6 Messages (7 pages) * Replaces DRAFT-CSL-DHC-DHCPV6-UNKNOWN-MSG-3315UPDATE * Normative Reference RFC3315 * Normative Reference RFC2119 * Normative Reference BCP14 * Updates RFC3315 * Normative Reference RFC7341 * Informative Reference DRAFT-DHCWG-DHC-RFC3315BIS RFC7341: DHCPv4-over-DHCPv6 (DHCP 4o6) Transport (16 pages) * Replaces DRAFT-SCSKF-DHC-DHCPV4-OVER-DHCPV6 * Normative Reference RFC2119 * Normative Reference BCP14 * Normative Reference RFC4242 * Possible Reference RFC5741 * Normative Reference RFC3315 * Normative Reference RFC4361 * Normative Reference RFC7283 * Informative Reference RFC951 * Normative Reference RFC2131 * Informative Reference DRAFT-IETF-SOFTWIRE-LW4OVER6 * Informative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Informative Reference DRAFT-IETF-SAVI-DHCP * Normative Reference DRAFT-IETF-DHC-DYNAMIC-SHARED-V4ALLOCATION * Normative Reference DRAFT-CUI-DHC-DHCP4O6-ACTIVE-LEASEQUERY * Normative Reference DRAFT-CUI-DHC-DHCP4O6-BULK-ACTIVE-LEASEQUERY Extensions for Scalable DNS Service Discovery (dnssd) ------------------------------------------------------ Charter Last Modified: 2013-10-25 Current Status: Active Chairs: Ralph Droms Tim Chown Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Mailing Lists: General Discussion: dnssd@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/dnssd Archive: http://www.ietf.org/mail-archive/web/dnssd Description of Working Group: Background ---------- Zero configuration networking protocols are currently well suited to discover services within the scope of a single link. In particular, the DNS-SD [RFC 6763] and mDNS [RFC6762] protocol suite (sometimes referred to using Apple Computer Inc.'s trademark, Bonjour) are widely used for DNS-based service discovery and host name resolution on a single link. The DNS-SD/mDNS protocol suite is used in many scenarios including home, campus, and enterprise networks. However, the zero configuration mDNS protocol is constrained to link-local multicast scope by design, and therefore cannot be used to discover services on remote links. In a home network that consists of a single (possibly bridged) link, users experience the expected discovery behavior; available services appear because all devices share a common link. However, in multi-link home networks (as envisaged by the homenet WG) or in routed campus or enterprise networks, devices and users can only discover services on the same link, which is a significant limitation. This has led to calls, such as the Educause petition, to develop an appropriate service discovery solution to span multiple links or to perform discovery across a wide area, not necessarily on directly connected links. In addition, the "Smart Energy Profile 2 Application Protocol Standard", published by ZigBee Alliance and HomePlug Powerline Alliance specifies the DNS-SD/mDNS protocol suite as the basis for its method of zero configuration service discovery. However, its use of wireless mesh multi-link subnets in conjunction with traditional routed networks will require extensions to the DNS-SD/mDNS protocols to allow operation across multiple links. The scenarios in which multi-link service discovery is required may be zero configuration environments, environments where administrative configuration is supported, or a mixture of the two. As demand for service discovery across wider area routed networks grows, some vendors are beginning to ship proprietary solutions. It is thus both timely and important that efforts to develop improved, scalable, autonomous service discovery solutions for routed networks are coordinated towards producing a single, standards-based solution. Working Group Description ------------------------- The focus of the WG is to develop a solution for extended, scalable DNS-SD. This work is likely to highlight problems and challenges with naming protocols, as some level of coexistence will be required between local zero configuration name services and those forming part of the global DNS. It is important that these issues are captured and documented for further analysis; solving those problems is however not within the scope of this WG. The WG will consider the tradeoffs between reusing/extending existing protocols and developing entirely new ones. It is highly desirable that any new solution is backwardly compatible with existing DNS-SD/mDNS deployments. Any solution developed by the dnssd WG must not conflict or interfere with the operation of other zero-configuration service and naming protocols such as uPnP or LLMNR. Integration with such protocols is out of scope for this WG. Current zero configuration discovery protocols are constrained to operate within a single link, which implicitly limits the scope of discovery. In extending service discovery protocols to operate over multiple links, devices will inherently become discoverable over a wider area, which may introduce security or privacy concerns. The WG will consider such concerns when exploring the solution space for multi-link service discovery. To that end, the primary goals of the dnssd WG are as follows: 1. To document a set of requirements for scalable, autonomous DNS-based service discovery in routed, multi-link networks in the following five scenarios: (A) Personal Area networks, e.g., one laptop and one printer. This is the simplest example of a service discovery network, and may or may not have external connectivity. (B) Home networks, as envisaged by the homenet WG, consisting of one or more exit routers, with one or more upstream providers or networks, and an arbitrary internal topology with heterogeneous media where routing is automatically configured. The home network would typically be a single zero configuration administrative domain with a relatively limited number of devices. (C) Wireless 'hotspot' networks, which may include wireless networks made available in public places, or temporary or permanent infrastructures targeted towards meeting or conference style events, e.g., as provided for IETF meetings. In such environments other devices may be more likely to be 'hostile' to the user. (D) Enterprise networks, consisting of larger routed networks, with large numbers of devices, which may be deployments spanning over multiple sites with multiple upstreams, and one more more administrative domains (depending on internal administrative delegation). The large majority of the forwarding and security devices are configured. These may be commercial or academic networks, with differing levels of administrative control over certain devices on the network, and BYOD devices commonplace in the campus scenario. (E) Mesh networks such as RPL/6LoWPAN, with one or more links per routable prefix, which may or may not have external connectivity. The topology may use technologies including 802.11 wireless, HomePlug AV and GP, and ZigBee IP. In the above scenarios, the aim is to facilitate service discovery across the defined site. It is also desirable that a user or device, when away from such a site, is still able to discover services within that site, e.g. a user discovering services in their home network while remote from it. It is also desirable that multiple discovery scopes are supported, from the point of view of either performing discovery within a specified scope or advertisement within a specified scope, and being able to discover (enumerate) the set of scopes such that an application could then choose to do either. It should be noted that scope in this sense might refer to 'building' or 'room' and thus might have no correlation to network topology. 2. To develop an improved, scalable solution for service discovery that can operate in multi-link networks, where devices may be in neighboring or non-neighboring links, applicable to the scenarios above. The solution will consider tradeoffs between reusing/extending existing protocols and developing entirely new protocols. The solution should include documentation or definition of the interfaces that can be implemented, separately to transport of the information. 3. To document challenges and problems encountered in the coexistence of zero configuration and global DNS name services in such multi-link networks, including consideration of both the name resolution mechanism and the namespace. It is important that the dnssd WG takes input from stakeholders in the scenarios it is considering. For example, the homenet WG is currently evaluating its own requirements for naming and service discovery; it is up to the homenet WG as to whether it wishes to recommend adoption of the solution developed in the dnssd WG, but coordination between the WGs is desirable. Goals and Milestones: Sep 2013 - Formation of the WG Oct 2013 - Adopt requirements draft as WG document Jan 2014 - Submit requirements draft to the IESG as an Informational RFC Mar 2014 - Adopt wide-area service discovery solution draft as WG document Mar 2014 - Adopt Informational document on the problems and challenges arising for zeroconf and unicast DNS name services Sep 2014 - Submit wide-area service discovery solution draft to the IESG as Standards Track RFC Sep 2014 - Submit the zeroconf and unicast DNS "problems and challenges" draft to the IESG as Informational. Internet-Drafts: - Hybrid Unicast/Multicast DNS-Based Service Discovery [draft-ietf-dnssd-hybrid-00] (19 pages) - On Interoperation of Labels Between mDNS and DNS [draft-ietf-dnssd-mdns-dns-interop-00] (8 pages) - DNS Push Notifications [draft-ietf-dnssd-push-00] (17 pages) - Requirements for Scalable DNS-SD/mDNS Extensions [draft-ietf-dnssd-requirements-06] (13 pages) No Requests for Comments Home Networking (homenet) ------------------------- Charter Last Modified: 2014-08-19 Current Status: Active Chairs: Mark Townsley Ray Bellis Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Tech Advisor: Acee Lindem Mailing Lists: General Discussion: homenet@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/homenet Archive: http://www.ietf.org/mail-archive/web/homenet/ Description of Working Group: This working group focuses on the evolving networking technology within and among relatively small "residential home" networks. For example, an obvious trend in home networking is the proliferation of networking technology in an increasingly broad range and number of devices. This evolution in scale and diversity sets some requirements on IETF protocols. Some of the relevant trends include: o Multiple segments: While less complex L3-toplogies involving as few subnets as possible are preferred in home networks for a variety of reasons including simpler management and service discovery, the introduction of more than one subnet into a home network is enough to add complexity that needs to be addressed, and multiple dedicated segments are necessary for some cases. For instance, a common feature in modern home routers in the ability to support both guest and private network segments. Also, link layer networking technology is poised to become more heterogeneous, as networks begin to employ both traditional Ethernet technology and link layers designed for low-powered sensor networks. Finally, similar needs for segmentation may occur in other cases, such as separating building control or corporate extensions from the Internet access network for the home. Different segments may be associated with subnets that have different routing and security policies. o Service providers are deploying IPv6, and support for IPv6 is increasingly available in home gateway devices. While IPv6 resembles IPv4 in many ways, it changes address allocation principles and allows direct IP addressability and routing to devices in the home from the Internet. This is a promising area in IPv6 that has proved challenging in IPv4 with the proliferation of NAT. o End-to-end communication is both an opportunity and a concern as it enables new applications but also exposes nodes in the internal networks to receipt of unwanted traffic from the Internet. Firewalls that restrict incoming connections may be used to prevent exposure, however, this reduces the efficacy of end-to-end connectivity that IPv6 has the potential to restore. Home networks need to provide the tools to handle these situations in a manner accessible to all users of home networks. Manual configuration is rarely, if at all, possible, as the necessary skills and in some cases even suitable management interfaces are missing. The purpose of this working group is to focus on this evolution, in particular as it addresses the introduction of IPv6, by developing an architecture addressing this full scope of requirements: o prefix configuration for routers o managing routing o name resolution o service discovery o network security The task of the group is to produce an architecture document that outlines how to construct home networks involving multiple routers and subnets. This document is expected to apply the IPv6 addressing architecture, prefix delegation, global and ULA addresses, source address selection rules and other existing components of the IPv6 architecture, as appropriate. The architecture document should drive what protocols changes, if any, are necessary. Specific protocol work described below is expected to be within the scope of the working group once the architecture work is complete. However, the group is required to review its charter and milestones with the IESG and IETF community before submitting documents that make protocol changes. It is expected that the group has to discuss some of the below solutions, however, in order to complete the architecture work. The group will apply existing protocols to handle the five requirements above. For prefix configuration, existing protocols are likely sufficient, and at worst may need some small enhancements, such as new options. For automatic routing, it is expected that existing routing protocols can be used as is, however, a new mechanism may be needed in order to turn a selected protocol on by default. For name resolution and service discovery, extensions to existing multicast-based name resolution protocols are needed to enable them to work across subnets. For network security, the group shall document the concept of "advanced security" as a further development of "simple security" from RFC 6092. The main goal of this work is to enable a security policy that adapts to IPv6 threats as they emerge, taking into account not only traffic from the Internet at large, but within and leaving the home network itself. It is expected that the working group will define a set of protocol specifications to accomplish the five requirements from above. However, it is not in the scope of the working group to define entirely new routing protocols or address allocation protocols. As noted, additional options or other small extensions may be necessary to use the existing protocols in these new configuration tasks. The working group shall also not make any changes to IPv6 protocols or addressing architecture. Prefix configuration, routing, and security related work shall not cause any changes that are not backwards compatible to existing IPv6 hosts. There may be host visible changes in the work on naming and discovery protocols, however. In its design, the working group shall also consider security aspects and the impact on manageability. The main focus of the working group is home networks, but the group's results may also find applications in other small networks. The group should assume that an IPv4 network may have to co-exist alongside the IPv6 network and should take this into account insofar as alignment with IPv6 is desirable. But the group should also ensure that even IPv6-only are possible, and while IP-version agnostic work is of course desirable, IPv4-specific work is outside the scope of the group. The working group will liaise with the relevant IETF working groups. In particular, the group should work closely with the V6OPS working group, review any use or extension of DHCP with the DHC working group, and work with additional DNS requirements with the DNSEXT and DNSOP working groups. If it turns out that additional options are needed for a routing protocol, they will be developed in the appropriate Routing Area working group, with the HOMENET working group providing the architecture and requirements for such enhancements. The working group will also liason with external standards bodies where it is expected that there are normative dependencies between the specifications of the two bodies. It is expected that in the architecture definition stage liaising with the Broadband Forum, DLNA, UPnP Forum, OASIS, ZigBee Alliance and other SDOs is necessary, as is understanding existing technology from these groups. Goals and Milestones: Done - Formation of the working group Done - First WG draft on the architecture Done - Submission of the architecture draft to the IESG as Informational RFC Dec 2011 - Charter re-evaluation based on the architecture work Dec 2011 - First WG draft on prefix configuration Dec 2011 - First WG draft on routing Jan 2012 - First WG draft on name resolution Feb 2012 - First WG draft on service discovery Feb 2012 - First WG draft on perimeter security Feb 2012 - Start of routing related work in the relevant routing area working group, if needed Mar 2012 - Submission of the prefix configuration draft to the IESG as Standards Track RFC Apr 2012 - Submission of the routing draft to the IESG as Informational RFC Sep 2012 - Submission of the name resolution draft to the IESG as Standards Track RFC Nov 2012 - Submission of the service discovery draft to the IESG as Standards Track RFC Dec 2012 - Submission of the perimeter security draft to the IESG as Informational RFC Internet-Drafts: - IPv6 Home Networking Architecture Principles [draft-ietf-homenet-arch-17] (49 pages) - Distributed Node Consensus Protocol [draft-ietf-homenet-dncp-01] (28 pages) - Outsourcing Home Network Authoritative Naming Service [draft-ietf-homenet-front-end-naming-delegation-01] (25 pages) - Home Networking Control Protocol [draft-ietf-homenet-hncp-04] (29 pages) - Auto-Configuration of a Network of Hybrid Unicast/Multicast DNS-Based Service Discovery Proxy Nodes [draft-ietf-homenet-hybrid-proxy-zeroconf-00] (15 pages) - DHCP Options for Homenet Naming Architecture [draft-ietf-homenet-naming-architecture-dhc-options-01] (28 pages) - Distributed Prefix Assignment Algorithm [draft-ietf-homenet-prefix-assignment-03] (18 pages) - Outsourcing Home Network Authoritative Naming Service [draft-mglt-homenet-front-end-naming-delegation-04] (21 pages) - DHCP Options for Homenet Naming Architecture [draft-mglt-homenet-naming-architecture-dhc-options-02] (24 pages) - Prefix and Address Assignment in a Home Network [draft-pfister-homenet-prefix-assignment-02] (29 pages) - Home Networking Control Protocol [draft-stenberg-homenet-hncp-00] (27 pages) Requests for Comments: RFC7368: IPv6 Home Networking Architecture Principles (49 pages) * Replaces DRAFT-CHOWN-HOMENET-ARCH * Informative Reference RFC6887 * Informative Reference RFC6762 * Normative Reference RFC2460 * Informative Reference RFC2775 * Informative Reference DRAFT-IETF-OSPF-OSPFV3-AUTOCONFIG * Informative Reference RFC5533 * Informative Reference DRAFT-VYNCKE-ADVANCED-IPV6-SECURITY * Informative Reference BCP38 * Informative Reference RFC4862 * Informative Reference DRAFT-IETF-V6OPS-6204BIS * Informative Reference RFC6092 * Informative Reference DRAFT-IETF-V6OPS-IPV6-MULTIHOMING-WITHOUT-IPV6NAT * Informative Reference RFC6724 * Informative Reference RFC1918 * Informative Reference RFC6333 * Normative Reference RFC3633 * Informative Reference RFC6177 * Informative Reference RFC3002 * Informative Reference RFC5969 * Informative Reference BCP157 * Normative Reference RFC4291 * Informative Reference BCP5 * Informative Reference RFC2475 * Informative Reference RFC5890 * Informative Reference RFC4864 * Informative Reference RFC6204 * Informative Reference RFC4941 * Normative Reference RFC4193 * Informative Reference RFC2827 * Informative Reference RFC4192 * Informative Reference RFC6555 * Informative Reference RFC4191 * Informative Reference DRAFT-IETF-CORE-COAP * Informative Reference RFC6296 * Informative Reference RFC6145 * Informative Reference RFC6144 * Informative Reference RFC6824 * Informative Reference RFC4033 * Informative Reference RFC3022 * Normative Reference DRAFT-IETF-DNSSD-REQUIREMENTS * Informative Reference RFC7421 * Informative Reference DRAFT-IETF-HOMENET-FRONT-END-NAMING-DELEGATION * Informative Reference DRAFT-IETF-SOFTWIRE-MAP-DEPLOYMENT * Informative Reference DRAFT-IETF-LMAP-FRAMEWORK * Informative Reference DRAFT-STENBERG-HOMENET-MINIMALIST-PCP-PROXY * Informative Reference DRAFT-IETF-HOMENET-HNCP * Informative Reference DRAFT-MRW-HOMENET-RTG-COMPARISON * Informative Reference DRAFT-GENG-HOMENET-MPVD-USE-CASES Host Identity Protocol (hip) ---------------------------- Charter Last Modified: 2013-03-13 Current Status: Active Chair: Gonzalo Camarillo Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Mailing Lists: General Discussion: hipsec@ietf.org To Subscribe: http://www.ietf.org/mailman/listinfo/hipsec Archive: http://www.ietf.org/mail-archive/web/hipsec/ Description of Working Group: The Host Identity Protocol (HIP) provides a method of separating the end-point identifier and locator roles of IP addresses. It introduces a new Host Identity (HI) name space, based on public keys, from which end-point identifiers are taken. The public keys are typically, but not necessarily, self generated. HIP uses existing IP addressing and forwarding for locators and packet delivery. The architecture and protocol details for these mechanisms are currently specified in the following Experimental RFCs: o HIP Architecture (RFC 4423) o Host Identity Protocol (RFC 5201) There are several publicly known interoperating implementations, some of which are open source. The HIP WG was chartered to publish protocol specifications in documents whose quality and security properties would meet the requirements for publication as standards track documents. These specifications have been published as Experimental RFCs, because the effects of the protocol on applications and on the Internet as a whole were unknown. The Experimental RFCs produced by the HIP WG allowed the community to experiment with HIP technologies and learn from these experiments. The HIP WG will now produce standards track versions of the main HIP RFCs taking as a base the existing Experimental RFCs. The WG will also specify certificate handling in HIP in a standards track RFC. Additionally, the WG will finish the WG items it was working on before starting the standards track work. These WG items relate to how to build HIP-based overlays and will result in Experimental RFCs. The following are charter items for the working group: o Revise RFCs 4423, 4843, 5201, 5202, 5203, 5204, 5205, 5206, and 5770 as standards track RFCs. o Specify in a standards track RFC how to carry certificates in the base exchange. This was removed from the base HIP spec so that the mechanism is specified in a stand-alone spec. o Specify in an Experimental RFC how to build a HIP-based overlay using RELOAD. o Specify in an Experimental RFC how to transport HIP messages over encrypted connections that were established using HIP. Goals and Milestones: Done - Submit Native API specification to the IESG Done - Submit Framework for HIP overlays specification to the IESG Done - Submit Multi-hop routing mechanism for HIP Done - Submit Upper-layer data transport in HIP to the IESG Done - WGLC Certs in HIP base exchange specification Done - WGLC the HIP over HIP specification Done - Submit Certs in HIP base exchange to the IESG as Experimental Done - Submit the HIP over HIP specification to the IESG Mar 2011 - WGLC the specification on how to build HIP-based overlays using RELOAD Apr 2011 - Submit the specification on how to build HIP-based overlays using RELOAD to the IESG May 2011 - WGLC RFC4423bis May 2011 - WGLC RFC4843bis May 2011 - WGLC RFC5201bis May 2011 - WGLC RFC5202bis Jun 2011 - Submit RFC5201bis to the IESG Jun 2011 - Submit RFC4843bis to the IESG Jun 2011 - Submit RFC4423bis to the IESG Jun 2011 - Submit RFC5202bis to the IESG Jul 2011 - WGLC RFC5203bis Jul 2011 - WGLC RFC5204bis Jul 2011 - WGLC RFC5205bis Jul 2011 - WGLC the mobility portion of RFC5206bis Aug 2011 - Submit RFC5203bis to the IESG Aug 2011 - Submit RFC5204bis to the IESG Aug 2011 - Submit RFC5205bis to the IESG Aug 2011 - Submit the mobility portion of RFC5206bis to the IESG Sep 2011 - WGLC RFC5770bis Sep 2011 - WGLC the multihoming portion of RFC5206bis Oct 2011 - Submit RFC5770bis to the IESG Oct 2011 - Submit the multihoming portion of RFC5206bis to the IESG Nov 2011 - WGLC Certs in HIP base exchange specification (referencing RFC5201bis) Dec 2011 - Submit Certs in HIP base exchange (referencing RFC5201bis) to the IESG as PS Jan 2012 - Recharter or close the WG Internet-Drafts: - Using the Host Identity Protocol with Legacy Applications [draft-ietf-hip-applications-04] (14 pages) - Host Identity Protocol (HIP) Architecture [draft-ietf-hip-arch-03] (24 pages) - Host Identity Protocol [draft-ietf-hip-base-10] (104 pages) - HIP BONE: Host Identity Protocol (HIP) Based Overlay Networking Environment (BONE) [draft-ietf-hip-bone-07] (21 pages) - Host Identity Protocol Certificates [draft-ietf-hip-cert-12] (12 pages) - Host Identity Protocol (HIP) Domain Name System (DNS) Extensions [draft-ietf-hip-dns-09] (17 pages) - Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP) [draft-ietf-hip-esp-06] (30 pages) - Host Identity Protocol (HIP) Immediate Carriage and Conveyance of Upper-Layer Protocol Signaling (HICCUPS) [draft-ietf-hip-hiccups-05] (17 pages) - End-Host Mobility and Multihoming with the Host Identity Protocol [draft-ietf-hip-mm-05] (40 pages) - Host Multihoming with the Host Identity Protocol [draft-ietf-hip-multihoming-05] (21 pages) - Basic Host Identity Protocol (HIP) Extensions for Traversal of Network Address Translators [draft-ietf-hip-nat-traversal-09] (34 pages) - Basic Socket Interface Extensions for the Host Identity Protocol (HIP) [draft-ietf-hip-native-api-12] (18 pages) - Native NAT Traversal Mode for the Host Identity Protocol [draft-ietf-hip-native-nat-traversal-08] (13 pages) - Encrypted Signaling Transport Modes for the Host Identity Protocol [draft-ietf-hip-over-hip-06] (13 pages) - Host Identity Protocol (HIP) Registration Extension [draft-ietf-hip-registration-02] (13 pages) - Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD) [draft-ietf-hip-reload-instance-10] (10 pages) - Host Identity Protocol Architecture [draft-ietf-hip-rfc4423-bis-09] (39 pages) - An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers Version 2 (ORCHIDv2) [draft-ietf-hip-rfc4843-bis-08] (14 pages) - Host Identity Protocol Version 2 (HIPv2) [draft-ietf-hip-rfc5201-bis-20] (131 pages) - Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP) [draft-ietf-hip-rfc5202-bis-07] (38 pages) - Host Identity Protocol (HIP) Registration Extension [draft-ietf-hip-rfc5203-bis-06] (14 pages) - Host Identity Protocol (HIP) Rendezvous Extension [draft-ietf-hip-rfc5204-bis-05] (14 pages) - Host Identity Protocol (HIP) Domain Name System (DNS) Extension [draft-ietf-hip-rfc5205-bis-06] (16 pages) - Host Mobility with the Host Identity Protocol [draft-ietf-hip-rfc5206-bis-08] (33 pages) - Host Identity Protocol Certificates [draft-ietf-hip-rfc6253-bis-01] (12 pages) - Host Identity Protocol (HIP) Rendezvous Extension [draft-ietf-hip-rvs-05] (15 pages) - Host Identity Protocol (HIP) Multi-Hop Routing Extension [draft-ietf-hip-via-03] (10 pages) Requests for Comments: RFC4423: Host Identity Protocol (HIP) Architecture (24 pages) * Informative Reference RFC3102 * Informative Reference BCP78 * Informative Reference RFC2766 * Informative Reference RFC4035 * Informative Reference RFC4034 * Informative Reference RFC4225 * Informative Reference RFC4033 * Informative Reference RFC4025 * Informative Reference RFC2136 * Informative Reference RFC3022 * Informative Reference RFC4306 * Informative Reference DRAFT-SARIKAYA-6LO-BOOTSTRAPPING-SOLUTION * Informative Reference DRAFT-IETF-HIP-RFC4423-BIS * Informative Reference DRAFT-NIKANDER-ESP-BEET-MODE * Informative Reference RFC5201 * Informative Reference DRAFT-TEMPLIN-IPVLX * Informative Reference RFC4907 * Informative Reference RFC6538 * Normative Reference RFC5206 * Informative Reference DRAFT-TSCHOFENIG-HIPRG-HIP-NATFW-TRAVERSAL * Informative Reference RFC5205 * Informative Reference RFC5204 * Informative Reference RFC5482 * Informative Reference RFC4830 * Informative Reference RFC5202 * Normative Reference DRAFT-IETF-SHIM6-APPLICABILITY * Informative Reference RFC5203 * Normative Reference RFC5207 * Informative Reference DRAFT-KORHONEN-MOBOPTS-LINK-CHARACTERISTICS-PS * Informative Reference DRAFT-TSCHOFENIG-NSIS-GIST-SECURITY * Informative Reference RFC4831 * Normative Reference DRAFT-SCHMITT-HIP-NAT-TRAVERSAL * Normative Reference RFC5770 * Informative Reference DRAFT-THALER-MOBILITY-COMPARISON * Informative Reference DRAFT-MELIA-MIPSHOP-NIHO-PS * Informative Reference DRAFT-KORHONEN-MOBOPTS-DELIVERY-ANALYSIS * Informative Reference DRAFT-LINDQVIST-HIP-TCP-PIGGYBACKING * Reference DRAFT-MELIA-MIPSHOP-MOBILITY-SERVICES-PS * Normative Reference DRAFT-IVANCIC-MOBILE-PLATFORMS-PROBLEM * Normative Reference RFC6316 * Informative Reference DRAFT-STIEMERLING-P2PSIP-IMPL * Normative Reference RFC6317 * Informative Reference RFC5164 * Normative Reference DRAFT-FARINACCI-LISP * Informative Reference DRAFT-NIKANDER-RAM-GENERIX-PROXYING * Informative Reference DRAFT-BEHRINGER-BGP-SESSION-SEC-REQ * Possible Reference DRAFT-VIDYA-IP-MOBILITY-MULTIHOMING-INTERACTIONS * Informative Reference DRAFT-NIKANDER-RAM-ILSE * Informative Reference DRAFT-NIKANDER-RAM-PASH * Informative Reference DRAFT-KORHONEN-MOBOPTS-MOBILITY-POLICY * Reference DRAFT-BONAVENTURE-IRTF-RRG-RIRA * Informative Reference DRAFT-CARPENTER-IDLOC-MAP-CONS * Informative Reference DRAFT-BRISCOE-TSVWG-ECN-TUNNEL * Normative Reference DRAFT-HAUTAKORPI-P2PSIP-WITH-HIP * Informative Reference DRAFT-PERERA-MOBOPTS-MOTIVATION-CAM * Informative Reference DRAFT-SCHUETZ-NID-ARCH * Informative Reference DRAFT-BAUMGART-P2PSIP-P2PNS * Informative Reference DRAFT-IETF-RPSEC-BGP-SESSION-SEC-REQ * Normative Reference DRAFT-JIANG-HIPRG-HHIT-ARCH * Informative Reference DRAFT-ZELTSAN-TERMINOLOGY-NETLMM * Informative Reference DRAFT-XU-RRG-HRA * Informative Reference DRAFT-THALER-IP-MODEL-EVOLUTION * Informative Reference RFC6250 * Informative Reference DRAFT-LEE-HIP-OBJECT * Informative Reference RFC5720 * Normative Reference DRAFT-CAO-HIP-GEOLOCATION * Informative Reference DRAFT-HADDAD-PREFIX-REACHABILITY-DETECTION * Normative Reference DRAFT-MEYER-LOC-ID-IMPLICATIONS * Normative Reference DRAFT-PONOMAREV-HIP-HIT2IP * Informative Reference DRAFT-IETF-HIP-RFC5202-BIS * Informative Reference RFC6115 * Informative Reference RFC6306 * Normative Reference DRAFT-VARJONEN-HIP-SRP * Normative Reference DRAFT-KUPTSOV-SAVA-HIP * Reference DRAFT-XU-RANGI * Normative Reference DRAFT-VARJONEN-HIP-EAP * Normative Reference DRAFT-IYENGAR-FORD-TNG * Informative Reference DRAFT-LEE-OBJECT-NAMING * Informative Reference RFC6319 * Informative Reference DRAFT-MGLT-IPSEC-MM-REQUIREMENTS * Normative Reference DRAFT-PONOMAREV-HIP-ECC * Informative Reference DRAFT-MOSKOWITZ-RFC5201-BIS * Informative Reference DRAFT-MOSKOWITZ-HIP-RFC5201-BIS * Possible Reference DRAFT-MOSKOWITZ-RFC4423-BIS * Possible Reference DRAFT-MOSKOWITZ-HIP-RFC4423-BIS * Normative Reference DRAFT-HENDERSON-HIP-RFC5206-BIS * Informative Reference DRAFT-HENDERSON-HIP-VPLS * Normative Reference DRAFT-WANG-HIPRG-SERVICE-OVERLAY * Informative Reference DRAFT-JOKELA-HIP-RFC5202-BIS * Informative Reference DRAFT-OFLYNN-CORE-BOOTSTRAPPING * Informative Reference RFC6281 * Informative Reference DRAFT-MOSKOWITZ-HIP-RG-DEX * Normative Reference DRAFT-XU-HIP-HIERARCHICAL * Informative Reference DRAFT-IETF-HIP-RFC5203-BIS * Informative Reference DRAFT-IETF-HIP-RFC5204-BIS * Informative Reference DRAFT-IETF-HIP-RFC5205-BIS * Informative Reference DRAFT-IETF-HIP-RFC5201-BIS * Informative Reference DRAFT-IETF-HIP-RFC5206-BIS * Informative Reference DRAFT-IETF-HIP-MULTIHOMING * Normative Reference DRAFT-LIANG-IDR-AIRA * Informative Reference DRAFT-SARIKAYA-CORE-SBOOTSTRAPPING * Informative Reference DRAFT-BOOT-AUTOCONF-SUPPORT4HOSTS * Normative Reference DRAFT-CAO-HIPRG-FLOW-MOBILITY * Normative Reference DRAFT-PERKINS-DMM-MATRIX * Normative Reference RFC6629 * Normative Reference DRAFT-DYKIM-RECURSIVE-ADDRESSING * Informative Reference DRAFT-SARIKAYA-ACE-SECURE-BOOTSTRAPPING * Normative Reference DRAFT-DYKIM-NARA * Informative Reference DRAFT-KHAN-OBJECT-NAMING * Informative Reference DRAFT-CHIAPPA-LISP-ARCHITECTURE * Informative Reference DRAFT-MOSKOWITZ-HIP-DEX * Informative Reference DRAFT-SARIKAYA-SOLACE-SETUP-FRAMEWORK * Normative Reference DRAFT-LIU-WIFI-FAST-RECOVERY * Informative Reference DRAFT-IETF-LISP-ARCHITECTURE * Informative Reference DRAFT-SARIKAYA-CORE-SECURE-BOOTSOLUTION * Informative Reference DRAFT-IETF-LISP-PERSPECTIVE * Normative Reference DRAFT-RAFIEE-SECAUTH-USECASE RFC5201: Host Identity Protocol (104 pages) * Normative Reference RFC4282 * Normative Reference RFC3484 * Normative Reference RFC5202 * Informative Reference RFC5205 * Informative Reference RFC5204 * Informative Reference RFC5206 * Normative Reference RFC2898 * Normative Reference RFC768 * Informative Reference RFC2460 * Normative Reference RFC3602 * Normative Reference RFC2463 * Normative Reference BCP14 * Informative Reference BCP78 * Normative Reference RFC2451 * Normative Reference RFC1035 * Informative Reference RFC2434 * Normative Reference RFC2536 * Normative Reference STD13 * Informative Reference RFC4423 * Normative Reference RFC3526 * Normative Reference RFC3972 * Informative Reference STD5 * Normative Reference RFC2119 * Informative Reference BCP26 * Normative Reference RFC3110 * Informative Reference RFC792 * Normative Reference RFC4843 * Normative Reference RFC4034 * Normative Reference RFC4307 * Informative Reference RFC4306 * Informative Reference RFC2412 * Normative Reference RFC2404 * Updates RFC6253 * Informative Reference DRAFT-OHBA-6TSCH-SECURITY * Informative Reference RFC7045 * Informative Reference DRAFT-SEITZ-ACE-DESIGN-CONSIDERATIONS * Informative Reference DRAFT-NIKANDER-ESP-BEET-MODE * Informative Reference RFC6538 * Normative Reference RFC5206 * Normative Reference RFC5205 * Normative Reference RFC5204 * Informative Reference RFC5338 * Informative Reference RFC5387 * Normative Reference RFC5202 * Normative Reference DRAFT-IETF-SHIM6-APPLICABILITY * Reference DRAFT-AHRENHOLZ-HIPRG-DHT * Normative Reference RFC5203 * Informative Reference RFC5533 * Normative Reference RFC5207 * Normative Reference RFC5770 * Informative Reference RFC5687 * Informative Reference DRAFT-IETF-BTNS-C-API * Normative Reference RFC6317 * Normative Reference RFC6092 * Informative Reference RFC6252 * Informative Reference DRAFT-LARSSON-MEXT-FLOW-DISTRIBUTION-RULES * Normative Reference DRAFT-HEER-HIP-MIDDLE-AUTH * Normative Reference RFC6079 * Normative Reference DRAFT-VARJONEN-HIP-CERT * Normative Reference RFC6253 * Normative Reference DRAFT-JIANG-HIPRG-HHIT-ARCH * Normative Reference DRAFT-MELEN-HIP-MR * Normative Reference DRAFT-URIEN-HIP-TAG * Informative Reference DRAFT-OHBA-6TISCH-SECURITY * Informative Reference DRAFT-LEE-HIP-OBJECT * Informative Reference DRAFT-NIKANDER-HIP-HICCUPS * Normative Reference DRAFT-CAO-HIP-GEOLOCATION * Informative Reference RFC6940 * Informative Reference RFC6071 * Informative Reference DRAFT-THALER-IPV6-SAF * Informative Reference RFC6115 * Normative Reference DRAFT-HEER-HIP-SERVICE * Normative Reference DRAFT-DONG-ESP-SA-CGA * Normative Reference DRAFT-VARJONEN-HIP-SRP * Informative Reference DRAFT-CARPENTER-BEHAVE-REFERRAL-OBJECT * Normative Reference DRAFT-ZHANG-HIP-HI-REVOCATION * Normative Reference DRAFT-ZHANG-SHEN-SA-CGA * Informative Reference RFC6709 * Normative Reference DRAFT-VARJONEN-HIP-EAP * Normative Reference DRAFT-CAMARILLO-HIP-VIA * Normative Reference DRAFT-KERANEN-HIP-RELOAD-INSTANCE * Normative Reference DRAFT-MELEN-HIP-PROXY * Informative Reference DRAFT-LEE-OBJECT-NAMING * Informative Reference DRAFT-MGLT-IPSEC-MM-REQUIREMENTS * Normative Reference DRAFT-URIEN-HIP-IOT * Normative Reference DRAFT-PONOMAREV-HIP-ECC * Informative Reference RFC6301 * Normative Reference RFC6078 * Normative Reference RFC6028 * Possible Reference DRAFT-MOSKOWITZ-RFC5201-BIS * Normative Reference DRAFT-MOSKOWITZ-HIP-RFC5201-BIS * Possible Reference DRAFT-MOSKOWITZ-RFC4423-BIS * Possible Reference DRAFT-MOSKOWITZ-HIP-RFC4423-BIS * Normative Reference DRAFT-HENDERSON-HIP-RFC5206-BIS * Informative Reference DRAFT-CARPENTER-GROBJ-REQTS * Normative Reference RFC7086 * Normative Reference DRAFT-KERANEN-HIP-OVER-HIP * Normative Reference DRAFT-HENDERSON-HIP-VPLS * Normative Reference DRAFT-WANG-HIPRG-SERVICE-OVERLAY * Normative Reference DRAFT-ZHANG-HIP-PRIVACY-PROTECTION * Normative Reference DRAFT-JOKELA-HIP-RFC5202-BIS * Normative Reference DRAFT-KERANEN-HIP-NATIVE-NAT-TRAVERSAL * Informative Reference RFC6261 * Normative Reference DRAFT-IRTF-HIPRG-REVOCATION * Normative Reference RFC6537 * Normative Reference DRAFT-IRTF-HIPRG-RFID * Normative Reference DRAFT-MOSKOWITZ-HIP-RG-DEX * Normative Reference DRAFT-XU-HIP-HIERARCHICAL * Normative Reference DRAFT-YUAN-HIPRG-FAILURE-DETECTION-RECOVERY * Normative Reference DRAFT-LAGUTIN-HIP-PLA * Normative Reference DRAFT-IETF-HIP-RFC4423-BIS * Normative Reference DRAFT-IETF-HIP-RFC5203-BIS * Normative Reference DRAFT-IETF-HIP-RFC5204-BIS * Normative Reference DRAFT-IETF-HIP-RFC5205-BIS * Informative Reference DRAFT-IETF-HIP-RFC5201-BIS * Normative Reference DRAFT-IETF-HIP-RFC5206-BIS * Informative Reference DRAFT-IETF-HIP-NATIVE-NAT-TRAVERSAL * Informative Reference DRAFT-MONGAZON-TCPM-TCP-REHASH * Normative Reference DRAFT-PELLIKKA-HIPRG-CERTREQ * Informative Reference DRAFT-BOUCADAIR-INTAREA-NAT-REVEAL-ANALYSIS * Normative Reference DRAFT-KUPTSOV-HHIT * Normative Reference DRAFT-CAO-HIPRG-LEGACY-HOST * Informative Reference DRAFT-GARCIA-CORE-SECURITY * Normative Reference DRAFT-SHIMA-CLOUDS-NET-PORTABILITY-REQS-AND-MODELS * Informative Reference DRAFT-ARKKO-CORE-SECURITY-ARCH * Normative Reference RFC6629 * Informative Reference RFC6967 * Informative Reference DRAFT-AKS-CRYPTO-SENSORS * Normative Reference DRAFT-HUMMEN-HIP-MIDDLE-PUZZLE * Informative Reference DRAFT-KHAN-OBJECT-NAMING * Normative Reference DRAFT-IETF-HIP-RFC5202-BIS * Normative Reference DRAFT-MOSKOWITZ-HIP-DEX * Normative Reference DRAFT-CARPENTER-6MAN-EXT-TRANSMIT * Informative Reference DRAFT-LORENZIN-SACM-TNC-INFORMATION-MODEL * Normative Reference DRAFT-GONT-OPSEC-IPV6-EH-FILTERING * Normative Reference DRAFT-GONT-6MAN-IPV6-OPT-TRANSMIT * Informative Reference DRAFT-COMBINED-SACM-INFORMATION-MODEL * Informative Reference DRAFT-IETF-SACM-INFORMATION-MODEL * Normative Reference DRAFT-IETF-HIP-MULTIHOMING * Normative Reference DRAFT-OHBA-MLE-HIP-DEX RFC5202: Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP) (30 pages) * Normative Reference RFC5201 * Informative Reference RFC3260 * Informative Reference BCP78 * Informative Reference RFC5206 * Informative Reference RFC3474 * Normative Reference RFC3602 * Normative Reference RFC4303 * Informative Reference RFC4301 * Informative Reference RFC4423 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference RFC2404 * Informative Reference RFC4306 * Normative Reference RFC5201 * Informative Reference RFC6538 * Normative Reference RFC5206 * Normative Reference RFC5770 * Normative Reference DRAFT-HEER-HIP-MIDDLE-AUTH * Normative Reference RFC6079 * Informative Reference DRAFT-NIKANDER-HIP-HICCUPS * Informative Reference RFC6071 * Informative Reference DRAFT-MGLT-IPSEC-MM-REQUIREMENTS * Informative Reference RFC6078 * Normative Reference DRAFT-MOSKOWITZ-RFC5201-BIS * Normative Reference DRAFT-MOSKOWITZ-HIP-RFC5201-BIS * Normative Reference DRAFT-MOSKOWITZ-RFC4423-BIS * Normative Reference DRAFT-MOSKOWITZ-HIP-RFC4423-BIS * Normative Reference DRAFT-HENDERSON-HIP-RFC5206-BIS * Normative Reference DRAFT-KERANEN-HIP-OVER-HIP * Normative Reference DRAFT-HENDERSON-HIP-VPLS * Normative Reference DRAFT-KERANEN-HIP-NATIVE-NAT-TRAVERSAL * Informative Reference RFC6261 * Normative Reference DRAFT-MOSKOWITZ-HIP-RG-DEX * Normative Reference DRAFT-IETF-HIP-RFC4423-BIS * Normative Reference DRAFT-IETF-HIP-RFC5201-BIS * Normative Reference DRAFT-IETF-HIP-RFC5206-BIS * Normative Reference DRAFT-IETF-HIP-NATIVE-NAT-TRAVERSAL * Informative Reference DRAFT-IETF-HIP-RFC5202-BIS * Normative Reference DRAFT-IETF-HIP-MULTIHOMING * Normative Reference DRAFT-MOSKOWITZ-HIP-DEX RFC5203: Host Identity Protocol (HIP) Registration Extension (13 pages) * Normative Reference RFC5201 * Informative Reference BCP78 * Informative Reference RFC5204 * Informative Reference RFC4423 * Informative Reference RFC3234 * Normative Reference RFC2434 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference BCP14 * Informative Reference RFC6538 * Normative Reference RFC5204 * Normative Reference RFC5770 * Normative Reference DRAFT-HEER-HIP-MIDDLE-AUTH * Normative Reference DRAFT-MELEN-HIP-MR * Normative Reference DRAFT-MELEN-HIP-NAT-MM * Normative Reference DRAFT-HEER-HIP-SERVICE * Normative Reference DRAFT-KUPTSOV-SAVA-HIP * Reference DRAFT-ZHANG-HIP-HIERARCHICAL-PARAMETER * Normative Reference DRAFT-KERANEN-HIP-NATIVE-NAT-TRAVERSAL * Normative Reference DRAFT-XU-HIP-HIERARCHICAL * Normative Reference DRAFT-IETF-HIP-RFC4423-BIS * Informative Reference DRAFT-IETF-HIP-RFC5203-BIS * Normative Reference DRAFT-IETF-HIP-RFC5204-BIS * Normative Reference DRAFT-IETF-HIP-NATIVE-NAT-TRAVERSAL RFC5204: Host Identity Protocol (HIP) Rendezvous Extension (15 pages) * Normative Reference RFC5201 * Normative Reference RFC3484 * Normative Reference RFC5203 * Informative Reference BCP78 * Normative Reference RFC5205 * Informative Reference RFC3013 * Informative Reference RFC5206 * Informative Reference BCP46 * Informative Reference BCP38 * Normative Reference RFC1122 * Informative Reference RFC4423 * Normative Reference RFC2434 * Informative Reference RFC2827 * Normative Reference BCP26 * Normative Reference RFC2119 * Normative Reference STD3 * Normative Reference BCP14 * Informative Reference DRAFT-SARIKAYA-6LO-BOOTSTRAPPING-SOLUTION * Informative Reference RFC5201 * Informative Reference RFC6538 * Normative Reference RFC5206 * Normative Reference RFC5205 * Informative Reference RFC5203 * Informative Reference RFC5770 * Informative Reference RFC6079 * Normative Reference DRAFT-MELEN-HIP-MR * Normative Reference DRAFT-CAO-HIP-GEOLOCATION * Normative Reference DRAFT-ZHANG-HIP-HI-REVOCATION * Informative Reference DRAFT-CAMARILLO-HIP-VIA * Normative Reference DRAFT-PONOMAREV-HIP-DNS-LOCATORS * Normative Reference DRAFT-MELEN-HIP-PROXY * Informative Reference RFC6028 * Informative Reference DRAFT-MOSKOWITZ-RFC5201-BIS * Informative Reference DRAFT-MOSKOWITZ-HIP-RFC5201-BIS * Normative Reference DRAFT-MOSKOWITZ-RFC4423-BIS * Normative Reference DRAFT-MOSKOWITZ-HIP-RFC4423-BIS * Normative Reference DRAFT-HENDERSON-HIP-RFC5206-BIS * Informative Reference DRAFT-KERANEN-HIP-OVER-HIP * Informative Reference RFC6261 * Normative Reference DRAFT-IRTF-HIPRG-REVOCATION * Informative Reference RFC6537 * Normative Reference DRAFT-IETF-HIP-RFC4423-BIS * Normative Reference DRAFT-IETF-HIP-RFC5203-BIS * Informative Reference DRAFT-IETF-HIP-RFC5204-BIS * Normative Reference DRAFT-IETF-HIP-RFC5205-BIS * Informative Reference DRAFT-IETF-HIP-RFC5201-BIS * Normative Reference DRAFT-IETF-HIP-RFC5206-BIS * Informative Reference DRAFT-IETF-HIP-MULTIHOMING * Informative Reference DRAFT-SARIKAYA-CORE-SBOOTSTRAPPING * Normative Reference DRAFT-CAO-HIPRG-FLOW-MOBILITY * Informative Reference DRAFT-SARIKAYA-ACE-SECURE-BOOTSTRAPPING * Informative Reference DRAFT-SARIKAYA-SOLACE-SETUP-FRAMEWORK * Informative Reference DRAFT-SARIKAYA-CORE-SECURE-BOOTSOLUTION RFC5205: Host Identity Protocol (HIP) Domain Name System (DNS) Extensions (17 pages) * Normative Reference RFC5201 * Informative Reference RFC3110 * Normative Reference RFC5204 * Informative Reference RFC5206 * Informative Reference BCP78 * Normative Reference RFC4648 * Informative Reference RFC3833 * Normative Reference RFC2181 * Normative Reference RFC4035 * Normative Reference RFC4034 * Normative Reference RFC1034 * Normative Reference RFC1035 * Informative Reference RFC4423 * Normative Reference RFC4033 * Normative Reference RFC4025 * Normative Reference RFC3596 * Informative Reference RFC2536 * Normative Reference RFC2119 * Normative Reference STD13 * Normative Reference BCP14 * Informative Reference RFC5201 * Informative Reference RFC6538 * Normative Reference RFC5204 * Reference DRAFT-AHRENHOLZ-HIPRG-DHT * Normative Reference RFC6317 * Informative Reference RFC6079 * Informative Reference DRAFT-JENNINGS-APP-DNS-UPDATE * Normative Reference DRAFT-VARJONEN-HIP-SRP * Reference DRAFT-ZHANG-HIP-HIERARCHICAL-PARAMETER * Normative Reference DRAFT-ZHANG-HIP-HI-REVOCATION * Normative Reference DRAFT-PONOMAREV-HIP-DNS-LOCATORS * Normative Reference DRAFT-MELEN-HIP-PROXY * Reference DRAFT-ZHANG-HIP-INVESTIGATION-PROXY * Informative Reference DRAFT-MOSKOWITZ-RFC5201-BIS * Informative Reference DRAFT-MOSKOWITZ-HIP-RFC5201-BIS * Normative Reference DRAFT-MOSKOWITZ-RFC4423-BIS * Normative Reference DRAFT-MOSKOWITZ-HIP-RFC4423-BIS * Normative Reference DRAFT-IRTF-HIPRG-PROXIES * Normative Reference DRAFT-IRTF-HIPRG-REVOCATION * Normative Reference RFC6537 * Normative Reference DRAFT-XU-HIP-HIERARCHICAL * Normative Reference DRAFT-IETF-HIP-RFC4423-BIS * Normative Reference DRAFT-IETF-HIP-RFC5204-BIS * Informative Reference DRAFT-IETF-HIP-RFC5205-BIS * Informative Reference DRAFT-IETF-HIP-RFC5201-BIS * Normative Reference DRAFT-CAO-HIPRG-FLOW-MOBILITY * Normative Reference DRAFT-CAO-HIPRG-LEGACY-HOST RFC5206: End-Host Mobility and Multihoming with the Host Identity Protocol (40 pages) * Normative Reference RFC5201 * Normative Reference RFC3484 * Normative Reference RFC5202 * Normative Reference RFC4291 * Normative Reference RFC5204 * Normative Reference RFC4303 * Informative Reference BCP78 * Normative Reference RFC4423 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference RFC4225 * Informative Reference RFC5201 * Informative Reference RFC6538 * Informative Reference RFC5205 * Informative Reference RFC5204 * Informative Reference RFC5202 * Informative Reference RFC5534 * Reference DRAFT-AHRENHOLZ-HIPRG-DHT * Informative Reference RFC5207 * Normative Reference RFC5770 * Normative Reference DRAFT-HEER-HIP-MIDDLE-AUTH * Informative Reference RFC6079 * Normative Reference DRAFT-MELEN-HIP-MR * Informative Reference DRAFT-NIKANDER-HIP-HICCUPS * Normative Reference DRAFT-MELEN-HIP-NAT-MM * Informative Reference RFC6418 * Informative Reference RFC6071 * Normative Reference DRAFT-MELEN-HIP-PROXY * Informative Reference DRAFT-MGLT-IPSEC-MM-REQUIREMENTS * Informative Reference RFC6078 * Informative Reference DRAFT-SAROLAHTI-MPTCP-AF-MULTIPATH * Informative Reference DRAFT-MOSKOWITZ-RFC5201-BIS * Informative Reference DRAFT-MOSKOWITZ-HIP-RFC5201-BIS * Normative Reference DRAFT-HENDERSON-HIP-VPLS * Informative Reference DRAFT-JOKELA-HIP-RFC5202-BIS * Informative Reference RFC6261 * Informative Reference RFC6537 * Normative Reference DRAFT-YUAN-HIPRG-FAILURE-DETECTION-RECOVERY * Normative Reference DRAFT-IETF-HIP-RFC4423-BIS * Informative Reference DRAFT-IETF-HIP-RFC5204-BIS * Informative Reference DRAFT-IETF-HIP-RFC5205-BIS * Informative Reference DRAFT-IETF-HIP-RFC5201-BIS * Possible Reference DRAFT-IETF-HIP-RFC5206-BIS * Informative Reference DRAFT-IETF-HIP-RFC5202-BIS * Informative Reference DRAFT-IETF-HIP-MULTIHOMING * Informative Reference RFC7157 * Normative Reference DRAFT-CAO-HIPRG-FLOW-MOBILITY * Informative Reference DRAFT-GARCIA-CORE-SECURITY RFC5338: Using the Host Identity Protocol with Legacy Applications (14 pages) * Replaces DRAFT-HENDERSON-HIP-APPLICATIONS * Informative Reference RFC5201 * Informative Reference RFC3493 * Informative Reference BCP78 * Informative Reference RFC4033 * Informative Reference RFC4843 * Informative Reference RFC1958 * Informative Reference DRAFT-IETF-HIP-RFC4423-BIS * Informative Reference RFC6538 * Normative Reference RFC6317 * Informative Reference RFC6079 * Normative Reference DRAFT-PONOMAREV-HIP-HIT2IP * Reference DRAFT-ZHANG-HIP-INVESTIGATION-PROXY * Informative Reference DRAFT-MOSKOWITZ-RFC5201-BIS * Informative Reference DRAFT-MOSKOWITZ-HIP-RFC5201-BIS * Normative Reference DRAFT-IRTF-HIPRG-PROXIES * Informative Reference DRAFT-IETF-HIP-RFC5201-BIS * Normative Reference DRAFT-CAO-HIPRG-LEGACY-HOST RFC5770: Basic Host Identity Protocol (HIP) Extensions for Traversal of Network Address Translators (34 pages) * Replaces DRAFT-SCHMITT-HIP-NAT-TRAVERSAL * Normative Reference RFC5201 * Normative Reference RFC5226 * Normative Reference RFC5203 * Normative Reference RFC5202 * Informative Reference RFC5204 * Informative Reference RFC5207 * Normative Reference RFC5206 * Informative Reference RFC4787 * Normative Reference BCP14 * Informative Reference RFC3948 * Possible Reference RFC5741 * Informative Reference RFC5128 * Normative Reference RFC5766 * Normative Reference RFC4291 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC5389 * Normative Reference RFC5245 * Informative Reference BCP127 * Normative Reference RFC4423 * Informative Reference RFC6538 * Informative Reference RFC6316 * Normative Reference DRAFT-HEER-HIP-MIDDLE-AUTH * Normative Reference RFC6079 * Informative Reference DRAFT-MOSKOWITZ-HIP-RFC4423-BIS * Normative Reference RFC7086 * Informative Reference DRAFT-ZHANG-HIP-PRIVACY-PROTECTION * Informative Reference RFC6261 * Normative Reference DRAFT-IETF-HIP-NATIVE-NAT-TRAVERSAL * Informative Reference DRAFT-IETF-HIP-RFC5202-BIS RFC6028: Host Identity Protocol (HIP) Multi-Hop Routing Extension (10 pages) * Normative Reference RFC5201 * Informative Reference RFC5226 * Informative Reference RFC5204 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference BCP26 * Normative Reference RFC7086 RFC6078: Host Identity Protocol (HIP) Immediate Carriage and Conveyance of Upper-Layer Protocol Signaling (HICCUPS) (17 pages) * Normative Reference RFC5201 * Informative Reference RFC5206 * Possible Reference RFC5741 * Informative Reference RFC5202 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference RFC7086 * Normative Reference RFC6079 * Informative Reference RFC6261 * Informative Reference DRAFT-IETF-HIP-RFC4423-BIS * Informative Reference DRAFT-ARKKO-CORE-SECURITY-ARCH * Informative Reference DRAFT-AKS-CRYPTO-SENSORS RFC6079: HIP BONE: Host Identity Protocol (HIP) Based Overlay Networking Environment (BONE) (21 pages) * Replaces DRAFT-CAMARILLO-HIP-BONE * Normative Reference RFC5201 * Informative Reference RFC5226 * Informative Reference RFC5205 * Informative Reference RFC5204 * Informative Reference RFC5206 * Informative Reference RFC4251 * Informative Reference RFC5389 * Normative Reference RFC4843 * Informative Reference RFC5245 * Possible Reference RFC5741 * Normative Reference RFC5202 * Normative Reference BCP14 * Normative Reference RFC5770 * Normative Reference RFC6078 * Informative Reference BCP26 * Normative Reference RFC2119 * Informative Reference RFC5338 * Informative Reference RFC6940 * Normative Reference RFC7086 RFC6253: Host Identity Protocol Certificates (12 pages) * Replaces DRAFT-VARJONEN-HIP-CERT * Updates RFC5201 * Normative Reference RFC5201 * Normative Reference RFC2693 * Normative Reference RFC4516 * Normative Reference RFC4514 * Normative Reference RFC4843 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC5280 * Normative Reference RFC5996 * Normative Reference RFC2119 * Informative Reference RFC6538 * Normative Reference DRAFT-HEER-HIP-MIDDLE-AUTH * Normative Reference RFC7086 * Normative Reference DRAFT-HENDERSON-HIP-VPLS * Informative Reference RFC6261 * Normative Reference RFC6537 * Normative Reference DRAFT-IETF-HIP-RFC4423-BIS * Normative Reference DRAFT-IETF-HIP-RFC5203-BIS * Informative Reference DRAFT-IETF-HIP-RFC5201-BIS * Informative Reference DRAFT-KHAN-OBJECT-NAMING * Normative Reference DRAFT-OHBA-MLE-HIP-DEX RFC6261: Encrypted Signaling Transport Modes for the Host Identity Protocol (13 pages) * Informative Reference RFC5201 * Normative Reference RFC5226 * Informative Reference RFC5204 * Informative Reference RFC5206 * Informative Reference RFC6253 * Normative Reference RFC2119 * Informative Reference RFC4303 * Possible Reference RFC5741 * Informative Reference RFC5202 * Normative Reference BCP14 * Informative Reference RFC5770 * Normative Reference BCP26 * Informative Reference RFC6078 * Normative Reference RFC7086 RFC6317: Basic Socket Interface Extensions for the Host Identity Protocol (HIP) (18 pages) * Normative Reference RFC5201 * Normative Reference RFC3493 * Normative Reference RFC5205 * Normative Reference RFC4843 * Normative Reference RFC6316 * Possible Reference RFC5741 * Informative Reference RFC5533 * Normative Reference RFC4423 * Normative Reference RFC5014 * Normative Reference RFC5338 * Informative Reference RFC6538 * Informative Reference RFC6316 * Informative Reference RFC6897 * Informative Reference DRAFT-IETF-HIP-RFC4423-BIS * Possible Reference DRAFT-PERKINS-DMM-MATRIX * Informative Reference DRAFT-TISSA-NETMOD-OAM * Informative Reference DRAFT-TISSA-LIME-YANG-OAM-MODEL * Informative Reference DRAFT-DEEPAK-TRILL-YANG-PM * Informative Reference DRAFT-IETF-TRILL-YANG-PM RFC7086: Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD) (10 pages) * Normative Reference RFC6078 * Normative Reference RFC6079 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC4843 * Normative Reference RFC5770 * Normative Reference RFC6261 * Normative Reference BCP14 * Possible Reference RFC5741 * Normative Reference RFC6028 * Normative Reference RFC6940 * Normative Reference RFC6253 * Normative Reference RFC5226 * Informative Reference RFC5246 * Normative Reference RFC5201 * Informative Reference RFC6940 RFC7343: An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers Version 2 (ORCHIDv2) (14 pages) * Normative Reference RFC2119 * Informative Reference RFC4270 * Informative Reference RFC3174 * Informative Reference RFC1918 * Normative Reference BCP14 * Normative Reference RFC3972 * Possible Reference RFC5741 * Informative Reference RFC4843 * Informative Reference BCP5 * Informative Reference BCP153 * Informative Reference RFC6890 * Informative Reference RFC4291 * Informative Reference RFC6920 * Obsoletes RFC4843 Internet Area Working Group (intarea) ------------------------------------- Charter Last Modified: 2013-12-23 Current Status: Active Chairs: Suresh Krishnan Juan-Carlos Zúñiga Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Mailing Lists: General Discussion: int-area@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/int-area Archive: http://www.ietf.org/mail-archive/web/int-area/ Description of Working Group: The Internet Area Working Group (INTAREA WG) acts primarily as a forum for discussing far-ranging topics that affect the entire area. Such topics include, for instance, address space issues, basic IP layer functionality, and architectural questions. The group also serves as a forum to distribute information about ongoing activities in the area, create a shared understanding of the challenges and goals for the area, and to enable coordination. The Internet Area receives occasional proposals for the development and publication of RFCs that are not in scope of an existing working group and do not justify the formation of a new working group. The INTAREA WG has a secondary role to serve as the forum for developing such work items in the IETF. The working group milestones are updated as needed to reflect the current work items and their associated milestones. New work must satisfy the following conditions: (1) WG consensus on the relevance for the Internet at large. (2) WG consensus on the suitability and projected quality of the proposed work item. (3) A core group of WG participants with sufficient energy and expertise to advance the work item according to the proposed schedule. (4) Commitment from the WG as a whole to provide sufficient and timely review of the proposed work item. (5) Agreement by the ADs, who, depending on the scope of the proposed work item, may decide that an IESG review is needed first. Goals and Milestones: May 2010 - Submission of IPID document to the IESG as PS Aug 2010 - Submission of tunneling issues document to the IESG as Info Aug 2010 - Submission of tunneling security issues document to the IESG as Info Internet-Drafts: - Using the IPv6 Flow Label for Load Balancing in Server Farms [draft-ietf-intarea-flow-label-balancing-03] (13 pages) - IPv6 Support for Generic Routing Encapsulation (GRE) [draft-ietf-intarea-gre-ipv6-02] (7 pages) - A Widely-Deployed Solution To The Generic Routing Encapsulation (GRE) Fragmentation Problem [draft-ietf-intarea-gre-mtu-01] (10 pages) - Updated Specification of the IPv4 ID Field [draft-ietf-intarea-ipv4-id-update-07] (19 pages) - IPv6 Support Required for All IP-Capable Nodes [draft-ietf-intarea-ipv6-required-02] (6 pages) - Analysis of Potential Solutions for Revealing a Host Identifier (HOST_ID) in Shared Address Deployments [draft-ietf-intarea-nat-reveal-analysis-10] (24 pages) - IP Router Alert Considerations and Usage [draft-ietf-intarea-router-alert-considerations-10] (19 pages) - Logging Recommendations for Internet-Facing Servers [draft-ietf-intarea-server-logging-recommendations-04] (5 pages) - Issues with IP Address Sharing [draft-ietf-intarea-shared-addressing-issues-05] (29 pages) - Tunnels in the Internet Architecture [draft-ietf-intarea-tunnels-00] (22 pages) Requests for Comments: BCP162: Logging Recommendations for Internet-Facing Servers (5 pages) * Informative Reference RFC5905 * Normative Reference RFC2119 * Possible Reference RFC5741 * Normative Reference BCP14 * Informative Reference RFC6146 * Informative Reference RFC3022 * Informative Reference RFC6269 * Normative Reference DRAFT-IETF-BEHAVE-IPFIX-NAT-LOGGING * Informative Reference DRAFT-NISHIZUKA-CGN-DEPLOYMENT-CONSIDERATIONS * Normative Reference RFC6888 * Informative Reference RFC6333 * Informative Reference RFC6908 * Informative Reference RFC7422 * Informative Reference RFC6973 * Informative Reference DRAFT-PENNO-SOFTWIRE-SDNAT * Informative Reference RFC6967 * Informative Reference DRAFT-CHKPVC-ENTERPRISE-INCREMENTAL-IPV6 * Informative Reference RFC6692 * Informative Reference RFC7381 * Informative Reference DRAFT-IETF-OPSEC-V6 BCP168: IP Router Alert Considerations and Usage (19 pages) * Replaces DRAFT-RAHMAN-RTG-ROUTER-ALERT-CONSIDERATIONS * Updates RFC2113 * Updates RFC2711 * Informative Reference RFC3376 * Informative Reference RFC4286 * Informative Reference RFC2205 * Normative Reference RFC2460 * Informative Reference RFC2710 * Normative Reference RFC2711 * Normative Reference BCP14 * Informative Reference RFC4081 * Informative Reference RFC2961 * Possible Reference RFC5741 * Informative Reference RFC6178 * Informative Reference RFC3209 * Informative Reference RFC3208 * Normative Reference RFC5350 * Informative Reference RFC6016 * Normative Reference RFC2113 * Informative Reference RFC4732 * Normative Reference RFC2119 * Informative Reference RFC3810 * Normative Reference RFC791 * Informative Reference RFC5971 * Informative Reference RFC3175 * Normative Reference RFC6401 * Informative Reference DRAFT-GONT-OPSEC-IP-OPTIONS-FILTERING * Normative Reference RFC7126 * Normative Reference DRAFT-MARTINSEN-MMUSIC-MALICE * Normative Reference DRAFT-RAZA-MPLS-OAM-IPV6-RAO * Normative Reference DRAFT-GONT-OPSEC-IPV6-EH-FILTERING * Normative Reference DRAFT-GONT-6MAN-IPV6-OPT-TRANSMIT * Normative Reference DRAFT-IETF-MPLS-OAM-IPV6-RAO BCP177: IPv6 Support Required for All IP-Capable Nodes (6 pages) * Informative Reference RFC1812 * Informative Reference RFC2460 * Informative Reference RFC1122 * Possible Reference RFC5741 * Informative Reference RFC6204 * Informative Reference RFC6434 * Informative Reference RFC1883 * Informative Reference STD3 * Informative Reference RFC6269 * Informative Reference DRAFT-GEORGE-MPLS-IPV6-ONLY-GAP * Informative Reference DRAFT-MPLS-IPV6-ONLY-GAP * Informative Reference RFC6782 * Informative Reference RFC7123 * Informative Reference RFC7452 * Informative Reference RFC7439 * Informative Reference DRAFT-ANDERSON-V6OPS-SIIT-DC * Informative Reference DRAFT-IETF-V6OPS-SIIT-DC RFC6269: Issues with IP Address Sharing (29 pages) * Replaces DRAFT-FORD-SHARED-ADDRESSING-ISSUES * Informative Reference RFC1337 * Informative Reference RFC2993 * Informative Reference RFC4787 * Informative Reference BCP5 * Informative Reference BCP148 * Informative Reference RFC3947 * Informative Reference BCP38 * Informative Reference RFC2140 * Informative Reference RFC1700 * Informative Reference RFC1918 * Possible Reference RFC5741 * Informative Reference RFC5961 * Informative Reference BCP135 * Informative Reference RFC6056 * Informative Reference RFC2827 * Informative Reference BCP156 * Informative Reference RFC3715 * Informative Reference RFC2663 * Informative Reference RFC1191 * Informative Reference RFC5508 * Informative Reference RFC5996 * Informative Reference RFC4380 * Informative Reference RFC2782 * Informative Reference RFC3056 * Informative Reference RFC3232 * Informative Reference RFC6146 * Informative Reference RFC6145 * Informative Reference BCP127 * Informative Reference RFC5135 * Informative Reference DRAFT-IETF-SOFTWIRE-LW4OVER6 * Normative Reference DRAFT-NISHIZUKA-CGN-DEPLOYMENT-CONSIDERATIONS * Informative Reference DRAFT-IETF-RADEXT-IP-PORT-RADIUS-EXT * Normative Reference RFC6888 * Informative Reference RFC6333 * Informative Reference RFC6346 * Informative Reference RFC6431 * Normative Reference DRAFT-TSOU-BEHAVE-NATX4-LOG-REDUCTION * Informative Reference RFC6555 * Normative Reference DRAFT-CUI-SOFTWIRE-B4-TRANSLATED-DS-LITE * Informative Reference RFC6950 * Informative Reference RFC7021 * Informative Reference RFC6598 * Informative Reference RFC6302 * Informative Reference DRAFT-BOUCADAIR-PCP-NAT-REVEAL * Informative Reference RFC6343 * Informative Reference DRAFT-BOUCADAIR-INTAREA-NAT-REVEAL-ANALYSIS * Informative Reference DRAFT-PETERSSON-FORWARDED-FOR * Informative Reference DRAFT-IETF-SOFTWIRE-STATELESS-4V6-MOTIVATION * Informative Reference DRAFT-CHENG-BEHAVE-CGN-CFG-RADIUS-EXT * Informative Reference RFC6540 * Informative Reference DRAFT-BDGKS-ARIN-SHARED-TRANSITION-SPACE * Informative Reference DRAFT-KUARSINGH-WIRELINE-INCREMENTAL-IPV6 * Informative Reference RFC6782 * Informative Reference RFC6908 * Possible Reference DRAFT-DENG-SOFTWIRE-APLUSP-EXPERIMENT-RESULTS * Normative Reference RFC7422 * Informative Reference DRAFT-ABDO-HOSTID-TCPOPT-IMPLEMENTATION * Informative Reference RFC6973 * Informative Reference DRAFT-MDT-SOFTWIRE-MAPPING-ADDRESS-AND-PORT * Informative Reference DRAFT-PENNO-SOFTWIRE-SDNAT * Informative Reference DRAFT-WILLIAMS-OVERLAYPATH-IP-TCP-RFC * Informative Reference RFC7239 * Informative Reference RFC6967 * Informative Reference DRAFT-CHEN-V6OPS-NAT64-EXPERIENCE * Normative Reference DRAFT-XUE-INTAREA-FMC-PS * Possible Reference DRAFT-MDT-SOFTWIRE-MAP-DEPLOYMENT * Informative Reference DRAFT-BOUCADAIR-PCP-BITTORRENT * Informative Reference DRAFT-IETF-SOFTWIRE-MAP * Informative Reference DRAFT-TSOU-STATELESS-NAT44 * Informative Reference RFC7269 * Informative Reference DRAFT-IETF-OPSEC-V6 * Normative Reference DRAFT-SUN-DHC-PORT-SET-OPTION * Informative Reference DRAFT-BOUCADAIR-INTAREA-HOST-IDENTIFIER-SCENARIOS * Informative Reference DRAFT-IETF-SOFTWIRE-MAP-T * Possible Reference DRAFT-IETF-SOFTWIRE-MAP-DEPLOYMENT * Informative Reference RFC7225 * Informative Reference DRAFT-CHEN-SUNSET4-CGN-PORT-ALLOCATION * Informative Reference DRAFT-CHEN-BEHAVE-NAT64-RADIUS-EXTENSION * Informative Reference DRAFT-WILLIAMS-EXP-TCP-HOST-ID-OPT * Informative Reference DRAFT-IETF-DHC-DYNAMIC-SHARED-V4ALLOCATION * Informative Reference DRAFT-DENG-MPTCP-PROXY * Informative Reference DRAFT-BOUCADAIR-TRANSPORT-PROTOCOLS * Informative Reference DRAFT-IETF-DPRIVE-PROBLEM-STATEMENT * Informative Reference DRAFT-FARRER-SOFTWIRE-BR-MULTIENDPOINTS RFC6302: Logging Recommendations for Internet-Facing Servers (5 pages) * Informative Reference RFC5905 * Normative Reference RFC2119 * Possible Reference RFC5741 * Normative Reference BCP14 * Informative Reference RFC6146 * Informative Reference RFC3022 * Informative Reference RFC6269 * Normative Reference DRAFT-IETF-BEHAVE-IPFIX-NAT-LOGGING * Informative Reference DRAFT-NISHIZUKA-CGN-DEPLOYMENT-CONSIDERATIONS * Normative Reference RFC6888 * Informative Reference RFC6333 * Informative Reference RFC6908 * Informative Reference RFC7422 * Informative Reference RFC6973 * Informative Reference DRAFT-PENNO-SOFTWIRE-SDNAT * Informative Reference RFC6967 * Informative Reference DRAFT-CHKPVC-ENTERPRISE-INCREMENTAL-IPV6 * Possible Reference DRAFT-ZHOU-SUNSET4-SCENARIOS * Informative Reference RFC7381 * Informative Reference DRAFT-IETF-OPSEC-V6 RFC6398: IP Router Alert Considerations and Usage (19 pages) * Replaces DRAFT-RAHMAN-RTG-ROUTER-ALERT-CONSIDERATIONS * Updates RFC2113 * Updates RFC2711 * Informative Reference RFC3376 * Informative Reference RFC4286 * Informative Reference RFC2205 * Normative Reference RFC2460 * Informative Reference RFC2710 * Normative Reference RFC2711 * Normative Reference BCP14 * Informative Reference RFC4081 * Informative Reference RFC2961 * Possible Reference RFC5741 * Informative Reference RFC6178 * Informative Reference RFC3209 * Informative Reference RFC3208 * Normative Reference RFC5350 * Informative Reference RFC6016 * Normative Reference RFC2113 * Informative Reference RFC4732 * Normative Reference RFC2119 * Informative Reference RFC3810 * Normative Reference RFC791 * Informative Reference RFC5971 * Informative Reference RFC3175 * Normative Reference DRAFT-GONT-OPSEC-IPV6-EH-FILTERING * Normative Reference RFC6401 * Informative Reference DRAFT-GONT-OPSEC-IP-OPTIONS-FILTERING * Normative Reference RFC7126 * Normative Reference DRAFT-MARTINSEN-MMUSIC-MALICE * Normative Reference DRAFT-RAZA-MPLS-OAM-IPV6-RAO * Normative Reference DRAFT-GONT-6MAN-IPV6-OPT-TRANSMIT * Normative Reference DRAFT-IETF-MPLS-OAM-IPV6-RAO RFC6540: IPv6 Support Required for All IP-Capable Nodes (6 pages) * Informative Reference RFC1812 * Informative Reference RFC2460 * Informative Reference RFC1122 * Possible Reference RFC5741 * Informative Reference RFC6204 * Informative Reference RFC6434 * Informative Reference RFC1883 * Informative Reference STD3 * Informative Reference RFC6269 * Informative Reference DRAFT-GEORGE-MPLS-IPV6-ONLY-GAP * Informative Reference DRAFT-MPLS-IPV6-ONLY-GAP * Informative Reference RFC6782 * Informative Reference RFC7123 * Informative Reference RFC7452 * Informative Reference RFC7439 * Informative Reference DRAFT-ANDERSON-V6OPS-SIIT-DC * Informative Reference DRAFT-IETF-V6OPS-SIIT-DC RFC6864: Updated Specification of the IPv4 ID Field (19 pages) * Replaces DRAFT-TOUCH-INTAREA-IPV4-UNIQUE-ID * Updates RFC1122 * Updates RFC2003 * Updates RFC791 * Informative Reference RFC2671 * Informative Reference RFC5225 * Informative Reference RFC2460 * Normative Reference RFC1122 * Normative Reference BCP14 * Informative Reference RFC6219 * Normative Reference RFC2003 * Informative Reference RFC3828 * Informative Reference RFC4301 * Normative Reference RFC1812 * Informative Reference RFC6145 * Possible Reference RFC5741 * Informative Reference RFC3022 * Informative Reference RFC3545 * Informative Reference RFC4963 * Informative Reference RFC4960 * Normative Reference RFC2119 * Normative Reference STD3 * Normative Reference RFC791 * Informative Reference RFC4302 * Informative Reference RFC5320 * Informative Reference RFC4443 * Informative Reference RFC2508 * Informative Reference RFC1144 * Informative Reference RFC6621 * Informative Reference DRAFT-IETF-SOFTWIRE-LW4OVER6 * Normative Reference DRAFT-IETF-TSVWG-BEHAVE-REQUIREMENTS-UPDATE * Informative Reference DRAFT-TEMPLIN-INTAREA-SEAL * Normative Reference DRAFT-BRISCOE-INTAREA-IPV4-ID-REUSE * Informative Reference RFC6967 * Informative Reference DRAFT-GENERIC-V6OPS-TUNMTU * Informative Reference DRAFT-BOUCADAIR-CHAINING-DESIGN-ANALYSIS * Informative Reference DRAFT-BOUCADAIR-SFC-DESIGN-ANALYSIS * Informative Reference DRAFT-TEMPLIN-AEROLINK * Informative Reference DRAFT-IETF-SOFTWIRE-MAP RFC6967: Analysis of Potential Solutions for Revealing a Host Identifier (HOST_ID) in Shared Address Deployments (24 pages) * Informative Reference RFC5201 * Informative Reference RFC6462 * Informative Reference RFC2753 * Informative Reference RFC6864 * Informative Reference RFC6302 * Informative Reference RFC6889 * Informative Reference BCP162 * Possible Reference RFC5741 * Normative Reference BCP156 * Informative Reference RFC1413 * Normative Reference RFC791 * Normative Reference RFC6056 * Informative Reference RFC6346 * Informative Reference RFC6146 * Normative Reference RFC3022 * Informative Reference RFC6269 * Informative Reference DRAFT-IETF-RADEXT-IP-PORT-RADIUS-EXT * Informative Reference DRAFT-CHENG-BEHAVE-CGN-CFG-RADIUS-EXT * Informative Reference DRAFT-WILLIAMS-OVERLAYPATH-IP-TCP-RFC * Informative Reference RFC7269 * Informative Reference DRAFT-BOUCADAIR-INTAREA-HOST-IDENTIFIER-SCENARIOS * Normative Reference DRAFT-SCHOTT-FMC-PREFIX-SHARING-PROTOCOL * Informative Reference DRAFT-BOUCADAIR-SFC-DESIGN-ANALYSIS * Informative Reference DRAFT-QUINN-SFC-PROBLEM-STATEMENT * Informative Reference DRAFT-WILLIAMS-EXP-TCP-HOST-ID-OPT * Informative Reference DRAFT-XUE-SFC-ADDRESS-SHARING-IN-SFC-USE-CASES * Informative Reference DRAFT-SARIKAYA-SFC-ADDRESS-SHARING-IN-SFC * Informative Reference DRAFT-BOUCADAIR-TRANSPORT-PROTOCOLS * Informative Reference DRAFT-XIE-HIAPS-HOSTID-IN-SFC RFC7098: Using the IPv6 Flow Label for Load Balancing in Server Farms (13 pages) * Replaces DRAFT-CARPENTER-FLOW-LABEL-BALANCING * Informative Reference RFC6294 * Informative Reference RFC6296 * Normative Reference RFC6434 * Informative Reference RFC6436 * Normative Reference RFC6437 * Informative Reference RFC6438 * Informative Reference RFC4864 * Possible Reference RFC5741 * Normative Reference RFC2460 * Informative Reference RFC2991 * Informative Reference DRAFT-WANG-V6OPS-FLOW-LABEL-REFELCTION * Informative Reference DRAFT-WANG-6MAN-FLOW-LABEL-REFLECTION IPv6 Maintenance (6man) ----------------------- Charter Last Modified: 2011-12-09 Current Status: Active Chairs: Robert M. Hinden Ole Troan Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Brian Haberman Mailing Lists: General Discussion: ipv6@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/ipv6 Archive: http://www.ietf.org/mail-archive/web/ipv6 Description of Working Group: The 6man working group is responsible for the maintenance, upkeep, and advancement of the IPv6 protocol specifications and addressing architecture. It is not chartered to develop major changes or additions to the IPv6 specifications. The working group will address protocol limitations/issues discovered during deployment and operation. It will also serve as a venue for discussing the proper location for working on IPv6-related issues within the IETF. 6man is the design authority for extensions and modifications to the IPv6 protocol. The working group may, at its discretion, review any document produced in another working group that extends or modifies the IPv6 protocol and, in consultation with the responsible ADs of both working groups, may recommend to the IESG that 6man working group consensus is needed before any of those documents can progress for publication. Goals and Milestones: Done - Submit RH0 Deprecation specification to IESG as a Proposed Standard Done - Submit PPP Compression Negotiation specification to IESG as a Proposed Standard Done - Determine way forward for ULA-C specification Done - Resolve open issues with "U/G" bits in Interface Identifiers Mar 2014 - Develop approach for IPv6 Fragmentation Mar 2014 - Develop approaches for IPv6 Extension Headers (Hop-by-Hop and Destination) Jul 2014 - Plan for advancing core IPv6 core specifications to Internet Standard Internet-Drafts: - Analysis of the 64-bit Boundary in IPv6 Addressing [draft-carpenter-6man-why64-01] (20 pages) - RFC 3627 to Historic Status [draft-ietf-6man-3627-historic-01] (3 pages) - Transmission of IPv6 over MS/TP Networks [draft-ietf-6man-6lobac-01] (20 pages) - Considerations for IPv6 Address Selection Policy Changes [draft-ietf-6man-addr-select-considerations-05] (18 pages) - Distributing Address Selection Policy Using DHCPv6 [draft-ietf-6man-addr-select-opt-13] (12 pages) - Solution approaches for address-selection problems [draft-ietf-6man-addr-select-sol-03] (17 pages) - Duplicate Address Detection Proxy [draft-ietf-6man-dad-proxy-07] (16 pages) - Recommendation on Stable IPv6 Interface Identifiers [draft-ietf-6man-default-iids-02] (8 pages) - Deprecating the Generation of IPv6 Atomic Fragments [draft-ietf-6man-deprecate-atomfrag-generation-00] (17 pages) - IPv6 Router Advertisement Options for DNS Configuration [draft-ietf-6man-dns-options-bis-08] (19 pages) - Enhanced Duplicate Address Detection [draft-ietf-6man-enhanced-dad-15] (10 pages) - Transmission and Processing of IPv6 Extension Headers [draft-ietf-6man-ext-transmit-05] (10 pages) - A Uniform Format for IPv6 Extension Headers [draft-ietf-6man-exthdr-06] (6 pages) - IPv6 Flow Label Specification [draft-ietf-6man-flow-3697bis-07] (15 pages) - Using the IPv6 Flow Label for Equal Cost Multipath Routing and Link Aggregation in Tunnels [draft-ietf-6man-flow-ecmp-05] (9 pages) - Rationale for Update to the IPv6 Flow Label Specification [draft-ietf-6man-flow-update-07] (13 pages) - IANA Allocation Guidelines for the IPv6 Routing Header [draft-ietf-6man-iana-routing-header-00] (3 pages) - Neighbor Unreachability Detection Is Too Impatient [draft-ietf-6man-impatient-nud-07] (8 pages) - Privacy Considerations for IPv6 Address Generation Mechanisms [draft-ietf-6man-ipv6-address-generation-privacy-04] (16 pages) - Processing of IPv6 "Atomic" Fragments [draft-ietf-6man-ipv6-atomic-fragments-04] (9 pages) - IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes [draft-ietf-6man-ipv6-subnet-model-12] (11 pages) - The Line-Identification Option [draft-ietf-6man-lineid-08] (17 pages) - Updates to the IPv6 Multicast Addressing Architecture [draft-ietf-6man-multicast-addr-arch-update-08] (10 pages) - IPv6 Multicast Address Scopes [draft-ietf-6man-multicast-scopes-07] (6 pages) - Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery [draft-ietf-6man-nd-extension-headers-05] (10 pages) - Validation of IPv6 Neighbor Discovery Options [draft-ietf-6man-nd-opt-validation-00] (15 pages) - Interface Identifier Assignment in IPv6 SLAAC [draft-ietf-6man-neighbor-inform-00] (17 pages) - IPv6 Node Requirements [draft-ietf-6man-node-req-bis-11] (30 pages) - Handling of Overlapping IPv6 Fragments [draft-ietf-6man-overlap-fragment-03] (6 pages) - Implications of Oversized IPv6 Header Chains [draft-ietf-6man-oversized-header-chain-09] (8 pages) - Security Implications of Predictable Fragment Identification Values [draft-ietf-6man-predictable-fragment-id-04] (16 pages) - Using 127-Bit IPv6 Prefixes on Inter-Router Links [draft-ietf-6man-prefixlen-p2p-01] (8 pages) - Reserved IPv6 Interface Identifiers [draft-ietf-6man-reserved-iids-03] (6 pages) - Packet loss resiliency for Router Solicitations [draft-ietf-6man-resilient-rs-05] (6 pages) - Update to RFC 3484 Default Address Selection for IPv6 [draft-ietf-6man-rfc3484-revise-05] (12 pages) - Default Address Selection for Internet Protocol Version 6 (IPv6) [draft-ietf-6man-rfc3484bis-06] (32 pages) - The Routing Protocol for Low-Power and Lossy Networks (RPL) Option for Carrying RPL Information in Data-Plane Datagrams [draft-ietf-6man-rpl-option-06] (9 pages) - An IPv6 Routing Header for Source Routes with the Routing Protocol for Low-Power and Lossy Networks (RPL) [draft-ietf-6man-rpl-routing-header-07] (13 pages) - A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC) [draft-ietf-6man-stable-privacy-addresses-17] (19 pages) - A Recommendation for IPv6 Address Text Representation [draft-ietf-6man-text-addr-representation-07] (14 pages) - IPv6 and UDP Checksums for Tunneled Packets [draft-ietf-6man-udpchecksums-08] (12 pages) - Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums [draft-ietf-6man-udpzero-12] (40 pages) - Significance of IPv6 Interface Identifiers [draft-ietf-6man-ug-06] (10 pages) - Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers [draft-ietf-6man-uri-zoneid-06] (10 pages) - Analysis of the 64-bit Boundary in IPv6 Addressing [draft-ietf-6man-why64-08] (24 pages) - Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol [draft-ietf-ipv6-compression-nego-v2-02] (7 pages) - Centrally Assigned Unique Local IPv6 Unicast Addresses [draft-ietf-ipv6-ula-central-02] (11 pages) - Packet loss resiliency for Router Solicitations [draft-krishnan-6man-resilient-rs-01] (6 pages) Requests for Comments: RFC5172: Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol (7 pages) * Obsoletes RFC2472 * Normative Reference STD51 * Informative Reference RFC1968 * Normative Reference RFC1661 * Informative Reference BCP78 * Normative Reference RFC3241 * Informative Reference RFC1962 * Normative Reference RFC3544 * Informative Reference RFC2472 * Informative Reference BCP88 * Informative Reference RFC1321 * Informative Reference RFC3748 * Normative Reference RFC5072 * Normative Reference BCP14 * Possible Reference RFC3818 * Possible Reference RFC2023 * Normative Reference RFC2507 * Informative Reference RFC6252 * Informative Reference DRAFT-LOURDELET-RADEXT-RFC3162BIS * Informative Reference DRAFT-QIN-PPPEXT-IPV6-ADDR-PREF * Reference DRAFT-KUNDRAT-IMAP-SUBMIT RFC5453: Reserved IPv6 Interface Identifiers (6 pages) * Normative Reference RFC5226 * Normative Reference RFC4291 * Informative Reference RFC5072 * Informative Reference RFC4489 * Normative Reference RFC2526 * Informative Reference RFC3315 * Informative Reference RFC3972 * Informative Reference RFC5156 * Normative Reference BCP14 * Informative Reference RFC4982 * Informative Reference RFC2590 * Informative Reference RFC4862 * Informative Reference RFC4941 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC7421 * Normative Reference RFC6434 * Normative Reference RFC7136 * Normative Reference DRAFT-JIANG-6MAN-ADDR-REGISTRATION-REQ * Normative Reference RFC6543 * Normative Reference RFC7217 * Normative Reference DRAFT-CARPENTER-6MAN-UG * Informative Reference DRAFT-SMITH-ENHANCE-VNE-WITH-IPV6 * Normative Reference DRAFT-GONT-DHC-STABLE-PRIVACY-ADDRESSES * Normative Reference DRAFT-IETF-DHC-STABLE-PRIVACY-ADDRESSES RFC5722: Handling of Overlapping IPv6 Fragments (6 pages) * Replaces DRAFT-KRISHNAN-6MAN-OVERLAP-FRAGMENT * Updates RFC2460 * Informative Reference RFC1858 * Normative Reference RFC2460 * Normative Reference BCP14 * Possible Reference STD1 * Normative Reference RFC2119 * Informative Reference RFC4942 * Updates RFC6946 * Informative Reference DRAFT-IETF-6MAN-PREDICTABLE-FRAGMENT-ID * Normative Reference RFC6434 * Informative Reference RFC6936 * Informative Reference DRAFT-GONT-6MAN-PREDICTABLE-FRAGMENT-ID * Normative Reference DRAFT-GONT-6MAN-IPV6-ATOMIC-FRAGMENTS * Normative Reference RFC7113 * Normative Reference RFC6946 * Informative Reference DRAFT-CHKPVC-ENTERPRISE-INCREMENTAL-IPV6 * Normative Reference DRAFT-GONT-OPSEC-DHCPV6-SHIELD * Normative Reference DRAFT-GONT-OPSEC-IPV6-ND-SHIELD * Informative Reference RFC7381 * Normative Reference RFC7269 * Normative Reference DRAFT-KORHONEN-V6OPS-RFC3316BIS * Informative Reference RFC7066 * Normative Reference DRAFT-IETF-OPSEC-DHCPV6-SHIELD * Normative Reference DRAFT-KAMPANAKIS-6MAN-IPV6-EH-PARSING * Normative Reference DRAFT-JPCERT-IPV6VULLNERABILITY-CHECK RFC5871: IANA Allocation Guidelines for the IPv6 Routing Header (3 pages) * Updates RFC2460 * Normative Reference RFC5226 * Informative Reference RFC2460 * Possible Reference RFC5741 * Informative Reference RFC4727 * Informative Reference RFC5095 * Normative Reference BCP26 RFC5942: IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes (11 pages) * Updates RFC4861 * Informative Reference RFC4291 * Informative Reference RFC950 * Informative Reference RFC4903 * Informative Reference RFC2461 * Informative Reference RFC1122 * Informative Reference STD3 * Informative Reference RFC3315 * Possible Reference RFC5741 * Informative Reference RFC4388 * Informative Reference RFC4862 * Normative Reference BCP14 * Informative Reference BCP122 * Normative Reference RFC4861 * Informative Reference STD5 * Informative Reference RFC3756 * Normative Reference RFC2119 * Informative Reference RFC4943 * Informative Reference RFC4632 * Normative Reference RFC7421 * Normative Reference RFC6434 * Normative Reference RFC6204 * Possible Reference DRAFT-JANKIEWICZ-V6OPS-V4V6BIBLIO * Normative Reference DRAFT-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-IETF-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference RFC7084 * Normative Reference DRAFT-MAQUEDA-6LOWPAN-PGW * Normative Reference DRAFT-VONHUGO-MULTIMOB-CXTP-EXTENSION * Informative Reference DRAFT-HAZEYAMA-WIDECAMP-IPV6-ONLY-EXPERIENCE * Normative Reference DRAFT-VONHUGO-MULTIMOB-DMM-CONTEXT * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQS-RFC3316UPDATE * Informative Reference DRAFT-SMITH-6MAN-MITIGATE-ND-CACHE-DOS-SLND * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQUIREMENTS * Normative Reference DRAFT-GONT-OPSEC-IPV6-ND-SECURITY * Informative Reference DRAFT-HAZEYAMA-SUNSET4-DNS-A-FILTER * Normative Reference DRAFT-IETF-OPSEC-IPV6-ND-SECURITY RFC5952: A Recommendation for IPv6 Address Text Representation (14 pages) * Replaces DRAFT-KAWAMURA-IPV6-TEXT-REPRESENTATION * Updates RFC4291 * Normative Reference RFC4291 * Informative Reference RFC5214 * Normative Reference STD66 * Normative Reference RFC2765 * Informative Reference RFC4038 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC3986 * Normative Reference RFC2119 * Informative Reference DRAFT-KLATSKY-DISPATCH-IPV6-IMPACT-IPV4 * Normative Reference DRAFT-IETF-CDNI-REDIRECTION * Normative Reference RFC7371 * Normative Reference RFC6155 * Normative Reference RFC7105 * Normative Reference RFC5954 * Normative Reference RFC6492 * Normative Reference RFC6434 * Informative Reference RFC6021 * Normative Reference RFC5953 * Normative Reference DRAFT-IETF-SIDR-RPSL-SIG * Normative Reference RFC6940 * Normative Reference DRAFT-IETF-WEIRDS-RDAP-QUERY * Normative Reference RFC7285 * Informative Reference RFC6120 * Informative Reference RFC6052 * Informative Reference RFC6714 * Normative Reference RFC7252 * Informative Reference RFC6122 * Informative Reference RFC6873 * Informative Reference DRAFT-JENNINGS-SENML * Normative Reference DRAFT-DENOG-V6OPS-ADDRESSPARTNAMING * Possible Reference DRAFT-JANKIEWICZ-V6OPS-V4V6BIBLIO * Normative Reference DRAFT-PETERSSON-FORWARDED-FOR * Normative Reference DRAFT-HARTMANN-6MAN-ADDRESSPARTNAMING * Normative Reference DRAFT-SHENG-WEIRDS-ICANN-RWS-DNRD * Informative Reference RFC6943 * Informative Reference DRAFT-SAKURA-6RD-DATACENTER * Normative Reference DRAFT-JENKINS-CDNI-METADATA * Normative Reference DRAFT-NEWTON-ET-AL-WEIRDS-RIR-QUERY * Informative Reference DRAFT-IETF-PPSP-BASE-TRACKER-PROTOCOL * Normative Reference DRAFT-ODONOGHUE-NTPV4-CONTROL * Normative Reference DRAFT-CARPENTER-6MAN-URI-ZONEID * Normative Reference RFC7390 * Normative Reference RFC7239 * Normative Reference DRAFT-HE-CDNI-ROUTING-REQUEST-REDIRECTION * Normative Reference RFC6874 * Normative Reference RFC6353 * Informative Reference RFC6217 * Informative Reference DRAFT-CHKPVC-ENTERPRISE-INCREMENTAL-IPV6 * Informative Reference DRAFT-VYNCKE-OPSEC-V6 * Normative Reference DRAFT-IETF-WEIRDS-JSON-RESPONSE * Normative Reference RFC6883 * Normative Reference DRAFT-DESIGNTEAM-WEIRDS-USING-HTTP * Normative Reference DRAFT-ZHOU-BEHAVE-SYSLOG-NAT-LOGGING * Informative Reference DRAFT-JANOG-SOFTWIRE-REPORT * Normative Reference DRAFT-CJLMW-CDNI-METADATA * Informative Reference RFC7381 * Informative Reference DRAFT-IETF-OPSEC-V6 * Normative Reference DRAFT-HOLLENBECK-WEIRDS-UNIFIED-RDAP-QUERY * Normative Reference DRAFT-NEWTON-WEIRDS-UNIFIED-JSON-RESPONSE * Normative Reference DRAFT-BOUCADAIR-DHC-ADDRESS-NAME-ENCODING * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQS-RFC3316UPDATE * Normative Reference DRAFT-NEWTON-JSON-CONTENT-RULES * Informative Reference DRAFT-SCHOENW-NETMOD-RFC6021-BIS * Normative Reference DRAFT-IETF-CDNI-METADATA * Informative Reference DRAFT-LEUNG-CDNI-URI-SIGNING * Normative Reference DRAFT-TRAMMELL-IPFIX-TEXT-ADT * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQUIREMENTS * Normative Reference DRAFT-PETITHUGUENIN-P2PSIP-RELOAD-ONE-TO-MANY * Informative Reference DRAFT-GOOGLE-SELF-PUBLISHED-GEOFEEDS * Informative Reference RFC6991 * Normative Reference DRAFT-ZHOU-WEIRDS-RDAP-RESTFUL-SEARCH * Normative Reference DRAFT-IETF-BEHAVE-SYSLOG-NAT-LOGGING * Informative Reference DRAFT-KITAMURA-IPV6-ZONEID-FREE * Normative Reference DRAFT-SWEET-URI-ZONEID * Normative Reference RFC7373 * Informative Reference DRAFT-IETF-CDNI-URI-SIGNING * Normative Reference DRAFT-SONG-DCLC-TCPDC * Normative Reference DRAFT-LABER-SMTP-IMPT * Informative Reference DRAFT-JENNINGS-CORE-SENML * Informative Reference DRAFT-JPCERT-IPV6VULLNERABILITY-CHECK RFC6106: IPv6 Router Advertisement Options for DNS Configuration (19 pages) * Obsoletes RFC5006 * Informative Reference BCP140 * Informative Reference RFC1536 * Informative Reference RFC1535 * Normative Reference BCP14 * Informative Reference BCP38 * Possible Reference RFC5741 * Informative Reference RFC1034 * Normative Reference RFC1035 * Informative Reference RFC5006 * Informative Reference RFC2827 * Informative Reference STD13 * Informative Reference RFC3646 * Informative Reference RFC3736 * Informative Reference RFC5358 * Informative Reference RFC3971 * Normative Reference RFC4862 * Normative Reference RFC4861 * Normative Reference RFC2119 * Informative Reference RFC3315 * Informative Reference RFC4339 * Informative Reference RFC6763 * Informative Reference RFC6775 * Normative Reference RFC6434 * Normative Reference RFC6204 * Informative Reference RFC6731 * Normative Reference DRAFT-HOWARD-ISP-IP6RDNS * Informative Reference RFC7157 * Informative Reference RFC6911 * Informative Reference DRAFT-IETF-OPSAWG-AUTOMATED-NETWORK-CONFIGURATION * Normative Reference RFC6586 * Possible Reference DRAFT-GUNDAVELLI-NETEXT-PMIPV6-WLAN-APPLICABILITY * Normative Reference DRAFT-JIANG-IPV6-SITE-RENUM-GUIDELINE * Normative Reference RFC7084 * Informative Reference DRAFT-MAQUEDA-6LOWPAN-PGW * Informative Reference DRAFT-V6OPS-MULTIHOMING-WITHOUT-IPV6NAT * Informative Reference DRAFT-FLING-V6OPS-HYBRID-BRIDGED-ROUTED * Informative Reference DRAFT-BOUCADAIR-6MAN-SIP-PROXY * Normative Reference DRAFT-JIANG-6RENUM-ENTERPRISE * Normative Reference RFC6879 * Informative Reference DRAFT-CHOWN-HOMENET-ARCH * Informative Reference DRAFT-HAZEYAMA-WIDECAMP-IPV6-ONLY-EXPERIENCE * Normative Reference DRAFT-ARKKO-HOMENET-PREFIX-ASSIGNMENT * Informative Reference DRAFT-SARIKAYA-MIF-6MAN-RA-ROUTE * Normative Reference DRAFT-GONT-6MAN-SLAAC-DNS-CONFIG-ISSUES * Normative Reference DRAFT-YASUDA-CACHE-SERVER-SELECTION * Informative Reference RFC7381 * Informative Reference DRAFT-SARIKAYA-SOFTWIRE-6MAN-RAOPTIONS * Informative Reference RFC7066 * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQS-RFC3316UPDATE * Informative Reference DRAFT-KORHONEN-V6OPS-RFC3316BIS * Normative Reference DRAFT-RAFIEE-INTAREA-CGA-TSIG * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQUIREMENTS * Normative Reference DRAFT-GONT-OPSEC-IPV6-ND-SECURITY * Normative Reference RFC7359 * Informative Reference DRAFT-JVKJJMB-HOME-NETWORKING-INCREMENTAL * Informative Reference DRAFT-SARIKAYA-6MAN-RFC4191BIS * Reference DRAFT-PFISTER-MOVING-NET-AUTOCONF * Informative Reference DRAFT-SMITH-V6OPS-CE-DHCPV6-TRANSPARENCY * Normative Reference DRAFT-IETF-OPSEC-IPV6-ND-SECURITY * Normative Reference DRAFT-PFISTER-HOMENET-PREFIX-ASSIGNMENT * Reference DRAFT-OTIS-DNSSD-MDNS-XLINK * Normative Reference DRAFT-HOWARD-DNSOP-IP6RDNS * Normative Reference DRAFT-GONT-6MAN-ND-OPT-VALIDATION * Normative Reference DRAFT-JEONG-HOMENET-DEVICE-NAME-AUTOCONF * Normative Reference DRAFT-SARIKAYA-6MAN-SADR-OVERVIEW * Normative Reference DRAFT-JPCERT-IPV6VULLNERABILITY-CHECK * Informative Reference DRAFT-SARIKAYA-6MAN-NEXT-HOP-RA * Informative Reference DRAFT-SARIKAYA-6MAN-SADR-RA * Normative Reference DRAFT-IETF-6MAN-ND-OPT-VALIDATION RFC6164: Using 127-Bit IPv6 Prefixes on Inter-Router Links (8 pages) * Replaces DRAFT-KOHNO-IPV6-PREFIXLEN-P2P * Normative Reference RFC4291 * Informative Reference RFC4271 * Informative Reference RFC2526 * Possible Reference RFC5741 * Informative Reference RFC4443 * Informative Reference RFC3627 * Normative Reference RFC4861 * Informative Reference RFC5375 * Informative Reference RFC3756 * Normative Reference RFC2119 * Informative Reference RFC3021 * Normative Reference BCP14 * Updates RFC6547 * Informative Reference RFC7136 * Normative Reference RFC7421 * Normative Reference DRAFT-GASHINSKY-V6ND-ENHANCE * Informative Reference DRAFT-YMBK-NO-SUBNET-ANYCAST * Normative Reference DRAFT-GEORGE-6MAN-3627-HISTORIC * Normative Reference DRAFT-GASHINSKY-V6OPS-V6ND-PROBLEMS * Normative Reference RFC6583 * Normative Reference RFC6547 * Normative Reference DRAFT-GASHINSKY-6MAN-V6ND-ENHANCE * Informative Reference RFC6741 * Informative Reference DRAFT-CHKPVC-ENTERPRISE-INCREMENTAL-IPV6 * Informative Reference DRAFT-LOPEZ-V6OPS-DC-IPV6 * Informative Reference RFC7381 * Informative Reference DRAFT-IETF-OPSEC-V6 * Informative Reference DRAFT-CARPENTER-6MAN-UG * Possible Reference DRAFT-MA-V6OPS-IPV6-ADDRESS-ASSIGNMENT * Informative Reference DRAFT-IETF-V6OPS-DC-IPV6 * Informative Reference DRAFT-IETF-V6OPS-CIDR-PREFIX RFC6434: IPv6 Node Requirements (30 pages) * Obsoletes RFC4294 * Normative Reference RFC2671 * Normative Reference RFC3484 * Informative Reference RFC4302 * Informative Reference RFC2675 * Normative Reference RFC5996 * Informative Reference RFC3493 * Informative Reference RFC2464 * Informative Reference RFC2205 * Possible Reference RFC5175 * Normative Reference RFC5790 * Normative Reference RFC2460 * Normative Reference RFC2710 * Normative Reference RFC2711 * Informative Reference RFC5555 * Normative Reference RFC3590 * Normative Reference RFC4311 * Normative Reference RFC4607 * Normative Reference RFC4835 * Informative Reference RFC2491 * Normative Reference RFC4604 * Informative Reference RFC4380 * Normative Reference RFC5095 * Normative Reference RFC4303 * Informative Reference RFC4584 * Normative Reference RFC4293 * Informative Reference RFC5121 * Informative Reference RFC2492 * Informative Reference RFC6275 * Normative Reference RFC1034 * Informative Reference RFC4877 * Possible Reference RFC5741 * Informative Reference RFC4338 * Normative Reference RFC5952 * Normative Reference RFC5722 * Informative Reference RFC5006 * Normative Reference RFC4035 * Informative Reference RFC5014 * Informative Reference RFC3146 * Normative Reference BCP14 * Normative Reference RFC5942 * Normative Reference RFC4213 * Informative Reference RFC3776 * Possible Reference RFC4294 * Normative Reference RFC4291 * Possible Reference RFC4279 * Normative Reference RFC1981 * Normative Reference RFC3736 * Informative Reference RFC3542 * Normative Reference RFC4292 * Informative Reference RFC3971 * Informative Reference RFC3972 * Normative Reference RFC4862 * Informative Reference RFC3678 * Normative Reference RFC4861 * Informative Reference RFC2590 * Informative Reference RFC4944 * Informative Reference RFC4821 * Normative Reference RFC4941 * Normative Reference RFC2119 * Normative Reference RFC3810 * Normative Reference RFC3596 * Informative Reference RFC4191 * Normative Reference RFC1035 * Informative Reference RFC793 * Normative Reference RFC5453 * Informative Reference RFC3363 * Normative Reference RFC3315 * Normative Reference RFC4034 * Normative Reference RFC4301 * Normative Reference RFC4443 * Informative Reference RFC5072 * Normative Reference STD13 * Normative Reference RFC4033 * Normative Reference RFC4307 * Normative Reference RFC6437 * Normative Reference RFC6204 * Informative Reference RFC4884 * Normative Reference RFC6106 * Informative Reference RFC4429 * Normative Reference DRAFT-LIU-V6OPS-DHCPV6-SLAAC-GUIDANCE * Normative Reference DRAFT-TEMPLIN-AEROLINK * Informative Reference RFC6672 * Informative Reference DRAFT-IETF-V6OPS-MOBILE-DEVICE-PROFILE * Informative Reference RFC7219 * Informative Reference RFC6606 * Informative Reference DRAFT-TEMPLIN-INTAREA-SEAL * Normative Reference RFC7084 * Normative Reference RFC6706 * Informative Reference RFC6540 * Informative Reference DRAFT-CHKPVC-ENTERPRISE-INCREMENTAL-IPV6 * Normative Reference RFC6883 * Normative Reference DRAFT-CARPENTER-FLOW-LABEL-BALANCING * Normative Reference DRAFT-TARREAU-EXTEND-FLOW-LABEL-BALANCING * Informative Reference RFC7381 * Informative Reference DRAFT-IETF-OPSEC-V6 * Informative Reference DRAFT-KORHONEN-V6OPS-RFC3316BIS * Informative Reference RFC7066 * Normative Reference RFC7098 RFC6436: Rationale for Update to the IPv6 Flow Label Specification (13 pages) * Replaces DRAFT-CARPENTER-6MAN-FLOW-UPDATE * Informative Reference RFC4302 * Informative Reference RFC2205 * Informative Reference RFC2474 * Informative Reference RFC2460 * Possible Reference RFC5741 * Informative Reference RFC3697 * Informative Reference RFC6438 * Informative Reference RFC6437 * Informative Reference RFC6294 * Informative Reference DRAFT-DREIBHOLZ-IPV4-FLOWLABEL * Informative Reference DRAFT-GONT-6MAN-FLOWLABEL-SECURITY * Informative Reference RFC6437 * Informative Reference DRAFT-CARPENTER-FLOW-LABEL-BALANCING * Informative Reference RFC7098 * Informative Reference DRAFT-SMITH-ENHANCE-VNE-WITH-IPV6 RFC6437: IPv6 Flow Label Specification (15 pages) * Updates RFC2205 * Updates RFC2460 * Obsoletes RFC3697 * Normative Reference RFC4086 * Informative Reference RFC4311 * Normative Reference RFC2205 * Normative Reference BCP106 * Informative Reference BCP38 * Normative Reference RFC2460 * Informative Reference RFC4303 * Possible Reference RFC5741 * Informative Reference RFC4301 * Informative Reference RFC3697 * Informative Reference RFC4302 * Informative Reference RFC5971 * Informative Reference RFC6438 * Informative Reference RFC6436 * Informative Reference RFC2827 * Informative Reference RFC4732 * Normative Reference RFC2119 * Normative Reference BCP14 * Informative Reference DRAFT-KENT-IPSECME-SAFORIP-RFC4301BIS * Normative Reference DRAFT-DREIBHOLZ-IPV4-FLOWLABEL * Normative Reference DRAFT-THUBERT-6MAN-FLOW-LABEL-FOR-RPL * Normative Reference RFC7421 * Informative Reference DRAFT-BOUCADAIR-SFC-DESIGN-ANALYSIS * Normative Reference RFC6434 * Informative Reference RFC6936 * Normative Reference RFC6674 * Normative Reference RFC6438 * Informative Reference RFC6436 * Informative Reference DRAFT-GONT-6MAN-FLOWLABEL-SECURITY * Informative Reference DRAFT-BAKER-OPENSTACK-IPV6-MODEL * Normative Reference DRAFT-CARPENTER-V6OPS-LABEL-BALANCE * Informative Reference DRAFT-THUBERT-ROLL-FLOW-LABEL * Normative Reference DRAFT-CARPENTER-FLOW-LABEL-BALANCING * Informative Reference DRAFT-IETF-SOFTWIRE-4RD * Normative Reference DRAFT-TARREAU-EXTEND-FLOW-LABEL-BALANCING * Informative Reference DRAFT-SMITH-6MAN-MITIGATE-ND-CACHE-DOS-SLND * Normative Reference RFC7098 * Informative Reference DRAFT-LEE-SOFTWIRE-LW4OVER6-FAILOVER * Informative Reference DRAFT-BOUCADAIR-CHAINING-DESIGN-ANALYSIS * Normative Reference DRAFT-JIANG-INTAREA-CONET-GAP-ANALYSIS * Informative Reference DRAFT-IETF-L2TPEXT-KEYED-IPV6-TUNNEL * Informative Reference DRAFT-SMITH-ENHANCE-VNE-WITH-IPV6 * Informative Reference DRAFT-YORK-DART-DSCP-RTP * Informative Reference DRAFT-EGGERT-TSVWG-RFC5405BIS * Normative Reference DRAFT-WANG-V6OPS-FLOW-LABEL-REFELCTION * Informative Reference DRAFT-IETF-DART-DSCP-RTP * Informative Reference DRAFT-BORMANN-6LO-RPL-MESH * Normative Reference DRAFT-WANG-6MAN-FLOW-LABEL-REFLECTION * Normative Reference DRAFT-CONET-AEON-GAP-ANALYSIS * Reference DRAFT-MASSAR-V6MAN-MTU-LABEL * Normative Reference DRAFT-JPCERT-IPV6VULLNERABILITY-CHECK * Informative Reference DRAFT-TSVWG-RFC5405BIS * Informative Reference DRAFT-IETF-TSVWG-RFC5405BIS RFC6438: Using the IPv6 Flow Label for Equal Cost Multipath Routing and Link Aggregation in Tunnels (9 pages) * Replaces DRAFT-CARPENTER-FLOW-ECMP * Informative Reference RFC2991 * Informative Reference RFC2474 * Normative Reference RFC2460 * Normative Reference RFC2119 * Possible Reference RFC5741 * Normative Reference RFC3697 * Normative Reference BCP14 * Normative Reference RFC6437 * Informative Reference RFC6391 * Informative Reference RFC2784 * Informative Reference RFC4379 * Normative Reference DRAFT-YONG-TSVWG-GRE-IN-UDP-ENCAP * Informative Reference DRAFT-TEMPLIN-AEROLINK * Informative Reference RFC7325 * Informative Reference DRAFT-TEMPLIN-INTAREA-SEAL * Normative Reference DRAFT-TEMPLIN-INTAREA-VET * Informative Reference RFC6936 * Informative Reference RFC6436 * Normative Reference DRAFT-GONT-6MAN-FLOWLABEL-SECURITY * Informative Reference RFC6437 * Informative Reference DRAFT-CARPENTER-V6OPS-LABEL-BALANCE * Informative Reference DRAFT-TARREAU-HTTPBIS-NETWORK-FRIENDLY * Informative Reference DRAFT-CARPENTER-FLOW-LABEL-BALANCING * Informative Reference DRAFT-BITAR-LASSERRE-NVO3-DP-REQS * Informative Reference DRAFT-BL-NVO3-DATAPLANE-REQUIREMENTS * Informative Reference DRAFT-VILLAMIZAR-MPLS-FORWARDING * Informative Reference DRAFT-IETF-NVO3-DATAPLANE-REQUIREMENTS * Informative Reference DRAFT-XU-SOFTWIRE-IP-IN-UDP * Informative Reference RFC7098 * Informative Reference DRAFT-IETF-MPLS-IN-UDP * Normative Reference DRAFT-YONG-TSVWG-UDP-ENCAP-4-IP-TUNNELING * Informative Reference DRAFT-BOUCADAIR-CHAINING-DESIGN-ANALYSIS * Informative Reference DRAFT-BOUCADAIR-SFC-DESIGN-ANALYSIS * Normative Reference DRAFT-IETF-TSVWG-GRE-IN-UDP-ENCAP * Informative Reference DRAFT-ARKKO-STRINT-NETWORKING-FUNCTIONS * Informative Reference DRAFT-SMITH-ENHANCE-VNE-WITH-IPV6 * Informative Reference DRAFT-EGGERT-TSVWG-RFC5405BIS * Normative Reference DRAFT-WANG-V6OPS-FLOW-LABEL-REFELCTION * Normative Reference DRAFT-WANG-6MAN-FLOW-LABEL-REFLECTION * Informative Reference DRAFT-TSVWG-RFC5405BIS * Informative Reference DRAFT-IETF-TSVWG-RFC5405BIS RFC6547: RFC 3627 to Historic Status (3 pages) * Obsoletes RFC3627 * Updates RFC6164 * Replaces DRAFT-GEORGE-6MAN-3627-HISTORIC * Informative Reference BCP9 * Normative Reference RFC3627 * Possible Reference RFC5741 * Informative Reference RFC2026 * Normative Reference RFC6164 * Informative Reference DRAFT-IETF-OPSEC-V6 * Possible Reference DRAFT-MA-V6OPS-IPV6-ADDRESS-ASSIGNMENT RFC6553: The Routing Protocol for Low-Power and Lossy Networks (RPL) Option for Carrying RPL Information in Data-Plane Datagrams (9 pages) * Replaces DRAFT-HUI-6MAN-RPL-OPTION * Normative Reference RFC6550 * Normative Reference RFC5226 * Informative Reference RFC6554 * Normative Reference RFC2460 * Normative Reference RFC2473 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC6206 * Normative Reference RFC2328 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference DRAFT-IETF-6TISCH-ARCHITECTURE * Normative Reference DRAFT-IETF-6TISCH-MINIMAL * Normative Reference DRAFT-GONT-OPSEC-IPV6-EH-FILTERING * Normative Reference DRAFT-THUBERT-6MAN-FLOW-LABEL-FOR-RPL * Normative Reference RFC6550 * Normative Reference DRAFT-WANG-ROLL-DATA-ROBUSTNESS * Informative Reference RFC6997 * Informative Reference DRAFT-CLAUSEN-LLN-RPL-EXPERIENCES * Normative Reference DRAFT-THUBERT-ROLL-FLOW-LABEL * Informative Reference DRAFT-HUI-VASSEUR-ROLL-RPL-DEPLOYMENT * Normative Reference DRAFT-BORMANN-6LO-RPL-MESH * Normative Reference DRAFT-TOUTAIN-6LO-LOCAL-EXTENSIONS * Normative Reference DRAFT-THUBERT-6LO-RPL-NHC * Normative Reference DRAFT-GONT-6MAN-IPV6-OPT-TRANSMIT * Normative Reference DRAFT-THUBERT-6LO-ROUTING-DISPATCH RFC6554: An IPv6 Routing Header for Source Routes with the Routing Protocol for Low-Power and Lossy Networks (RPL) (13 pages) * Replaces DRAFT-HUI-6MAN-RPL-ROUTING-HEADER * Informative Reference RFC6550 * Normative Reference RFC2473 * Normative Reference RFC2460 * Normative Reference RFC5095 * Possible Reference RFC5741 * Normative Reference RFC4443 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference DRAFT-IETF-ROLL-APPLICABILITY-HOME-BUILDING * Informative Reference RFC7045 * Normative Reference DRAFT-IETF-6TISCH-ARCHITECTURE * Normative Reference DRAFT-IETF-6TISCH-MINIMAL * Normative Reference DRAFT-GONT-OPSEC-IPV6-EH-FILTERING * Normative Reference RFC6550 * Informative Reference RFC6553 * Normative Reference DRAFT-BRANDT-ROLL-RPL-APPLICABILITY-HOME-BUILDING * Normative Reference RFC6997 * Normative Reference RFC6998 * Informative Reference DRAFT-CLAUSEN-LLN-RPL-EXPERIENCES * Informative Reference DRAFT-HUI-VASSEUR-ROLL-RPL-DEPLOYMENT * Normative Reference DRAFT-BARYUN-MANET-TERMINOLOGY * Informative Reference DRAFT-CARPENTER-6MAN-EXT-TRANSMIT * Normative Reference DRAFT-KO-ROLL-MIX-NETWORK-PATHOLOGY * Informative Reference DRAFT-WKUMARI-LONG-HEADERS * Normative Reference DRAFT-TOUTAIN-6LO-LOCAL-EXTENSIONS * Normative Reference DRAFT-YI-MANET-OLSRV2-MULTIPATH * Informative Reference DRAFT-BORMANN-6LO-RPL-MESH * Normative Reference DRAFT-IETF-MANET-OLSRV2-MULTIPATH * Normative Reference DRAFT-GONT-6MAN-IPV6-OPT-TRANSMIT * Informative Reference DRAFT-VYNCKE-6MAN-SEGMENT-ROUTING-SECURITY * Informative Reference DRAFT-BERGMANN-BIER-CCAST * Normative Reference DRAFT-THUBERT-6LO-ROUTING-DISPATCH RFC6564: A Uniform Format for IPv6 Extension Headers (6 pages) * Updates RFC2460 * Normative Reference RFC2460 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference RFC7045 * Normative Reference DRAFT-GONT-6MAN-RFC6564BIS * Normative Reference RFC6971 * Normative Reference DRAFT-GONT-OPSEC-DHCPV6-SHIELD * Normative Reference DRAFT-GONT-OPSEC-IPV6-ND-SHIELD * Normative Reference DRAFT-CARPENTER-6MAN-EXT-TRANSMIT * Informative Reference DRAFT-BOUCADAIR-CHAINING-DESIGN-ANALYSIS * Informative Reference DRAFT-BOUCADAIR-SFC-DESIGN-ANALYSIS * Normative Reference DRAFT-GONT-6MAN-IPV6-UNIVERSAL-EXTENSION-HEADER * Normative Reference DRAFT-KAMPANAKIS-6MAN-IPV6-EH-PARSING * Normative Reference DRAFT-IETF-SPRING-PROBLEM-STATEMENT * Normative Reference DRAFT-SKEEN-6MAN-IPV6GEO * Normative Reference DRAFT-JPCERT-IPV6VULLNERABILITY-CHECK RFC6724: Default Address Selection for Internet Protocol Version 6 (IPv6) (32 pages) * Replaces DRAFT-IETF-6MAN-RFC3484-REVISE * Obsoletes RFC3484 * Informative Reference RFC3484 * Informative Reference RFC3927 * Informative Reference RFC5220 * Informative Reference RFC6598 * Informative Reference RFC1794 * Normative Reference BCP14 * Informative Reference BCP38 * Informative Reference RFC4380 * Informative Reference RFC1812 * Informative Reference RFC1918 * Informative Reference RFC6275 * Possible Reference RFC5741 * Informative Reference RFC2827 * Informative Reference RFC5969 * Informative Reference RFC4213 * Informative Reference RFC3493 * Informative Reference RFC4291 * Informative Reference BCP153 * Informative Reference BCP5 * Informative Reference RFC5214 * Informative Reference RFC4007 * Informative Reference RFC3879 * Normative Reference RFC4862 * Informative Reference RFC4861 * Normative Reference RFC4941 * Normative Reference RFC2119 * Normative Reference RFC4193 * Informative Reference RFC4191 * Normative Reference RFC3056 * Normative Reference RFC6145 * Informative Reference RFC5014 * Informative Reference RFC3701 * Informative Reference DRAFT-LIU-RUNNING-MULTIPLE-PREFIXES * Informative Reference DRAFT-LIU-OPSAREA-IPV6-RENUMBERING-GUIDELINES * Normative Reference DRAFT-WING-DHC-DNS-RECONFIGURE * Normative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Informative Reference DRAFT-IETF-V6OPS-ULA-USAGE-RECOMMENDATIONS * Informative Reference DRAFT-MARTIN-SMTP-TARGET-HOST-SELECTION-IPV4-IPV6 * Reference DRAFT-CARPENTER-NMRG-HOMENET-AN-USE-CASE * Normative Reference RFC7051 * Informative Reference DRAFT-IETF-V6OPS-MOBILE-DEVICE-PROFILE * Normative Reference DRAFT-TEMPLIN-INTAREA-VET * Informative Reference DRAFT-IETF-6MAN-ADDR-SELECT-CONSIDERATIONS * Normative Reference DRAFT-IETF-HIP-RFC5204-BIS * Normative Reference DRAFT-IETF-HIP-RFC5201-BIS * Informative Reference RFC6732 * Normative Reference RFC7157 * Informative Reference RFC7078 * Normative Reference DRAFT-IETF-V6OPS-6TO4-TO-HISTORIC * Normative Reference RFC6971 * Informative Reference RFC6964 * Informative Reference RFC7010 * Informative Reference RFC6782 * Normative Reference DRAFT-WING-MPTCP-PCP * Informative Reference RFC7368 * Normative Reference DRAFT-REDDY-MIF-DHCPV6-PRECEDENCE-OPS * Normative Reference DRAFT-BHANDARI-DHC-CLASS-BASED-PREFIX * Informative Reference DRAFT-LIU-V6OPS-ULA-USAGE-ANALYSIS * Normative Reference RFC6740 * Possible Reference RFC6748 * Normative Reference DRAFT-KORHONEN-DMM-PREFIX-PROPERTIES * Normative Reference DRAFT-IETF-MIF-HAPPY-EYEBALLS-EXTENSION * Normative Reference DRAFT-JIANG-SEMANTIC-PREFIX * Normative Reference DRAFT-ZUNIGA-DMM-GAP-ANALYSIS * Informative Reference DRAFT-SMITH-V6OPS-LARGER-IPV6-LOOPBACK-PREFIX * Informative Reference DRAFT-KERANEN-MMUSIC-RFC5245BIS * Informative Reference RFC7381 * Normative Reference RFC7269 * Informative Reference RFC7404 * Normative Reference DRAFT-KALIWODA-SUNSET4-DUAL-IPV6-COEXIST * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQS-RFC3316UPDATE * Normative Reference DRAFT-REDDY-MMUSIC-ICE-HAPPY-EYEBALLS * Normative Reference DRAFT-JIANG-V6OPS-SEMANTIC-PREFIX * Normative Reference DRAFT-GONT-OPSEC-VPN-LEAKAGES * Normative Reference DRAFT-BOOT-HOMENET-BRDP * Informative Reference DRAFT-BAKER-HAPPIER-EYEBALLS * Normative Reference DRAFT-BINET-V6OPS-CELLULAR-HOST-REQUIREMENTS * Normative Reference RFC7488 * Normative Reference RFC7359 * Informative Reference RFC7429 * Informative Reference RFC7059 * Informative Reference DRAFT-GRUNDEMANN-HOMENET-HIPNET * Normative Reference DRAFT-KORHONEN-6MAN-PREFIX-PROPERTIES * Normative Reference DRAFT-TROAN-HOMENET-SADR * Normative Reference DRAFT-YEGIN-DMM-ONDEMAND-MOBILITY * Informative Reference DRAFT-BAJPAI-HAPPY * Informative Reference DRAFT-GRUNDEMANN-HIPNET * Informative Reference DRAFT-ANIPKO-MIF-MPVD-ARCH * Informative Reference DRAFT-LIU-V6OPS-RUNNING-MULTIPLE-PREFIXES * Informative Reference DRAFT-LEPAPE-6MAN-PREFIX-METADATA * Informative Reference DRAFT-IETF-MMUSIC-RFC5245BIS * Informative Reference DRAFT-COOPER-6MAN-IPV6-ADDRESS-GENERATION-PRIVACY * Normative Reference DRAFT-VANREIN-6BED4 * Normative Reference DRAFT-IETF-6MAN-IPV6-ADDRESS-GENERATION-PRIVACY * Informative Reference DRAFT-IETF-MIF-MPVD-ARCH * Informative Reference DRAFT-IETF-DHC-CONN-STATUS * Informative Reference DRAFT-IETF-SIPCORE-DNS-DUAL-STACK * Normative Reference DRAFT-IETF-RTCWEB-TRANSPORTS * Normative Reference DRAFT-SARIKAYA-6MAN-SADR-OVERVIEW * Normative Reference DRAFT-MARTINSEN-MMUSIC-ICE-DUALSTACK-FAIRNESS * Normative Reference DRAFT-IETF-OPSEC-IPV6-HOST-SCANNING * Normative Reference DRAFT-HERBERT-NVO3-ILA * Informative Reference DRAFT-THALER-6LO-PRIVACY-ADDRS * Normative Reference DRAFT-SIJEON-DMM-USE-CASES-API-SOURCE * Informative Reference DRAFT-PFISTER-6MAN-SADR-RA * Normative Reference DRAFT-MOSES-DMM-DHCP-ONDEMAND-MOBILITY RFC6788: The Line-Identification Option (17 pages) * Normative Reference RFC3971 * Normative Reference RFC1661 * Informative Reference RFC3046 * Informative Reference RFC4649 * Normative Reference RFC2473 * Normative Reference RFC2119 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference RFC4862 * Normative Reference BCP14 * Normative Reference RFC4861 * Informative Reference RFC20 * Informative Reference RFC2132 * Normative Reference DRAFT-GONT-OPSEC-IPV6-EH-FILTERING * Informative Reference DRAFT-SARIKAYA-SOFTWIRE-6RDMULTICAST * Informative Reference DRAFT-ZHOU-SOFTWIRE-6RDMULTICAST * Normative Reference DRAFT-GONT-6MAN-IPV6-OPT-TRANSMIT RFC6874: Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers (10 pages) * Replaces DRAFT-CARPENTER-6MAN-URI-ZONEID * Updates RFC3986 * Normative Reference RFC5234 * Informative Reference RFC3493 * Informative Reference RFC4001 * Normative Reference STD66 * Informative Reference RFC4007 * Possible Reference RFC5741 * Normative Reference RFC5952 * Normative Reference BCP14 * Informative Reference RFC3986 * Normative Reference STD68 * Normative Reference RFC2119 * Informative Reference RFC6943 * Informative Reference DRAFT-MCDONALD-LDAP-PRINTER-SCHEMA * Normative Reference DRAFT-KERWIN-FILE-SCHEME * Informative Reference DRAFT-IETF-WEIRDS-RDAP-QUERY * Normative Reference DRAFT-KITAMURA-IPV6-ZONEID-FREE * Informative Reference DRAFT-SWEET-URI-ZONEID * Normative Reference DRAFT-IETF-APPSAWG-FILE-SCHEME RFC6935: IPv6 and UDP Checksums for Tunneled Packets (12 pages) * Updates RFC2460 * Informative Reference BCP145 * Informative Reference RFC5619 * Normative Reference RFC2460 * Possible Reference RFC5741 * Informative Reference RFC5405 * Informative Reference RFC6830 * Informative Reference RFC3828 * Normative Reference BCP14 * Informative Reference BCP38 * Informative Reference RFC2827 * Normative Reference RFC6936 * Normative Reference RFC2119 * Possible Reference DRAFT-HERBERT-GUE * Normative Reference DRAFT-BRYANT-IP-METADATA * Normative Reference DRAFT-YONG-TSVWG-GRE-IN-UDP-ENCAP * Informative Reference RFC7450 * Informative Reference DRAFT-TEMPLIN-AEROLINK * Informative Reference DRAFT-TEMPLIN-INTAREA-SEAL * Informative Reference RFC6936 * Normative Reference DRAFT-IETF-TSVWG-GRE-IN-UDP-ENCAP * Normative Reference DRAFT-IETF-LISP-INTRODUCTION * Informative Reference DRAFT-GROSS-GENEVE * Informative Reference DRAFT-HERBERT-GUECSUM * Normative Reference DRAFT-XU-SOFTWIRE-IP-IN-UDP * Informative Reference DRAFT-IETF-TSVWG-RFC5405BIS * Informative Reference DRAFT-IETF-TAPS-TRANSPORTS * Normative Reference DRAFT-IETF-MPLS-IN-UDP * Normative Reference DRAFT-RTG-DT-ENCAP RFC6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums (40 pages) * Replaces DRAFT-FAIRHURST-TSVWG-6MAN-UDPZERO * Replaces DRAFT-6MAN-UDPZERO * Informative Reference BCP145 * Informative Reference STD64 * Normative Reference RFC768 * Informative Reference RFC3550 * Informative Reference RFC2460 * Informative Reference RFC5415 * Normative Reference BCP14 * Informative Reference BCP38 * Informative Reference RFC5097 * Informative Reference BCP89 * Possible Reference RFC5741 * Informative Reference RFC6830 * Informative Reference RFC5722 * Informative Reference RFC2827 * Informative Reference RFC6935 * Informative Reference RFC4963 * Informative Reference RFC5405 * Informative Reference RFC3828 * Informative Reference RFC3819 * Normative Reference RFC2119 * Informative Reference RFC1071 * Informative Reference RFC793 * Normative Reference RFC791 * Informative Reference RFC4443 * Informative Reference RFC6438 * Informative Reference RFC6437 * Informative Reference RFC1624 * Informative Reference RFC1141 * Normative Reference DRAFT-HERBERT-GUE * Normative Reference DRAFT-BRYANT-IP-METADATA * Normative Reference DRAFT-YONG-TSVWG-GRE-IN-UDP-ENCAP * Informative Reference RFC7450 * Informative Reference DRAFT-TEMPLIN-AEROLINK * Informative Reference DRAFT-TEMPLIN-INTAREA-SEAL * Informative Reference RFC7252 * Normative Reference RFC6935 * Informative Reference RFC6951 * Normative Reference DRAFT-IETF-MPLS-IN-UDP * Normative Reference DRAFT-IETF-TSVWG-GRE-IN-UDP-ENCAP * Normative Reference DRAFT-IETF-LISP-INTRODUCTION * Informative Reference DRAFT-HERBERT-GUECSUM * Normative Reference DRAFT-XU-SOFTWIRE-IP-IN-UDP * Informative Reference DRAFT-IETF-TSVWG-RFC5405BIS * Informative Reference DRAFT-IETF-TAPS-TRANSPORTS * Normative Reference DRAFT-RTG-DT-ENCAP RFC6946: Processing of IPv6 "Atomic" Fragments (9 pages) * Replaces DRAFT-GONT-6MAN-IPV6-ATOMIC-FRAGMENTS * Updates RFC2460 * Updates RFC5722 * Normative Reference RFC2460 * Informative Reference RFC6274 * Possible Reference RFC5741 * Normative Reference RFC4443 * Normative Reference RFC5722 * Normative Reference BCP14 * Normative Reference RFC4861 * Normative Reference RFC2119 * Informative Reference RFC5927 * Informative Reference DRAFT-IETF-6MAN-PREDICTABLE-FRAGMENT-ID * Normative Reference RFC7269 * Informative Reference DRAFT-TAYLOR-V6OPS-FRAGDROP * Normative Reference DRAFT-KAMPANAKIS-6MAN-IPV6-EH-PARSING * Normative Reference DRAFT-GONT-V6OPS-IPV6-EHS-IN-REAL-WORLD * Informative Reference DRAFT-GONT-6MAN-DEPRECATE-ATOMFRAG-GENERATION * Informative Reference DRAFT-ANDERSON-V6OPS-SIIT-DC * Informative Reference DRAFT-IETF-6MAN-DEPRECATE-ATOMFRAG-GENERATION * Informative Reference DRAFT-JPCERT-IPV6VULLNERABILITY-CHECK * Informative Reference DRAFT-IETF-V6OPS-SIIT-DC RFC6957: Duplicate Address Detection Proxy (16 pages) * Replaces DRAFT-COSTA-6MAN-DAD-PROXY * Informative Reference RFC6496 * Informative Reference RFC6275 * Informative Reference RFC6775 * Informative Reference RFC3971 * Possible Reference RFC5741 * Informative Reference RFC4389 * Informative Reference RFC3972 * Normative Reference RFC4862 * Informative Reference RFC5909 * Normative Reference RFC4861 * Normative Reference BCP14 * Informative Reference RFC5072 * Normative Reference RFC2119 * Informative Reference RFC6620 * Normative Reference RFC6085 * Informative Reference RFC7136 * Normative Reference DRAFT-FAN-IPFIX-CONTENT-INFO-REQ * Normative Reference DRAFT-YOURTCHENKO-6MAN-DAD-ISSUES * Normative Reference DRAFT-NORDMARK-6MAN-DAD-APPROACHES RFC6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery (10 pages) * Replaces DRAFT-GONT-6MAN-ND-EXTENSION-HEADERS * Updates RFC3971 * Updates RFC4861 * Informative Reference RFC6494 * Normative Reference RFC2119 * Informative Reference RFC3971 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC4861 * Informative Reference RFC3756 * Informative Reference RFC6105 * Informative Reference RFC6104 * Normative Reference RFC7113 * Normative Reference RFC7066 * Informative Reference DRAFT-GONT-V6OPS-IPV6-EHS-IN-REAL-WORLD * Informative Reference DRAFT-TEMPLIN-AEROLINK * Normative Reference DRAFT-JPCERT-IPV6VULLNERABILITY-CHECK * Informative Reference DRAFT-IETF-OPSEC-V6 RFC7045: Transmission and Processing of IPv6 Extension Headers (10 pages) * Replaces DRAFT-CARPENTER-6MAN-EXT-TRANSMIT * Informative Reference BCP26 * Normative Reference RFC2119 * Informative Reference RFC6275 * Normative Reference RFC2780 * Normative Reference BCP37 * Normative Reference RFC3692 * Normative Reference BCP14 * Informative Reference RFC5533 * Normative Reference BCP82 * Possible Reference RFC5741 * Informative Reference RFC4303 * Informative Reference RFC5095 * Normative Reference RFC2460 * Normative Reference RFC6564 * Informative Reference RFC4302 * Normative Reference RFC4727 * Informative Reference RFC6554 * Informative Reference RFC5226 * Informative Reference RFC5201 * Updates RFC2780 * Updates RFC2460 * Normative Reference DRAFT-GONT-OPSEC-IPV6-EH-FILTERING * Normative Reference DRAFT-GONT-6MAN-RFC6564BIS * Informative Reference DRAFT-IETF-HIP-RFC5201-BIS * Normative Reference RFC7113 * Normative Reference RFC7112 * Normative Reference DRAFT-IETF-OPSEC-DHCPV6-SHIELD * Informative Reference DRAFT-IETF-MPLS-OAM-IPV6-RAO * Normative Reference DRAFT-GONT-6MAN-IPV6-OPT-TRANSMIT * Normative Reference DRAFT-GONT-6MAN-IPV6-UNIVERSAL-EXTENSION-HEADER * Normative Reference DRAFT-KAMPANAKIS-6MAN-IPV6-EH-PARSING * Normative Reference DRAFT-IETF-SPRING-PROBLEM-STATEMENT * Informative Reference DRAFT-GONT-V6OPS-IPV6-EHS-IN-REAL-WORLD * Informative Reference DRAFT-BOUCADAIR-SFC-DESIGN-ANALYSIS * Informative Reference DRAFT-NADERI-IPV6-PROBING * Normative Reference DRAFT-GONT-OPSEC-IPV6-FIREWALL-REQS RFC7048: Neighbor Unreachability Detection Is Too Impatient (8 pages) * Replaces DRAFT-NORDMARK-6MAN-IMPATIENT-NUD * Updates RFC4861 * Normative Reference RFC2119 * Informative Reference STD37 * Normative Reference RFC4861 * Normative Reference BCP14 * Informative Reference RFC826 * Possible Reference RFC5741 * Normative Reference RFC3971 * Informative Reference RFC6583 * Informative Reference DRAFT-CERVENY-BMWG-IPV6-ND * Informative Reference DRAFT-CHAKRABARTI-NORDMARK-6MAN-EFFICIENT-ND * Normative Reference DRAFT-YOURTCHENKO-COLITTI-ND-REDUCE-MULTICAST * Normative Reference DRAFT-MCCANN-DMM-PREFIXCOST RFC7078: Distributing Address Selection Policy Using DHCPv6 (12 pages) * Replaces DRAFT-FUJISAKI-6MAN-ADDR-SELECT-OPT * Normative Reference RFC2119 * Informative Reference RFC4941 * Normative Reference BCP14 * Possible Reference RFC5741 * Normative Reference RFC3315 * Informative Reference RFC2460 * Informative Reference RFC5220 * Informative Reference RFC6724 * Informative Reference RFC5221 * Informative Reference RFC4291 * Informative Reference RFC3484 * Normative Reference RFC7157 * Informative Reference DRAFT-IETF-MIF-MPVD-ARCH * Normative Reference DRAFT-SARIKAYA-6MAN-SADR-OVERVIEW * Informative Reference DRAFT-TEMPLIN-AEROLINK RFC7112: Implications of Oversized IPv6 Header Chains (8 pages) * Replaces DRAFT-GONT-6MAN-OVERSIZED-HEADER-CHAIN * Updates RFC2460 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference BCP84 * Normative Reference RFC1981 * Normative Reference RFC7045 * Informative Reference RFC2827 * Informative Reference BCP38 * Normative Reference RFC4443 * Normative Reference RFC4821 * Possible Reference RFC5741 * Informative Reference RFC3704 * Normative Reference RFC2460 * Normative Reference DRAFT-GONT-OPSEC-IPV6-EH-FILTERING * Informative Reference DRAFT-GONT-6MAN-RFC6564BIS * Normative Reference RFC7113 * Informative Reference DRAFT-IETF-OPSEC-V6 * Normative Reference DRAFT-IETF-OPSEC-DHCPV6-SHIELD * Informative Reference DRAFT-GONT-6MAN-IPV6-UNIVERSAL-EXTENSION-HEADER * Normative Reference DRAFT-KAMPANAKIS-6MAN-IPV6-EH-PARSING * Normative Reference DRAFT-GONT-OPSEC-IPV6-FIREWALL-REQS * Normative Reference DRAFT-GONT-6MAN-IPV6-OPT-TRANSMIT * Informative Reference DRAFT-JPCERT-IPV6VULLNERABILITY-CHECK RFC7136: Significance of IPv6 Interface Identifiers (10 pages) * Replaces DRAFT-CARPENTER-6MAN-UG * Normative Reference RFC7042 * Informative Reference RFC6775 * Informative Reference RFC6164 * Informative Reference RFC4982 * Informative Reference RFC2526 * Informative Reference BCP26 * Normative Reference RFC2119 * Informative Reference RFC4941 * Normative Reference RFC4862 * Informative Reference RFC3972 * Informative Reference RFC6957 * Informative Reference RFC5214 * Normative Reference RFC4291 * Informative Reference RFC6741 * Informative Reference RFC3307 * Informative Reference RFC3306 * Updates RFC4291 * Informative Reference RFC6052 * Possible Reference RFC5741 * Normative Reference RFC5453 * Normative Reference BCP14 * Informative Reference RFC5535 * Normative Reference BCP141 * Informative Reference RFC5226 * Normative Reference DRAFT-RAFIEE-6MAN-CGA-ATTACK * Informative Reference DRAFT-IRTF-NMRG-AN-GAP-ANALYSIS * Normative Reference DRAFT-RAFIEE-6MAN-SSAS * Normative Reference RFC7421 * Normative Reference RFC7217 * Informative Reference DRAFT-IETF-SOFTWIRE-4RD * Normative Reference DRAFT-IETF-OPSEC-IPV6-HOST-SCANNING * Normative Reference DRAFT-IETF-6LO-BTLE * Normative Reference DRAFT-IETF-6MAN-IPV6-ADDRESS-GENERATION-PRIVACY * Informative Reference DRAFT-SMITH-ENHANCE-VNE-WITH-IPV6 * Normative Reference DRAFT-IETF-6LO-6LOBAC * Normative Reference DRAFT-RAFIEE-RFC3972-BIS * Normative Reference DRAFT-GONT-DHC-STABLE-PRIVACY-ADDRESSES * Informative Reference DRAFT-THALER-6LO-PRIVACY-ADDRS * Normative Reference DRAFT-IETF-DHC-STABLE-PRIVACY-ADDRESSES RFC7217: A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC) (19 pages) * Replaces DRAFT-GONT-6MAN-STABLE-PRIVACY-ADDRESSES * Informative Reference RFC7113 * Normative Reference RFC3315 * Informative Reference RFC6105 * Normative Reference RFC7136 * Normative Reference RFC2119 * Normative Reference RFC4193 * Normative Reference RFC4941 * Informative Reference RFC1321 * Informative Reference RFC1948 * Normative Reference RFC4861 * Normative Reference RFC4862 * Normative Reference RFC3972 * Normative Reference RFC3971 * Informative Reference RFC2470 * Informative Reference RFC3542 * Normative Reference BCP106 * Informative Reference RFC4122 * Normative Reference RFC4291 * Informative Reference RFC3493 * Informative Reference RFC6059 * Informative Reference RFC6151 * Possible Reference RFC5741 * Normative Reference RFC4086 * Normative Reference RFC5453 * Normative Reference BCP14 * Normative Reference RFC2460 * Informative Reference RFC2467 * Informative Reference RFC2464 * Informative Reference DRAFT-IETF-V6OPS-MOBILE-DEVICE-PROFILE * Informative Reference DRAFT-IETF-OPSEC-V6 * Normative Reference DRAFT-IETF-OPSEC-IPV6-HOST-SCANNING * Informative Reference DRAFT-IETF-V6OPS-DESIGN-CHOICES * Normative Reference DRAFT-IETF-6MAN-IPV6-ADDRESS-GENERATION-PRIVACY * Informative Reference DRAFT-SMITH-ENHANCE-VNE-WITH-IPV6 * Informative Reference DRAFT-THUBERT-6LO-RFC6775-UPDATE-REQS * Normative Reference DRAFT-SARIKAYA-6LO-CGA-ND * Informative Reference RFC7421 * Informative Reference DRAFT-GONT-DHC-STABLE-PRIVACY-ADDRESSES * Informative Reference DRAFT-BAKER-OPENSTACK-IPV6-MODEL * Normative Reference DRAFT-STRUIK-6LO-ON-IPV6-ADDRESSING * Normative Reference DRAFT-IETF-6MAN-DEFAULT-IIDS * Informative Reference DRAFT-THALER-6LO-PRIVACY-ADDRS * Informative Reference DRAFT-IETF-DHC-STABLE-PRIVACY-ADDRESSES RFC7346: IPv6 Multicast Address Scopes (6 pages) * Normative Reference RFC4291 * Normative Reference RFC4007 * Informative Reference DRAFT-IETF-ROLL-TRICKLE-MCAST * Updates RFC4291 * Updates RFC4007 * Normative Reference DRAFT-IETF-DNSSD-REQUIREMENTS * Normative Reference DRAFT-IETF-ROLL-ADMIN-LOCAL-POLICY * Normative Reference DRAFT-IETF-ROLL-TRICKLE-MCAST * Informative Reference RFC7390 * Possible Reference DRAFT-HERBERT-NVO3-ILA RFC7371: Updates to the IPv6 Multicast Addressing Architecture (10 pages) * Replaces DRAFT-BOUCADAIR-6MAN-MULTICAST-ADDR-ARCH-UPDATE * Normative Reference RFC3306 * Normative Reference RFC5952 * Normative Reference RFC3956 * Normative Reference RFC4291 * Informative Reference DRAFT-IETF-MBONED-64-MULTICAST-ADDRESS-FORMAT * Normative Reference BCP14 * Normative Reference RFC2119 * Updates RFC3306 * Updates RFC3956 * Updates RFC4291 * Normative Reference DRAFT-CHODOREK-6MAN-MULTIGROUP-MULTICAST-ADDR RFC7421: Analysis of the 64-bit Boundary in IPv6 Addressing (24 pages) * Normative Reference RFC3590 * Normative Reference RFC5692 * Normative Reference RFC7136 * Normative Reference RFC6164 * Normative Reference RFC2529 * Normative Reference RFC5453 * Normative Reference RFC7084 * Normative Reference RFC3315 * Normative Reference RFC5969 * Normative Reference RFC3056 * Normative Reference RFC4191 * Informative Reference RFC7368 * Normative Reference RFC3956 * Normative Reference RFC2526 * Normative Reference RFC3810 * Normative Reference RFC4941 * Informative Reference RFC5505 * Normative Reference BCP157 * Normative Reference RFC4944 * Normative Reference RFC2590 * Normative Reference RFC4861 * Normative Reference RFC4862 * Normative Reference RFC3972 * Normative Reference RFC6437 * Normative Reference RFC2470 * Informative Reference RFC4692 * Normative Reference RFC5214 * Informative Reference RFC6877 * Normative Reference RFC2492 * Normative Reference RFC4291 * Normative Reference RFC7296 * Informative Reference DRAFT-IETF-6LO-6LOBAC * Normative Reference RFC4213 * Normative Reference RFC6296 * Normative Reference RFC5942 * Informative Reference RFC3756 * Normative Reference RFC3146 * Normative Reference RFC6177 * Informative Reference RFC6741 * Informative Reference RFC4887 * Informative Reference RFC7094 * Informative Reference DRAFT-IETF-6MAN-IPV6-ADDRESS-GENERATION-PRIVACY * Normative Reference RFC3306 * Normative Reference RFC6052 * Normative Reference RFC4338 * Possible Reference RFC5741 * Informative Reference DRAFT-TEMPLIN-AEROLINK * Informative Reference DRAFT-IETF-6LO-LOWPANZ * Normative Reference RFC5072 * Normative Reference RFC5121 * Normative Reference STD79 * Informative Reference RFC7278 * Normative Reference RFC6146 * Normative Reference RFC4380 * Informative Reference RFC6583 * Normative Reference RFC5533 * Normative Reference RFC5535 * Informative Reference RFC2629 * Normative Reference RFC2710 * Replaces DRAFT-CARPENTER-6MAN-WHY64 * Normative Reference RFC2497 * Normative Reference RFC2467 * Normative Reference RFC2464 * Informative Reference DRAFT-IETF-OPSEC-IPV6-HOST-SCANNING * Informative Reference RFC7217 * Informative Reference DRAFT-IETF-6LOWPAN-BTLE * Normative Reference RFC4429 * Informative Reference DRAFT-IETF-6MAN-IPV6-ADDRESS-GENERATION-PRIVACY * Informative Reference DRAFT-IETF-OPSEC-IPV6-HOST-SCANNING * Informative Reference DRAFT-IETF-V6OPS-CIDR-PREFIX * Informative Reference DRAFT-THALER-6LO-PRIVACY-ADDRS IPv6 over Networks of Resource-constrained Nodes (6lo) ------------------------------------------------------ Charter Last Modified: 2014-12-17 Current Status: Active Chairs: Samita Chakrabarti Gabriel Montenegro Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Brian Haberman Tech Advisor: Ralph Droms Secretary: james Mailing Lists: General Discussion: 6lo@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/6lo Archive: http://www.ietf.org/mail-archive/web/6lo/current/maillist.html Description of Working Group: 6lo focuses on the work that facilitates IPv6 connectivity over constrained node networks with the characteristics of: * limited power, memory and processing resources * hard upper bounds on state, code space and processing cycles * optimization of energy and network bandwidth usage * lack of some layer 2 services like complete device connectivity and broadcast/multicast Specifically, 6lo will work on: 1. IPv6-over-foo adaptation layer specifications using 6LoWPAN technologies (RFC4944, RFC6282, RFC6775) for link layer technologies of interest in constrained node networks 2. Information and data models (e.g., MIB modules) for these adaptation layers for basic monitoring and troubleshooting. 3. Specifications, such as low-complexity header compression, that are applicable to more than one adaptation layer specification 4. Maintenance and informational documents required for the existing IETF specifications in this space. Only specifications targeting constrained node networks are in scope. 6lo will work closely with the 6man working group, which will continue to work on IP-over-foo documents outside the constrained node network space and will continue to be the focal point for IPv6 maintenance. For adaptation layer specifications that do not have implications on IPv6 architecture, 6man will be notified about 6lo's working group last call. Specifications that might have such an impact (e.g., by using IPv6 addresses in a specific way or by introducing new ND options or by exposing to IPv6 a link model different from either Ethernet or 6lowpan) will be closely coordinated with 6man, and/or specific parts will be fanned out to 6man documents. Beyond 6man, 6lo will also coordinate with LWIG and INTAREA. 6lo works on small, focused pieces of work, but does not take on larger cross-layer efforts. The working group will continue to reuse existing protocols and mechanisms whenever reasonable and possible. Security and management work that is not specific to the link layers being worked on is out of scope. Work related to routing is out of scope. 6lo will coordinate closely with the working groups in other areas that focus on constrained node networks, such as ROLL (RTG) and CoRE (APP). Goals and Milestones: Done - WG decision on adoption for draft-bormann-6lo-ghc Done - WG decision on adoption for draft-brandt-6man-lowpanz Done - WG decision on adoption for draft-ietf-6man-6lobac Done - WG decision on adoption for draft-schoenw-6lo-lowpan-mib Done - WG decision on adoption of draft-mariager-6lowpan-v6over-dect-ule Done - WG LC for draft-ietf-6lo-btle Done - WG adoption call for draft-hong-6lo-ipv6-over-nfc Mar 2015 - WG LC for draft-ietf-6lo-dect-ule Mar 2015 - WG last call for draft-ietf-6lo-6lobac Apr 2015 - WG adoption call for 6lo security related draft Internet-Drafts: - Transmission of IPv6 over MS/TP Networks [draft-ietf-6lo-6lobac-01] (22 pages) - Transmission of IPv6 Packets over BLUETOOTH(R) Low Energy [draft-ietf-6lo-btle-10] (17 pages) - Transmission of IPv6 Packets over DECT Ultra Low Energy [draft-ietf-6lo-dect-ule-01] (16 pages) - 6LoWPAN-GHC: Generic Header Compression for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) [draft-ietf-6lo-ghc-05] (24 pages) - Definition of Managed Objects for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) [draft-ietf-6lo-lowpan-mib-04] (27 pages) - Transmission of IPv6 Packets over ITU-T G.9959 Networks [draft-ietf-6lo-lowpanz-08] (21 pages) - Transmission of IPv6 Packets over Near Field Communication [draft-ietf-6lo-nfc-00] (15 pages) Requests for Comments: RFC7388: Definition of Managed Objects for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) (27 pages) * Replaces DRAFT-SCHOENW-6LO-LOWPAN-MIB * Normative Reference RFC2578 * Normative Reference RFC2119 * Normative Reference RFC2580 * Informative Reference RFC3410 * Normative Reference RFC4944 * Informative Reference DRAFT-IETF-6LO-BTLE * Normative Reference BCP14 * Informative Reference RFC4443 * Possible Reference RFC5741 * Informative Reference RFC4113 * Informative Reference RFC2460 * Informative Reference RFC768 * Normative Reference STD58 * Informative Reference RFC4292 * Normative Reference RFC2863 * Informative Reference RFC7252 * Informative Reference RFC4293 * Normative Reference RFC2579 * Informative Reference DRAFT-VANDERSTOK-CORE-COMI RFC7400: 6LoWPAN-GHC: Generic Header Compression for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) (24 pages) * Normative Reference RFC2119 * Informative Reference RFC4821 * Normative Reference RFC6282 * Normative Reference RFC4944 * Normative Reference RFC6775 * Normative Reference BCP14 * Informative Reference RFC1951 * Informative Reference RFC5795 * Informative Reference RFC7228 * Informative Reference DRAFT-OFLYNN-6LOWPAN-ICMPHC * Normative Reference RFC4861 * Informative Reference RFC3095 * Informative Reference DRAFT-BORMANN-6LO-6LOWPAN-ROADMAP * Normative Reference RFC5226 * Replaces DRAFT-BORMANN-6LO-GHC * Normative Reference BCP26 * Informative Reference DRAFT-IETF-DICE-PROFILE * Normative Reference DRAFT-HE-IOT-SECURITY-BOOTSTRAPPING * Normative Reference DRAFT-THALER-6LO-PRIVACY-ADDRS * Normative Reference DRAFT-HE-6LO-ANALYSIS-IOT-SBOOTSTRAPPING RFC7428: Transmission of IPv6 Packets over ITU-T G.9959 Networks (21 pages) * Normative Reference RFC2119 * Informative Reference RFC3756 * Informative Reference RFC6282 * Normative Reference RFC4944 * Normative Reference RFC4861 * Normative Reference BCP14 * Informative Reference BCP89 * Informative Reference RFC6775 * Normative Reference DRAFT-IETF-6LO-GHC * Informative Reference RFC3315 * Informative Reference RFC3587 * Informative Reference RFC2460 * Informative Reference RFC3819 * Normative Reference RFC4193 * Normative Reference RFC4291 * Informative Reference RFC6550 * Informative Reference RFC6997 IPv6 over the TSCH mode of IEEE 802.15.4e (6tisch) -------------------------------------------------- Charter Last Modified: 2013-10-08 Current Status: Active Chairs: Pascal Thubert Thomas Watteyne Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Mailing Lists: General Discussion: 6tisch@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/6tisch Archive: http://www.ietf.org/mail-archive/web/6tisch Description of Working Group: 6TiSCH: "IPv6 over the TSCH mode of IEEE 802.15.4e". Background/Introduction: ------------------------ Low-power and Lossy Networks (LLNs) interconnect a possibly large number of resource-constrained nodes to form a wireless mesh network. The 6LoWPAN, ROLL and CoRE IETF Working Groups have defined protocols at various layers of the protocol stack, including an IPv6 adaptation layer, a routing protocol and a web transfer protocol. This protocol stack has been used with IEEE802.15.4 low-power radios. The IEEE802.15.4e Timeslotted Channel Hopping (TSCH) is a recent amendment to the Medium Access Control (MAC) portion of the IEEE802.15.4 standard. TSCH is the emerging standard for industrial automation and process control LLNs, with a direct inheritance from WirelessHART and ISA100.11a. Defining IPv6 over TSCH, 6TiSCH is a key to enable the further adoption of IPv6 in industrial standards and the convergence of Operational Technology (OT) with Information Technology (IT). The nodes in a IEEE802.15.4e TSCH network communicate by following a Time Division Multiple Access (TDMA) schedule. A timeslot in this schedule provides a unit of bandwidth that is allocated for communication between neighbor nodes. The allocation can be programmed such that the predictable transmission pattern matches the traffic. This avoids idle listening, and extends battery lifetime for constrained nodes. Channel-hopping improves reliability in the presence of narrow- band interference and multi-path fading. These techniques enable a new range of use cases for LLNs, including: - Control loops in a wireless process control network, in which high reliability and a fully deterministic behavior are required. - Service Provider networks transporting data from different independent clients, and for which an operator needs flow isolation and traffic shaping. - Networks comprising energy harvesting nodes, which require an extremely low and predictable average power consumption. IEEE802.15.4e only defines the link-layer mechanisms. It does not define how the network communication schedule is built and matched to the traffic requirements of the network. Description of Working Group: ----------------------------- The Working Group will focus on enabling IPv6 over the TSCH mode of the IEEE802.15.4e standard. The extent of the problem space for the WG is one or more LLNs, eventually federated through a common backbone link via one or more LLN Border Routers (LBRs). The WG will rely on, and if necessary extend, existing mechanisms for authenticating LBRs. Initially, the WG will limit its scope to distributed routing over a static schedule. In that case, a node's schedule can be either preconfigured, or learnt by a node when joining the network, but it remains unchanged after the node has joined a network. The Routing Protocol for LLNs (RPL) is used on the resulting network. The WG will interface with other appropriate groups in the IETF Internet, Operations and Management, Routing and Security areas. Work Items: ----------- The group will: 1. Produce "6TiSCH architecture" to describe the design of 6TiSCH networks. This document will highlight the different architectural blocks and signalling flows, including the operation of the network in the presence of multiple LBRs. Initially, the document will focus on distributed routing operation over a static TSCH schedule. 2. Produce an Information Model containing the management requirements of a 6TiSCH node. This includes describing how an entity can manage the TSCH schedule on a 6TiSCH node, and query timeslot information from that node. A data model mapping for an existing protocol (such as Concise Binary Object Representation (CBOR) over the Constrained Application Protocol (CoAP)) will be provided. 3. Produce "Minimal 6TiSCH Configuration" defining how to build a 6TiSCH network using the Routing Protocol for LLNs (RPL) and a static TSCH schedule. It is expected that RPL and the Objective Function 0 (OF0) will be reused as-is. The work will include a best practice configuration for RPL and OF0 operation over the static schedule. Based on that experience the group may produce a requirements draft for OF0 extensions, to be studied in ROLL. Non-milestone work items: ------------------------- The Working Group may maintain a number of running, often-respun documents, that evolve as the technology is refined for work items that do not affect the milestone work items: - implementers guide: this document will collect clarifying information based on input from implementers, in particular as it becomes available from interoperability events. This guide will contain information about test harnesses used for interoperability testing. - coexistence guide: this document will provide information on how 6TiSCH can be operated in an environment shared with other protocols that use the same or a similar TSCH MAC, and/or operate on the same frequency band. The WG will welcome requirements for dynamic timeslot operation, for example for centralized schedule computation. Goals and Milestones: Done - WG to adopt IEEE802.15.4e TSCH overview Done - WG to adopt 6TiSCH architecture Done - WG to adopt 6TiSCH minimal configuration Done - WG to adopt 6top draft(s) Done - WG to adopt 6TiSCH data model for CoAP Done - WG to adopt 6TiSCH terminology Done - Submit YANG data model in 6top draft for preliminary OPSDIR review Aug 2014 - Submit 6TiSCH architecture for preliminary SECDIR review Nov 2014 - Initial submission of 6TiSCH minimal configuration to the IESG Nov 2014 - Initial submission of 6top draft(s) to the IESG Nov 2014 - Initial submission of 6TiSCH data model for CoAP to the IESG Nov 2014 - Initial submission of 6TiSCH TSCH to the IESG Dec 2014 - Initial submission of 6TiSCH terminology to the IESG Dec 2014 - Initial submission of 6TiSCH architecture to the IESG Dec 2014 - Evaluate WG progress, propose new charter to the IESG Jun 2015 - 6TiSCH Minimal and 6top draft(s) in RFC publication queue Dec 2015 - 6TiSCH architecture and terminology in RFC publication queue Internet-Drafts: - 6TiSCH Operation Sublayer (6top) Interface [draft-ietf-6tisch-6top-interface-03] (39 pages) - An Architecture for IPv6 over the TSCH mode of IEEE 802.15.4e [draft-ietf-6tisch-architecture-06] (42 pages) - 6TiSCH Resource Management and Interaction using CoAP [draft-ietf-6tisch-coap-03] (16 pages) - Minimal 6TiSCH Configuration [draft-ietf-6tisch-minimal-06] (22 pages) - Terminology in IPv6 over the TSCH mode of IEEE 802.15.4e [draft-ietf-6tisch-terminology-03] (14 pages) - Using IEEE802.15.4e TSCH in an IoT context: Overview, Problem Statement and Goals [draft-ietf-6tisch-tsch-06] (21 pages) - 6TiSCH Resource Management and Interaction using CoAP [draft-sudhaakar-6tisch-coap-01] (14 pages) No Requests for Comments Layer Two Tunneling Protocol Extensions (l2tpext) ------------------------------------------------- Charter Last Modified: 2013-03-13 Current Status: Active Chairs: Ignacio Goyret Carlos Pignataro Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Mailing Lists: General Discussion: l2tpext@ietf.org To Subscribe: l2tpext-request@ietf.org Archive: http://www.ietf.org/mail-archive/web/l2tpext/ Description of Working Group: This group is responsible for extensions to the Layer 2 Tunneling Protocol. Examples of L2TP "extensions" include any changes to the L2TP encapsulation, control messages, or new AVPs sent in IETF standard control messages. I. L2TP Background: L2TP (RFC2661) provides a means for tunneling PPP over IP. Because PPP can effectivly carry any traffic (e.g., IP (RFC 1332), IPX (RFC 1552), etc.) it can effectively be used to tunnel arbitrary protocols over IP. L2TP provides: - An extensible control protocol for dynamic setup, maintenance, and teardown of multiple layer 2 tunnels between two logical endpoints. - An encapsulation method for tunneling PPP frames between each endpoint. This includes multiplexing of multiple, discrete, PPP streams between each endpoint. L2TP looks (in most ways) like just another point-to-point link to PPP and may thereby take advantage of the work done for any protocol defined for use over a traditional PPP WAN link. It should be noted, however, that the ability to dynamically establish a PPP connection between any two IP connected endpoints brings new applications and challenges of scale to existing PPP implementations and protocol definitions that must be considered. As high-speed broadband access to the home replaces traditional dialup infrastructure, L2TP has been utilized as one standard method for aggregation and delivery of PPP connections over packet networks. Thus, rather than a relatively small scale or low speed circuit-switched connection such as an analog modem or ISDN connection at the L2TP Access Concentrator (LAC), we see PPP being received over ATM PVCs which are generally higher speed and "always-on" vs. temporally connected. Further, there are non-IETF standard PPP tunneling protocols that have been developed and deployed, including PPPoE (RFC 2516) and the 3GPP2 Wireless GPRS Tunneling Protocol Standard (http://www.3gpp.org) that interface with L2TP at various points in the network. While it is unfortunate that there is more than one standard method for tunneling PPP defined, each of these have their own installed bases and specific application-driven nuances. Proper integration with these various tunneling methods as they "hand-off" to the L2TP portion of the network must be ensured. II. L2TP Interaction with PWE3 for Pseudo-Wire Transport: In addition to tunneling PPP, L2TPEXT will develop protocol extensions necessary for the tunneling of specific "pseudo-wires" as defined in the PWE3 WG. Specific milestone identification for this activity is currently subject to ongoing work and results from PWE3. III. WG Activities The Working Group is currently focussed on the following activities: - RFC2661 bundles data transport, protocol signaling, and PPP emulation methods into a single document. This working group will separate RFC2661 into stand-alone documents for greater modularity. This will consist of a base L2TP document defining common tunneling constructs and encapsulation, and a PPP document defining the use of these constructs for tunneling of PPP sessions as defined in RFC2661. Documents for tunneling of pseudo-wires defined in PWE3 will be forthcoming as well. As RFC2661 is rewritten to separate the tunnel setup and maintenance sections for support of new applications and increased modularity, some modifications to the base protocol may be necessary. This includes addition of a Pseudo Wire AVP to identify the pseudo wire being carried (with PPP identified as 0). In all cases, these will follow the extensible models offered in the L2TP base protocol design, with as much attention to backwards compatibility as possible given the new requirements. In addition to its broader scope, L2TPEXT has ongoing work to complete from its inception as a tunneling protocol for PPP only. While RFC2661 will ultimately be made obsolete by a new L2TP base specification and companion PPP over L2TP specification, documents based on RFC2661 which do not require this new degree of modularity will still be published in the near term. These include: - Identification of specific parameters and modes of IPsec in order to aid interoperability when IPsec is used to secure L2TP traffic. - An L2TP MIB for network management. - An L2TP Differentiated Services Extension to negotiate DSCP parameters to be set for packets associated with a given L2TP tunnel, sessions within a tunnel, or L2TP control traffic which may need differentiated QoS settings. - Extensions to L2TP for additional or more robust control information for informational or operational purposes as deemed necessary based on operational experience. These include better transfer of L2TP PPP LCP Information between tunnel endpoints when such state needs to be shared, PPP Disconnect codes within L2TP control messages for better debugging, and L2TP session information for enhanced logging, billing, and error reporting. - Standard methods for operation over such packet networks such as Frame Relay and AAL5. - L2TP defines a base encapsulation for operation in typical environments for tunneling PPP at the time RFC2661 was being developed. In cases where bandwidth cost is at a premium, the size of the L2TP header becomes more significant. L2TP will define a compressed version of the L2TP header for these environments that takes advantage of the L2TP control plane to establish operational parameters allowing removal of information from individual packets. Goals and Milestones: Done - Submit L2TP over Frame Relay to IESG for consideration as a Proposed Standard Done - Submit L2TP Security to IESG for consideration as a Proposed Standard Done - Submit L2TP PPP Disconnect Information to IESG for consideration as a Proposed Standard Done - Submit L2TP ATM extensions to IESG for consideration as a Proposed Standard Done - Submit L2TP MIB to IESG for consideration as a Proposed Standard Done - Submit L2TP Link Information to IESG for consideration as a Proposed Standard Done - Submit L2TP Session Info to IESG for consideration as a Proposed Standard Done - Submit L2TP Differentiated Services to IESG for consideration as a Proposed Standard Done - Submit L2TP over AAL5 to IESG for consideration as a Proposed Standard Done - Submit initial Internet-Draft of L2TP Base Specification Done - Submit initial Internet-Draft of PPP over L2TP Done - Submit final Internet-Draft of L2TPv3 Base Specification to IESG Done - Submit Internet-Draft of HDLC over L2TPv3 to IESG Done - Submit Internet-Draft of Frame Relay over L2TPv3 to IESG Done - Submit L2VPN Extensions for L2TP to IESG Done - Submit Internet-Draft of Ethernet over L2TPv3 to IESG Done - WG Last Call on L2TP Failover Mar 2008 - Submit Internet-Draft of PPP over L2TPv3 to IESG Done - WG Last Call on TDM over L2TPv3 Jun 2008 - WG Last Call on IP over L2TPv3 Internet-Drafts: - Layer 2 Tunneling Protocol (L2TP) Active Discovery Relay for PPP over Ethernet (PPPoE) [draft-dasilva-l2tp-relaysvc-08] (17 pages) - Layer Two Tunneling Protocol - Setup of TDM Pseudowires [draft-ieft-l2tpext-tdm-03] (8 pages) - L2TP Alternate Data Channel ('ADC') [draft-ietf-l2tpext-adc-00] (4 pages) - Layer Two Tunnelling Protocol (L2TP): ATM access network extensions [draft-ietf-l2tpext-atmext-04] (19 pages) - Layer Two Tunneling Protocol : ATM Access Network Extensions [draft-ietf-l2tpext-atmext-rfc3301-bis-00] (18 pages) - Layer 2 Tunneling Protocol Version 3 (L2TPv3) Extended Circuit Status Values [draft-ietf-l2tpext-circuit-status-extensions-05] (11 pages) - Layer Two Tunneling Protocol (L2TP) Differentiated Services Extension [draft-ietf-l2tpext-ds-05] (10 pages) - Ethernet Service Type for Layer Two Tunneling Protocol [draft-ietf-l2tpext-eth-00] (6 pages) - Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover" [draft-ietf-l2tpext-failover-12] (26 pages) - Layer Two Tunneling Protocol (L2TP) over Frame Relay [draft-ietf-l2tpext-fr-01] (7 pages) - Keyed IPv6 Tunnel [draft-ietf-l2tpext-keyed-ipv6-tunnel-04] (11 pages) - Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5) [draft-ietf-l2tpext-l2tp-atm-03] (13 pages) - Layer Two Tunneling Protocol - Version 3 (L2TPv3) [draft-ietf-l2tpext-l2tp-base-15] (94 pages) - Layer Two Tunneling Protocol "L2TP" Management Information Base [draft-ietf-l2tpext-l2tp-mib-04] (70 pages) - PPP Tunneling Using Layer Two Tunneling Protocol Version 3 (L2TPv3) [draft-ietf-l2tpext-l2tp-ppp-08] (44 pages) - Layer Two Tunneling Protocol 'L2TP' [draft-ietf-l2tpext-l2tpbis-01] (77 pages) - L2TP Header Compression ('L2TPHC') [draft-ietf-l2tpext-l2tphc-06] (7 pages) - Layer Two Tunneling Protocol (Version 3) "L2TPv3" Management Information Base [draft-ietf-l2tpext-l2tpmib-base-02] (55 pages) - Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP) [draft-ietf-l2tpext-l2vpn-07] (15 pages) - Layer-Two Tunneling Protocol Extensions for PPP Link Control Protocol Negotiation [draft-ietf-l2tpext-link-07] (10 pages) - Extensions to Support Efficient Carrying of Multicast Traffic in Layer-2 Tunneling Protocol (L2TP) [draft-ietf-l2tpext-mcast-05] (28 pages) - Layer Two Tunneling Protocol 'L2TP' Multi-Protocol Label Switching Extension [draft-ietf-l2tpext-mpls-00] (5 pages) - L2TP Disconnect Cause Information [draft-ietf-l2tpext-ppp-discinfo-04] (10 pages) - L2TP Proxy Authenticate Extensions for EAP [draft-ietf-l2tpext-proxy-authen-ext-eap-02] (11 pages) - Asynchronous Transfer Mode (ATM) over Layer 2 Tunneling Protocol Version 3 (L2TPv3) [draft-ietf-l2tpext-pwe3-atm-04] (26 pages) - Transport of Ethernet Frames over Layer 2 Tunneling Protocol Version 3 (L2TPv3) [draft-ietf-l2tpext-pwe3-ethernet-09] (14 pages) - Frame Relay over Layer 2 Tunneling Protocol Version 3 (L2TPv3) [draft-ietf-l2tpext-pwe3-fr-07] (14 pages) - High-Level Data Link Control (HDLC) Frames over Layer 2 Tunneling Protocol, Version 3 (L2TPv3) [draft-ietf-l2tpext-pwe3-hdlc-07] (11 pages) - Signaling and Encapsulation for the Transport of IP over L2TPv3 [draft-ietf-l2tpext-pwe3-ip-05] (20 pages) - RADIUS & L2TP Extended NAS-Port AVPs [draft-ietf-l2tpext-radius-ext-nas-port-02] (14 pages) - Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers Authority (IANA) Considerations Update [draft-ietf-l2tpext-rfc2661-iana-01] (5 pages) - Securing L2TP using IPsec [draft-ietf-l2tpext-security-08] (28 pages) - L2TP Session Information (``SESINFO'') [draft-ietf-l2tpext-sesinfo-04] (4 pages) - L2TP Service Type [draft-ietf-l2tpext-svctype-01] (7 pages) - Layer Two Tunneling Protocol version 3 - Setup of Time-Division Multiplexing (TDM) Pseudowires [draft-ietf-l2tpext-tdm-07] (11 pages) - PPP over L2TP Tunnel Switching [draft-ietf-l2tpext-tunnel-switching-08] (16 pages) - Signalling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP) [draft-ietf-l2tpext-v92-moh-05] (13 pages) - L2TP Over AAL5 and FUNI [draft-ietf-pppext-l2tp-atm-02] (11 pages) - Layer Two Tunnelling Protocol : ATM access network extensions. [draft-ietf-pppext-l2tp-atmext-01] (14 pages) - Layer Two Tunneling Protocol ''L2TP'' IP Differential Services Extension [draft-ietf-pppext-l2tp-ds-03] (5 pages) - Layer Two Tunneling Protocol (L2TP) over Frame Relay [draft-ietf-pppext-l2tp-fr-02] (7 pages) - Layer Two Tunneling Protocol 'L2TP' Management Information Base [draft-ietf-pppext-l2tp-mib-05] (68 pages) - Layer Two Tunneling Protocol ''L2TP'' Multi-Protocol Label Switching Extension [draft-ietf-pppext-l2tp-mpls-02] (5 pages) - Securing L2TP using IPSEC [draft-ietf-pppext-l2tp-security-05] (14 pages) Requests for Comments: BCP68: Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers Authority (IANA) Considerations Update (5 pages) * Normative Reference RFC2661 * Normative Reference BCP14 * Normative Reference RFC2434 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC4045 * Normative Reference RFC3931 * Informative Reference DRAFT-IETF-L2TPEXT-L2TP-PPP * Informative Reference DRAFT-IETF-L2TPEXT-TUNNEL-SWITCHING * Informative Reference RFC4591 * Informative Reference RFC4349 * Informative Reference RFC4623 * Informative Reference RFC5085 * Normative Reference RFC6074 * Normative Reference RFC4720 * Informative Reference RFC4454 * Informative Reference DRAFT-MARTINI-PWE3-PW-SWITCHING * Informative Reference DRAFT-KLENSIN-IANA-REG-POLICY * Informative Reference RFC6073 * Informative Reference DRAFT-KELKAR-L2TPEXT-EAP-PROXY-AUTHEN-EXT * Informative Reference DRAFT-PIGNATARO-L2TPEXT-PWE3-IPL2 * Informative Reference DRAFT-IETF-L2TPEXT-PWE3-IP * Normative Reference RFC5515 * Normative Reference DRAFT-GP-L2TPEXT-SBFD-DISCRIMINATOR RFC3070: Layer Two Tunneling Protocol (L2TP) over Frame Relay (7 pages) * Reference RFC1490 * Reference RFC2868 * Reference RFC2661 * Reference BCP14 * Possible Reference STD1 * Possible Reference RFC2119 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Informative Reference RFC3931 * Reference DRAFT-TOWNSLEY-PWE3-L2TPV3 * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 * Informative Reference RFC6328 RFC3145: L2TP Disconnect Cause Information (10 pages) * Reference BCP11 * Reference RFC2279 * Possible Reference STD1 * Reference BCP14 * Reference RFC2661 * Possible Reference DRAFT-IETF-NGTRANS-IPV4SURVEY * Normative Reference DRAFT-IETF-L2TPEXT-TUNNEL-SWITCHING * Possible Reference DRAFT-IETF-V6OPS-IPV4SURVEY * Possible Reference RFC3790 RFC3193: Securing L2TP using IPsec (28 pages) * Reference STD51 * Reference RFC1968 * Reference RFC2284 * Reference RFC1994 * Reference RFC1969 * Possible Reference STD1 * Reference RFC1962 * Reference RFC2661 * Reference RFC2420 * Reference BCP11 * Reference RFC2409 * Reference RFC2419 * Reference BCP14 * Reference RFC2246 * Reference RFC2373 * Reference RFC2402 * Reference RFC2401 * Reference RFC2406 * Reference RFC2407 * Reference DRAFT-IETF-L2TPEXT-SESINFO * Informative Reference RFC3715 * Informative Reference RFC3948 * Informative Reference RFC3817 * Normative Reference RFC3931 * Informative Reference DRAFT-IETF-L2TPEXT-TUNNEL-SWITCHING * Reference DRAFT-ADRANGI-MOBILEIP-VPN-TRAVERSAL * Reference DRAFT-ELWIN-PPVPN-L2TP-ARCH * Possible Reference DRAFT-IETF-IPSEC-SONOFIKE-RQTS * Possible Reference DRAFT-TOWNSLEY-PWE3-L2TPV3 * Normative Reference DRAFT-LEE-CE-BASED-VPL * Normative Reference DRAFT-PUTHENKULAM-EAP-BINDING * Normative Reference DRAFT-LEE-L2TPEXT-PWE3-VPL * Informative Reference RFC5102 * Informative Reference RFC4891 * Informative Reference DRAFT-YAMAMOTO-V6TC-SECURITY-CONSIDERATIONS * Informative Reference DRAFT-KELKAR-L2TPEXT-EAP-PROXY-AUTHEN-EXT * Informative Reference DRAFT-IETF-L2TPEXT-PROXY-AUTHEN-EXT-EAP * Normative Reference RFC5571 * Informative Reference RFC5619 * Informative Reference RFC5515 * Normative Reference DRAFT-MA-SOFTWIRE-IPSEC-GRE-DEMULTIPLEXING-PS * Informative Reference DRAFT-D-SEC-UDT * Informative Reference DRAFT-CLAISE-IPFIX-INFORMATION-MODEL-RFC5102BIS * Normative Reference DRAFT-JANOG-SOFTWIRE-REPORT RFC3301: Layer Two Tunnelling Protocol (L2TP): ATM access network extensions (19 pages) * Reference BCP14 * Reference RFC2364 * Possible Reference STD1 * Reference RFC2119 * Reference RFC2661 * Normative Reference DRAFT-IETF-L2TPEXT-L2TP-PPP * Normative Reference DRAFT-IETF-L2TPEXT-TUNNEL-SWITCHING RFC3308: Layer Two Tunneling Protocol (L2TP) Differentiated Services Extension (10 pages) * Reference RFC1661 * Reference RFC2983 * Possible Reference STD1 * Reference RFC2475 * Reference RFC2474 * Reference RFC2661 * Reference BCP14 * Reference RFC3140 * Reference RFC2119 * Normative Reference DRAFT-IETF-L2TPEXT-TUNNEL-SWITCHING * Informative Reference DRAFT-AUGUSTYN-PPVPN-L2VPN-REQUIREMENTS * Reference DRAFT-CHIUSSI-PPVPN-QOS-FRAMEWORK * Informative Reference DRAFT-LEE-CE-BASED-VPL * Informative Reference RFC4665 * Normative Reference RFC5049 * Normative Reference DRAFT-GAOYANG-MMUSIC-CLASSIFICATION-OF-SDP RFC3355: Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5) (13 pages) * Reference STD51 * Reference RFC1661 * Possible Reference RFC3337 * Reference RFC2661 * Possible Reference RFC2364 * Reference BCP14 * Reference RFC2331 * Reference RFC2684 * Possible Reference STD1 * Reference RFC2119 * Informative Reference RFC3931 RFC3371: Layer Two Tunneling Protocol "L2TP" Management Information Base (70 pages) * Reference RFC2579 * Reference RFC2580 * Reference RFC2863 * Reference STD58 * Reference RFC2574 * Reference RFC2575 * Reference RFC2572 * Reference RFC2573 * Reference RFC2570 * Reference RFC2571 * Reference RFC1157 * Reference STD16 * Reference RFC2578 * Reference RFC1215 * Reference RFC2667 * Reference RFC2661 * Reference RFC1155 * Possible Reference STD1 * Possible Reference RFC2119 * Reference RFC1212 * Reference RFC1906 * Reference RFC1905 * Reference RFC1901 * Reference RFC2401 * Informative Reference RFC4951 * Reference DRAFT-RAJINI-L2TPEXT-ML2TP * Possible Reference DRAFT-CAO-SIP-RESPONSE-AUTH * Possible Reference DRAFT-CAO-SIP-RESPONSE-IDENTITY * Normative Reference RFC5571 * Normative Reference DRAFT-CAI-SOFTWIRE-6RD-MIB RFC3437: Layer-Two Tunneling Protocol Extensions for PPP Link Control Protocol Negotiation (10 pages) * Normative Reference BCP14 * Normative Reference RFC1661 * Normative Reference RFC2661 * Normative Reference RFC2119 * Informative Reference DRAFT-IETF-L2TPEXT-L2TP-PPP * Normative Reference DRAFT-IETF-L2TPEXT-TUNNEL-SWITCHING RFC3438: Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers Authority (IANA) Considerations Update (5 pages) * Normative Reference RFC2661 * Normative Reference BCP14 * Normative Reference RFC2434 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC4045 * Normative Reference RFC3931 * Informative Reference DRAFT-IETF-L2TPEXT-L2TP-PPP * Informative Reference DRAFT-IETF-L2TPEXT-TUNNEL-SWITCHING * Informative Reference RFC4591 * Informative Reference RFC5085 * Normative Reference RFC6074 * Normative Reference RFC4720 * Informative Reference DRAFT-MARTINI-PWE3-PW-SWITCHING * Informative Reference DRAFT-KLENSIN-IANA-REG-POLICY * Informative Reference RFC6073 * Informative Reference DRAFT-KELKAR-L2TPEXT-EAP-PROXY-AUTHEN-EXT * Informative Reference DRAFT-PIGNATARO-L2TPEXT-PWE3-IPL2 * Informative Reference DRAFT-IETF-L2TPEXT-PWE3-IP * Normative Reference RFC5515 * Normative Reference DRAFT-GP-L2TPEXT-SBFD-DISCRIMINATOR RFC3573: Signalling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP) (13 pages) * Informative Reference STD51 * Informative Reference BCP9 * Informative Reference RFC1661 * Normative Reference RFC2661 * Normative Reference BCP14 * Normative Reference BCP26 RFC3817: Layer 2 Tunneling Protocol (L2TP) Active Discovery Relay for PPP over Ethernet (PPPoE) (17 pages) * Normative Reference STD51 * Informative Reference BCP78 * Informative Reference RFC3193 * Normative Reference RFC2661 * Normative Reference BCP14 * Normative Reference RFC2516 * Possible Reference RFC2119 * Normative Reference BCP26 RFC3931: Layer Two Tunneling Protocol - Version 3 (L2TPv3) (94 pages) * Normative Reference RFC3629 * Informative Reference RFC2890 * Informative Reference RFC3355 * Informative Reference RFC2732 * Normative Reference RFC3193 * Informative Reference RFC2341 * Informative Reference RFC2104 * Normative Reference BCP14 * Normative Reference BCP18 * Informative Reference RFC2581 * Informative Reference RFC1958 * Informative Reference RFC1700 * Informative Reference RFC1661 * Informative Reference BCP78 * Normative Reference RFC2865 * Normative Reference BCP68 * Informative Reference RFC2809 * Informative Reference RFC1034 * Normative Reference RFC2434 * Normative Reference RFC3438 * Normative Reference RFC2277 * Informative Reference STD13 * Informative Reference RFC1981 * Normative Reference RFC2473 * Informative Reference RFC1321 * Informative Reference RFC1191 * Informative Reference RFC2072 * Informative Reference RFC2661 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC3066 * Informative Reference RFC3070 * Normative Reference BCP47 * Normative Reference STD63 * Informative Reference RFC2637 * Informative Reference RFC2401 * Informative Reference RFC1750 * Updates RFC5641 * Informative Reference DRAFT-YONG-TSVWG-GRE-IN-UDP-ENCAP * Normative Reference RFC4170 * Normative Reference RFC5087 * Normative Reference RFC4951 * Informative Reference DRAFT-IETF-L2TPEXT-L2TP-PPP * Informative Reference DRAFT-IETF-L3VPN-CE-BASED * Normative Reference DRAFT-IETF-L2TPEXT-TUNNEL-SWITCHING * Informative Reference RFC5470 * Normative Reference RFC4591 * Normative Reference RFC5601 * Normative Reference RFC4349 * Informative Reference RFC4448 * Normative Reference RFC3985 * Normative Reference RFC4623 * Normative Reference RFC4719 * Informative Reference DRAFT-IETF-L2TPEXT-RADIUS-EXT-NAS-PORT * Normative Reference RFC5085 * Normative Reference RFC6074 * Normative Reference RFC4553 * Normative Reference RFC4720 * Normative Reference RFC4667 * Normative Reference DRAFT-IEFT-L2TPEXT-TDM * Reference DRAFT-AISSAOUI-L2VPN-VPWS-IW-OAM * Informative Reference DRAFT-IETF-L2VPN-VPWS-IW-OAM * Informative Reference RFC5086 * Normative Reference RFC4454 * Informative Reference DRAFT-BRYANT-IPFRR-TUNNELS * Normative Reference RFC4459 * Normative Reference DRAFT-MARTINI-PWE3-PW-SWITCHING * Normative Reference RFC4779 * Informative Reference RFC6310 * Normative Reference DRAFT-TOWNSLEY-MPLS-OVER-L2TPV3 * Normative Reference RFC5611 * Normative Reference RFC4817 * Informative Reference DRAFT-BRYANT-SHAND-IPFRR-NOTVIA-ADDRESSES * Informative Reference RFC6981 * Normative Reference RFC6073 * Normative Reference DRAFT-PIGNATARO-L2TPEXT-PWE3-IPL2 * Normative Reference DRAFT-IETF-L2TPEXT-PWE3-IP * Informative Reference DRAFT-TEMPLIN-MTUASSURANCE * Informative Reference DRAFT-SAITO-MMUSIC-SDES-IPSEC * Informative Reference RFC5571 * Normative Reference DRAFT-WU-SOFTWIRE-MESH-FRAMEWORK * Normative Reference RFC5565 * Normative Reference DRAFT-ASATI-BGP-MPLS-BLACKHOLE-AVOIDANCE * Normative Reference RFC5515 * Informative Reference RFC6169 * Informative Reference RFC5885 * Informative Reference DRAFT-BERGER-IDR-ENCAPS-IPSEC * Normative Reference RFC5512 * Normative Reference DRAFT-NMCGILL-L2TPEXT-CIRCUIT-STATUS-EXTENSIONS * Normative Reference RFC5641 * Normative Reference DRAFT-METZ-SOFTWIRES-MULTICAST-PROBLEM-STATEMENT * Informative Reference RFC5566 * Normative Reference DRAFT-PMOHAPAT-SOFTWIRE-LB * Normative Reference RFC5640 * Informative Reference DRAFT-TOUCH-INTAREA-TUNNELS * Informative Reference DRAFT-IETF-INTAREA-TUNNELS * Informative Reference DRAFT-YOKOTA-NETLMM-PMIPV6-MN-ITHO-SUPPORT * Normative Reference DRAFT-GEIB-IPPM-METRICTEST * Informative Reference RFC6361 * Informative Reference DRAFT-MELIA-NETEXT-LOGICAL-INTERFACE-SUPPORT * Normative Reference RFC6576 * Informative Reference DRAFT-FARREL-MPLS-TP-MIB-MANAGEMENT-OVERVIEW * Informative Reference RFC6639 * Informative Reference RFC7155 * Informative Reference DRAFT-TIAN-V4V6TRAN-BROADBAND-SP-USECASE * Informative Reference DRAFT-HUANG-V6OPS-V4V6TRAN-BB-USECASE * Informative Reference DRAFT-ZORN-EMU-TEAM * Informative Reference DRAFT-ZUNIGA-MIF-LIF-IMPLEMENTATION-GUIDELINES * Normative Reference DRAFT-NADEAU-PWE3-VCCV-2 * Informative Reference DRAFT-MORTON-IPPM-TESTPLAN-RFC2679 * Normative Reference DRAFT-BASHANDY-BGP-EDGE-NODE-FRR * Informative Reference DRAFT-MORTON-IPPM-TESTPLAN-RFC2680 * Informative Reference RFC6808 * Normative Reference DRAFT-IETF-PWE3-VCCV-FOR-GAL * Normative Reference DRAFT-SALDANA-TSVWG-TCMTF * Informative Reference DRAFT-DAVIE-STT * Normative Reference DRAFT-MKONSTAN-L2TPEXT-KEYED-IPV6-TUNNEL * Normative Reference DRAFT-BASHANDY-BGP-FRR-VECTOR-LABEL * Informative Reference RFC7290 * Informative Reference RFC7364 * Informative Reference RFC7298 * Normative Reference DRAFT-BASHANDY-BGP-FRR-MIRROR-TABLE * Informative Reference DRAFT-MORTON-IPPM-2679-BIS * Informative Reference DRAFT-MORTON-IPPM-2680-BIS * Informative Reference DRAFT-XU-SOFTWIRE-ENCAPS-UDP * Normative Reference DRAFT-YONG-TSVWG-UDP-ENCAP-4-IP-TUNNELING * Normative Reference DRAFT-MKONSTAN-KEYED-IPV6-TUNNEL * Possible Reference DRAFT-FAN-L2TP-VP * Informative Reference DRAFT-IETF-TSVWG-GRE-IN-UDP-ENCAP * Informative Reference DRAFT-RIJSMAN-SFC-METADATA-CONSIDERATIONS * Normative Reference DRAFT-IETF-OPSAWG-CAPWAP-ALT-TUNNEL * Normative Reference DRAFT-XUE-OPSAWG-CAPWAP-ALT-TUNNEL-INFORMATION * Normative Reference DRAFT-SHEN-L2TPEXT-L2TPV3-YANG-MODEL * Normative Reference DRAFT-HY-NVO3-GUE-4-NVO * Normative Reference DRAFT-HY-GUE-4-SECURE-TRANSPORT * Informative Reference DRAFT-XU-SOFTWIRE-IP-IN-UDP * Informative Reference RFC7424 * Informative Reference DRAFT-XU-BESS-ENCAPS-UDP * Normative Reference DRAFT-GP-L2TPEXT-SBFD-DISCRIMINATOR * Normative Reference DRAFT-IETF-L2TPEXT-KEYED-IPV6-TUNNEL * Normative Reference DRAFT-VANDEVELDE-IDR-REMOTE-NEXT-HOP * Informative Reference DRAFT-SUN-L2TPEXT-KEYED-V6-TUNNEL-YANG * Normative Reference DRAFT-RTG-DT-ENCAP RFC4045: Extensions to Support Efficient Carrying of Multicast Traffic in Layer-2 Tunneling Protocol (L2TP) (28 pages) * Normative Reference RFC3376 * Normative Reference RFC1661 * Informative Reference BCP78 * Normative Reference RFC1112 * Normative Reference RFC2710 * Normative Reference RFC2236 * Normative Reference BCP14 * Normative Reference RFC3438 * Normative Reference RFC2661 * Normative Reference BCP68 * Normative Reference RFC2119 * Normative Reference RFC3810 * Normative Reference RFC3590 * Informative Reference RFC4834 RFC4349: High-Level Data Link Control (HDLC) Frames over Layer 2 Tunneling Protocol, Version 3 (L2TPv3) (11 pages) * Informative Reference BCP78 * Normative Reference RFC3931 * Normative Reference BCP14 * Informative Reference BCP68 * Normative Reference RFC2119 * Updates RFC5641 * Normative Reference RFC4591 * Normative Reference RFC4720 * Normative Reference RFC5641 RFC4454: Asynchronous Transfer Mode (ATM) over Layer 2 Tunneling Protocol Version 3 (L2TPv3) (26 pages) * Informative Reference BCP78 * Normative Reference RFC3931 * Informative Reference BCP68 * Informative Reference RFC3985 * Informative Reference RFC2434 * Informative Reference RFC2914 * Informative Reference RFC2684 * Possible Reference STD1 * Normative Reference RFC2119 * Informative Reference BCP26 * Normative Reference BCP14 * Updates RFC5641 * Informative Reference RFC5085 * Informative Reference RFC6310 * Informative Reference RFC6073 * Normative Reference RFC5641 * Informative Reference RFC7276 RFC4591: Frame Relay over Layer 2 Tunneling Protocol Version 3 (L2TPv3) (14 pages) * Informative Reference BCP78 * Normative Reference RFC3931 * Normative Reference RFC4349 * Informative Reference BCP68 * Normative Reference BCP14 * Informative Reference RFC3438 * Possible Reference STD1 * Normative Reference RFC2119 * Updates RFC5641 * Normative Reference RFC4720 * Normative Reference RFC6310 * Informative Reference DRAFT-NMCGILL-L2TPEXT-CIRCUIT-STATUS-EXTENSIONS * Normative Reference RFC5641 RFC4667: Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP) (15 pages) * Informative Reference BCP78 * Normative Reference RFC3931 * Informative Reference RFC2661 * Normative Reference BCP14 * Informative Reference BCP116 * Informative Reference RFC4664 * Normative Reference RFC2119 * Normative Reference RFC6074 * Informative Reference RFC6073 * Informative Reference DRAFT-IETF-L2TPEXT-PWE3-IP * Normative Reference DRAFT-STOKES-VKOMPELLA-L2VPN-VPLS-OAM RFC4719: Transport of Ethernet Frames over Layer 2 Tunneling Protocol Version 3 (L2TPv3) (14 pages) * Informative Reference RFC3448 * Informative Reference BCP78 * Normative Reference RFC3931 * Informative Reference RFC2474 * Normative Reference RFC2119 * Informative Reference RFC3985 * Normative Reference RFC4623 * Informative Reference RFC2914 * Possible Reference STD1 * Normative Reference BCP14 * Updates RFC5641 * Normative Reference RFC4720 * Normative Reference RFC5641 * Normative Reference DRAFT-WU-MIP4-ETHER * Normative Reference RFC6576 * Informative Reference DRAFT-BITAR-DATACENTER-VPN-APPLICABILITY * Normative Reference DRAFT-MKONSTAN-L2TPEXT-KEYED-IPV6-TUNNEL * Informative Reference DRAFT-BITAR-NVO3-VPN-APPLICABILITY * Normative Reference DRAFT-MKONSTAN-KEYED-IPV6-TUNNEL * Normative Reference DRAFT-IETF-L2TPEXT-KEYED-IPV6-TUNNEL RFC4951: Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover" (26 pages) * Replaces DRAFT-VIPIN-L2TPEXT-FAILOVER * Informative Reference BCP78 * Normative Reference RFC3931 * Informative Reference RFC3371 * Normative Reference RFC2661 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference RFC5515 RFC5611: Layer Two Tunneling Protocol version 3 - Setup of Time-Division Multiplexing (TDM) Pseudowires (11 pages) * Replaces DRAFT-IEFT-L2TPEXT-TDM * Informative Reference RFC5226 * Normative Reference RFC3931 * Normative Reference RFC2119 * Possible Reference STD1 * Normative Reference RFC5086 * Informative Reference BCP26 * Normative Reference BCP14 * Informative Reference RFC4446 * Informative Reference BCP116 * Informative Reference RFC5087 * Normative Reference RFC4553 * Informative Reference RFC5287 RFC5641: Layer 2 Tunneling Protocol Version 3 (L2TPv3) Extended Circuit Status Values (11 pages) * Replaces DRAFT-NMCGILL-L2TPEXT-CIRCUIT-STATUS-EXTENSIONS * Updates RFC3931 * Updates RFC4349 * Updates RFC4454 * Updates RFC4591 * Updates RFC4719 * Normative Reference RFC3931 * Normative Reference RFC4349 * Informative Reference RFC4447 * Normative Reference RFC4719 * Normative Reference BCP14 * Informative Reference RFC4446 * Normative Reference RFC4454 * Informative Reference BCP116 * Normative Reference RFC4591 * Possible Reference STD1 * Normative Reference RFC2119 * Informative Reference RFC5085 * Normative Reference RFC6310 * Normative Reference RFC6073 * Informative Reference RFC7276 * Normative Reference DRAFT-MITY-NVO3-USE-CASE * Normative Reference DRAFT-HY-NVO3-VPN-PROTOCOL-GAP-ANALYSIS Light-Weight Implementation Guidance (lwig) ------------------------------------------- Charter Last Modified: 2014-08-19 Current Status: Active Chairs: Zhen Cao Robert Cragie Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Brian Haberman Mailing Lists: General Discussion: lwip@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/lwip Archive: http://www.ietf.org/mail-archive/web/lwip Description of Working Group: Communications technology is being embedded into our environment. Different types of devices in our buildings, vehicles, equipment and other objects have a need to communicate. It is expected that most of these devices will employ the Internet Protocol suite. However, there is a lot of variation in the capabilities between different types of devices, and it is not always easy to embed all the necessary features. The Light-Weight Implementation Guidance (LWIG) Working Group focuses on helping the implementors of the smallest devices. The goal is to be able to build minimal yet interoperable IP-capable devices for the most constrained environments. Building a small implementation does not have to be hard. Many small devices use stripped down versions of general purpose operating systems and their TCP/IP stacks. However, there are implementations that go even further in minimization and can exist in as few as a couple of kilobytes of code, as on some devices this level of optimization is necessary. Technical and cost considerations may limit the computing power, battery capacity, available memory, or communications bandwidth that can be provided. To overcome these limitations the implementors have to employ the right hardware and software mechanisms. For instance, certain types of memory management or even fixed memory allocation may be required. It is also useful to understand what is necessary from the point of view of the communications protocols and the application employing them. For instance, a device that only acts as a client or only requires one connection can simplify its TCP implementation. The purpose of the LWIG working group is to collect experiences from implementors of IP stacks in constrained devices. The group shall focus only on techniques that have been used in actual implementations and do not impact interoperability with other devices. The techniques shall also not affect conformance to the relevant specifications. The output of this work is a document that describes implementation techniques for reducing complexity, memory footprint, or power usage. The topics for this working group will be chosen from these protocols: IPv4, IPv6, UDP, TCP, ICMPv4/v6, MLD/IGMP, ND, DNS, DHCPv4/v6, IPsec, 6LOWPAN, COAP, RPL, SNMP and NETCONF protocols. This document will be helpful for the implementors of new devices or for the implementors of new general-purpose small IP stacks. It is also expected that the document increases our knowledge of what existing small implementations do, and helps in the further optimization of the existing implementations. On areas where the considerations for small implementations have already been documented the group shall make an effort to refer to those documents instead of developing its own. Generic hardware design advice and software implementation techniques are outside the scope of this work, as such expertise is not within the IETF domain. Protocol implementation experience, however, is within the IETF domain. The group shall also not develop any new protocols or protocol behavior modifications beyond what is already allowed by existing RFCs, because it is important to ensure that different types of devices can work together. The group shall not develop assumptions or profiles about the operating environment of the devices, because, in general, it is not possible to guarantee any special configuration. Finally, while implementation techniques relating to security mechanisms are within scope, mere removal of security functionality from a protocol is not an acceptable recommendation. Given that the group works on both IP and transport layer protocols it is necessary to ensure that expertise in both aspects is present in the group. Participation from the implementors of existing small IP stacks is also required. Goals and Milestones: Done - First version of the implementation guidance document submitted Done - First version of the terminology document submitted Done - Minimal TLS document summited Done - Minimal IKEv2 document summited Mar 2013 - Submit the terminology document to the IESG for publication as an Informational RFC Jul 2013 - Submit the implementation guidance document to the IESG for publication as an Informational RFC Nov 2013 - First version of the energy efficient implementation guidance document submitted Mar 2014 - Submit the minimal IKEv2 implementation document to the IESG for publication as an Informational RFC Mar 2014 - Submit the minimal TLS implementation document to the IESG for publication as an Informational RFC Nov 2014 - Submit the energy efficient implementation guidance document to the IESG for publication as an Informational RFC Internet-Drafts: - Building Power-Efficient CoAP Devices for Cellular Networks [draft-ietf-lwig-cellular-03] (16 pages) - CoAP Implementation Guidance [draft-ietf-lwig-coap-01] (21 pages) - Energy Efficient Implementation of IETF Constrained Protocol Suite [draft-ietf-lwig-energy-efficient-02] (19 pages) - Guidance for Light-Weight Implementations of the Internet Protocol Suite [draft-ietf-lwig-guidance-03] (34 pages) - Minimal IKEv2 [draft-ietf-lwig-ikev2-minimal-02] (33 pages) - Terminology for Constrained-Node Networks [draft-ietf-lwig-terminology-07] (17 pages) - A Hitchhiker's Guide to the (Datagram) Transport Layer Security Protocol for Smart Objects and Constrained Node Networks [draft-ietf-lwig-tls-minimal-01] (15 pages) Requests for Comments: RFC7228: Terminology for Constrained-Node Networks (17 pages) * Replaces DRAFT-BORMANN-LWIG-TERMS * Informative Reference RFC4919 * Informative Reference RFC7102 * Informative Reference RFC4838 * Informative Reference RFC6606 * Possible Reference RFC5741 * Informative Reference RFC793 * Informative Reference RFC6551 * Informative Reference RFC6550 * Informative Reference RFC7400 * Informative Reference DRAFT-VANDERSTOK-CORE-COMI * Informative Reference DRAFT-IETF-ROLL-APPLICABILITY-HOME-BUILDING * Informative Reference DRAFT-IETF-6TISCH-TSCH * Informative Reference DRAFT-SCHMERTMANN-DICE-CODTLS * Informative Reference DRAFT-IETF-CORE-OBSERVE * Informative Reference DRAFT-IETF-CORE-BLOCK * Informative Reference DRAFT-JIMENEZ-P2PSIP-COAP-RELOAD * Informative Reference RFC7397 * Informative Reference RFC7452 * Normative Reference DRAFT-SILVERAJAN-CORE-COAP-ALTERNATIVE-TRANSPORTS * Normative Reference DRAFT-IETF-LWIG-CELLULAR * Informative Reference DRAFT-KUMAR-DICE-DTLS-RELAY * Informative Reference DRAFT-IETF-OPSAWG-COMAN-PROBSTATE-REQS * Informative Reference DRAFT-IETF-OPSAWG-COMAN-USE-CASES * Informative Reference DRAFT-IETF-ACE-USECASES * Informative Reference DRAFT-SEITZ-ACE-USECASES * Informative Reference DRAFT-IETF-LWIG-ENERGY-EFFICIENT * Informative Reference DRAFT-IETF-LWIG-COAP * Informative Reference DRAFT-SEITZ-ACE-PROBLEM-DESCRIPTION * Normative Reference DRAFT-GERDES-ACE-ACTORS * Reference DRAFT-WANG-CFRG-SDA-WSN * Possible Reference DRAFT-SCHMITT-ACE-TWOWAYAUTH-FOR-IOT * Informative Reference DRAFT-SELANDER-ACE-OBJECT-SECURITY * Informative Reference DRAFT-BORMANN-JOSE-COSE * Normative Reference DRAFT-THUBERT-6LO-ROUTING-DISPATCH * Informative Reference DRAFT-IETF-DICE-PROFILE * Normative Reference DRAFT-HE-6LO-ANALYSIS-IOT-SBOOTSTRAPPING * Informative Reference DRAFT-MALER-ACE-OAUTH-UMA * Informative Reference DRAFT-SOOD-6MAN-ND-SIGNALLING-N-DAD-TEST Locator/ID Separation Protocol (lisp) ------------------------------------- Charter Last Modified: 2014-07-24 Current Status: Active Chairs: Joel M. Halpern Luigi Iannone Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Brian Haberman Secretaries: Damien Saucez Wassim Haddad Mailing Lists: General Discussion: lisp@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/lisp Archive: http://www.ietf.org/mail-archive/web/lisp/ Description of Working Group: The IAB's October 2006 Routing and Addressing Workshop (RFC 4984) rekindled interest in scalable routing and addressing architectures for the Internet. Among the many issues driving this renewed interest are concerns about the scalability of the routing system. Since the IAB workshop, several proposals have emerged which attempt to address the concerns expressed there and elsewhere. In general, these proposals are based on the "locator/identifier separation". The basic idea behind the separation is that the Internet architecture combines two functions, routing locators, (where you are attached to the network) and identifiers (who you are) in one number space: The IP address. Proponents of the separation architecture postulate that splitting these functions apart will yield several advantages, including improved scalability for the routing system. The separation aims to decouple locators and identifiers, thus allowing for efficient aggregation of the routing locator space and providing persistent identifiers in the identifier space. A number of approaches are being looked at in parallel in other contexts. The IRTF RRG examined several proposals, some of which were published as IRTF-track Experimental RFCs. The LISP WG has completed the first set of Experimental RFCs describing the Locator/ID Separation Protocol. LISP requires no changes to end-systems or to routers that do not directly participate in the LISP deployment. LISP aims for an incrementally deployable protocol. The LISP WG is chartered to continue work on the LISP base protocol, completing the ongoing work, and any items which directly impact LISP protocol structures and which are related to using LISP for improving Internet routing scalability. Specifically, the group will work on: - Architecture description: This document will describe the architecture of the entire LISP system, making it easier to read the rest of the LISP specifications and providing a basis for discussion about the details of the LISP protocols. The document will include a description of the cache management and ETR synchronization essential characteristics needed to ensure the correct operation of the protocol. - Deployment models: This document will describe what kind of deployments can be expected for LISP, and give operational advice on how they can be set up. - A description of the impacts of LISP: This document will describe the problems that LISP is intended to address and the impacts that employing LISP has. While the work on LISP was initiated by Internet routing scaling concerns, there has also been an interest on improved solutions to a number of different problems, such as traffic engineering. This document should describe problem areas (such as scaling or traffic engineer) where LISP is expected to have a positive effect, as well as any tradeoffs that are caused by LISP's design. - LISP security threats and solutions: This document will describe the security analysis of the LISP system, what issues it needs to protect against, and a solution that helps defend against those issues. The replay attack problem discussed on the mailing list should be included in this work. - Allocation of Endpoint IDentifier (EID) space: This document requests address space to be used for the LISP experiment as identifier space - Alternate mapping system designs: Develop alternative mapping designs to be tested. - Data models for management of LISP. The first three items (architecture, deployment models, impacts) need to be completed first before other items can be submitted as RFCs. The three first documents also need to complement each other, by describing how the architecture supports a solution for a particular problem area and how the solution can be deployed to help with that problem. In addition, if work chartered in some other IETF WG requires changes in the LISP base protocol or any items which directly impact LISP protocol structures, then the LISP WG is chartered to work on such changes. It is expected that the results of specifying, implementing, and testing LISP will be fed to the general efforts at the IETF and IRTF to understand which type of a solution is optimal. The LISP WG is not chartered to develop a standard solution for solving the routing scalability problem at this time. The specifications developed by the WG are Experimental and labeled with accurate disclaimers about their limitations and not fully understood implications for Internet traffic. In addition, as these issues are understood, the working group will analyze and document the implications of LISP on Internet traffic, applications, routers, and security. Goals and Milestones: Sep 2012 - Submit a LISP impact discussion document to the IESG for publication as an Experimental RFC Sep 2012 - Submit an architecture description to the IESG for publication as an Experimental RFC Oct 2012 - Submit an EID allocation document to the IESG for publication as an Experimental RFC Oct 2012 - Submit a LISP threats analysis document to the IESG for publication as an Experimental RFC Jan 2013 - Submit an lternate mapping system designs to the IESG for publication as an Experimental RFC Mar 2013 - Summarize results of specifying, implementing, and testing LISP and forward to IESG and/or IRTF. Done - Submit a deployment model document to the IESG for publication as an Experimental RFC Done - Submit a data model (e.g., a MIB) document to the IESG for publication as an Experimental RFC Internet-Drafts: - An Architectural Perspective on the LISP Location-Identity Separation System [draft-chiappa-lisp-architecture-01] (19 pages) - An Introduction to the LISP Location-Identity Separation System [draft-chiappa-lisp-introduction-01] (29 pages) - LISP Data-Plane Confidentiality [draft-farinacci-lisp-crypto-01] (10 pages) - LISP Canonical Address Format (LCAF) [draft-farinacci-lisp-lcaf-10] (29 pages) - The Locator/ID Separation Protocol (LISP) [draft-ietf-lisp-24] (75 pages) - Locator/ID Separation Protocol Alternative Logical Topology (LISP+ALT) [draft-ietf-lisp-alt-10] (25 pages) - An Architectural Perspective on the LISP Location-Identity Separation System [draft-ietf-lisp-architecture-00] (19 pages) - LISP Data-Plane Confidentiality [draft-ietf-lisp-crypto-00] (11 pages) - LISP Delegated Database Tree [draft-ietf-lisp-ddt-02] (35 pages) - Locator/Identifier Separation Protocol (LISP) Network Element Deployment Considerations [draft-ietf-lisp-deployment-12] (30 pages) - LISP EID Block [draft-ietf-lisp-eid-block-10] (16 pages) - LISP EID Block Management Guidelines [draft-ietf-lisp-eid-block-mgmnt-04] (13 pages) - LISP Impact [draft-ietf-lisp-impact-01] (16 pages) - Interworking between Locator/ID Separation Protocol (LISP) and Non-LISP Sites [draft-ietf-lisp-interworking-06] (19 pages) - An Architectural Introduction to the Locator/ID Separation Protocol (LISP) [draft-ietf-lisp-introduction-12] (28 pages) - LISP Canonical Address Format (LCAF) [draft-ietf-lisp-lcaf-07] (35 pages) - The Locator/ID Separation Protocol Internet Groper (LIG) [draft-ietf-lisp-lig-06] (12 pages) - Locator/ID Separation Protocol (LISP) Map-Versioning [draft-ietf-lisp-map-versioning-09] (21 pages) - Locator/ID Separation Protocol (LISP) MIB [draft-ietf-lisp-mib-13] (66 pages) - Locator/ID Separation Protocol (LISP) Map-Server Interface [draft-ietf-lisp-ms-16] (13 pages) - The Locator/ID Separation Protocol (LISP) for Multicast Environments [draft-ietf-lisp-multicast-14] (28 pages) - An Architectural Perspective on the LISP Location-Identity Separation System [draft-ietf-lisp-perspective-00] (21 pages) - LISP-Security (LISP-SEC) [draft-ietf-lisp-sec-07] (19 pages) - LISP Threats Analysis [draft-ietf-lisp-threats-12] (20 pages) - LISP Impact [draft-saucez-lisp-impact-07] (15 pages) Requests for Comments: RFC6830: The Locator/ID Separation Protocol (LISP) (75 pages) * Normative Reference RFC5226 * Normative Reference RFC768 * Normative Reference RFC2460 * Informative Reference BCP107 * Normative Reference BCP14 * Normative Reference RFC4086 * Possible Reference RFC5741 * Normative Reference RFC1918 * Normative Reference BCP106 * Normative Reference RFC6275 * Informative Reference RFC1034 * Normative Reference RFC3168 * Normative Reference RFC6833 * Informative Reference RFC6832 * Informative Reference RFC6831 * Informative Reference RFC6837 * Normative Reference RFC6836 * Informative Reference RFC6835 * Normative Reference RFC6834 * Normative Reference RFC5944 * Informative Reference RFC2784 * Normative Reference RFC5496 * Informative Reference RFC3261 * Informative Reference RFC4107 * Normative Reference BCP5 * Informative Reference RFC6480 * Informative Reference STD13 * Informative Reference RFC4866 * Normative Reference RFC4632 * Normative Reference BCP26 * Normative Reference RFC2119 * Normative Reference RFC4868 * Informative Reference RFC4192 * Informative Reference RFC3056 * Normative Reference RFC791 * Normative Reference RFC6115 * Normative Reference RFC3232 * Informative Reference RFC6518 * Informative Reference RFC4984 * Normative Reference BCP122 * Normative Reference RFC2404 * Informative Reference DRAFT-HERBERT-GUE * Informative Reference DRAFT-IETF-6TISCH-ARCHITECTURE * Informative Reference DRAFT-YEGIN-IP-MOBILITY-ORCHESTRATOR * Normative Reference RFC6837 * Normative Reference RFC6836 * Normative Reference RFC6832 * Normative Reference RFC6831 * Normative Reference DRAFT-BARKAI-LISP-NFV * Normative Reference RFC6833 * Normative Reference RFC6835 * Informative Reference DRAFT-TEMPLIN-INTAREA-VET * Normative Reference DRAFT-MEYER-LISP-MN * Informative Reference RFC6936 * Normative Reference RFC7052 * Informative Reference RFC6834 * Informative Reference RFC6935 * Normative Reference DRAFT-SMITH-LISP-LAYER2 * Normative Reference RFC7215 * Informative Reference DRAFT-IETF-LISP-EID-BLOCK-MGMNT * Normative Reference DRAFT-IETF-LISP-SEC * Informative Reference DRAFT-IETF-LISP-EID-BLOCK * Normative Reference DRAFT-IETF-LISP-THREATS * Informative Reference DRAFT-TEMPLIN-IRONBIS * Normative Reference DRAFT-ERMAGAN-LISP-NAT-TRAVERSAL * Normative Reference DRAFT-FARINACCI-LISP-RIG * Normative Reference DRAFT-FARINACCI-LISP-TE * Normative Reference DRAFT-SAUCEZ-LISP-ITR-GRACEFUL * Normative Reference DRAFT-CHENG-LISP-SHDHT * Normative Reference DRAFT-CORAS-LISP-RE * Informative Reference DRAFT-MAINO-NVO3-LISP-CP * Normative Reference DRAFT-FARINACCI-LISP-MR-SIGNALING * Informative Reference RFC7364 * Normative Reference DRAFT-IETF-LISP-LCAF * Normative Reference DRAFT-HADDAD-HOMENET-MULTIHOMED * Normative Reference DRAFT-CHENG-LISP-NAT-TRAVERSAL-EXTENSION * Normative Reference DRAFT-SAUCEZ-LISP-IMPACT * Informative Reference DRAFT-IETF-LISP-DDT * Informative Reference DRAFT-XU-SOFTWIRE-IP-IN-UDP * Informative Reference DRAFT-YONG-TSVWG-UDP-ENCAP-4-IP-TUNNELING * Informative Reference RFC7059 * Normative Reference DRAFT-WU-NVO3-MAC-LEARNING-ARP * Informative Reference DRAFT-IANNONE-LISP-EID-BLOCK-MGMNT * Normative Reference DRAFT-ARANGO-PIM-JOIN-ATTRIBUTES-FOR-LISP * Informative Reference DRAFT-BROCKNERS-LISP-SR * Informative Reference DRAFT-LEWIS-LISP-GPE * Reference DRAFT-THUBERT-DMM-GLOBAL-HAHA * Informative Reference DRAFT-HERTOGHS-NVO3-LISP-CONTROLPLANE-UNIFIED * Informative Reference DRAFT-HERTOGHS-LISP-MOBILITY-USE-CASES * Normative Reference DRAFT-RODRIGUEZNATAL-LISP-SDN * Informative Reference DRAFT-MORENO-LISP-DATACENTER-DEPLOYMENT * Normative Reference DRAFT-FARINACCI-LISP-CRYPTO * Normative Reference DRAFT-KOUVELAS-LISP-RELIABLE-TRANSPORT * Normative Reference DRAFT-LEWIS-LISP-VPNS * Informative Reference DRAFT-FREITASBELLAGAMBA-LISP-HYBRID-CLOUD-USE-CASE * Informative Reference DRAFT-FARINACCI-LISP-SIGNAL-FREE-MULTICAST * Normative Reference DRAFT-LOPEZ-LISP-OE * Normative Reference DRAFT-IETF-PIM-JOIN-ATTRIBUTES-FOR-LISP * Informative Reference DRAFT-THUBERT-6LO-RFC6775-UPDATE-REQS * Informative Reference DRAFT-RODRIGUEZNATAL-LISP-OAM * Normative Reference DRAFT-SHEN-LISP-MULTIPROVIDER-VPN * Normative Reference DRAFT-IETF-LISP-INTRODUCTION * Normative Reference DRAFT-IETF-LISP-IMPACT * Normative Reference DRAFT-IETF-LISP-CRYPTO * Informative Reference DRAFT-QUINN-VXLAN-GPE * Normative Reference DRAFT-RTG-DT-ENCAP RFC6831: The Locator/ID Separation Protocol (LISP) for Multicast Environments (28 pages) * Replaces DRAFT-FARINACCI-LISP-MULTICAST * Informative Reference RFC5059 * Informative Reference RFC6836 * Normative Reference RFC3618 * Normative Reference RFC4760 * Normative Reference RFC3956 * Normative Reference RFC6832 * Normative Reference RFC5496 * Normative Reference BCP135 * Possible Reference RFC5741 * Normative Reference RFC6830 * Normative Reference RFC5015 * Normative Reference RFC5135 * Normative Reference BCP14 * Normative Reference RFC4607 * Normative Reference RFC4604 * Normative Reference RFC2119 * Normative Reference RFC4601 * Informative Reference RFC6830 * Normative Reference DRAFT-MEYER-LISP-MN * Normative Reference DRAFT-SMITH-LISP-LAYER2 * Informative Reference DRAFT-IETF-LISP-EID-BLOCK-MGMNT * Normative Reference DRAFT-IETF-LISP-EID-BLOCK * Normative Reference DRAFT-FARINACCI-LISP-TE * Normative Reference DRAFT-CORAS-LISP-RE * Informative Reference DRAFT-MAINO-NVO3-LISP-CP * Normative Reference DRAFT-FARINACCI-LISP-MR-SIGNALING * Normative Reference DRAFT-SAUCEZ-LISP-IMPACT * Informative Reference DRAFT-IANNONE-LISP-EID-BLOCK-MGMNT * Normative Reference DRAFT-ARANGO-PIM-JOIN-ATTRIBUTES-FOR-LISP * Informative Reference DRAFT-HERTOGHS-NVO3-LISP-CONTROLPLANE-UNIFIED * Informative Reference DRAFT-HERTOGHS-LISP-MOBILITY-USE-CASES * Informative Reference DRAFT-MORENO-LISP-DATACENTER-DEPLOYMENT * Informative Reference DRAFT-FARINACCI-LISP-SIGNAL-FREE-MULTICAST * Normative Reference DRAFT-IETF-PIM-JOIN-ATTRIBUTES-FOR-LISP * Informative Reference DRAFT-RODRIGUEZNATAL-LISP-OAM * Normative Reference DRAFT-IETF-LISP-INTRODUCTION * Normative Reference DRAFT-IETF-LISP-IMPACT RFC6832: Interworking between Locator/ID Separation Protocol (LISP) and Non-LISP Sites (19 pages) * Replaces DRAFT-LEWIS-LISP-INTERWORKING * Informative Reference RFC2993 * Normative Reference RFC1918 * Normative Reference BCP5 * Normative Reference RFC6830 * Normative Reference RFC6836 * Possible Reference RFC5741 * Informative Reference RFC6836 * Normative Reference RFC6831 * Normative Reference RFC6835 * Informative Reference RFC6830 * Normative Reference DRAFT-MEYER-LISP-MN * Normative Reference RFC7052 * Normative Reference RFC6834 * Normative Reference RFC7215 * Informative Reference DRAFT-IETF-LISP-EID-BLOCK-MGMNT * Informative Reference DRAFT-IETF-LISP-EID-BLOCK * Normative Reference DRAFT-IETF-LISP-THREATS * Normative Reference DRAFT-FARINACCI-LISP-TE * Informative Reference DRAFT-MAINO-NVO3-LISP-CP * Normative Reference DRAFT-SAUCEZ-LISP-IMPACT * Informative Reference RFC7059 * Informative Reference DRAFT-IANNONE-LISP-EID-BLOCK-MGMNT * Informative Reference DRAFT-HERTOGHS-NVO3-LISP-CONTROLPLANE-UNIFIED * Informative Reference DRAFT-HERTOGHS-LISP-MOBILITY-USE-CASES * Informative Reference DRAFT-MORENO-LISP-DATACENTER-DEPLOYMENT * Normative Reference DRAFT-LEWIS-LISP-VPNS * Informative Reference DRAFT-FREITASBELLAGAMBA-LISP-HYBRID-CLOUD-USE-CASE * Informative Reference DRAFT-RODRIGUEZNATAL-LISP-OAM * Normative Reference DRAFT-IETF-LISP-INTRODUCTION * Normative Reference DRAFT-IETF-LISP-IMPACT RFC6833: Locator/ID Separation Protocol (LISP) Map-Server Interface (13 pages) * Replaces DRAFT-FULLER-LISP-MS * Informative Reference RFC4107 * Normative Reference RFC2104 * Informative Reference BCP107 * Possible Reference RFC5741 * Normative Reference RFC6830 * Informative Reference RFC6837 * Normative Reference RFC6836 * Normative Reference RFC6234 * Normative Reference RFC1035 * Normative Reference STD13 * Informative Reference RFC6837 * Normative Reference RFC6836 * Normative Reference RFC6835 * Normative Reference RFC6830 * Normative Reference DRAFT-MEYER-LISP-MN * Normative Reference RFC7052 * Normative Reference RFC7215 * Informative Reference DRAFT-IETF-LISP-EID-BLOCK-MGMNT * Normative Reference DRAFT-IETF-LISP-SEC * Informative Reference DRAFT-IETF-LISP-EID-BLOCK * Normative Reference DRAFT-IETF-LISP-THREATS * Normative Reference DRAFT-ERMAGAN-LISP-NAT-TRAVERSAL * Normative Reference DRAFT-FARINACCI-LISP-RIG * Normative Reference DRAFT-FARINACCI-LISP-TE * Normative Reference DRAFT-SAUCEZ-LISP-ITR-GRACEFUL * Normative Reference DRAFT-CHENG-LISP-SHDHT * Informative Reference DRAFT-MAINO-NVO3-LISP-CP * Normative Reference DRAFT-SAUCEZ-LISP-IMPACT * Normative Reference DRAFT-IETF-LISP-DDT * Informative Reference RFC7059 * Informative Reference DRAFT-IANNONE-LISP-EID-BLOCK-MGMNT * Informative Reference DRAFT-BROCKNERS-LISP-SR * Informative Reference DRAFT-HERTOGHS-NVO3-LISP-CONTROLPLANE-UNIFIED * Normative Reference DRAFT-RODRIGUEZNATAL-LISP-SDN * Informative Reference DRAFT-MORENO-LISP-DATACENTER-DEPLOYMENT * Normative Reference DRAFT-KOUVELAS-LISP-RELIABLE-TRANSPORT * Normative Reference DRAFT-LEWIS-LISP-VPNS * Informative Reference DRAFT-FARINACCI-LISP-SIGNAL-FREE-MULTICAST * Normative Reference DRAFT-IETF-LISP-INTRODUCTION * Normative Reference DRAFT-IETF-LISP-IMPACT RFC6834: Locator/ID Separation Protocol (LISP) Map-Versioning (21 pages) * Possible Reference RFC5741 * Normative Reference RFC6832 * Informative Reference RFC6830 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference RFC6830 * Normative Reference DRAFT-MEYER-LISP-MN * Informative Reference DRAFT-IETF-LISP-EID-BLOCK-MGMNT * Informative Reference RFC7215 * Normative Reference DRAFT-IETF-LISP-EID-BLOCK * Normative Reference DRAFT-IETF-LISP-THREATS * Normative Reference DRAFT-SAUCEZ-LISP-IMPACT * Informative Reference DRAFT-IANNONE-LISP-EID-BLOCK-MGMNT * Informative Reference DRAFT-LEWIS-LISP-GPE * Normative Reference DRAFT-IETF-LISP-INTRODUCTION * Normative Reference DRAFT-IETF-LISP-IMPACT RFC6835: The Locator/ID Separation Protocol Internet Groper (LIG) (12 pages) * Replaces DRAFT-FARINACCI-LISP-LIG * Normative Reference BCP122 * Normative Reference RFC6832 * Normative Reference RFC6833 * Possible Reference RFC5741 * Normative Reference RFC6830 * Informative Reference RFC6837 * Informative Reference RFC6836 * Normative Reference RFC4632 * Informative Reference RFC6830 * Informative Reference DRAFT-IETF-LISP-EID-BLOCK-MGMNT * Normative Reference DRAFT-IETF-LISP-EID-BLOCK * Normative Reference DRAFT-FARINACCI-LISP-RIG * Informative Reference DRAFT-IANNONE-LISP-EID-BLOCK-MGMNT * Normative Reference DRAFT-IETF-LISP-INTRODUCTION RFC6836: Locator/ID Separation Protocol Alternative Logical Topology (LISP+ALT) (25 pages) * Replaces DRAFT-FULLER-LISP-ALT * Normative Reference RFC4760 * Informative Reference RFC6832 * Normative Reference RFC4271 * Normative Reference RFC2784 * Normative Reference RFC6833 * Possible Reference RFC5741 * Normative Reference RFC6830 * Normative Reference BCP122 * Informative Reference RFC5925 * Normative Reference RFC4632 * Informative Reference RFC6837 * Normative Reference RFC6832 * Informative Reference RFC6831 * Normative Reference RFC6833 * Informative Reference RFC6835 * Normative Reference RFC6830 * Normative Reference DRAFT-MEYER-LISP-MN * Normative Reference DRAFT-IETF-LISP-LCAF * Informative Reference RFC7215 * Informative Reference DRAFT-IETF-LISP-EID-BLOCK-MGMNT * Informative Reference DRAFT-IETF-LISP-EID-BLOCK * Normative Reference DRAFT-CHENG-LISP-SHDHT * Informative Reference DRAFT-MAINO-NVO3-LISP-CP * Normative Reference DRAFT-SAUCEZ-LISP-IMPACT * Informative Reference DRAFT-IETF-LISP-DDT * Informative Reference DRAFT-IANNONE-LISP-EID-BLOCK-MGMNT * Informative Reference DRAFT-HERTOGHS-NVO3-LISP-CONTROLPLANE-UNIFIED * Informative Reference DRAFT-MORENO-LISP-DATACENTER-DEPLOYMENT * Normative Reference DRAFT-IETF-LISP-INTRODUCTION * Normative Reference DRAFT-IETF-LISP-IMPACT RFC7052: Locator/ID Separation Protocol (LISP) MIB (66 pages) * Replaces DRAFT-SCHUDEL-LISP-MIB * Normative Reference RFC2579 * Normative Reference RFC2578 * Normative Reference RFC2119 * Normative Reference RFC2580 * Informative Reference RFC3410 * Normative Reference RFC4382 * Normative Reference BCP14 * Normative Reference RFC6353 * Normative Reference RFC3414 * Normative Reference RFC6830 * Possible Reference RFC5741 * Normative Reference RFC6833 * Normative Reference RFC5592 * Normative Reference STD62 * Normative Reference STD58 * Normative Reference RFC5591 * Normative Reference RFC6832 * Normative Reference RFC3826 * Normative Reference DRAFT-IETF-LISP-INTRODUCTION RFC7215: Locator/Identifier Separation Protocol (LISP) Network Element Deployment Considerations (30 pages) * Replaces DRAFT-JAKAB-LISP-DEPLOYMENT * Informative Reference RFC6836 * Informative Reference DRAFT-IETF-LISP-THREATS * Informative Reference RFC4459 * Informative Reference RFC6834 * Informative Reference RFC4984 * Normative Reference RFC6830 * Informative Reference BCP126 * Normative Reference RFC6832 * Normative Reference RFC6833 * Informative Reference DRAFT-IETF-LISP-SEC * Informative Reference RFC4786 * Informative Reference DRAFT-IETF-LISP-DDT * Informative Reference RFC6887 * Informative Reference DRAFT-IETF-LISP-EID-BLOCK * Informative Reference DRAFT-IETF-LISP-THREATS * Normative Reference DRAFT-IETF-LISP-INTRODUCTION * Normative Reference DRAFT-IETF-LISP-IMPACT Mobility for IPv4 (mip4) ------------------------ Charter Last Modified: 2011-12-09 Current Status: Active Chairs: Henrik Levkowetz Pete McCann Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Brian Haberman Mailing Lists: General Discussion: mip4@ietf.org To Subscribe: mip4-request@ietf.org Archive: http://www.ietf.org/mail-archive/web/mip4/ Description of Working Group: IP mobility support for IPv4 nodes (hosts and routers) is specified in RFC3344. RFC 3344 mobility allows a node to continue using its "permanent" home address as it moves around the Internet. The Mobile IP protocols support transparency above the IP layer, including maintenance of active TCP connections and UDP port bindings. Besides the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal with concerns such as optimization, security, extensions, AAA support, and deployment issues. MIPv4 is currently being deployed on a wide basis (e.g., in cdma2000 networks). The scope of the deployment is on a fairly large scale and accordingly, the MIP4 WG will focus on deployment issues and on addressing known deficiencies and shortcomings in the protocol that have come up as a result of deployment experience. Specifically, the working group will complete the work items to facilitate interactions with AAA environments, interactions with enterprise environments when MIPv4 is used therein, and updating existing protocol specifications in accordance with deployment needs and advancing those protocols that are on the standards track. Work expected to be done by the MIP4 WG as proposed by this charter is as follows: 1. MIPv4 has been a Proposed Standard for several years. It has been adopted by other standard development organizations and has been deployed commercially. One of the next steps for the WG is to advance the protocol to draft standard status. As part of advancing base Mobile IP specifications to Draft Standard, the MIPv4 NAI RFC (2794) will be revised to reflect implementation experience. 2. The WG will complete the MIB specifications for the Mobile IPv4 base protocol and the UDP tunneling extension. 3. A requirements document for RADIUS MIP4 support was previously completed and published as RFC 5030. Based on these requirements, the WG will complete the specification of MIPv4 RADIUS attributes, solicit feedback from the RADEXT WG, adjust, and submit this for publication. Note that the work may require extensions to the RADIUS attribute space which will be handled outside the MIP4 WG. 4. Like fixed nodes, mobile nodes sometimes need to be dynamically configured with parameters such as DNS server IP addresses. Previous work in the WG proposed to put a generic container for host configuration options into Mobile IPv4 signaling. However, it may be easier for mobile nodes to implement the already existing DHCP specification, and to run DHCP over the tunnel established with an initial registration. The WG will take on a draft describing any modifications to Mobile IPv4 that may be needed to facilitate this mode of operation, and submit for publication as a Proposed Standard or Best Current Practice as appropriate. 5. The proliferation of devices with multiple interface technologies and the desire to use each interface for the type of traffic most appropriate to it (even simultaneously with other interfaces active at the same time) has led to requirements for supporting multiple simultaneous tunnels between the Home Agent and Mobile Node. The WG will adopt and take to publication as an Experimental RFC one draft that describes how to manage such tunnels and how to direct traffic to use the appropriate tunnel when multiple choices are available. This work will be coordinated with similar Mobile IPv6 work ongoing in the mext working group. In particular, we will strive to converge on a consistent set of architectural decisions (such as which entities are responsible for signaling flow-to-tunnel bindings) and we will share protocol definitions wherever practical (such as the layout of packet flow filters). 6. The WG has published a basic Network Mobility (NEMO) specification as RFC 5177. The WG has taken up an extension to NEMO that will allow for dynamic home network prefix allocation to a moving network. The WG will finish work on this draft and publish as a Proposed Standard. 7. Route optimization has been the focus of a large amount of effort in the Mobile IPv6 WG. For Mobile IPv4, however, the usage case is less clear due to a variety of factors, including the inability to modify already deployed correspondent nodes. Recently a specific use case has been proposed involving route optimization for a more closed network where modifications are made to site routers and a centralized Home Agent to enable offloading of traffic from the Home Agent. The WG will take on and publish a draft on this topic as a Experimental RFC. 8. The use of GRE tunneling with Mobile IPv4 enables support for multiple overlapping private address spaces within the same mobility agent. However, to distinguish flows from two different mobile nodes that happen to share the same (private) IP address, the GRE Key field needs to be populated with a unique identifier that will enable the mobility agent to demultiplex the flows. The value used for the Key needs to be signaled at the time of tunnel establishment, which means a new Mobile IPv4 extension is needed for this purpose. The WG will take on an publish a draft on this topic as a Proposed Standard. 9. Support for multicast and broadcast packets in Mobile IPv4 as specified in RFC 3024 currently requires encapsulated delivery style for all packets. This leads to inefficiencies on the MN-to-FA link because even unicast packets must be encapsulated. Eliminating this inefficiency is possible if there is a mechanism to negotiate a mode of operation where only multicast/broadcast packets are encapsulated, while unicast packets can use direct delivery style. The WG will take on a draft to solve this problem and publish as a Proposed Standard. Goals and Milestones: Done - AAA Keys for MIPv4 to IESG Done - MIPv4 VPN interaction problem statement to IESG Done - Low latency handover to experimental Done - Experimental MIPv4 message and extensions draft to IESG Done - Dynamic Home Agent assignment protocol solution to IESG Done - Revised MIPv4 Challenge/Response (3012bis) to IESG Done - Regional registration document to IESG Done - Generic Strings for MIPv4 (Proposed Std.) to the IESG Done - MIPv4 Mobike interaction (BCP) to the IESG Done - MIPv4 RADIUS Extensions Requirements to the IESG Done - MIPv4 Extension for Config. Options (Proposed Std.) to the IESG Done - FMIPv4 (Experimental) to the IESG Done - MIPv4 VPN interaction (BCP) to the IESG Done - Base MIPv4 Mobile Network Support (Draft Std.) to IESG Done - Dual-stack MIPv4 (Draft Std.) to IESG Done - Notification Mechanism (Draft Std.) to IESG Jul 2009 - Revised MIPv4 specification (Proposed Std.) to IESG Jul 2009 - Revised MIB for MIPv4 (Proposed Std.) to IESG Aug 2009 - NEMO Dynamic Address Assignment (Proposed Std.) to IESG Nov 2009 - GRE Key Extension (Proposed Std) to IESG Nov 2009 - Revised rfc2794bis (NAI extension) (Proposed Std.) to the IESG Nov 2009 - RADIUS Extensions for MIPv4 to the RADEXT WG for comment Dec 2009 - MIB for UDP encapsulation (Proposed Std.) to IESG Feb 2010 - RADIUS Extensions for MIPv4 (Proposed Std.) to the IESG Mar 2010 - Home Agent Assisted Route Optimization (Experimental) to the IESG Apr 2010 - Multiple/Broadcast delivery style (Proposed Std.) to IESG May 2010 - Multiple tunnel support and flow binding (Experimental) to IESG Internet-Drafts: - Authentication, Authorization, and Accounting (AAA) Registration Keys for Mobile IPv4 [draft-ietf-mip4-aaa-key-06] (27 pages) - Mobile IPv4 Extension for Carrying Network Access Identifiers [draft-ietf-mip4-aaa-nai-02] (8 pages) - Dual-Stack Mobile IPv4 [draft-ietf-mip4-dsmipv4-10] (18 pages) - Mobile IPv4 Dynamic Home Agent (HA) Assignment [draft-ietf-mip4-dynamic-assignment-07] (25 pages) - Experimental Message, Extensions, and Error Codes for Mobile IPv4 [draft-ietf-mip4-experimental-messages-02] (11 pages) - Foreign Agent Error Extension for Mobile IPv4 [draft-ietf-mip4-faerr-02] (6 pages) - Mobile IPv4 Fast Handovers [draft-ietf-mip4-fmipv4-07] (28 pages) - Mobile IPv4 Extension for Configuration Options Exchange [draft-ietf-mip4-gen-ext-04] (13 pages) - Generic Notification Message for Mobile IPv4 [draft-ietf-mip4-generic-notification-message-16] (33 pages) - Generic Routing Encapsulation (GRE) Key Extension for Mobile IPv4 [draft-ietf-mip4-gre-key-extension-05] (8 pages) - IPv4 Mobility Extension for Multicast and Broadcast Packets [draft-ietf-mip4-mcbc-01] (12 pages) - Mobile IPv4 Message String Extension [draft-ietf-mip4-message-string-ext-03] (7 pages) - Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE) [draft-ietf-mip4-mobike-connectivity-03] (15 pages) - Flow Binding Support for Mobile IP [draft-ietf-mip4-multiple-tunnel-support-11] (18 pages) - Home Agent-Assisted Route Optimization between Mobile IPv4 Networks [draft-ietf-mip4-nemo-haaro-07] (53 pages) - Network Mobility (NEMO) Extensions for Mobile IPv4 [draft-ietf-mip4-nemo-v4-base-11] (26 pages) - Dynamic Prefix Allocation for Network Mobility for Mobile IPv4 (NEMOv4) [draft-ietf-mip4-nemov4-dynamic-06] (5 pages) - FA extensions to NEMOv4 Base [draft-ietf-mip4-nemov4-fa-03] (10 pages) - Mobile IPv4 RADIUS Requirements [draft-ietf-mip4-radius-requirements-04] (9 pages) - Mobile IPv4 Regional Registration [draft-ietf-mip4-reg-tunnel-04] (35 pages) - The Definitions of Managed Objects for IP Mobility Support using SMIv2, revised [draft-ietf-mip4-rfc2006bis-06] (112 pages) - Mobile IPv4 Challenge/Response Extensions (Revised) [draft-ietf-mip4-rfc3012bis-05] (26 pages) - IP Mobility Support for IPv4, Revised [draft-ietf-mip4-rfc3344bis-10] (100 pages) - The Definitions of Managed Objects for Mobile IP UDP Tunneling [draft-ietf-mip4-udptunnel-mib-02] (14 pages) - Mobile IPv4 Traversal across IPsec-Based VPN Gateways [draft-ietf-mip4-vpn-problem-solution-05] (39 pages) - Problem Statement: Mobile IPv4 Traversal of Virtual Private Network (VPN) Gateways [draft-ietf-mip4-vpn-problem-statement-03] (19 pages) - Low-Latency Handoffs in Mobile IPv4 [draft-ietf-mobileip-lowlatency-handoffs-v4-11] (64 pages) - Mobile IPv4 Traversal Across IPsec-based VPN Gateways [draft-ietf-mobileip-vpn-problem-solution-03] (49 pages) Requests for Comments: BCP136: Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE) (15 pages) * Replaces DRAFT-DEVARAPALLI-MIP4-MOBIKE-CONNECTIVITY * Informative Reference RFC4093 * Informative Reference RFC3519 * Informative Reference RFC3024 * Normative Reference RFC3344 * Normative Reference RFC5265 * Normative Reference RFC4301 * Informative Reference RFC2409 * Informative Reference RFC3947 * Normative Reference RFC4306 * Informative Reference BCP78 * Normative Reference RFC4555 * Informative Reference RFC3948 * Normative Reference RFC2119 * Normative Reference BCP14 * Informative Reference RFC5454 * Informative Reference DRAFT-MARTINELLI-CCAMP-OPTICAL-IMP-SIGNALING * Informative Reference RFC6071 * Normative Reference DRAFT-KOUVELAS-LISP-RELIABLE-TRANSPORT RFC3846: Mobile IPv4 Extension for Carrying Network Access Identifiers (8 pages) * Normative Reference RFC2794 * Normative Reference BCP78 * Normative Reference RFC2486 * Normative Reference RFC3344 * Normative Reference RFC3588 * Normative Reference BCP14 * Normative Reference BCP26 * Normative Reference RFC4004 * Normative Reference DRAFT-IETF-MIP4-RFC2006BIS * Normative Reference RFC4857 * Possible Reference DRAFT-NAKHJIRI-RADIUS-MIP4 * Normative Reference DRAFT-FAJARDO-DIME-INTEROP-TEST-SUITE * Normative Reference DRAFT-FAJARDO-DIME-MISC-APP-TEST-SUITE * Normative Reference DRAFT-ACEE-MIP4-BULK-REVOCATION * Normative Reference DRAFT-MCCANN-DIME-RFC4004BIS RFC3957: Authentication, Authorization, and Accounting (AAA) Registration Keys for Mobile IPv4 (27 pages) * Replaces DRAFT-IETF-MOBILEIP-AAA-KEY * Normative Reference RFC2794 * Informative Reference BCP78 * Normative Reference RFC2486 * Informative Reference RFC2865 * Normative Reference RFC3344 * Informative Reference RFC2977 * Informative Reference RFC3127 * Normative Reference RFC2104 * Informative Reference RFC3588 * Normative Reference BCP14 * Normative Reference RFC2356 * Normative Reference RFC3012 * Possible Reference STD1 * Normative Reference BCP26 * Normative Reference RFC1750 * Normative Reference RFC4004 * Informative Reference RFC4067 * Normative Reference RFC4433 * Informative Reference RFC5944 * Informative Reference RFC4857 * Reference DRAFT-NAKHJIRI-RADIUS-MIP4 * Informative Reference DRAFT-VIDYA-MIPSHOP-HANDOVER-KEYS-AAA * Informative Reference RFC5419 * Reference DRAFT-NAKHJIRI-PMIP-KEY * Normative Reference RFC5030 * Normative Reference DRAFT-FAJARDO-DIME-INTEROP-TEST-SUITE * Informative Reference RFC4988 * Informative Reference DRAFT-DEVARAPALLI-MIP6-AUTHPROTOCOL-BOOTSTRAP * Normative Reference DRAFT-LIOR-MIPKEYS-EAP * Normative Reference DRAFT-QIN-MIP6-DSBOOTSTRAPPING * Informative Reference DRAFT-RAM-DHC-DHCPV6-AAKEY * Informative Reference DRAFT-VANDERVEEN-AAA-ROAMING * Normative Reference DRAFT-FAJARDO-DIME-MISC-APP-TEST-SUITE * Normative Reference DRAFT-MCCANN-DIME-RFC4004BIS * Normative Reference DRAFT-MCCANN-MIP4-MBB * Informative Reference DRAFT-PERKINS-MEXT-HATUNADDR * Informative Reference DRAFT-PERKINS-NETEXT-HATUNADDR RFC4064: Experimental Message, Extensions, and Error Codes for Mobile IPv4 (11 pages) * Normative Reference RFC1700 * Informative Reference BCP78 * Informative Reference RFC3012 * Informative Reference RFC3115 * Possible Reference RFC768 * Normative Reference RFC3232 * Normative Reference BCP14 * Informative Reference BCP82 * Normative Reference RFC3344 RFC4093: Problem Statement: Mobile IPv4 Traversal of Virtual Private Network (VPN) Gateways (19 pages) * Replaces DRAFT-IETF-MOBILEIP-VPN-PROBLEM-STATEMENT-REQ * Informative Reference BCP78 * Informative Reference RFC1918 * Normative Reference RFC3344 * Informative Reference BCP5 * Informative Reference RFC3519 * Informative Reference RFC2003 * Informative Reference RFC3715 * Informative Reference RFC3947 * Informative Reference BCP14 * Informative Reference RFC2401 * Informative Reference RFC2119 * Informative Reference RFC2131 * Informative Reference RFC5265 * Informative Reference DRAFT-DEVARAPALLI-MIP4-MOBIKE-CONNECTIVITY * Informative Reference RFC5266 * Informative Reference DRAFT-MEGHANA-MIP4-MOBIKE-OPTIMIZATIONS * Informative Reference RFC6071 RFC4433: Mobile IPv4 Dynamic Home Agent (HA) Assignment (25 pages) * Normative Reference RFC2794 * Normative Reference BCP78 * Normative Reference RFC3012 * Normative Reference RFC3344 * Normative Reference RFC3957 * Normative Reference BCP14 * Normative Reference BCP34 * Normative Reference RFC2132 * Possible Reference RFC2119 * Informative Reference RFC5563 * Normative Reference DRAFT-GONDI-NETLMM-PMIP-AAAM * Normative Reference DRAFT-DOSWALD-ROBERT-MIP4-BTN-FMIPV4 * Reference DRAFT-YAO-OPSAWG-ANYCAST-PING * Normative Reference DRAFT-CUI-NETLMM-MIP-INTERACTIONS * Informative Reference DRAFT-PATIL-MEXT-DMM-APPROACHES * Informative Reference DRAFT-PATIL-DMM-ISSUES-AND-APPROACHES2DMM RFC4636: Foreign Agent Error Extension for Mobile IPv4 (6 pages) * Updates RFC3344 * Normative Reference BCP78 * Normative Reference RFC3344 * Normative Reference RFC3543 * Normative Reference BCP14 * Normative Reference STD6 * Possible Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC4721 RFC4721: Mobile IPv4 Challenge/Response Extensions (Revised) (26 pages) * Replaces DRAFT-IETF-MOBILEIP-RFC3012BIS * Obsoletes RFC3012 * Updates RFC3344 * Normative Reference RFC1256 * Normative Reference RFC2794 * Normative Reference BCP78 * Normative Reference RFC3012 * Normative Reference RFC2865 * Normative Reference RFC4086 * Normative Reference RFC3344 * Normative Reference BCP106 * Normative Reference RFC2119 * Normative Reference RFC4636 * Normative Reference RFC2104 * Normative Reference BCP14 * Normative Reference RFC1321 * Possible Reference STD1 * Normative Reference RFC1994 * Normative Reference RFC4881 * Possible Reference DRAFT-IETF-IDR-BGP4-MIBV2 * Normative Reference DRAFT-IETF-MIP4-RFC2006BIS * Normative Reference RFC4742 * Normative Reference RFC5944 * Normative Reference RFC4857 * Normative Reference RFC5030 * Normative Reference RFC4988 * Informative Reference RFC5446 * Informative Reference DRAFT-XU-RRG-HRA * Normative Reference DRAFT-MCCANN-MIP4-MBB * Reference DRAFT-YAO-MIP4-MOBILE-AGENT-PROXY * Normative Reference DRAFT-SHEIKH-TRUE-MOBILITY * Possible Reference DRAFT-HARES-BGP-PATH-SELECT-BIB * Normative Reference DRAFT-WHITE-BGPBGP RFC4857: Mobile IPv4 Regional Registration (35 pages) * Normative Reference RFC4282 * Normative Reference RFC1256 * Normative Reference RFC2794 * Normative Reference RFC3846 * Informative Reference RFC3012 * Informative Reference RFC3957 * Normative Reference RFC3344 * Informative Reference RFC4004 * Normative Reference RFC3519 * Normative Reference RFC4721 * Informative Reference BCP78 * Normative Reference BCP14 * Normative Reference RFC3024 * Normative Reference RFC2119 * Normative Reference RFC4881 * Normative Reference DRAFT-IETF-MIP4-RFC2006BIS * Informative Reference RFC5944 * Possible Reference DRAFT-OHBA-802DOT21-BASIC-SCHEMA * Reference DRAFT-VIDYA-IP-MOBILITY-MULTIHOMING-INTERACTIONS * Informative Reference DRAFT-PALLE-PCE-STATEFUL-PCE-P2MP * Informative Reference DRAFT-PALLE-PCE-STATEFUL-PCE-INITIATED-P2MP-LSP RFC4881: Low-Latency Handoffs in Mobile IPv4 (64 pages) * Normative Reference RFC1256 * Informative Reference BCP78 * Normative Reference RFC4303 * Normative Reference RFC4857 * Normative Reference RFC3344 * Normative Reference RFC4721 * Informative Reference BCP26 * Normative Reference BCP14 * Normative Reference STD5 * Normative Reference RFC3024 * Normative Reference STD37 * Normative Reference RFC2784 * Normative Reference RFC2404 * Informative Reference RFC4306 * Informative Reference RFC4957 * Normative Reference DRAFT-OHBA-MOBOPTS-MPA-FRAMEWORK * Informative Reference DRAFT-OHBA-MOBOPTS-MPA-IMPLEMENTATION * Informative Reference DRAFT-OHBA-802DOT21-BASIC-SCHEMA * Reference DRAFT-VIDYA-IP-MOBILITY-MULTIHOMING-INTERACTIONS * Normative Reference RFC6252 * Normative Reference DRAFT-DOSWALD-ROBERT-MIP4-BTN-FMIPV4 RFC4917: Mobile IPv4 Message String Extension (7 pages) * Normative Reference RFC3629 * Normative Reference BCP78 * Normative Reference RFC2865 * Normative Reference RFC3344 * Normative Reference STD63 * Normative Reference BCP14 * Normative Reference RFC2434 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC6098 * Normative Reference DRAFT-POT-WEBDAV-RESOURCE-SHARING RFC4988: Mobile IPv4 Fast Handovers (28 pages) * Informative Reference RFC3957 * Informative Reference BCP78 * Normative Reference RFC4068 * Normative Reference RFC3344 * Normative Reference RFC4065 * Normative Reference RFC2460 * Normative Reference RFC1256 * Normative Reference RFC4721 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference RFC2131 * Normative Reference DRAFT-YOKOTA-MIPSHOP-PFMIPV6 * Informative Reference RFC5949 * Normative Reference DRAFT-DOSWALD-ROBERT-MIP4-BTN-FMIPV4 * Normative Reference DRAFT-LIU-MULTIMOB-MULTICAST-RECEIVER-MOBILITY * Informative Reference DRAFT-KWON-QMIPV4 * Normative Reference DRAFT-YOKOTA-DMM-SCENARIO * Informative Reference DRAFT-CHAN-DISTRIBUTED-MOBILITY-PS * Informative Reference DRAFT-CHAN-DMM-FRAMEWORK-GAP-ANALYSIS * Informative Reference DRAFT-LIU-DMM-BEST-PRACTICES-GAP-ANALYSIS * Informative Reference DRAFT-CHAN-DMM-FRAMEWORK RFC5030: Mobile IPv4 RADIUS Requirements (9 pages) * Normative Reference RFC3957 * Informative Reference BCP78 * Normative Reference RFC2865 * Normative Reference RFC2866 * Normative Reference RFC2867 * Informative Reference RFC2868 * Informative Reference RFC2869 * Normative Reference RFC3344 * Normative Reference RFC4004 * Normative Reference RFC2977 * Normative Reference RFC4721 * Normative Reference RFC4962 * Informative Reference RFC3576 * Informative Reference RFC3579 * Normative Reference BCP132 * Informative Reference RFC3580 * Normative Reference RFC2119 * Normative Reference BCP14 RFC5177: Network Mobility (NEMO) Extensions for Mobile IPv4 (26 pages) * Normative Reference RFC2794 * Normative Reference RFC2453 * Informative Reference RFC3963 * Possible Reference RFC2002 * Normative Reference RFC3344 * Normative Reference RFC1323 * Normative Reference RFC4271 * Normative Reference RFC2119 * Normative Reference RFC2328 * Normative Reference BCP14 * Normative Reference RFC2434 * Normative Reference RFC2006 * Informative Reference BCP78 * Possible Reference STD1 * Informative Reference RFC4885 * Normative Reference BCP26 * Updates RFC6626 * Informative Reference RFC6098 * Normative Reference RFC6626 * Normative Reference DRAFT-IETF-MIP4-NEMOV4-FA * Normative Reference DRAFT-MAKELA-MIP4-NEMO-HAARO * Normative Reference RFC6521 * Informative Reference DRAFT-GUNDAVELLI-MIP4-MULTIPLE-TUNNEL-SUPPORT RFC5265: Mobile IPv4 Traversal across IPsec-Based VPN Gateways (39 pages) * Replaces DRAFT-IETF-MOBILEIP-VPN-PROBLEM-SOLUTION * Informative Reference RFC4093 * Informative Reference RFC4282 * Informative Reference BCP78 * Normative Reference RFC4303 * Normative Reference RFC5226 * Informative Reference RFC2002 * Normative Reference RFC3344 * Normative Reference BCP5 * Normative Reference RFC3519 * Informative Reference RFC3456 * Normative Reference RFC4301 * Normative Reference RFC3947 * Informative Reference RFC3776 * Informative Reference RFC4555 * Normative Reference RFC3948 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference BCP14 * Normative Reference RFC5266 * Informative Reference RFC5454 * Informative Reference RFC6071 RFC5266: Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE) (15 pages) * Replaces DRAFT-DEVARAPALLI-MIP4-MOBIKE-CONNECTIVITY * Informative Reference RFC4093 * Informative Reference RFC3519 * Informative Reference RFC3024 * Normative Reference RFC3344 * Normative Reference RFC5265 * Normative Reference RFC4301 * Informative Reference RFC2409 * Informative Reference RFC3947 * Normative Reference RFC4306 * Informative Reference BCP78 * Normative Reference RFC4555 * Informative Reference RFC3948 * Normative Reference RFC2119 * Normative Reference BCP14 * Informative Reference RFC5454 * Informative Reference DRAFT-MARTINELLI-CCAMP-OPTICAL-IMP-SIGNALING * Informative Reference RFC6071 * Normative Reference DRAFT-KOUVELAS-LISP-RELIABLE-TRANSPORT RFC5454: Dual-Stack Mobile IPv4 (18 pages) * Normative Reference RFC5226 * Normative Reference RFC2460 * Informative Reference RFC5266 * Informative Reference RFC5265 * Normative Reference BCP14 * Informative Reference RFC2004 * Normative Reference RFC3963 * Informative Reference RFC3168 * Informative Reference RFC3588 * Normative Reference RFC3633 * Normative Reference RFC3775 * Normative Reference RFC3024 * Informative Reference RFC2784 * Normative Reference RFC4213 * Informative Reference BCP136 * Informative Reference RFC2983 * Normative Reference RFC3344 * Informative Reference RFC2710 * Normative Reference RFC3519 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference BCP26 * Informative Reference RFC3810 * Informative Reference RFC5563 * Informative Reference DRAFT-IETF-MIP4-MULTIPLE-TUNNEL-SUPPORT * Informative Reference RFC6301 * Normative Reference RFC6180 * Informative Reference DRAFT-CHAN-DISTRIBUTED-MOBILITY-PS RFC5944: IP Mobility Support for IPv4, Revised (100 pages) * Obsoletes RFC3344 * Informative Reference RFC1332 * Normative Reference BCP106 * Informative Reference RFC3519 * Normative Reference RFC4721 * Informative Reference RFC2356 * Normative Reference RFC2104 * Normative Reference BCP14 * Informative Reference BCP38 * Normative Reference RFC2006 * Normative Reference RFC2004 * Normative Reference RFC2005 * Informative Reference RFC2002 * Normative Reference RFC2003 * Informative Reference RFC2988 * Informative Reference STD51 * Informative Reference RFC1661 * Possible Reference RFC4086 * Normative Reference RFC5905 * Informative Reference RFC4857 * Informative Reference BCP50 * Normative Reference RFC1256 * Possible Reference RFC5741 * Informative Reference RFC3220 * Normative Reference RFC3024 * Normative Reference STD37 * Normative Reference RFC2784 * Informative Reference RFC925 * Informative Reference RFC3344 * Informative Reference RFC3543 * Normative Reference RFC1321 * Informative Reference BCP28 * Informative Reference RFC2863 * Informative Reference RFC2290 * Normative Reference STD5 * Normative Reference STD6 * Possible Reference RFC2119 * Normative Reference BCP26 * Informative Reference RFC2131 * Informative Reference RFC3957 * Normative Reference RFC2794 * Normative Reference RFC3115 * Informative Reference RFC3135 * Normative Reference RFC4302 * Informative Reference RFC2757 * Informative Reference RFC1144 * Informative Reference DRAFT-YEGIN-IP-MOBILITY-ORCHESTRATOR * Normative Reference RFC5980 * Informative Reference RFC5979 * Normative Reference RFC6098 * Normative Reference DRAFT-DREIBHOLZ-RSERPOOL-APPLIC-MOBILITY * Normative Reference DRAFT-LIU-DMM-FLOWS-DISTRIBUTION-AND-HANDOFF * Normative Reference RFC6626 * Informative Reference RFC6252 * Normative Reference RFC6521 * Informative Reference RFC6275 * Normative Reference DRAFT-IETF-MIP4-MULTIPLE-TUNNEL-SUPPORT * Normative Reference RFC6306 * Informative Reference RFC6139 * Normative Reference RFC6830 * Informative Reference RFC6618 * Informative Reference RFC6301 * Normative Reference DRAFT-SHYAM-MSHN-IPV6 * Normative Reference RFC6245 * Normative Reference DRAFT-PERKINS-MEXT-HATUNADDR * Possible Reference DRAFT-PETRESCU-MIP4-TUNTYPE-CHANGE * Normative Reference DRAFT-SHIMA-CLOUDS-NET-PORTABILITY-REQS-AND-MODELS * Reference DRAFT-LONVICK-PRIVATE-TAX * Informative Reference RFC6636 * Possible Reference RFC6740 * Normative Reference DRAFT-PERKINS-NETEXT-HATUNADDR * Informative Reference DRAFT-GU-STATEMIGRATION-FRAMEWORK * Informative Reference RFC7333 * Informative Reference DRAFT-KUTSCHER-ICNRG-CHALLENGES * Normative Reference DRAFT-YEGIN-DMM-CNET-HOMING * Informative Reference DRAFT-YEGIN-DMM-ONDEMAND-MOBILITY * Normative Reference DRAFT-SHYAM-SITE-MULTI * Normative Reference DRAFT-SHYAM-REAL-IP-FRAMEWORK * Normative Reference DRAFT-IETF-LISP-INTRODUCTION * Informative Reference DRAFT-IRTF-ICNRG-CHALLENGES RFC6098: Generic Notification Message for Mobile IPv4 (33 pages) * Replaces DRAFT-DENG-MIP4-GENERIC-NOTIFICATION-MESSAGE * Informative Reference RFC5226 * Normative Reference RFC4086 * Normative Reference RFC4917 * Informative Reference RFC5177 * Normative Reference RFC5905 * Normative Reference RFC3543 * Normative Reference BCP106 * Possible Reference RFC5741 * Normative Reference RFC5944 * Normative Reference RFC2119 * Informative Reference BCP26 * Normative Reference BCP14 RFC6245: Generic Routing Encapsulation (GRE) Key Extension for Mobile IPv4 (8 pages) * Normative Reference RFC2890 * Normative Reference RFC2119 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC5944 * Normative Reference RFC3024 * Normative Reference RFC2784 * Informative Reference DRAFT-NARTEN-NVO3-OVERLAY-PROBLEM-STATEMENT * Informative Reference RFC7364 RFC6521: Home Agent-Assisted Route Optimization between Mobile IPv4 Networks (53 pages) * Replaces DRAFT-MAKELA-MIP4-NEMO-HAARO * Informative Reference RFC4282 * Normative Reference RFC5226 * Informative Reference RFC4086 * Informative Reference STD13 * Normative Reference RFC5177 * Informative Reference BCP106 * Informative Reference RFC3543 * Informative Reference RFC6275 * Normative Reference RFC3519 * Normative Reference RFC2784 * Possible Reference RFC5741 * Informative Reference RFC1035 * Normative Reference RFC2004 * Normative Reference BCP14 * Normative Reference RFC2003 * Normative Reference RFC5944 * Normative Reference RFC2119 * Normative Reference BCP26 RFC6626: Dynamic Prefix Allocation for Network Mobility for Mobile IPv4 (NEMOv4) (5 pages) * Updates RFC5177 * Normative Reference RFC2794 * Normative Reference RFC5177 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC5944 * Normative Reference RFC2119 * Informative Reference DRAFT-IETF-MIP4-MULTIPLE-TUNNEL-SUPPORT Multiple Interfaces (mif) ------------------------- Charter Last Modified: 2013-03-13 Current Status: Active Chairs: Margaret Wasserman Hui Deng Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Mailing Lists: General Discussion: mif@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/mif Archive: http://www.ietf.org/mail-archive/web/mif Description of Working Group: Nodes attached to multiple networks may encounter problems due to conflict of network configuration information and/or simultaneous use of the multiple available networks. This can happen over multiple physical network interfaces, a combination of physical and virtual interfaces (VPNs or tunnels), or even indirectly through multiple default routers being on the same link. For instance, current laptops and smartphones typically have multiple access network interfaces. The MIF problem statement document [RFC6418] enumerates the problems into 3 categories: 1. Lack of consistent and distinctive management of configuration elements, associated with different networks. 2. Inappropriate mixed use of configuration elements, associated with different networks, in the course of a particular network activity / connection. 3. Use of a particular network, not consistent with the intent of the scenario / involved parties, leading to connectivity failure and / or other undesired consequences. The purpose of the MIF working group is to describe the architecture detailing how devices attach to and operate in multiple networks. The group shall also analyze how applications can be influenced by these existing mechanisms. The WG shall employ and refer to existing IETF work in this area, including, for instance, strong/weak models (RFC 1122), default address selection (RFC 6724), ICE and other mechanisms higher layers can use for address selection, DHCP mechanisms, Router Advertisement mechanisms, and DNS recommendations. The focus of the working group should be on documenting the system level effects to host IP stacks and identification of gaps between the existing IETF recommendations and existing practice. Having completed some of its initial goals the group is also developing the following: 1. An incrementally deployable architecture, defining a consistent approach and recommended practices for handling sets of network configuration objects by hosts, attached to multiple networks, which enable hosts to improve network connectivity for the host's applications and users. Each of these sets of network configuration objects is referred to collectively as a provisioning domain (PVD). 2. A set of requirements for changes to or the uses of protocols, that provide network configuration information, to enable improved handling of multiple sets of network configuration in networks and hosts. For example, requirements for DHCPv6 options, Neighbor Discovery options etc. to communicate association of the configuration information with particular networks. 3. In cooperation with other working groups, uses of existing protocols in accordance with the requirements produced under item 2. Any changes of function of protocols are out of scope. 4. A MIF API: While no changes are required for applications to run on multiple interface hosts, a new API could provide additional services to applications running on hosts attached to multiple networks. For instance, these services could assist advanced applications in having greater control over first-hop, source address and/or DNS resolver, interface and other network configuration element selection. This API will be defined as an abstract interface specification. That is, specific details about mapping to operating system primitives or programming languages will be left out, and the API will not be specified in terms of familiar APIs (e.g., "BSD sockets API"). In addition to the new API, the behavior of existing APIs may be changed to improve the behavior of unmodified applications. 5. Guidelines to applications, to provide an improved connectivity experience when the host is attached to multiple networks or there is a change in the set of networks the host is attached to, e.g., via MIF API usage. 6. The MIF working group will document either as part of the MIF API specification, as part of the MIF architecture document, or in a separate document, the issues and requirements for a high-level MIF user interface that would allow the user to exert control over how individual applications or application roles make use of different provisioning domains and network interfaces. 7. A specification for the format, generation and usage of PVD IDs. Network discovery and selection on lower layers as defined by RFC 5113 is out of scope. With the exception of identifying requirements for additional DHCPv6 and/or ND options, as well as requirements for possible related changes in these protocols, the group shall not assume any software beyond basic IP protocol support on its peers or in network hosts. No work will be done to enable traffic flows to move from one interface to another. The group recognizes existing work on mechanisms that require peer or network support for moving traffic flows such as RFC 5206, RFC 4980 and the use of multiple care-of addresses in Mobile IPv6. This group does not work on or impact such mechanisms. Future work in this area requires rechartering the working group or asking other, specialized working groups (such as DHC or 6MAN) to deal with specific issues. Goals and Milestones: Done - WG chartered Done - Initial draft on problem statement adopted by the WG Done - Initial draft on existing practices adopted by the WG Done - Initial draft on analysis of existing practices adopted by the WG Done - Problem statement draft submitted to the IESG for publication as an Informational RFC Done - Existing practices draft submitted to the IESG for publication as an Informational RFC Done - Initial WG draft on advanced DNS server selection solution Done - Initial WG draft on MIF API extension Done - Analysis draft submitted to the IESG for publication as an Informational RFC Done - Submit advanced DNS server selection solution to IESG for publication as a Proposed Standard RFC Done - Initial draft on MPvD architecture adopted by the WG Jun 2014 - MPvD Architecture draft submitted to the IESG for publication as an Informational RFC Jul 2014 - Initial draft on the requirements for changes to DHCPv6 and ND adopted by the WG Jul 2014 - Initial draft on the guidance to applications adopted by the WG Jul 2014 - MIF API extension solution to IESG for publication as an Informational RFC Jul 2014 - Initial draft on high level MIF API adopted by the WG Jul 2014 - Initial draft on format and usage of PvD ID adoped by the WG Nov 2014 - Initial draft on DHCPv6 and ND extention adopted by the WG Nov 2014 - Requirements for changes to DHCPv6 and ND submitted to the IESG for publication as an Informational RFC Nov 2014 - Guidance to applications submitted to the IESG for publication as an Informational RFC Internet-Drafts: - Multiple Provisioning Domain Architecture [draft-anipko-mif-mpvd-arch-05] (16 pages) - MIF API consideration [draft-ietf-mif-api-extension-05] (17 pages) - Current Practices for Multiple-Interface Hosts [draft-ietf-mif-current-practices-12] (21 pages) - DHCPv6 Route Options [draft-ietf-mif-dhcpv6-route-option-05] (22 pages) - Improved Recursive DNS Server Selection for Multi-Interfaced Nodes [draft-ietf-mif-dns-server-selection-12] (29 pages) - Happy Eyeballs Extension for Multiple Interfaces [draft-ietf-mif-happy-eyeballs-extension-06] (11 pages) - Multiple Provisioning Domain Architecture [draft-ietf-mif-mpvd-arch-11] (22 pages) - Support for multiple provisioning domains in DHCPv6 [draft-ietf-mif-mpvd-dhcp-support-01] (10 pages) - Identification of provisioning domains [draft-ietf-mif-mpvd-id-01] (6 pages) - Support for multiple provisioning domains in IPv6 Neighbor Discovery Protocol [draft-ietf-mif-mpvd-ndp-support-01] (11 pages) - Multiple Interfaces and Provisioning Domains Problem Statement [draft-ietf-mif-problem-statement-15] (22 pages) Requests for Comments: RFC6418: Multiple Interfaces and Provisioning Domains Problem Statement (22 pages) * Replaces DRAFT-BLANCHET-MIF-PROBLEM-STATEMENT * Informative Reference RFC3484 * Informative Reference RFC5221 * Informative Reference RFC5220 * Informative Reference BCP5 * Informative Reference RFC1122 * Informative Reference RFC6316 * Informative Reference RFC5533 * Informative Reference BCP38 * Informative Reference RFC3315 * Informative Reference STD51 * Informative Reference RFC5245 * Informative Reference RFC1661 * Informative Reference RFC1918 * Informative Reference RFC5206 * Informative Reference RFC6275 * Possible Reference RFC5741 * Informative Reference RFC2827 * Informative Reference RFC6147 * Informative Reference RFC4294 * Informative Reference RFC1136 * Informative Reference RFC3542 * Informative Reference RFC2474 * Informative Reference RFC6182 * Informative Reference RFC4960 * Informative Reference RFC4861 * Informative Reference RFC5648 * Informative Reference STD3 * Informative Reference RFC2131 * Informative Reference RFC6419 * Informative Reference RFC3704 * Informative Reference RFC5014 * Informative Reference BCP84 * Informative Reference RFC5113 * Informative Reference DRAFT-IRTF-NMRG-AN-GAP-ANALYSIS * Informative Reference RFC6731 * Normative Reference RFC6419 * Informative Reference RFC6897 * Informative Reference DRAFT-IETF-6MAN-ADDR-SELECT-CONSIDERATIONS * Informative Reference RFC7050 * Informative Reference RFC7286 * Informative Reference RFC6629 * Informative Reference DRAFT-TEMPLIN-MIF-IRONAPP * Informative Reference DRAFT-IETF-MIF-HAPPY-EYEBALLS-EXTENSION * Informative Reference DRAFT-CAO-MIF-SRV-DIS-PS * Informative Reference DRAFT-CAO-HOMENET-MIF-SRVDIS * Informative Reference DRAFT-LIU-MIF-FLOW-CONTROL-PS * Informative Reference DRAFT-ANIPKO-MIF-MPVD-ARCH * Informative Reference DRAFT-IETF-MIF-MPVD-ARCH * Reference DRAFT-PSKIM-MIF-CAPACITY-NEMO * Informative Reference DRAFT-GENG-HOMENET-MPVD-USE-CASES RFC6419: Current Practices for Multiple-Interface Hosts (21 pages) * Replaces DRAFT-MRW-MIF-CURRENT-PRACTICES * Informative Reference RFC3484 * Normative Reference RFC6418 * Informative Reference RFC1122 * Possible Reference RFC5741 * Informative Reference RFC4311 * Informative Reference STD3 * Informative Reference RFC6418 * Informative Reference RFC6897 * Informative Reference DRAFT-TEMPLIN-MIF-IRONAPP * Informative Reference DRAFT-CAO-MIF-SRV-DIS-PS * Possible Reference DRAFT-AKHTER-LMAP-FRAMEWORK * Informative Reference DRAFT-CAO-HOMENET-MIF-SRVDIS * Informative Reference DRAFT-ANIPKO-MIF-MPVD-ARCH * Possible Reference DRAFT-FOLKS-LMAP-FRAMEWORK * Informative Reference DRAFT-IETF-LMAP-FRAMEWORK * Informative Reference DRAFT-IETF-MIF-MPVD-ARCH * Reference DRAFT-PSKIM-MIF-CAPACITY-NEMO RFC6731: Improved Recursive DNS Server Selection for Multi-Interfaced Nodes (29 pages) * Replaces DRAFT-SAVOLAINEN-MIF-DNS-SERVER-SELECTION * Normative Reference RFC2317 * Informative Reference RFC4191 * Informative Reference RFC3442 * Informative Reference RFC3397 * Normative Reference RFC3396 * Informative Reference RFC6106 * Informative Reference RFC6418 * Informative Reference RFC6147 * Possible Reference RFC5741 * Informative Reference RFC4193 * Normative Reference RFC4242 * Informative Reference RFC3646 * Normative Reference RFC3596 * Normative Reference BCP20 * Normative Reference RFC3315 * Normative Reference RFC2132 * Normative Reference RFC2119 * Normative Reference BCP14 * Informative Reference DRAFT-LIU-RUNNING-MULTIPLE-PREFIXES * Informative Reference DRAFT-IETF-6MAN-ADDR-SELECT-CONSIDERATIONS * Normative Reference RFC7157 * Normative Reference DRAFT-IETF-MIF-HAPPY-EYEBALLS-EXTENSION * Normative Reference DRAFT-CAO-MIF-SRV-DIS-PS * Normative Reference DRAFT-CAO-HOMENET-MIF-SRVDIS * Informative Reference DRAFT-ANIPKO-MIF-MPVD-ARCH * Informative Reference DRAFT-LIU-V6OPS-RUNNING-MULTIPLE-PREFIXES * Informative Reference DRAFT-IETF-MIF-MPVD-ARCH Network Time Protocol (ntp) --------------------------- Charter Last Modified: 2011-12-09 Current Status: Active Chair: Karen O'Donoghue Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Brian Haberman Mailing Lists: General Discussion: ntpwg@lists.ntp.org To Subscribe: https://lists.ntp.org/listinfo/ntpwg Archive: http://lists.ntp.org/pipermail/ntpwg/ Description of Working Group: The Network Time Protocol (NTP) is widely deployed and used in the Internet. However, the standardization status of this protocol has lagged in the IETF. RFC 1305 (NTP version 3) was published in March 1992 and remains unchanged and at Draft Standard status. RFC 1305 represents the majority of full NTP implementations deployed today. RFC 2030 (SNTP version 4) was published as an Informational RFC in October 1996 as a lightweight version of NTP for deployments not requiring the full functionality of NTP. SNTP now represents the majority of both NTP traffic and NTP implementation issues on the Internet. A good deal of work has been produced in the NTP community updating both NTPv3 and SNTPv4. This work is ongoing and available through the collaborative development effort in the NTP community, but it has not been reflected back into the NTP specifications. The goal of this working group is to document NTPv4 based on the extensive work of the NTP community and to advance the standardization status of NTP. It is an explicit goal of this effort to have NTPv4 interoperate with the deployed base avoiding any backwards-incompatible changes. A number of topics have been raised as potential work items for an update to NTP including support for IPv6, security considerations including authentication, automatic configuration including possible requirements for DHCP, and algorithm improvements. This working group will focus first on delivering NTPv4 and will defer additional development efforts until after the delivery of NTPv4. Support for IPv6 and defining mechanisms for securing NTP transactions is considered part of the core NTPv4 functionality. Potential further modifications and additions to the NTP protocol will be documented for possible further work beyond the initial NTPv4 effort. The working group will initially focus on the following deliverables: 1. NTPv4 Scope and Requirements Document (documenting the scope of the NTPv4 update and identifying issues deferred for future work). 2. NTPv4 Protocol Specification (documenting the protocol on the wire) 3. NTPv4 Architecture and Algorithms Specification (documenting the architecture, mathematical algorithms, and behavior of NTP servers and clients) 4. NTPv4 MIB (provision for management and monitoring of NTP via SNMP) Goals and Milestones: Done - NTP BOF at IETF 61 Done - NTP WG Charter Approved Done - Draft of Scope and Requirements Document Done - Draft of NTP Protocol Specification Done - Draft of MIB Specification Done - Draft of NTP Algorithms Specification Done - Draft of NTP Autokey Specification - Informational RFC Dec 2007 - WG Last Call NTP Protocol Specification Dec 2007 - WG Last Call NTP MIB Specification Dec 2007 - Draft of NTP Control Protocol - Informational RFC Mar 2008 - WG Last Call NTP Autokey Specification - Informational RFC Mar 2008 - WG Last Call NTP Control Protocol - Informational RFC Internet-Drafts: - Network Time Protocol Version 4: Autokey Specification [draft-ietf-ntp-autokey-08] (58 pages) - Using UDP Checksum Trailers in the Network Time Protocol (NTP) [draft-ietf-ntp-checksum-trailer-01] (10 pages) - Protecting Network Time Security Messages with the Cryptographic Message Syntax (CMS) [draft-ietf-ntp-cms-for-nts-message-02] (16 pages) - Network Time Protocol (NTP) Server Option for DHCPv6 [draft-ietf-ntp-dhcpv6-ntp-opt-06] (9 pages) - The Network Time Protocol Version 4 (NTPv4) Extension Fields [draft-ietf-ntp-extension-field-02] (9 pages) - Network Time Security [draft-ietf-ntp-network-time-security-08] (35 pages) - The Network Time Protocol Version 4 Algorithm Specification [draft-ietf-ntp-ntpv4-algorithms-01] (25 pages) - Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4) [draft-ietf-ntp-ntpv4-mib-07] (26 pages) - Network Time Protocol Version 4: Protocol and Algorithms Specification [draft-ietf-ntp-ntpv4-proto-13] (110 pages) - Requirements for Network Time Protocol Version 4 [draft-ietf-ntp-reqs-01] (16 pages) - Using the Network Time Security Specification to Secure the Network Time Protocol [draft-ietf-ntp-using-nts-for-ntp-00] (16 pages) - Using UDP Checksum Trailers in the Network Time Protocol (NTP) [draft-mizrahi-ntp-checksum-trailer-02] (10 pages) - Using NTP Extension Fields without Authentication [draft-mizrahi-ntp-extension-field-03] (9 pages) Requests for Comments: RFC5905: Network Time Protocol Version 4: Protocol and Algorithms Specification (110 pages) * Obsoletes RFC1305 * Obsoletes RFC4330 * Informative Reference RFC1305 * Informative Reference RFC5906 * Normative Reference RFC768 * Normative Reference RFC793 * Informative Reference RFC1345 * Normative Reference RFC791 * Informative Reference RFC1321 * Informative Reference RFC5226 * Possible Reference RFC5741 * Normative Reference BCP14 * Informative Reference RFC4330 * Normative Reference RFC2119 * Informative Reference BCP26 * Normative Reference DRAFT-JIANG-DHC-SEDHCPV6 * Normative Reference DRAFT-IETF-ISIS-EXTENDED-SEQUENCE-NO-TLV * Informative Reference DRAFT-MATHEWSON-NO-GMTUNIXTIME * Informative Reference DRAFT-IETF-NTP-EXTENSION-FIELD * Informative Reference RFC7162 * Normative Reference DRAFT-ELKINS-V6OPS-IPV6-PDM-RECOMMENDED-USAGE * Normative Reference RFC7182 * Informative Reference DRAFT-IETF-MMUSIC-RFC2326BIS * Normative Reference RFC6787 * Informative Reference DRAFT-IETF-IPPM-REGISTRY-PASSIVE * Informative Reference DRAFT-IETF-RMT-FLUTE-SDP * Normative Reference RFC5944 * Informative Reference DRAFT-IRTF-NMRG-AN-GAP-ANALYSIS * Normative Reference RFC6726 * Normative Reference RFC6098 * Informative Reference RFC6407 * Normative Reference RFC5981 * Informative Reference DRAFT-IETF-PAYLOAD-RTP-HOWTO * Normative Reference RFC5907 * Informative Reference RFC6733 * Informative Reference RFC6765 * Informative Reference RFC6450 * Informative Reference DRAFT-IETF-RMT-SEC-DISCUSSION * Normative Reference RFC5906 * Normative Reference DRAFT-IETF-P2PSIP-DIAGNOSTICS * Informative Reference DRAFT-IETF-MMUSIC-RFC4566BIS * Informative Reference RFC7231 * Informative Reference RFC7234 * Informative Reference RFC7325 * Normative Reference RFC5908 * Normative Reference RFC6105 * Normative Reference DRAFT-IETF-DHC-SECURE-DHCPV6 * Normative Reference DRAFT-IETF-SIDR-RPSL-SIG * Normative Reference RFC6051 * Informative Reference RFC6817 * Normative Reference RFC6622 * Normative Reference DRAFT-IETF-AVT-PORTS-FOR-UCAST-MCAST-RTP * Informative Reference RFC6272 * Informative Reference RFC7094 * Normative Reference RFC6284 * Normative Reference RFC6222 * Informative Reference RFC6797 * Informative Reference DRAFT-JIANG-CONFIG-NEGOTIATION-PROTOCOL * Normative Reference DRAFT-BRANDENBURG-AVT-RTCP-FOR-IDMS * Informative Reference RFC7115 * Normative Reference DRAFT-FROST-MPLS-LOSS-DELAY * Normative Reference RFC6374 * Informative Reference RFC6302 * Informative Reference RFC6988 * Informative Reference DRAFT-IETF-TICTOC-1588OVERMPLS * Normative Reference DRAFT-JABLEY-DNSOP-VALIDATOR-BOOTSTRAP * Informative Reference RFC6754 * Normative Reference RFC7084 * Normative Reference DRAFT-BRANDENBURG-AVTCORE-RTCP-FOR-IDMS * Normative Reference RFC7272 * Informative Reference DRAFT-IETF-SIDR-BGPSEC-OPS * Normative Reference DRAFT-ASAEDA-XRBLOCK-RTCP-XR-SYNCHRONIZATION * Normative Reference DRAFT-MIZRAHI-TICTOC-CHECKSUM-TRAILER * Informative Reference DRAFT-IETF-TICTOC-PTP-MIB * Normative Reference DRAFT-ARKKO-CORE-SECURITY-ARCH * Informative Reference DRAFT-WILLIAMS-AVTCORE-CLKSRC * Normative Reference DRAFT-CLAISE-IPFIX-PROTOCOL-RFC5101BIS * Normative Reference RFC6776 * Normative Reference DRAFT-CLAISE-IPFIX-INFORMATION-MODEL-RFC5102BIS * Normative Reference RFC6843 * Normative Reference DRAFT-FBB-MPLS-GACH-ADV * Normative Reference RFC7212 * Normative Reference DRAFT-MIZRAHI-TICTOC-SECURITY-REQUIREMENTS * Normative Reference DRAFT-ODONOGHUE-NTPV4-CONTROL * Informative Reference DRAFT-IETF-AVTEXT-RTP-GROUPING-TAXONOMY * Normative Reference DRAFT-CHUNDURI-ISIS-EXTENDED-SEQUENCE-NO-TLV * Normative Reference RFC6812 * Normative Reference RFC7384 * Normative Reference RFC7011 * Informative Reference DRAFT-IETF-PPSP-PEER-PROTOCOL * Normative Reference DRAFT-BCD-6MAN-NTP-SERVER-RA-OPT * Normative Reference DRAFT-IPFIX-INFORMATION-MODEL-RFC5102BIS * Normative Reference DRAFT-ELKINS-V6OPS-IPV6-END-TO-END-RT-NEEDED * Normative Reference DRAFT-CUI-TICTOC-ENCRYPTED-SYNCHRONIZATION * Normative Reference DRAFT-GROSS-LEAP-SECOND * Normative Reference DRAFT-GROSS-AVTCORE-LEAP-SECOND * Normative Reference DRAFT-PERRIN-TLS-TACK * Informative Reference RFC7164 * Normative Reference RFC7273 * Normative Reference RFC7244 * Informative Reference DRAFT-SIBOLD-AUTOKEY * Informative Reference RFC6962 * Informative Reference DRAFT-VILLAMIZAR-MPLS-FORWARDING * Informative Reference DRAFT-BORMANN-APPAREA-BPACK * Reference DRAFT-SUN-IPPM-FLOWBASED-PM * Informative Reference DRAFT-OGUD-DHC-UDP-TIME-OPTION * Informative Reference DRAFT-MIZRAHI-NTP-EXTENSION-FIELD * Normative Reference DRAFT-SHPINER-MULTI-PATH-SYNCHRONIZATION * Normative Reference DRAFT-MIZRAHI-NTP-CHECKSUM-TRAILER * Normative Reference DRAFT-BAGNULO-IPPM-NEW-REGISTRY * Normative Reference DRAFT-BAGNULO-IPPM-NEW-REGISTRY-INDEPENDENT * Normative Reference DRAFT-MORTON-IPPM-LMAP-PATH * Normative Reference DRAFT-RUOSKA-ENCODING * Informative Reference DRAFT-CHEN-COLORING-BASED-IPFPM-FRAMEWORK * Normative Reference DRAFT-XIA-AVTEXT-SPLICING-NOTIFICATION * Normative Reference DRAFT-HERBERG-MANET-RFC6622-BIS * Informative Reference DRAFT-LENNOX-RAIAREA-RTP-GROUPING-TAXONOMY * Informative Reference DRAFT-IETF-TICTOC-PTP-ENTERPRISE-PROFILE * Informative Reference DRAFT-CHEN-IPPM-COLORING-BASED-IPFPM-FRAMEWORK * Informative Reference DRAFT-MM-NETCONF-TIME-CAPABILITY * Normative Reference DRAFT-IETF-DHC-SEDHCPV6 * Normative Reference RFC7293 * Normative Reference DRAFT-ACKERMANN-TICTOC-PDM-NTP-USAGE * Normative Reference DRAFT-MORTON-IPPM-REGISTRY-PDV * Normative Reference DRAFT-MORNULO-IPPM-REGISTRY-COLUMNS * Normative Reference DRAFT-MORNULO-IPPM-REGISTRY * Informative Reference DRAFT-LAURIE-RFC6962-BIS * Normative Reference DRAFT-MGLT-HOMENET-DNSSEC-VALIDATOR-DHC-OPTIONS * Normative Reference DRAFT-MORTON-BMWG-VIRTUAL-NET * Normative Reference DRAFT-IETF-TRANS-RFC6962-BIS * Normative Reference DRAFT-BOUAZIZI-MMTP * Normative Reference DRAFT-IETF-IPPM-REGISTRY-ACTIVE * Normative Reference DRAFT-ZHENG-IPPM-FRAMEWORK-PASSIVE * Reference DRAFT-JONGLEZ-BABEL-RTT-EXTENSION * Normative Reference DRAFT-LITKOWSKI-IDR-BGP-TIMESTAMP * Informative Reference DRAFT-IETF-IPPM-METRIC-REGISTRY * Normative Reference DRAFT-IETF-NTP-CHECKSUM-TRAILER * Informative Reference DRAFT-RASZUK-IDR-BGP-PR * Normative Reference DRAFT-IETF-TICTOC-MULTI-PATH-SYNCHRONIZATION * Normative Reference DRAFT-IETF-AVTEXT-SPLICING-NOTIFICATION * Normative Reference DRAFT-IETF-NTP-USING-NTS-FOR-NTP * Normative Reference DRAFT-MORNULEY-IPPM-INITIAL-REGISTRY * Normative Reference DRAFT-MIRSKY-MPLS-RESIDENCE-TIME * Informative Reference DRAFT-IETF-NTP-NETWORK-TIME-SECURITY * Informative Reference DRAFT-IETF-NTP-CMS-FOR-NTS-MESSAGE * Informative Reference DRAFT-WEIS-DELAY-DETECTION * Informative Reference DRAFT-ACEE-RTG-YANG-KEY-CHAIN * Informative Reference DRAFT-CARPENTER-ANIMA-GDN-PROTOCOL * Normative Reference DRAFT-MIRSKY-IPPM-TIME-FORMAT * Normative Reference DRAFT-WU-NTP-NTP-CFG * Normative Reference DRAFT-JIANG-DHC-SEDHCPV4 * Normative Reference DRAFT-DHCWG-DHC-RFC3315BIS * Normative Reference DRAFT-KUMARZHENG-BIER-PING RFC5906: Network Time Protocol Version 4: Autokey Specification (58 pages) * Informative Reference RFC1305 * Informative Reference RFC2875 * Normative Reference RFC5905 * Informative Reference RFC3279 * Informative Reference RFC4303 * Possible Reference RFC5741 * Informative Reference RFC4306 * Informative Reference RFC5280 * Informative Reference RFC2522 * Informative Reference RFC4302 * Informative Reference RFC4210 * Informative Reference RFC2412 * Informative Reference DRAFT-IETF-NTP-EXTENSION-FIELD * Informative Reference RFC5905 * Informative Reference DRAFT-MATHEWSON-NO-GMTUNIXTIME * Normative Reference RFC5908 * Normative Reference DRAFT-MIZRAHI-TICTOC-SECURITY-REQUIREMENTS * Informative Reference DRAFT-ODONOGHUE-NTPV4-CONTROL * Informative Reference RFC7384 * Informative Reference DRAFT-SIBOLD-AUTOKEY * Informative Reference DRAFT-MIZRAHI-NTP-EXTENSION-FIELD RFC5907: Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4) (26 pages) * Normative Reference RFC5905 * Normative Reference STD58 * Possible Reference RFC5741 * Normative Reference RFC2287 * Normative Reference BCP14 * Normative Reference RFC4001 * Informative Reference RFC3410 * Normative Reference RFC2580 * Normative Reference RFC2119 * Normative Reference RFC2578 * Normative Reference RFC2579 * Informative Reference DRAFT-ODONOGHUE-NTPV4-CONTROL * Informative Reference DRAFT-MM-NETCONF-TIME-CAPABILITY * Normative Reference DRAFT-WU-NTP-NTP-CFG RFC5908: Network Time Protocol (NTP) Server Option for DHCPv6 (9 pages) * Informative Reference RFC3971 * Informative Reference RFC4075 * Normative Reference RFC5226 * Normative Reference RFC5905 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC5906 * Informative Reference RFC4330 * Normative Reference RFC2119 * Normative Reference BCP26 * Informative Reference RFC7227 * Normative Reference RFC7084 * Informative Reference DRAFT-ODONOGHUE-NTPV4-CONTROL * Informative Reference DRAFT-PENTIKOUSIS-DECADE-DISCOVERY * Normative Reference DRAFT-MGLT-HOMENET-DNSSEC-VALIDATOR-DHC-OPTIONS Network-Based Mobility Extensions (netext) ------------------------------------------ Charter Last Modified: 2014-02-03 Current Status: Active Chairs: Rajeev Koodli Basavaraj Patil Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Brian Haberman Mailing Lists: General Discussion: netext@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/netext Archive: http://www.ietf.org/mail-archive/web/netext/ Description of Working Group: Proxy Mobile IPv6, specified in RFC 5213, is a network-based mobility protocol. It uses a Mobile Access Gateway (MAG) and a Local Mobility Anchor (LMA) to allow hosts to move around within a domain while keeping their address or address prefix stable. Proxy Mobile IPv6 has been incorporated into a number of products and deployments are starting. Certain deployment considerations, including localized routing and bulk refresh of lifetime are already emerging. The working group will focus on the following topics relevant for network-based mobility: Localized Routing: a specification for routing traffic between the MAG(s) without involving the LMA. That is, allow the MAGs to route traffic between hosts from one MAG to another, without being tunneled all the way to the LMA. This reduces latency and backhaul load. Applications such as voice can benefit from the reduced latency. The working group will produce a problem statement and a specification of the localized routing mechanism. Bulk Refresh: a specification of improving the signaling load for binding lifetime refresh. The current specifications call for the handling of each mobility session independent of each other. When a large number of hosts are served by a single MAG, a periodic refresh of the binding lifetimes can lead to a signaling storm. The purpose of the Bulk Refresh feature is to construct a protocol feature that allows such refreshes to occur on a per-MAG basis. LMA Redirection: a specification for allowing an LMA to redirect a MAG to another LMA. This is primarily needed as a way to perform load balancing. This functionality is complementary to implementation techniques that allow distributed MAG implementations to move tasks around without a visible impact at the protocol level, and the initial LMA discovery work in the NETLMM WG. An applicability statement describing the situations where the new functionality is or is not applicable has to be included in the specification. Hiding access technology changes from host IP layer: Proxy mobility is based on the assumption that changes in host IP stacks are undesirable. However, link layer implementations can hide the actually used physical interfaces from the IP stack. For instance, a "logical interface" at the IP layer may enable packet transmission and reception over different physical media. Such techniques can be used to achieve inter-access handovers or flow mobility, i.e., the movement of selected flows from one access technology to another. It is assumed that an IP layer interface can simultaneously and/or sequentially attach to multiple MAGs (possibly over multiple media). The hiding mechanisms also need to work together with existing RFC 5213 handover hint mechanisms. The specification of any actual link layer mechanisms is outside the scope of the working group, but the group works on the following: - Informational applicability statement that analyzes the issues involved with this approach and characterizes the contexts in which such use is or is not appropriate. - The working group will determine what protocol extensions are required between the Proxy Mobile IPv6 network nodes (MAGs and LMAs) to support the ability for an interface (at the IP layer) to transmit packets over different media, the ability to distribute specific traffic flows on different media components of that interface, and making this work with the handover hints in the base protocol. The relevant protocol extensions will be developed as necessary. Radius Extensions to PMIP6: In order to enable network based mobility using PMIP6, the policy profile needs to signal a set of attributes and policies to the MAG and LMA. New Radius attributes need to be specified that are relevant to PMIP6 based mobility. This work item will specify Radius extensions and attributes specific to PMIP6. The work in this charter is entirely internal to the network and does not affect host IP stack operation in any way (except perhaps through impacting packet forwarding capacity visible to the hosts). The working group is not allowed to specify new IP layer protocol mechanisms to signal mobility related events between the host and the network. The proposed activity will be complementary to the existing IETF Working Groups, notably the NETLMM and MEXT WGs. The NETEXT working group will also act as the primary forum where new extensions on top of the Proxy Mobile IPv6 protocol can be developed. The addition of such new extensions to the working group involves addition of the extension to this charter through the normal rechartering process. Goals and Milestones: Done - WG chartered Done - Initial WG draft on Bulk Refresh Done - Decision on the inclusion of possible additional work items Done - Initial WG draft on LMA Redirection Done - Initial WG draft on Localized Routing Problem Statement Done - Submit Bulk Refresh to IESG for publication as a Proposed Standard RFC Done - Submit LMA Redirection to IESG for publication as a Proposed Standard RFC Done - Initial WG document on RADIUS extensions to PMIP6 Done - Submit Localized Routing Problem Statement to IESG for publication as an Informational RFC Done - Initial WG draft on Localized Routing Solution Done - Submit Access Network Identifier (ANI) Option for PMIP6 to IESG for publication as a proposed standard Apr 2012 - Initial WG document on Service Selection for MIP6 and PMIP6 Apr 2012 - Initial WG document on EAP Attributes for WiFi - EPC Integration Oct 2012 - Submit Prefix Delegation for Proxy Mobile IPv6 to IESG for publication as a proposed standard Nov 2012 - Submit IPv4 Traffic Offload Selector Option for Proxy Mobile IPv6 to IESG for publication as a proposed Feb 2013 - Submit Proxy Mobile IPv6 Extensions to Support Flow Mobility to IESG for publication as a proposed standard Mar 2013 - Submit Service Selection for MIP6 and PMIP6 to the IESG for publication as a proposed standard Apr 2013 - Submit Logical Interface Support for multi-mode IP Hosts for publication as an Informational document May 2013 - Submit EAP Attributes for WiFi - EPC Integration to IESG for publication as a proposed standard Internet-Drafts: - Access Network Identifier (ANI) Option for Proxy Mobile IPv6 [draft-ietf-netext-access-network-option-13] (19 pages) - Extensions to the PMIPv6 Access Network Identifier Option [draft-ietf-netext-ani-location-08] (12 pages) - Bulk Binding Update Support for Proxy Mobile IPv6 [draft-ietf-netext-bulk-re-registration-12] (23 pages) - Logical-interface Support for Multi-access enabled IP Hosts [draft-ietf-netext-logical-interface-support-11] (18 pages) - Prefix Delegation Support for Proxy Mobile IPv6 [draft-ietf-netext-pd-pmip-14] (27 pages) - Separation of Control and User Plane for Proxy Mobile IPv6 [draft-ietf-netext-pmip-cp-up-separation-07] (12 pages) - Localized Routing for Proxy Mobile IPv6 [draft-ietf-netext-pmip-lr-10] (20 pages) - Mapping PMIPv6 QoS Procedures with WLAN QoS Procedures [draft-ietf-netext-pmip-qos-wifi-07] (23 pages) - A central policy controlling based PMIPv6 Solutions [draft-ietf-netext-pmip6-cpc-00] (19 pages) - Proxy Mobile IPv6 (PMIPv6) Localized Routing Problem Statement [draft-ietf-netext-pmip6-lr-ps-06] (14 pages) - Quality-of-Service Option for Proxy Mobile IPv6 [draft-ietf-netext-pmip6-qos-12] (58 pages) - Proxy Mobile IPv6 Extensions to Support Flow Mobility [draft-ietf-netext-pmipv6-flowmob-13] (20 pages) - IPv4 Traffic Offload Selector Option for Proxy Mobile IPv6 [draft-ietf-netext-pmipv6-sipto-option-12] (14 pages) - RADIUS Support for Proxy Mobile IPv6 [draft-ietf-netext-radius-pmip6-08] (36 pages) - Runtime Local Mobility Anchor (LMA) Assignment Support for Proxy Mobile IPv6 [draft-ietf-netext-redirect-12] (22 pages) - Service Selection for Mobile IPv6 and Proxy Mobile IPv6 [draft-ietf-netext-rfc5149bis-02] (12 pages) - Update Notifications for Proxy Mobile IPv6 [draft-ietf-netext-update-notifications-12] (21 pages) - Extensible Authentication Protocol (EAP) Attributes for Wi-Fi Integration with the Evolved Packet Core [draft-ietf-netext-wifi-epc-eap-attributes-16] (18 pages) Requests for Comments: RFC6279: Proxy Mobile IPv6 (PMIPv6) Localized Routing Problem Statement (14 pages) * Normative Reference RFC5213 * Possible Reference RFC5741 * Normative Reference RFC5844 * Informative Reference RFC5779 * Normative Reference BCP14 * Informative Reference RFC3775 * Normative Reference RFC2119 * Informative Reference RFC7156 * Informative Reference RFC6705 * Normative Reference DRAFT-LUO-DMM-PMIP-BASED-DMM-APPROACH RFC6463: Runtime Local Mobility Anchor (LMA) Assignment Support for Proxy Mobile IPv6 (22 pages) * Replaces DRAFT-KORHONEN-NETEXT-REDIRECT * Informative Reference RFC3484 * Informative Reference RFC4291 * Informative Reference RFC5844 * Normative Reference RFC6275 * Normative Reference RFC5213 * Informative Reference RFC2616 * Possible Reference RFC5741 * Informative Reference RFC5142 * Normative Reference BCP14 * Informative Reference RFC2136 * Informative Reference RFC5779 * Informative Reference RFC6097 * Informative Reference RFC5996 * Normative Reference RFC2119 * Informative Reference DRAFT-KRISHNAN-NETEXT-UPDATE-NOTIFICATIONS * Normative Reference DRAFT-XUE-NETEXT-FLOWMO-MULTILMA * Normative Reference DRAFT-ZUNIGA-DMM-GAP-ANALYSIS * Informative Reference RFC7429 * Informative Reference DRAFT-WAKIKAWA-NETEXT-PMIP-CP-UP-SEPARATION * Informative Reference DRAFT-PAZHYANNUR-NETEXT-CIVIC-LOCATION-ANI-SUBOPT * Normative Reference DRAFT-SIJEON-NETEXT-PMIP-MSR * Reference DRAFT-YAN-NETEXT-HNPRENUM * Informative Reference RFC7389 * Reference DRAFT-YAN-DMM-HNPRENUM RFC6572: RADIUS Support for Proxy Mobile IPv6 (36 pages) * Normative Reference RFC4282 * Normative Reference RFC2865 * Informative Reference RFC2866 * Informative Reference RFC3579 * Normative Reference RFC4372 * Normative Reference RFC5213 * Possible Reference RFC5741 * Informative Reference RFC3748 * Normative Reference RFC5844 * Normative Reference RFC3588 * Normative Reference BCP14 * Informative Reference RFC2869 * Normative Reference RFC5779 * Informative Reference RFC6097 * Normative Reference RFC5447 * Normative Reference RFC2119 * Informative Reference RFC5149 * Informative Reference DRAFT-GUNDAVELLI-NETEXT-PMIPV6-WLAN-APPLICABILITY * Normative Reference DRAFT-DEKOK-RADEXT-DATATYPES RFC6602: Bulk Binding Update Support for Proxy Mobile IPv6 (23 pages) * Informative Reference RFC4283 * Normative Reference RFC5846 * Normative Reference RFC6275 * Normative Reference RFC5213 * Possible Reference RFC5741 * Informative Reference RFC5845 * Normative Reference RFC5844 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference RFC7077 RFC6705: Localized Routing for Proxy Mobile IPv6 (20 pages) * Informative Reference RFC6279 * Normative Reference RFC6275 * Normative Reference RFC5213 * Possible Reference RFC5741 * Normative Reference RFC5845 * Normative Reference RFC5844 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference RFC4832 * Normative Reference DRAFT-ASAEDA-MULTIMOB-PMIP6-EXTENSION * Informative Reference DRAFT-KORHONEN-DMM-LOCAL-PREFIX * Informative Reference RFC7333 * Normative Reference DRAFT-ZUNIGA-DMM-GAP-ANALYSIS * Informative Reference RFC7429 * Normative Reference DRAFT-ASAEDA-MULTIMOB-PMIP6-ROPT-WITH-PIM * Normative Reference DRAFT-CUI-NETEXT-MULTIHOME-LR RFC6757: Access Network Identifier (ANI) Option for Proxy Mobile IPv6 (19 pages) * Replaces DRAFT-GUNDAVELLI-NETEXT-ACCESS-NETWORK-OPTION * Normative Reference RFC3629 * Normative Reference STD63 * Normative Reference RFC6275 * Informative Reference RFC3046 * Informative Reference RFC2460 * Normative Reference RFC5213 * Possible Reference RFC5741 * Normative Reference RFC1035 * Normative Reference BCP14 * Normative Reference RFC5844 * Normative Reference RFC5139 * Normative Reference RFC2119 * Normative Reference STD13 * Informative Reference RFC6225 * Informative Reference DRAFT-GUNDAVELLI-V6OPS-COMMUNITY-WIFI-SVCS * Normative Reference DRAFT-BHANDARI-DHC-ACCESS-NETWORK-IDENTIFIER * Informative Reference RFC7077 * Possible Reference DRAFT-PAZHYANNUR-NETEXT-CIVIC-LOCATION-ANI-SUBOPT * Informative Reference DRAFT-IETF-DHC-ACCESS-NETWORK-IDENTIFIER * Possible Reference DRAFT-GUNDAVELLI-NETEXT-RFC6757BIS * Normative Reference DRAFT-IETF-NETEXT-ANI-LOCATION RFC6909: IPv4 Traffic Offload Selector Option for Proxy Mobile IPv6 (14 pages) * Replaces DRAFT-GUNDAVELLI-NETEXT-PMIPV6-SIPTO-OPTION * Normative Reference RFC6275 * Normative Reference RFC5213 * Informative Reference RFC2663 * Possible Reference RFC5741 * Normative Reference RFC6088 * Normative Reference RFC6089 * Normative Reference BCP14 * Normative Reference RFC5844 * Informative Reference RFC5101 * Normative Reference RFC2119 * Normative Reference DRAFT-RPCW-PCP-PMIPV6-SERV-DISCOVERY * Informative Reference RFC7333 * Informative Reference RFC7077 * Informative Reference DRAFT-CHEN-PCP-SIPTO-SERV-DISCOVERY RFC7077: Update Notifications for Proxy Mobile IPv6 (21 pages) * Normative Reference BCP14 * Informative Reference BCP26 * Normative Reference RFC2119 * Normative Reference RFC5094 * Informative Reference RFC6909 * Normative Reference RFC6602 * Normative Reference RFC4283 * Normative Reference RFC5844 * Informative Reference RFC4301 * Possible Reference RFC5741 * Informative Reference RFC5847 * Normative Reference RFC5213 * Normative Reference RFC6275 * Informative Reference RFC5226 * Informative Reference RFC5846 * Informative Reference RFC4303 * Informative Reference RFC6757 * Normative Reference DRAFT-IETF-NETEXT-PMIPV6-FLOWMOB * Normative Reference DRAFT-SIJEON-NETEXT-PMIP-MSR * Normative Reference DRAFT-IETF-NETEXT-PMIP-QOS-WIFI * Reference DRAFT-YAN-NETEXT-HNPRENUM * Reference DRAFT-YAN-DMM-HNPRENUM RFC7148: Prefix Delegation Support for Proxy Mobile IPv6 (27 pages) * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference RFC4885 * Normative Reference RFC6603 * Normative Reference RFC3633 * Normative Reference RFC5844 * Normative Reference RFC4301 * Possible Reference RFC5741 * Normative Reference RFC6276 * Normative Reference RFC4877 * Normative Reference RFC5213 * Normative Reference RFC6275 * Informative Reference RFC6656 * Normative Reference RFC4649 * Normative Reference RFC3315 * Normative Reference DRAFT-SEITE-DMM-RG-MULTIHOMING RFC7222: Quality-of-Service Option for Proxy Mobile IPv6 (58 pages) * Informative Reference RFC2475 * Informative Reference RFC2474 * Normative Reference DRAFT-IETF-NETEXT-UPDATE-NOTIFICATIONS * Informative Reference RFC5149 * Informative Reference RFC4594 * Normative Reference RFC2119 * Informative Reference RFC5845 * Normative Reference BCP14 * Normative Reference RFC5844 * Normative Reference RFC6088 * Informative Reference RFC5846 * Normative Reference RFC5213 * Informative Reference DRAFT-VONHUGO-EACP-HETNET * Normative Reference DRAFT-NETEXT-PMIP-QOS-WIFI * Normative Reference DRAFT-IETF-NETEXT-PMIP-QOS-WIFI * Normative Reference DRAFT-IETF-NETEXT-ANI-LOCATION RFC7389: Separation of Control and User Plane for Proxy Mobile IPv6 (12 pages) * Normative Reference RFC2119 * Informative Reference RFC5810 * Normative Reference BCP14 * Normative Reference RFC4301 * Possible Reference RFC5741 * Normative Reference RFC5213 * Informative Reference RFC6275 * Informative Reference DRAFT-WAKIKAWA-REQ-MOBILE-CP-SEPARATION * Informative Reference RFC2473 * Informative Reference DRAFT-MATSUSHIMA-STATELESS-UPLANE-VEPC * Normative Reference RFC5844 * Informative Reference RFC6459 * Informative Reference RFC6463 * Informative Reference RFC1701 * Informative Reference RFC4213 RFC7458: Extensible Authentication Protocol (EAP) Attributes for Wi-Fi Integration with the Evolved Packet Core (18 pages) * Informative Reference RFC4186 * Normative Reference RFC4187 * Possible Reference RFC2119 * Normative Reference BCP26 * Informative Reference RFC5448 * Informative Reference RFC3748 * Informative Reference RFC5415 * Informative Reference RFC5213 * Normative Reference RFC6459 * Normative Reference RFC5226 Port Control Protocol (pcp) --------------------------- Charter Last Modified: 2013-03-13 Current Status: Active Chairs: Dave Thaler Reinaldo Penno Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Mailing Lists: General Discussion: pcp@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/pcp Archive: http://www.ietf.org/mail-archive/web/pcp/ Description of Working Group: Middleboxes such as NATs and firewalls have seen significant deployment in residential and enterprise networks for years. Applications have adapted to such environments. A first family of solutions involves some form of static configuration on the middlebox to perform port opening and/or port forwarding. Another family of solutions works indirectly, using external services to help the establishment of connections and work around the NAT. STUN (RFC 5389) and TURN (RFC 5766) are examples of such solutions. A third family of solutions include protocols that work directly with the middlebox to dynamically open up ports. Universal Plug and Play Internet Gateway Device (UPnP-IGD) and NAT Port Mapping Protocol (NAT-PMP) are examples of such solutions. IPv4 address exhaustion is now forcing ISPs to deploy carrier-grade NAT devices in their network. Those devices could operate either in addition to or instead of an existing NAT device. An example of the former case is a double NAT configuration and an example of the latter case is the application of Dual Stack Lite (DS-Lite) in a network. These deployments will break a fundamental assumption made by protocols, such UPnP or NAT-PMP, that the NAT is located on the same link as the host running the client application. As a result, such applications may break in the presence of a carrier grade NAT. The PCP working group is chartered to standardize a client/server Port Control Protocol (PCP) to enable an explicit dialog with a middlebox such as a NAT or a firewall to open up and/or forward TCP or UDP port, regardless of the location of that middlebox. A PCP client can be used by applications to directly dialog with the middlebox running a PCP server. It can also be used by a home gateways on behalf of applications. This eases the deployment of PCP in situations where applications have already changed to support the APIs necessary for communicating with UPnP-IGD or NAT-PMP. Those applications only work today when the home gateway gets a public address, but may no longer work in situations where the gateway is behind another NAT. Home gateways could use PCP to translate and relay those UPnP and NAP-PMP messages to the PCP server, thus allowing such applications to continue working as they do today. The functionality that enables the control of IPv4 middleboxes such as NAT devices or firewalls can also be useful in IPv6 context, to control IPv6 functionality in firewalls. As such, PCP will be defined for both IPv4 and IPv6. The discovery PCP servers, using classic methods such as DHCP options, is in scope for the PCP working group. The working group will also ensure that the protocol has the necessary security mechanisms. The IETF will make no changes to either NAT-PMP or UPnP-IGP protocols, and they will be used only as is. Deliverables: - PCP protocol description and terminology document - PCP service discovery document - PCP relay of UPnP document - PCP relay of NAT-PMP document Goals and Milestones: Done - First WG draft on PCP protocol description Done - First WG draft on PCP service discovery Done - First WG draft on UPnP relay Done - First WG draft on NAT-PMP relay Done - Send PCP protocol description to IESG for publication as Proposed Standard May 2011 - Send PCP service discovery to IESG for publication as Proposed Standard Oct 2011 - Send UPnP relay to IESG for publication as Proposed Standard Oct 2011 - Send NAT-PMP relay to IESG for publication as Proposed Standard Oct 2013 - Send PCP Description option to IESG as a proposed Standard Oct 2013 - Send Learn NAT64 PREFIX64s using PCP to IESG as proposed Standard Dec 2013 - Send Port Control Protocol (PCP) Proxy Function to IESG as proposed Standard Internet-Drafts: - The Port Control Protocol in Dual-Stack Lite environments [draft-dupont-pcp-dslite-05] (6 pages) - Port Control Protocol (PCP) Anycast Addresses [draft-ietf-pcp-anycast-04] (12 pages) - Port Control Protocol (PCP) Authentication Mechanism [draft-ietf-pcp-authentication-07] (28 pages) - Port Control Protocol (PCP) [draft-ietf-pcp-base-29] (88 pages) - Description Option for the Port Control Protocol (PCP) [draft-ietf-pcp-description-option-05] (6 pages) - DHCP Options for the Port Control Protocol (PCP) [draft-ietf-pcp-dhcp-13] (11 pages) - The Port Control Protocol in Dual-Stack Lite environments [draft-ietf-pcp-dslite-00] (6 pages) - Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP) [draft-ietf-pcp-nat64-prefix64-06] (17 pages) - Optimizing NAT and Firewall Keepalives Using Port Control Protocol (PCP) [draft-ietf-pcp-optimize-keepalives-05] (18 pages) - Port Control Protocol (PCP) Extension for Port Set Allocation [draft-ietf-pcp-port-set-07] (17 pages) - Port Control Protocol (PCP) Proxy Function [draft-ietf-pcp-proxy-06] (12 pages) - Port Control Protocol (PCP) Server Selection [draft-ietf-pcp-server-selection-10] (12 pages) - PCP Third Party ID Option [draft-ietf-pcp-third-party-id-option-02] (12 pages) - Universal Plug and Play (UPnP) Internet Gateway Device - Port Control Protocol Interworking Function (IGD-PCP IWF) [draft-ietf-pcp-upnp-igd-interworking-10] (23 pages) - PCP Third Party ID Option [draft-ripke-pcp-tunnel-id-option-02] (10 pages) Requests for Comments: RFC6887: Port Control Protocol (PCP) (88 pages) * Replaces DRAFT-WING-PCP-BASE * Normative Reference RFC5226 * Informative Reference RFC6886 * Informative Reference RFC4787 * Informative Reference RFC6888 * Normative Reference BCP106 * Informative Reference RFC4340 * Normative Reference BCP14 * Normative Reference BCP38 * Informative Reference BCP142 * Informative Reference RFC6092 * Normative Reference RFC4086 * Informative Reference RFC1918 * Normative Reference RFC768 * Informative Reference RFC6333 * Possible Reference RFC5741 * Informative Reference BCP131 * Normative Reference RFC6056 * Informative Reference RFC3587 * Informative Reference RFC6763 * Informative Reference RFC6296 * Informative Reference RFC6619 * Normative Reference BCP156 * Normative Reference RFC4291 * Informative Reference BCP5 * Informative Reference RFC4961 * Informative Reference RFC4960 * Informative Reference RFC2136 * Informative Reference RFC4941 * Normative Reference RFC2119 * Normative Reference BCP26 * Informative Reference RFC5382 * Normative Reference RFC2827 * Normative Reference RFC4193 * Informative Reference RFC3581 * Informative Reference RFC793 * Informative Reference RFC3022 * Informative Reference RFC4303 * Informative Reference RFC6146 * Informative Reference RFC6145 * Informative Reference BCP127 * Informative Reference RFC3007 * Informative Reference RFC7288 * Informative Reference DRAFT-JIANG-CONFIG-NEGOTIATION-PS * Informative Reference DRAFT-IYENGAR-MINION-PROTOCOL * Informative Reference DRAFT-CONET-AEON-PROBLEM-STATEMENT * Normative Reference DRAFT-WING-PCP-THIRD-PARTY-AUTHZ * Normative Reference DRAFT-PERREAULT-SOFTWIRE-LW4OVER6-PCP * Informative Reference DRAFT-THALER-IAB-HOST-FIREWALLS * Normative Reference DRAFT-IETF-PCP-DSLITE * Normative Reference DRAFT-CHESHIRE-PCP-UNSUPP-FAMILY * Normative Reference DRAFT-PENNO-RTCWEB-PCP * Normative Reference DRAFT-BOUCADAIR-PCP-CAPABILITY * Normative Reference RFC7220 * Informative Reference DRAFT-IETF-RADEXT-IP-PORT-RADIUS-EXT * Informative Reference RFC6886 * Normative Reference RFC6888 * Normative Reference DRAFT-IETF-PCP-PORT-SET * Informative Reference DRAFT-HUTTON-RTCWEB-NAT-FIREWALL-CONSIDERATIONS * Informative Reference DRAFT-DENG-MPTCP-NRSACK * Informative Reference RFC7021 * Normative Reference DRAFT-BOUCADAIR-PCP-NAT-REVEAL * Normative Reference DRAFT-MAGLIONE-PCP-RADIUS-EXT * Informative Reference DRAFT-BOUCADAIR-PCP-FAILURE * Normative Reference RFC6889 * Normative Reference RFC7084 * Normative Reference DRAFT-BOUCADAIR-PCP-FLOW-EXAMPLES * Normative Reference DRAFT-REDDY-PCP-AUTH-REQ * Informative Reference RFC7215 * Normative Reference DRAFT-REDDY-MMUSIC-ICE-BEST-INTERFACE-PCP * Normative Reference DRAFT-WING-MPTCP-PCP * Informative Reference RFC7368 * Informative Reference RFC7422 * Normative Reference RFC7291 * Normative Reference RFC6970 * Normative Reference DRAFT-RPCW-PCP-PMIPV6-SERV-DISCOVERY * Normative Reference DRAFT-CHEN-PCP-MOBILE-DEPLOYMENT * Normative Reference DRAFT-TSOU-SOFTWIRE-BFD-DS-LITE * Normative Reference DRAFT-IETF-PCP-PROXY * Informative Reference DRAFT-IETF-SOFTWIRE-4RD * Informative Reference DRAFT-CHENG-BEHAVE-CGN-CFG-RADIUS-EXT * Possible Reference RFC7393 * Normative Reference RFC7269 * Normative Reference DRAFT-MOU-PCP-APPLICATION-NETWORK-FEEDBACK * Informative Reference DRAFT-AKHTER-LMAP-FRAMEWORK * Normative Reference DRAFT-PENNO-PCP-EXT-ADDR * Normative Reference RFC7488 * Normative Reference DRAFT-CHESHIRE-PCP-ANYCAST * Normative Reference RFC7225 * Informative Reference DRAFT-IETF-BEHAVE-SYSLOG-NAT-LOGGING * Informative Reference DRAFT-LEE-SOFTWIRE-LW4OVER6-FAILOVER * Normative Reference DRAFT-WING-PCP-FLOWDATA * Normative Reference DRAFT-SUN-SOFTWIRE-LW4OVER6-RADEXT * Normative Reference DRAFT-SUN-SOFTWIRE-LW4OVER6-DHCPV6 * Informative Reference DRAFT-GRUNDEMANN-HIPNET * Normative Reference DRAFT-PENNO-PCP-MOBILE-QOS * Normative Reference DRAFT-VINAPAMULA-SOFTWIRE-DSLITE-PREFIX-BINDING * Normative Reference DRAFT-BOUCADAIR-PCP-DEPLOYMENT-CASES * Normative Reference DRAFT-IETF-PCP-OPTIMIZE-KEEPALIVES * Normative Reference DRAFT-CHEN-PCP-SIPTO-SERV-DISCOVERY * Possible Reference DRAFT-FOLKS-LMAP-FRAMEWORK * Normative Reference DRAFT-PENNO-PCP-ASDN * Informative Reference DRAFT-IETF-V6OPS-BALANCED-IPV6-SECURITY * Normative Reference DRAFT-RIPKE-PCP-TUNNEL-ID-OPTION * Normative Reference DRAFT-STENBERG-HOMENET-MINIMALIST-PCP-PROXY * Normative Reference DRAFT-BOUCADAIR-PCP-SFC-CLASSIFIER-CONTROL * Normative Reference DRAFT-CHEN-PCP-AUTHENTICATION-SIM * Normative Reference DRAFT-CONET-AEON-GAP-ANALYSIS * Possible Reference DRAFT-SUN-APONF-OPENV6-USE-CASES * Normative Reference DRAFT-WANG-PCP-BIND-OPERATION * Informative Reference DRAFT-IETF-PCP-AUTHENTICATION * Normative Reference DRAFT-IETF-PCP-ANYCAST * Normative Reference DRAFT-VINAPAMULA-FLOW-HA * Reference DRAFT-SHI-MODEL-JSON-MSG-YANG * Reference DRAFT-SHI-ALTO-YANG-JSON * Informative Reference DRAFT-IETF-SOFTWIRE-LW4OVER6 * Informative Reference DRAFT-IETF-LMAP-FRAMEWORK * Normative Reference DRAFT-REDDY-PCP-SDN-FIREWALL * Informative Reference DRAFT-CARPENTER-ANIMA-GDN-PROTOCOL * Normative Reference DRAFT-IETF-PCP-THIRD-PARTY-ID-OPTION * Informative Reference DRAFT-IETF-V6OPS-MOBILE-DEVICE-PROFILE * Informative Reference DRAFT-BOUCADAIR-TRANSPORT-PROTOCOLS * Normative Reference DRAFT-BOUCADAIR-PCP-SIP-IPV6 * Informative Reference DRAFT-XIE-HIAPS-HOSTID-IN-SFC * Informative Reference DRAFT-BOUCADAIR-MPTCP-SYMMETRIC * Updates RFC7488 RFC6970: Universal Plug and Play (UPnP) Internet Gateway Device - Port Control Protocol Interworking Function (IGD-PCP IWF) (23 pages) * Replaces DRAFT-BPW-PCP-UPNP-IGD-INTERWORKING * Normative Reference RFC6887 * Informative Reference RFC6146 * Informative Reference RFC6333 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference RFC7220 * Informative Reference DRAFT-BOUCADAIR-PCP-DEPLOYMENT-CASES * Informative Reference DRAFT-RIPKE-PCP-TUNNEL-ID-OPTION * Informative Reference DRAFT-IETF-PCP-THIRD-PARTY-ID-OPTION * Informative Reference DRAFT-BOUCADAIR-MPTCP-SYMMETRIC RFC7220: Description Option for the Port Control Protocol (PCP) (6 pages) * Replaces DRAFT-BOUCADAIR-PCP-DESCRIPTION-OPTION * Normative Reference RFC3629 * Informative Reference RFC6462 * Normative Reference RFC6887 * Normative Reference STD63 * Normative Reference BCP14 * Informative Reference RFC6970 * Normative Reference RFC2119 * Informative Reference DRAFT-BOUCADAIR-PCP-SIP-IPV6 * Informative Reference DRAFT-RIPKE-PCP-TUNNEL-ID-OPTION RFC7225: Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP) (17 pages) * Replaces DRAFT-BOUCADAIR-PCP-NAT64-PREFIX64-OPTION * Normative Reference RFC6887 * Informative Reference RFC4566 * Normative Reference BCP14 * Informative Reference DRAFT-IETF-BEHAVE-NAT64-LEARN-ANALYSIS * Normative Reference RFC6147 * Normative Reference RFC6146 * Normative Reference RFC6052 * Informative Reference DRAFT-IETF-MMUSIC-LATCHING * Informative Reference RFC3261 * Informative Reference RFC4033 * Normative Reference RFC4632 * Informative Reference DRAFT-IETF-BEHAVE-NAT64-DISCOVERY-HEURISTIC * Normative Reference RFC2119 * Informative Reference RFC6269 * Informative Reference DRAFT-IETF-RTCWEB-OVERVIEW * Informative Reference DRAFT-ZHANG-BEHAVE-NAT64-LOAD-BALANCING * Informative Reference DRAFT-CARPENTER-BEHAVE-REFERRAL-OBJECT * Informative Reference DRAFT-BOUCADAIR-PCP-BITTORRENT * Informative Reference RFC4034 * Informative Reference DRAFT-IETF-PCP-PORT-SET * Normative Reference BCP122 * Informative Reference RFC4035 * Informative Reference DRAFT-BOUCADAIR-PCP-NAT64-EXPERIMENTS * Informative Reference DRAFT-BOUCADAIR-PCP-SIP-IPV6 * Informative Reference DRAFT-IETF-V6OPS-MOBILE-DEVICE-PROFILE * Informative Reference RFC7445 * Informative Reference DRAFT-SUN-V6OPS-XLAT-MULTI RFC7291: DHCP Options for the Port Control Protocol (PCP) (11 pages) * Replaces DRAFT-BPW-PCP-DHCP * Normative Reference RFC2131 * Normative Reference RFC2119 * Normative Reference RFC2132 * Normative Reference BCP14 * Normative Reference RFC3315 * Informative Reference RFC6333 * Informative Reference DRAFT-IETF-PCP-SERVER-SELECTION * Normative Reference RFC6887 * Normative Reference RFC4291 * Informative Reference DRAFT-IETF-DHC-TOPO-CONF * Informative Reference DRAFT-BOUCADAIR-PCP-SIP-IPV6 * Informative Reference RFC7488 * Informative Reference DRAFT-IETF-PCP-ANYCAST * Informative Reference DRAFT-BOUCADAIR-MPTCP-SYMMETRIC RFC7488: Port Control Protocol (PCP) Server Selection (12 pages) * Replaces DRAFT-BOUCADAIR-PCP-SERVER-SELECTION * Normative Reference RFC6887 * Informative Reference STD3 * Normative Reference RFC2119 * Informative Reference RFC2260 * Normative Reference BCP14 * Informative Reference RFC1122 * Informative Reference RFC4116 * Normative Reference RFC6724 * Informative Reference RFC7291 * Updates RFC6887 Softwires (softwire) -------------------- Charter Last Modified: 2013-03-13 Current Status: Active Chairs: Suresh Krishnan Yong Cui Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Tech Advisor: Xing Li Mailing Lists: General Discussion: softwires@ietf.org To Subscribe: softwires-request@ietf.org Archive: http://www.ietf.org/mail-archive/web/softwires/ Description of Working Group: The Softwires Working Group is specifying the standardization of discovery, control and encapsulation methods for connecting IPv4 networks across IPv6 networks and IPv6 networks across IPv4 networks in a way that will encourage multiple, inter-operable implementations. For various reasons, native IPv4 and/or IPv6 transport may not be available in all cases, and there is a need to tunnel IPv4 in IPv6 or IPv6 in IPv4 to cross a part of the network which is not IPv4 or IPv6 capable. The Softwires Problem Statement, RFC 4925, identifies two distinct topological scenarios that the Working Group will provide solutions for: "Hubs and Spokes" and "Mesh." In the former case (Hubs and Spokes), hosts or "stub" networks are attached via individual, point-to-point, IPv4 over IPv6 or IPv6 over IPv4 softwires to a centralized Softwire Concentrator. In the latter case (Mesh), network islands of one Address Family (IPv4 or IPv6) are connected over a network of another Address Family via point to multi-point softwires among Address Family Border Routers (AFBRs). The Softwires Working Group will reuse existing technologies as much as possible and only when necessary, create additional protocol building blocks. For generality, all base softwires encapsulation mechanisms should support all combinations of IP versions over one other (IPv4 over IPv6, IPv6 over IPv4, IPv4 over IPv4, IPv6 over IPv6). IPv4/IPv6 translation mechanisms, new addressing schemes, and block address assignments are out of scope. DHCP options developed in this working group will be reviewed jointly with the DHC Working Group. RADIUS attributes developed in the Softwires Working Group will be reviewed jointly with the RADEXT Working Group. The MIB Doctors directorate will be asked to review any MIB modules developed in the Softwires Working Group. BGP and other routing and signaling protocols developed in this group will be reviewed jointly with the proper working groups and other workings that may take interest (e.g. IDR, L3VPN, PIM, LDP, SAAG, etc). The specific work areas for this working group are: 1. Developments for Mesh softwires topology; the Mesh topology work will be reviewed in the L3VPN and IDR Working Groups - multicast - MIB module 2. Developments for 6rd: - multicast - operational specification - RADIUS attribute for 6rd server - MIB module - Gateway-initiated 6rd (GI-6rd) 3. Developments for Dual-Stack Lite (DS-Lite): - multicast - operational specification - RADIUS attribute for AFTR - proxy extensions; GI-DS-Lite; No NAT on AFTR - MIB module 4. Developments for stateless legacy IPv4 carried over IPv6 - develop a solution motivation document to be published as an RFC - develop a protocol specification response to the solution motivation document; this work item will not be taken through Working Group last call until the solution motivation document has been published or approved for publication 5. Finalize discovery and configuration mechanisms for a gateway to use DS-Lite or 6rd; these discovery and configuration mechanisms must take into a account other operating environments such as dual-stack and tunneling mechanisms not defined by the Softwires Working Group. Development of new mechanisms will involve the DHC and/or V6OPS Working Groups as appropriate Other work items would require Working Group approval and rechartering. Goals and Milestones: Done - Submit a problem statement to the IESG to be considered as an Informational RFC Jun 2011 - Submit DS-lite RADIUS attribute document for Proposed Standard Jun 2011 - Adopt DS-lite operational document as a Working Group document Jul 2011 - Submit 6rd RADIUS attribute document for Proposed Standard Jul 2011 - Submit GI DS-lite document for Proposed Standard Jul 2011 - Adopt DS-Lite without NAT document as a Working Group document Jul 2011 - Adopt DHCPv4 over tunnel document as a Working Group document Aug 2011 - Adopt 6rd operational document as a Working Group document Aug 2011 - Adopt Multicast extensions document as a Working Group document Aug 2011 - Submit DS-lite operational document for Informational Aug 2011 - Adopt stateless legacy IPv4 solution motivation document as a Working Group document Sep 2011 - Submit DS-Lite without NAT document for Informational Sep 2011 - Submit DHCPv4 over tunnel document for Proposed Standard Nov 2011 - Submit Multicast extensions document for Informational Nov 2011 - Submit 6rd operational document for Informational Nov 2011 - Adopt 6rd MIB module document as a Working Group document Nov 2011 - Adopt DS-lite MIB module document as a Working Group document Nov 2011 - Adopt Mesh topology MIB module document as a Working Group document Dec 2011 - Submit stateless legacy IPv4 solution motivation document for Informational Dec 2011 - Adopt stateless legacy IPv4 specification document as a Working Group document Apr 2012 - Submit stateless legacy IPv4 specification document for Proposed Standard Nov 2012 - Submit 6rd MIB module document for Proposed Standard Nov 2012 - Submit DS-lite MIB module document for Proposed Standard Nov 2012 - Submit Mesh topology MIB module document for Proposed Standard Internet-Drafts: - Unified IPv4-in-IPv6 Softwire CPE [draft-bfmk-softwire-unified-cpe-02] (13 pages) - Definitions of Managed Objects for 6rd [draft-cai-softwire-6rd-mib-05] (10 pages) - Lightweight 4over6: An Extension to the DS-Lite Architecture [draft-cui-softwire-b4-translated-ds-lite-11] (19 pages) - Definitions of Managed Objects for MAP-E [draft-fu-softwire-map-mib-05] (13 pages) - IPv4 unicast/multicast VPNs over an IPv6 core [draft-ietf-softwire-4over6vpns-00] (7 pages) - IPv4 Residual Deployment via IPv6 - a Stateless Solution (4rd) [draft-ietf-softwire-4rd-10] (40 pages) - RADIUS Attribute for IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) [draft-ietf-softwire-6rd-radius-attrib-11] (12 pages) - BGP Traffic Engineering Attribute [draft-ietf-softwire-bgp-te-attribute-04] (6 pages) - Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite [draft-ietf-softwire-ds-lite-tunnel-option-10] (7 pages) - Deployment Considerations for Dual-Stack Lite [draft-ietf-softwire-dslite-deployment-08] (14 pages) - DS-Lite Management Information Base (MIB) [draft-ietf-softwire-dslite-mib-08] (22 pages) - Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network [draft-ietf-softwire-dslite-multicast-09] (19 pages) - RADIUS Extensions for Dual-Stack Lite [draft-ietf-softwire-dslite-radius-ext-07] (11 pages) - Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion [draft-ietf-softwire-dual-stack-lite-11] (32 pages) - BGP IPsec Tunnel Encapsulation Attribute [draft-ietf-softwire-encaps-ipsec-03] (8 pages) - The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute [draft-ietf-softwire-encaps-safi-05] (13 pages) - Gateway-Initiated Dual-Stack Lite Deployment [draft-ietf-softwire-gateway-init-ds-lite-08] (15 pages) - Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2) [draft-ietf-softwire-hs-framework-l2tpv2-13] (41 pages) - IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification [draft-ietf-softwire-ipv6-6rd-10] (18 pages) - Load-Balancing for Mesh Softwires [draft-ietf-softwire-lb-03] (6 pages) - Lightweight 4over6: An Extension to the DS-Lite Architecture [draft-ietf-softwire-lw4over6-13] (22 pages) - Mapping of Address and Port with Encapsulation (MAP) [draft-ietf-softwire-map-13] (32 pages) - Mapping of Address and Port (MAP) - Deployment Considerations [draft-ietf-softwire-map-deployment-05] (30 pages) - DHCPv6 Options for configuration of Softwire Address and Port Mapped Clients [draft-ietf-softwire-map-dhcp-12] (18 pages) - Definitions of Managed Objects for MAP-E [draft-ietf-softwire-map-mib-03] (13 pages) - RADIUS Attribute for MAP [draft-ietf-softwire-map-radius-03] (15 pages) - Mapping of Address and Port using Translation (MAP-T) [draft-ietf-softwire-map-t-08] (24 pages) - Softwire Mesh Framework [draft-ietf-softwire-mesh-framework-06] (31 pages) - Softwire Mesh Management Information Base (MIB) [draft-ietf-softwire-mesh-mib-08] (16 pages) - Softwire Mesh Multicast [draft-ietf-softwire-mesh-multicast-09] (21 pages) - DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 Prefixes [draft-ietf-softwire-multicast-prefix-option-08] (7 pages) - Softwire Problem Statement [draft-ietf-softwire-problem-statement-03] (23 pages) - Public IPv4-over-IPv6 Access Network [draft-ietf-softwire-public-4over6-10] (13 pages) - Softwire Security Analysis and Requirements [draft-ietf-softwire-security-requirements-09] (28 pages) - Motivations for Carrier-side Stateless IPv4 over IPv6 Migration Solutions [draft-ietf-softwire-stateless-4v6-motivation-05] (15 pages) - Unified IPv4-in-IPv6 Softwire CPE [draft-ietf-softwire-unified-cpe-01] (15 pages) - Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop [draft-ietf-softwire-v4nlri-v6nh-02] (10 pages) - RADIUS Attribute for MAP [draft-jiang-softwire-map-radius-04] (14 pages) Requests for Comments: RFC4925: Softwire Problem Statement (23 pages) * Informative Reference BCP78 * Informative Reference RFC4365 * Normative Reference RFC3056 * Normative Reference RFC3041 * Informative Reference RFC4364 * Informative Reference RFC2462 * Informative Reference RFC3315 * Normative Reference RFC3972 * Informative Reference RFC3633 * Normative Reference RFC3053 * Informative Reference RFC4891 * Normative Reference RFC4213 * Informative Reference RFC2131 * Normative Reference DRAFT-STEVANT-SOFTWIRE-ACCOUNTING * Normative Reference RFC5747 * Informative Reference RFC5571 * Informative Reference RFC5565 * Informative Reference RFC5619 * Normative Reference DRAFT-XU-SOFTWIRE-4OVER6MULTICAST * Informative Reference DRAFT-IETF-IDR-V4NLRI-V6NH * Normative Reference DRAFT-DESPRES-V6OPS-6RD-IPV6-RAPID-DEPLOYMENT * Normative Reference DRAFT-METZ-SOFTWIRES-MULTICAST-PROBLEM-STATEMENT * Informative Reference DRAFT-DROMS-SOFTWIRES-SNAT * Informative Reference RFC5549 * Informative Reference DRAFT-WING-NAT-PT-REPLACEMENT-COMPARISON * Informative Reference RFC6127 * Informative Reference DRAFT-GUO-SOFTWIRE-SC-DISCOVERY * Normative Reference DRAFT-CUI-SOFTWIRE-PET * Informative Reference RFC6674 * Informative Reference DRAFT-GUO-SOFTWIRE-AUTO-GRE * Informative Reference DRAFT-SHIRASAKI-NAT444 * Informative Reference DRAFT-DESPRES-SOFTWIRE-MESH-SAM * Informative Reference DRAFT-DESPRES-SOFTWIRE-SAM * Normative Reference DRAFT-CUI-SOFTWIRE-HOST-4OVER6 * Normative Reference DRAFT-LEE-SOFTWIRE-DSLITE-DEPLOYMENT * Normative Reference DRAFT-XU-SOFTWIRE-MESH-MULTICAST * Normative Reference DRAFT-CUI-SOFTWIRE-MESH-MIB * Informative Reference DRAFT-CHEN-SOFTWIRE-4V6-MOTIVATION * Normative Reference DRAFT-CUI-SOFTWIRE-DHCP-OVER-TUNNEL * Normative Reference RFC7040 * Normative Reference DRAFT-IEFT-SOFTWIRE-DSLITE-DEPLOYMENT * Normative Reference DRAFT-IETF-SOFTWIRE-MESH-MULTICAST * Normative Reference DRAFT-CUI-DHC-DHCPV4-OVER-IPV6 * Informative Reference DRAFT-LI-SOFTWIRE-DSLITE-INTRA-DOMAIN * Normative Reference DRAFT-IETF-DHC-DHCPV4-OVER-IPV6 * Normative Reference DRAFT-WU-DHC-PORT-SET-OPTION * Normative Reference DRAFT-IETF-SOFTWIRE-4RD * Normative Reference DRAFT-SUN-DHC-DHCPV6-OPT-V4CONFIG * Normative Reference DRAFT-IETF-SOFTWIRE-MESH-MIB RFC5512: The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute (13 pages) * Normative Reference RFC2003 * Normative Reference RFC2890 * Normative Reference RFC3931 * Normative Reference RFC4760 * Normative Reference RFC4360 * Normative Reference RFC4271 * Normative Reference RFC2119 * Normative Reference BCP14 * Normative Reference RFC2784 * Normative Reference RFC4213 * Informative Reference DRAFT-GEORGE-MPLS-IPV6-ONLY-GAP * Normative Reference DRAFT-WAKIKAWA-REQ-MOBILE-CP-SEPARATION * Normative Reference RFC5747 * Normative Reference RFC5565 * Normative Reference RFC5566 * Normative Reference RFC5640 * Informative Reference DRAFT-IETF-IDR-BGP-BESTPATH-SELECTION-CRITERIA * Normative Reference DRAFT-CUI-SOFTWIRE-VA-BASED-TRANSITION * Informative Reference DRAFT-RASZUK-TI-BGP * Normative Reference DRAFT-GUO-SOFTWIRE-SC-DISCOVERY * Normative Reference DRAFT-CUI-SOFTWIRE-VA-BASED-SOFTWIRE * Normative Reference DRAFT-IETF-GROW-VA-GRE * Normative Reference DRAFT-IETF-GROW-VA-MPLS-INNERLABEL * Reference DRAFT-XU-SOFTWIRE-TUNNEL-ENDPOINT * Normative Reference DRAFT-CUI-SOFTWIRE-MESH-MIB * Normative Reference DRAFT-BASHANDY-BGP-EDGE-NODE-FRR * Normative Reference DRAFT-VANDEVELDE-IDR-REMOTE-NEXT-HOP * Informative Reference DRAFT-XU-MPLS-IN-UDP * Informative Reference DRAFT-XU-IDR-TUNNEL-ADDRESS-PREFIX * Normative Reference DRAFT-SAJASSI-L2VPN-EVPN-ETREE * Normative Reference DRAFT-IETF-SOFTWIRE-MESH-MIB * Normative Reference DRAFT-BASHANDY-BGP-FRR-VECTOR-LABEL * Normative Reference DRAFT-SAJASSI-DRAKE-L2VPN-EVPN-OVERLAY * Normative Reference DRAFT-DRAKE-NVO3-EVPN-CONTROL-PLANE * Normative Reference DRAFT-BASHANDY-BGP-FRR-MIRROR-TABLE * Possible Reference DRAFT-SAJASSI-NVO3-EVPN-OVERLAY * Informative Reference DRAFT-DRAO-BGP-L3VPN-VIRTUAL-NETWORK-OVERLAYS * Normative Reference DRAFT-XU-SOFTWIRE-ENCAPS-UDP * Normative Reference DRAFT-KUMAR-SOFTWIRE-UET * Normative Reference DRAFT-SD-L2VPN-EVPN-OVERLAY * Possible Reference DRAFT-IETF-NETMOD-IANA-AFN-SAFI * Normative Reference DRAFT-MATSUSHIMA-STATELESS-UPLANE-VEPC * Possible Reference DRAFT-RABADAN-L2VPN-EVPN-PREFIX-ADVERTISEMENT * Normative Reference DRAFT-DRAO-L3VPN-VIRTUAL-NETWORK-OVERLAY-MULTICAST * Informative Reference RFC7439 * Possible Reference DRAFT-RABADAN-BESS-DCI-EVPN-OVERLAY * Normative Reference DRAFT-SAJASSI-BESS-EVPN-ETREE * Normative Reference DRAFT-IETF-BESS-EVPN-OVERLAY * Possible Reference DRAFT-IETF-BESS-EVPN-INTER-SUBNET-FORWARDING * Possible Reference DRAFT-IETF-BESS-DCI-EVPN-OVERLAY * Possible Reference DRAFT-IETF-BESS-EVPN-PREFIX-ADVERTISEMENT * Normative Reference DRAFT-XU-BESS-ENCAPS-UDP * Normative Reference DRAFT-XU-IDR-BIER-EXTENSIONS * Normative Reference DRAFT-HAO-BESS-INTER-NVO3-VPN * Informative Reference DRAFT-XU-SPRING-ISLANDS-CONNECTION-OVER-IP * Normative Reference DRAFT-HAO-NVO3-INTER-AS-VPN RFC5543: BGP Traffic Engineering Attribute (6 pages) * Informative Reference RFC5195 * Normative Reference RFC3471 * Normative Reference RFC4271 * Informative Reference RFC5307 * Normative Reference BCP14 * Informative Reference RFC4203 * Normative Reference RFC4201 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference DRAFT-KNOLL-IDR-QOS-ATTRIBUTE * Normative Reference DRAFT-IETF-IDR-ERROR-HANDLING RFC5549: Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop (10 pages) * Informative Reference RFC5226 * Informative Reference RFC4798 * Normative Reference RFC4760 * Normative Reference RFC3107 * Informative Reference RFC4925 * Informative Reference RFC4659 * Normative Reference RFC4364 * Normative Reference RFC5492 * Normative Reference RFC2119 * Informative Reference RFC4684 * Normative Reference BCP14 * Normative Reference RFC4291 * Normative Reference RFC2545 * Informative Reference BCP26 * Normative Reference DRAFT-KUMAR-IDR-LINK-LOCAL-NEXTHOP * Normative Reference RFC5747 * Normative Reference RFC5565 * Informative Reference RFC5566 * Normative Reference DRAFT-CUI-SOFTWIRE-VA-BASED-TRANSITION * Normative Reference DRAFT-CUI-SOFTWIRE-VA-BASED-SOFTWIRE * Informative Reference DRAFT-ROSEN-L3VPN-MVPN-INFRA-ADDRS * Informative Reference RFC6515 * Normative Reference DRAFT-CUI-SOFTWIRE-HOST-4OVER6 * Informative Reference DRAFT-IETF-IDR-ERROR-HANDLING RFC5565: Softwire Mesh Framework (31 pages) * Replaces DRAFT-WU-SOFTWIRE-MESH-FRAMEWORK * Informative Reference RFC5496 * Informative Reference RFC4364 * Informative Reference RFC4176 * Normative Reference RFC5512 * Normative Reference BCP14 * Informative Reference RFC4291 * Normative Reference RFC2003 * Normative Reference RFC4798 * Normative Reference RFC4023 * Informative Reference RFC4459 * Normative Reference RFC2784 * Informative Reference RFC4378 * Normative Reference RFC3209 * Normative Reference RFC3931 * Normative Reference RFC5549 * Informative Reference RFC4271 * Informative Reference RFC1195 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference RFC5566 * Informative Reference RFC4925 * Informative Reference RFC4303 * Informative Reference RFC4302 * Informative Reference RFC4301 * Informative Reference RFC2328 * Informative Reference RFC4306 * Informative Reference RFC2385 * Informative Reference RFC5036 * Normative Reference RFC3031 * Normative Reference RFC3032 * Normative Reference RFC5747 * Informative Reference RFC5619 * Normative Reference DRAFT-XU-SOFTWIRE-4OVER6MULTICAST * Informative Reference RFC5566 * Informative Reference DRAFT-BOUCADAIR-DSLITE-INTERCO-V4V6 * Informative Reference DRAFT-BOUCADAIR-SOFTWIRE-DSLITE-V6ONLY * Normative Reference DRAFT-CUI-SOFTWIRE-VA-BASED-SOFTWIRE * Normative Reference DRAFT-CUI-PET * Normative Reference DRAFT-CUI-SOFTWIRE-PET * Normative Reference DRAFT-CUI-SOFTWIRE-PET-FRAMEWORK * Reference DRAFT-XU-SOFTWIRE-TUNNEL-ENDPOINT * Normative Reference DRAFT-CUI-SOFTWIRE-PET64 * Informative Reference DRAFT-DESPRES-SOFTWIRE-MESH-SAM * Normative Reference RFC6180 * Informative Reference DRAFT-DESPRES-SOFTWIRE-SAM * Normative Reference DRAFT-SOFTWIRE-GATEWAY-INIT-DS-LITE * Informative Reference DRAFT-CHENG-OSPF-IPV4-EMBEDDED-IPV6-ROUTING * Normative Reference DRAFT-XU-IDR-BEST-EXTERNAL-LOOP-AVOIDANCE * Informative Reference DRAFT-DESPRES-SOFTWIRE-6RDPLUS * Normative Reference DRAFT-CUI-SOFTWIRE-HOST-4OVER6 * Informative Reference DRAFT-LEE-V4V6TRAN-PROBLEM * Normative Reference DRAFT-XU-SOFTWIRE-MESH-MULTICAST * Informative Reference DRAFT-TEMPLIN-IRON-PM * Informative Reference DRAFT-BASHANDY-IDR-BGP-REPAIR-LABEL * Normative Reference DRAFT-CUI-SOFTWIRE-MESH-MIB * Informative Reference DRAFT-MATSUSHIMA-V6OPS-TRANSITION-EXPERIENCE * Informative Reference DRAFT-SUN-INTAREA-4RD-APPLICABILITY * Normative Reference RFC6992 * Informative Reference DRAFT-BASHANDY-BGP-EDGE-NODE-FRR * Normative Reference DRAFT-IETF-SOFTWIRE-MESH-MULTICAST * Normative Reference DRAFT-XU-SAVI-TRANSITION * Informative Reference DRAFT-BASHANDY-ISIS-BGP-EDGE-NODE-FRR * Informative Reference DRAFT-BASHANDY-MPLS-LDP-BGP-FRR * Informative Reference DRAFT-XU-IDR-TUNNEL-ADDRESS-PREFIX * Normative Reference DRAFT-IETF-SOFTWIRE-MESH-MIB * Informative Reference DRAFT-BASHANDY-BGP-FRR-VECTOR-LABEL * Informative Reference DRAFT-RTGWG-BGP-PIC * Informative Reference DRAFT-BASHANDY-BGP-FRR-MIRROR-TABLE * Normative Reference DRAFT-YONG-TSVWG-UDP-ENCAP-4-IP-TUNNELING * Informative Reference DRAFT-YAMAYA-IPSECME-MPSA * Normative Reference DRAFT-KUMAR-SOFTWIRE-UET * Informative Reference DRAFT-XU-SOFTWIRE-IP-IN-UDP RFC5566: BGP IPsec Tunnel Encapsulation Attribute (8 pages) * Informative Reference RFC4364 * Normative Reference RFC5512 * Normative Reference BCP14 * Informative Reference RFC3931 * Informative Reference RFC2003 * Normative Reference RFC2119 * Informative Reference RFC4023 * Informative Reference RFC2784 * Informative Reference RFC4798 * Informative Reference RFC5549 * Informative Reference RFC4659 * Informative Reference RFC4272 * Normative Reference RFC4271 * Possible Reference STD1 * Informative Reference RFC5565 * Normative Reference RFC4303 * Normative Reference RFC4302 * Normative Reference RFC4301 * Normative Reference RFC4306 * Informative Reference RFC2385 * Normative Reference RFC5565 * Informative Reference RFC5619 * Informative Reference RFC6071 * Informative Reference DRAFT-XU-ISIS-ENCAPSULATION-CAP * Informative Reference DRAFT-XU-OSPF-ENCAPSULATION-CAP * Normative Reference DRAFT-VANDEVELDE-IDR-REMOTE-NEXT-HOP RFC5571: Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2) (41 pages) * Normative Reference RFC1332 * Normative Reference RFC3371 * Normative Reference RFC3193 * Normative Reference BCP5 * Informative Reference RFC1473 * Informative Reference RFC1471 * Normative Reference RFC3947 * Informative Reference RFC1877 * Informative Reference RFC4623 * Normative Reference RFC4818 * Normative Reference RFC3948 * Normative Reference RFC1994 * Normative Reference STD51 * Informative Reference RFC3575 * Normative Reference RFC1661 * Normative Reference RFC3162 * Normative Reference RFC2865 * Informative Reference RFC2867 * Informative Reference RFC2868 * Possible Reference STD1 * Informative Reference RFC2433 * Informative Reference RFC4787 * Normative Reference RFC3633 * Informative Reference RFC3022 * Informative Reference RFC3931 * Informative Reference RFC4293 * Normative Reference RFC3736 * Normative Reference RFC2661 * Informative Reference RFC5405 * Informative Reference BCP145 * Normative Reference RFC4862 * Informative Reference RFC4861 * Informative Reference RFC5080 * Informative Reference RFC2132 * Normative Reference RFC2119 * Informative Reference RFC2131 * Informative Reference RFC4193 * Informative Reference RFC4925 * Informative Reference RFC4087 * Normative Reference RFC3315 * Informative Reference RFC3748 * Informative Reference BCP127 * Normative Reference RFC5072 * Informative Reference RFC3646 * Informative Reference RFC4941 * Normative Reference RFC1918 * Normative Reference BCP14 * Informative Reference RFC5619 * Informative Reference RFC6333 * Normative Reference DRAFT-GUO-SOFTWIRE-SC-DISCOVERY * Normative Reference DRAFT-WBEEBEE-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-LEE-SOFTWIRE-6RD-UDP * Normative Reference DRAFT-GUO-SOFTWIRE-AUTO-GRE * Normative Reference DRAFT-HUANG-IPV6CP-OPTIONS * Possible Reference DRAFT-JANKIEWICZ-V6OPS-V4V6BIBLIO * Informative Reference DRAFT-CARPENTER-V6OPS-6TO4-TEREDO-ADVISORY * Informative Reference RFC6343 * Normative Reference DRAFT-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-IETF-V6OPS-IPV6-CPE-ROUTER-BIS * Possible Reference DRAFT-OPERATORS-SOFTWIRE-STATELESS-4V6-MOTIVATION * Informative Reference DRAFT-SUN-OPENV6-PROBLEM-STATEMENT * Informative Reference DRAFT-SUN-APONF-OPENV6-USE-CASES RFC5619: Softwire Security Analysis and Requirements (28 pages) * Informative Reference BCP146 * Informative Reference RFC3193 * Informative Reference RFC4016 * Informative Reference RFC4111 * Normative Reference RFC3947 * Normative Reference BCP14 * Informative Reference RFC5571 * Normative Reference RFC3948 * Normative Reference RFC1994 * Informative Reference RFC4081 * Informative Reference RFC4364 * Informative Reference RFC5565 * Informative Reference RFC3562 * Informative Reference RFC4593 * Informative Reference RFC4891 * Informative Reference RFC4213 * Normative Reference RFC4306 * Normative Reference RFC4107 * Informative Reference RFC5216 * Informative Reference RFC4272 * Informative Reference RFC2607 * Informative Reference RFC5406 * Normative Reference RFC2661 * Possible Reference STD1 * Normative Reference RFC2119 * Informative Reference RFC5566 * Normative Reference BCP107 * Informative Reference RFC4925 * Normative Reference RFC4303 * Normative Reference RFC4302 * Normative Reference RFC4301 * Informative Reference RFC2409 * Informative Reference RFC4225 * Normative Reference RFC2385 * Informative Reference RFC2401 * Normative Reference DRAFT-EUBANKS-CHIMENTO-6MAN * Normative Reference DRAFT-GUO-SOFTWIRE-AUTO-GRE * Informative Reference RFC6935 RFC5640: Load-Balancing for Mesh Softwires (6 pages) * Replaces DRAFT-PMOHAPAT-SOFTWIRE-LB * Normative Reference RFC2890 * Normative Reference RFC3931 * Normative Reference RFC2119 * Normative Reference RFC5512 * Normative Reference BCP14 * Possible Reference STD1 * Normative Reference RFC2784 * Informative Reference DRAFT-GEORGE-MPLS-IPV6-ONLY-GAP * Informative Reference DRAFT-XU-MPLS-IN-UDP * Informative Reference DRAFT-XU-IDR-TUNNEL-ADDRESS-PREFIX * Informative Reference DRAFT-XU-SOFTWIRE-IP-IN-UDP * Normative Reference DRAFT-KUMAR-SOFTWIRE-UET * Informative Reference RFC7439 * Informative Reference DRAFT-IETF-MPLS-IN-UDP * Informative Reference RFC7424 RFC5969: IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification (18 pages) * Informative Reference RFC3484 * Normative Reference RFC4291 * Normative Reference BCP5 * Normative Reference BCP14 * Informative Reference RFC2983 * Informative Reference RFC3964 * Normative Reference RFC1918 * Informative Reference RFC3068 * Normative Reference RFC3168 * Possible Reference RFC5741 * Informative Reference RFC3633 * Normative Reference RFC4213 * Normative Reference RFC2491 * Informative Reference RFC5214 * Informative Reference RFC5569 * Informative Reference RFC4632 * Normative Reference RFC4861 * Normative Reference RFC2132 * Normative Reference RFC2119 * Normative Reference RFC3056 * Informative Reference RFC2578 * Informative Reference BCP122 * Informative Reference STD58 * Normative Reference RFC7421 * Normative Reference RFC6264 * Informative Reference DRAFT-VANDEVELDE-V6OPS-HARMFUL-TUNNELS * Normative Reference DRAFT-WBEEBEE-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference RFC6324 * Informative Reference RFC6180 * Normative Reference DRAFT-GUO-SOFTWIRE-6RD-IPV6-CONFIG * Informative Reference RFC6342 * Informative Reference DRAFT-KUARSINGH-LSN-DEPLOYMENT * Informative Reference DRAFT-HUANG-V6OPS-V4V6TRAN-BB-USECASE * Informative Reference DRAFT-YANG-V6OPS-V4V6TRAN-BB-TRANSITION-GUIDE * Normative Reference DRAFT-LEE-V4V6TRAN-USECASE-CABLE * Possible Reference DRAFT-JANKIEWICZ-V6OPS-V4V6BIBLIO * Informative Reference RFC6732 * Informative Reference RFC6751 * Normative Reference DRAFT-LEE-V6OPS-TRAN-CABLE-USECASE * Normative Reference RFC6654 * Normative Reference DRAFT-GUO-SOFTWIRE-6RD-RADIUS-ATTRIB * Normative Reference RFC6930 * Normative Reference DRAFT-TSOU-SOFTWIRE-6RD-MULTICAST * Informative Reference DRAFT-CARPENTER-V6OPS-6TO4-TEREDO-ADVISORY * Informative Reference RFC6343 * Informative Reference DRAFT-IETF-V6OPS-6TO4-TO-HISTORIC * Normative Reference DRAFT-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference DRAFT-IETF-V6OPS-IPV6-CPE-ROUTER-BIS * Normative Reference RFC7084 * Informative Reference DRAFT-DESPRES-INTAREA-6A44 * Informative Reference DRAFT-MATSUSHIMA-V6OPS-TRANSITION-EXPERIENCE * Informative Reference DRAFT-DESPRES-INTAREA-4RD * Informative Reference DRAFT-TSOU-V6OPS-MULTICAST-TRANSITION-V6ONLY * Normative Reference DRAFT-SARIKAYA-SOFTWIRE-DSLITE6RDMULTICAST * Normative Reference DRAFT-SARIKAYA-SOFTWIRE-6RDMULTICAST * Possible Reference DRAFT-OPERATORS-SOFTWIRE-STATELESS-4V6-MOTIVATION * Informative Reference RFC6964 * Informative Reference DRAFT-ANDREWS-V6OPS-6TO4-ROUTER-OPTION * Normative Reference DRAFT-CAI-SOFTWIRE-6RD-MIB * Informative Reference DRAFT-YANG-V6OPS-FAST6-TOOLS-SELECTION * Informative Reference DRAFT-YANG-V6OPS-FAST6-PPPOE * Informative Reference DRAFT-SARIKAYA-SOFTWIRE-DSLITEMULTICAST * Informative Reference DRAFT-LI-V6OPS-LOAD-BALANCING-REQUIREMENT * Normative Reference DRAFT-TSOU-GWINIT-6RD * Normative Reference DRAFT-SAKURA-6RD-DATACENTER * Informative Reference DRAFT-MURAKAMI-SOFTWIRE-4RD * Informative Reference DRAFT-KUARSINGH-WIRELINE-INCREMENTAL-IPV6 * Informative Reference RFC6782 * Normative Reference DRAFT-FREEDMAN-PPPEXT-IPV6-6RD * Informative Reference DRAFT-DESPRES-SOFTWIRE-4RD-ADDMAPPING * Informative Reference DRAFT-DESPRES-SOFTWIRE-4RD-U * Informative Reference RFC7368 * Informative Reference DRAFT-SARIKAYA-SOFTWIRE-DSLITE4CLOUD * Informative Reference DRAFT-SARIKAYA-SOFTWIRE-V6MIGRATION4CLOUD * Informative Reference DRAFT-MDT-SOFTWIRE-MAPPING-ADDRESS-AND-PORT * Normative Reference DRAFT-TOWNSLEY-V6OPS-6RD-SUNSETTING * Normative Reference DRAFT-IETF-DHC-DHCPV6-TUNNEL * Normative Reference DRAFT-TOWNSLEY-TROAN-IPV6-CE-TRANSITIONING * Informative Reference DRAFT-MDT-SOFTWIRE-MAP-ENCAPSULATION * Normative Reference RFC7123 * Informative Reference RFC6724 * Informative Reference DRAFT-VYNCKE-OPSEC-V6 * Informative Reference DRAFT-DONLEY-V6OPS-CE-ROUTER-DESIGN * Informative Reference DRAFT-YANG-V6OPS-FAST6 * Normative Reference DRAFT-GONT-OPSEC-IPV6-IMPLICATIONS-ON-IPV4-NETS * Informative Reference RFC7289 * Normative Reference DRAFT-FOO-V6OPS-6RDMTU * Informative Reference DRAFT-IETF-SOFTWIRE-4RD * Informative Reference DRAFT-GENERIC-V6OPS-TUNMTU * Informative Reference DRAFT-IETF-SOFTWIRE-MAP * Possible Reference DRAFT-SHISHIO-SOFTWIRE-RFC4087UPDATE * Informative Reference DRAFT-IETF-OPSEC-V6 * Informative Reference RFC7059 * Normative Reference DRAFT-SHISHIO-V6OPS-DPVT * Informative Reference DRAFT-IETF-BEHAVE-SYSLOG-NAT-LOGGING * Informative Reference DRAFT-MOREIRAS-V6OPS-RFC3849BIS * Informative Reference DRAFT-SUN-OPENV6-PROBLEM-STATEMENT * Normative Reference DRAFT-ZHOU-SOFTWIRE-6RDMULTICAST * Informative Reference DRAFT-SUN-APONF-OPENV6-USE-CASES * Normative Reference DRAFT-JPCERT-IPV6VULLNERABILITY-CHECK RFC6333: Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion (32 pages) * Replaces DRAFT-DURAND-SOFTWIRE-DUAL-STACK-LITE * Informative Reference BCP162 * Informative Reference BCP142 * Informative Reference RFC2993 * Informative Reference RFC4787 * Informative Reference BCP5 * Informative Reference BCP148 * Normative Reference BCP14 * Informative Reference RFC5571 * Informative Reference RFC6334 * Informative Reference RFC1918 * Possible Reference RFC5741 * Normative Reference RFC4213 * Informative Reference RFC4033 * Normative Reference BCP152 * Normative Reference RFC2474 * Normative Reference RFC2473 * Informative Reference RFC2663 * Informative Reference RFC1191 * Informative Reference RFC5508 * Normative Reference RFC2119 * Normative Reference RFC5625 * Informative Reference RFC6269 * Informative Reference RFC5382 * Informative Reference RFC6302 * Informative Reference RFC5320 * Informative Reference BCP127 * Informative Reference RFC4987 * Informative Reference DRAFT-BOUCADAIR-NETWORK-FUNCTION-CHAINING * Informative Reference DRAFT-PERREAULT-SOFTWIRE-LW4OVER6-PCP * Normative Reference DRAFT-IETF-PCP-DSLITE * Informative Reference DRAFT-WAKIKAWA-REQ-MOBILE-CP-SEPARATION * Normative Reference DRAFT-IETF-SOFTWIRE-LW4OVER6 * Informative Reference DRAFT-NISHIZUKA-CGN-DEPLOYMENT-CONSIDERATIONS * Informative Reference DRAFT-IETF-RADEXT-IP-PORT-RADIUS-EXT * Normative Reference DRAFT-ZHOU-DIME-4OVER6-PROVISIONING * Normative Reference RFC6888 * Normative Reference RFC6334 * Normative Reference DRAFT-IETF-SOFTWIRE-UNIFIED-CPE * Informative Reference RFC6346 * Normative Reference RFC6674 * Informative Reference RFC6619 * Informative Reference RFC6947 * Informative Reference DRAFT-KUARSINGH-LSN-DEPLOYMENT * Informative Reference RFC6732 * Normative Reference DRAFT-IETF-SOFTWIRE-DSLITE-MULTICAST * Normative Reference RFC6519 * Normative Reference DRAFT-CUI-SOFTWIRE-B4-TRANSLATED-DS-LITE * Informative Reference RFC7021 * Informative Reference RFC6887 * Informative Reference DRAFT-BOUCADAIR-PCP-NAT-REVEAL * Informative Reference DRAFT-MAGLIONE-PCP-RADIUS-EXT * Informative Reference DRAFT-BOUCADAIR-PCP-FAILURE * Normative Reference RFC7084 * Informative Reference DRAFT-BPW-PCP-PROXY * Reference DRAFT-FLEISCHHAUER-IPV4-ADDR-SAVING * Normative Reference DRAFT-FU-SOFTWIRE-DSLITE-MIB * Informative Reference DRAFT-CHENG-BEHAVE-CGN-CFG-RADIUS-EXT * Normative Reference DRAFT-SARIKAYA-SOFTWIRE-DSLITEMULTICAST * Informative Reference DRAFT-GEORGE-IPV6-SUPPORT * Informative Reference DRAFT-KUARSINGH-WIRELINE-INCREMENTAL-IPV6 * Informative Reference RFC6782 * Normative Reference DRAFT-DUPONT-PCP-DSLITE * Informative Reference DRAFT-PERREAULT-OPSAWG-NATMIB-BIS * Normative Reference RFC7040 * Normative Reference RFC6908 * Informative Reference RFC7368 * Reference DRAFT-SUN-SOFTWIRE-STATELESS-4OVER6 * Informative Reference RFC7422 * Normative Reference DRAFT-SARIKAYA-SOFTWIRE-DSLITE4CLOUD * Normative Reference DRAFT-SARIKAYA-SOFTWIRE-V6MIGRATION4CLOUD * Informative Reference DRAFT-QIN-SOFTWIRE-MULTICAST-PREFIX-OPTION * Informative Reference DRAFT-LI-SOFTWIRE-DSLITE-INTRA-DOMAIN * Informative Reference DRAFT-MDT-SOFTWIRE-MAPPING-ADDRESS-AND-PORT * Normative Reference DRAFT-PENNO-SOFTWIRE-SDNAT * Informative Reference RFC7291 * Normative Reference DRAFT-XU-SAVI-TRANSITION * Informative Reference RFC6970 * Normative Reference DRAFT-BOUCADAIR-MMUSIC-IPV6-USE-CASES * Informative Reference DRAFT-MAWATARI-V6OPS-464XLAT * Informative Reference DRAFT-MKONSTAN-L2TPEXT-KEYED-IPV6-TUNNEL * Informative Reference DRAFT-TSOU-SOFTWIRE-PORT-SET-ALGORITHMS-ANALYSIS * Reference DRAFT-SUN-SOFTWIRE-LIGHTWEIGH-4OVER6-DEPLOYMENT * Normative Reference DRAFT-TSOU-BFD-DS-LITE * Normative Reference DRAFT-TSOU-SOFTWIRE-BFD-DS-LITE * Informative Reference DRAFT-IETF-SOFTWIRE-MULTICAST-PREFIX-OPTION * Informative Reference DRAFT-DONLEY-V6OPS-CE-ROUTER-DESIGN * Informative Reference DRAFT-IETF-BEHAVE-NAT-MIB * Informative Reference RFC7289 * Informative Reference DRAFT-GENERIC-V6OPS-TUNMTU * Informative Reference DRAFT-IETF-SOFTWIRE-MAP * Normative Reference RFC7393 * Normative Reference DRAFT-XLI-SOFTWIRE-MAP-TESTING * Normative Reference DRAFT-WU-SOFTWIRE-PUBLIC4OVER6-DEPLOYMENT * Possible Reference DRAFT-PERREAULT-SUNSET4-CGN-MIB * Possible Reference DRAFT-SHISHIO-SOFTWIRE-RFC4087UPDATE * Normative Reference DRAFT-IETF-SOFTWIRE-DSLITE-MIB * Normative Reference DRAFT-FARRER-SOFTWIRE-LW4O6-DETERMINISTIC-ARCH * Informative Reference DRAFT-IETF-OPSEC-V6 * Informative Reference RFC6890 * Informative Reference DRAFT-MAGLIONE-SOFTWIRE-MAP-T-SCENARIOS * Informative Reference DRAFT-BOUCADAIR-INTAREA-HOST-IDENTIFIER-SCENARIOS * Possible Reference DRAFT-MA-SOFTWIRE-DSLITE-TEST * Normative Reference DRAFT-CHEN-SUNSET4-TRAFFIC-MIGRATION * Normative Reference DRAFT-BFMK-SOFTWIRE-UNIFIED-CPE * Informative Reference RFC7059 * Normative Reference DRAFT-CHEN-SUNSET4-CGN-PORT-ALLOCATION * Informative Reference DRAFT-IETF-BEHAVE-SYSLOG-NAT-LOGGING * Normative Reference DRAFT-BYRNE-V6OPS-CLATIP * Informative Reference DRAFT-SUN-SOFTWIRE-LW4OVER6-RADEXT * Informative Reference DRAFT-SUN-SOFTWIRE-LW4OVER6-DHCPV6 * Informative Reference DRAFT-MATSUSHIMA-STATELESS-UPLANE-VEPC * Informative Reference DRAFT-MKONSTAN-KEYED-IPV6-TUNNEL * Normative Reference DRAFT-VINAPAMULA-SOFTWIRE-DSLITE-PREFIX-BINDING * Informative Reference DRAFT-BOUCADAIR-SERVICE-CHAINING-FRAMEWORK * Informative Reference DRAFT-BOUCADAIR-SFC-FRAMEWORK * Informative Reference DRAFT-SUN-OPENV6-PROBLEM-STATEMENT * Informative Reference DRAFT-LIU-6MAN-TUNNEL-MTU-CONFIG * Informative Reference DRAFT-LIU-6MAN-IDENT-TUNNEL-PACKET-ADDR * Informative Reference DRAFT-WILLIAMS-EXP-TCP-HOST-ID-OPT * Normative Reference DRAFT-MENG-SFC-BROADBAND-USECASES * Normative Reference DRAFT-CUI-INTAREA-UNIFIED-V6-FRAMEWORK * Reference DRAFT-JIANG-AUTO-ADDR-MANAGEMENT * Normative Reference RFC7335 * Informative Reference DRAFT-DENG-MPTCP-PROXY * Informative Reference DRAFT-CUI-SOFTWIRE-UNIFIED-V6-FRAMEWORK * Informative Reference DRAFT-SUN-APONF-OPENV6-USE-CASES * Normative Reference DRAFT-WANG-V6OPS-FLOW-LABEL-REFELCTION * Normative Reference DRAFT-SARIKAYA-DMM-FOR-WIFI * Updates RFC7335 * Informative Reference DRAFT-SUN-SOFTWIRE-YANG * Informative Reference DRAFT-BOUCADAIR-PCP-SIP-IPV6 * Informative Reference DRAFT-WANG-6MAN-FLOW-LABEL-REFLECTION * Normative Reference DRAFT-SONG-SUNSET4-IPV6ONLY-DNS * Informative Reference DRAFT-MI-SOFTWIRE-APPLICABLE-INDEX-ENCAPSULATION * Informative Reference DRAFT-PERRAULT-BEHAVE-NATV2-MIB * Informative Reference DRAFT-CHIMIAK-ENHANCED-IPV4 * Informative Reference DRAFT-BOUCADAIR-TRANSPORT-PROTOCOLS * Informative Reference DRAFT-BOUCADAIR-MPTCP-CONNECTIVITY-CHECKS * Normative Reference DRAFT-GEORGESCU-BMWG-IPV6-TRAN-TECH-BENCHMARKING RFC6334: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite (7 pages) * Replaces DRAFT-DHANKINS-SOFTWIRE-TUNNEL-OPTION * Normative Reference RFC6333 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference RFC1034 * Normative Reference RFC1035 * Normative Reference RFC3646 * Normative Reference RFC3596 * Normative Reference RFC2119 * Normative Reference STD13 * Normative Reference BCP14 * Normative Reference DRAFT-PERREAULT-SOFTWIRE-LW4OVER6-PCP * Informative Reference RFC7227 * Informative Reference DRAFT-ZHOU-DIME-4OVER6-PROVISIONING * Informative Reference DRAFT-IETF-SOFTWIRE-UNIFIED-CPE * Informative Reference RFC6333 * Normative Reference RFC6519 * Normative Reference DRAFT-CUI-SOFTWIRE-B4-TRANSLATED-DS-LITE * Normative Reference RFC7084 * Normative Reference RFC7040 * Normative Reference RFC6908 * Normative Reference DRAFT-SARIKAYA-SOFTWIRE-DSLITE4CLOUD * Normative Reference DRAFT-SARIKAYA-SOFTWIRE-V6MIGRATION4CLOUD * Reference DRAFT-SUN-SOFTWIRE-LIGHTWEIGH-4OVER6-DEPLOYMENT * Normative Reference DRAFT-TSOU-BFD-DS-LITE * Normative Reference DRAFT-TSOU-SOFTWIRE-BFD-DS-LITE * Informative Reference RFC7037 * Normative Reference DRAFT-WU-SOFTWIRE-PUBLIC4OVER6-DEPLOYMENT * Informative Reference DRAFT-BOUCADAIR-DHC-ADDRESS-NAME-ENCODING * Informative Reference DRAFT-BFMK-SOFTWIRE-UNIFIED-CPE * Normative Reference DRAFT-SUN-SOFTWIRE-LW4OVER6-RADEXT * Normative Reference DRAFT-SUN-SOFTWIRE-LW4OVER6-DHCPV6 * Informative Reference DRAFT-BOUCADAIR-MPTCP-SYMMETRIC RFC6519: RADIUS Extensions for Dual-Stack Lite (11 pages) * Normative Reference RFC2865 * Normative Reference RFC6334 * Informative Reference RFC5176 * Normative Reference RFC6333 * Normative Reference RFC3315 * Possible Reference RFC5741 * Normative Reference RFC5080 * Normative Reference RFC2119 * Normative Reference BCP14 * Informative Reference DRAFT-ZHOU-DIME-4OVER6-PROVISIONING * Normative Reference DRAFT-MAGLIONE-PCP-RADIUS-EXT * Normative Reference RFC6908 * Normative Reference RFC7037 * Normative Reference DRAFT-HU-SOFTWIRE-MULTICAST-RADIUS-EXT * Normative Reference DRAFT-MENG-SFC-BROADBAND-USECASES * Possible Reference DRAFT-DEKOK-RADEXT-DATATYPES RFC6674: Gateway-Initiated Dual-Stack Lite Deployment (15 pages) * Replaces DRAFT-GUNDAVELLI-SOFTWIRE-GATEWAY-INIT-DS-LITE * Replaces DRAFT-SOFTWIRE-GATEWAY-INIT-DS-LITE * Informative Reference RFC5555 * Normative Reference RFC4364 * Informative Reference RFC5844 * Normative Reference RFC2890 * Normative Reference RFC1918 * Informative Reference RFC4925 * Normative Reference RFC6275 * Normative Reference RFC2784 * Informative Reference RFC5213 * Normative Reference RFC6333 * Possible Reference RFC5741 * Normative Reference RFC5880 * Normative Reference BCP14 * Normative Reference RFC6437 * Normative Reference BCP5 * Normative Reference RFC2119 * Normative Reference RFC4379 * Informative Reference DRAFT-LIU-SERVICE-CHAINING-USE-CASES * Informative Reference DRAFT-IETF-BEHAVE-NAT-MIB * Informative Reference DRAFT-IETF-BEHAVE-SYSLOG-NAT-LOGGING * Informative Reference DRAFT-BOUCADAIR-SFC-DESIGN-ANALYSIS * Informative Reference DRAFT-LIU-SFC-USE-CASES * Informative Reference DRAFT-SUN-OPENV6-PROBLEM-STATEMENT * Informative Reference DRAFT-LIU-OPENV6-ARCHITECTURE * Informative Reference DRAFT-SUN-V6OPS-OPENV6-ADDRESS-POOL-MANAGEMENT * Informative Reference DRAFT-SUN-OPENV6-ADDRESS-POOL-MANAGEMENT * Informative Reference DRAFT-SUN-APONF-OPENV6-USE-CASES * Informative Reference DRAFT-IETF-PCP-THIRD-PARTY-ID-OPTION RFC6908: Deployment Considerations for Dual-Stack Lite (14 pages) * Informative Reference BCP160 * Informative Reference RFC4035 * Informative Reference BCP162 * Informative Reference RFC2983 * Informative Reference BCP152 * Normative Reference RFC6334 * Informative Reference RFC2475 * Informative Reference RFC6302 * Informative Reference RFC2473 * Normative Reference RFC6333 * Informative Reference RFC5245 * Possible Reference RFC5741 * Normative Reference RFC6519 * Informative Reference RFC6280 * Informative Reference RFC5985 * Informative Reference RFC3022 * Informative Reference RFC5625 * Informative Reference RFC6269 * Reference DRAFT-SUN-SOFTWIRE-LIGHTWEIGH-4OVER6-DEPLOYMENT * Informative Reference DRAFT-VINAPAMULA-SOFTWIRE-DSLITE-PREFIX-BINDING RFC6930: RADIUS Attribute for IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) (12 pages) * Informative Reference RFC2869 * Informative Reference RFC2607 * Normative Reference RFC3162 * Normative Reference RFC2865 * Informative Reference RFC3580 * Normative Reference BCP158 * Normative Reference RFC2119 * Possible Reference RFC5741 * Normative Reference RFC4301 * Normative Reference RFC6733 * Informative Reference RFC6929 * Normative Reference BCP14 * Normative Reference RFC6158 * Normative Reference RFC5080 * Normative Reference RFC2132 * Normative Reference RFC5969 * Normative Reference RFC2131 * Possible Reference DRAFT-DEKOK-RADEXT-DATATYPES RFC7040: Public IPv4-over-IPv6 Access Network (13 pages) * Possible Reference RFC5741 * Normative Reference RFC6333 * Normative Reference RFC2473 * Normative Reference RFC4925 * Normative Reference RFC6334 * Informative Reference DRAFT-IETF-SOFTWIRE-LW4OVER6 * Normative Reference DRAFT-SONG-SUNSET4-IPV6ONLY-DNS * Informative Reference DRAFT-MI-SOFTWIRE-APPLICABLE-INDEX-ENCAPSULATION Source Address Validation Improvements (savi) --------------------------------------------- Charter Last Modified: 2013-03-13 Current Status: Active Chair: Jean-Michel Combes Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Tech Advisor: Jianping Wu Secretary: Jun Bi Mailing Lists: General Discussion: savi@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/savi Archive: http://www.ietf.org/mail-archive/web/savi/ Description of Working Group: While ingress filtering [RFC 2827, BCP 38] provides a way to validate IP source addresses at an aggregated level, there is not yet a standardized mechanism for IP source address validation at a finer granularity. Having a finer granularity would be helpful in a number of situations, including filtering traffic from customer interfaces implemented as ports in a layer 3 aware bridge or a router, general improvements in filtering accuracy in enterprise networks, etc. Depending on the situation, there may be a requirement for blocking spoofed packets or merely logging packets that appear to be spoofed. Partial solutions exist to prevent nodes from spoofing the IP source address of another node in the same IP link (e.g., the "IP source guard"), but are proprietary. The purpose of the proposed "Source Address Validation Improvements" working group is to standardize mechanisms that prevent nodes attached to the same IP link from spoofing each other's IP addresses. The scope of the WG is as follows: - The working group considers only solutions implemented on systems located on the same IP link as a to-be-verified node. The goal of the working group is the LAN environment and solutions running in routers or layer 3 aware Ethernet bridges. - Both IPv4 and IPv6 need to be covered. - The first goal of the working group is on unicast traffic, but using the same mechanisms to police multicast traffic is also within the scope. - All address assignment mechanisms need to be supported, including stateless, stateful, and manual configuration; as well as privacy and cryptographically generated addresses. - Solutions are preferably based on observing user traffic, or on observing or using existing signaling protocols. Examples of protocols that can be useful to observe/use are ARP, Neighbor Discovery, DHCP, and DHCP Prefix Delegation protocols. Observing addresses in IP headers can also be useful. The gathered information is used to determine what IP source addresses in packets are appropriate. Where automatic operation is impossible or would lead to sub-optimal validation results, solutions may require manual configuration. - Interdomain scenarios (across Autonomous Systems) that require information from routing protocols like BGP are out of scope. Nevertheless, solution may observe routing protocol signaling to detect that a device is a router. - Tracking other protocols is not within the scope of the WG. - No changes to hosts are allowed. - The WG is prohibited from creating its own protocols or extensions/modifications of current protocols. These limitations in the scope may be relaxed through later rechartering. For instance, solutions tailored for PPP links and specific environments may be added later, or solutions involving co-operation of the nodes on the link may be developed once the baseline solutions have been completed. However, the WG is already chartered to work also on a solution for Ethernet-based broadband access networks that are used in DSL environments. This work is a specialization of the working group's primary LAN-based solution. In order to reach a result that is widely usable and unlikely to disturb existing network practices, the working group needs to take into account - nodes that use static addresses, - nodes with multiple IP addresses on the same interface, - nodes that use multiple link-layer addresses on the same interface, - nodes that have multiple interfaces to the same link, - attachment of another bridge at a bridge port, - presence of routers, NATs, and other similar devices on the same link, including their distinction from hosts with multiple interfaces or hosts with multiple IP addresses on a single interface, - use of SEcure Neighbor Discovery in some networks, - nodes that move to another port on the same link, and - hosts with anycast addresses. However, should such wide applicability turn out to be impossible, the working group will document the limitations of the solutions in due manner. In particular, it is likely that anycast addressing and nodes that employ multiple interfaces for load balancing at link layer are indistinguishable from an actual spoofing attack. There may also be a difference in the applicability between blocking and merely logging spoofed packets. In any case, the solutions may require to be explicitly turned on for each network or interface where they are applicable. For background information, the working group will also develop a threats analysis document that describes what threats the solutions from the WG protect against. This document also contrasts SAVI to existing solutions. Goals and Milestones: Jul 2008 - WG approval Aug 2008 - First WG draft on threats document Oct 2008 - First WG draft on SLAAC solution Dec 2008 - First WG draft on SeND solution Dec 2009 - First WG draft on DHCP solution Dec 2009 - First WG draft on protocol framework Mar 2010 - Submit document on threats to IESG for Informational RFC Mar 2010 - First WG draft on solution for Ethernet-based broadband access networks Dec 2010 - Submit Ethernet-based broadband access network solution to IESG for Proposed Standard Dec 2010 - Submit protocol framework to IESG for Informational RFC Dec 2010 - Submit SLAAC solution to IESG for Proposed Standard Dec 2010 - Submit SeND solution to IESG for Proposed Standard Dec 2010 - Submit DHCP solution to IESG for Proposed Standard Apr 2011 - First WG draft on mix scenario solution Jul 2011 - Submit mix scenario solution to IESG for Proposed Standard Internet-Drafts: - SAVI Solution for DHCP [draft-ietf-savi-dhcp-34] (53 pages) - FCFS SAVI: First-Come, First-Served Source Address Validation Improvement for Locally Assigned IPv6 Addresses [draft-ietf-savi-fcfs-14] (35 pages) - Source Address Validation Improvement (SAVI) Framework [draft-ietf-savi-framework-06] (14 pages) - SAVI for Mixed Address Assignment Methods Scenario [draft-ietf-savi-mix-07] (9 pages) - A Solution Space Analysis for First-Hop IP Source Address Validation [draft-ietf-savi-rationale-00] (6 pages) - SEcure Neighbor Discovery (SEND) Source Address Validation Improvement (SAVI) [draft-ietf-savi-send-11] (38 pages) - Source Address Validation Improvement (SAVI) Threat Scope [draft-ietf-savi-threat-scope-08] (25 pages) Requests for Comments: RFC6620: FCFS SAVI: First-Come, First-Served Source Address Validation Improvement for Locally Assigned IPv6 Addresses (35 pages) * Replaces DRAFT-BAGNULO-SAVI-FCFS * Normative Reference BCP38 * Informative Reference RFC1958 * Informative Reference RFC3971 * Possible Reference RFC5741 * Informative Reference RFC4862 * Normative Reference BCP14 * Normative Reference RFC4861 * Normative Reference RFC2827 * Informative Reference RFC4732 * Normative Reference RFC2119 * Informative Reference DRAFT-IETF-6TISCH-ARCHITECTURE * Normative Reference RFC7039 * Normative Reference DRAFT-IETF-SAVI-DHCP * Normative Reference DRAFT-AN-SAVI-MIB * Informative Reference RFC6957 * Normative Reference DRAFT-IETF-SAVI-MIX * Informative Reference RFC7219 * Informative Reference DRAFT-VYNCKE-OPSEC-V6 * Normative Reference DRAFT-IETF-6MAN-ENHANCED-DAD * Informative Reference DRAFT-RIBIERE-SAVI-PREFIX-GUARD * Informative Reference DRAFT-IETF-OPSEC-V6 * Possible Reference DRAFT-THUBERT-6TISCH-ARCHITECTURE * Normative Reference DRAFT-THUBERT-6MAN-WIND-SAIL * Normative Reference DRAFT-YOURTCHENKO-COLITTI-ND-REDUCE-MULTICAST * Normative Reference DRAFT-BI-SAVI-WLAN * Normative Reference DRAFT-IETF-OPSEC-IPV6-HOST-SCANNING * Informative Reference DRAFT-BAKER-OPENSTACK-IPV6-MODEL * Normative Reference DRAFT-YOURTCHENKO-6MAN-DAD-ISSUES * Normative Reference DRAFT-NORDMARK-6MAN-DAD-APPROACHES RFC6959: Source Address Validation Improvement (SAVI) Threat Scope (25 pages) * Replaces DRAFT-MCPHERSON-SAVI-THREAT-SCOPE * Informative Reference RFC4861 * Normative Reference RFC2460 * Normative Reference RFC791 * Possible Reference RFC5741 * Informative Reference RFC3704 * Informative Reference RFC826 * Informative Reference RFC4862 * Informative Reference RFC4271 * Informative Reference BCP38 * Informative Reference RFC4953 * Informative Reference RFC2827 * Informative Reference STD37 * Informative Reference BCP84 * Normative Reference RFC7039 * Informative Reference RFC7381 RFC7039: Source Address Validation Improvement (SAVI) Framework (14 pages) * Replaces DRAFT-VOGT-SAVI-FRAMEWORK * Normative Reference RFC2131 * Normative Reference RFC6620 * Normative Reference RFC5996 * Informative Reference BCP38 * Informative Reference BCP84 * Normative Reference RFC4862 * Possible Reference RFC5741 * Normative Reference RFC3971 * Normative Reference RFC5026 * Normative Reference RFC6959 * Normative Reference RFC3315 * Normative Reference RFC5739 * Informative Reference DRAFT-KARAGIANNIS-APONF-PROBLEM-STATEMENT * Informative Reference RFC7219 * Normative Reference DRAFT-AN-SAVI-MIB * Normative Reference DRAFT-IETF-SAVI-MIX * Normative Reference DRAFT-XU-SAVI-TRANSITION * Informative Reference DRAFT-IETF-OPSEC-V6 * Informative Reference DRAFT-IETF-MPTCP-ATTACKS * Informative Reference DRAFT-IETF-SAVI-DHCP RFC7219: SEcure Neighbor Discovery (SEND) Source Address Validation Improvement (SAVI) (38 pages) * Replaces DRAFT-BAGNULO-SAVI-SEND * Normative Reference RFC2119 * Informative Reference RFC2827 * Normative Reference RFC4861 * Normative Reference RFC4862 * Normative Reference RFC3972 * Possible Reference RFC5741 * Normative Reference RFC3971 * Informative Reference BCP38 * Informative Reference RFC7039 * Informative Reference RFC6434 * Normative Reference BCP14 * Informative Reference RFC6620 * Normative Reference DRAFT-IETF-SAVI-MIX * Normative Reference DRAFT-AN-SAVI-MIB * Informative Reference DRAFT-BAKER-OPENSTACK-IPV6-MODEL Sunsetting IPv4 (sunset4) ------------------------- Charter Last Modified: 2013-03-13 Current Status: Active Chairs: Marc Blanchet Wesley George Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Tech Advisors: Martin Stiemerling Stewart Bryant Fred Baker Mailing Lists: General Discussion: sunset4@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/sunset4 Archive: http://www.ietf.org/mail-archive/web/sunset4/ Description of Working Group: Global IPv4 addresses, once considered plentiful, are an increasingly scarce resource for many who wish to connect to the Internet today. IPv6 provides an abundance of freely available addresses, and while deployment alongside IPv4 has begun in earnest, much work remains. In order to fully transition the Internet to IPv6, individual applications, hosts, and networks that have enabled IPv6 must also be able to operate fully in the absence of IPv4. The Working Group will point out specific areas of concern, provide recommendations, and standardize protocols that facilitate the graceful "sunsetting" of the IPv4 Internet in areas where IPv6 has been deployed. This includes the act of shutting down IPv4 itself, as well as the ability of IPv6-only portions of the Internet to continue to connect with portions of the Internet that remain IPv4-only. While this work obviously spans multiple IETF areas including Internet, Operations, Transport, Applications, and Routing, this working group provides a single venue for the consideration of IPv4 sunsetting. Work in this group shall never impede the deployment of IPv6, will not duplicate functions and capabilities already available in existing technologies, and should demonstrate widespread operational need. Cross-area coordination and support is essential. Disabling IPv4 in applications, hosts, and networks is new territory for much of the Internet today, and it is expected that problems will be uncovered including those related to basic IPv4 functionality, interoperability, as well as potential security concerns. The working group will report on common issues, provide recommendations, and, when necessary, protocol extensions in order to facilitate disabling IPv4 in networks where IPv6 has been deployed. Operational scenarios considered by the working group shall include IPv6-only nodes and networks as the goal. Work on technologies that involve increased sharing of global IPv4 addresses should be limited to what is necessary for communicating with endpoints or over networks that are IPv6-only. The initial work items are: * NAT64 port allocation and address sharing methods involving scenarios where an IPv6-only node is present (and NAT44, as it overlaps NAT64 address sharing and port use). This may require a description of the use of an existing protocol, the development of extensions to an existing protocol, or the definition of an entirely new protocol. * Gap analysis of IPv4/IPv6 features to facilitate IPv4 sunsetting * Provisioning methods to signal a dual-stack host to disable or depreference the use of IPv4 Goals and Milestones: Mar 2014 - Submit gap analysis on IPv4 sunsetting to IESG for consideration as an Informational RFC Apr 2014 - Submit provisioning methods to signal a dual-stack host to disable the use of IPv4 to IESG for consideration as Proposed Standard Jul 2014 - Submit NAT64 port allocation and address sharing methods to IESG for consideration as an Informational RFC Internet-Drafts: - Gap Analysis for IPv4 Sunset [draft-ietf-sunset4-gapanalysis-05] (10 pages) - Turning off IPv4 Using DHCPv6 or Router Advertisements [draft-ietf-sunset4-noipv4-01] (14 pages) No Requests for Comments Timing over IP Connection and Transfer of Clock (tictoc) -------------------------------------------------------- Charter Last Modified: 2011-12-09 Current Status: Active Chairs: Yaakov Stein Karen O'Donoghue Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Brian Haberman Mailing Lists: General Discussion: tictoc@ietf.org To Subscribe: TICTOC-request@ietf.org Archive: http://www.ietf.org/mail-archive/web/tictoc Description of Working Group: The Timing over IP Connections and Transfer Of Clock (TICTOC) WG is concerned with highly accurate time and frequency distribution over native IP and MPLS-enabled IP Packet Switched Networks (PSNs). While this need arises from a variety of sources (see draft-bryant-tictoc-probstat-01.txt), the application areas of focus for this WG are: (1) Network infrastructures with the need for highly accurate time and frequency distribution within well-engineered service provider or enterprise campus networks. On-path support with specialized hardware may be expected to be available at one or more hops on a given path. (2) Individual hosts and devices on the public Internet requiring functionality or performance not currently available in NTP. On-path support may be utilized if available, but is not expected. This application brings additional requirements beyond improved accuracy, for example, the traceable and authenticated distribution of UTC time, including correct handling of leap seconds. The NTP Working Group is currently standardizing the fourth version of NTP for time distribution over IP networks. The NTP WG has focused its deliverables largely on standardizing the currently deployed NTPv4, while collecting requirements for future extensions. These requirements will transition to the tictoc WG for further development. Meeting those requirements may include revision of the protocol to a new version level. However, in all cases backwards compatibility and coexistence with currently deployed NTPv4 is a paramount concern. An applicability statement will describe the use cases for which any extension of NTP is targeted. The IEEE Test and Measurement Society is in the closing stages of standardizing a second version of IEEE1588. This is unofficially known as IEEE1588v2 and is expected to be published as IEEE1588-2008. IEEE1588v2 is emerging as a viable solution for time transfer over service provider and campus Ethernet networks, and for which on-path hardware support is becoming available. IEEE1588v2 specifically encourages other standards organizations to adapt it to their requirements, and provides guidelines for doing so. TICTOC will determine whether a profile for IEEE1588v2 over IP or MPLS-enabled IP networks would be suitable for (1), and if so will produce a profile within the guidelines provided in the IEEE1588v2 specification. An applicability statement will describe the use cases for which any profile of IEEE1588v2 is targeted. Time and Frequency distribution is considered by many to be a complex and often esoteric subject area. The WG will develop a modular framework in order to map out components within the solution space, define terminology, and identify common areas of protocol work that can be capitalized upon. TICTOC will also consider the co-existence of IEEE1588v2 and NTP in the same network. In doing so, TICTOC will first verify that the data model of NTP can be accommodated by IEEE1588v2 protocol operation and document any deficiencies compared to NTP. If there is a need to map the data models, it will produce a specification for how to utilize IEEE 1588 in a localized region as one portion of an NTP-based system. TICTOC protocols will be applicable to a variety of link layer technologies. To get the highest quality time and frequency transfer the user should take advantage of two types of on-path service where they are available: Link based frequency transfer, and hop-by-hop delay correction (for time). Examples of link based frequency support are SONET/SDH, TDM, Synchronous Ethernet and DSL with timing reference support. The main types of support that can be provided by a network element are boundary clock (where the clock is regenerated at the node in a multistage master slave relationship) and transparent clock where corrections are applied to time transfer packets as they pass through to compensate for the queuing delay, and where known for asymmetry in the link delay. Transparent clock (queue delay correction) requires routers to identify a time transfer packet, record the queuing delay, and either apply an on the fly correction to the packet, or to generate a follow-up packet with the necessary time correction information. TICTOC will ensure that any transparent clock design is acceptable in an Internet environment. On-path support is not a given, and TICTOC will investigate methods for automatically discovering when this support is available and when it is not. TICTOC will transfer time and frequency over both IP and IP enabled MPLS PSNs. One of the major users of TICTOC technology is the service provider community, where MPLS enabled IP networks are common. If necessary, TICTOC may take advantage of the path control properties of MPLS and the ability to signal modifications to per packet forwarding behavior. The security of time transfer, including the authentication of the time reference is an important consideration and must be designed in from the beginning. The ultimate system-level accuracy of time and frequency transfer depends on a number of factors outside the scope of the protocols themselves. Thus, even if it is possible for TICTOC to make a number of improvements at the protocol level to facilitate more accurate time and frequency transfer, it is impossible for the WG to provide system-level accuracy guarantees on its own. The TICTOC WG will co-ordinate with the PWE3 and NTP WGs in the IETF, as well as IEEE1588, IEEE 802.1AS and ITU-T SG15 Q13. It is also expected that active individuals in the TICTOC WG will propose the formation of an IRTF RG to study more advanced aspects of time and frequency distribution. First phase Objectives: - To develop a time and frequency distribution requirements document for the two cases listed above, including coexistence of the two as appropriate. - To develop a document defining the modular breakdown of functionality within the solution space. - To determine the extent to which these requirements can be satisfied using IEEE1588v2 and NTPv4 within each use case, along with an associated gap analysis for what requirements are not met without adaptation or extension of these protocols. - To develop an IEEE1588v2 profile as necessary for time and frequency distribution, with primary focus on (1). This profile will include a MIB module for IEEE1588v2. - To develop extensions to NTPv4 as necessary for time and frequency distribution, with primary focus on (2). - If required, to develop mechanisms for coexistence of IEEE1588v2 and NTP. - To document threat analyses and security mechanisms for all protocols developed by the WG. - To document media mappings for link layer technologies of interest. Second phase Objectives (requiring re-charter of the WG): To propose and document algorithms, protocols and mechanisms for transport, frequency acquisition, ranging, and packet selection/discard, master clock selection, path selection, OAM, synchronization status messaging, performance monitoring, security, and network management. Goals and Milestones: Sep 2008 - Problem statement document exits WGLC Nov 2008 - Modular Framework documentation document exits WGLC Jan 2009 - Requirements analysis for use cases, including gap analysis for NTPv4 and 1588v2 document exits WGLC Apr 2009 - 1588v2 profile, if needed, document exits WGLC Apr 2009 - NTPv4 extensions, if needed, document exits WGLC Apr 2009 - Security document(s) document exits WGLC Aug 2009 - MIB for IEEE 1588v2 profile and NTPv4 extensions (TICTOC MIB) document exits WGLC Aug 2009 - Prioritize second phase deliverables and add milestones or re-charter document exits WGLC Internet-Drafts: - TICTOC Problem Statement [draft-bryant-tictoc-probstat-02] (16 pages) - Transporting Timing messages over MPLS Networks [draft-ietf-tictoc-1588overmpls-06] (36 pages) - Multi-Path Time Synchronization [draft-ietf-tictoc-multi-path-synchronization-01] (16 pages) - Enterprise Profile for the Precision Time Protocol With Mixed Multicast and Unicast Messages [draft-ietf-tictoc-ptp-enterprise-profile-05] (12 pages) - Precision Time Protocol Version 2 (PTPv2) Management Information Base [draft-ietf-tictoc-ptp-mib-06] (78 pages) - TICTOC Requirement [draft-ietf-tictoc-requirements-01] (32 pages) - Security Requirements of Time Protocols in Packet Switched Networks [draft-ietf-tictoc-security-requirements-12] (36 pages) - Multi-Path Time Synchronization [draft-shpiner-multi-path-synchronization-03] (16 pages) - Architecture for the Transmission of Timing over Packet Networks [draft-stein-tictoc-modules-03] (22 pages) Requests for Comments: RFC7384: Security Requirements of Time Protocols in Packet Switched Networks (36 pages) * Informative Reference RFC4301 * Possible Reference RFC5741 * Informative Reference DRAFT-XU-TICTOC-IPSEC-SECURITY-FOR-SYNCHRONIZATION * Normative Reference RFC5905 * Informative Reference RFC5906 * Normative Reference BCP14 * Informative Reference RFC4430 * Normative Reference RFC2119 * Informative Reference DRAFT-IETF-NTP-NETWORK-TIME-SECURITY * Informative Reference DRAFT-MM-NETCONF-TIME-CAPABILITY * Informative Reference DRAFT-IETF-NTP-USING-NTS-FOR-NTP * Informative Reference DRAFT-FINN-DETNET-PROBLEM-STATEMENT * Informative Reference DRAFT-MIRSKY-MPLS-RESIDENCE-TIME * Informative Reference DRAFT-FINN-DETNET-ARCHITECTURE Transparent Interconnection of Lots of Links (trill) ---------------------------------------------------- Charter Last Modified: 2014-09-25 Current Status: Active Chairs: Susan Hares Jon Hudson Internet Area Directors: Brian Haberman Ted Lemon Internet Area Advisor: Ted Lemon Secretary: Donald Eastlake Mailing Lists: General Discussion: trill@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/trill Archive: http://www.ietf.org/mail-archive/web/trill/current/maillist.html Description of Working Group: The TRILL WG has specified a solution for transparent unicast shortest-path and multi-destination frame routing in multi-hop networks with arbitrary topology. End stations, including Layer 3 routers, connected to TRILL switches are assumed to be IEEE 802.1Q compliant end stations. TRILL switches may be interconnected with multi-access or point-to-point links of arbitrary technology. The current work of the working group is around operational support and additional extensions and optimizations of TRILL for the properties of the networks on which it is deployed. The TRILL WG may also produce corrections, clarifications, and updates of existing TRILL RFCs. The WG will work on the following items: (1) Following on from the TRILL OAM requirements (RFC 6905), specify a framework and specific protocols for the handling of Operations, Administration, and Maintenance (OAM) in networks using TRILL, focusing on fault management and performance and preferring existing OAM mechanisms that might apply to TRILL, such as SNMP, Netconf/Yang and mechanisms based on the IEEE 802.1 CFM framework. (2) Specify protocols to support "active-active" service to end stations that are multiply connected to a TRILL campus to provide them with flow level traffic spreading and rapid adaptation to link failure similar to that provided by TRILL for TRILL switches. (3) Develop, within the TRILL protocol context, protocol specifications for broadcast/multicast (multi-destination) frame reduction. Examples: protocol extensions supporting replacement of broadcast/multicast by unicast where appropriate; ARP/ND (Neighbor Discovery) reduction through extensions to the TRILL ESADI protocol. (4) Specify protocols for TRILL over pseudowires and TRILL over IP tunnels, for example to connect branch office TRILL switches to a central TRILL campus over the Internet. (5) Specify extensions to the TRILL protocol to support multi-level routing to improve scaling and multi-topology routing to provide different topologies for different classes or types of traffic, based existing IS-IS multi-level and multi-topology routing facilities. (6) Specify a reduced TRILL control plane protocol for interconnection, with improved error isolation, between TRILL campuses under coordinated management. (7) Analyze the use of IS-IS security (RFC 5310) in TRILL and determine if any work is needed to accommodate any specific TRILL control or data plane security leveraging IS-IS security. (8) Produce an interoperability / implementation report for TRILL. The TRILL WG will continue to work with other IETF working groups such as the ISIS WG, and SDO groups such as IEEE 802.1 through established inter-WG relationships and SDO liaison processes, including early and WG last call review by the ISIS WG of documents extending IS-IS routing. Goals and Milestones: Done - Accept base protocol specification as a WG document Done - Accept problem statement and applicability as a WG work item Done - Choose routing protocol(s) that can meet the requirements Done - Submit problem statement and applicability to IESG for Informational RFC Done - Submit base protocol specification to IEEE/IETF expert review Done - Base protocol specification submitted to the IESG for publication as a Proposed Standard RFC Done - Initial WG draft on VLAN Mapping (draft-ietf-trill-rbridge-vlan-mapping) Done - Initial WG draft on trill adjacency state machine (draft-ietf-trill-adj) Done - Submit trill adjacency state machine to IESG for publication as Proposed Standard (draft-ietf-trill-adj) Done - Submit RBridge MIB module to IESG for publication as Proposed Standard (draft-ietf-trill-rbridge-mib) Done - Submit TRILL Header Options to IESG for publication as Proposed Standard (draft-ietf-trill-rbridge-options) Done - Initial WG draft on RBridge OAM (draft-bond-trill-rbridge-oam) Done - Initial WG draft on RBridge OAM (draft-bond-trill-rbridge-oam) Done - Submit RBridge OAM requirements document to the IESG for publication Done - Initial WG framework document on RBridge OAM Done - Initial WG document on RBridge OAM fault management Done - Initial WG document on RBridge OAM performance management Done - Initial WG draft on TRILL over IP Done - Submit RBridge OAM framework document to the IESG for publication Done - Submit OAM Fault Management to IESG for Proposed Standard Done - Submit OAM Performance Management to IESG for Proposed Standard Dec 2014 - Submit Active-Active to IESG for Proposed Standard Dec 2014 - Submit TRILL-over-IP to IESG for Proposed Standard Jan 2015 - Initial WG draft on ARP/ND optimizations Apr 2015 - Submit TRILL ARP/ND optimizations to IESG for publication as Proposed Standard Apr 2015 - Initial WG draft on TRILL Implementation Report May 2015 - Submit Multi-level TRILL to IESG for Proposed Standard Jun 2015 - Initial WG draft on TRILL IS-IS Security Aug 2015 - Submit Multi-topology TRILL to IESG for Proposed Standard Dec 2015 - Submit RBridge support of Data Center Bridging to IESG for publication as Proposed Standard (draft-eastlake-trill-rbridge-dcb) Aug 2016 - Re-charter or shut down the WG Internet-Drafts: - TRILL OAM MIB [draft-deepak-trill-oam-mib-01] (50 pages) - YANG Data Model for TRILL Operations, Administration, and Maintenance (OAM) Performance Management [draft-deepak-trill-yang-pm-01] (38 pages) - Directory Assisted RBridge Edge [draft-dunbar-trill-directory-assisted-edge-05] (14 pages) - Directory Assisted TRILL Encapsulation [draft-dunbar-trill-directory-assisted-encap-08] (11 pages) - TRILL: Edge Directory Assistance Mechanisms [draft-dunbar-trill-scheme-for-directory-assist-06] (36 pages) - TRILL: RBridge Channel Tunnel Protocol [draft-eastlake-trill-channel-tunnel-00] (25 pages) - TRILL: Interface Addresses APPsub-TLV [draft-eastlake-trill-ia-appsubtlv-03] (24 pages) - TRILL: Adjacency [draft-eastlake-trill-rfc6327bis-00] (39 pages) - TRILL: Clarifications, Corrections, and Updates [draft-eastlake-trill-rfc7180bis-01] (52 pages) - Centralized Replication for BUM traffic in active-active edge connection [draft-hao-trill-centralized-replication-02] (15 pages) - TRILL Distributed Layer 3 Gateway [draft-hao-trill-irb-05] (20 pages) - TRILL YANG Data Model [draft-hao-trill-yang-01] (27 pages) - TRILL: The ESADI Protocol [draft-hu-trill-rbridge-esadi-04] (19 pages) - PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol [draft-ietf-pppext-trill-protocol-08] (8 pages) - TRILL Active-Active Edge Using Multiple MAC Attachments [draft-ietf-trill-aa-multi-attach-03] (19 pages) - Problem Statement and Goals for Active-Active Connection at the Transparent Interconnection of Lots of Links (TRILL) Edge [draft-ietf-trill-active-active-connection-prob-07] (13 pages) - Routing Bridges (RBridges): Adjacency [draft-ietf-trill-adj-07] (26 pages) - Centralized Replication for BUM traffic in active-active edge connection [draft-ietf-trill-centralized-replication-01] (14 pages) - TRILL: RBridge Channel Tunnel Protocol [draft-ietf-trill-channel-tunnel-04] (28 pages) - Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates [draft-ietf-trill-clear-correct-06] (24 pages) - Coordinated Multicast Trees (CMT) for TRILL [draft-ietf-trill-cmt-06] (17 pages) - TRILL: Edge Directory Assist Mechanisms [draft-ietf-trill-directory-assist-mechanisms-01] (38 pages) - Directory Assisted TRILL Encapsulation [draft-ietf-trill-directory-assisted-encap-00] (11 pages) - Directory Assistance Problem and High-Level Design Proposal [draft-ietf-trill-directory-framework-07] (15 pages) - Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) Protocol [draft-ietf-trill-esadi-09] (31 pages) - Transparent Interconnection of Lots of Links (TRILL): Fine-Grained Labeling [draft-ietf-trill-fine-labeling-07] (27 pages) - TRILL: Interface Addresses APPsub-TLV [draft-ietf-trill-ia-appsubtlv-02] (25 pages) - TRILL Distributed Layer 3 Gateway [draft-ietf-trill-irb-03] (20 pages) - Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL) [draft-ietf-trill-loss-delay-08] (32 pages) - TRILL IS-IS MTU Negotiation [draft-ietf-trill-mtu-negotiation-00] (12 pages) - Transparent Interconnection of Lots of Links (TRILL) Transport Using Pseudowires [draft-ietf-trill-o-pw-06] (11 pages) - Transparent Interconnection of Lots of Links (TRILL): Fault Management [draft-ietf-trill-oam-fm-11] (63 pages) - Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) Framework [draft-ietf-trill-oam-framework-04] (33 pages) - TRILL OAM MIB [draft-ietf-trill-oam-mib-02] (52 pages) - Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL) [draft-ietf-trill-oam-req-05] (13 pages) - Transparent Interconnection of Lots of Links (TRILL) over IP [draft-ietf-trill-over-ip-02] (19 pages) - Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement [draft-ietf-trill-prob-06] (17 pages) - TRILL: Pseudo-Nickname for Active-Active Access [draft-ietf-trill-pseudonode-nickname-04] (31 pages) - Routing Bridges (RBridges): Appointed Forwarders [draft-ietf-trill-rbridge-af-05] (15 pages) - The Architecture of an RBridge Solution to TRILL [draft-ietf-trill-rbridge-arch-05] (36 pages) - Transparent Interconnection of Lots of Links (TRILL): Bidirectional Forwarding Detection (BFD) Support [draft-ietf-trill-rbridge-bfd-07] (12 pages) - Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Support [draft-ietf-trill-rbridge-channel-08] (21 pages) - Transparent Interconnection of Lots of Links (TRILL): Header Extension [draft-ietf-trill-rbridge-extension-05] (12 pages) - Definitions of Managed Objects for Routing Bridges (RBridges) [draft-ietf-trill-rbridge-mib-10] (59 pages) - Routing Bridges (RBridges): Operations, Administration, and Maintenance (OAM) Support [draft-ietf-trill-rbridge-oam-02] (33 pages) - RBridges: Further TRILL Header Extensions [draft-ietf-trill-rbridge-options-07] (19 pages) - Routing Bridges (RBridges): Base Protocol Specification [draft-ietf-trill-rbridge-protocol-16] (99 pages) - TRILL: Campus Label and Priority Regions [draft-ietf-trill-rbridge-vlan-mapping-10] (19 pages) - TRILL Resilient Distribution Trees [draft-ietf-trill-resilient-trees-02] (19 pages) - Transparent Interconnection of Lots of Links (TRILL): Adjacency [draft-ietf-trill-rfc6327bis-04] (35 pages) - TRILL: Clarifications, Corrections, and Updates [draft-ietf-trill-rfc7180bis-03] (59 pages) - TRILL Routing Requirements in Support of RBridges [draft-ietf-trill-routing-reqs-02] (11 pages) - TRILL Smart Endnodes [draft-ietf-trill-smart-endnodes-00] (10 pages) - TRILL YANG Data Model [draft-ietf-trill-yang-00] (None pages) - YANG Data Model for TRILL Operations, Administration, and Maintenance (OAM) [draft-ietf-trill-yang-oam-00] (24 pages) - YANG Data Model for TRILL Operations, Administration, and Maintenance (OAM) Performance Management [draft-ietf-trill-yang-pm-00] (38 pages) - Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL) [draft-mizrahi-trill-loss-delay-01] (34 pages) - Transparent Interconnection of Lots of Links (TRILL) over IP [draft-mrw-trill-over-ip-04] (15 pages) - TRILL Smart Endnodes [draft-perlman-trill-smart-endnodes-04] (10 pages) - TRILL Fault Management [draft-tissa-trill-oam-fm-02] (53 pages) - YANG Data Model for TRILL Operations, Administration, and Maintenance (OAM) [draft-tissa-trill-yang-oam-00] (24 pages) - Problem Statement and Goals for Active-Active TRILL Edge [draft-yizhou-trill-active-active-connection-prob-02] (10 pages) - TRILL: ARP/ND Optimization [draft-yizhou-trill-arp-optimization-01] (10 pages) - TRILL Over Pseudowires [draft-yong-trill-o-pw-01] (10 pages) - TRILL IS-IS MTU Negotiation [draft-zhang-trill-mtu-negotiation-08] (12 pages) - TRILL Resilient Distribution Trees [draft-zhang-trill-resilient-trees-04] (19 pages) Requests for Comments: RFC5556: Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement (17 pages) * Replaces DRAFT-TOUCH-TRILL-PROB * Informative Reference RFC3376 * Informative Reference RFC4286 * Informative Reference RFC3927 * Informative Reference RFC1812 * Informative Reference RFC4826 * Informative Reference RFC4861 * Informative Reference RFC3971 * Informative Reference RFC4541 * Informative Reference RFC826 * Informative Reference RFC3819 * Informative Reference STD37 * Informative Reference BCP89 * Informative Reference RFC6325 * Informative Reference DRAFT-TOUCH-INTAREA-TUNNELS * Informative Reference DRAFT-IETF-INTAREA-TUNNELS * Informative Reference RFC6606 * Informative Reference DRAFT-ZEBROSE-TRILL-RBRIDGE-MIB * Informative Reference RFC6850 * Informative Reference RFC6361 * Informative Reference DRAFT-MALC-ARMD-MOOSE * Informative Reference DRAFT-EASTLAKE-RBRIDGE-COMPATIBILITY * Informative Reference DRAFT-EASTLAKE-TRILL-RBRIDGE-FINE-LABELING * Informative Reference DRAFT-SRIDHARAN-VIRTUALIZATION-NVGRE * Normative Reference DRAFT-JANAPATH-OPSAWG-FLOWOAM-REQ RFC6325: Routing Bridges (RBridges): Base Protocol Specification (99 pages) * Replaces DRAFT-PERLMAN-TRILL-RBRIDGE-PROTOCOL * Normative Reference RFC3376 * Informative Reference RFC5556 * Normative Reference RFC4286 * Informative Reference RFC5342 * Normative Reference RFC5226 * Normative Reference RFC2464 * Normative Reference RFC5303 * Informative Reference RFC5304 * Normative Reference RFC5305 * Normative Reference RFC2710 * Informative Reference RFC4541 * Normative Reference BCP14 * Informative Reference RFC1661 * Informative Reference RFC4789 * Informative Reference RFC4086 * Informative Reference BCP141 * Possible Reference RFC5741 * Normative Reference RFC3419 * Informative Reference RFC3411 * Normative Reference RFC3417 * Informative Reference RFC5310 * Informative Reference BCP106 * Normative Reference RFC1112 * Normative Reference RFC1195 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC6326 * Normative Reference RFC6165 * Informative Reference STD62 * Updates RFC6327 * Updates RFC6439 * Normative Reference DRAFT-IETF-TRILL-RESILIENT-TREES * Normative Reference DRAFT-YONG-TRILL-O-PW * Informative Reference DRAFT-DUNBAR-NVO3-NVA-GAP-ANALYSIS * Possible Reference DRAFT-HAO-EVPN-MHN * Normative Reference DRAFT-DEEPAK-TRILL-OAM-MIB * Normative Reference DRAFT-EASTLAKE-TRILL-MULTI-TOPOLOGY * Normative Reference DRAFT-EASTLAKE-TRILL-RFC6327BIS * Normative Reference DRAFT-HAO-TRILL-IRB * Updates RFC7357 * Normative Reference DRAFT-IETF-TRILL-IA-APPSUBTLV * Normative Reference DRAFT-HAO-TRILL-ANALYSIS-ACTIVE-ACTIVE * Updates RFC7180 * Updates RFC7179 * Updates RFC7177 * Updates RFC7172 * Normative Reference DRAFT-IETF-TRILL-RBRIDGE-OPTIONS * Informative Reference DRAFT-IETF-TRILL-RBRIDGE-VLAN-MAPPING * Possible Reference DRAFT-HAO-L2VPN-EVPN-MHN * Informative Reference RFC6328 * Informative Reference DRAFT-KASHIMA-IPFIX-DATA-LINK-LAYER-MONITORING * Normative Reference RFC6850 * Normative Reference RFC6361 * Normative Reference DRAFT-HAO-TRILL-DUP-AVOIDANCE-ACTIVE-ACTIVE * Normative Reference RFC6326 * Normative Reference DRAFT-EASTLAKE-TRILL-RBRIDGE-DCB * Normative Reference RFC7175 * Normative Reference DRAFT-EASTLAKE-TRILL-RBRIDGE-MORE-OPTIONS * Normative Reference DRAFT-IETF-TRILL-RBRIDGE-OAM * Normative Reference RFC7178 * Normative Reference DRAFT-IETF-TRILL-CHANNEL-TUNNEL * Informative Reference RFC6327 * Normative Reference DRAFT-HU-TRILL-RBRIDGE-VRRP * Normative Reference DRAFT-ZHANG-TRILL-VLAN-ASSIGN * Normative Reference DRAFT-PERLMAN-TRILL-RBRIDGE-MULTILEVEL * Normative Reference RFC6439 * Normative Reference RFC6847 * Normative Reference DRAFT-PERLMAN-TRILL-RBRIDGE-DATA-ENCODING * Normative Reference DRAFT-HU-TRILL-PSEUDONODE-NICKNAME * Normative Reference DRAFT-HU-TRILL-RBRIDGE-ESADI * Informative Reference DRAFT-EASTLAKE-RBRIDGE-COMPATIBILITY * Normative Reference DRAFT-EASTLAKE-TRILL-RBRIDGE-FINE-LABELING * Normative Reference DRAFT-EASTLAKE-TRILL-RBRIDGE-MULTI-TOPO * Informative Reference RFC7348 * Normative Reference DRAFT-YIZHOU-TRILL-MULTI-DESTINATION-PING * Informative Reference DRAFT-NARTEN-NVO3-OVERLAY-PROBLEM-STATEMENT * Normative Reference DRAFT-TISSA-TRILL-OAM * Normative Reference DRAFT-MRW-TRILL-OVER-IP * Normative Reference DRAFT-YONG-TRILL-TRILL-O-MPLS * Normative Reference DRAFT-ZHANG-TRILL-AGGREGATION * Normative Reference DRAFT-EASTLAKE-TRILL-RBRIDGE-CLEAR-CORRECT * Normative Reference DRAFT-BITAR-DATACENTER-VPN-APPLICABILITY * Normative Reference DRAFT-EASTLAKE-ISIS-RFC6326BIS * Normative Reference RFC7179 * Normative Reference DRAFT-XL-TRILL-OVER-WAN * Normative Reference RFC7172 * Normative Reference DRAFT-TISSA-TRILL-CMT * Normative Reference DRAFT-ZHANG-TRILL-DVLAN-AUTO * Normative Reference DRAFT-HU-TRILL-TRAFFIC-ENGINEERING * Informative Reference RFC7180 * Normative Reference DRAFT-ZHANG-TRILL-MULTI-TOPO-RPFC * Normative Reference DRAFT-TISSA-TRILL-MULTILEVEL * Normative Reference DRAFT-ROHIT-TRILL-PROACTIVE-OAM * Normative Reference DRAFT-HAO-TRILL-CENTRALIZED-REPLICATION * Normative Reference DRAFT-YIZHOU-TRILL-TREE-SELECTION * Normative Reference DRAFT-ALDRIN-TRILL-DATA-CENTER-INTERCONNECT * Normative Reference DRAFT-EASTLAKE-TRILL-LLDP * Normative Reference DRAFT-DUNBAR-TRILL-SCHEME-FOR-DIRECTORY-ASSIST * Possible Reference DRAFT-TISSA-TRILL-MT-ENCODE * Normative Reference DRAFT-IETF-TRILL-CMT * Informative Reference DRAFT-TISSA-TRILL-OAM-REQ * Normative Reference DRAFT-KVK-TRILL-FAIR-SHARE-AF-LOAD-SHARE * Normative Reference DRAFT-IETF-L2VPN-TRILL-EVPN * Informative Reference RFC7357 * Informative Reference DRAFT-TISSA-TRILL-8021AG * Normative Reference DRAFT-SALAM-TRILL-OAM-FRAMEWORK * Normative Reference DRAFT-ZHANG-TRILL-RESILIENT-TREES * Informative Reference RFC6905 * Normative Reference DRAFT-YIZHOU-TRILL-TC-AWARENESS * Normative Reference DRAFT-WU-TRILL-LSP-EXT-TREE-DISTR-OPT * Informative Reference RFC7067 * Informative Reference DRAFT-LAPUKHOV-BGP-ROUTING-LARGE-DC * Normative Reference DRAFT-ALDRIN-TRILL-CAMPUS-EXTENSION * Informative Reference RFC7364 * Normative Reference DRAFT-PERLMAN-TRILL-CLOUDLET * Normative Reference DRAFT-BITAR-NVO3-VPN-APPLICABILITY * Normative Reference DRAFT-HY-NVO3-VPN-PROTOCOL-GAP-ANALYSIS * Normative Reference DRAFT-TISSA-TRILL-OAM-FM * Normative Reference DRAFT-ZHAI-ESADI-EXTENSION-FOR-RBV * Normative Reference DRAFT-ZHAI-TRILL-ESADI-EXTENSION-FOR-RBV * Normative Reference RFC7176 * Normative Reference DRAFT-EASTLAKE-TRILL-NICK-LABEL-PROP * Normative Reference RFC7177 * Normative Reference DRAFT-HAO-TRILL-RB-SYN * Normative Reference RFC7174 * Normative Reference DRAFT-PERLMAN-TRILL-SMART-ENDNODES * Informative Reference DRAFT-EASTLAKE-TRILL-PFC-ETS * Normative Reference DRAFT-EASTLAKE-TRILL-CN * Normative Reference DRAFT-YANG-TRILL-PARENT-SELETION * Informative Reference DRAFT-GINSBERG-ISIS-FS-LSP * Normative Reference DRAFT-WU-NVO3-MAC-LEARNING-ARP * Normative Reference DRAFT-EASTLAKE-TRILL-VENDOR-CHANNEL * Normative Reference DRAFT-CHEN-TRILL-ISIS-PURGE * Normative Reference DRAFT-YIZHOU-TRILL-ACTIVE-ACTIVE-CONNECTION-PROB * Normative Reference DRAFT-MIZRAHI-TRILL-LOSS-DELAY * Normative Reference DRAFT-YONG-PWE3-TRILL-O-PW * Normative Reference RFC7455 * Normative Reference DRAFT-EASTLAKE-TRILL-IA-APPSUBTLV * Normative Reference RFC7173 * Informative Reference RFC7356 * Normative Reference DRAFT-ZHANG-TRILL-ACTIVE-ACTIVE-CP-REQ * Normative Reference DRAFT-EASTLAKE-TRILL-CHANNEL-TUNNEL * Normative Reference DRAFT-IETF-TRILL-OAM-MIB * Reference DRAFT-OTIS-DNSSD-MDNS-XLINK * Normative Reference DRAFT-XIA-NVO3-L2GW * Normative Reference DRAFT-HAO-TRILL-ANYCAST-GW * Normative Reference DRAFT-IETF-TRILL-DIRECTORY-ASSIST-MECHANISMS * Normative Reference DRAFT-IETF-TRILL-OVER-IP * Informative Reference DRAFT-TISSA-NETMOD-OAM * Informative Reference DRAFT-TISSA-NVO3-YANG-OAM * Informative Reference DRAFT-TISSA-TRILL-YANG-OAM * Informative Reference DRAFT-IETF-TRILL-AA-MULTI-ATTACH * Normative Reference RFC7456 * Normative Reference DRAFT-UMAIR-MULTIPLE-TRILL-CAMPUS-TO-LAN * Normative Reference DRAFT-ZHANG-TRILL-MTU-NEGOTIATION * Informative Reference DRAFT-IETF-RTGWG-BGP-ROUTING-LARGE-DC * Informative Reference DRAFT-HAO-TRILL-YANG * Informative Reference DRAFT-IETF-TRILL-YANG-OAM * Normative Reference DRAFT-BESTLER-TRANSACTIONAL-SUBSET-MULTICAST * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Normative Reference RFC7379 * Possible Reference DRAFT-DONG-I2RS-L2-NETWORK-TOPOLOGY * Informative Reference DRAFT-TISSA-LIME-YANG-OAM-MODEL * Normative Reference DRAFT-YIZHOU-TRILL-ARP-OPTIMIZATION * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS * Informative Reference DRAFT-DEEPAK-TRILL-YANG-PM * Normative Reference DRAFT-IETF-TRILL-SMART-ENDNODES * Normative Reference DRAFT-IETF-TRILL-DIRECTORY-ASSISTED-ENCAP * Normative Reference DRAFT-IETF-TRILL-CENTRALIZED-REPLICATION * Normative Reference DRAFT-ZHANG-TRILL-P2MP-BFD * Informative Reference DRAFT-IETF-TRILL-YANG-PM * Normative Reference DRAFT-IETF-TRILL-IRB * Possible Reference DRAFT-DUNBAR-NVO3-NVA-MAPPING-DISTRIBUTION * Informative Reference DRAFT-EASTLAKE-TRILL-RFC6439BIS * Normative Reference DRAFT-IETF-TRILL-MTU-NEGOTIATION * Normative Reference DRAFT-ZHANG-TRILL-MULTILEVEL-SINGLE-NICKNAME * Normative Reference DRAFT-IETF-TRILL-PSEUDONODE-NICKNAME * Normative Reference DRAFT-EASTLAKE-TRILL-LINK-SECURITY * Updates RFC7455 RFC6327: Routing Bridges (RBridges): Adjacency (26 pages) * Updates RFC6325 * Informative Reference RFC3719 * Normative Reference RFC6326 * Informative Reference RFC6325 * Possible Reference RFC5741 * Informative Reference RFC5880 * Normative Reference RFC1195 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference DRAFT-EASTLAKE-TRILL-RFC6327BIS * Updates RFC7180 * Obsoletes RFC7177 * Informative Reference DRAFT-IETF-TRILL-RBRIDGE-VLAN-MAPPING * Normative Reference RFC6326 * Normative Reference DRAFT-ZHANG-TRILL-VLAN-ASSIGN * Normative Reference RFC6439 * Informative Reference DRAFT-PERLMAN-TRILL-RBRIDGE-DATA-ENCODING * Normative Reference DRAFT-HU-TRILL-RBRIDGE-ESADI * Informative Reference DRAFT-EASTLAKE-TRILL-RBRIDGE-FINE-LABELING * Normative Reference DRAFT-TISSA-TRILL-OAM * Informative Reference DRAFT-EASTLAKE-TRILL-RBRIDGE-CLEAR-CORRECT * Normative Reference DRAFT-EASTLAKE-ISIS-RFC6326BIS * Normative Reference DRAFT-XL-TRILL-OVER-WAN * Normative Reference DRAFT-TISSA-TRILL-CMT * Normative Reference DRAFT-ZHANG-TRILL-DVLAN-AUTO * Normative Reference RFC7180 * Normative Reference DRAFT-EASTLAKE-TRILL-LLDP * Normative Reference DRAFT-SALAM-TRILL-OAM-FRAMEWORK * Normative Reference DRAFT-YIZHOU-TRILL-TC-AWARENESS * Informative Reference RFC7177 * Normative Reference DRAFT-HAO-TRILL-RB-SYN * Normative Reference DRAFT-UMAIR-MULTIPLE-TRILL-CAMPUS-TO-LAN * Informative Reference DRAFT-YONG-PWE3-TRILL-O-PW * Normative Reference DRAFT-ZHANG-TRILL-ACTIVE-ACTIVE-CP-REQ * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS RFC6361: PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol (8 pages) * Informative Reference RFC1968 * Normative Reference STD51 * Normative Reference RFC1661 * Informative Reference RFC3931 * Normative Reference RFC5226 * Informative Reference RFC6326 * Normative Reference RFC6325 * Informative Reference RFC5310 * Informative Reference RFC5304 * Informative Reference RFC3748 * Informative Reference RFC3518 * Possible Reference RFC5741 * Informative Reference RFC5556 * Normative Reference BCP14 * Informative Reference RFC2153 * Informative Reference RFC1994 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference DRAFT-YONG-TRILL-O-PW * Informative Reference DRAFT-EASTLAKE-TRILL-RFC6327BIS * Informative Reference RFC7175 * Informative Reference DRAFT-PERLMAN-TRILL-RBRIDGE-MULTILEVEL * Informative Reference DRAFT-PERLMAN-TRILL-RBRIDGE-DATA-ENCODING * Informative Reference DRAFT-MRW-TRILL-OVER-IP * Normative Reference DRAFT-YONG-TRILL-TRILL-O-MPLS * Informative Reference DRAFT-EASTLAKE-TRILL-LLDP * Normative Reference RFC7357 * Possible Reference DRAFT-SALAM-TRILL-OAM-FRAMEWORK * Informative Reference DRAFT-TISSA-TRILL-OAM-FM * Informative Reference RFC7177 * Informative Reference RFC7174 * Normative Reference DRAFT-YONG-PWE3-TRILL-O-PW * Informative Reference RFC7455 * Normative Reference RFC7173 * Informative Reference DRAFT-IETF-TRILL-CHANNEL-TUNNEL * Informative Reference DRAFT-EASTLAKE-TRILL-CHANNEL-TUNNEL * Reference DRAFT-OTIS-DNSSD-MDNS-XLINK * Informative Reference DRAFT-IETF-TRILL-OVER-IP * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS * Normative Reference DRAFT-EASTLAKE-TRILL-LINK-SECURITY RFC6439: Routing Bridges (RBridges): Appointed Forwarders (15 pages) * Replaces DRAFT-PERLMAN-TRILL-RBRIDGE-AF * Updates RFC6325 * Normative Reference RFC6327 * Normative Reference RFC6326 * Normative Reference RFC6325 * Possible Reference RFC5741 * Normative Reference RFC1195 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference DRAFT-DUNBAR-NVO3-NVA-GAP-ANALYSIS * Informative Reference DRAFT-EASTLAKE-TRILL-MULTI-TOPOLOGY * Informative Reference DRAFT-EASTLAKE-TRILL-RFC6327BIS * Informative Reference DRAFT-HAO-TRILL-ANALYSIS-ACTIVE-ACTIVE * Updates RFC7180 * Possible Reference DRAFT-ZHANG-TRILL-VLAN-ASSIGN * Normative Reference DRAFT-PERLMAN-TRILL-RBRIDGE-MULTILEVEL * Normative Reference DRAFT-EASTLAKE-TRILL-RBRIDGE-MULTI-TOPO * Normative Reference DRAFT-EASTLAKE-TRILL-RBRIDGE-CLEAR-CORRECT * Normative Reference DRAFT-EASTLAKE-ISIS-RFC6326BIS * Informative Reference RFC7172 * Possible Reference DRAFT-TISSA-TRILL-CMT * Normative Reference RFC7180 * Normative Reference DRAFT-YIZHOU-TRILL-TREE-SELECTION * Normative Reference DRAFT-IETF-TRILL-CMT * Normative Reference DRAFT-KVK-TRILL-FAIR-SHARE-AF-LOAD-SHARE * Normative Reference DRAFT-YIZHOU-TRILL-TC-AWARENESS * Informative Reference RFC7067 * Normative Reference RFC7176 * Informative Reference RFC7177 * Normative Reference DRAFT-HAO-TRILL-RB-SYN * Normative Reference DRAFT-YIZHOU-TRILL-ACTIVE-ACTIVE-CONNECTION-PROB * Normative Reference DRAFT-ZHANG-TRILL-ACTIVE-ACTIVE-CP-REQ * Normative Reference RFC7379 * Normative Reference DRAFT-IETF-TRILL-AA-MULTI-ATTACH * Normative Reference DRAFT-IETF-TRILL-PSEUDONODE-NICKNAME * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Normative Reference DRAFT-YIZHOU-TRILL-ARP-OPTIMIZATION * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS * Normative Reference DRAFT-IETF-TRILL-DIRECTORY-ASSISTED-ENCAP * Informative Reference DRAFT-EASTLAKE-TRILL-RFC6439BIS RFC6850: Definitions of Managed Objects for Routing Bridges (RBridges) (59 pages) * Replaces DRAFT-ZEBROSE-TRILL-RBRIDGE-MIB * Informative Reference RFC5556 * Normative Reference RFC5591 * Normative Reference RFC4363 * Normative Reference RFC5592 * Normative Reference RFC3826 * Normative Reference BCP14 * Normative Reference RFC2580 * Normative Reference RFC6353 * Informative Reference RFC4663 * Possible Reference RFC5741 * Normative Reference STD58 * Normative Reference RFC4188 * Normative Reference RFC4001 * Informative Reference RFC3410 * Normative Reference RFC3414 * Normative Reference RFC2579 * Normative Reference RFC2863 * Normative Reference RFC2119 * Normative Reference STD62 * Normative Reference RFC4444 * Normative Reference RFC2578 * Normative Reference RFC6325 RFC6905: Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL) (13 pages) * Replaces DRAFT-TISSA-TRILL-OAM-REQ * Informative Reference RFC2680 * Informative Reference RFC2681 * Informative Reference RFC5860 * Informative Reference RFC2679 * Informative Reference RFC6325 * Informative Reference RFC4377 * Possible Reference RFC5741 * Informative Reference RFC5960 * Normative Reference BCP14 * Normative Reference RFC6291 * Normative Reference BCP161 * Normative Reference RFC2119 * Normative Reference RFC7174 * Informative Reference RFC7276 * Informative Reference DRAFT-TISSA-TRILL-OAM-FM * Informative Reference DRAFT-MIZRAHI-TRILL-LOSS-DELAY * Informative Reference RFC7455 * Informative Reference RFC7456 * Informative Reference DRAFT-IETF-TRILL-OAM-MIB RFC7067: Directory Assistance Problem and High-Level Design Proposal (15 pages) * Replaces DRAFT-DUNBAR-TRILL-DIRECTORY-ASSISTED-EDGE * Informative Reference STD37 * Informative Reference RFC4861 * Informative Reference RFC6439 * Informative Reference RFC826 * Possible Reference RFC5741 * Informative Reference RFC3971 * Informative Reference RFC6325 * Informative Reference RFC6326 * Informative Reference DRAFT-IETF-TRILL-IA-APPSUBTLV * Normative Reference DRAFT-PERLMAN-TRILL-SMART-ENDNODES * Informative Reference DRAFT-IETF-TRILL-DIRECTORY-ASSIST-MECHANISMS * Informative Reference DRAFT-YIZHOU-TRILL-ARP-OPTIMIZATION * Normative Reference DRAFT-IETF-TRILL-SMART-ENDNODES * Informative Reference DRAFT-IETF-TRILL-DIRECTORY-ASSISTED-ENCAP RFC7172: Transparent Interconnection of Lots of Links (TRILL): Fine-Grained Labeling (27 pages) * Replaces DRAFT-EASTLAKE-TRILL-RBRIDGE-FINE-LABELING * Updates RFC6325 * Normative Reference RFC2119 * Informative Reference RFC6439 * Normative Reference BCP14 * Informative Reference RFC6165 * Normative Reference RFC7176 * Possible Reference RFC5741 * Normative Reference RFC5305 * Informative Reference RFC7178 * Normative Reference RFC7180 * Normative Reference RFC6325 * Normative Reference RFC7177 * Informative Reference RFC7174 * Informative Reference DRAFT-IETF-TRILL-RESILIENT-TREES * Normative Reference DRAFT-HAO-TRILL-IRB * Normative Reference DRAFT-IETF-TRILL-IA-APPSUBTLV * Normative Reference DRAFT-IETF-TRILL-CHANNEL-TUNNEL * Informative Reference DRAFT-PERLMAN-TRILL-RBRIDGE-MULTILEVEL * Normative Reference DRAFT-YIZHOU-TRILL-TREE-SELECTION * Normative Reference RFC7357 * Normative Reference RFC7176 * Informative Reference RFC7177 * Normative Reference RFC7174 * Normative Reference DRAFT-PERLMAN-TRILL-SMART-ENDNODES * Normative Reference RFC7455 * Normative Reference RFC7173 * Normative Reference DRAFT-IETF-TRILL-OAM-MIB * Normative Reference DRAFT-IETF-TRILL-DIRECTORY-ASSIST-MECHANISMS * Normative Reference RFC7379 * Informative Reference DRAFT-IETF-TRILL-OVER-IP * Normative Reference DRAFT-IETF-TRILL-AA-MULTI-ATTACH * Normative Reference DRAFT-IETF-TRILL-PSEUDONODE-NICKNAME * Normative Reference RFC7456 * Normative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Normative Reference DRAFT-YIZHOU-TRILL-ARP-OPTIMIZATION * Normative Reference DRAFT-IETF-TRILL-RFC7180BIS * Normative Reference DRAFT-IETF-TRILL-SMART-ENDNODES * Normative Reference DRAFT-ZHANG-TRILL-P2MP-BFD * Normative Reference DRAFT-IETF-TRILL-IRB * Normative Reference DRAFT-EASTLAKE-TRILL-RFC6439BIS RFC7173: Transparent Interconnection of Lots of Links (TRILL) Transport Using Pseudowires (11 pages) * Replaces DRAFT-YONG-TRILL-O-PW * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference RFC4618 * Informative Reference RFC4448 * Normative Reference RFC4447 * Informative Reference RFC3985 * Normative Reference RFC6361 * Possible Reference RFC5741 * Informative Reference RFC7177 * Normative Reference RFC7180 * Normative Reference RFC5462 * Normative Reference RFC6325 * Informative Reference RFC4023 * Normative Reference RFC7172 * Normative Reference RFC1661 * Normative Reference STD51 * Informative Reference RFC7175 * Informative Reference RFC7177 * Informative Reference DRAFT-IETF-TRILL-OVER-IP * Normative Reference DRAFT-EASTLAKE-TRILL-LINK-SECURITY RFC7174: Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) Framework (33 pages) * Replaces DRAFT-SALAM-TRILL-OAM-FRAMEWORK * Informative Reference RFC4379 * Normative Reference RFC6905 * Informative Reference RFC7087 * Informative Reference RFC6241 * Normative Reference RFC6325 * Normative Reference RFC7172 * Normative Reference RFC7177 * Informative Reference RFC7175 * Informative Reference RFC3410 * Informative Reference RFC5424 * Informative Reference RFC6361 * Normative Reference RFC2579 * Normative Reference RFC6291 * Possible Reference RFC5741 * Normative Reference STD58 * Informative Reference RFC5860 * Informative Reference RFC1661 * Informative Reference STD51 * Informative Reference RFC5880 * Informative Reference RFC6371 * Normative Reference RFC2544 * Normative Reference BCP161 * Informative Reference RFC7172 * Informative Reference DRAFT-IETF-TRILL-OAM-MIB * Informative Reference DRAFT-TISSA-NETMOD-OAM * Informative Reference RFC7456 * Informative Reference RFC7455 * Informative Reference DRAFT-TISSA-LIME-YANG-OAM-MODEL * Informative Reference DRAFT-DEEPAK-TRILL-YANG-PM * Informative Reference DRAFT-IETF-TRILL-YANG-PM * Informative Reference DRAFT-IETF-TRILL-PSEUDONODE-NICKNAME * Normative Reference DRAFT-RTG-DT-ENCAP RFC7175: Transparent Interconnection of Lots of Links (TRILL): Bidirectional Forwarding Detection (BFD) Support (12 pages) * Replaces DRAFT-MANRAL-TRILL-BFD-ENCAPS * Normative Reference RFC2119 * Informative Reference RFC6361 * Informative Reference RFC6291 * Informative Reference RFC5082 * Informative Reference RFC6234 * Normative Reference BCP14 * Normative Reference RFC5880 * Normative Reference RFC5881 * Possible Reference RFC5741 * Normative Reference RFC6213 * Normative Reference RFC7178 * Normative Reference RFC6325 * Informative Reference RFC7173 * Normative Reference RFC7177 * Informative Reference BCP161 * Normative Reference DRAFT-IETF-TRILL-RESILIENT-TREES * Informative Reference DRAFT-IETF-TRILL-CHANNEL-TUNNEL * Informative Reference RFC7176 * Normative Reference RFC7177 * Informative Reference RFC7174 * Informative Reference RFC7379 * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS * Normative Reference DRAFT-ZHANG-TRILL-P2MP-BFD RFC7177: Transparent Interconnection of Lots of Links (TRILL): Adjacency (35 pages) * Replaces DRAFT-EASTLAKE-TRILL-RFC6327BIS * Updates RFC6325 * Obsoletes RFC6327 * Normative Reference RFC2119 * Normative Reference RFC6328 * Informative Reference RFC6439 * Normative Reference BCP14 * Normative Reference RFC1195 * Normative Reference RFC7176 * Informative Reference RFC6361 * Possible Reference RFC5741 * Normative Reference RFC6213 * Normative Reference RFC7178 * Normative Reference RFC7180 * Normative Reference RFC5120 * Normative Reference RFC6325 * Informative Reference RFC6327 * Informative Reference RFC7172 * Informative Reference RFC7173 * Normative Reference BCP164 * Informative Reference RFC3719 * Normative Reference RFC7175 * Normative Reference RFC7175 * Normative Reference RFC7178 * Informative Reference DRAFT-PERLMAN-TRILL-RBRIDGE-MULTILEVEL * Normative Reference RFC7172 * Normative Reference DRAFT-IETF-TRILL-CMT * Normative Reference RFC7357 * Normative Reference RFC7176 * Normative Reference RFC7174 * Informative Reference RFC7173 * Normative Reference DRAFT-IETF-TRILL-OVER-IP * Normative Reference DRAFT-ZHANG-TRILL-MTU-NEGOTIATION * Normative Reference DRAFT-IETF-TRILL-AA-MULTI-ATTACH * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS * Normative Reference DRAFT-ZHANG-TRILL-P2MP-BFD * Normative Reference DRAFT-EASTLAKE-TRILL-RFC6439BIS * Normative Reference DRAFT-IETF-TRILL-MTU-NEGOTIATION * Normative Reference DRAFT-EASTLAKE-TRILL-LINK-SECURITY RFC7178: Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Support (21 pages) * Replaces DRAFT-EASTLAKE-TRILL-RBRIDGE-BFD * Replaces DRAFT-EASTLAKE-TRILL-RBRIDGE-CHANNEL * Normative Reference RFC7120 * Normative Reference RFC2119 * Normative Reference BCP26 * Informative Reference RFC5082 * Normative Reference BCP14 * Normative Reference RFC1195 * Informative Reference RFC5880 * Possible Reference RFC5741 * Informative Reference RFC5586 * Normative Reference BCP100 * Normative Reference RFC7179 * Normative Reference RFC7176 * Normative Reference RFC6325 * Informative Reference RFC7180 * Informative Reference RFC5882 * Normative Reference RFC5348 * Normative Reference RFC7177 * Normative Reference RFC5226 * Informative Reference DRAFT-IETF-TRILL-IA-APPSUBTLV * Informative Reference DRAFT-HAO-TRILL-ANALYSIS-ACTIVE-ACTIVE * Normative Reference RFC7175 * Informative Reference DRAFT-IETF-TRILL-CHANNEL-TUNNEL * Normative Reference RFC7179 * Informative Reference RFC7172 * Informative Reference RFC7180 * Normative Reference RFC7176 * Normative Reference RFC7177 * Informative Reference RFC7455 * Normative Reference DRAFT-IETF-TRILL-DIRECTORY-ASSIST-MECHANISMS * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS * Normative Reference DRAFT-ZHANG-TRILL-P2MP-BFD RFC7179: Transparent Interconnection of Lots of Links (TRILL): Header Extension (12 pages) * Updates RFC6325 * Normative Reference BCP26 * Normative Reference RFC2119 * Normative Reference BCP14 * Normative Reference RFC7176 * Possible Reference RFC5741 * Normative Reference RFC7178 * Normative Reference RFC6325 * Normative Reference RFC5226 * Normative Reference RFC7178 * Normative Reference RFC7176 * Informative Reference RFC7455 * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS RFC7180: Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates (24 pages) * Replaces DRAFT-EASTLAKE-TRILL-RBRIDGE-CLEAR-CORRECT * Updates RFC6439 * Updates RFC6327 * Updates RFC6325 * Normative Reference RFC2119 * Informative Reference RFC7042 * Normative Reference RFC6439 * Normative Reference BCP14 * Normative Reference RFC1195 * Normative Reference RFC7176 * Possible Reference RFC5741 * Informative Reference RFC7178 * Normative Reference RFC5306 * Normative Reference RFC5305 * Informative Reference RFC6325 * Normative Reference RFC6327 * Informative Reference BCP141 * Normative Reference DRAFT-IETF-TRILL-RESILIENT-TREES * Informative Reference RFC7178 * Normative Reference RFC7172 * Normative Reference DRAFT-IETF-TRILL-CMT * Normative Reference RFC7357 * Normative Reference RFC7176 * Normative Reference RFC7177 * Normative Reference DRAFT-YANG-TRILL-PARENT-SELETION * Normative Reference RFC7173 * Normative Reference DRAFT-IETF-TRILL-DIRECTORY-ASSIST-MECHANISMS * Normative Reference DRAFT-IETF-TRILL-OVER-IP * Normative Reference DRAFT-UMAIR-MULTIPLE-TRILL-CAMPUS-TO-LAN * Informative Reference RFC7455 * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS * Informative Reference DRAFT-EASTLAKE-TRILL-RFC6439BIS RFC7357: Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) Protocol (31 pages) * Replaces DRAFT-HU-TRILL-RBRIDGE-ESADI * Updates RFC6325 * Normative Reference RFC6165 * Normative Reference RFC6823 * Informative Reference RFC6822 * Informative Reference RFC6325 * Normative Reference RFC7172 * Normative Reference RFC7176 * Normative Reference RFC7177 * Normative Reference BCP26 * Normative Reference RFC2119 * Normative Reference RFC1195 * Normative Reference RFC6361 * Normative Reference RFC5310 * Possible Reference RFC5741 * Informative Reference RFC3748 * Normative Reference RFC7180 * Informative Reference RFC7356 * Normative Reference RFC4086 * Informative Reference RFC6234 * Normative Reference BCP14 * Normative Reference BCP106 * Normative Reference RFC5226 * Informative Reference DRAFT-PERLMAN-TRILL-RBRIDGE-MULTILEVEL * Normative Reference DRAFT-IETF-TRILL-IA-APPSUBTLV * Normative Reference DRAFT-IETF-TRILL-DIRECTORY-ASSIST-MECHANISMS * Normative Reference DRAFT-IETF-TRILL-AA-MULTI-ATTACH * Informative Reference DRAFT-ZHANG-TRILL-MTU-NEGOTIATION * Normative Reference DRAFT-IETF-TRILL-PSEUDONODE-NICKNAME * Normative Reference DRAFT-HAO-TRILL-IRB * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Normative Reference DRAFT-PERLMAN-TRILL-SMART-ENDNODES * Possible Reference DRAFT-YIZHOU-TRILL-ARP-OPTIMIZATION * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS * Normative Reference DRAFT-IETF-TRILL-SMART-ENDNODES * Normative Reference DRAFT-IETF-TRILL-IRB * Normative Reference DRAFT-EASTLAKE-TRILL-RFC6439BIS * Informative Reference DRAFT-IETF-TRILL-MTU-NEGOTIATION * Normative Reference DRAFT-ZHANG-TRILL-MULTILEVEL-SINGLE-NICKNAME RFC7379: Problem Statement and Goals for Active-Active Connection at the Transparent Interconnection of Lots of Links (TRILL) Edge (13 pages) * Replaces DRAFT-YIZHOU-TRILL-ACTIVE-ACTIVE-CONNECTION-PROB * Normative Reference RFC6439 * Normative Reference BCP14 * Normative Reference RFC6165 * Normative Reference RFC7176 * Possible Reference RFC5741 * Normative Reference RFC2119 * Normative Reference RFC7172 * Informative Reference RFC7175 * Normative Reference RFC6325 * Informative Reference DRAFT-IETF-TRILL-CMT * Normative Reference DRAFT-IETF-TRILL-AA-MULTI-ATTACH * Informative Reference DRAFT-IETF-TRILL-PSEUDONODE-NICKNAME * Informative Reference DRAFT-EASTLAKE-TRILL-RFC7180BIS * Informative Reference DRAFT-IETF-TRILL-IRB * Informative Reference DRAFT-EASTLAKE-TRILL-RFC6439BIS * Informative Reference DRAFT-IETF-TRILL-RFC7180BIS RFC7455: Transparent Interconnection of Lots of Links (TRILL): Fault Management (63 pages) * Replaces DRAFT-TISSA-TRILL-OAM-FM * Informative Reference RFC4379 * Normative Reference BCP26 * Normative Reference RFC2119 * Informative Reference DRAFT-DEEPAK-TRILL-OAM-MIB * Informative Reference RFC6291 * Normative Reference RFC5310 * Informative Reference RFC6905 * Normative Reference BCP14 * Informative Reference RFC7176 * Informative Reference RFC6361 * Informative Reference RFC7178 * Informative Reference RFC7179 * Normative Reference RFC7172 * Normative Reference RFC6325 * Informative Reference RFC7180 * Informative Reference RFC7174 * Informative Reference DRAFT-TISSA-TRILL-OAM-FM * Normative Reference RFC5226 * Updates RFC6325 RFC7456: Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL) (32 pages) * Replaces DRAFT-MIZRAHI-TRILL-LOSS-DELAY * Replaces DRAFT-MIZRAHI-TRILL-LOSS-DELAY * Informative Reference RFC6291 * Informative Reference RFC6905 * Normative Reference BCP14 * Informative Reference RFC6374 * Informative Reference RFC2681 * Normative Reference DRAFT-IETF-TRILL-OAM-FM * Informative Reference RFC7276 * Normative Reference RFC6325 * Informative Reference RFC2679 * Normative Reference RFC7172 * Informative Reference RFC7174 * Informative Reference RFC2680 Autonomic Networking Integrated Model and Approach (anima) ---------------------------------------------------------- Charter Last Modified: 2015-01-26 Current Status: Active Chairs: Toerless Eckert Sheng Jiang Operations and Management Area Directors: Benoit Claise Joel Jaeggli Operations and Management Area Advisor: Ted Lemon Tech Advisor: Nancy Cam-Winget Mailing Lists: General Discussion: anima@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/anima Archive: http://www.ietf.org/mail-archive/web/anima/ Description of Working Group: Autonomic networking refers to the self-managing characteristics (configuration, protection, healing, and optimization) of distributed network elements, adapting to unpredictable changes while hiding intrinsic complexity from operators and users. Autonomic Networking, which often involves closed-loop control, is applicable to the complete network (functions) lifecycle (e.g. installation, commissioning, operating, etc). An autonomic function that works in a distributed way across various network elements is a candidate for protocol design. Such functions should allow central guidance and reporting, and co-existence with non-autonomic methods of management. The general objective of this working group is to enable the progressive introduction of autonomic functions into operational networks, as well as reusable autonomic network infrastructure, in order to reduce the OpEx. This work builds on definitions and design goals, as well as a simple architecture model undertaken in the Network Management Research Group (NMRG) of the IRTF (See draft-irtf-nmrg-an-gap-analysis and its companion draft-irtf-nmrg-autonomic-network-definitions). Elements of autonomic functions already exist today. However, all such functions today have their own discovery, node identification, negotiation, transport, messaging and security mechanisms as well as non-autonomic management interfaces. There is no common infrastructure for distributed functions. This leads to inefficiencies. Additionally, management and optimisation of operational device configurations is expensive, tedious, and prone to human error. A simple example is assigning address prefixes to network segments in a large and constantly changing network. Similarly, repair or bypassing of faults requires human intervention and causes significant down time. This WG will develop a system of autonomic functions that carry out the intentions of the network operator without the need for detailed low- level management of individual devices. This will be done by providing a secure closed-loop interaction mechanism whereby network elements cooperate directly to satisfy management intent. The working group will develop a control paradigm where network processes coordinate their decisions and automatically translate them into local actions, based on various sources of information including operator-supplied configuration information or from the existing protocols, such as routing protocol, etc. While a complete solution for full autonomic networking is an ambitious goal, the initial scope of this working group's effort is much more modest: the specification of a minimum set of specific reusable infrastructure components to support autonomic interactions between devices, and to specify the application of these components to one or two elementary use cases of general value. Practically, these components should be capable of providing the following services to those distributed functions: o a common way to identify nodes o a common security model o a discovery mechanism o a negotiation mechanism to enable closed-loop interaction o a secure and logically separated communications channel o a consistent autonomic management model ANIMA and HOMENET will need to co-ordinate to ensure that the commonalities and differences in solutions are properly taken into account. Where suitable protocols, models or methods exist, they will be preferred over creating new ones. It is preferred that autonomic functions would co-exist with traditional methods of management and configuration, and the initial focus would be on self-configuration. Future work may include a more detailed systems architecture to support the development of autonomic service agents. The ANIMA working group focuses on professionally-managed networks. Like traditional network management, the topological scope of autonomic functions is expected to be limited by administrative boundaries. The goal of this working group shall be to develop one or more protocol specifications (or extensions to existing protocols) to address the following problem areas. These were selected to according to the analyzed technical gaps in draft-irtf-nmrg-an-gap-analysis: o Discovery for autonomic nodes o Negotiation for autonomic nodes Starting point: draft-carpenter-anima-gdn-protocol o Bootstrapping a trust infrastructure Starting point: draft-pritikin-anima-bootstrapping-keyinfra o Separated Autonomic Control Plane Starting point: draft-behringer-anima-autonomic-control-plane The design of these proposals should clearly target reusability. In addition, the WG will validate the application and reusability of the components to the following two use cases: o A solution for distributed IPv6 prefix management within a large-scale network. Although prefix delegation is currently supported, it relies on human action to subdivide and assign prefixes according to local requirements, and this process could become autonomic. o A solution for always-on, data plane independent connectivity between network elements (i.e., stable in the case of mis-configurations), which can be used for call home, network provisioning, or simply trouble- shooting. It is essential that these components and solutions fit together as an integrated whole. For this reason, a reference document will be developed in parallel with the individual specifications. The initial set of work items is limited to the above list to stay focused and avoid "boiling the ocean". Additional documents concerning other autonomic infrastructure components, policy intent, use cases or autonomic service agents are strongly encouraged, as individual submissions, or as submissions to the IRTF Network Network Management Research Group. Additional work items may only be added with approval from the responsible Area Director or by re-chartering. Goals and Milestones: Mar 2015 - Adoption of initial drafts on AN components: Discovery and negotiation protocol(s), Bootstrap a trust infrastructure solution, Autonomic control plane solution Jul 2015 - Adoption of reference model Jul 2015 - Adoption of the two validation drafts Apr 2016 - Submit discovery and negotiation protocol(s) to IESG (Standards Track) Apr 2016 - Submit bootstrap a trust infrastructure solution to IESG (Standards Track) Sep 2016 - Submit the two validation drafts to IESG (Informational) Sep 2016 - Submit autonomic control plane solution to IESG (Standards Track) Dec 2016 - Submit reference model to IESG (Informational) Dec 2016 - recharter to refocus scope, or close Internet-Drafts: No Requests for Comments Benchmarking Methodology (bmwg) ------------------------------- Charter Last Modified: 2013-04-25 Current Status: Active Chairs: Sarah Banks Al C. Morton Operations and Management Area Directors: Benoit Claise Joel Jaeggli Operations and Management Area Advisor: Joel Jaeggli Mailing Lists: General Discussion: bmwg@ietf.org To Subscribe: bmwg-request@ietf.org Archive: http://www.ietf.org/mail-archive/web/bmwg/ Description of Working Group: The Benchmarking Methodology Working Group (BMWG) will continue to produce a series of recommendations concerning the key performance characteristics of internetworking technologies, or benchmarks for network devices, systems, and services. Taking a view of networking divided into planes, the scope of work includes benchmarks for the management, control, and forwarding planes. Each recommendation will describe the class of equipment, system, or service being addressed; discuss the performance characteristics that are pertinent to that class; clearly identify a set of metrics that aid in the description of those characteristics; specify the methodologies required to collect said metrics; and lastly, present the requirements for the common, unambiguous reporting of benchmarking results. The set of relevant benchmarks will be developed with input from the community of users (e.g., network operators and testing organizations) and from those affected by the benchmarks when they are published (networking and test equipment manufacturers). When possible, the benchmarks and other terminologies will be developed jointly with organizations that are willing to share their expertise. Joint review requirements for a specific work area will be included in the detailed description of the task, as listed below. To better distinguish the BMWG from other measurement initiatives in the IETF, the scope of the BMWG is limited to the characterization of implementations of various internetworking technologies using controlled stimuli in a laboratory environment. Said differently, the BMWG does not attempt to produce benchmarks for live, operational networks. Moreover, the benchmarks produced by this WG shall strive to be vendor independent or otherwise have universal applicability to a given technology class. Because the demands of a particular technology may vary from deployment to deployment, a specific non-goal of the Working Group is to define acceptance criteria or performance requirements. An ongoing task is to provide a forum for development and advancement of measurements which provide insight on the capabilities and operation of implementations of inter-networking technology. Ideally, BMWG should communicate with the operations community through organizations such as NANOG, RIPE, and APRICOT. The BMWG is explicitly tasked to develop benchmarks and methodologies for the following technologies: BGP Control-plane Convergence Methodology (Terminology is complete): With relevant performance characteristics identified, BMWG will prepare a Benchmarking Methodology Document with review from the Routing Area (e.g., the IDR working group and/or the RTG-DIR). The Benchmarking Methodology will be Last-Called in all the groups that previously provided input, including another round of network operator input during the last call. SIP Networking Devices: Develop new terminology and methods to characterize the key performance aspects of network devices using SIP, including the signaling plane scale and service rates while considering load conditions on both the signaling and media planes. This work will be harmonized with related SIP performance metric definitions prepared by the PMOL working group. Traffic Management: Develop the methods to characterize the capacity of traffic management features in network devices, such as classification, policing, shaping, and active queue management. Existing terminology will be used where appropriate. Configured operation will be verified as a part of the methodology. The goal is a methodology to assess the maximum forwarding performance that a network device can sustain without dropping or impairing packets, or compromising the accuracy of multiple instances of traffic management functions. This is the benchmark for comparison between devices. Another goal is to devise methods that utilize flows with congestion-aware transport as part of the traffic load and still produce repeatable results in the isolated test environment. IPv6 Neighbor Discovery: Large address space in IPv6 subnets presents several networking challenges, as described in RFC 6583. Indexes to describe the performance of network devices, such as the number of reachable devices on a sub-network, are useful benchmarks to the operations community. The BMWG will develop the necessary terminology and methodologies to measure such benchmarks. In-Service Software Upgrade: Develop new methods and benchmarks to characterize the upgrade of network devices while in-service, considering both data and control plane operations and impacts. These devices are generally expected to maintain control plane session integrity, including routing connections. Quantification of upgrade impact will include packet loss measurement, and other forms of recovery behavior will be noted accordingly. The work will produce a definition of ISSU, which will help refine the scope. Liaisons will be established as needed. Data Center Benchmarking: This work will define additional terms, benchmarks, and methods applicable to data center performance evaluations. This includes data center specific congestion scenarios, switch buffer analysis, microburst, head of line blocking, while also using a wide mix of traffic conditions. Some aspects from BMWG's past work are not meaningful when testing switches that implement new IEEE specifications in the area of data center bridging. For example, throughput as defined in RFC 1242 cannot be measured when testing devices that implement three new IEEE specifications: priority-based flow control (802.1Qbb); priority groups (802.1Qaz); and congestion notification (802.1Qau). This work will update RFC1242, RFC2544, RFC2889 (and other key RFCs), and exchange Liaisons with relevant SDOs, especially at WG Last Call. VNF and Related Infrastructure Benchmarking: Benchmarking Methodologies have reliably characterized many physical devices. This work item extends and enhances the methods to virtual network functions (VNF) and their unique supporting infrastructure. A first deliverable from this activity will be a document that considers the new benchmarking space to ensure that common issues are recognized from the start, using background materials from industry and SDOs (e.g., IETF, ETSI NFV). Benchmarks for platform capacity and performance characteristics of virtual routers, switches, and related components will follow, including comparisons between physical and virtual network functions. In many cases, the traditional benchmarks should be applicable to VNFs, but the lab set-ups, configurations, and measurement methods will likely need to be revised or enhanced. Goals and Milestones: Jun 2014 - Basic BGP Convergence Benchmarking Methodology to IESG Review Jul 2014 - Terminology for SIP Device Benchmarking to IESG Review Jul 2014 - Methodology for SIP Device Benchmarking to IESG Review Aug 2014 - Draft on Traffic Management Benchmarking to IESG Review Dec 2014 - Draft on IPv6 Neighbor Discovery to IESG Review Mar 2015 - Draft on In-Service Software Upgrade Benchmarking to IESG Review Aug 2015 - Draft on VNF Benchmarking Considerations to IESG Review Dec 2015 - Drafts on Data Center Benchmarking to IESG Review Internet-Drafts: - Applicability Statement for RFC 2544: Use on Production Networks Considered Harmful [draft-ietf-bmwg-2544-as-08] (11 pages) - Framework for Accelerated Stress Benchmarking [draft-ietf-bmwg-acc-bench-framework-00] (7 pages) - Methodology Guidelines for Accelerated Stress Benchmarking [draft-ietf-bmwg-acc-bench-meth-09] (13 pages) - Methodology for Benchmarking Accelerated Stress with Operational EBGP Instabilities [draft-ietf-bmwg-acc-bench-meth-ebgp-00] (9 pages) - Methodology for Benchmarking Accelerated Stress with Operational Security [draft-ietf-bmwg-acc-bench-meth-opsec-00] (7 pages) - Terminology for Accelerated Stress Benchmarking [draft-ietf-bmwg-acc-bench-term-13] (27 pages) - Methodology for ATM Benchmarking [draft-ietf-bmwg-atm-method-03] (127 pages) - Terminology for ATM Benchmarking [draft-ietf-bmwg-atm-term-00] (32 pages) - Terminology for ATM ABR Benchmarking [draft-ietf-bmwg-atm-term-abr-03] (16 pages) - Benchmarking Methodology for Routers Supporting Resource Reservation [draft-ietf-bmwg-benchres-method-00] (15 pages) - Benchmarking Terminology for Resource Reservation Capable Routers [draft-ietf-bmwg-benchres-term-08] (24 pages) - Basic BGP Convergence Benchmarking Methodology for Data Plane Convergence [draft-ietf-bmwg-bgp-basic-convergence-05] (34 pages) - Benchmarking Methodology for Basic BGP Convergence [draft-ietf-bmwg-bgpbas-01] (16 pages) - Benchmarking Methodology for Content-Aware Network Devices [draft-ietf-bmwg-ca-bench-meth-04] (19 pages) - Terminology for Cell/Call Benchmarking [draft-ietf-bmwg-call-04] (29 pages) - Terminology for Benchmarking BGP Device Convergence in the Control Plane [draft-ietf-bmwg-conterm-06] (36 pages) - Methodology for Benchmarking Network-layer Traffic Control Mechanisms [draft-ietf-bmwg-dsmmeth-02] (13 pages) - Terminology for Benchmarking Network-layer Traffic Control Mechanisms [draft-ietf-bmwg-dsmterm-13] (34 pages) - Benchmarking Methodology for Ethernet Switches [draft-ietf-bmwg-ethernet-switches-01] (13 pages) - Methodology for Forwarding Information Base (FIB) based Router Performance [draft-ietf-bmwg-fib-meth-03] (13 pages) - Terminology for Forwarding Information Base (FIB) based Router Performance [draft-ietf-bmwg-fib-term-04] (15 pages) - Benchmarking Methodology for Firewall Performance [draft-ietf-bmwg-firewall-08] (34 pages) - Terminology for Frame Relay Benchmarking [draft-ietf-bmwg-fr-term-06] (24 pages) - Hash and Stuffing: Overlooked Factors in Network Device Benchmarking [draft-ietf-bmwg-hash-stuffing-08] (26 pages) - Considerations for Benchmarking Link-State IGP Data Plane Route Convergence [draft-ietf-bmwg-igp-dataplane-conv-app-17] (6 pages) - Benchmarking Methodology for Link-State IGP Data-Plane Route Convergence [draft-ietf-bmwg-igp-dataplane-conv-meth-23] (42 pages) - Terminology for Benchmarking Link-State IGP Data-Plane Route Convergence [draft-ietf-bmwg-igp-dataplane-conv-term-23] (29 pages) - IMIX Genome: Specification of Variable Packet Sizes for Additional Testing [draft-ietf-bmwg-imix-genome-05] (10 pages) - IP Flow Information Accounting and Export Benchmarking Methodology [draft-ietf-bmwg-ipflow-meth-10] (39 pages) - Connectivity [draft-ietf-bmwg-ippm-connect-00] (9 pages) - Methodology for Benchmarking IPsec Devices [draft-ietf-bmwg-ipsec-meth-05] (41 pages) - Terminology for Benchmarking IPsec Devices [draft-ietf-bmwg-ipsec-term-12] (46 pages) - IPv6 Benchmarking Methodology for Network Interconnect Devices [draft-ietf-bmwg-ipv6-meth-05] (20 pages) - ISSU Benchmarking Methodology [draft-ietf-bmwg-issu-meth-00] (17 pages) - Benchmarking Terminology for LAN Switching Devices [draft-ietf-bmwg-lanswitch-06] (25 pages) - Terminology for IP Multicast Benchmarking [draft-ietf-bmwg-mcast-08] (16 pages) - Methodology for IP Multicast Benchmarking [draft-ietf-bmwg-mcastm-14] (31 pages) - Benchmarking Methodology for Network Interconnect Devices [draft-ietf-bmwg-methodology-02] (30 pages) - MPLS Forwarding Benchmarking Methodology for IP Flows [draft-ietf-bmwg-mpls-forwarding-meth-06] (27 pages) - Benchmarking Methodology for LAN Switching Devices [draft-ietf-bmwg-mswitch-04] (35 pages) - Considerations When Using Basic OSPF Convergence Benchmarks [draft-ietf-bmwg-ospfconv-applicability-07] (11 pages) - Benchmarking Basic OSPF Single Router Control Plane Convergence [draft-ietf-bmwg-ospfconv-intraarea-10] (16 pages) - OSPF Benchmarking Terminology and Concepts [draft-ietf-bmwg-ospfconv-term-10] (9 pages) - Benchmarking Methodologies for Overall Network Performance [draft-ietf-bmwg-overallperf-00] (6 pages) - Methodology for Benchmarking MPLS Traffic Engineered (MPLS-TE) Fast Reroute Protection [draft-ietf-bmwg-protection-meth-14] (35 pages) - Benchmarking Terminology for Protection Performance [draft-ietf-bmwg-protection-term-09] (33 pages) - Device Reset Characterization [draft-ietf-bmwg-reset-06] (17 pages) - Framework for Router Benchmarking [draft-ietf-bmwg-rtr-framework-00] (8 pages) - Benchmarking Terminology for Firewall Performance [draft-ietf-bmwg-secperf-08] (26 pages) - Methodology for Benchmarking Session Initiation Protocol (SIP) Devices: Basic session setup and registration [draft-ietf-bmwg-sip-bench-meth-12] (20 pages) - Terminology for Benchmarking Session Initiation Protocol (SIP) Devices: Basic session setup and registration [draft-ietf-bmwg-sip-bench-term-12] (20 pages) - Benchmarking Terminology for Network Interconnection Devices [draft-ietf-bmwg-terms-01] (12 pages) - Traffic Management Benchmarking [draft-ietf-bmwg-traffic-management-03] (40 pages) Requests for Comments: RFC1242: Benchmarking Terminology for Network Interconnection Devices (12 pages) * Updates RFC6201 * Possible Reference DRAFT-LABARRE-INTERNETMIB-ISO * Possible Reference DRAFT-CHANG-IIMC-PROXY * Possible Reference RFC1944 * Reference RFC2285 * Possible Reference DRAFT-IETF-BMWG-CALL * Reference RFC2432 * Reference RFC2647 * Reference RFC2889 * Possible Reference RFC3133 * Normative Reference RFC3918 * Possible Reference RFC2761 * Possible Reference RFC3134 * Reference RFC3222 * Possible Reference DRAFT-IETF-BMWG-RTR-FRAMEWORK * Reference DRAFT-FEHER-BENCHRESRES * Reference DRAFT-KHURANA-BMWG-DIFFSERVM * Normative Reference RFC3511 * Reference DRAFT-FEHER-BMWG-BENCHRES-METHOD * Reference DRAFT-FEHER-BMWG-BENCHRES-TERM * Reference DRAFT-BERKOWITZ-BGPCON * Reference DRAFT-WLAI-TEWG-MEASURE * Normative Reference RFC4689 * Reference DRAFT-AMBROSE-ROUTING-PROTOCOL-TERM * Normative Reference RFC4883 * Normative Reference DRAFT-IETF-BMWG-FIB-METH * Reference DRAFT-PORETSKY-ROUTERSALT-TERM * Reference DRAFT-KIMURA-PROTECTION-TERM * Possible Reference DRAFT-PORETSKY-IGP-CONVERGENCE-TERM * Possible Reference DRAFT-PORETSKY-IGP-CONVERGENCE-METH * Possible Reference DRAFT-PORETSKY-IGP-CONVERGENCE-APP * Normative Reference DRAFT-IETF-BMWG-IPSEC-TERM * Normative Reference RFC6413 * Normative Reference RFC6412 * Normative Reference DRAFT-IETF-BMWG-ACC-BENCH-TERM * Possible Reference DRAFT-PORETSKY-MPLS-PROTECTION-METH * Possible Reference DRAFT-IETF-BMWG-ACC-BENCH-FRAMEWORK * Normative Reference DRAFT-IETF-BMWG-ACC-BENCH-METH * Normative Reference DRAFT-ALEXANDER-WLAN-METH * Normative Reference DRAFT-PORETSKY-PROTECTION-TERM * Normative Reference DRAFT-IETF-BMWG-ACC-BENCH-METH-EBGP * Normative Reference DRAFT-IETF-BMWG-ACC-BENCH-METH-OPSEC * Normative Reference DRAFT-FLYNN-RTGWG-LCF * Normative Reference DRAFT-IETF-BMWG-IPSEC-METH * Possible Reference DRAFT-VAPIWALA-BMWG-FRR-FAILOVER-METH * Informative Reference DRAFT-POPOVICIU-BMWG-IPV6BENCHMARKING * Normative Reference DRAFT-IETF-BMWG-DSMMETH * Informative Reference DRAFT-AKHTER-BMWG-MPLS-METH * Informative Reference DRAFT-PORETSKY-SIP-BENCH-TERM * Possible Reference DRAFT-PAPNEJA-MPLS-PROTECTION-METH-MERGE * Possible Reference DRAFT-SDRY-BMWG-MVPNSCALE * Normative Reference RFC6414 * Normative Reference DRAFT-PORETSKY-BMWG-SIP-BENCH-METH * Normative Reference RFC6894 * Informative Reference RFC5180 * Possible Reference DRAFT-KARTHIK-BMWG-LDP-CONVERGENCE-METH * Possible Reference DRAFT-SALAHUDDIN-BMWG-BFD-MOTIVATION * Possible Reference DRAFT-VAPIWALA-BMWG-RSVPTE-CONVERGENCE-MOTIVATION * Normative Reference DRAFT-ALEXANDER-BMWG-WLAN-SWITCH-TERM * Normative Reference DRAFT-ALEXANDER-BMWG-WLAN-SWITCH-METH * Informative Reference DRAFT-JANOVAK-BMWG-IPFLOW-METH * Informative Reference DRAFT-NOVAK-BMWG-IPFLOW-METH * Informative Reference RFC6645 * Normative Reference RFC5695 * Informative Reference DRAFT-IETF-BMWG-SIP-BENCH-TERM * Normative Reference DRAFT-HAMILTON-BMWG-CA-BENCH-METH * Normative Reference DRAFT-IETF-BMWG-CA-BENCH-METH * Normative Reference DRAFT-PLAYER-DCB-BENCHMARKING * Informative Reference DRAFT-XHK-MPLS-TP-THROUGHPUT * Normative Reference RFC6201 * Informative Reference DRAFT-XIAO-MPLS-TP-THROUGHPUT-ESTIMATION * Informative Reference DRAFT-PAPNEJA-BGP-BASIC-DP-CONVERGENCE * Possible Reference DRAFT-BAILLARGEON-IPPM-TWAMP-VALUE-ADDED-OCTETS * Normative Reference DRAFT-CHAIRS-BMWG-2544-AS * Informative Reference RFC6815 * Normative Reference DRAFT-HAMILTON-BMWG-CA-BENCH-TERM * Normative Reference DRAFT-GREEN-BMWG-SECEFF-BENCH-METH * Possible Reference RFC2544 * Normative Reference DRAFT-DCBENCH-DEF * Normative Reference DRAFT-BMWG-DCBENCH-METHODOLOGY * Informative Reference DRAFT-MORTON-IPPM-REGISTRY-PDV * Informative Reference DRAFT-MORNULO-IPPM-REGISTRY-COLUMNS * Informative Reference DRAFT-MORNULO-IPPM-REGISTRY * Informative Reference DRAFT-MORTON-BMWG-VIRTUAL-NET * Informative Reference DRAFT-IETF-IPPM-REGISTRY-ACTIVE * Normative Reference DRAFT-IETF-BMWG-TRAFFIC-MANAGEMENT * Informative Reference DRAFT-MORNULEY-IPPM-INITIAL-REGISTRY * Informative Reference DRAFT-IETF-BMWG-BGP-BASIC-CONVERGENCE * Informative Reference DRAFT-GEORGESCU-BMWG-IPV6-TRAN-TECH-BENCHMARKING RFC1944: Benchmarking Methodology for Network Interconnect Devices (30 pages) * Possible Reference RFC1242 * Obsoletes RFC2544 * Reference RFC2285 * Possible Reference DRAFT-IETF-BMWG-CALL * Reference RFC2432 * Reference DRAFT-ZHU-PUBLIC-CIRCUIT-SWITCH * Possible Reference RFC3133 * Possible Reference RFC2544 * Possible Reference RFC2599 RFC2285: Benchmarking Terminology for LAN Switching Devices (25 pages) * Reference RFC1242 * Possible Reference RFC2119 * Reference RFC1944 * Possible Reference DRAFT-IETF-BMWG-CALL * Reference RFC2432 * Reference RFC2647 * Reference RFC2889 * Possible Reference RFC3133 * Normative Reference RFC3918 * Possible Reference RFC2761 * Possible Reference RFC3134 * Reference DRAFT-FEHER-BENCHRESRES * Normative Reference RFC3511 * Reference DRAFT-FEHER-BMWG-BENCHRES-METHOD * Reference DRAFT-FEHER-BMWG-BENCHRES-TERM * Normative Reference RFC4689 * Possible Reference DRAFT-AMBROSE-ROUTING-PROTOCOL-TERM * Normative Reference RFC4883 * Reference DRAFT-PORETSKY-ROUTERSALT-TERM * Reference DRAFT-KIMURA-PROTECTION-TERM * Normative Reference DRAFT-IETF-BMWG-IPSEC-TERM * Normative Reference RFC6413 * Normative Reference RFC6412 * Normative Reference DRAFT-IETF-BMWG-ACC-BENCH-TERM * Possible Reference DRAFT-IETF-BMWG-ACC-BENCH-FRAMEWORK * Normative Reference DRAFT-IETF-BMWG-ACC-BENCH-METH * Informative Reference DRAFT-ALEXANDER-WLAN-METH * Normative Reference DRAFT-PORETSKY-PROTECTION-TERM * Normative Reference DRAFT-IETF-BMWG-ACC-BENCH-METH-EBGP * Normative Reference DRAFT-IETF-BMWG-ACC-BENCH-METH-OPSEC * Normative Reference DRAFT-IETF-BMWG-IPSEC-METH * Normative Reference DRAFT-IETF-BMWG-DSMMETH * Informative Reference DRAFT-PORETSKY-SIP-BENCH-TERM * Possible Reference DRAFT-SDRY-BMWG-MVPNSCALE * Normative Reference RFC6414 * Normative Reference DRAFT-PORETSKY-BMWG-SIP-BENCH-METH * Informative Reference RFC6894 * Normative Reference DRAFT-ALEXANDER-BMWG-WLAN-SWITCH-TERM * Informative Reference DRAFT-ALEXANDER-BMWG-WLAN-SWITCH-METH * Informative Reference DRAFT-JANOVAK-BMWG-IPFLOW-METH * Informative Reference DRAFT-NOVAK-BMWG-IPFLOW-METH * Informative Reference RFC6645 * Informative Reference DRAFT-IETF-BMWG-SIP-BENCH-TERM * Normative Reference DRAFT-PLAYER-DCB-BENCHMARKING * Informative Reference DRAFT-PAPNEJA-BGP-BASIC-DP-CONVERGENCE * Normative Reference DRAFT-MBELSHE-HTTPBIS-SPDY * Possible Reference DRAFT-CONSTANTINE-BMWG-TRAFFIC-MANAGEMENT * Informative Reference DRAFT-IETF-BMWG-BGP-BASIC-CONVERGENCE RFC2432: Terminology for IP Multicast Benchmarking (16 pages) * Reference RFC1242 * Reference RFC1944 * Reference RFC2285 * Normative Reference RFC3918 * Informative Reference RFC4834 * Normative Reference DRAFT-FLYNN-RTGWG-LCF * Normative Reference DRAFT-IETF-BMWG-IPSEC-METH * Possible Reference DRAFT-SDRY-BMWG-MVPNSCALE RFC2647: Benchmarking Terminology for Firewall Performance (26 pages) * Reference RFC1242 * Possible Reference RFC1918 * Reference RFC2544 * Reference BCP5 * Reference RFC2285 * Normative Reference RFC3511 * Informative Reference RFC4487 * Possible Reference DRAFT-IETF-OPSEC-EFFORTS * Normative Reference DRAFT-HAMILTON-BMWG-CA-BENCH-METH * Normative Reference DRAFT-IETF-BMWG-CA-BENCH-METH * Informative Reference RFC6272 * Informative Reference DRAFT-CUI-MEXT-FIREWALL-TRAVERSING * Normative Reference DRAFT-HAMILTON-BMWG-CA-BENCH-TERM * Normative Reference DRAFT-GREEN-BMWG-SECEFF-BENCH-METH * Informative Reference DRAFT-GONT-OPSEC-IPV6-FIREWALL-REQS * Informative Reference DRAFT-IETF-AQM-EVAL-GUIDELINES * Informative Reference DRAFT-GEORGESCU-BMWG-IPV6-TRAN-TECH-BENCHMARKING RFC2761: Terminology for ATM Benchmarking (32 pages) * Possible Reference RFC1242 * Possible Reference RFC2544 * Possible Reference RFC791 * Possible Reference BCP11 * Possible Reference RFC2285 * Possible Reference RFC2331 * Possible Reference RFC2119 * Possible Reference RFC3133 * Reference RFC3116 * Possible Reference RFC3134 * Possible Reference DRAFT-IETF-BMWG-RTR-FRAMEWORK * Normative Reference DRAFT-KAPLAN-ENUM-SIP-ROUTING RFC2889: Benchmarking Methodology for LAN Switching Devices (35 pages) * Reference RFC2285 * Reference RFC2544 * Reference RFC1242 * Possible Reference RFC2119 * Normative Reference RFC3511 * Informative Reference RFC4689 * Normative Reference DRAFT-NEWMAN-HASH-STUFFING * Normative Reference RFC4814 * Normative Reference DRAFT-ALEXANDER-WLAN-METH * Informative Reference DRAFT-WELCH-STREAMING-TEST * Normative Reference DRAFT-ALEXANDER-BMWG-WLAN-SWITCH-METH * Normative Reference DRAFT-PLAYER-DCB-BENCHMARKING * Informative Reference DRAFT-DCBENCH-DEF * Informative Reference DRAFT-BMWG-DCBENCH-METHODOLOGY RFC3116: Methodology for ATM Benchmarking (127 pages) * Possible Reference BCP11 * Reference RFC2761 * Reference RFC2544 * Reference RFC2225 RFC3133: Terminology for Frame Relay Benchmarking (24 pages) * Reference RFC2954 * Possible Reference RFC2761 * Possible Reference RFC1242 * Possible Reference BCP11 * Possible Reference RFC2285 * Possible Reference RFC1944 * Informative Reference DRAFT-WHITTLE-IVIP-FPR RFC3134: Terminology for ATM ABR Benchmarking (16 pages) * Possible Reference RFC2544 * Possible Reference RFC2285 * Possible Reference RFC2761 * Possible Reference RFC1242 * Possible Reference DRAFT-IESG-INFO-EXP RFC3222: Terminology for Forwarding Information Base (FIB) based Router Performance (15 pages) * Reference BCP9 * Reference RFC1242 * Reference RFC1812 * Reference RFC2544 * Reference RFC2026 * Reference DRAFT-IETF-BMWG-BGPBAS * Normative Reference DRAFT-IETF-BMWG-FIB-METH * Informative Reference RFC4061 * Informative Reference RFC4063 RFC3511: Benchmarking Methodology for Firewall Performance (34 pages) * Possible Reference RFC1858 * Normative Reference RFC2647 * Informative Reference RFC815 * Normative Reference RFC2889 * Normative Reference RFC2544 * Normative Reference RFC1242 * Informative Reference RFC2616 * Normative Reference RFC2285 * Informative Reference STD7 * Normative Reference DRAFT-HAMILTON-BMWG-CA-BENCH-METH * Normative Reference DRAFT-IETF-BMWG-CA-BENCH-METH * Informative Reference RFC6272 * Normative Reference DRAFT-HAMILTON-BMWG-CA-BENCH-TERM * Informative Reference DRAFT-GREEN-BMWG-SECEFF-BENCH-METH * Informative Reference DRAFT-GONT-OPSEC-IPV6-FIREWALL-REQS * Informative Reference DRAFT-GEORGESCU-BMWG-IPV6-TRAN-TECH-BENCHMARKING RFC3918: Methodology for IP Multicast Benchmarking (31 pages) * Informative Reference RFC3376 * Normative Reference RFC1242 * Normative Reference RFC2285 * Normative Reference RFC2544 * Informative Reference RFC1112 * Informative Reference RFC2236 * Normative Reference RFC2432 * Normative Reference RFC2365 * Possible Reference BCP14 * Informative Reference STD5 * Informative Reference BCP78 * Normative Reference BCP23 * Normative Reference RFC2119 * Informative Reference RFC3415 * Normative Reference DRAFT-ALEXANDER-BMWG-WLAN-SWITCH-METH RFC4061: Benchmarking Basic OSPF Single Router Control Plane Convergence (16 pages) * Informative Reference BCP78 * Normative Reference STD54 * Informative Reference RFC2544 * Normative Reference RFC4062 * Normative Reference RFC4063 * Normative Reference BCP14 * Informative Reference RFC3222 * Normative Reference RFC2119 * Normative Reference RFC4062 * Normative Reference RFC4063 * Normative Reference RFC6413 * Possible Reference DRAFT-ZHANGM-CCAMP-METRIC RFC4062: OSPF Benchmarking Terminology and Concepts (9 pages) * Normative Reference BCP14 * Normative Reference STD54 * Informative Reference BCP78 * Normative Reference RFC2119 * Normative Reference RFC4061 * Normative Reference RFC4061 * Normative Reference RFC4063 * Normative Reference RFC6413 RFC4063: Considerations When Using Basic OSPF Convergence Benchmarks (11 pages) * Informative Reference BCP78 * Normative Reference STD54 * Informative Reference RFC2544 * Normative Reference RFC4062 * Normative Reference RFC4061 * Informative Reference RFC3222 * Normative Reference RFC4061 * Normative Reference RFC6413 RFC4098: Terminology for Benchmarking BGP Device Convergence in the Control Plane (36 pages) * Normative Reference RFC2280 * Informative Reference BCP78 * Informative Reference RFC2858 * Normative Reference RFC1812 * Normative Reference RFC2547 * Informative Reference RFC2545 * Informative Reference RFC3345 * Normative Reference RFC2622 * Normative Reference RFC2385 * Informative Reference RFC3654 * Normative Reference RFC1771 * Informative Reference RFC2918 * Normative Reference RFC2439 * Informative Reference RFC4984 * Informative Reference DRAFT-PAPNEJA-BGP-BASIC-DP-CONVERGENCE * Normative Reference DRAFT-HARES-ARMD-NANOG52 * Normative Reference DRAFT-IETF-BMWG-BGP-BASIC-CONVERGENCE RFC4689: Terminology for Benchmarking Network-layer Traffic Control Mechanisms (34 pages) * Informative Reference RFC2544 * Informative Reference RFC3246 * Normative Reference RFC2474 * Informative Reference RFC2889 * Informative Reference RFC2679 * Informative Reference STD64 * Informative Reference RFC2475 * Normative Reference RFC1242 * Normative Reference RFC2309 * Informative Reference RFC3393 * Informative Reference RFC3168 * Informative Reference RFC3550 * Normative Reference RFC2285 * Informative Reference RFC1254 * Informative Reference RFC2680 * Normative Reference BCP14 * Normative Reference RFC1224 * Informative Reference BCP78 * Possible Reference RFC2119 * Informative Reference RFC896 * Normative Reference RFC6413 * Normative Reference RFC6412 * Normative Reference RFC6414 * Informative Reference RFC6894 * Normative Reference DRAFT-PLAYER-DCB-BENCHMARKING * Informative Reference RFC7021 * Possible Reference DRAFT-CONSTANTINE-BMWG-TRAFFIC-MANAGEMENT * Normative Reference DRAFT-MORTON-BMWG-VIRTUAL-NET * Normative Reference DRAFT-IETF-BMWG-TRAFFIC-MANAGEMENT RFC4814: Hash and Stuffing: Overlooked Factors in Network Device Benchmarking (26 pages) * Normative Reference RFC1662 * Normative Reference RFC1661 * Normative Reference BCP78 * Normative Reference RFC2889 * Normative Reference RFC2544 * Normative Reference RFC2615 * Normative Reference RFC2661 * Normative Reference BCP14 * Normative Reference RFC2119 * Normative Reference RFC3032 * Normative Reference RFC6413 * Informative Reference RFC5180 * Normative Reference DRAFT-ALEXANDER-BMWG-WLAN-SWITCH-METH * Normative Reference DRAFT-MORTON-IPPM-ADVANCE-METRICS * Normative Reference DRAFT-MORTON-IPPM-TESTPLAN-RFC2679 * Normative Reference DRAFT-MORTON-IPPM-TESTPLAN-RFC2680 * Informative Reference DRAFT-KRISHNAN-LARGE-FLOW-LOAD-BALANCING RFC4883: Benchmarking Terminology for Resource Reservation Capable Routers (24 pages) * Informative Reference RFC4080 * Informative Reference BCP78 * Informative Reference RFC4094 * Informative Reference RFC2205 * Normative Reference RFC1242 * Informative Reference RFC1819 * Normative Reference RFC2285 * Normative Reference BCP14 * Informative Reference RFC3175 * Possible Reference RFC2119 * Informative Reference RFC1633 RFC5180: IPv6 Benchmarking Methodology for Network Interconnect Devices (20 pages) * Informative Reference STD51 * Possible Reference RFC4773 * Informative Reference RFC2544 * Informative Reference RFC4814 * Normative Reference RFC4193 * Informative Reference RFC3849 * Informative Reference RFC1242 * Normative Reference RFC2460 * Normative Reference RFC2615 * Normative Reference RFC4303 * Informative Reference BCP78 * Normative Reference BCP14 * Normative Reference RFC4861 * Informative Reference RFC3330 * Possible Reference RFC2119 * Normative Reference DRAFT-IETF-BMWG-IPSEC-METH * Normative Reference DRAFT-CERVENY-BMWG-IPV6-ND * Informative Reference DRAFT-NOVAK-BMWG-IPFLOW-METH * Informative Reference RFC6645 * Informative Reference RFC5695 * Normative Reference DRAFT-HAMILTON-BMWG-CA-BENCH-METH * Normative Reference DRAFT-IETF-BMWG-CA-BENCH-METH * Normative Reference DRAFT-PLAYER-DCB-BENCHMARKING * Informative Reference DRAFT-ASATI-BMWG-RESET * Informative Reference RFC6201 * Normative Reference DRAFT-MANDERSON-IANA-OBJECTS * Normative Reference DRAFT-CHAIRS-BMWG-2544-AS * Normative Reference RFC6815 * Informative Reference RFC6491 * Normative Reference DRAFT-HAMILTON-BMWG-CA-BENCH-TERM * Informative Reference RFC6890 * Informative Reference DRAFT-BOUCADAIR-CHAINING-DESIGN-ANALYSIS * Informative Reference DRAFT-BOUCADAIR-SFC-DESIGN-ANALYSIS * Informative Reference DRAFT-GONT-OPSEC-IPV6-FIREWALL-REQS * Informative Reference DRAFT-GEORGESCU-BMWG-IPV6-TRAN-TECH-BENCHMARKING RFC5695: MPLS Forwarding Benchmarking Methodology for IP Flows (27 pages) * Informative Reference RFC3209 * Normative Reference RFC1242 * Informative Reference RFC5462 * Normative Reference RFC5036 * Informative Reference RFC3443 * Normative Reference RFC2544 * Normative Reference RFC3107 * Informative Reference RFC4364 * Informative Reference RFC4928 * Normative Reference RFC2119 * Informative Reference BCP128 * Informative Reference RFC2328 * Informative Reference RFC4271 * Normative Reference BCP14 * Informative Reference RFC5180 * Informative Reference RFC4090 * Informative Reference RFC4664 * Normative Reference RFC3031 * Normative Reference RFC3032 * Normative Reference RFC6894 * Informative Reference RFC7325 * Informative Reference RFC6645 * Informative Reference DRAFT-ASATI-BMWG-RESET * Informative Reference RFC6201 * Normative Reference DRAFT-ASATI-DHC-RELAY-AGENT-CONFIG * Informative Reference DRAFT-VILLAMIZAR-MPLS-FORWARDING RFC6201: Device Reset Characterization (17 pages) * Replaces DRAFT-ASATI-BMWG-RESET * Updates RFC1242 * Updates RFC2544 * Informative Reference RFC5180 * Normative Reference RFC1242 * Normative Reference RFC2544 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC2119 * Informative Reference RFC5695 * Possible Reference DRAFT-VARLASHKIN-ROUTER-CONV-BENCH RFC6412: Terminology for Benchmarking Link-State IGP Data-Plane Route Convergence (29 pages) * Normative Reference RFC2544 * Normative Reference RFC5308 * Normative Reference RFC5340 * Normative Reference STD54 * Normative Reference RFC3357 * Normative Reference RFC2285 * Normative Reference RFC1242 * Normative Reference RFC3393 * Possible Reference RFC5741 * Normative Reference RFC1195 * Normative Reference BCP14 * Normative Reference RFC2991 * Normative Reference RFC6413 * Possible Reference RFC2119 * Normative Reference RFC4689 * Normative Reference RFC6413 * Normative Reference RFC6414 * Normative Reference RFC6894 * Normative Reference DRAFT-PARISE-LDP-CONVERGENCE-TERM * Normative Reference DRAFT-IETF-BMWG-BGP-BASIC-CONVERGENCE * Normative Reference DRAFT-PARISE-BMWG-LDP-CONVERGENCE-TERM RFC6413: Benchmarking Methodology for Link-State IGP Data-Plane Route Convergence (42 pages) * Normative Reference RFC5308 * Normative Reference RFC5340 * Normative Reference RFC2991 * Normative Reference RFC3357 * Normative Reference RFC5715 * Normative Reference RFC2544 * Normative Reference RFC2285 * Normative Reference BCP14 * Normative Reference RFC4814 * Normative Reference STD54 * Possible Reference RFC5741 * Normative Reference RFC1242 * Normative Reference RFC4062 * Normative Reference RFC4063 * Normative Reference RFC4061 * Normative Reference RFC1195 * Possible Reference RFC2119 * Normative Reference RFC4090 * Normative Reference RFC5714 * Normative Reference RFC3393 * Normative Reference RFC6412 * Normative Reference RFC4689 * Normative Reference RFC6412 * Normative Reference DRAFT-PARISE-LDP-CONVERGENCE-TERM * Normative Reference DRAFT-PARISE-BMWG-LDP-CONVERGENCE-TERM RFC6414: Benchmarking Terminology for Protection Performance (33 pages) * Normative Reference BCP9 * Normative Reference RFC2285 * Normative Reference RFC1242 * Possible Reference RFC2119 * Possible Reference RFC5741 * Normative Reference RFC2026 * Informative Reference RFC4090 * Normative Reference RFC5798 * Normative Reference BCP14 * Informative Reference RFC2474 * Normative Reference RFC4737 * Normative Reference RFC6412 * Normative Reference RFC4689 * Normative Reference RFC6894 RFC6645: IP Flow Information Accounting and Export Benchmarking Methodology (39 pages) * Replaces DRAFT-NOVAK-BMWG-IPFLOW-METH * Replaces DRAFT-JANOVAK-BMWG-IPFLOW-METH * Informative Reference RFC5470 * Informative Reference RFC1242 * Normative Reference RFC2119 * Informative Reference RFC2285 * Informative Reference RFC2544 * Informative Reference RFC5180 * Informative Reference RFC3031 * Possible Reference RFC5741 * Informative Reference RFC3954 * Normative Reference BCP14 * Informative Reference RFC5101 * Informative Reference RFC3917 * Informative Reference RFC5695 RFC6815: Applicability Statement for RFC 2544: Use on Production Networks Considered Harmful (11 pages) * Replaces DRAFT-CHAIRS-BMWG-2544-AS * Updates RFC2544 * Normative Reference RFC5180 * Informative Reference RFC1242 * Informative Reference RFC2544 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC2119 * Possible Reference DRAFT-IETF-BMWG-ISSU-METH RFC6894: Methodology for Benchmarking MPLS Traffic Engineered (MPLS-TE) Fast Reroute Protection (35 pages) * Normative Reference RFC2544 * Informative Reference RFC2285 * Normative Reference RFC1242 * Normative Reference RFC5695 * Normative Reference RFC2119 * Possible Reference RFC5741 * Normative Reference RFC4090 * Normative Reference BCP14 * Informative Reference RFC4202 * Normative Reference RFC6412 * Normative Reference RFC6414 * Informative Reference RFC4689 RFC6985: IMIX Genome: Specification of Variable Packet Sizes for Additional Testing (10 pages) * Replaces DRAFT-MORTON-BMWG-IMIX-GENOME * Informative Reference RFC5470 * Normative Reference RFC2544 * Possible Reference RFC5741 * Normative Reference BCP14 * Normative Reference RFC2119 * Possible Reference DRAFT-BMWG-DCBENCH-METHODOLOGY * Informative Reference RFC7312 Diameter Maintenance and Extensions (dime) ------------------------------------------ Charter Last Modified: 2015-01-26 Current Status: Active Chairs: Jouni Korhonen Lionel Morand Operations and Management Area Directors: Benoit Claise Joel Jaeggli Operations and Management Area Advisor: Kathleen Moriarty Mailing Lists: General Discussion: dime@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/dime Archive: http://www.ietf.org/mail-archive/web/dime/ Description of Working Group: The Diameter Maintenance and Extensions WG will focus on maintenance and extensions to the Diameter protocol required to enable its use for authentication, authorization, accounting, charging in network access, provisioning of configuration information within the network, and for new AAA session management uses within the extensibility rules of the Diameter base protocol. The DIME working group plans to address the following items: - Maintaining and/or progressing, along the standards track, the Diameter Base protocol and Diameter Applications. This includes extensions to Diameter Base protocol that can be considered as enhanced features or bug fixes. - Diameter application design guideline. This document will provide guidelines for design of Diameter extensions. It will detail when to consider reusing an existing application and when to develop a new application. - Protocol extensions for bulk and grouped AAA session management. The aim of this work is to study and standardize a solution for handling groups of AAA sessions within the Diameter base protocol context. The solution would define how to identify and handle grouped AAA sessions in commands and operations. - Diameter overload control. The aim of this work is to identify the limitations of the Diameter protocol level overload control provided by the current Diameter Base protocol. A set of requirements will be provided to define a new Diameter level overload control mechanism. Additionally, Diameter-based systems require interoperability in order to work. The working group, along with the AD, will need to evaluate any potential extensions and require verification that the proposed extension is needed, and is within the extensibility rules of Diameter and AAA scope. Coordination with other IETF working groups and other SDOs (e.g. 3GPP) will be used to ensure this. Goals and Milestones: Done - Submit the following two Diameter Mobility documents to the IESG for consideration as a Proposed Standards:* 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction' * 'Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction' Done - Submit 'Diameter API' to the IESG for consideration as an Informational RFC Done - Submit 'Quality of Service Parameters for Usage with Diameter' to the IESG for consideration as a Proposed Standard. Done - Submit 'Diameter QoS Application' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Support for EAP Re-authentication Protocol' as DIME working group item Done - Submit 'Diameter User-Name and Realm Based Request Routing Clarifications' as DIME working group item Done - Submit 'Diameter Proxy Mobile IPv6' as DIME working group item Done - Submit 'Quality of Service Attributes for Diameter' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Proxy Mobile IPv6' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter User-Name and Realm Based Request Routing Clarifications' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter NAT Control Application' as DIME working group item Done - Submit 'Diameter Capabilities Update' as DIME working group item Done - Submit 'Diameter Credit Control Application MIB' to the IESG for consideration as an Informational RFC Done - Submit 'Diameter Base Protocol MIB' to the IESG for consideration as an Informational RFC Done - Submit 'Diameter Capabilities Update' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Extended NAPTR' as DIME working group item Done - Submit 'Realm-Based Redirection In Diameter' as DIME working group item Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized Routing' as DIME working group item Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic Key Transport' as DIME working group item Done - Submit 'Diameter Priority Attribute Value Pairs' as DIME working group item Done - Submit 'Diameter IKEv2 PSK' as DIME working group item Done - Submit Revision of 'Diameter Base Protocol' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Attribute-Value Pairs for Cryptographic Key Transport' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Priority Attribute Value Pairs' to the IESG for consideration as a Proposed Standard Done - Submit Revision of 'Diameter Network Access Server Application - RFC 4005bis' as DIME working group item Done - Submit 'Diameter NAT Control Application' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter IKEv2 PSK' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Extended NAPTR' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Support for Proxy Mobile IPv6 Localized Routing' to the IESG for consideration as a Proposed Standard Done - Submit 'Realm-Based Redirection In Diameter' to the IESG for consideration as a Proposed Standard Done - Submit Revision of 'Diameter Network Access Server Application - RFC 4005bis' to the IESG for consideration as a Proposed Standard Done - Submit 'Diameter Application Design Guidelines' to the IESG for consideration as a BCP document Done - Submit 'Diameter Support for EAP Re-authentication Protocol' to the IESG for consideration as a Proposed Standard Aug 2012 - Submit 'problem statement and requirements for Diameter end-to-end security framework' as Dime working group item Done - Submit a document on 'Protocol extension for bulk and group signaling' as a working group item Done - Submit I-D 'Diameter Overload Control Requirements' as a working group document. To be Informational RFC Done - Submit I-D 'Diameter Overload Control' as a working group document. To be Standards Track RFC Done - Submit I-D 'Diameter Overload Control Requirements' to the IESG for consideration as a Informational Dec 2012 - Submit 'problem statement and requirements for Diameter end-to-end security framework' to the IESG for consideration as an Informational RFC Mar 2013 - Submit I-D 'Diameter Overload Control' to the IESG for consideration as a Proposed Standard Aug 2013 - Submit a document on 'Protocol extension for bulk and group signaling' to the IESG for consideration as a Proposed Standard Nov 2014 - Submit I-D 'Diameter Congestion and Filter Attributes' to the IESG for considerations as a Proposed Standard Jan 2015 - Submit a document on 'Diameter Agent Overload' as a working group item Jan 2015 - Submit a document on 'Diameter Overload Control Rate Abatement Algorithm' as a working group item Mar 2015 - Submit a document on 'Diameter Load Information' as a working group item Jan 2016 - Submit I-D 'Diameter Agent Overload' to the IESG for consideration as a Proposed Standard Jan 2016 - Submit I-D 'Diameter Overload Control Rate Abatement Algorithm' to the IESG for consideration as a Proposed Standard Mar 2016 - Submit I-D 'Diameter Load Information' to the IESG for consideration as a Proposed Standard Internet-Drafts: - Diameter Overload Indication Conveyance [draft-docdt-dime-ovli-01] (41 pages) - Diameter Agent Overload [draft-ietf-dime-agent-overload-01] (19 pages) - Diameter Applications Design Guidelines [draft-ietf-dime-app-design-guide-28] (29 pages) - The Diameter Capabilities Update Application [draft-ietf-dime-capablities-update-07] (6 pages) - Diameter Congestion and Filter Attributes [draft-ietf-dime-congestion-flow-attributes-01] (9 pages) - The Diameter API [draft-ietf-dime-diameter-api-08] (46 pages) - Diameter Base Protocol MIB [draft-ietf-dime-diameter-base-protocol-mib-06] (51 pages) - Diameter Credit Control Application MIB [draft-ietf-dime-diameter-cc-appl-mib-03] (21 pages) - Updated IANA Considerations for Diameter Command Code Allocations [draft-ietf-dime-diameter-cmd-iana-01] (5 pages) - Diameter Quality-of-Service Application [draft-ietf-dime-diameter-qos-15] (51 pages) - Diameter Overload Rate Control [draft-ietf-dime-doic-rate-control-01] (19 pages) - Diameter AVP Level Security End-to-End Security: Scenarios and Requirements [draft-ietf-dime-e2e-sec-req-02] (9 pages) - Diameter Support for the EAP Re-authentication Protocol (ERP) [draft-ietf-dime-erp-17] (18 pages) - Diameter Straightforward-Naming Authority Pointer (S-NAPTR) Usage [draft-ietf-dime-extended-naptr-09] (14 pages) - Diameter Group Signaling [draft-ietf-dime-group-signaling-04] (22 pages) - Diameter IKEv2 SK: Using Shared Keys to Support Interaction between IKEv2 Servers and Diameter Servers [draft-ietf-dime-ikev2-psk-diameter-11] (17 pages) - Diameter Attribute-Value Pairs for Cryptographic Key Transport [draft-ietf-dime-local-keytran-14] (7 pages) - Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction [draft-ietf-dime-mip6-integrated-12] (17 pages) - Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction [draft-ietf-dime-mip6-split-17] (34 pages) - Clarifications on the Routing of Diameter Requests Based on the Username and the Realm [draft-ietf-dime-nai-routing-04] (11 pages) - Diameter Network Address and Port Translation Control Application [draft-ietf-dime-nat-control-17] (58 pages) - Diameter Overload Control Requirements [draft-ietf-dime-overload-reqs-13] (29 pages) - Diameter Overload Indication Conveyance [draft-ietf-dime-ovli-08] (51 pages) - Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter Server [draft-ietf-dime-pmip6-04] (20 pages) - Diameter Support for Proxy Mobile IPv6 Localized Routing [draft-ietf-dime-pmip6-lr-18] (11 pages) - Diameter Priority Attribute-Value Pairs [draft-ietf-dime-priority-avps-06] (10 pages) - Traffic Classification and Quality of Service (QoS) Attributes for Diameter [draft-ietf-dime-qos-attributes-15] (43 pages) - Quality of Service Parameters for Usage with Diameter [draft-ietf-dime-qos-parameters-11] (12 pages) - Realm-Based Redirection In Diameter [draft-ietf-dime-realm-based-redirect-13] (10 pages) - Diameter Base Protocol [draft-ietf-dime-rfc3588bis-34] (152 pages) - Diameter Network Access Server Application [draft-ietf-dime-rfc4005bis-14] (70 pages) - Diameter AVP Level Security: Scenarios and Requirements [draft-tschofenig-dime-e2e-sec-req-01] (8 pages) - Attribute-Value Pairs For Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional Solutions [draft-zhou-dime-4over6-provisioning-05] (19 pages) Requests for Comments: BCP193: Diameter Applications Design Guidelines (29 pages) * Replaces DRAFT-FAJARDO-DIME-APP-DESIGN-GUIDE * Informative Reference RFC5246 * Informative Reference RFC7155 * Normative Reference RFC2119 * Informative Reference RFC5447 * Informative Reference RFC4740 * Informative Reference RFC5777 * Informative Reference RFC7075 * Normative Reference RFC6733 * Normative Reference BCP14 * Informative Reference RFC3588 * Informative Reference RFC4301 * Informative Reference BCP26 * Informative Reference RFC6083 * Informative Reference RFC4005 * Informative Reference RFC2409 * Informative Reference RFC5996 * Informative Reference RFC6735 * Informative Reference RFC4072 * Informative Reference RFC5226 RFC5447: Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction (17 pages) * Replaces DRAFT-TSCHOFENIG-DIME-MIP6-INTEGRATED * Informative Reference RFC5226 * Informative Reference RFC4640 * Normative Reference RFC2865 * Possible Reference STD1 * Normative Reference RFC4004 * Normative Reference RFC4005 * Informative Reference BCP26 * Normative Reference RFC4072 * Normative Reference RFC3588 * Normative Reference BCP14 * Normative Reference RFC3775 * Informative Reference RFC5026 * Normative Reference RFC2119 * Informative Reference RFC3753 * Normative Reference RFC6611 * Normative Reference RFC5778 * Informative Reference RFC6610 * Informative Reference RFC7423 * Normative Reference RFC5779 * Normative Reference DRAFT-XIA-NETLMM-RADIUS * Informative Reference DRAFT-KORHONEN-NETLMM-LMA-DISCOVERY * Normative Reference DRAFT-KORHONEN-DIME-MIP6-FEATURE-BITS * Informative Reference DRAFT-ZORN-DIME-DOC-SET * Normative Reference DRAFT-CUI-NETEXT-LMA-REDIRECTION-SOLUTION * Normative Reference DRAFT-WU-DIME-PMIP6-LR * Normative Reference RFC7156 * Normative Reference DRAFT-XIA-NETEXT-RADIUS * Normative Reference RFC6572 * Normative Reference DRAFT-IETF-NETEXT-PMIP6-CPC * Normative Reference DRAFT-JIE-NETEXT-CPC-PMIP6 * Normative Reference DRAFT-KOODLI-NETEXT-MULTIACCESS-INDICATOR * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference RFC6632 * Possible Reference DRAFT-DEKOK-RADEXT-DATATYPES RFC5624: Quality of Service Parameters for Usage with Diameter (12 pages) * Replaces DRAFT-KORHONEN-DIME-QOS-PARAMETERS * Informative Reference RFC3260 * Informative Reference RFC2697 * Informative Reference RFC3246 * Normative Reference RFC3140 * Informative Reference RFC2475 * Normative Reference RFC2474 * Normative Reference RFC2215 * Normative Reference RFC2210 * Normative Reference RFC3588 * Normative Reference BCP14 * Normative Reference STD58 * Informative Reference RFC2597 * Possible Reference STD1 * Normative Reference RFC2119 * Normative Reference RFC2578 * Normative Reference RFC5866 * Informative Reference RFC5777 * Normative Reference RFC6735 RFC5719: Updated IANA Considerations for Diameter Command Code Allocations (5 pages) * Updates RFC3588 * Normative Reference RFC5226 * Possible Reference RFC5741 * Normative Reference RFC3588 * Normative Reference BCP14 * Normative Reference RFC3692 * Normative Reference BCP82 * Normative Reference RFC2119 * Normative Reference BCP26 * Obsoletes RFC6733 * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference RFC6632 RFC5729: Clarifications on the Routing of Diameter Requests Based on the Username and the Realm (11 pages) * Replaces DRAFT-KORHONEN-DIME-NAI-ROUTING * Updates RFC3588 * Normative Reference RFC4282 * Informative Reference RFC3490 * Informative Reference RFC2486 * Informative Reference RFC2865 * Informative Reference RFC4284 * Informative Reference RFC1035 * Informative Reference RFC4005 * Informative Reference STD13 * Informative Reference RFC3748 * Informative Reference RFC4072 * Normative Reference RFC3588 * Normative Reference BCP14 * Informative Reference RFC1034 * Possible Reference STD1 * Normative Reference RFC2119 * Informative Reference RFC5113 * Normative Reference RFC6733 * Normative Reference RFC6159 * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference RFC6632 * Informative Reference DRAFT-IETF-RADEXT-NAI RFC5777: Traffic Classification and Quality of Service (QoS) Attributes for Diameter (43 pages) * Replaces DRAFT-KORHONEN-DIME-QOS-ATTRIBUTES * Normative Reference RFC5226 * Informative Reference RFC2475 * Normative Reference RFC2474 * Informative Reference RFC4005 * Normative Reference RFC3168 * Possible Reference RFC5741 * Normative Reference RFC3588 * Normative Reference BCP14 * Normative Reference BCP37 * Normative Reference RFC2780 * Normative Reference RFC2119 * Normative Reference BCP26 * Informative Reference RFC5624 * Normative Reference RFC5778 * Normative Reference RFC5866 * Informative Reference RFC7423 * Normative Reference RFC6736 * Normative Reference DRAFT-HUANG-DIME-PCN-COLLECTION * Normative Reference RFC7155 * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference RFC6632 * Normative Reference DRAFT-BERTZ-DIME-CONGESTION-FLOW-ATTRIBUTES * Normative Reference DRAFT-IETF-DIME-CONGESTION-FLOW-ATTRIBUTES RFC5778: Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction (34 pages) * Replaces DRAFT-TSCHOFENIG-DIME-MIP6-SPLIT * Informative Reference RFC5555 * Normative Reference RFC4283 * Informative Reference RFC4640 * Normative Reference RFC4072 * Normative Reference RFC4285 * Normative Reference BCP14 * Informative Reference RFC5637 * Normative Reference RFC4877 * Informative Reference RFC5226 * Possible Reference RFC5741 * Normative Reference RFC4372 * Normative Reference RFC3775 * Normative Reference RFC3588 * Normative Reference RFC5026 * Normative Reference RFC5149 * Normative Reference RFC4004 * Normative Reference RFC4005 * Normative Reference RFC5447 * Normative Reference RFC2119 * Informative Reference BCP26 * Normative Reference RFC5142 * Normative Reference RFC4306 * Normative Reference RFC5777 * Normative Reference RFC5779 * Normative Reference RFC6408 * Informative Reference RFC6738 * Normative Reference DRAFT-IETF-NETEXT-PMIP6-CPC * Normative Reference DRAFT-JIE-NETEXT-CPC-PMIP6 * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference RFC6632 RFC5779: Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter Server (20 pages) * Replaces DRAFT-KORHONEN-DIME-PMIP6 * Normative Reference RFC4282 * Informative Reference RFC4283 * Possible Reference RFC3580 * Normative Reference RFC5213 * Normative Reference RFC4005 * Informative Reference RFC3315 * Possible Reference RFC5741 * Informative Reference RFC3748 * Normative Reference RFC4072 * Normative Reference RFC3588 * Normative Reference RFC5778 * Informative Reference RFC3775 * Normative Reference BCP14 * Informative Reference RFC2131 * Normative Reference RFC5447 * Normative Reference RFC2119 * Informative Reference RFC5149 * Informative Reference DRAFT-SARIKAYA-NETLMM-LMA-DNSDISCOVERY * Informative Reference RFC6097 * Informative Reference RFC6279 * Informative Reference RFC6463 * Normative Reference RFC7156 * Normative Reference RFC6572 * Normative Reference DRAFT-IETF-NETEXT-PMIP6-CPC * Normative Reference DRAFT-JIE-NETEXT-CPC-PMIP6 * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Normative Reference DRAFT-GUNDAVELLI-NETEXT-PMIPV6-WLAN-APPLICABILITY * Informative Reference RFC6632 * Informative Reference DRAFT-MA-MEXT-DMM-ARMIP * Informative Reference DRAFT-MA-MEXT-DMM-ROMIP * Informative Reference DRAFT-MA-DMM-ARMIP * Informative Reference DRAFT-MA-DMM-ROMIP RFC5866: Diameter Quality-of-Service Application (51 pages) * Replaces DRAFT-TSCHOFENIG-DIME-DIAMETER-QOS * Informative Reference RFC4282 * Informative Reference RFC2205 * Informative Reference RFC4566 * Normative Reference BCP14 * Informative Reference RFC2865 * Possible Reference RFC5741 * Normative Reference RFC3588 * Informative Reference RFC3261 * Informative Reference RFC2474 * Normative Reference RFC4005 * Informative Reference RFC2211 * Informative Reference RFC2212 * Informative Reference RFC3520 * Informative Reference RFC3521 * Normative Reference RFC2119 * Normative Reference RFC5624 * Informative Reference RFC2753 * Informative Reference RFC5246 * Informative Reference RFC3313 * Normative Reference RFC5777 * Informative Reference RFC5973 * Informative Reference RFC5977 * Informative Reference RFC5945 * Normative Reference RFC6408 * Normative Reference RFC6735 * Informative Reference DRAFT-ERSUE-OPSAWG-MANAGEMENT-FW * Informative Reference RFC6632 * Informative Reference DRAFT-KORHONEN-DIME-E2E-SECURITY RFC6408: Diameter Straightforward-Naming Authority Pointer (S-NAPTR) Usage (14 pages) * Replaces DRAFT-JONES-DIME-EXTENDED-NAPTR * Updates RFC3588 * Normative Reference RFC4072 * Informative Reference BCP165 * Normative Reference BCP14 * Normative Reference RFC4740 * Informative Reference RFC6335 * Possible Reference RFC5741 * Normative Reference RFC1035 * Normative Reference RFC3588 * Normative Reference RFC5866 * Normative Reference RFC2782 * Normative Reference STD13 * Normative Reference RFC5234 * Normative Reference RFC4004 * Normative Reference RFC4006 * Normative Reference RFC2119 * Normative Reference RFC3958 * Normative Reference STD68 * Normative Reference RFC5778 * Normative Reference RFC3596 * Normative Reference RFC3403 * Normative Reference RFC6733 * Informative Reference RFC6632 * Informative Reference DRAFT-KORHONEN-DIME-OVL * Informative Reference DRAFT-WU-PCE-DNS-PCE-DISCOVERY RFC6733: Diameter Base Protocol (152 pages) * Obsoletes RFC3588 * Obsoletes RFC5719 * Normative Reference RFC4282 * Normative Reference RFC5226 * Normative Reference RFC3492 * Normative Reference RFC3539 * Informative Reference RFC5176 * Normative Reference BCP106 * Informative Reference RFC2104 * Normative Reference BCP14 * Possible Reference RFC1323 * Informative Reference RFC5461 * Informative Reference BCP165 * Informative Reference RFC6335 * Informative Reference RFC1661 * Informative Reference RFC3162 * Informative Reference RFC2865 * Informative Reference RFC2866 * Informative Reference RFC5905 * Informative Reference RFC2869 * Informative Reference RFC4301 * Normative Reference RFC6408 * Possible Reference RFC5741 * Informative Reference RFC3588 * Informative Reference RFC2782 * Normative Reference RFC5729 * Normative Reference RFC5234 * Informative Reference STD51 * Normative Reference RFC4291 * Informative Reference RFC4690 * Normative Reference RFC4004 * Normative Reference RFC4005 * Informative Reference RFC2989 * Informative Reference RFC2881 * Informative Reference RFC5890 * Normative Reference RFC5891 * Normative Reference RFC3629 * Normative Reference RFC4960 * Normative Reference RFC4006 * Normative Reference RFC6083 * Normative Reference RFC6347 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC3958 * Normative Reference STD68 * Informative Reference RFC1492 * Normative Reference RFC4086 * Informative Reference RFC6737 * Normative Reference STD63 * Normative Reference RFC793 * Normative Reference STD66 * Normative Reference RFC791 * Informative Reference RFC2975 * Informative Reference RFC3748 * Normative Reference RFC5246 * Normative Reference RFC3986 * Possible Reference RFC1644 * Normative Reference RFC5280 * Informative Reference RFC5927 * Updates RFC7075 * Informative Reference DRAFT-IETF-SOFTWIRE-MAP-RADIUS * Informative Reference RFC6919 * Normative Reference DRAFT-RAFIEE-SECAUTH-USECASE * Informative Reference DRAFT-IETF-DIME-OVLI * Informative Reference RFC7241 * Normative Reference RFC7423 * Normative Reference DRAFT-ZHOU-DIME-4OVER6-PROVISIONING * Normative Reference RFC6942 * Normative Reference RFC6736 * Normative Reference RFC6737 * Normative Reference RFC6734 * Normative Reference RFC7075 * Informative Reference RFC7256 * Normative Reference RFC6735 * Normative Reference RFC6738 * Normative Reference RFC7155 * Normative Reference RFC6930 * Informative Reference RFC6867 * Normative Reference DRAFT-IETF-ABFAB-ARCH * Normative Reference DRAFT-JIANG-SOFTWIRE-MAP-RADIUS * Normative Reference DRAFT-KORHONEN-DIME-E2E-SECURITY * Possible Reference DRAFT-IETF-DIME-GROUP-SIGNALING * Normative Reference DRAFT-JIANG-SOFTWIRE-4RD-RADIUS * Informative Reference DRAFT-WALTERMIRE-SACM-USE-CASES * Normative Reference DRAFT-CAMPBELL-DIME-OVERLOAD-ISSUES * Normative Reference RFC7068 * Informative Reference DRAFT-ROACH-DIME-OVERLOAD-CTRL * Normative Reference DRAFT-KORHONEN-DIME-OVL * Informative Reference DRAFT-IETF-RADEXT-NAI * Normative Reference DRAFT-ATWOOD-MBONED-MRAC-ARCH * Normative Reference DRAFT-BERTZ-DIME-CONGESTION-FLOW-ATTRIBUTES * Informative Reference DRAFT-SILVERAJAN-CORE-COAP-ALTERNATIVE-TRANSPORTS * Informative Reference DRAFT-CORUJO-ICN-MGMT * Normative Reference DRAFT-TSCHOFENIG-DIME-E2E-SEC-REQ * Normative Reference DRAFT-TSCHOFENIG-DIME-KEYING-DATABASE * Normative Reference DRAFT-CAMPBELL-DIME-OVERLOAD-DATA-ANALYSIS * Normative Reference DRAFT-FANG-L3VPN-VIRTUAL-PE * Normative Reference DRAFT-WU-PCE-DNS-PCE-DISCOVERY * Normative Reference DRAFT-CHEN-BEHAVE-NAT64-RADIUS-EXTENSION * Normative Reference DRAFT-TSCHOFENIG-DIME-OVERLOAD-ARCH * Normative Reference DRAFT-TSCHOFENIG-DIME-DLBA * Normative Reference DRAFT-TSCHOFENIG-DIME-OVERLOAD-PIGGYBACKING * Informative Reference DRAFT-DBH-SACM-TERMINOLOGY * Normative Reference DRAFT-IETF-DIME-E2E-SEC-REQ * Informative Reference DRAFT-DOCDT-DIME-OVLI * Normative Reference DRAFT-DONOVAN-DIME-AGENT-OVERLOAD * Normative Reference DRAFT-JIANG-INTAREA-CONET-GAP-ANALYSIS * Informative Reference DRAFT-RIJSMAN-SFC-METADATA-CONSIDERATIONS * Informative Reference DRAFT-WINTER-RADEXT-POPULATING-EAPIDENTITY * Normative Reference DRAFT-DONOVAN-DIME-DOC-RATE-CONTROL * Informative Reference DRAFT-IETF-DICE-PROFILE * Normative Reference DRAFT-IETF-DIME-CONGESTION-FLOW-ATTRIBUTES * Informative Reference DRAFT-IETF-SFC-USE-CASE-MOBILITY * Normative Reference DRAFT-CHEN-PCP-AUTHENTICATION-SIM * Normative Reference DRAFT-CONET-AEON-GAP-ANALYSIS * Normative Reference DRAFT-WEI-SFC-RE-CLASSIFICATION * Normative Reference DRAFT-WEI-SFC-MOBILE-CONSIDERATION * Normative Reference DRAFT-DONOVAN-DOIC-AGENT-CASES * Normative Reference DRAFT-TAYLOR-DIME-ADDRESSORPREFIX * Informative Reference DRAFT-CARPENTER-ANIMA-GDN-PROTOCOL * Normative Reference DRAFT-CAMPBELL-DIME-LOAD-CONSIDERATIONS * Informative Reference DRAFT-IETF-RADEXT-DYNAMIC-DISCOVERY * Informative Reference DRAFT-GREEVENBOSCH-ACE-COMPARISON * Normative Reference DRAFT-IETF-BESS-VIRTUAL-PE * Normative Reference DRAFT-IETF-DIME-DOIC-RATE-CONTROL * Normative Reference DRAFT-IETF-DIME-AGENT-OVERLOAD * Normative Reference DRAFT-RAFIEE-SDNAUTH-USECASE * Normative Reference DRAFT-DONOVAN-DIME-DRMP RFC6734: Diameter Attribute-Value Pairs for Cryptographic Key Transport (7 pages) * Replaces DRAFT-WU-DIME-LOCAL-KEYTRAN * Normative Reference RFC5226 * Normative Reference RFC4072 * Informative Reference RFC5216 * Informative Reference RFC6696 * Informative Reference RFC5247 * Possible Reference RFC5741 * Normative Reference RFC3748 * Informative Reference RFC5295 * Normative Reference RFC6733 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference BCP14 * Normative Reference RFC6942 * Normative Reference RFC6738 * Possible Reference DRAFT-BRYANT-MPLS-SYNONYMOUS-FLOW-LABELS RFC6735: Diameter Priority Attribute-Value Pairs (10 pages) * Replaces DRAFT-CARLBERG-DIME-PRIORITY-AVPS * Normative Reference RFC2205 * Normative Reference RFC6401 * Normative Reference RFC3181 * Normative Reference RFC4412 * Possible Reference RFC5741 * Normative Reference RFC6733 * Normative Reference BCP14 * Normative Reference RFC5866 * Normative Reference RFC2119 * Normative Reference RFC5624 * Informative Reference RFC7423 RFC6736: Diameter Network Address and Port Translation Control Application (58 pages) * Replaces DRAFT-BROCKNERS-DIAMETER-NAT-CONTROL * Normative Reference RFC5226 * Informative Reference RFC3550 * Normative Reference BCP14 * Informative Reference STD51 * Informative Reference RFC1661 * Possible Reference RFC5741 * Informative Reference RFC3303 * Normative Reference RFC4675 * Informative Reference RFC3304 * Informative Reference RFC3411 * Informative Reference RFC3022 * Informative Reference RFC5189 * Normative Reference RFC4005 * Informative Reference RFC2663 * Normative Reference RFC2119 * Normative Reference BCP26 * Normative Reference RFC6733 * Informative Reference RFC4097 * Informative Reference STD62 * Informative Reference STD64 * Informative Reference RFC6241 * Informative Reference RFC6146 * Informative Reference RFC6145 * Normative Reference RFC5777 RFC6737: The Diameter Capabilities Update Application (6 pages) * Replaces DRAFT-ZORN-DIME-CAPABLITIES-UPDATE * Possible Reference RFC5741 * Normative Reference RFC6733 * Possible Reference RFC3588 * Normative Reference BCP14 * Informative Reference RFC4960 * Normative Reference RFC2119 * Informative Reference RFC6733 RFC6738: Diameter IKEv2 SK: Using Shared Keys to Support Interaction between IKEv2 Servers and Diameter Servers (17 pages) * Normative Reference RFC6734 * Normative Reference RFC4302 * Informative Reference RFC4285 * Normative Reference RFC4303 * Possible Reference RFC5741 * Informative Reference RFC3748 * Normative Reference RFC6733 * Normative Reference RFC5295 * Informative Reference RFC5778 * Normative Reference RFC5996 * Normative Reference RFC2119 * Normative Reference BCP14 * Possible Reference DRAFT-CHENG-MPLS-TP-PWE3-DUAL-HOMED-PROTECTION RFC6942: Diameter Support for the EAP Re-authentication Protocol (ERP) (18 pages) * Normative Reference RFC5226 * Normative Reference RFC6734 * Normative Reference RFC4072 * Normative Reference RFC6696 * Informative Reference RFC4303 * Possible Reference RFC5741 * Normative Reference RFC3748 * Normative Reference RFC5295 * Informative Reference RFC3588 * Normative Reference BCP14 * Normative Reference RFC6733 * Informative Reference RFC6347 * Informative Reference RFC5246 * Normative Reference RFC2119 * Normative Reference BCP26 * Informative Reference DRAFT-PEREZ-ABFAB-WG-ARCH-ERP RFC7068: Diameter Overload Control Requirements (29 pages) * Replaces DRAFT-MCMURRY-DIME-OVERLOAD-REQS * Normative Refer