[prev in list] [next in list] [prev in thread] [next in thread]
List: ietf
Subject: RE: [PWE3] FW: LastCall: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated
From: Ross Callon <rcallon () juniper ! net>
Date: 2012-03-23 15:45:52
Message-ID: DF7F294AF4153D498141CBEFADB17704C70D0DB7B1 () EMBX01-WF ! jnpr ! net
[Download RAW message or body]
A current AD might take precedence over a past one, but back when I was on the IESG \
we twice had discussions of the use of RFC2119 keywords in informational track \
documents. Both times we fortunately came to the same conclusion - that it is fine to \
use RFC2119 keywords in informational (or experimental) RFCs.
Ross
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of \
Malcolm.BETTS@zte.com.cn
Sent: Friday, March 23, 2012 11:39 AM
To: t.petch
Cc: ietf@ietf.org
Subject: Re: [PWE3] FW: LastCall: \
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code \
Point for Use byITU-T Ethernet basedOAM) to Informational RFC
Tom,
I have no objections to using the RFC 2119 key words, I am not sure if that is \
appropriate in an informational track document, I expect that our AD will provide \
some guidance.
Regards,
Malcolm
"t.petch" <daedulus@btconnect.com>
23/03/2012 05:50 AM
To
"Loa Andersson" <loa@pi.nu>, <Malcolm.BETTS@zte.com.cn>
cc
<ietf@ietf.org>
Subject
Re: [PWE3] FW: LastCall: \
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel \
Code Point for Use byITU-T Ethernet basedOAM) to Informational RFC
Loa
The one point that jumps out at me is the proposed text
"Other message types should not be carried behind this code point."
or should that be
"Other message types SHOULD NOT be carried behind this code point."
which, in IETF-Land, is a bit different.
I prefer the latter.
Tom Petch
----- Original Message -----
From: "Loa Andersson" <loa@pi.nu>
To: <Malcolm.BETTS@zte.com.cn>
Cc: <ietf@ietf.org>
Sent: Friday, March 23, 2012 10:44 AM
Subject: Re: [PWE3] FW: LastCall:
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel
Code Point for Use byITU-T Ethernet basedOAM) to Informational RFC
> Malcolm,
>
> good that we are making some progress!
>
> On the experimental code point
> ------------------------------
>
> I doesn't seem appropriate to call out the fact that some commercial
> products has been using an experimental code point in production
> setting!
>
> On the remain (key) disagreements
> ---------------------------------
>
> I will let other people comment for now.
>
>
> /Loa
>
> On 2012-03-21 21:33, Malcolm.BETTS@zte.com.cn wrote:
> > Loa,
> >
> > Thank you for your comments and suggestions, please see in line below.
> >
> > Regards,
> >
> > Malcolm
> >
> >
> > ietf-bounces@ietf.org wrote on 12/03/2012 04:31:43 AM:
> >
> > > Loa Andersson <loa@pi.nu>
> > > Sent by: ietf-bounces@ietf.org
> > >
> > > 12/03/2012 04:31 AM
> > >
> > > To
> > >
> > > ietf@ietf.org
> > >
> > > cc
> > >
> > > Subject
> > >
> > > Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-
> > > point-03.txt>(Allocation of an Associated Channel Code Point for Use
> > > byITU-T Ethernet based OAM) to Informational RFC
> > >
> > > All,
> > >
> > > I've been asked to clarify thee comments in this mail, I done
> > > so by proposing new text to draft-betts-.
> > >
> > > I hope this helps.
> > >
> > >
> > > Title
> > > =====
> > >
> > > Comment: We want to assign a Associated Channel Type. The registry
> > > that it will be assigned from is "Pseudowire Associated Channel
> > > Types"; however RFC 5586, makes the Channel Types generic and I
> > > think the title should be changed as follows:
> > >
> > > OLD:
> > > Allocation of an Associated Channel Code Point for Use by ITU-T
> > > Ethernet based OAM
> > >
> > > NEW:
> > > Allocation of an Generic Associated Channel Type for ITU-T
> > > MPLS-TP OAM
> > >
> > > Note: Neither MPLS-TP or OAM are in the RFC Editors list of wellknown
> > > acronyms, therfore the title probably should be:
> > >
> > > NEW:
> > > Allocation of an Generic Associated Channel Type for ITU-T
> > > MPLS Transport Profile Operation, Maintenance and Administration.
> > >
> >
> > MB: No objection to this change
> >
> > >
> > > Introduction - first paragraph
> > > ==============================
> > >
> > > In the first paragraph of the introduction, there seems to be an
> > > oddity in the description of the role of the ietf-tp-oam-analysis
> > > document. Instead of:
> > >
> > > OLD
> > > "tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis], that
> > > are intended to meet the OAM functional requirements defined in
> > > [RFC5860]."
> > >
> > > NEW:
> > > "tools described by the IETF [I-D.ietf-mpls-tp-oam-analysis], which
> > > are used to meet the OAM functional requirements defined
> > > in [RFC5860]."
> >
> > MB: No objection to this change
> >
> > >
> > > Intrduction - second paragraph
> > > ==============================
> > >
> > > The next paragraph in describing G.8113.1, stumbles over the current
> > > vs anticipated future state of G.8113.1 and its relationship to
> > > its antecedents. I'm a bit un-certain about the correct terminology,
> > > but I think the following change would improve the document.
> > >
> > > OLD:
> > >
> > > The ITU-T has documented, in draft new Recommendation [G.8113.1], the
> > > use of Ethernet based OAM mechanisms, originally defined in [Y.1731],
> > > carried in the MPLS Generic Associated Channel (G-ACh). This approach
> > > requires the allocation of an ACH Type from the registry of ACH types
> > > maintained by IANA in order that the messages that will be described
> > > in [G.8113.1] can be identified by an implementation.
> > >
> > > NEW:
> > >
> > > "The ITU-T has Draft Recommendation [G.8113.1] documented MPLS OAM
> > > which as of this writing is undergoing the ITU-T Traditional
> > > Approval Process (TAP). This Recommendation builds upon Ethernet
> > > OAM as documented in [Y.1731]. The messages in [G.8113.1] are defined
> > > to be carried in a new Associated Channel Type in the MPLS Generaic
> > > Associated Channel (G-Ach). In order to carry these messages in an
> > > interoperable fashion, an Associated Channel Type from the IANA
> > > maintained registry "Pseudowire Associated Channel Types is to be
> > > used."
> >
> > MB: Since the draft will not be published as an RFC until after G.8113.1
> > is approved we can directly reference the approved Recommendation and I
> > suggest that we modify paragraph to:
> >
> >
> > ITU-T Recommendation [G.8113.1] documents MPLS OAM. This Recommendation
> > builds upon Ethernet OAM as documented in [Y.1731]. The messages in
> > [G.8113.1] are defined to be carried in a new Associated Channel Type in
> > the MPLS Generaic Associated Channel (G-Ach). In order to carry these
> > messages in an interoperable fashion, an Associated Channel Type from
> > the IANA maintained registry "Pseudowire Associated Channel Types is to
> > be used."
> >
> >
> > >
> > > Note there are confusion around some of the Associated Channel
> > > acronyms that are refledted in this document.
> > >
> > > ACh is Associated Channel
> > > ACH is Associated Chamnnel Header
> > > G-ACh is Generic Associated Channel
> > >
> > > "ACH Type" is not used anywhere in IETF documents; we talk about
> > > Associated Channel Type or Generic Associated Channel Type
> > > (G-ACh Type).
> >
> > MB: Thank you, I will fix this.
> >
> > >
> > > Introduction - third paragraph
> > > ==============================
> > >
> > > In the third paragraph, there seems to be an unnecessary reference
> > > to experimental types. When asking for a code point for a standard,
> > > it is not helped to bring up experimental code space. Can we remove
> > > the text reading:
> > >
> > > OLD:
> > > "without continuing to resorting to the use of an experimental
> > > ACH Type,"
> > >
> > > NEW
> > > -
> >
> > MB: I do not agree with the deletion of this text, these existing
> > deployments, and the desire to migrate to an allocated code point, are
> > part of the rational for requesting the code point.
> >
> > >
> > >
> > > Section 2 - first paragraph
> > > ===========================
> > >
> > >
> > >
> > > In section 2, the first sentence refers to Ethernet based OAM
> > > messages. As far as I know, the messages in G.8113.1 are either
> > > MPLS-TP OAM messages, or they are simply the OAM messages defined
> > > in G.8113.1. The simplest path to clarity would seem to be to
> > > replace "Ethernet based OAM messages" in that sentence with
> > > "messages".
> > >
> > > The second sentence of that paragraph does not seem to say anything
> > > we need to say. Can we remove it?
> > >
> > > OLD:
> > >
> > > The code point allocated by this document is intended to be used only
> > > for Ethernet based OAM messages, defined in the ITU-T Recommendation
> > > [G.8113.1], carried in the G-ACh . These Ethernet based OAM messages
> > > and procedures, address the OAM functional requirements defined in
> > > [RFC5860]. Other message types should not be carried behind this code
> > > point.
> > >
> > > NEW:
> > >
> > > The code point allocated by this document is intended to be used
> > > only for OAM messages, defined in the ITU-T Recommendation
> > > [G.8113.1], carried in the G-ACh . Other message types should not
> > > be carried behind this Associated Channel Type.
> >
> >
> > MB: I do not agree with this proposed change. Other comments request
> > that the restriction on the applicability of the code point is
> > strengthened so I propose the following:
> >
> > The code point allocated by this document should only be used for OAM
> > messages, defined in the ITU-T Recommendation [G.8113.1], carried in the
> > G-ACh. The messages and procedures carried behind this code point, are
> > restricted to only those that the address the OAM functional
> > requirements defined in [RFC5860]. Other message types should not be
> > carried behind this code point.
> >
> >
> > >
> > > Section 2 - second paragraph
> > > ============================
> > >
> > > A matter of some clarity, can we change this paragrap like this:
> > >
> > > OLD:
> > > This code point may be used on any transport construct that uses
> > > the G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs.
> > >
> > > NEW:
> > >
> > > The Generic Associated Channel Type assigned by this
> > > document may be used on any transport construct that uses the
> > > G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs as specified
> > > by G.8113.1.
> >
> > MB: No objection to this change.
> >
> > >
> > >
> > > Section 2 - third paragraph
> > > ===========================
> > >
> > > With regard to revisions, which is what I think the third paragraph
> > > is about, I am not clear what you are trying to say. A code point
> > > allocation must point to a stable referent. If the desired referent
> > > changes, then process needs to be followed to make sure that the IANA
> > > is updated in accordance with IETF procedures. Hence, I am left to
> > > the conclusion that the third paragraph is actually asking for
> > > something we can not do. Can we remove that?
> > >
> > > OLD:
> > > All ITU-T Recommendations are subject to revisions. Therefore, the
> > > code point allocated by this document may be used for future versions
> > > of [G.8113.1].
> > >
> > > NEW:
> > > -
> > >
> > >
> >
> > MB: I do not agree with the removal of this text:
> >
> > The intention of this statement is to bring to the attention of the IETF
> > the normal practice in the ITU of developing amendments to
> > Recommendations to fully meet the functional requirements (e.g. adding
> > pro-active loss measurement). Normally any reference to ITU-T Rec
> > G.8113.1 will automatically be directed to the current version
> > (including any amendments).
> >
> > Only those interfaces that support G.8113.1 OAM will act on these OAM
> > messages, any interface that does not support this G-ACh type will
> > discard these OAM messages as defined in RFC5586.
> >
> > Restricting the application of the code point to a specific version of
> > Recommendation G.8113.1 would require the ITU to deviate from its normal
> > process for enhancing Recommendations and would put the IETF back into
> > the discussion for approval.
> >
> >
> >
> > > ---------------snip
> >
> >
> > >
> > > Loa Andersson email: loa.andersson@ericsson.com
> > > Sr Strategy and Standards Manager loa@pi.nu
> > > Ericsson Inc phone: +46 10 717 52 13
> > > +46 767 72 92 13
> > > _______________________________________________
> > > Ietf mailing list
> > > Ietf@ietf.org
> > > https://www.ietf.org/mailman/listinfo/ietf
> > >
>
> --
>
>
> Loa Andersson email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager loa@pi.nu
> Ericsson Inc phone: +46 10 717 52 13
> +46 767 72 92 13
>
>
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div \
class=WordSection1><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>A current \
AD might take precedence over a past one, but back when I was on the IESG we twice \
had discussions of the use of RFC2119 keywords in informational track documents. Both \
times we fortunately came to the same conclusion – that it is fine to use \
RFC2119 keywords in informational (or experimental) RFCs. <o:p></o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ross<o:p></o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div \
style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p \
class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ietf-bounces@ietf.org \
[mailto:ietf-bounces@ietf.org] <b>On Behalf Of \
</b>Malcolm.BETTS@zte.com.cn<br><b>Sent:</b> Friday, March 23, 2012 11:39 \
AM<br><b>To:</b> t.petch<br><b>Cc:</b> ietf@ietf.org<br><b>Subject:</b> Re: [PWE3] \
FW: LastCall: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an \
Associated Channel Code Point for Use byITU-T Ethernet basedOAM) to Informational \
RFC<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p \
class=MsoNormal style='margin-bottom:12.0pt'><span \
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Tom,</span> <br><br><span \
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I have no objections to \
using the RFC 2119 key words, I am not sure if that is appropriate in an \
informational track document, I expect that our AD will provide some guidance.</span> \
<br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Regards,</span> \
<br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Malcolm</span> \
<br><br><br><o:p></o:p></p><table class=MsoNormalTable border=0 cellpadding=0 \
width="100%" style='width:100.0%'><tr><td width="36%" valign=top \
style='width:36.0%;padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><b><span \
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"t.petch" \
<daedulus@btconnect.com></span></b><span \
style='font-size:7.5pt;font-family:"Arial","sans-serif"'> \
</span><o:p></o:p></p><p><span \
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>23/03/2012 05:50 AM</span> \
<o:p></o:p></p></td><td width="63%" valign=top style='width:63.0%;padding:.75pt .75pt \
.75pt .75pt'><table class=MsoNormalTable border=0 cellpadding=0 width="100%" \
style='width:100.0%'><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p \
class=MsoNormal align=right style='text-align:right'><span \
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>To</span><o:p></o:p></p></td><td \
valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span \
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Loa Andersson" \
<loa@pi.nu>, <Malcolm.BETTS@zte.com.cn></span> \
<o:p></o:p></p></td></tr><tr><td valign=top style='padding:.75pt .75pt .75pt \
.75pt'><p class=MsoNormal align=right style='text-align:right'><span \
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>cc</span><o:p></o:p></p></td><td \
valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span \
style='font-size:7.5pt;font-family:"Arial","sans-serif"'><ietf@ietf.org></span> \
<o:p></o:p></p></td></tr><tr><td valign=top style='padding:.75pt .75pt .75pt \
.75pt'><p class=MsoNormal align=right style='text-align:right'><span \
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Subject</span><o:p></o:p></p></td><td \
valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span \
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Re: [PWE3] FW: LastCall: \
\
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof \
an Associated Channel Code Point for Use byITU-T Ethernet \
basedOAM) to Informational \
RFC</span><o:p></o:p></p></td></tr></table><p \
class=MsoNormal><o:p> </o:p></p><table class=MsoNormalTable border=0 \
cellpadding=0><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'></td><td \
valign=top style='padding:.75pt .75pt .75pt \
.75pt'></td></tr></table></td></tr></table><p class=MsoNormal \
style='margin-bottom:12.0pt'><br><br><br><tt><span \
style='font-size:10.0pt'>Loa</span></tt><span \
style='font-size:10.0pt;font-family:"Courier New"'><br><br><tt>The one point that \
jumps out at me is the proposed text</tt><br><tt>"Other message types should not \
be carried behind this code point."</tt><br><tt>or should that \
be</tt><br><tt>"Other message types SHOULD NOT be carried behind this code \
point."</tt><br><tt>which, in IETF-Land, is a bit different.</tt><br><br><tt>I \
prefer the latter.</tt><br><br><tt>Tom Petch</tt><br><br><br><tt>----- Original \
Message -----</tt><br><tt>From: "Loa Andersson" \
<loa@pi.nu></tt><br><tt>To: <Malcolm.BETTS@zte.com.cn></tt><br><tt>Cc: \
<ietf@ietf.org></tt><br><tt>Sent: Friday, March 23, 2012 10:44 \
AM</tt><br><tt>Subject: Re: [PWE3] FW: \
LastCall:</tt><br><tt><draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof \
an Associated Channel</tt><br><tt>Code Point for Use byITU-T Ethernet basedOAM) to \
Informational RFC</tt><br><br><br><tt>> Malcolm,</tt><br><tt>></tt><br><tt>> \
good that we are making some progress!</tt><br><tt>></tt><br><tt>> On the \
experimental code point</tt><br><tt>> \
------------------------------</tt><br><tt>></tt><br><tt>> I doesn't seem \
appropriate to call out the fact that some commercial</tt><br><tt>> products has \
been using an experimental code point in production</tt><br><tt>> \
setting!</tt><br><tt>></tt><br><tt>> On the remain (key) \
disagreements</tt><br><tt>> \
---------------------------------</tt><br><tt>></tt><br><tt>> I will let other \
people comment for now.</tt><br><tt>></tt><br><tt>></tt><br><tt>> \
/Loa</tt><br><tt>></tt><br><tt>> On 2012-03-21 21:33, Malcolm.BETTS@zte.com.cn \
wrote:</tt><br><tt>> > Loa,</tt><br><tt>> ></tt><br><tt>> > Thank \
you for your comments and suggestions, please see in line below.</tt><br><tt>> \
></tt><br><tt>> > Regards,</tt><br><tt>> ></tt><br><tt>> > \
Malcolm</tt><br><tt>> ></tt><br><tt>> ></tt><br><tt>> > \
ietf-bounces@ietf.org wrote on 12/03/2012 04:31:43 AM:</tt><br><tt>> \
></tt><br><tt>> > > Loa Andersson \
<loa@pi.nu></tt><br><tt>> > > Sent by: \
ietf-bounces@ietf.org</tt><br><tt>> > ></tt><br><tt>> > \
> 12/03/2012 04:31 AM</tt><br><tt>> > ></tt><br><tt>> > \
> To</tt><br><tt>> > ></tt><br><tt>> > > \
ietf@ietf.org</tt><br><tt>> > ></tt><br><tt>> > > \
cc</tt><br><tt>> > ></tt><br><tt>> > > \
Subject</tt><br><tt>> > ></tt><br><tt>> > > Re: [PWE3] \
FW: Last Call: <draft-betts-itu-oam-ach-code-</tt><br><tt>> > > \
point-03.txt>(Allocation of an Associated Channel Code Point for \
Use</tt><br><tt>> > > byITU-T Ethernet based OAM) to Informational \
RFC</tt><br><tt>> > ></tt><br><tt>> > > \
All,</tt><br><tt>> > ></tt><br><tt>> > > I've been \
asked to clarify thee comments in this mail, I done</tt><br><tt>> > > \
so by proposing new text to draft-betts-.</tt><br><tt>> > \
></tt><br><tt>> > > I hope this helps.</tt><br><tt>> > \
></tt><br><tt>> > ></tt><br><tt>> > > \
Title</tt><br><tt>> > > =====</tt><br><tt>> > \
></tt><br><tt>> > > Comment: We want to assign a Associated \
Channel Type. The registry</tt><br><tt>> > > that it will be assigned \
from is "Pseudowire Associated Channel</tt><br><tt>> > > \
Types"; however RFC 5586, makes the Channel Types generic and I</tt><br><tt>> \
> > think the title should be changed as follows:</tt><br><tt>> > \
></tt><br><tt>> > > OLD:</tt><br><tt>> > > \
Allocation of an Associated Channel Code Point for Use by ITU-T</tt><br><tt>> > \
> Ethernet based OAM</tt><br><tt>> > ></tt><br><tt>> > \
> NEW:</tt><br><tt>> > > Allocation of an Generic Associated \
Channel Type for ITU-T</tt><br><tt>> > > MPLS-TP OAM</tt><br><tt>> \
> ></tt><br><tt>> > > Note: Neither MPLS-TP or OAM are in \
the RFC Editors list of wellknown</tt><br><tt>> > > acronyms, therfore \
the title probably should be:</tt><br><tt>> > ></tt><br><tt>> > \
> NEW:</tt><br><tt>> > > Allocation of an Generic Associated \
Channel Type for ITU-T</tt><br><tt>> > > MPLS Transport Profile \
Operation, Maintenance and Administration.</tt><br><tt>> > \
></tt><br><tt>> ></tt><br><tt>> > MB: No objection to this \
change</tt><br><tt>> ></tt><br><tt>> > ></tt><br><tt>> > \
> Introduction - first paragraph</tt><br><tt>> > > \
==============================</tt><br><tt>> > ></tt><br><tt>> > \
> In the first paragraph of the introduction, there seems to be \
an</tt><br><tt>> > > oddity in the description of the role of the \
ietf-tp-oam-analysis</tt><br><tt>> > > document. Instead \
of:</tt><br><tt>> > ></tt><br><tt>> > > \
OLD</tt><br><tt>> > > "tools defined by the IETF \
[I-D.ietf-mpls-tp-oam-analysis], that</tt><br><tt>> > > are intended \
to meet the OAM functional requirements defined in</tt><br><tt>> > > \
[RFC5860]."</tt><br><tt>> > ></tt><br><tt>> > > \
NEW:</tt><br><tt>> > > "tools described by the IETF \
[I-D.ietf-mpls-tp-oam-analysis], which</tt><br><tt>> > > are used to \
meet the OAM functional requirements defined</tt><br><tt>> > > in \
[RFC5860]."</tt><br><tt>> ></tt><br><tt>> > MB: No objection to this \
change</tt><br><tt>> ></tt><br><tt>> > ></tt><br><tt>> > \
> Intrduction - second paragraph</tt><br><tt>> > > \
==============================</tt><br><tt>> > ></tt><br><tt>> > \
> The next paragraph in describing G.8113.1, stumbles over the \
current</tt><br><tt>> > > vs anticipated future state of G.8113.1 and \
its relationship to</tt><br><tt>> > > its antecedents. I'm a bit \
un-certain about the correct terminology,</tt><br><tt>> > > but I \
think the following change would improve the document.</tt><br><tt>> > \
></tt><br><tt>> > > OLD:</tt><br><tt>> > \
></tt><br><tt>> > > The ITU-T has documented, in draft new \
Recommendation [G.8113.1], the</tt><br><tt>> > > use of Ethernet based \
OAM mechanisms, originally defined in [Y.1731],</tt><br><tt>> > > \
carried in the MPLS Generic Associated Channel (G-ACh). This \
approach</tt><br><tt>> > > requires the allocation of an ACH Type from \
the registry of ACH types</tt><br><tt>> > > maintained by IANA in \
order that the messages that will be described</tt><br><tt>> > > in \
[G.8113.1] can be identified by an implementation.</tt><br><tt>> > \
></tt><br><tt>> > > NEW:</tt><br><tt>> > \
></tt><br><tt>> > > "The ITU-T has Draft Recommendation \
[G.8113.1] documented MPLS OAM</tt><br><tt>> > > which as of this \
writing is undergoing the ITU-T Traditional</tt><br><tt>> > > Approval \
Process (TAP). This Recommendation builds upon Ethernet</tt><br><tt>> > \
> OAM as documented in [Y.1731]. The messages in [G.8113.1] are \
defined</tt><br><tt>> > > to be carried in a new Associated Channel \
Type in the MPLS Generaic</tt><br><tt>> > > Associated Channel \
(G-Ach). In order to carry these messages in an</tt><br><tt>> > > \
interoperable fashion, an Associated Channel Type from the IANA</tt><br><tt>> > \
> maintained registry "Pseudowire Associated Channel Types is to \
be</tt><br><tt>> > > used."</tt><br><tt>> \
></tt><br><tt>> > MB: Since the draft will not be published as an RFC until \
after G.8113.1</tt><br><tt>> > is approved we can directly reference the \
approved Recommendation and I</tt><br><tt>> > suggest that we modify paragraph \
to:</tt><br><tt>> ></tt><br><tt>> ></tt><br><tt>> > ITU-T \
Recommendation [G.8113.1] documents MPLS OAM. This Recommendation</tt><br><tt>> \
> builds upon Ethernet OAM as documented in [Y.1731]. The messages \
in</tt><br><tt>> > [G.8113.1] are defined to be carried in a new Associated \
Channel Type in</tt><br><tt>> > the MPLS Generaic Associated Channel (G-Ach). \
In order to carry these</tt><br><tt>> > messages in an interoperable fashion, \
an Associated Channel Type from</tt><br><tt>> > the IANA maintained registry \
"Pseudowire Associated Channel Types is to</tt><br><tt>> > be \
used."</tt><br><tt>> ></tt><br><tt>> ></tt><br><tt>> > \
></tt><br><tt>> > > Note there are confusion around some of \
the Associated Channel</tt><br><tt>> > > acronyms that are refledted \
in this document.</tt><br><tt>> > ></tt><br><tt>> > > \
ACh is Associated Channel</tt><br><tt>> > > ACH is Associated Chamnnel \
Header</tt><br><tt>> > > G-ACh is Generic Associated \
Channel</tt><br><tt>> > ></tt><br><tt>> > > "ACH \
Type" is not used anywhere in IETF documents; we talk about</tt><br><tt>> \
> > Associated Channel Type or Generic Associated Channel \
Type</tt><br><tt>> > > (G-ACh Type).</tt><br><tt>> \
></tt><br><tt>> > MB: Thank you, I will fix this.</tt><br><tt>> \
></tt><br><tt>> > ></tt><br><tt>> > > Introduction - \
third paragraph</tt><br><tt>> > > \
==============================</tt><br><tt>> > ></tt><br><tt>> > \
> In the third paragraph, there seems to be an unnecessary \
reference</tt><br><tt>> > > to experimental types. When asking for a \
code point for a standard,</tt><br><tt>> > > it is not helped to bring \
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic