RE: [mpls] Last Call: <draft-ietf-mpls-tp-mip-mep-map-08.txt> (Per-Interface MIP Addressing Requirements and Design Considerations) to Informational RFC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Authors,

In  the terminology section ( section 3) of draft , the in-mip and out-mip are defined using forwarding engine as reference .
But the term forwarding engine has not been explained in terminology section. Since the  forwarding engine ( FW) is used in all the diagram in the draft , I feel it will be helpful if you could add some description in terminology section to state what does the forwarding engine means here .  

Regards,
Vivek

 

-----Original Message-----
From: mpls-bounces@xxxxxxxx [mailto:mpls-bounces@xxxxxxxx] On Behalf Of The IESG
Sent: Wednesday, July 31, 2013 3:19 PM
To: IETF-Announce
Cc: mpls@xxxxxxxx
Subject: [mpls] Last Call: <draft-ietf-mpls-tp-mip-mep-map-08.txt> (Per-Interface MIP Addressing Requirements and Design Considerations) to Informational RFC


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'Per-Interface MIP Addressing Requirements and Design Considerations'
  <draft-ietf-mpls-tp-mip-mep-map-08.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@xxxxxxxx mailing lists by 2013-08-21. Exceptionally, comments may be
sent to iesg@xxxxxxxx instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The Framework for Operations, Administration and Maintenance (OAM)
   within the MPLS Transport Profile (MPLS-TP) describes how Maintenance
   Entity Group Intermediate Points (MIPs) may be situated within
   network nodes at the incoming and outgoing interfaces.

   This document elaborates on important considerations for internal MIP
   addressing.  More precisely it describes important restrictions for
   any mechanism that specifies a way of forming OAM messages so that
   they can be targeted at MIPs on incoming or MIPs on outgoing
   interfaces and forwarded correctly through the forwarding engine.
   Furthermore, the document includes considerations for node
   implementations where there is no distinction between the incoming
   and outgoing MIP.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-mip-mep-map/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-mip-mep-map/ballot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
mpls mailing list
mpls@xxxxxxxx
https://www.ietf.org/mailman/listinfo/mpls







[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]