Re: [mpls] working group last call on draft-ietf-mpls-tp-requirements-08.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mpls] working group last call on draft-ietf-mpls-tp-requirements-08.txt
Colleagues,
All comments received during this WG LC have been resolved and a new version
of the draft is available here:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-requirements-09.txt
I have attached an HTML document detailing the received WG LC comments and
the resolutions.
The document is also available here:
http://www.niven-jenkins.co.uk/MPLS-TP/MPLS-TPReqs2ndWGLC.htm
Ben
On 18/05/2009 16:31, "Loa Andersson" <loa at pi.nu> wrote:
> Working Group(s),
>
> this is to start a two week working group last call on
> http://tools.ietf.org/id/draft-ietf-mpls-tp-requirements-08.txt
>
> The document has been updated to address all comments received in the
> earlier working group last call and comments received from the
> ITU-T ad hoc team on MPLS-TP.
>
> Please send your comments to the mpls-tp mailing list.
>
> The working group last call ends on June 1st.
>
> /Loa
<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:css="http://macVmlSchemaUri"; xmlns="http://www.w3.org/TR/REC-html40";>
<head>
<meta name=Title content="">
<meta name=Keywords content="">
<meta http-equiv=Content-Type content="text/html; charset=macintosh">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 2008">
<meta name=Originator content="Microsoft Word 2008">
<link rel=File-List
href="MPLS-TP%20Requirements%20comment%20resolution%2008%20to%2009_01_files/filelist.xml">
<!--[if gte mso 9]><xml>
<o:DocumentProperties>
<o:Author>Benjamin Niven-Jenkins</o:Author>
<o:Template>Normal.dotm</o:Template>
<o:LastAuthor>Benjamin Niven-Jenkins</o:LastAuthor>
<o:Revision>2</o:Revision>
<o:TotalTime>24</o:TotalTime>
<o:Created>2009-06-22T19:47:00Z</o:Created>
<o:LastSaved>2009-06-22T19:47:00Z</o:LastSaved>
<o:Pages>2</o:Pages>
<o:Words>755</o:Words>
<o:Characters>4307</o:Characters>
<o:Lines>35</o:Lines>
<o:Paragraphs>8</o:Paragraphs>
<o:CharactersWithSpaces>5289</o:CharactersWithSpaces>
<o:Version>12.0</o:Version>
</o:DocumentProperties>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>125</w:Zoom>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:TrackMoves>false</w:TrackMoves>
<w:TrackFormatting/>
<w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>
<w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>
<w:UseMarginsForDrawingGridOrigin/>
<w:ValidateAgainstSchemas>false</w:ValidateAgainstSchemas>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotUnderlineInvalidXML/>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:UseNormalStyleForList/>
<w:DontUseIndentAsNumberingTabStop/>
<w:DontGrowAutofit/>
<w:FELineBreak11/>
<w:WW11IndentRules/>
<w:DontAutofitConstrainedTables/>
<w:AutofitLikeWW11/>
<w:HangulWidthLikeWW11/>
</w:Compatibility>
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" LatentStyleCount="276">
</w:LatentStyles>
</xml><![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin-top:0cm;
margin-right:0cm;
margin-bottom:10.0pt;
margin-left:0cm;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-ascii-font-family:Cambria;
mso-fareast-font-family:Cambria;
mso-hansi-font-family:Cambria;
mso-bidi-font-family:"Times New Roman";}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 122.95pt 72.0pt 90.0pt;
mso-header-margin:35.4pt;
mso-footer-margin:35.4pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ascii-font-family:Cambria;
mso-hansi-font-family:Cambria;}
</style>
<![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050"/>
</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-GB style='tab-interval:36.0pt'>
<div class=Section1>
<p class=MsoNormal align=center style='text-align:center'><b style='mso-bidi-font-weight:
normal'>Comment resolutions from 2<sup>nd</sup> WG Last Call on MPLS-TP
Requirements (draft-ietf-mpls-tp-requirements-08)<o:p></o:p></b></p>
<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight:
normal'><o:p> </o:p></b></p>
<p class=MsoNormal style='text-align:justify'>All changes noted below are
reflected in version -09 that is now available in the I-D repository.</p>
<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight:
normal'><o:p> </o:p></b></p>
<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight:
normal'>Key<o:p></o:p></b></p>
<p class=MsoNormal style='text-align:justify'>Original comment</p>
<p class=MsoNormal style='text-align:justify'><span style='color:blue'>Secondary
commenter<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span class=SpellE><span
style='color:green'>BPNÕs</span></span><span style='color:green'> response<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight:
normal'><o:p> </o:p></b></p>
<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight:
normal'>ITU-T Liaison from Q9, 10, 12, 14 SG15<o:p></o:p></b></p>
<p class=MsoNormal style='text-align:justify'>1) Requirement 59: Item c should
be moved from requirement 59 to a separate requirement since it is not part of
the SLA</p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>I have
moved requirement 59 C to be a <span class=GramE>stand alone</span> requirement
in the same section (Recovery requirements).<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'>2) Requirement 70:<span
style="mso-spacerun: yes"> </span>Should be moved to the restoration
section (2.8.2). Currently, it is under the protection section.</p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>I have
moved requirement 70 to the restoration section (2.8.2). I also moved the
protection requirement related to reversion to the protection section (2.8.1.1)
and deleted the reversion section as it now contains no requirements.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'>3) Requirement 66 D: The term
"backtracking" should be <span class=GramE>defined,</span> this
should be included in the <span class=SpellE>rosetta</span> draft. </p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>Reworded
requirement 66 D to the following as per Stewart BryantÕs suggestion to the
MPLS-TP ITU and IETF mailing lists:<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>The <span
class=GramE>action of protection switching MUST NOT cause</span> the user data
to enter an uncontrolled loop. The protection switching system MAY cause
traffic to pass over a given link more than once, but it must do so in a
controlled way such that uncontrolled loops do not form.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'>4) Ring protection section <span
class=GramE>2.8.6.1 :</span> </p>
<p class=MsoNormal style='text-align:justify'>The paragraph below requirement
e, replace the words in "this section" with Òsection 2.8.6.1"
and replace the words "expressed above" by "requirements
expressed in sections 2.8 up to section 2.8.6.1"</p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>I have
made the changes you suggested, the paragraph now reads:<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.0cm;text-align:justify'><span
style='color:green'>It may be observed that the requirements in Section 2.8.6.1
are fully compatible with the generic requirements expressed in Section 2.8
through Section 2.8.6 inclusive, and that no requirements that are specific to
ring topologies have been identified.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'>5) Requirement 107B: Replace the
current text with following:</p>
<p class=MsoNormal style='text-align:justify'>It SHOULD protect against
multiple failures</p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>I have
replaced the current text with your suggested text.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><o:p> </o:p></p>
<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight:
normal'>Private comments from <span class=SpellE>Italo</span> <span
class=SpellE>Busi</span>:<o:p></o:p></b></p>
<p class=MsoNormal style='text-align:justify'>1) In the last line of section 1
(just before the heading of section 1.1), there is still the text "control
plane for dynamic configuration"</p>
<p class=MsoNormal style='text-align:justify'>My understanding from the MEAD
call was that, to avoid confusion regarding what do we mean by control plane in
this document, we have agree to add the definition of control plane (that is
fine) and to remove <span class=SpellE>remove</span> "for dynamic configuration"
in the text.</p>
<p class=MsoNormal style='text-align:justify'>Have I missed something?</p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>No. I
removed reference to "control plane for dynamic configuration" from
one of the requirements but overlooked it in section 1. I have removed it from
section 1 as well.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'>2) It is my understanding that
requirements 9-12 have been moved from section 2.3 to section 2.1.</p>
<p class=MsoNormal style='text-align:justify'>I do not remember this discussion
but I am fine with this change.</p>
<p class=MsoNormal style='text-align:justify'>However, for consistency, I think
that also requirement 40 should be moved from 2.3 to 2.1.</p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>There
was some discussion of it in the context of the wording on the mailing list and
I judged consensus of that discussion to also be to move them to section 2.1. I
have moved requirement 40 to section 2.1.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'>3) My understanding from the MEAD
call we agreed that that requirement 47 should be moved from section 2.4 to
section 2.3 as it is a data plane and not a control plane requirement.</p>
<p class=MsoNormal style='text-align:justify'>Have I missed something?</p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>I must
have missed that, I have moved requirement 47 to section 2.3.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight:
normal'>Comments on MPLS-TP list conversation between <span class=SpellE>Yaacov</span>
Weingarten & <span style='color:blue'>Adrian <span class=SpellE>Farrel</span></span><o:p></o:p></b></p>
<p class=MsoNormal style='text-align:justify'>1. <span class=SpellE>Req</span>
27-C: MPLS-TP MUST support rings of at least 16 nodes...MPLS-TP SHOULD support
rings with more than 16 nodes.</p>
<p class=MsoNormal style='text-align:justify'>So is it a MUST or a SHOULD?<span
style="mso-spacerun: yes"> </span>Isn't "at least 16" and
"more than 16" almost equivalent (except for exactly 16)?</p>
<p class=MsoNormal style='text-align:justify'><span style='color:blue'>Right <o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='color:blue'>MUST support
0-16 <o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='color:blue'>SHOULD
support 17...<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='color:blue'>That is
what the text says.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='color:blue'>É<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='color:blue'>I think
this is good material for discussion in Sophia <span class=SpellE>Antipolis</span>.<br>
AFAIK, the<br>
precise
wording came from the ITU-T meeting in Geneva.<br>
We should, therefore, get
signoff from ITU-T folk when we change it.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>Consensus
in Sophia was that ITU-T did not require any changes to the text.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'>2) In <span class=SpellE>Req</span>
100 & 102 - What is the difference between "Recovery mechanisms"
and "Recovery techniques"? Why is the first a MUST and the second a
SHOULD?</p>
<p class=MsoNormal style='text-align:justify'><span style='color:blue'>Good
catch.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='color:blue'>Only one
of the two requirements should remain.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span class=GramE><span
style='color:blue'>But which?</span></span><span style='color:blue'><o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>I
removed Requirement 100.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'>3) Finally, just a little
spelling note: in <span class=SpellE>Req</span> 32-A: change "bellow"
to "below".</p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>Corrected.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><o:p> </o:p></p>
<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight:
normal'>Comment from <span class=SpellE>Jia</span> He<o:p></o:p></b></p>
<p class=MsoNormal style='text-align:justify'>One minor comment about
Requirement 21</p>
<p class=MsoNormal style='text-align:justify'>"<span class=GramE>21<span
style="mso-spacerun: yes"> </span>A</span> solution MUST be defined to
support dynamic provisioning and<span style="mso-spacerun:
yes"> </span>restoration of MPLS-TP
transport paths via a control plane."</p>
<p class=MsoNormal style='text-align:justify'>I'm wondering whether this is
better to be included in Section 2.4, which focuses on control plane
requirements, rather than in Section 2.1(General requirements).</p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>Agreement
offline the MPLS-TP list to leave requirement 21 in section 2.1 but to move it
directly under the requirement on static provisioning.<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><o:p> </o:p></p>
<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight:
normal'>Private comments from Loa <span class=SpellE>Andersson</span><o:p></o:p></b></p>
<p class=MsoNormal><span class=GramE>two</span> nits - ATM and RAN is only used
in the abbreviations section.</p>
<p class=MsoNormal style='text-align:justify'><span style='color:green'>I have
removed RAN from the abbreviations section. I didnÕt remove ATM as it is used
in requirement 31. I also removed <span class=GramE>ASTN</span> as it is no
longer used.<o:p></o:p></span></p>
</div>
</body>
</html>
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.
