[prev in list] [next in list] [prev in thread] [next in thread]
List: mpls
Subject: Re: [mpls] Extended: working group last call on draft-ietf-mpls-ipv6-pw-lsp-ping-01
From: "Carlos Pignataro (cpignata)" <cpignata () cisco ! com>
Date: 2012-09-25 18:16:11
Message-ID: 90517418-4933-45A1-8C8D-E550982F884F () cisco ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Kireeti,
On Sep 25, 2012, at 2:11 PM, Kireeti Kompella wrote:
> Hi Carlos,
>
> On Sep 25, 2012, at 10:47 , Carlos Pignataro (cpignata) <cpignata@cisco.com> wrote:
>
> > Kireeti,
> >
> > Thanks for the comments! Certainly useful. Ack to both points, please see more \
> > details inline.
>
> Cool!
>
> > On Sep 25, 2012, at 12:54 PM, Kireeti Kompella wrote:
> >
> > > No objection (sorry, Loa, I know you were looking for positive comments). \
> > > However, some hopefully useful comments:
> > >
> > > 2. IPv4 Pseudowire Sub-TLVs
> > >
> > > This document updates Section 3.2 and Sections 3.2.8 through 3.2.10
> > > of [RFC4379] as follows and as indicated in Section 4 and Section 6.
> > > This is done to avoid any potential ambiguity, confusion, and
> > > backwards compatibility issues.
> > >
> > >
> > > I would remove "backwards compatibility"; there cannot be backwards \
> > > compatibility issues with a name change.
> >
> > I am fine making this change; the "potential backwards compatibility" piece was \
> > because of the underdefinition of the subtype, that does not specify the AFI for \
> > the address -- though can be inferred from the length, can cause compat issues.
>
> As I understand, you're essentially saying in the draft that sub-types 9-11 are \
> IPv4 only; so, even though there isn't an AFI (which would have been nice), there \
> should be no ambiguity about this. Inference from length should not be needed.
Right -- inference from the length should not be needed. However, reading \
http://tools.ietf.org/html/rfc4379#section-3.2.8, \
http://tools.ietf.org/html/rfc4379#section-3.2.9, and \
http://tools.ietf.org/html/rfc4379#section-3.2.10, there is nothing that specifies \
that these are IPv4 PE Addresses -- other than reverse engineering the length.
I agree with your proposed change though, we want to remove the "potential \
ambiguity".
>
> > > To underscore that, I would emphasize that the changes here are *just* to the \
> > > names of the sub-TLVs, not to the content or semantics.
> >
> > Yes, that's there already:
>
> I know it's there; pointing this out explicitly at the beginning of the section \
> would drive it home.
Sure. Sounds good.
> > Sections 3.2.8 through 3.2.10 of [RFC4379] list the PW sub-TLVs and
> > state:
> >
> > ...
> >
> > These names and titles are now changed to:
> >
> >
> > >
> > > 6. IANA Considerations
> > >
> > > IANA is requested to perform the following assignments in the "Multi-
> > > Protocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping
> > > Parameters" registry, "TLVs and sub-TLVs" sub-registry.
> > >
> > > [RFC Editor: To be REMOVED prior to publication. This registration
> > > should take place at <http://www.iana.org/assignments/
> > > mpls-lsp-ping-parameters/
> > > mpls-lsp-ping-parameters.xml#mpls-lsp-ping-parameters-7>]
> > >
> > > Update the Value fields of these three Sub-TLVs, adding the "IPv4"
> > > qualifier (see Section 2), and update the Reference to point to this
> > > document:
> > >
> > >
> > > Change above para to (note that IANA is good about updating references):
> > >
> > >
> > > Update the names of the Value fields of these three Sub-TLVs,
> > > adding the "IPv4" qualifier (see Section 2) as follows:
> > >
> >
> > Ack.
>
> Excellent!
>
> -)
Thanks again,
-- Carlos.
> Kireeti.
>
> > Thanks,
> >
> > -- Carlos.
> >
> >
> > >
> > > Kireeti.
> > >
> > > On Sep 24, 2012, at 06:08 , Loa Andersson <loa@pi.nu> wrote:
> > >
> > > > Working Group,
> > > >
> > > > this working group last call was started Sep 4, but when it concluded
> > > > we had received no responses.
> > > >
> > > > There are more than one way to interpret this; we could say "Great -
> > > > everyone is happy!" or we could say "To bad - there is no interest
> > > > whatsoever for this draft!" The actions following each of these
> > > > conclusions would be wildly different.
> > > >
> > > > We have there for decided to extend the working group last call until
> > > > Oct 5, 2012. This time we invite specifically positive responses
> > > > (e.g. "Yes - I believe this draft is ready to be published as an RFC").
> > > >
> > > > Normal wg last call comments are of course also welcome.
> > > >
> > > > Please send your comments to the mpls working group mailing list
> > > > (mpls@ietf.org).
> > > >
> > > > /Loa
> > > > for the mpls working group co-chairs
> > > >
> > > > On 2012-09-04 20:58, Loa Andersson wrote:
> > > > > Working Group,
> > > > >
> > > > > this is to start a working group last call on
> > > > > draft-ietf-mpls-ipv6-pw-lsp-ping-01.
> > > > >
> > > > > Please send your comments to the MPLS wg mailing list (mpls@ietf.org).
> > > > >
> > > > > We have done an IPR poll among the authors and on the mpls wg mailing
> > > > > list. All the authors has responded that they are not aware any IPR
> > > > > claims on this document.
> > > > >
> > > > > No IPR disclosures has been filed against this document.
> > > > >
> > > > >
> > > > > /Loa
> > > > > (for the wg co-chairs)
> > > >
> > > > --
> > > >
> > > >
> > > > 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
> > > > _______________________________________________
> > > > mpls mailing list
> > > > mpls@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/mpls
> > >
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls
> > >
> >
>
[Attachment #5 (unknown)]
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
-webkit-line-break: after-white-space; ">Hi \
Kireeti,<div><br></div><div><br><div><div>On Sep 25, 2012, at 2:11 PM, Kireeti \
Kompella wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> \
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><div \
style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: \
after-white-space; ">Hi Carlos,<div><br><div><div>On Sep 25, 2012, at 10:47 , Carlos \
Pignataro (cpignata) <<a \
href="mailto:cpignata@cisco.com">cpignata@cisco.com</a>> wrote:</div><br \
class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: \
break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; \
">Kireeti,<div><br></div><div>Thanks for the comments! Certainly useful. Ack to both \
points, please see more details \
inline.</div></div></blockquote><div><br></div>Cool!</div><div><br><blockquote \
type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; \
-webkit-line-break: after-white-space; "><div><div><div>On Sep 25, 2012, at 12:54 PM, \
Kireeti Kompella wrote:</div><br class="Apple-interchange-newline"><blockquote \
type="cite">No objection (sorry, Loa, I know you were looking for positive comments). \
However, some hopefully useful comments:<br><br><br>2. IPv4 Pseudowire \
Sub-TLVs<br><br> This document updates Section 3.2 and Sections 3.2.8 \
through 3.2.10<br> of [RFC4379] as follows and as indicated in Section 4 \
and Section 6.<br> This is done to avoid any potential ambiguity, \
confusion, and<br> backwards compatibility issues.<br><br><br>I would \
remove "backwards compatibility"; there cannot be backwards compatibility issues with \
a name change.</blockquote><div><br></div><div>I am fine making this change; the \
"potential backwards compatibility" piece was because of the underdefinition of the \
subtype, that does not specify the AFI for the address -- though can be inferred from \
the length, can cause compat \
issues.</div></div></div></div></blockquote><div><br></div><div>As I understand, \
you're essentially saying in the draft that sub-types 9-11 are IPv4 only; so, even \
though there isn't an AFI (which would have been nice), there should be no ambiguity \
about this. Inference from length should not be \
needed.</div></div></div></div></blockquote><div><br></div><div>Right -- inference \
from the length should not be needed. However, reading <a \
href="http://tools.ietf.org/html/rfc4379#section-3.2.8">http://tools.ietf.org/html/rfc4379#section-3.2.8</a>, <a \
href="http://tools.ietf.org/html/rfc4379#section-3.2.9">http://tools.ietf.org/html/rfc4379#section-3.2.9</a>, \
and </div><a href="http://tools.ietf.org/html/rfc4379#section-3.2.10">http://tools.ietf.org/html/rfc4379#section-3.2.10</a>, \
there is nothing that specifies that these are IPv4 PE Addresses -- other than \
reverse engineering the length.</div><div><br></div><div>I agree with your proposed \
change though, we want to remove the "potential \
ambiguity".</div><div><br></div><div><br><blockquote type="cite"><div \
style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: \
after-white-space; "><div><div><br><blockquote type="cite"><div style="word-wrap: \
break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; \
"><div><div><blockquote type="cite"> To underscore that, I would emphasize that \
the changes here are *just* to the names of the sub-TLVs, not to the content or \
semantics.<br></blockquote><div><br></div><div>Yes, that's there \
already:</div></div></div></div></blockquote><div><br></div><div>I know it's there; \
pointing this out explicitly at the beginning of the section would drive it \
home.</div><br></div></div></div></blockquote><div><br></div><div>Sure. Sounds \
good.</div><br><blockquote type="cite"><div style="word-wrap: break-word; \
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; \
"><div><div><blockquote type="cite"><div style="word-wrap: break-word; \
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; \
"><div><div><div><pre class="newpage" style="font-size: 1em; margin-top: 0px; \
margin-bottom: 0px; page-break-before: always; font-style: normal; font-variant: \
normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; \
text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: \
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "> Sections <a \
href="http://tools.ietf.org/html/draft-ietf-mpls-ipv6-pw-lsp-ping-01#section-3.2.8">3.2.8</a> \
through <a href="http://tools.ietf.org/html/draft-ietf-mpls-ipv6-pw-lsp-ping-01#section-3.2.10">3.2.10</a> \
of [<a href="http://tools.ietf.org/html/rfc4379" title=""Detecting \
Multi-Protocol Label Switched (MPLS) Data Plane Failures"">RFC4379</a>] list the \
PW sub-TLVs and state:
</pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: \
0px; page-break-before: always; font-style: normal; font-variant: normal; \
font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; \
text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: \
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><br></pre><pre \
class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; \
page-break-before: always; font-style: normal; font-variant: normal; font-weight: \
normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: start; \
text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; \
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">...</pre><pre \
class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; \
page-break-before: always; font-style: normal; font-variant: normal; font-weight: \
normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: start; \
text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; \
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><br></pre><pre \
class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; \
page-break-before: always; font-style: normal; font-variant: normal; font-weight: \
normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: start; \
text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; \
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "> These names and \
titles are now changed to: </pre><div><br></div></div><br><blockquote \
type="cite"><br>6. IANA Considerations<br><br> IANA is requested to \
perform the following assignments in the "Multi-<br> Protocol Label \
Switching (MPLS) Label Switched Paths (LSPs) Ping<br> Parameters" \
registry, "TLVs and sub-TLVs" sub-registry.<br><br> [RFC Editor: To be \
REMOVED prior to publication. This registration<br> should take \
place at <<a href="http://www.iana.org/assignments/">http://www.iana.org/assignments/</a><br> \
mpls-lsp-ping-parameters/<br> \
mpls-lsp-ping-parameters.xml#mpls-lsp-ping-parameters-7>]<br><br> \
Update the Value fields of these three Sub-TLVs, adding the "IPv4"<br> \
qualifier (see Section 2), and update the Reference to point to this<br> \
document:<br><br><br>Change above para to (note that IANA is good about \
updating references):<br><br><br> Update the names of the Value fields of \
these three Sub-TLVs,<br> adding the "IPv4" qualifier (see Section 2) as \
follows:<br><br></blockquote><div><br></div><div>Ack.</div></div></div></div></blockqu \
ote><div><br></div><div>Excellent!</div><div><br></div></div></div></div></blockquote><div><br></div><div>:-)</div><div><br></div><div>Thanks \
again,</div><div><br></div><div>-- Carlos.</div><br><blockquote type="cite"><div \
style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: \
after-white-space; "><div><div><div>Kireeti.</div><br><blockquote type="cite"><div \
style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: \
after-white-space; "><div><div><div>Thanks,</div><div><br></div><div>-- \
Carlos.</div><div><br></div><br><blockquote type="cite"><br>Kireeti.<br><br>On Sep \
24, 2012, at 06:08 , Loa Andersson <<a href="mailto:loa@pi.nu">loa@pi.nu</a>> \
wrote:<br><br><blockquote type="cite">Working Group,<br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">this working group last call was \
started Sep 4, but when it concluded<br></blockquote><blockquote type="cite">we had \
received no responses.<br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">There are more than one way to \
interpret this; we could say "Great -<br></blockquote><blockquote \
type="cite">everyone is happy!" or we could say "To bad - there is no \
interest<br></blockquote><blockquote type="cite">whatsoever for this draft!" The \
actions following each of these<br></blockquote><blockquote type="cite">conclusions \
would be wildly different.<br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">We have there for decided to \
extend the working group last call until<br></blockquote><blockquote type="cite">Oct \
5, 2012. This time we invite specifically positive \
responses<br></blockquote><blockquote type="cite">(e.g. "Yes - I believe this draft \
is ready to be published as an RFC").<br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">Normal wg last call comments are \
of course also welcome.<br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">Please send your comments to the \
mpls working group mailing list<br></blockquote><blockquote type="cite">(<a \
href="mailto:mpls@ietf.org">mpls@ietf.org</a>).<br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">/Loa<br></blockquote><blockquote \
type="cite">for the mpls working group co-chairs<br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">On 2012-09-04 20:58, Loa \
Andersson wrote:<br></blockquote><blockquote type="cite"><blockquote \
type="cite">Working Group,<br></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite">this is to start a working group last call \
on<br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite">draft-ietf-mpls-ipv6-pw-lsp-ping-01.<br></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite">Please send your comments to the MPLS wg mailing \
list (<a href="mailto:mpls@ietf.org">mpls@ietf.org</a>).<br></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite">We have done an IPR poll among the authors and on \
the mpls wg mailing<br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite">list. All the authors has responded that they are not aware any \
IPR<br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite">claims on this document.<br></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite">No IPR disclosures has been filed against this \
document.<br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite">/Loa<br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite">(for the wg co-chairs)<br></blockquote></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">-- <br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote \
type="cite">Loa Andersson \
email: \
<a href="mailto:loa.andersson@ericsson.com">loa.andersson@ericsson.com</a><br></blockquote><blockquote \
type="cite">Sr Strategy and Standards Manager \
<a \
href="mailto:loa@pi.nu">loa@pi.nu</a><br></blockquote><blockquote \
type="cite">Ericsson Inc \
phone: \
+46 10 717 52 13<br></blockquote><blockquote type="cite"> \
&n \
bsp; &nbs \
p; +46 \
767 72 92 13<br></blockquote><blockquote \
type="cite">_______________________________________________<br></blockquote><blockquote \
type="cite">mpls mailing list<br></blockquote><blockquote type="cite"><a \
href="mailto:mpls@ietf.org">mpls@ietf.org</a><br></blockquote><blockquote \
type="cite"><a href="https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/ \
mailman/listinfo/mpls</a><br></blockquote><br>_______________________________________________<br>mpls \
mailing list<br><a href="mailto:mpls@ietf.org">mpls@ietf.org</a><br><a \
href="https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/mailman/listinf \
o/mpls</a><br><br></blockquote></div><br></div></div></blockquote></div><br></div></div></blockquote></div><br></div></body></html>
["signature.asc" (signature.asc)]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
iEYEARECAAYFAlBh9OoACgkQtfDPGTp3USxMywCgx57OIc/BER2kr0wJVjlzbYoq
/mMAoIoOsS+Je2sGTanIG+PrPs/gC3R5
=Xtty
-----END PGP SIGNATURE-----
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
--===============0384938600304912040==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic