idnits 2.17.1 draft-ietf-bess-pta-flags-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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC6514, but the abstract doesn't seem to directly say this. It does mention RFC6514 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC6514, updated by this document, for RFC5378 checks: 2006-08-01) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 23, 2015) is 3343 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BESS Working Group E. Rosen 3 Internet-Draft Juniper Networks, Inc. 4 Updates: 6514 (if approved) February 23, 2015 5 Intended status: Standards Track 6 Expires: August 27, 2015 8 IANA Registry for P-Multicast Service Interface Tunnel Attribute Flags 9 draft-ietf-bess-pta-flags-00.txt 11 Abstract 13 RFC6514 defines the "P-Multicast Service Interface Tunnel (PMSI 14 Tunnel) attribute". This attribute contains an octet of "flags". 15 Only one flag is defined in that RFC, but there is now a need to 16 define additional flags. Since the RFC did not create a registry for 17 the assignment of flag bits, this document updates the RFC by 18 creating a registry for that purpose. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on August 27, 2015. 37 Copyright Notice 39 Copyright (c) 2015 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 56 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 57 4. Normative References . . . . . . . . . . . . . . . . . . . . 3 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 60 1. Introduction 62 [RFC6514] defines the "P-Multicast Service Interface Tunnel (PMSI 63 Tunnel) attribute". This attribute contains an octet of "flags". 64 Only one flag is defined in that RFC, but there is now a need to 65 define additional flags. Since the RFC did not create a registry for 66 the assignment of flag bits, this document creates a registry for 67 that purpose. 69 2. IANA Considerations 71 IANA is requested to create a new registry called "P-Multicast 72 Service Interface Tunnel (PMSI Tunnel) Attribute Flags" in the 73 "Border Gateway Protocol (BGP) Parameters" registry. 75 Per [RFC6514] section 5, a PMSI Tunnel Attribute contains a "Flags" 76 octet. The Flags field is a single octet, with bits numbered, left- 77 to-right, from 0 to 7. IANA is requested to initialize the registry 78 as follows: 80 Bit Position Description Reference 81 (left to right) 82 0 unassigned 83 1 unassigned 84 2 unassigned 85 3 unassigned 86 4 unassigned 87 5 unassigned 88 6 unassigned 89 7 Leaf Information Required (LIR) RFC6514 91 PMSI Tunnel Attribute Flags 93 The registration procedure for this registry is Standards Action. 95 3. Security Considerations 97 No security considerations are raised by this document. 99 4. Normative References 101 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 102 Encodings and Procedures for Multicast in MPLS/BGP IP 103 VPNs", RFC 6514, February 2012. 105 Author's Address 107 Eric C. Rosen 108 Juniper Networks, Inc. 109 10 Technology Park Drive 110 Westford, Massachusetts 01886 111 USA 113 Email: erosen@juniper.net