Liaison statement
Liaison to IETF on IP Services Approved Draft 1
Additional information about IETF liaison relationships is available on the
IETF webpage
and the
Internet Architecture Board liaison webpage.
State | Posted |
---|---|
Submitted Date | 2017-05-03 |
From Group | MEF |
From Contact | Raghu Ranganathan |
To Groups | OPS, RTG |
To Contacts | Warren Kumari <warren@kumari.net> Benoit Claise <bclaise@cisco.com> Alia Atlas <akatlas@gmail.com> Alvaro Retana <aretana@cisco.com> Deborah Brungard <db3546@att.com> |
Cc | Alvaro Retana <aretana@cisco.com> Deborah Brungard <db3546@att.com> Alia Atlas <akatlas@gmail.com> Warren Kumari <warren@kumari.net> The IETF Chair <chair@ietf.org> Benoit Claise <bclaise@cisco.com> Raghu Ranganathan <rraghu@ciena.com> |
Response Contact | rraghu@ciena.com nan@mef.net ssteiff@pccwglobal.com |
Purpose | For information |
Attachments | L00263_001_LiaisontoIETFonIPServicesApprovedDraft1_Ball_Ranganathan.pdf |
Body |
Following our previous liaisons, we would like to update you on the progress of the MEF IP Service Attributes project. A new Approved Draft of our specification for IP Service Attributes for Subscriber Services is available, which can be accessed as described below. Note that a corresponding specification for IP Service Attributes for Operator Services is in progress but an Approved Draft is not yet available. In the course of our work, we have reviewed some of the internet drafts from the L3SM working group that preceded publication of RFC 8049 ("Yang Data Model for L3VPN Service Delivery"), and we used this as input to our specification. Now that RFC 8049 is published, we intend to review it again to ensure our work remains aligned. We would appreciate your review of our Approved Draft, and in particular any assistance you can give in identifying areas where it may conflict or be otherwise misaligned with RFC 8049. Note that the scope of the current IP Service Attributes project does not include definition of a yang module; however, we expect that a future project will include specification of a yang module based on the service attributes defined in this document. It is our hope that such a module can be defined as an augment of the module defined in RFC 8049. MEF’s liaison partners may access all MEF approved drafts as follows: https://mef.net/liaison-login Username: mef Password: M3F3030 The next MEF meetings are: July 24 - 27, Toronto, Canada October 23 - 26, Raleigh, USA |