Loa Andersson | 2 Oct 08:51 2014
Picon

IPR poll on draft-raza-mpls-oam-ipv6-rao

Working Group,

The authors of draft-raza-mpls-oam-ipv6-rao have told us that the
draft is ready to be accepted as a working group document.

Before we do poll to see if we have consensus to accept the document
as a working group document we want to do an IPR poll on the document.

This mail starts that IPR poll.

Are you aware of any IPR that applies to draft-raza-mpls-oam-ipv6-rao?

If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3979, 4879, 3669 and 5378 for more details).

Currently there are no IPR disclosures that relates to this document.

If you are listed as a document author or contributor please respond to
this email regardless of whether or not you are aware of any relevant
IPR. *The response needs to be sent to the MPLS wg mailing list.* The 
document will not advance to the next stage until a response has been
received from each author and contributor.

If you are on the MPLS WG email list but are not listed as an author or
contributor, then please explicitly respond only if you are aware of any
IPR that has not yet been disclosed in conformance with IETF rules.

Thanks, Loa
(as MPLS WG co-chair)
--

-- 
(Continue reading)

Dutta, Pranjal K (Pranjal | 2 Oct 02:08 2014

Re: MPLS-RT review of I-D Action: draft-raza-mpls-oam-ipv6-rao-01.txt

Hi Loa and Authors,

                                  I have reviewed this document.  It is short document with a simple extension. It is useful and technically sound. I think the document is ready for WG adoption.

Thanks,

Pranjal

 

-----Original Message-----
From: Loa Andersson [mailto:loa <at> pi.nu]
Sent: Wednesday, September 17, 2014 8:58 AM
To: Osborne, Eric; Lizhong Jin; Dutta, Pranjal K (Pranjal); Eric Gray; mpls-chairs <at> tools.ietf.org; VIGOUREUX, MARTIN (MARTIN)
Subject: MPLS-RT review of I-D Action: draft-raza-mpls-oam-ipv6-rao-01.txt

 

Eric, Lizhong, Pranjal and Eric,

 

You have be selected as MPLS-RT reviewers for draft-raza-mpls- oam-ipv6-rao.

 

Note to authors: You have been CC'd on this email so that you can know that this review is going on. However, please do not review your own document.

 

Reviews should comment on whether the document is coherent, is it useful (ie, is it likely to be actually useful in operational networks), and is the document technically sound?  We are interested in knowing whether the document is ready to be considered for WG adoption (ie, it doesn't have to be perfect at this point, but should be a good start).

 

Reviews should be sent to the document authors, WG co-chairs and WG secretary, and CC'd to the MPLS WG email list. If necessary, comments may be sent privately to only the WG chairs.

 

If you have technical comments you should try to be explicit about what

*really* need to be resolved before adopting it as a working group document, and what can wait until the document is a working group document and the working group has the revision control.

 

Are you able to review this draft by Oct 1, 2014? Please respond in a

timely fashion.  

 

 

Thanks, Loa

(as MPLS WG chair)

 

 

-------- Original Message --------

Subject: I-D Action: draft-raza-mpls-oam-ipv6-rao-01.txt

Date: Wed, 17 Sep 2014 06:53:44 -0700

From: internet-drafts <at> ietf.org

Reply-To: internet-drafts <at> ietf.org

To: i-d-announce <at> ietf.org

CC: mpls <at> ietf.org

 

 

A New Internet-Draft is available from the on-line Internet-Drafts directories.

  This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

 

         Title           : IPv6 Router Alert Option for MPLS OAM

         Authors         : Kamran Raza

                           Nobo Akiya

                           Carlos Pignataro

      Filename        : draft-raza-mpls-oam-ipv6-rao-01.txt

      Pages           : 5

      Date            : 2014-09-17

 

Abstract:

    RFC4379 defines the MPLS LSP Ping/Traceroute mechanism, in which the

    Router Alert option must be set in the IP header of the MPLS Echo

    Request messages, and may conditionally be set in the IP header of

    the MPLS Echo Reply messages.  While a generic "Router shall examine

    packet" Option Value is used for the IPv4 Router Alert Option (RAO),

    there is no generic Router Alert Option Value defined for IPv6 that

    can be used.  This document allocates a new generic IPv6 Router Alert

    Option Value that can be used by MPLS OAM tools, including the MPLS

    Echo Request and MPLS Echo Reply messages for MPLS IPv6.

 

    The initial motivation to request an IPv6 Router Alert Option (RAO)

    code point for MPLS OAM comes from MPLS LSP Ping/Traceroute.

    However, this codepoint is applicable to all MPLS OAM and not limited

    to MPLS LSP Ping/Traceroute.

 

 

The IETF datatracker status page for this draft is:

https://datatracker.ietf.org/doc/draft-raza-mpls-oam-ipv6-rao/

 

There's also a htmlized version available at:

http://tools.ietf.org/html/draft-raza-mpls-oam-ipv6-rao-01

 

A diff from the previous version is available at:

http://www.ietf.org/rfcdiff?url2=draft-raza-mpls-oam-ipv6-rao-01

 

 

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

 

Internet-Drafts are also available by anonymous FTP at:

ftp://ftp.ietf.org/internet-drafts/

 

_______________________________________________

I-D-Announce mailing list

I-D-Announce <at> ietf.org

https://www.ietf.org/mailman/listinfo/i-d-announce

Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

 

 

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
internet-drafts | 1 Oct 03:46 2014
Picon

I-D Action: draft-raza-mpls-oam-ipv6-rao-02.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

        Title           : IPv6 Router Alert Option for MPLS OAM
        Authors         : Kamran Raza
                          Nobo Akiya
                          Carlos Pignataro
	Filename        : draft-raza-mpls-oam-ipv6-rao-02.txt
	Pages           : 5
	Date            : 2014-09-30

Abstract:
   RFC4379 defines the MPLS LSP Ping/Traceroute mechanism, in which the
   Router Alert option must be set in the IP header of the MPLS Echo
   Request messages, and may conditionally be set in the IP header of
   the MPLS Echo Reply messages.  While a generic "Router shall examine
   packet" Option Value is used for the IPv4 Router Alert Option (RAO),
   there is no generic Router Alert Option Value defined for IPv6 that
   can be used.  This document allocates a new generic IPv6 Router Alert
   Option Value that can be used by MPLS OAM tools, including the MPLS
   Echo Request and MPLS Echo Reply messages for MPLS IPv6.

   The initial motivation to request an IPv6 Router Alert Option (RAO)
   code point for MPLS OAM comes from MPLS LSP Ping/Traceroute.
   However, this codepoint is applicable to all MPLS OAM and not limited
   to MPLS LSP Ping/Traceroute.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-raza-mpls-oam-ipv6-rao/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-raza-mpls-oam-ipv6-rao-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-raza-mpls-oam-ipv6-rao-02

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls

internet-drafts | 30 Sep 20:48 2014
Picon

I-D Action: draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

        Title           : Configuration of Pro-Active Operations, Administration, and Maintenance (OAM) Functions for
MPLS-based Transport Networks using LSP Ping
        Authors         : Elisa Bellagamba
                          Gregory Mirsky
                          Loa Andersson
                          Pontus Skoldstrom
                          Dave Ward
                          John Drake
	Filename        : draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-07.txt
	Pages           : 21
	Date            : 2014-09-30

Abstract:
   This specification describes the configuration of pro-active MPLS-TP
   Operations, Administration, and Maintenance (OAM) Functions for a
   given LSP using a set of TLVs that are carried by the LSP-Ping
   protocol.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-07

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls

Lizhong Jin | 30 Sep 16:55 2014
Picon

Re: MPLS-RT review of I-D Action: draft-raza-mpls-oam-ipv6-rao-01.txt

Hi Loa, authors,
I review this document. It is a short document, and is usefull and technically sound. And I believe it is ready for adoption.
One small comment is the name of the option value. MPLS OAM is a general term, not a special protocol. Currently IPv6 RAO is only defined for special protocol. My concern is, it seems all kinds of future MPLS OAM protocols are required to use the option value defined in this draft, which may not be a good choice for them.

Regards
Lizhong Jin
 
Date: 2014-09-17 23:58
Subject: MPLS-RT review of I-D Action: draft-raza-mpls-oam-ipv6-rao-01.txt
Eric, Lizhong, Pranjal and Eric,
 
You have be selected as MPLS-RT reviewers for draft-raza-mpls-
oam-ipv6-rao.
 
Note to authors: You have been CC'd on this email so that you can know
that this review is going on. However, please do not review your own
document.
 
Reviews should comment on whether the document is coherent, is it
useful (ie, is it likely to be actually useful in operational
networks), and is the document technically sound?  We are interested
in knowing whether the document is ready to be considered for WG
adoption (ie, it doesn't have to be perfect at this point, but should be
a good start).
 
Reviews should be sent to the document authors, WG co-chairs and
WG secretary, and CC'd to the MPLS WG email list. If necessary, comments
may be sent privately to only the WG chairs.
 
If you have technical comments you should try to be explicit about what
*really* need to be resolved before adopting it as a working group
document, and what can wait until the document is a working group
document and the working group has the revision control.
 
Are you able to review this draft by Oct 1, 2014? Please respond in a
timely fashion.
 
 
Thanks, Loa
(as MPLS WG chair)
 
 
-------- Original Message --------
Subject: I-D Action: draft-raza-mpls-oam-ipv6-rao-01.txt
Date: Wed, 17 Sep 2014 06:53:44 -0700
From: internet-drafts <at> ietf.org
Reply-To: internet-drafts <at> ietf.org
To: i-d-announce <at> ietf.org
CC: mpls <at> ietf.org
 
 
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
  This draft is a work item of the Multiprotocol Label Switching Working
Group of the IETF.
 
         Title           : IPv6 Router Alert Option for MPLS OAM
         Authors         : Kamran Raza
                           Nobo Akiya
                           Carlos Pignataro
Filename        : draft-raza-mpls-oam-ipv6-rao-01.txt
Pages           : 5
Date            : 2014-09-17
 
Abstract:
    RFC4379 defines the MPLS LSP Ping/Traceroute mechanism, in which the
    Router Alert option must be set in the IP header of the MPLS Echo
    Request messages, and may conditionally be set in the IP header of
    the MPLS Echo Reply messages.  While a generic "Router shall examine
    packet" Option Value is used for the IPv4 Router Alert Option (RAO),
    there is no generic Router Alert Option Value defined for IPv6 that
    can be used.  This document allocates a new generic IPv6 Router Alert
    Option Value that can be used by MPLS OAM tools, including the MPLS
    Echo Request and MPLS Echo Reply messages for MPLS IPv6.
 
    The initial motivation to request an IPv6 Router Alert Option (RAO)
    code point for MPLS OAM comes from MPLS LSP Ping/Traceroute.
    However, this codepoint is applicable to all MPLS OAM and not limited
    to MPLS LSP Ping/Traceroute.
 
 
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-raza-mpls-oam-ipv6-rao/
 
There's also a htmlized version available at:
http://tools.ietf.org/html/draft-raza-mpls-oam-ipv6-rao-01
 
A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-raza-mpls-oam-ipv6-rao-01
 
 
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
 
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
 
_______________________________________________
I-D-Announce mailing list
I-D-Announce <at> ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
 
 
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
Rakesh Gandhi (rgandhi | 30 Sep 16:07 2014
Picon

Re: New Version Notification for draft-ietf-mpls-p2mp-loose-path-reopt-01.txt

Hi WG,

We have updated the draft to address review comments. Changes are as
follows:

- Include sub-group based re-optimization mode where multiple Path
messages are combined (Section 1.2, 3.2) as per review comments from
Dimitri.
- Add extension for BEGIN and END markers for the S2L sub-LSP in the
descriptor list when Path messages are combined (Section 4.3, 7.3).
- Editing changes as per review comments from Nobo Akiya (Multiple
Sections).
- Minor misc editing changes.

Your review comments on the changes and this draft in general are welcome.

Thanks,
Rakesh

On 2014-09-30 8:37 AM, "internet-drafts <at> ietf.org"
<internet-drafts <at> ietf.org> wrote:

>
>A new version of I-D, draft-ietf-mpls-p2mp-loose-path-reopt-01.txt
>has been successfully submitted by Rakesh Gandhi and posted to the
>IETF repository.
>
>Name:		draft-ietf-mpls-p2mp-loose-path-reopt
>Revision:	01
>Title:		Extensions to Resource Reservation Protocol For Re-optimization
>of Loosely Routed Point-to-Multipoint Traffic Engineering LSPs
>Document date:	2014-09-30
>Group:		mpls
>Pages:		15
>URL:            
>http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-loose-path-reopt-
>01.txt
>Status:         
>https://datatracker.ietf.org/doc/draft-ietf-mpls-p2mp-loose-path-reopt/
>Htmlized:       
>http://tools.ietf.org/html/draft-ietf-mpls-p2mp-loose-path-reopt-01
>Diff:           
>http://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-p2mp-loose-path-reopt-01
>
>Abstract:
>   For a Traffic Engineered (TE) point-to-multipoint (P2MP) Label
>   Switched Path (LSP), it is preferable in some cases to re-evaluate
>   and re-optimize the entire P2MP-TE LSP by re-signaling all its
>   Source-to-Leaf (S2L) sub-LSP(s).  Existing mechanisms, a mechanism
>   for an ingress Label Switched Router (LSR) to trigger a new path re-
>   evaluation request and a mechanism for a mid-point LSR to notify an
>   availability of a preferred path, operate on an individual or a sub-
>   group of S2L sub-LSP(s) basis only.
>
>   This document defines RSVP-TE signaling extensions to allow an
>   ingress node of a P2MP-TE LSP to request the re-evaluation of the
>   entire LSP tree containing one or more S2L sub-LSPs whose paths are
>   loose (or abstract) hop expanded, and for a mid-point LSR to notify
>   to the ingress node that a preferable tree exists for the entire
>   P2MP-TE LSP.  This document also defines markers to indicate
>   beginning and end of a S2L sub-LSP descriptor list when RSVP message
>   needs to be fragmented due to large number of S2L sub-LSPs when
>   performing re-optimization.
>
>
>                  
>        
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls

internet-drafts | 30 Sep 14:37 2014
Picon

I-D Action: draft-ietf-mpls-p2mp-loose-path-reopt-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

        Title           : Extensions to Resource Reservation Protocol For Re-optimization of Loosely Routed
Point-to-Multipoint Traffic Engineering LSPs
        Authors         : Tarek Saad
                          Rakesh Gandhi
                          Zafar Ali
                          Robert H. Venator
                          Yuji Kamite
	Filename        : draft-ietf-mpls-p2mp-loose-path-reopt-01.txt
	Pages           : 15
	Date            : 2014-09-30

Abstract:
   For a Traffic Engineered (TE) point-to-multipoint (P2MP) Label
   Switched Path (LSP), it is preferable in some cases to re-evaluate
   and re-optimize the entire P2MP-TE LSP by re-signaling all its
   Source-to-Leaf (S2L) sub-LSP(s).  Existing mechanisms, a mechanism
   for an ingress Label Switched Router (LSR) to trigger a new path re-
   evaluation request and a mechanism for a mid-point LSR to notify an
   availability of a preferred path, operate on an individual or a sub-
   group of S2L sub-LSP(s) basis only.

   This document defines RSVP-TE signaling extensions to allow an
   ingress node of a P2MP-TE LSP to request the re-evaluation of the
   entire LSP tree containing one or more S2L sub-LSPs whose paths are
   loose (or abstract) hop expanded, and for a mid-point LSR to notify
   to the ingress node that a preferable tree exists for the entire
   P2MP-TE LSP.  This document also defines markers to indicate
   beginning and end of a S2L sub-LSP descriptor list when RSVP message
   needs to be fragmented due to large number of S2L sub-LSPs when
   performing re-optimization.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mpls-p2mp-loose-path-reopt/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mpls-p2mp-loose-path-reopt-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-p2mp-loose-path-reopt-01

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls

internet-drafts | 30 Sep 02:05 2014
Picon

I-D Action: draft-kini-mpls-spring-entropy-label-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

        Title           : Entropy labels for source routed stacked tunnels
        Authors         : Sriganesh Kini
                          Kireeti Kompella
                          Siva Sivabalan
                          Stephane Litkowski
                          Rob Shakir
                          Xiaohu Xu
                          Wim Hendrickx
                          Jeff Tantsura
	Filename        : draft-kini-mpls-spring-entropy-label-01.txt
	Pages           : 10
	Date            : 2014-09-29

Abstract:
   Source routed tunnel stacking is a technique that can be leveraged to
   provide a method to steer a packet through a controlled set of
   segments.  This can be applied to the Multi Protocol Label Switching
   (MPLS) data plane.  Entropy label (EL) is a technique used in MPLS to
   improve load balancing.  This document examines and describes how ELs
   are to be applied to source routed stacked tunnels.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-kini-mpls-spring-entropy-label/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-kini-mpls-spring-entropy-label-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-kini-mpls-spring-entropy-label-01

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls

Gregory Mirsky | 30 Sep 02:04 2014
Picon

draft-raza-mpls-oam-ipv6-rao

Dear All,

this is very useful work, thank you. I think that it will be useful to clarify the RFC 4379 in regard to use of Router Alert option in the IP header referencing specifically IPv6 Router Alert Option for MPLS OAM value. E.g. the first paragraph of the section 4.3 can be extended by:

In case of IPv4 control plane, the generic Option Value 0x0 [RFC2113] SHOULD be used. In case of IPv6 control plane, the allocated through this document IPv6 Router Alert Option value for MPLS OAM MUST be used.

Similarly, text of the first paragraph of the Section 4.5 of RFC 4379 may be updated to clarify use of the new RAO value in IPv6 case:

… then the IP header MUST contain the Router Alert IP option. In case of IPv4 control plane, the generic Option Value 0x0 [RFC2113] SHOULD be used. In case of IPv6 control plane, the allocated through this document IPv6 Router Alert Option value for MPLS OAM MUST be used. If the reply is sent …

 

 

                Regards,

                                Greg

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
The IESG | 29 Sep 13:54 2014
Picon

Last Call: <draft-ietf-mpls-lsp-ping-relay-reply-04.txt> (Relayed Echo Reply mechanism for LSP Ping) to Proposed Standard


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'Relayed Echo Reply mechanism for LSP Ping'
  <draft-ietf-mpls-lsp-ping-relay-reply-04.txt> as Proposed Standard

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 <at> ietf.org mailing lists by 2014-10-13. Exceptionally, comments may be
sent to iesg <at> ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   In some inter autonomous system (AS) and inter-area deployment
   scenarios for RFC 4379 "Label Switched Path (LSP) Ping and
   Traceroute", a replying LSR may not have the available route to the
   initiator, and the Echo Reply message sent to the initiator would be
   discarded resulting in false negatives or complete failure of
   operation of LSP Ping and Traceroute.  This document describes
   extensions to LSP Ping mechanism to enable the replying Label
   Switching Router (LSR) to have the capability to relay the Echo
   Response by a set of routable intermediate nodes to the initiator.
   This document updates RFC 4379.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-lsp-ping-relay-reply/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-lsp-ping-relay-reply/ballot/

The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/1945/
   http://datatracker.ietf.org/ipr/828/

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls

Loa Andersson | 29 Sep 12:55 2014
Picon

Routing Directorate QA review of draft-filsfils-spring-segment-routing-mpls

Hello,

I have been selected as the Routing Directorate QA reviewer for
draft-filsfils-spring-segment-routing-mpls-03.txt.

The Routing Directorate QA reviews are intended to be a support to
improve the quality of RTG Area documents as the pass through the IETF
process.

This is the QA review at the time of wg document adoption poll.

Document: draft-filsfils-spring-segment-routing-mpls-03.txt
Reviewer: Loa Andersson
Review Date: 2014-09-28
Working Group Adoption Poll end date: Oct 8, 2014
Intended Status: Standards Track

Please find the review at:

http://trac.tools.ietf.org/area/rtg/trac/wiki/QA%20review%20Sep%202014

/Loa

--

-- 

Loa Andersson                        email: loa <at> mail01.huawei.com
Senior MPLS Expert                          loa <at> pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls


Gmane