[prev in list] [next in list] [prev in thread] [next in thread]
List: ms-ospf
Subject: Re: [OSPF] AD review of draft-ietf-ospf-two-part-metric-05
From: "Acee Lindem (acee)" <acee () cisco ! com>
Date: 2016-08-02 22:28:19
Message-ID: D3C6946B.74536%acee () cisco ! com
[Download RAW message or body]
[Attachment #2 (text/plain)]
Hi Alia,
Thanks for your review and progression.
From: Alia Atlas <akatlas@gmail.com<mailto:akatlas@gmail.com>>
Date: Friday, July 29, 2016 at 11:19 PM
To: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>, \
"draft-ietf-ospf-two-part-metric@ietf.org<mailto:draft-ietf-ospf-two-part-metric@ietf.org>" \
<draft-ietf-ospf-two-part-metric@ietf.org<mailto:draft-ietf-ospf-two-part-metric@ietf.org>>
Subject: AD review of draft-ietf-ospf-two-part-metric-05
Resent-From: <alias-bounces@ietf.org<mailto:alias-bounces@ietf.org>>
Resent-To: Lili Wang <liliw@juniper.net<mailto:liliw@juniper.net>>, Acee Lindem \
<acee@cisco.com<mailto:acee@cisco.com>>, \
<Dave.Dubois@gdc4s.com<mailto:Dave.Dubois@gdc4s.com>>, Vibhor Julka \
<vibhor.julka@l-3Com.com<mailto:vibhor.julka@l-3Com.com>>, Tom McMillan \
<tom.mcmillan@l-3com.com<mailto:tom.mcmillan@l-3com.com>>, Jeffrey Zhang \
<zzhang@juniper.net<mailto:zzhang@juniper.net>>
Resent-Date: Friday, July 29, 2016 at 11:19 PM
First, I would like to thank the authors, Jeffrey, Lili, Acee, David, Vibhor and Tom, \
for their work on this draft.
As is customary, I have done my AD review of draft-ietf-ospf-two-part-metric-05.
I do have a few concerns which are detailed below. The number of authors will block \
progressing to IESG telechat until it is addressed. Trusting to a timely resolution \
of the issues below, I am requesting IETF Last Call. With prompt action, this \
document can make it to the August 18 telechat for approval.
Review Comments:
First, this fairly short document has 6 authors. As you all well know, the usual \
limit for drafts progressing is 5. This greatly simplifies the interactions during \
AUTH48 and there is rarely more than a few active editors. Please consider if you \
can reduce it and explain to me privately what justifications might exist, if any, \
for not doing so.
Okay - we will do this and get back to you.
Second, please update the TBDs in the document for the various IANA allocated sub-TLV \
values to be TBD1, TBD2, and TBD3 so it's easier to replace during IANA and RFC \
Editor processing.
Yes - we will do this.
Third, Sec 3.7 defines bit 0 to have specific meaning but doesn't indicate that in \
the IANA section. Please update the IANA section to clearly indicate the bit being \
requested (or update the bit to be a TBD4). The term used to refer to the bit also \
varies between 3.7 and 4. Please pick one term and stick with it. In 3.7, it is \
"Router Functional Capability Bit" and in Sec 4, it is Router Informational \
Capability Bits.
Will do - it is a definitely a "Router Functional Capability Bit" as defined in RFC \
7770.
Thanks,
Acee
Regards,
Alia
[Attachment #3 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: \
after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, \
sans-serif;"> <div>Hi Alia, </div>
<div><br>
</div>
<div>Thanks for your review and progression. </div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; \
BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; \
PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: \
medium none; PADDING-TOP: 3pt"> <span style="font-weight:bold">From: </span>Alia \
Atlas <<a href="mailto:akatlas@gmail.com">akatlas@gmail.com</a>><br> <span \
style="font-weight:bold">Date: </span>Friday, July 29, 2016 at 11:19 PM<br> <span \
style="font-weight:bold">To: </span>OSPF WG List <<a \
href="mailto:ospf@ietf.org">ospf@ietf.org</a>>, "<a \
href="mailto:draft-ietf-ospf-two-part-metric@ietf.org">draft-ietf-ospf-two-part-metric@ietf.org</a>" \
<<a href="mailto:draft-ietf-ospf-two-part-metric@ietf.org">draft-ietf-ospf-two-part-metric@ietf.org</a>><br>
<span style="font-weight:bold">Subject: </span>AD review of \
draft-ietf-ospf-two-part-metric-05<br> <span style="font-weight:bold">Resent-From: \
</span><<a href="mailto:alias-bounces@ietf.org">alias-bounces@ietf.org</a>><br> \
<span style="font-weight:bold">Resent-To: </span>Lili Wang <<a \
href="mailto:liliw@juniper.net">liliw@juniper.net</a>>, Acee Lindem <<a \
href="mailto:acee@cisco.com">acee@cisco.com</a>>, <<a \
href="mailto:Dave.Dubois@gdc4s.com">Dave.Dubois@gdc4s.com</a>>, Vibhor Julka \
<<a href="mailto:vibhor.julka@l-3Com.com">vibhor.julka@l-3Com.com</a>>, Tom \
McMillan <<a href="mailto:tom.mcmillan@l-3com.com">tom.mcmillan@l-3com.com</a>>, \
Jeffrey Zhang <<a href="mailto:zzhang@juniper.net">zzhang@juniper.net</a>><br> \
<span style="font-weight:bold">Resent-Date: </span>Friday, July 29, 2016 at 11:19 \
PM<br> </div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 \
solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"> <div>
<div>
<div dir="ltr">First, I would like to thank the authors, Jeffrey, Lili, Acee, David, \
Vibhor and Tom, for their work on this draft. <div><br>
</div>
<div>As is customary, I have done my AD review \
of draft-ietf-ospf-two-part-metric-05.</div> <div>I do have a few concerns which \
are detailed below. The number of authors will block progressing to IESG \
telechat until it is addressed. Trusting to a timely resolution of the issues \
below, I am requesting IETF Last Call. With prompt action, this document can \
make it to the August 18 telechat for approval.</div> <div><br>
</div>
<div>Review Comments: </div>
<div><br>
</div>
<div>First, this fairly short document has 6 authors. As you all well know, \
the usual limit for drafts progressing is 5. This greatly simplifies the \
interactions during AUTH48 and there is rarely more than a few active editors. \
Please consider if you can reduce it and explain to me privately what justifications \
might exist, if any, for not doing so.</div> </div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Okay - we will do this and get back to you. </div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 \
solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"> <div>
<div>
<div dir="ltr">
<div><br>
</div>
<div>Second, please update the TBDs in the document for the various IANA allocated \
sub-TLV values to be TBD1, TBD2, and TBD3 so it's easier to replace during IANA and \
RFC Editor processing. </div> </div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Yes - we will do this. </div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 \
solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"> <div>
<div>
<div dir="ltr">
<div><br>
</div>
<div>Third, Sec 3.7 defines bit 0 to have specific meaning but doesn't indicate that \
in the IANA section. Please update the IANA section to clearly indicate the bit \
being requested (or update the bit to be a TBD4). The term used to refer to the \
bit also varies between 3.7 and 4. Please pick one term and stick with \
it. In 3.7, it is "Router Functional Capability Bit" and in Sec \
4, it is Router Informational Capability Bits.</div> </div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Will do - it is a definitely a "Router Functional Capability Bit" as defined in \
RFC 7770. </div> <div><br>
</div>
<div>Thanks,</div>
<div>Acee </div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 \
solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"> <div>
<div>
<div dir="ltr">
<div><br>
</div>
<div><br>
</div>
<div>Regards,</div>
<div>Alia</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf
--===============0593300919969588995==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic