All,
It is up to the sponsoring AD to decide on the review process. The mpls wg
co-chairs will discuss this this week, and we'll let the AD know what we think.
With my wg chair hat off I have to say that more review is better than less.
I assume that the will inform us of the review process as
Shouldn't this document be referred to MPLS WG and PWE3 WG so that we
can discuss the merits and demerits of allocating yet another request
for the code point...
The name of the document suggests it has to do with the official ITU
request for a code point ..but nowhere in the document does it ac
ext t.petch [mailto:daedu...@btconnect.com]
Sent: Saturday, December 03, 2011 7:44 PM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbry...@cisco.com; Adrian
Farrel
Cc: iesg; ietf
Subject: Re: Request to publish
draft-betts-itu-oam-ach-code-point-01.txt
- Original Message -
From: "Sprec
tworks
-Original Message-
From: ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of
ext Huub helvoort
Sent: Thursday, December 01, 2011 11:17 PM
To: Adrian Farrel
Cc: draft-betts-itu-oam-ach-code-po...@tools.ietf.org; The IESG;
Ietf@ietf.org
Subject: Request to publish draft-betts-i
PM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbry...@cisco.com; Adrian
Farrel
Cc: iesg; ietf
Subject: Re: Request to publish
draft-betts-itu-oam-ach-code-point-01.txt
- Original Message -
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)"
To: ; "Adrian Farrel"
Cc:
raft-betts-itu-oam-ach-code-po...@tools.ietf.org; i...@ietf.org;
> Ietf@ietf.org
> Subject: Re: Request to publish
> draft-betts-itu-oam-ach-code-point-01.txt
>
> Adrian
>
> "It is the opinion of the document shepherd that discussion of
> this document on the worki
tu-oam-ach-code-po...@tools.ietf.org; The IESG; Ietf@ietf.org
> Subject: Request to publish draft-betts-itu-oam-ach-code-point-01.txt
>
> Document Writeup for draft-betts-itu-oam-ach-code-point-01.txt
>
> As required by RFC-to-be draft-iesg-sponsoring-guidelines, this is the
&g
6:07 PM
To: stbry...@cisco.com; Adrian Farrel
Cc: draft-betts-itu-oam-ach-code-po...@tools.ietf.org; i...@ietf.org;
Ietf@ietf.org
Subject: RE: Request to publish
draft-betts-itu-oam-ach-code-point-01.txt
Hi,
I fully support Stewart!
G.8113.1 proposes a OAM solution for MPLS-TP networks.
It use
: Adrian Farrel
Cc: draft-betts-itu-oam-ach-code-po...@tools.ietf.org; i...@ietf.org;
Ietf@ietf.org
Subject: Re: Request to publish
draft-betts-itu-oam-ach-code-point-01.txt
Adrian
"It is the opinion of the document shepherd that discussion of
this document on the working group lists would
oun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of
John E Drake
Sent: Friday, December 02, 2011 7:17 AM
To: Huub helvoort; Adrian Farrel
Cc: itu-t-liais...@iab.org;
draft-betts-itu-oam-ach-code-po...@tools.ietf.org; The IESG;
Ietf@ietf.org
Subject: RE: Request to publish
draft-betts-itu-oam-ach-co
On 02/12/2011 13:29, t.petch wrote:
Original Message -
From: "Thomas Nadeau"
To: "Huub helvoort"
Cc: "Adrian Farrel";
; "The IESG"
;
Sent: Friday, December 02, 2011 2:40 PM
I disagree with the document shepherd's evaluation of this document. This
document sets out to
standardize an ad
Original Message -
From: "Thomas Nadeau"
To: "Huub helvoort"
Cc: "Adrian Farrel" ;
; "The IESG"
;
Sent: Friday, December 02, 2011 2:40 PM
>
> I disagree with the document shepherd's evaluation of this document. This
document sets out to
> standardize an additional code point to support
I disagree with the document shepherd's evaluation of this document.
This document sets out to
standardize an additional code point to support a type of OAM for MPLS, and as
such the MPLS WG must
review the document for technical correctness. As far as I understand things,
all MPLS d
--On Friday, December 02, 2011 04:17 -0800 John E Drake
wrote:
> Huub,
>
> In your email, below, you state:
>
> "This protocol has been defined in the ITU-T and should not be
> considered to be a MPLS protocol and therefore should not
> subject to the provisions of RFC 4929."
>...
> Doesn't t
drian Farrel
> Cc: draft-betts-itu-oam-ach-code-po...@tools.ietf.org; The IESG;
> Ietf@ietf.org
> Subject: Request to publish draft-betts-itu-oam-ach-code-point-01.txt
>
> Document Writeup for draft-betts-itu-oam-ach-code-point-01.txt
>
> As required by RFC-to-be draft-iesg
Adrian
"It is the opinion of the document shepherd that discussion of
this document on the working group lists would be a distraction
from the technical protocol work that the working groups
need to do."
I disagree with the document shepherd in his evaluation.
The draft clearly sets out to enab
Document Writeup for draft-betts-itu-oam-ach-code-point-01.txt
As required by RFC-to-be draft-iesg-sponsoring-guidelines, this is the
current template for the Document Shepherd Write-Up for individual
submissions via the IESG.
Changes are expected over time. This version is dated February 5, 2007
17 matches
Mail list logo