idnits 2.17.1 draft-xu-ospf-ipv6-router-id-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 24, 2014) is 3655 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC1195' is defined on line 120, but no explicit reference was found in the text == Unused Reference: 'RFC5305' is defined on line 123, but no explicit reference was found in the text == Unused Reference: 'RFC5308' is defined on line 126, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4970 (Obsoleted by RFC 7770) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group X. Xu 3 Internet-Draft Huawei 4 Intended status: Standards Track April 24, 2014 5 Expires: October 26, 2014 7 Carrying IPv6 Router ID in OSPFv3 RI LSA 8 draft-xu-ospf-ipv6-router-id-00 10 Abstract 12 This document proposes a new TLV within the body of the OSPFv3 Router 13 Information (RI) Opaque LSA, called IPv6 Router ID TLV. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on October 26, 2014. 32 Copyright Notice 34 Copyright (c) 2014 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 51 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 52 3. IPv6 Router ID TLV . . . . . . . . . . . . . . . . . . . . . 2 53 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 54 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 55 6. Security Considerations . . . . . . . . . . . . . . . . . . . 3 56 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 7.1. Normative References . . . . . . . . . . . . . . . . . . 3 58 7.2. Informative References . . . . . . . . . . . . . . . . . 3 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1. Introduction 63 There are several situations where it is useful for the OSPFv3 64 routers in one area to establish the correlations between the IPv6 65 addresses and the capabilities of the other OSPFv3 routers in another 66 area. However, in the OSPFv3 Router Information (RI) Opaque LSA as 67 defined in [RFC4970], which is used by OSPFv3 routers to announce 68 their capabilities, only a 4-octet router ID is contained (in the 69 Advertising Router field). Therefore, this document propose a new 70 TLV within the body of this RI LSA to carry an 16-octect router ID. 71 This 16-octect router ID MUST be a routable IPv6 global address of 72 the router originating the RI LSA. 74 1.1. Requirements Language 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 77 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 78 document are to be interpreted as described in RFC 2119 [RFC2119]. 80 2. Terminology 82 This memo makes use of the terms defined in [RFC4970]. 84 3. IPv6 Router ID TLV 86 A new TLV within the body of the OSPFv3 RI Opaque LSA, called IPv6 87 Router ID TLV is defined to carry a routable IPv6 global address of 88 the router originating the RI LSA. The Type of this TLV is TBD, the 89 Length is set to 16, and the Value field contains an routable IPv6 90 global address of the router originating the RI LSA. This TLV is 91 only applicable to OSPFv3. The scope of the advertisement depends on 92 the application but it is recommended that it SHOULD be domain-wide. 94 4. Acknowledgements 96 TBD. 98 5. IANA Considerations 100 This document includes a request to IANA to allocate a TLV type for 101 the new RI LSA TLV proposed in this document. 103 6. Security Considerations 105 This document does not introduce any new security risk. 107 7. References 109 7.1. Normative References 111 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 112 Requirement Levels", BCP 14, RFC 2119, March 1997. 114 [RFC4970] Lindem, A., Shen, N., Vasseur, JP., Aggarwal, R., and S. 115 Shaffer, "Extensions to OSPF for Advertising Optional 116 Router Capabilities", RFC 4970, July 2007. 118 7.2. Informative References 120 [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and 121 dual environments", RFC 1195, December 1990. 123 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 124 Engineering", RFC 5305, October 2008. 126 [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, October 127 2008. 129 Author's Address 131 Xiaohu Xu 132 Huawei 134 Email: xuxiaohu@huawei.com