YANG Data Model for L3VPN Service Delivery
draft-wu-l3sm-rfc8049bis-07

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 8299.
Authors Qin Wu , Stephane Litkowski , Luis Tomotaki , Kenichi Ogaki
Last updated 2017-10-25 (Latest revision 2017-10-13)
RFC stream Internet Engineering Task Force (IETF)
Formats
txt htmlized pdf bibtex bibxml
Reviews
SECDIR Telechat review (of -09) by Rifaat Shekh-Yusef Ready
RTGDIR Last Call review by Lou Berger Has issues
GENART Last Call review by Jari Arkko Ready w/issues
SECDIR Last Call review (of -05) by Rifaat Shekh-Yusef Has issues
OPSDIR Last Call review (of -05) by Carlos Martínez Ready
Additional resources
Stream WG state (None)
Document shepherd Adrian Farrel
Shepherd write-up Show Last changed 2017-09-12
IESG IESG state Became RFC 8299 (Proposed Standard)
Consensus boilerplate Yes
Telechat date (None)
Needs 9 more YES or NO OBJECTION positions to pass.
Responsible AD Benoît Claise
Send notices to adrian@olddog.co.uk
IANA IANA review state IANA OK - Actions Needed
Email authors IPR References Referenced by Nits Search email archive
draft-wu-l3sm-rfc8049bis-07 
quot; YANG module MUST be
   carefully created, read, updated, or deleted as appropriate.  The
   entries in the lists below include customer-proprietary or
   confidential information; therefore, access to confidential
   information MUST be limited to authorized clients, and other clients
   MUST NOT be permitted to access the information.

   o  /l3vpn-svc/vpn-services/vpn-service

   o  /l3vpn-svc/sites/site

   The data model defines some security parameters than can be extended
   via augmentation as part of the customer service request; those
   parameters are described in Section 6.9.

11.  IANA Considerations

   IANA has assigned a new URI from the "IETF XML Registry" [RFC3688].

             URI: urn:ietf:params:xml:ns:yang:ietf-l3vpn-svc
             Registrant Contact: The IESG
             XML: N/A; the requested URI is an XML namespace.

Wu, et al.               Expires April 16, 2018               [Page 180]
Internet-Draft YANG Data Model for L3VPN Service Delivery   October 2017

   IANA has recorded a YANG module name in the "YANG Module Names"
   registry [RFC7950] as follows:

           Name: ietf-l3vpn-svc
           Namespace: urn:ietf:params:xml:ns:yang:ietf-l3vpn-svc
           Prefix: l3vpn-svc
           Reference: RFC 8049

   IANA is requested to update this registry to reference this document
   on publication as an RFC.

12.  References

12.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              DOI 10.17487/RFC3688, January 2004,
              <https://www.rfc-editor.org/info/rfc3688>.

   [RFC4364]  Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
              Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
              2006, <https://www.rfc-editor.org/info/rfc4364>.

   [RFC4577]  Rosen, E., Psenak, P., and P. Pillay-Esnault, "OSPF as the
              Provider/Customer Edge Protocol for BGP/MPLS IP Virtual
              Private Networks (VPNs)", RFC 4577, DOI 10.17487/RFC4577,
              June 2006, <https://www.rfc-editor.org/info/rfc4577>.

   [RFC4862]  Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
              Address Autoconfiguration", RFC 4862,
              DOI 10.17487/RFC4862, September 2007,
              <https://www.rfc-editor.org/info/rfc4862>.

   [RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
              and A. Bierman, Ed., "Network Configuration Protocol
              (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
              <https://www.rfc-editor.org/info/rfc6241>.

   [RFC6513]  Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
              BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
              2012, <https://www.rfc-editor.org/info/rfc6513>.

Wu, et al.               Expires April 16, 2018               [Page 181]
Internet-Draft YANG Data Model for L3VPN Service Delivery   October 2017

   [RFC6536]  Bierman, A. and M. Bjorklund, "Network Configuration
              Protocol (NETCONF) Access Control Model", RFC 6536,
              DOI 10.17487/RFC6536, March 2012,
              <https://www.rfc-editor.org/info/rfc6536>.

   [RFC7950]  Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
              RFC 7950, DOI 10.17487/RFC7950, August 2016,
              <https://www.rfc-editor.org/info/rfc7950>.

   [RFC8040]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
              <https://www.rfc-editor.org/info/rfc8040>.

   [RFC8049]  Litkowski, S., Tomotaki, L., and K. Ogaki, "YANG Data
              Model for L3VPN Service Delivery", RFC 8049,
              DOI 10.17487/RFC8049, February 2017,
              <https://www.rfc-editor.org/info/rfc8049>.

12.2.  Informative References

   [RFC4026]  Andersson, L. and T. Madsen, "Provider Provisioned Virtual
              Private Network (VPN) Terminology", RFC 4026,
              DOI 10.17487/RFC4026, March 2005,
              <https://www.rfc-editor.org/info/rfc4026>.

   [RFC4110]  Callon, R. and M. Suzuki, "A Framework for Layer 3
              Provider-Provisioned Virtual Private Networks (PPVPNs)",
              RFC 4110, DOI 10.17487/RFC4110, July 2005,
              <https://www.rfc-editor.org/info/rfc4110>.

   [RFC4760]  Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
              "Multiprotocol Extensions for BGP-4", RFC 4760,
              DOI 10.17487/RFC4760, January 2007,
              <https://www.rfc-editor.org/info/rfc4760>.

Appendix A.  Acknowledgements

   Maxim Klyus, Luis Miguel Contreras, Gregory Mirsky, Zitao Wang, Jing
   Zhao, Kireeti Kompella, Eric Rosen, Aijun Wang,Michael Scharf, Xufeng
   Liu, David Ball, Lucy Yong, Jean-Philippe Landry, and Andrew Leu
   provided useful review to this document.

   Jan Lindblad reviewed the first release of RFC8049 and found some
   bugs and His thorough YANG Doctor review on the YANG Model is
   valuable input to revision of RFC8049.  David ball also provided a
   second review on published RFC8049.

   Many thanks to these people.

Wu, et al.               Expires April 16, 2018               [Page 182]
Internet-Draft YANG Data Model for L3VPN Service Delivery   October 2017

Appendix B.  Contributors

   The authors would like to thank Rob Shakir for his major
   contributions to the initial modeling and use cases.

   Adrian Farrel prepared the editorial revisions for this bis.

Authors' Addresses

   Qin Wu (editor)
   Huawei Technologies

   Email: bill.wu@huawei.com

   Stephane Litkowski
   Orange Business Services

   Email: stephane.litkowski@orange.com

   Luis Tomotaki
   Verizon

   Email: luis.tomotaki@verizon.com

   Kenichi Ogaki
   KDDI Corporation

   Email: ke-oogaki@kddi.com

Wu, et al.               Expires April 16, 2018               [Page 183]