
From nobody Fri Mar  3 09:37:19 2017
Return-Path: <csp@csperkins.org>
X-Original-To: tsv-art@ietf.org
Delivered-To: tsv-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7681E129967; Fri,  3 Mar 2017 09:37:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Colin Perkins <csp@csperkins.org>
To: <tsv-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148856263248.10117.15594191397352700006.idtracker@ietfa.amsl.com>
Date: Fri, 03 Mar 2017 09:37:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/9O8Fw16-p9XR0NT1cGie99CDmBg>
Cc: dns-privacy@ietf.org, ietf@ietf.org, draft-ietf-dprive-dtls-and-tls-profiles.all@ietf.org
Subject: [Tsv-art] Review of draft-ietf-dprive-dtls-and-tls-profiles-08
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Mar 2017 17:37:12 -0000

Reviewer: Colin Perkins
Review result: Ready with Nits

I've reviewed this document as part of TSV-ART's ongoing effort to
review key IETF documents. These comments were written primarily for
the transport area directors, but are copied to the document's authors
for their information and to allow them to address any issues raised.
When done at the time of IETF Last Call, the authors should consider
this review together with any other last-call comments they receive.
Please always CC tsv-art@ietf.org if you reply to or forward this
review.

Summary: Ready with nits

The draft describe authentication mechanisms for DNS servers accessed
via TLS and DTLS, and defines profiles for DNS clients and servers
implementing DNS-over-TLS and DTLS. There seems little of transport
concern here, since the draft refers to RFC 7858 and
draft-ietf-dprive-dnsodtls to specify DNS over TLS and DTLS, and
doesn't define such mechanisms itself, Similarly, the (D)TLS profile
is a security profile, rather than transport-related changes.

I just had a couple of nits:

- The short title at the top of each page is “(D)TLS Authentication”.
If there’s space, it'd be clearer if this was “(D)TLS Authentication
for DNS”, or similar, to avoid confusion about what is being
authenticated. 

- Section 9 mandates implementation of TLS session resumption without
server-side state [RFC5077], TLS False Start, and the TLS Cached
Information Extension. I can’t comment on the security implications,
if any, but these extensions seem appropriate for reducing transport
overheads. However, the recommendations in this draft seem
inconsistent with those in RFC 7858 (e.g., RFC 7858 says "DNS servers
SHOULD enable fast TLS session resumption [RFC5077], and this SHOULD
be used when reestablishing connections" but this draft is "MUST
implement"). It would help to align these, or mark this draft as
updating the RFC. 

Colin


From nobody Fri Mar  3 16:38:32 2017
Return-Path: <David.Black@dell.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C788E1293E4; Fri,  3 Mar 2017 16:38:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dell.com header.b=csPdz4Bc; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=rXp6Ltg/
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K_41bx9moLZL; Fri,  3 Mar 2017 16:38:27 -0800 (PST)
Received: from esa6.dell-outbound.iphmx.com (esa6.dell-outbound.iphmx.com [68.232.149.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53B5D12706D; Fri,  3 Mar 2017 16:38:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1488587907; x=1520123907; h=from:cc:to:subject:date:message-id:references: in-reply-to:mime-version; bh=q7PW85yL+GbZtd7O6fYi9MTQIV+2QzGTVM/stRaOk/Y=; b=csPdz4Bcq5aPmmM8rPkzinnAjXUS7tGTXDYy0iGbwz2oEt6fkMeBWyz2 VMC68JXTs4m1dvieZk/BRRbMqjZwFMolgSo9zxuPpB3lx12nH2JFc3Ref LGJrzuUlCsieZjbMFAH78m+yAkPAy7ANE9QBvIWm87TgKOhgn/0K5Epy/ I=;
Received: from esa3.dell-outbound2.iphmx.com ([68.232.154.63]) by esa6.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Mar 2017 18:38:26 -0600
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwdur.emc.com ([128.221.224.79]) by esa3.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Mar 2017 06:37:21 +0600
Received: from maildlpprd51.lss.emc.com (maildlpprd51.lss.emc.com [10.106.48.155]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v240cN3O019994 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 3 Mar 2017 19:38:24 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com v240cN3O019994
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1488587904; bh=N+E+HZVZ5jwA77wVi+Ooc8rq/eM=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=rXp6Ltg/sA1Fo+tPP5Eek4Id+vf5ZHl3dHqWKNF5KVq70uwXPtr4JZQnyhGewH/OT UYiIOiKlPEpLEyi1zub1rtkfkGLR3PNrqzAL9yvhhdW/Mor1JZp/zHuhdV73te0xAH Vxnlz9Ww40ylmv+30KciJQaX0j49uYu01LCmuXIE=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com v240cN3O019994
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd51.lss.emc.com (RSA Interceptor); Fri, 3 Mar 2017 19:37:00 -0500
Received: from MXHUB310.corp.emc.com (MXHUB310.corp.emc.com [10.146.3.36]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v240c5hd012718 (version=TLSv1.2 cipher=AES128-SHA256 bits=128 verify=FAIL); Fri, 3 Mar 2017 19:38:06 -0500
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB310.corp.emc.com ([10.146.3.36]) with mapi id 14.03.0266.001; Fri, 3 Mar 2017 19:38:05 -0500
To: Shitanshu Shah <shitanshu_shah@hotmail.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
Thread-Topic: Review of draft-ietf-idr-sla-exchange-10
Thread-Index: AQHSjn2hotpFQg8pf0qPmuGxW7GZeaF4QrTwgACFLACABFiS0IAB9hiAgATKWFA=
Date: Sat, 4 Mar 2017 00:38:05 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362F8DD70A@MX307CL04.corp.emc.com>
References: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com> <DM3PR13MB0604160394059613AD0331AFE5520@DM3PR13MB0604.namprd13.prod.outlook.com>, <CE03DB3D7B45C245BCA0D243277949362F8C4510@MX307CL04.corp.emc.com> <DM3PR13MB0604865EC77A246609544830E5520@DM3PR13MB0604.namprd13.prod.outlook.com>, <CE03DB3D7B45C245BCA0D243277949362F8D16F3@MX307CL04.corp.emc.com> <DM3PR13MB0604AF5667DD40C1C569422AE5560@DM3PR13MB0604.namprd13.prod.outlook.com>
In-Reply-To: <DM3PR13MB0604AF5667DD40C1C569422AE5560@DM3PR13MB0604.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.62]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949362F8DD70AMX307CL04corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/fiAbbfvzVKzbmd5W_a8UGIcVKoU>
Cc: "idr@ietf.org" <idr@ietf.org>, "Black, David" <David.Black@dell.com>, "draft-ietf-idr-sla-exchange.all@ietf.org" <draft-ietf-idr-sla-exchange.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Tsv-art] Review of draft-ietf-idr-sla-exchange-10
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Mar 2017 00:38:32 -0000

--_000_CE03DB3D7B45C245BCA0D243277949362F8DD70AMX307CL04corpem_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Embedded in my question about VPNs is an implicit suggestion (which I'll no=
w make explicit ...) -- this L2 overhead parameter would be more robust if =
it were defined as the number of octets difference between the full frame t=
hat is sent on the wire and the size of the IP packet to which  the token b=
uckets apply.  Even if there are no known current needs to account for anyt=
hing other than L2 framing, this approach is robust to future network engin=
eering encapsulation "creativity" ;-).

Thanks, --David

From: Tsv-art [mailto:tsv-art-bounces@ietf.org] On Behalf Of Shitanshu Shah
Sent: Tuesday, February 28, 2017 1:24 PM
To: Black, David; tsv-art@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org
Subject: Re: [Tsv-art] Review of draft-ietf-idr-sla-exchange-10




Hi David,



We will add more text to clarify rationale for L2_OVERHEAD.



Do you have a preference or suggest a way to specify L2 rates? We will work=
 on defining 2 TSpecs to specify two rates (min and max).

As far as VPN terminating between Consumer and Producer, I am not aware of =
use-cases, at least in the context of the deployment scenario considered fo=
r the draft.

Regards,
Shitanshu
________________________________
From: Black, David <David.Black@dell.com<mailto:David.Black@dell.com>>
Sent: Monday, February 27, 2017 10:42 AM
To: Shitanshu Shah; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>; Black, David
Subject: RE: Review of draft-ietf-idr-sla-exchange-10

Ok, please make that rationale for the L2_OVERHEAD parameter clear in the d=
raft:
> Though for the cases where physical links are not to be over-run, and/or,=
 sla defined are based on l2 rates, the Consumer would
> need to know l2 overhead from the Producer. Otherwise 10 byes of l2 overh=
ead difference on 64 bytes packets can be significant
> compare to on 1400 bytes packets, and thus the Producer does not have a w=
ay to convert rates to ip based (this can cause
> functional issue), since this has to be per packet consideration.
It looks like the result is that if the Producer's L2 overhead is larger th=
an the Consumer's, and the token buckets are specified in IP octets, the co=
nsumer has to calculate a per-packet charge of the L2 overhead difference a=
gainst the IP token bucket (and in the opposite case, there may be a per-pa=
cket credit).   Are there cases where the overhead is not all L2, e.g., SLA=
/TCA Consumer is using a VPN that terminates between Consumer and Producer?

Thanks, --David

From: Shitanshu Shah [mailto:shitanshu_shah@hotmail.com]
Sent: Friday, February 24, 2017 1:05 PM
To: Black, David; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Re: Review of draft-ietf-idr-sla-exchange-10




Hi David,



One response inline ##svshah2

________________________________
From: Black, David <David.Black@dell.com<mailto:David.Black@dell.com>>
Sent: Friday, February 24, 2017 8:53 AM
To: Shitanshu Shah; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>; Black, David
Subject: RE: Review of draft-ietf-idr-sla-exchange-10

David> Inline ...

Thanks, --David

From: Shitanshu Shah [mailto:shitanshu_shah@hotmail.com]
Sent: Friday, February 24, 2017 4:09 AM
To: Black, David; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Re: Review of draft-ietf-idr-sla-exchange-10




Hi David,



Thank you for taking time for the review..



Please find our response inline ##svshah and [Med]


Regards,
Shitanshu
________________________________
From: David Black <david.black@emc.com<mailto:david.black@emc.com>>
Sent: Tuesday, February 21, 2017 3:31 PM
To: tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Review of draft-ietf-idr-sla-exchange-10

Reviewer: David Black
Review result: Not Ready

I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. When done at the time of IETF
Last Call, the authors should consider this review together with any
other last-call comments they receive. Please always CC
tsv-art@ietf.org<mailto:tsv-art@ietf.org> if you reply to or forward this r=
eview.

Document: draft-ietf-idr-sla-10
Reviewer: David Black
Review Date: February 21, 2017

Review result: Not Ready

This is an early TSV-ART review of a working group draft, requested by
the IDR Working Group.

This draft defines an extension to BGP to allow exchange of traffic
handling parameters (e.g., configured rates, burst sizes, drop
thresholds).  While this is a useful area of technology to standardize
across network operators, this draft has significant problems, and
parts of it could use some serious rethought.

This reviewer has discussed small portions of this draft with some of
the authors in the past, but this is his first comprehensive reading
and review of the draft.

Major Issues:

[1] The draft is misnamed.  This is not an SLA (Service Level
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -
see the definition of TCA in RFC 2475.  This draft should start from
that definition and generalize the applicability of TCA beyond
Diffserv.  Large areas of SLA content are not covered by this draft -
for more details, see the Wikipedia article on SLA:
https://en.wikipedia.org/wiki/Service-level_agreement .

##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.


David> That would be good, thanks.

[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to
specify a token bucket is a good idea, but it's not a good idea to
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)
octets, as the RFC 2115 TSpec is specified in terms of IP octets.
This change to specification in terms of L2 octets results in needing
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)
framing overhead at sender and receiver of this information.  The
TSpec should be respecified at the IP layer, with L2 framing overhead
left to the Producer and Consumer to factor into their calculations
based on each's direct knowledge of L2 functionality and configuration
in the local AS.  That ought to enable elimination of the L2_OVERHEAD
TLV, thereby reducing complexity.
##svshah, the purpose for advertising L2 overhead, from the Producer to the=
 Consumer, is to make sure traffic is well conditioned, at the egress of th=
e Consumer, to avoid possible indiscriminate drops at the ingress of the Pr=
oducer. In another words, the Producer is telling the Consumer to ignore it=
s own link level overhead, instead use Producer's provided link level overh=
ead while running frames through QoS functions (this is relevant in use-cas=
es where l2 overhead of the egress link on Consumer and of ingress link on =
the Producer are of different size, e.g., in the vpn/tunnel connection betw=
een two peer nodes which physically may be multiple hops away).
I understand your comments regarding re-using TSpec without any modificatio=
n. Do you agree with the use-case of l2 differences? If yes, any suggestion=
 how to accommodate that?

David> Specifying this in terms of IP octets implies that L2 overhead is to=
 be ignored on both links.  That's simpler, and a few sentences of discussi=
on about possible L2 framing differences should cover what needs to be done=
 (e.g., if traffic rates are configured in terms of L2 octets, then explain=
 how each entity converts between IP traffic and L2 traffic - the draft alr=
eady effectively contains that explanation).

##svshah2, just to make sure that some of the real use are not left out..

For the traffic conditioning where sla established is for the ip based rate=
s only, it suffices for the Producer to send rates only IP based ignoring a=
ny specific of l2 overheads.

Though for the cases where physical links are not to be over-run, and/or, s=
la defined are based on l2 rates, the Consumer would need to know l2 overhe=
ad from the Producer. Otherwise 10 byes of l2 overhead difference on 64 byt=
es packets can be significant compare to on 1400 bytes packets, and thus th=
e Producer does not have a way to convert rates to ip based (this can cause=
 functional issue), since this has to be per packet consideration.

Regards,
Shitanshu




[3] A token bucket should have two rate-related marking parameters
based on its token fill rate, i.e., min-rate, not the four
rate-related marking parameters in this draft.  The max-rate
parameters in sections 3.3.2.5-6 ought to be specified against a
second token bucket.  In addition, the handling precedence algorithm
in section 3.3.2.7 is an overly complex way to specify the
relationship of two token buckets.  All of this is even more
important, because max-rate, as defined in RFC 2115, is only
applicable to bursting - that max-rate for bursting often turns out to
be an interface line rate, which is not generally useful for the
traffic provisioning purposes of this draft.

##svshah, what you describe below conceptually very much makes sense and th=
at is what we attempt to achieve. What is unclear though how to capture tha=
t using TSpec definition specified in RFC2215. Since that TSpec definition =
has both minimum-rate and maximum-rate, but no in/out profile marking param=
eters.

Is your proposal below to define two TSpecs using the same definition from =
RFC2215? Wouldn't in that case we have min/max specified twice? min/max in =
each TSpec? and thus confusing to represent one min and one max through two=
 TSpecs?

David> See RFC 2698 for the desired behavior and the parameters needed to s=
pecify it.  The current idr-sla draft is not able to represent the traffic =
conditioning mechanisms specified in both RFC 2698 and RFC 2697, as each me=
chanism requires two token buckets (e.g., there are two burst sizes, but th=
e idr-sla draft TSpec only contains one).  This deficiency needs to be deal=
t with.  One possibility for simplification is to drop the max-rate from th=
e RFC 2115 TSpec and assume that the max-rate for bursting is the effective=
 line rate.

The following should be done instead:
        - Define TSpecs for two token buckets, a primary/committed token bu=
cket
                and a secondary/peak token bucket that MUST be nested, i.e.=
, traffic
                that is in-profile for the secondary/peak token bucket is a=
lways
                in-profile for the primary/committed token bucket.  Some of=
 the details
                of how to specify this are subtle, see RFC 2698 for a worke=
d example.
                Use of a secondary/peak token bucket requires use of the pr=
imary/
                committed token bucket, but a primary/committed token bucke=
t can be used
                without a secondary/peak token bucket.
        - For a single token bucket, define two handling TLVs, Committed (i=
n profile) and
                Excess (out of profile).
        - For two token buckets, define three handling TLVs, Committed (in =
profile for both
                token buckets), Peak (out of profile for primary/committed =
token bucket, but in
                profile for secondary/peak token bucket) and Excess (out of=
 profile for both
                token buckets).
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess
terms.

[4] The drop threshold TLV in section 3.3.2.8 is not specified
sufficiently to be implemented interoperably.  For example, I don't
understand what an implementation is supposed to do when it receives 3
drop thresholds.
##svshah, It is around the semantics of a single queue with a different thr=
eshold for a set of code-points, where packet for a specific code-point is =
to be tail dropped if overall queue-depth hits code-point specific threshol=
d at the arrival of that packet.
We will add appropriate clarification for this semantics.

David> Will look at revision

[5] The relative priority TLV in section 3.3.2.9 has the same
insufficient specification problem as the drop threshold TLV,
compounded by a functional incompleteness problem - if the recipient
is using a weighted packet transmission scheduler (e.g., WRR),
priorities cannot be used to configure that scheduler.  Hence, some
specification of weights and scheduling algorithms that use weights
needs to be added.
##svshah, Sure. Is following clarification okay? (some of the wordings take=
n from RFC2598)

"
A higher priority class of traffic to be served without pre-empted by lower=
 priority class of traffic for more than a packet time at the configured ra=
te.

In the system that implements WRR, the use of relative priority may get res=
tricted where a single queue may be used for a higher priority traffic clas=
s where that queue  is configured for the full share of the output bandwidt=
h.
"

David> Last sentence basically says that WRR weights are out-of-scope.  Tha=
t seems wrong.  Will look at revision.

[6] I have no idea what the sub-traffic classes TLV in section
3.3.2.10 is supposed to do, as that TLV is specified based on "Traffic
Class TLVs" which is an undefined term in this draft (e.g., that term
is not used outside of section 3.3.2.10.
##svshah, They are to facilitate hierarchy. A specific Traffic Class, can f=
urther be divided in a multiple  subset of Traffic Classes, with their own =
Traffic Class Elements and Traffic Class Services.

Will correct the wording to remove your this specific concern.

David> Will look at revision

[7] This draft's QoS contents need to be functionally aligned with
work-in-progress on YANG QoS models, in order to provide some
assurance that that this draft is implementable for actual network
switch/router data paths.  The current acknowledgement of the
existence of YANG, NETCONF and RESTConf at the end of Section 1 does
not suffice.
##svshah, While eventually "Traffic Conditioning Agreement" should be trans=
lated to the actual forwarding qos policy on any vendor specific device, TC=
A exchange largely carries concepts/semantics that is either standard based=
 or well understood.

While we are not aware of any working group document of QoS Yang Model, we =
think that  concepts of Traffic Conditioning should be easily adaptable to =
any QoS Yang Models since they also have to be defined to support those con=
cepts.


David> Still want to see cross-check with implementations here.


[8] There are significant complexity and correctness problems caused
by the option to not specify the Source AS - e.g., Section 3.2 defines
an SLA ID as an "identifier which is unique in the scope of Source AS"
which is meaningless if there is no Source AS.  It would be simpler to
always specify Source AS, even in the point-to-point case.

##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in cases.=
 Given specification of Source AS always is more clearer in multiple feed-b=
ack we have gotten so far, we can modify the specification to incorporate t=
hat over the simplicity of implementation for certain cases.

David> OK, thanks.

[9] In section 3.2, the "intended for the peer receiver of the BGP
UPDATE message" text in the specification of bit 0 of the SLA Subtype
flags is unclear.  I suspect that this is intended to differentiate
the two usages described in sections 4.1.1 (Point-to-Point) and 4.1.2
(Multiple Hops), in which case the parenthesized terms (or similar
terminology) should be used with cross-references to those two
sections.
##svshah, sure will make necessary changes, also in the context of earlier =
comment.


[10] There needs to be a coherent discussion in one place about how
SLA advertisement, update and withdrawal work.  A single ADVERTISE
method may suffice on the wire, but the details on how initial
advertisement, subsequent advertisement (update) and withdrawal work
need to be specified in one place.  The third paragraph of Section 4
is a start on this material, but it's too terse;

[Med] That text is terse because we are reusing the BGP machinery for adver=
tising/withdrawing; we only augment it with triggers that are linked to the=
 SLA information. A new SLA will lead to an update message with ADVERTISE, =
an update of an existing SLA will trigger an update message. We do think th=
is information is already present in the document.

David>This is hard to understand it, as there is no statement that the BGP =
machinery is being used, and the material on SLA usage is spread in differe=
nt places.  I suggest starting section 3 with a discussion of advertisement=
/update/withdrawal, and how all three are realized via a single ADVERTISE m=
ethod via BGP UPDATE - this was difficult to figure out in reading the curr=
ent draft.

it should be expanded
into its own subsection, and moved earlier to come before the
ADVERTISE method in Section 3.2.  This text from Section 3.2 should be
moved into that new subsection and likewise expanded:

[Med] Another option is to move it Section 4. From our standpoint, we do th=
ink it is straightforward to describe the behavior once the attributes form=
at are defined.

David> Ok, that's an editorial choice - I prefer to explain how something w=
orks before defining its on-the-wire data format.

      If an advertised SLA ID is different from earlier advertised one,
      for the same prefix and from the same Source AS, indicates Source
      AS is advertising new SLA Content to replace the previous one
      advertised with the same SLA ID.

In addition, I wonder whether functionality should be added to allow
withdrawal of an advertisement by specifying its SLA ID, although that
was not part of the original design.


[Med] The reason we didn't adopted that design is that we don't want to mak=
e assumptions on which data the remote peer will be used for enforcing loca=
l actions and also because of this text:

      The SLA ID applies to aggregate traffic to prefixes for a given

      AFI/SAFI that share the same Source AS and SLA ID.

David> That's fine, I wanted to ensure that this had been considered.  The =
discussion of BGP mechanism reuse will probably help here.

[11] Notions of context for interpretation of all the IPFIX parameters
in 3.3.1 need to be added, e.g.:
        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.
        - The IP address parameters are rather likely to be VPN-specific wh=
en there's more
                than one BGP/MPLS VPN that spans or transits the ASs involv=
ed.
        - The transport port parameters need specification of which transpo=
rt header and where it
                is located (e.g., for TCP traffic carried by in VXLAN, is t=
his the inner TCP header
                or the outer UDP header in VXLAN).
There are probably simple approaches to specifying context in all
cases, but that context does need to be specified ... in all cases.

[Med] We dind't include a context field because we thought that the definit=
ion of the IPFIX attributes is sufficient by itself, but if you do think it=
 is helpful to have such information, we can update the table.
David>  Really???  Please reread the first comment above:

        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.

David>  Taking just DSCP, it can change on a per-link basis, so something h=
as to specify which link (between the SLA Producer and SLA Consumer?) is in=
volved.  It probably suffices to say that it's the link that crosses the re=
levant AS boundary, but that does have to be stated, as it's nowhere to be =
found in the far more general IPFIX registry.

[12] The security considerations (section 10) are severely incomplete
and insufficient:

David> I stand by this statement and recommend a complete rewrite of the se=
curity considerations.

        - Discussion of possible abuse of this BGP option for denial-of-ser=
vice and theft-of-service,
                needs to be added, including possible countermeasures and m=
itigations.

[Med] This attack vector is not specific to this attribute; this is valid f=
or BGP in general.

David> There are additional attacks enabled by this attribute.

        - This sentence at the end of the second paragraph in Section 10 is=
 content-free:

                   It is NOT RECOMMENDED to enable this attribute at the
                   scale of the Internet unless if means to prevent leaking=
 sensitive
                   information are enforced.

                What exactly is an implementer or admin supposed to do?

[Med] An example of what an admin needs to check if this information can be=
 sent to a given peer or not. Some of the content of the attribute contains=
 some sensitive information such as contract Id, classes, etc.

How does one
                figure out whether an implementation or deployment is  "at =
the scale
                of the Internet" ??

[Med] The idea here is to avoid leaking such data in to the global routing =
table. Only entitled peers need receive such information with controlled sc=
ope.

David> I understand the idea - the problem is that I don't see specificatio=
n of what has to be implemented in either the text in the draft or the abov=
e explanations.
        - The next to last paragraph in section 10 is almost content-free, =
as it leaves
                decisions on implementation and deployment of key security =
functionality as
                "an exercise for the reader" - that's not acceptable.

[Med] I guess you are referring to the following text. Validation checks ar=
e really deployment-specific. The text calls out the issue and recommends a=
n action; how to translate this action into detailed actions is realty loca=
l to a domain

   The attribute may be advertised by a misbehaving node to communicate

   SLA parameters that are not aligned with the SLA agreements.  Though

   the enforcement of SLA parameters is outside the scope of this

   document, it is RECOMMENDED that the SLA Consumer to enforce a set of

   validation checks before translating the SLA parameters conveyed in

   the QoS attributes into provisioning actions.  Such validations MAY

   rely on SLA parameters like the origin AS or SLA ID, like generating

   SLA ID using pseudo-random schemes [RFC4086<https://tools.ietf.org/html/=
rfc4086>].

David> I stand by the "exercise to the reader"  criticism - one way to be h=
onest about this would be to change the paragraph to:



        The attribute may be advertised by a misbehaving node to communicat=
e

   SLA parameters that are not aligned with the SLA agreements.  The

   enforcement of SLA parameters is outside the scope of this document.



David> That does not change any normative content of the original paragraph=
.  My view is that the "outside the scope of this document" statement is wr=
ong because all of these parameters are being defined in this draft.

        - Last, but not least, the final paragraph in Section 10 is a joke =
that will
                be lost on a security directorate reviewer - to understand =
why, see
                Section 2 of RFC 6919, and take note of the publication dat=
e of RFC 6919.

David> For anyone who didn't catch the reference, RFC 6919 is an April 1 RF=
C ... and the "SHOULD BE considered" language used in the last security con=
siderations paragraph of this draft is accurately characterized as vague in=
 Section 2 of RFC 6919:
   The phrase "SHOULD CONSIDER" indicates that the authors of the
   specification think that implementations should do something, but
   they're not sure quite what.
------------------------

Having noted a dozen major issues, I'll end the review here for now,
as I believe a serious revision of the draft is called for, which
would be a better starting point to review for minor issues and
editorial items.

--------------------------------------------------------
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953     Cell: +1 (978) 394-7754
David.Black@dell.com<mailto:David.Black@dell.com>  <=3D=3D=3D NEW =3D=3D=3D
--------------------------------------------------------

--_000_CE03DB3D7B45C245BCA0D243277949362F8DD70AMX307CL04corpem_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 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;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.xmsonormal, li.xmsonormal, div.xmsonormal
	{mso-style-name:xmsonormal;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Embedded in my question a=
bout VPNs is an implicit suggestion (which I&#8217;ll now make explicit ...=
) -- this L2 overhead parameter would be more robust if it were
 defined as the number of octets difference between the full frame that is =
sent on the wire and the size of the IP packet to which &nbsp;the token buc=
kets apply.&nbsp; Even if there are no known current needs to account for a=
nything other than L2 framing, this approach
 is robust to future network engineering encapsulation &#8220;creativity&#8=
221; ;-).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks, --David<o:p></o:p=
></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tsv-art =
[mailto:tsv-art-bounces@ietf.org]
<b>On Behalf Of </b>Shitanshu Shah<br>
<b>Sent:</b> Tuesday, February 28, 2017 1:24 PM<br>
<b>To:</b> Black, David; tsv-art@ietf.org<br>
<b>Cc:</b> idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@iet=
f.org<br>
<b>Subject:</b> Re: [Tsv-art] Review of draft-ietf-idr-sla-exchange-10<o:p>=
</o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Hi&nbsp;David,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">We will add more text to clarify rationale for L2_OVERHEAD.<o:p>=
</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Do you have a preference or suggest a way to specify L2 rates? W=
e will work on defining 2 TSpecs to specify two rates (min and max).&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><br>
As far as VPN terminating between Consumer and Producer, I am not aware of =
use-cases, at least in the context of the deployment scenario considered fo=
r the draft.
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">Shitanshu<o:p></o:p></span></p>
</div>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k">
<hr size=3D"2" width=3D"98%" align=3D"center">
</span></div>
<div id=3D"divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black">From:</span></b><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"> Black, David &lt;<a href=3D"mailto:David.Black@dell.com">=
David.Black@dell.com</a>&gt;<br>
<b>Sent:</b> Monday, February 27, 2017 10:42 AM<br>
<b>To:</b> Shitanshu Shah; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf=
.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a>; Black, David<br>
<b>Subject:</b> RE: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Ok, please make that rationale for the =
L2_OVERHEAD parameter clear in the draft:</span><span style=3D"color:black"=
><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&gt; Though for the cases where&nbsp;phys=
ical&nbsp;links are not to be&nbsp;over-run, and/or,&nbsp;sla defined are b=
ased on
 l2 rates, the&nbsp;Consumer would<br>
&gt; need to know l2 overhead from the Producer. Otherwise 10 byes of l2 ov=
erhead difference on 64 bytes packets can be significant<br>
&gt; compare to on 1400 bytes packets, and thus the Producer does not have =
a way to convert rates to&nbsp;ip based (this can cause<br>
&gt; functional issue), since this has to be per packet consideration.</spa=
n><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">It looks like the result is that if the=
 Producer&#8217;s L2 overhead is larger than the Consumer&#8217;s, and
 the token buckets are specified in IP octets, the consumer has to calculat=
e a per-packet charge of the L2 overhead difference against the IP token bu=
cket (and in the opposite case, there may be a per-packet credit).&nbsp;&nb=
sp; Are there cases where the overhead is
 not all L2, e.g., SLA/TCA Consumer is using a VPN that terminates between =
Consumer and Producer?</span><span style=3D"color:black"><o:p></o:p></span>=
</p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Thanks, --David</span><span style=3D"co=
lor:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
> Shitanshu
 Shah [<a href=3D"mailto:shitanshu_shah@hotmail.com">mailto:shitanshu_shah@=
hotmail.com</a>]
<br>
<b>Sent:</b> Friday, February 24, 2017 1:05 PM<br>
<b>To:</b> Black, David; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.o=
rg</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Re: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Hi David,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">One response inline ##svshah2<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k">
<hr size=3D"2" width=3D"98%" noshade=3D"" style=3D"color:black" align=3D"ce=
nter">
</span></div>
<div id=3D"divRplyFwdMsg">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k"> Black,
 David &lt;<a href=3D"mailto:David.Black@dell.com">David.Black@dell.com</a>=
&gt;<br>
<b>Sent:</b> Friday, February 24, 2017 8:53 AM<br>
<b>To:</b> Shitanshu Shah; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf=
.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a>; Black, David<br>
<b>Subject:</b> RE: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">
</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Inline ...</span><span style=
=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Thanks, --David</span><span style=3D"co=
lor:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
> Shitanshu
 Shah [<a href=3D"mailto:shitanshu_shah@hotmail.com">mailto:shitanshu_shah@=
hotmail.com</a>]
<br>
<b>Sent:</b> Friday, February 24, 2017 4:09 AM<br>
<b>To:</b> Black, David; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.o=
rg</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Re: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Hi David,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Thank you for taking time for the review..<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Please find our response inline ##svshah and [Med]<o:p></o:p></s=
pan></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">Regards,
</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Shitanshu</span><span style=3D"color:black"><o:p></o:p></span></=
p>
<div>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k">
<hr size=3D"2" width=3D"98%" align=3D"center">
</span></div>
<div id=3D"x_divRplyFwdMsg">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k"> David
 Black &lt;<a href=3D"mailto:david.black@emc.com">david.black@emc.com</a>&g=
t;<br>
<b>Sent:</b> Tuesday, February 21, 2017 3:31 PM<br>
<b>To:</b> <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Review of draft-ietf-idr-sla-exchange-10</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">
</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Reviewer: David Black<br>
Review result: Not Ready<br>
<br>
I've reviewed this document as part of the transport area<br>
directorate's ongoing effort to review key IETF documents. These<br>
comments were written primarily for the transport area directors, but<br>
are copied to the document's authors for their information and to<br>
allow them to address any issues raised. When done at the time of IETF<br>
Last Call, the authors should consider this review together with any<br>
other last-call comments they receive. Please always CC<br>
<a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a> if you reply to or=
 forward this review.<br>
<br>
Document: draft-ietf-idr-sla-10<br>
Reviewer: David Black<br>
Review Date: February 21, 2017<br>
<br>
Review result: Not Ready<br>
<br>
This is an early TSV-ART review of a working group draft, requested by<br>
the IDR Working Group.<br>
<br>
This draft defines an extension to BGP to allow exchange of traffic<br>
handling parameters (e.g., configured rates, burst sizes, drop<br>
thresholds).&nbsp; While this is a useful area of technology to standardize=
<br>
across network operators, this draft has significant problems, and<br>
parts of it could use some serious rethought.<br>
<br>
This reviewer has discussed small portions of this draft with some of<br>
the authors in the past, but this is his first comprehensive reading<br>
and review of the draft.<br>
<br>
Major Issues:<br>
<br>
[1] The draft is misnamed.&nbsp; This is not an SLA (Service Level<br>
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -<br>
see the definition of TCA in RFC 2475.&nbsp; This draft should start from<b=
r>
that definition and generalize the applicability of TCA beyond<br>
Diffserv.&nbsp; Large areas of SLA content are not covered by this draft -<=
br>
for more details, see the Wikipedia article on SLA:<br>
<a href=3D"https://en.wikipedia.org/wiki/Service-level_agreement" id=3D"LPl=
nk481142">https://en.wikipedia.org/wiki/Service-level_agreement</a> .<br>
<br>
##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">David&gt; That would be good, thanks.</sp=
an><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
<br>
[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to<br>
specify a token bucket is a good idea, but it's not a good idea to<br>
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)<br>
octets, as the RFC 2115 TSpec is specified in terms of IP octets. <br>
This change to specification in terms of L2 octets results in needing<br>
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)<br>
framing overhead at sender and receiver of this information.&nbsp; The<br>
TSpec should be respecified at the IP layer, with L2 framing overhead<br>
left to the Producer and Consumer to factor into their calculations<br>
based on each's direct knowledge of L2 functionality and configuration<br>
in the local AS.&nbsp; That ought to enable elimination of the L2_OVERHEAD<=
br>
TLV, thereby reducing complexity.</span><span style=3D"color:black"><o:p></=
o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, the purpose for advertising L2 =
overhead, from the Producer to the Consumer,&nbsp;is to make sure
 traffic is well conditioned, at the egress of the&nbsp;Consumer, to avoid =
possible indiscriminate drops at the ingress of the Producer. In another wo=
rds, the&nbsp;Producer is telling the&nbsp;Consumer to ignore its own link =
level overhead, instead use Producer's provided
 link level overhead while running frames through QoS functions (this is&nb=
sp;relevant in use-cases where l2 overhead of the&nbsp;egress link on Consu=
mer and of ingress link on the Producer are of different size, e.g., in the=
&nbsp;vpn/tunnel connection between two peer&nbsp;nodes
 which physically may be multiple hops away).</span><span style=3D"color:bl=
ack"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">I understand your comments regarding re-u=
sing TSpec without any modification.&nbsp;Do you agree with the
 use-case of l2 differences? If yes, any suggestion how to accommodate that=
?</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Specifying this in terms of I=
P octets implies that L2 overhead is to be ignored on both links.&nbsp;
 That&#8217;s simpler, and a few sentences of discussion about possible L2 =
framing differences should cover what needs to be done (e.g., if traffic ra=
tes are configured in terms of L2 octets, then explain how each entity conv=
erts between IP traffic and L2 traffic
 - the draft already effectively contains that explanation).</span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah2, just to make sure that some of=
 the real use are not left out..</span><span style=3D"color:black"><o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">For the traffic conditioning where sla es=
tablished is for the ip based rates only, it suffices for
 the Producer to&nbsp;send rates only IP based ignoring any specific of l2 =
overheads.</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Though for the cases where&nbsp;physical&=
nbsp;links are not to be&nbsp;over-run, and/or,&nbsp;sla defined are based =
on
 l2 rates, the&nbsp;Consumer would need to know l2 overhead from the Produc=
er. Otherwise 10 byes of l2 overhead difference on 64 bytes packets can be =
significant compare to on 1400 bytes packets, and thus the Producer does no=
t have a way to convert rates to&nbsp;ip based
 (this can cause functional issue), since this has to be per packet conside=
ration.</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Regards,</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Shitanshu</span><span style=3D"color:blac=
k"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
[3] A token bucket should have two rate-related marking parameters<br>
based on its token fill rate, i.e., min-rate, not the four<br>
rate-related marking parameters in this draft.&nbsp; The max-rate<br>
parameters in sections 3.3.2.5-6 ought to be specified against a<br>
second token bucket.&nbsp; In addition, the handling precedence algorithm<b=
r>
in section 3.3.2.7 is an overly complex way to specify the<br>
relationship of two token buckets.&nbsp; All of this is even more<br>
important, because max-rate, as defined in RFC 2115, is only<br>
applicable to bursting - that max-rate for bursting often turns out to<br>
be an interface line rate, which is not generally useful for the<br>
traffic provisioning purposes of this draft.</span><span style=3D"color:bla=
ck"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, what you describe below concept=
ually very much makes sense and that is what we attempt to
 achieve. What is unclear though how to capture that using TSpec definition=
 specified in RFC2215. Since that TSpec definition has both minimum-rate an=
d maximum-rate, but no in/out profile marking parameters.</span><span style=
=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Is your proposal below to define two TSpe=
cs using the same&nbsp;definition from RFC2215? Wouldn't in that
 case we have min/max specified twice? min/max in each TSpec? and thus conf=
using to represent one min and one max through two TSpecs?</span><span styl=
e=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; See RFC 2698 for the desired =
behavior and the parameters needed to specify it.&nbsp; The current
 idr-sla draft is not able to represent the traffic conditioning mechanisms=
 specified in both RFC 2698 and RFC 2697, as each mechanism requires two to=
ken buckets (e.g., there are two burst sizes, but the idr-sla draft TSpec o=
nly contains one).&nbsp; This deficiency
 needs to be dealt with.&nbsp; One possibility for simplification is to dro=
p the max-rate from the RFC 2115 TSpec and assume that the max-rate for bur=
sting is the effective line rate.</span><span style=3D"color:black"><o:p></=
o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
The following should be done instead:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Define TSpecs for two token bu=
ckets, a primary/committed token</span><span style=3D"font-size:10.0pt;font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">bucket<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; and a secondary/peak token bucket that MUST be nested, i.e.=
,</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">traffic<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; that is in-profile for the secondary/peak token bucket is a=
lways<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; in-profile for the primary/committed token bucket.&nbsp; So=
me of the</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">details<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; of how to specify this are subtle, see RFC 2698 for a worke=
d</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">example.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Use of a secondary/peak token bucket requires use of the pr=
imary/<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; committed token bucket, but a primary/committed token bucke=
t can be</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">used<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; without a secondary/peak token bucket.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For a single token bucket, def=
ine two handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt;=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">profile) and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Excess (out of profile).<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For two token buckets, define =
three handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">profile for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets), Peak (out of profile for primary/committed =
token</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">bucket, but in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; profile for secondary/peak token bucket) and Excess (out of=
 profile</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets).<br>
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess<br>
terms.<br>
<br>
[4] The drop threshold TLV in section 3.3.2.8 is not specified<br>
sufficiently to be implemented interoperably.&nbsp; For example, I don't<br=
>
understand what an implementation is supposed to do when it receives 3<br>
drop thresholds.</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah,&nbsp;It is around the semantics=
 of&nbsp;a single queue with a different threshold for a set of code-points=
,
 where packet for a specific code-point is to be tail dropped if overall qu=
eue-depth hits code-point specific threshold at the arrival of that packet.=
</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">We will add appropriate clarification for=
 this semantics.</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; Will look at revision
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
[5] The relative priority TLV in section 3.3.2.9 has the same<br>
insufficient specification problem as the drop threshold TLV,<br>
compounded by a functional incompleteness problem - if the recipient<br>
is using a weighted packet transmission scheduler (e.g., WRR),<br>
priorities cannot be used to configure that scheduler.&nbsp; Hence, some<br=
>
specification of weights and scheduling algorithms that use weights<br>
needs to be added.</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, Sure. Is following clarificatio=
n okay? (some of the wordings taken from RFC2598)</span><span style=3D"colo=
r:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&quot;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">A higher priority class of traffic&nbsp;t=
o be served without pre-empted by lower priority&nbsp;class of traffic&nbsp=
;for
 more than a packet time at the configured rate.</span><span style=3D"color=
:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">In the system that implements WRR, the us=
e of relative priority may get restricted where a single queue
 may be used for a&nbsp;higher priority traffic class where that queue &nbs=
p;is configured for the full share of the output bandwidth.</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&quot;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; Last sentence basically says that W=
RR weights are out-of-scope.&nbsp; That seems wrong.&nbsp; Will look at
 revision.</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
[6] I have no idea what the sub-traffic classes TLV in section<br>
3.3.2.10 is supposed to do, as that TLV is specified based on &quot;Traffic=
<br>
Class TLVs&quot; which is an undefined term in this draft (e.g., that term<=
br>
is not used outside of section 3.3.2.10.</span><span style=3D"color:black">=
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, They are to facilitate hierarch=
y. A specific Traffic Class, can further be divided in a multiple
 &nbsp;subset of&nbsp;Traffic Classes, with their own Traffic Class Element=
s and Traffic Class Services.</span><span style=3D"color:black"><o:p></o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Will correct the wording to remove your t=
his specific concern.</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">David&gt; Will look at revision
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
[7] This draft's QoS contents need to be functionally aligned with<br>
work-in-progress on YANG QoS models, in order to provide some<br>
assurance that that this draft is implementable for actual network<br>
switch/router data paths.&nbsp; The current acknowledgement of the<br>
existence of YANG, NETCONF and RESTConf at the end of Section 1 does<br>
not suffice.</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, While&nbsp;eventually &quot;Tra=
ffic Conditioning Agreement&quot; should be translated to the actual forwar=
ding
 qos policy on any vendor specific device, TCA exchange largely carries con=
cepts/semantics that is either standard based or&nbsp;well understood.</spa=
n><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">While we are not aware of any working gro=
up document of QoS Yang Model, we think that &nbsp;concepts of
 Traffic Conditioning should be easily adaptable to any QoS Yang Models sin=
ce they also have to be defined to support those concepts.</span><span styl=
e=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Still want to see cross-check=
 with implementations here.</span><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
<br>
[8] There are significant complexity and correctness problems caused<br>
by the option to not specify the Source AS - e.g., Section 3.2 defines<br>
an SLA ID as an &quot;identifier which is unique in the scope of Source AS&=
quot;<br>
which is meaningless if there is no Source AS.&nbsp; It would be simpler to=
<br>
always specify Source AS, even in the point-to-point case.<br>
<br>
##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in&nbsp;c=
ases. Given specification of Source AS always is more clearer in multiple f=
eed-back we have gotten so far, we can
 modify the specification to incorporate that over the simplicity of implem=
entation for certain cases.</span><span style=3D"color:black"><o:p></o:p></=
span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; OK, thanks.</span><span style=
=3D"color:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[9] In section 3.2, the &quot;intended for =
the peer receiver of the BGP</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">UPDATE message&quot; text in the specificat=
ion of bit 0 of the SLA Subtype</span><span style=3D"font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">flags is unclear.&nbsp; I suspect that this=
 is intended to differentiate</span><span style=3D"font-family:&quot;Calibr=
i&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">the two usages described in sections 4.1.1 =
(Point-to-Point) and 4.1.2</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">(Multiple Hops), in which case the parenthe=
sized terms (or similar</span><span style=3D"font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">terminology) should be used with cross-refe=
rences to those two</span><span style=3D"font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">sections.</span><span style=3D"color:black"=
><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, sure will make necessary change=
s, also in the context of earlier comment.</span><span style=3D"color:black=
"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[10] There needs to be a coherent discussio=
n in one place about how</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">SLA advertisement, update and withdrawal wo=
rk.&nbsp; A single ADVERTISE</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">method may suffice on the wire, but the det=
ails on how initial</span><span style=3D"font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">advertisement, subsequent advertisement (up=
date) and withdrawal work</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">need to be specified in one place.&nbsp; Th=
e third paragraph of Section 4</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">is a start on this material, but it's too t=
erse;&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">[Med] That text is terse because we are reusing the BGP mach=
inery for advertising/withdrawing; we only augment
 it with triggers that are linked to the SLA information. A new SLA will le=
ad to an update message with ADVERTISE, an update of an existing SLA will t=
rigger an update message. We do think this information is already present i=
n the document.
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt;This is hard to understand it,=
 as there is no statement that the BGP machinery is being used,
 and the material on SLA usage is spread in different places.&nbsp; I sugge=
st starting section 3 with a discussion of advertisement/update/withdrawal,=
 and how all three are realized via a single ADVERTISE method via BGP UPDAT=
E - this was difficult to figure out
 in reading the current draft.</span><span style=3D"color:black"><o:p></o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">it should be expanded</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br=
>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">into its own subsection, and moved earlier =
to come before the</span><span style=3D"font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">ADVERTISE method in Section 3.2.&nbsp; This=
 text from Section 3.2 should be</span><span style=3D"font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">moved into that new subsection and likewise=
 expanded:</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] Another option is to move it Section 4. From our standpo=
int, we do think it is straightforward to describe the behavior once the at=
tributes format are defined.&nbsp;</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Ok, that&#8217;s an editorial=
 choice - I prefer to explain how something works before defining its
 on-the-wire data format.</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If an adve=
rtised SLA ID is different from earlier advertised</span><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:=
#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">one,</span><span style=3D"font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the same=
 prefix and from the same Source AS, indicates</span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F4=
97D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Source</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AS is advert=
ising new SLA Content to replace the previous one</span><span style=3D"font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; advertised w=
ith the same SLA ID.</span><span style=3D"font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">In addition, I wonder whether functionality=
 should be added to allow</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">withdrawal of an advertisement by specifyin=
g its SLA ID, although that</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">was not part of the original design.</span>=
<span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt;orphans:2;widows:2"><=
span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:bl=
ack">[Med] The reason we didn&#8217;t adopted that design is that we don&#8=
217;t want to make assumptions on which data the remote peer
 will be used for enforcing local actions and also because of this text:</s=
pan><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;c=
olor:black"><o:p></o:p></span></p>
<p class=3D"xmsonormal" style=3D"orphans:2;widows:2"><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Courier New&quot;;color:#212121">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; The SLA ID applies to aggregate traffic to prefixes for a =
given</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"xmsonormal" style=3D"orphans:2;widows:2"><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Courier New&quot;;color:#212121">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; AFI/SAFI that share the same Source AS and SLA ID.</span><=
span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:=
black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; That&#8217;s fine, I wanted to ensu=
re that this had been considered.&nbsp; The discussion of BGP mechanism
 reuse will probably help here.</span><span style=3D"font-size:10.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[11] Notions of context for interpretation =
of all the IPFIX parameters</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">in 3.3.1 need to be added, e.g.:</span><spa=
n style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The first three parameters (DSCP, MPLS EXP field in top label,</span><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-seri=
f&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">802.1q priority) can</span><span style=3D"f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-li=
nk or LSP-by-LSP basis along a traffic's</span><span style=3D"font-size:10.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">network path.</span><span style=3D"font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The IP address parameters are rather likely to be VPN-specific when</span=
><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">there's more</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; than one BGP/MPLS VPN that =
spans or transits the ASs involved.</span><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The transport port parameters need specification of which transport</span=
><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">header and where it</span><span style=3D"fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is located (e.g., for TCP t=
raffic carried by in VXLAN, is this the</span><span style=3D"font-size:10.0=
pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">inner TCP header</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or the outer UDP header in =
VXLAN).</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">There are probably simple approaches to spe=
cifying context in all</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">cases, but that context does need to be spe=
cified ... in all cases.</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] We dind&#8217;t include a context field because we thoug=
ht that the definition of the IPFIX attributes is sufficient by itself, but=
 if you do think it is helpful to have such information,
 we can update the table.</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt;&nbsp; Really???&nbsp; Please =
reread the first comment above:</span><span style=3D"color:black"><o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - The first three parameters (DSCP, MPLS EXP field in top label, 802.1q p=
riority) can</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-li=
nk or LSP-by-LSP basis along a traffic's network path.</span><span style=3D=
"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt;&nbsp; Taking just DSCP, it ca=
n change on a per-link basis, so something has to specify which link
 (between the SLA Producer and SLA Consumer?) is involved.&nbsp; It probabl=
y suffices to say that it&#8217;s the link that crosses the relevant AS bou=
ndary, but that does have to be stated, as it&#8217;s nowhere to be found i=
n the far more general IPFIX registry.</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[12] The security considerations (section 1=
0) are severely incomplete</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">and insufficient:</span><span style=3D"colo=
r:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; I stand by this statement and=
 recommend a complete rewrite of the security considerations.</span><span s=
tyle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- Discussion of possible abuse of this BGP option for</span><span style=3D"=
font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">denial-of-service and theft-of-service,</sp=
an><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs to be added, includin=
g possible countermeasures and</span><span style=3D"font-size:10.0pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">mitigations.</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] This attack vector is not specific to this attribute; th=
is is valid for BGP in general.</span><span style=3D"color:black"><o:p></o:=
p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; There are additional attacks =
enabled by this attribute.</span><span style=3D"color:black"><o:p></o:p></s=
pan></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- This sentence at the end of the second paragraph in Section 10 is</span><=
span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">content-free:</span><span style=3D"font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is NOT=
 RECOMMENDED to enable this attribute at the</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; scale of =
the Internet unless if means to prevent leaking</span><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F=
497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">sensitive</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; informati=
on are enforced.</span><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What exactly is an implemen=
ter or admin supposed to do?&nbsp;</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">[Med] An example of what an admin needs to check if this inf=
ormation can be sent to a given peer or not. Some
 of the content of the attribute contains some sensitive information such a=
s contract Id, classes, etc.</span><span style=3D"color:black"><o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:5.25pt;text-indent:30.75pt">
<span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:black">How does</span><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">one</span><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; figure out whether an imple=
mentation or deployment is&nbsp; &quot;at the</span><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F49=
7D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">scale</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the Internet&quot; ??</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">[Med] The idea here is to avoid leaking such data in to the =
global routing table. Only entitled peers need receive
 such information with controlled scope.</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; I understand the idea - the problem=
 is that I don&#8217;t see specification of what has to be implemented
 in either the text in the draft or the above explanations.</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Th=
e next to last paragraph in section 10 is almost content-free, as</span><sp=
an style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">it leaves</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decisions on implementation=
 and deployment of key security</span><span style=3D"font-size:10.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">functionality as</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;an exercise for the r=
eader&quot; - that's not acceptable.</span><span style=3D"color:black"><o:p=
></o:p></span></p>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-=
size:10.0pt;font-family:&quot;Courier New&quot;;color:black">[Med] I guess =
you are referring to the following text. Validation checks are really deplo=
yment-specific. The text calls out the issue and
 recommends an action; how to translate this action into detailed actions i=
s realty local to a domain</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; The attribute may be advertised by a misbehaving node to communicate</spa=
n><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; SLA parameters that are not aligned with the SLA agreements.&nbsp; Though=
</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; the enforcement of SLA parameters is outside the scope of this</span><spa=
n style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; document, it is RECOMMENDED that the SLA Consumer to enforce a set of</sp=
an><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; validation checks before translating the SLA parameters conveyed in</span=
><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; the QoS attributes into provisioning actions.&nbsp; Such validations MAY<=
/span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; rely on SLA parameters like the origin AS or SLA ID, like generating</spa=
n><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; SLA ID using pseudo-random schemes [<a href=3D"https://tools.ietf.org/htm=
l/rfc4086" target=3D"_blank" title=3D"&quot;Randomness Requirements for Sec=
urity&quot;">RFC4086</a>].</span><span style=3D"color:black"><o:p></o:p></s=
pan></pre>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; I stand by the &#8220;exercis=
e to the reader&#8221; &nbsp;criticism - one way to be honest about this wo=
uld
 be to change the paragraph to:</span><span style=3D"color:black"><o:p></o:=
p></span></p>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o=
:p></o:p></span></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span><span style=3D"color:#212121">The attribute may be advertised by a m=
isbehaving node to communicate</span><span style=3D"color:black"><o:p></o:p=
></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; SLA parameters that are not aligned with the SLA agreements.&nbsp; The</s=
pan><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span style=3D"color:#212121">&nbsp;&nbsp; enforcement of SLA paramete=
rs is outside the scope of this document.</span><span style=3D"color:black"=
><o:p></o:p></span></pre>
<pre><span style=3D"color:#212121">&nbsp;</span><span style=3D"color:black"=
><o:p></o:p></span></pre>
<pre><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;=
color:#1F497D">David&gt; That does not change any normative content of the =
original paragraph.&nbsp; My view is that the &#8220;outside the scope of t=
his document&#8221; statement is wrong because all of these parameters are =
being defined in this draft.</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- Last, but not least, the final paragraph in Section 10 is a joke</span><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">that will</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be lost on a security direc=
torate reviewer - to understand why, see</span><span style=3D"font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 2 of RFC 6919, and =
take note of the publication date of RFC</span><span style=3D"font-size:10.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">6919.</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D"><br>
David&gt; For anyone who didn&#8217;t catch the reference, RFC 6919 is an A=
pril 1 RFC ... and the &#8220;SHOULD BE considered&#8221; language used in =
the last security considerations paragraph of this draft is accurately char=
acterized as vague in Section 2 of RFC 6919:</span><span style=3D"color:bla=
ck"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;text-autospace:none">
<span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot;;color:b=
lack">&nbsp;&nbsp; The phrase &quot;SHOULD CONSIDER&quot; indicates that th=
e authors of the</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;text-autospace:none">
<span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot;;color:b=
lack">&nbsp;&nbsp; specification think that implementations should do somet=
hing, but</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot;;colo=
r:black">&nbsp;&nbsp; they're not sure quite what.</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black">------------------------</span><span style=3D"f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Having noted a dozen major issues, I'll end=
 the review here for now,</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">as I believe a serious revision of the draf=
t is called for, which</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">would be a better starting point to review =
for minor issues and</span><span style=3D"font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">editorial items.</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">-------------------------------------------=
-------------</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">David L. Black, Distinguished Engineer</spa=
n><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Dell EMC, 176 South St., Hopkinton, MA&nbsp=
; 01748</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&#43;1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbs=
p; Cell: &#43;1 (978) 394-7754</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black"><a href=3D"mailto:David.Black@dell.com">Dav=
id.Black@dell.com</a>&nbsp; &lt;=3D=3D=3D NEW =3D=3D=3D</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br=
>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">-------------------------------------------=
-------------</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_CE03DB3D7B45C245BCA0D243277949362F8DD70AMX307CL04corpem_--


From nobody Fri Mar 17 14:57:44 2017
Return-Path: <bob.hinden@gmail.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90FA3129626; Fri, 17 Mar 2017 14:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9JhS43d9cVpy; Fri, 17 Mar 2017 14:57:33 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59D8F12964B; Fri, 17 Mar 2017 14:57:26 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id y76so75366272qkb.0; Fri, 17 Mar 2017 14:57:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=gvrXSvmqcDlquJ0BLz6Dn10E9+COA0RqNahhARl8YTA=; b=OsaarYT/E23XrBQAQ/56gQb8fTlPk1z5YyeFyXhV5hgG+/NRU6k5+MulAYXMA00irV asxmU0pZxLVl3BVKgiV0Oyp3JRO8IhauUfmT4BIiLbOVePhC6jQgYN7n6GJSPktvbhZl 2Sk6gQWIrPPOIrat42b+/GU+liH12A7hZtoq1jX4ZUOCrjvtR1ubzMNQJPZop/jKGB27 lbH1bZyJ3KnskSm94UVUaW3aebCjEbScY/vF62Z7ZIzeYxzx6//OK+6AHfupTzIl8u/o CYtBHCM3nOTruObu4KPTy1EBJQ1k0j+uKY79syGq4FmcVSKgewQdUHhlvwsN23jDweqU EYMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=gvrXSvmqcDlquJ0BLz6Dn10E9+COA0RqNahhARl8YTA=; b=sgG7efm+idqnNhLJlUJZTb/AL2TuHSki6aNDjLll4NNU+g1owQdBycGPBLegMD3Y5P KGlIBXGGyjDbsz51j/p8DGcMZ/UgpY1Ol1eroM8ww58t+MShTMbtM6Sxh+msHzh0NmbE nnk8/XcdDnBE4pB/oQ7h8fn1lRcD7xglVKSmkdK47ZiTU5hr4Ss7KB3wGXzA51XE5934 vz8Ps1Lt+9QCi+NOiUfYbueip+CbkBxQ2vwtdSGrJSpdYoaKX68m8FOZAMjUxnxibQym bLnkBLZdeZWHABRdtbs0TtiGdRIIhAhggvQQLYJD/NScYrdmVCsNnKAOzMVoia1MBdUK Z+2w==
X-Gm-Message-State: AFeK/H0roQTjfS1wmjA9bYpZAzQ4Ywwz5dCUe44t/evbLFKe3uP6N+VO9ZASn6L2geUQ3g==
X-Received: by 10.55.176.135 with SMTP id z129mr11140882qke.308.1489787845442;  Fri, 17 Mar 2017 14:57:25 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id 44sm6840438qts.15.2017.03.17.14.57.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Mar 2017 14:57:24 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <41A44496-F222-40D5-95FE-5CE142C3827F@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_38742971-3019-4F6C-B32C-25B01CAA4AB2"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Fri, 17 Mar 2017 14:57:23 -0700
In-Reply-To: <48bfa3a1-e53c-6b31-69b0-2645ddd5937f@isi.edu>
Cc: Bob Hinden <bob.hinden@gmail.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>,  IESG <iesg@ietf.org>, IPv6 List <ipv6@ietf.org>
To: Joe Touch <touch@isi.edu>
References: <48bfa3a1-e53c-6b31-69b0-2645ddd5937f@isi.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/zw9i3U9nTbXhuiw9aDgYIzVT7hs>
Subject: Re: [Tsv-art] TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Mar 2017 21:57:36 -0000

--Apple-Mail=_38742971-3019-4F6C-B32C-25B01CAA4AB2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Joe,

Thanks for the detailed review.

Several of the reviews have suggested significant changes to this =
document.  The working group was trying to make a few changes to bring =
it into alignment with some changes to rfc2460bis (based on updating =
documents).  It was not attempting a major rewrite when advancing it to =
Internet Standard.  The alternative that the working group discussed was =
to file errata on RFC1981 and leave it to a future document update.

I don=E2=80=99t think many of these changes can be done and still =
advance it to Internet Standard. If we can=E2=80=99t advance the current =
document, then the w.g. may want to just do the errata and withdraw the =
advancement request.  Of course, if people want to work on a revision of =
IPv6 Path MTU Discovery, it would be welcomed, but it won=E2=80=99t be =
able to advanced to Internet Standard.

Comments below.

Thanks,
Bob

> On Feb 15, 2017, at 1:51 PM, Joe Touch <touch@isi.edu> wrote:
>=20
> Document: draft-ietf-6man-rfc1981bis-04
> Reviewer: Joe Touch
> Review Date: February 15, 2017
> IETF LC End Date: March 3, 2017
> IESG Telechat date: February 28, 2017
>=20
> Review result: significant issues
>=20
> NOTE: some of this review is informed by tracking some of the issues =
raised by others on the IETF list, notably Gorry Fairhurst.

In my response to Gorry, I proposed some changes to the document.

>=20
> Major issues:
>=20
> 1) the current text is insufficiently realistic about the (in)ability =
of this mechanism to operate in current networks, regardless of the =
support for generating ICMPs at routers or PMTUD support at endpoints, =
due to ICMP filtering for security reasons. [this comment is already =
being addressed by consensus text]


As far as I can tell, we don=E2=80=99t have much much information on how =
much ICMPv6 PTB messages is filter or not.  It=E2=80=99s clearly a =
problem with IPv4 ICMP PTB, but I haven=E2=80=99t see any recent data =
regarding ICMPv6 PTB messages.  IPv6 deployment has increased =
significantly since the last data I saw and it may or may not be a =
significant problem.


>=20
> 2) the current text is insufficiently clear on on the difference =
between the path MTU, which determines the largest supported IPv6 =
fragment, vs. the effective MTU to receive (EMTU_R), which determines =
the largest IP packet that can transit between the source and =
destination. The document should be more explicit throughput about its =
goal being to manage or avoid IPv6 source fragmentation rather than =
about source to destination packet maximums, and in specific in clearly =
referring to maximum fragments or atomic packets rather than maximum =
packets.
>=20
> E.g.: see the following text, which is incorrect in its current form:
>    Nodes not implementing Path MTU Discovery use the IPv6 minimum link
>    MTU defined in [
> I-D.ietf-6man-rfc2460bis
> ] as the maximum packet size.
>=20
> The value used by either Path MTU Discovery or its default represents =
the path MTU, which is the largest IPv6 *fragment* (or atomic packet, =
see RFC6864) that can be supported on the path between the endpoints. =
The maximum IP packet size is limited by the effective MTU to receive =
(EMTU_R) [RFC1122], which is at least 1500 bytes for IPv6 and not =
necessarily related to the link MTUs. The text should also clearly =
indicate that there is no ICMP mechanism for determining larger EMTU_R =
support.
>=20
> E.g., the following text is also incorrect in its current form:
>    The value sent in the TCP MSS option is independent of the PMTU.
>    This MSS option value is used by the other end of the connection,
>    which may be using an unrelated PMTU value.
>=20
> The first sentence is correct because TCP MSS is related to EMTU_R =
(and needs to account for headers, as per RFC6691), and EMTU_R is not =
directly related to the PMTU (except that it would never be smaller than =
the PMTU). The MSS option is calculated from EMTU_R, not PMTU.
>=20
> In addition, it should be noted that ICMPv6 PTB messages are NOT sent =
when source fragmentation is enabled.

I think these are all good issues to cover in a rewrite, but I don=E2=80=99=
t see how they can be done now.

>=20
> 3. need verification of current support for some features, esp. =
regarding TCP and NFS interactions
> See Gorry's note of 2/14/17

Please see my responses to his review.

>=20
> 4. the concept of a single path MTU value between two IP addresses =
does not account for multipath routing, e.g., ECMP (as currently =
deployed, noted in RFC7690, which should be cited) or BANANA (and its =
solutions in development) See Fred Templin's posts on this on 2/15/17
>=20
> Minor issues:
>=20
> - some of the updates and/or current text could be updated to reflect =
current terminology or practice. See Gorry Fairhursts's post of 2/14/17

I suggest some changes to address some of the issues he raised.

>=20
> - fragmentation, while considered harmful and costly, is absolutely =
necessary to support tunnels even in the presence of PMTUD. The text on =
this issue should reflect this reality.
>=20
> - the requirement that transports be notified of PTB messages might =
usefully cite the corresponding IPv4, TCP, and UDP sections of RFC1122

I think that is doable.  Please suggest some specific text.


> - section 5.4 should cite and include context from RFC6691, especially =
including a discussion of the impact of variable IP EHs on the =
interaction between TCP MSS and ICMP PTB
>=20

Please suggest some specific text.




> --
>=20
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_38742971-3019-4F6C-B32C-25B01CAA4AB2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJYzFvDAAoJEK7rdBF357uoSjkIAIjGKuseXIpuNUhVZAmaB1yx
qbXo7IkDYJBxKV/m83MqPhK789nHnbsRGXQbCdijaDZAPWgDiaQDZTw5Cwn2jaLU
US8CivNAdlnyOJDFaRiNZPa3M9jRorJxle2D4bTSKtskGCt2gH64+sM/HmY46xUe
UBGfaVYjLsV2vNh1PDGKYUS6nNV8sfN83bR0/RqDxNi32mRb3kz70K/3AbJGsC6Q
NXKVd7VrdcSxsX4vC+6zYp+OCJVO+1JUBnc0SyJ7Qquv8cIM2g9SjrqtcjncEe5f
hL12J+tZ4btzQEQElqo8hEhsJVRCoCoCBjLJQLU8CoNbm587NR1EL9v7rSwtOUs=
=4S38
-----END PGP SIGNATURE-----

--Apple-Mail=_38742971-3019-4F6C-B32C-25B01CAA4AB2--


From nobody Fri Mar 17 15:55:07 2017
Return-Path: <touch@isi.edu>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF5DC12955D; Fri, 17 Mar 2017 15:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0i2H_BtqcFfD; Fri, 17 Mar 2017 15:55:04 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA902127419; Fri, 17 Mar 2017 15:55:04 -0700 (PDT)
Received: from [128.9.184.195] ([128.9.184.195]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v2HMsj94026678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 17 Mar 2017 15:54:46 -0700 (PDT)
To: Bob Hinden <bob.hinden@gmail.com>
References: <48bfa3a1-e53c-6b31-69b0-2645ddd5937f@isi.edu> <41A44496-F222-40D5-95FE-5CE142C3827F@gmail.com>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, IESG <iesg@ietf.org>, IPv6 List <ipv6@ietf.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <46d7ae23-cf3d-570d-3d79-9d915663cf16@isi.edu>
Date: Fri, 17 Mar 2017 15:54:46 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <41A44496-F222-40D5-95FE-5CE142C3827F@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-MailScanner-ID: v2HMsj94026678
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/jXqU59z38NWS4TwsEgEnpoRLAFU>
Subject: Re: [Tsv-art] TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Mar 2017 22:55:07 -0000

Hi, Bob (et al.),

Although I appreciate the goal of avoiding a major rewrite, I cannot see
how to advance this document with these substantive errors intact.
Moving forward in its current state propagates these errors.

Note that there are also two points below that you did not address:

- item #4 about ECMP

- the minor issue bullet point about the need for fragmentation

I'll hold off suggesting text as requested below until you decide how to
proceed.

Joe


On 3/17/2017 2:57 PM, Bob Hinden wrote:
> Joe,
>
> Thanks for the detailed review.
>
> Several of the reviews have suggested significant changes to this docum=
ent.  The working group was trying to make a few changes to bring it into=
 alignment with some changes to rfc2460bis (based on updating documents).=
  It was not attempting a major rewrite when advancing it to Internet Sta=
ndard.  The alternative that the working group discussed was to file erra=
ta on RFC1981 and leave it to a future document update.
>
> I don=E2=80=99t think many of these changes can be done and still advan=
ce it to Internet Standard. If we can=E2=80=99t advance the current docum=
ent, then the w.g. may want to just do the errata and withdraw the advanc=
ement request.  Of course, if people want to work on a revision of IPv6 P=
ath MTU Discovery, it would be welcomed, but it won=E2=80=99t be able to =
advanced to Internet Standard.
>
> Comments below.
>
> Thanks,
> Bob
>
>> On Feb 15, 2017, at 1:51 PM, Joe Touch <touch@isi.edu> wrote:
>>
>> Document: draft-ietf-6man-rfc1981bis-04
>> Reviewer: Joe Touch
>> Review Date: February 15, 2017
>> IETF LC End Date: March 3, 2017
>> IESG Telechat date: February 28, 2017
>>
>> Review result: significant issues
>>
>> NOTE: some of this review is informed by tracking some of the issues r=
aised by others on the IETF list, notably Gorry Fairhurst.
> In my response to Gorry, I proposed some changes to the document.
>
>> Major issues:
>>
>> 1) the current text is insufficiently realistic about the (in)ability =
of this mechanism to operate in current networks, regardless of the suppo=
rt for generating ICMPs at routers or PMTUD support at endpoints, due to =
ICMP filtering for security reasons. [this comment is already being addre=
ssed by consensus text]
>
> As far as I can tell, we don=E2=80=99t have much much information on ho=
w much ICMPv6 PTB messages is filter or not.  It=E2=80=99s clearly a prob=
lem with IPv4 ICMP PTB, but I haven=E2=80=99t see any recent data regardi=
ng ICMPv6 PTB messages.  IPv6 deployment has increased significantly sinc=
e the last data I saw and it may or may not be a significant problem.
>
>
>> 2) the current text is insufficiently clear on on the difference betwe=
en the path MTU, which determines the largest supported IPv6 fragment, vs=
=2E the effective MTU to receive (EMTU_R), which determines the largest I=
P packet that can transit between the source and destination. The documen=
t should be more explicit throughput about its goal being to manage or av=
oid IPv6 source fragmentation rather than about source to destination pac=
ket maximums, and in specific in clearly referring to maximum fragments o=
r atomic packets rather than maximum packets.
>>
>> E.g.: see the following text, which is incorrect in its current form:
>>    Nodes not implementing Path MTU Discovery use the IPv6 minimum link=

>>    MTU defined in [
>> I-D.ietf-6man-rfc2460bis
>> ] as the maximum packet size.
>>
>> The value used by either Path MTU Discovery or its default represents =
the path MTU, which is the largest IPv6 *fragment* (or atomic packet, see=
 RFC6864) that can be supported on the path between the endpoints. The ma=
ximum IP packet size is limited by the effective MTU to receive (EMTU_R) =
[RFC1122], which is at least 1500 bytes for IPv6 and not necessarily rela=
ted to the link MTUs. The text should also clearly indicate that there is=
 no ICMP mechanism for determining larger EMTU_R support.
>>
>> E.g., the following text is also incorrect in its current form:
>>    The value sent in the TCP MSS option is independent of the PMTU.
>>    This MSS option value is used by the other end of the connection,
>>    which may be using an unrelated PMTU value.
>>
>> The first sentence is correct because TCP MSS is related to EMTU_R (an=
d needs to account for headers, as per RFC6691), and EMTU_R is not direct=
ly related to the PMTU (except that it would never be smaller than the PM=
TU). The MSS option is calculated from EMTU_R, not PMTU.
>>
>> In addition, it should be noted that ICMPv6 PTB messages are NOT sent =
when source fragmentation is enabled.
> I think these are all good issues to cover in a rewrite, but I don=E2=80=
=99t see how they can be done now.
>
>> 3. need verification of current support for some features, esp. regard=
ing TCP and NFS interactions
>> See Gorry's note of 2/14/17
> Please see my responses to his review.
>
>> 4. the concept of a single path MTU value between two IP addresses doe=
s not account for multipath routing, e.g., ECMP (as currently deployed, n=
oted in RFC7690, which should be cited) or BANANA (and its solutions in d=
evelopment) See Fred Templin's posts on this on 2/15/17
>>
>> Minor issues:
>>
>> - some of the updates and/or current text could be updated to reflect =
current terminology or practice. See Gorry Fairhursts's post of 2/14/17
> I suggest some changes to address some of the issues he raised.
>
>> - fragmentation, while considered harmful and costly, is absolutely ne=
cessary to support tunnels even in the presence of PMTUD. The text on thi=
s issue should reflect this reality.
>>
>> - the requirement that transports be notified of PTB messages might us=
efully cite the corresponding IPv4, TCP, and UDP sections of RFC1122
> I think that is doable.  Please suggest some specific text.
>
>
>> - section 5.4 should cite and include context from RFC6691, especially=
 including a discussion of the impact of variable IP EHs on the interacti=
on between TCP MSS and ICMP PTB
>>
> Please suggest some specific text.
>
>
>
>
>> --
>>
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------



From nobody Fri Mar 17 16:31:46 2017
Return-Path: <bob.hinden@gmail.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE03C12955D; Fri, 17 Mar 2017 16:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n92xgTLhk1yH; Fri, 17 Mar 2017 16:31:36 -0700 (PDT)
Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4F3C127419; Fri, 17 Mar 2017 16:31:36 -0700 (PDT)
Received: by mail-qt0-x22f.google.com with SMTP id i34so74652870qtc.0; Fri, 17 Mar 2017 16:31:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=P3kh5vmzno6W3bkaQjzPsLbPzLVzrDaccTzCh3Z/Puk=; b=Z5/8h26rd2OSNRjnEnu/Nam+wi7vLTamEumOT2T7L6z+5HtSNGeLRqdTH1JzRZJ4iJ bO4X/odOkBF/5fXRbwG76XHT4af9KwxTijWoPqxe91EWXrsUSVAt0w7qZIuLG9RV8W6J Zr9l3SpUi7XN1sfo4toKxk80Mu1DVOnNLwFwodMcg7NNLSpuuxa0IUn29G+m3gicE/c1 BDhyRnRO7ixm0dIzv9ZnpbbixNgK7HmuWslcNo4xnwDVrtHl6uQijF3YynzXfYal/VM6 TG+r1T3PzHSnFYgLDCBORDkHCyJbx/UoJbs8jPN5g6yW6mMFkZKyGRX9d5Y9mROGbkqW UwOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=P3kh5vmzno6W3bkaQjzPsLbPzLVzrDaccTzCh3Z/Puk=; b=JeURKBvFzff91FVV/F493zdlx16XFwfzoFNEyqr85bRVId2aOitgkSIETuKB8aa4qn 5p86O8vqLw7x/10GIt26Z/6w56TVI5jhuXXj6CkRmkAD79Bl5M/oORWWtTkXE0zyrg/n w2aobqvcfyteTFsm0OYyZd82XkcLEe9qp2+kVsV3pftx40ctwyh97gHHdtwoiZhho1FR agmp1gt0PU+GHtvtICCcCZYqKR5+sDRh7cutdCUeTyBJgjL1Y8a5mkG80IJRtOaaPaPG D0Y8rblk5/xmf7Eq863XCOz5sY8OlqzzVoEz/m+K1Gn3nORnoJS1mlZgEmiju6DqXPlw 835w==
X-Gm-Message-State: AFeK/H1CSvWhF0aGlqXXLcE+F2HNtmSFTXNvkKiXfpCkiVjYswuzlYF8kmzycuMGlmMH/g==
X-Received: by 10.200.55.82 with SMTP id p18mr10438020qtb.285.1489793495725; Fri, 17 Mar 2017 16:31:35 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id g143sm1292831qke.58.2017.03.17.16.31.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Mar 2017 16:31:34 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <8D6CA1F7-CB01-4FCD-B81C-ECBEFC088EAE@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_7CD741D0-B121-4CF5-9FE3-E64C534B4913"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Fri, 17 Mar 2017 16:31:32 -0700
In-Reply-To: <46d7ae23-cf3d-570d-3d79-9d915663cf16@isi.edu>
Cc: Bob Hinden <bob.hinden@gmail.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>,  IESG <iesg@ietf.org>, IPv6 List <ipv6@ietf.org>
To: Joe Touch <touch@isi.edu>
References: <48bfa3a1-e53c-6b31-69b0-2645ddd5937f@isi.edu> <41A44496-F222-40D5-95FE-5CE142C3827F@gmail.com> <46d7ae23-cf3d-570d-3d79-9d915663cf16@isi.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/TEUWUwVxz6XAIerplWRGyT9IdJk>
Subject: Re: [Tsv-art] TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Mar 2017 23:31:39 -0000

--Apple-Mail=_7CD741D0-B121-4CF5-9FE3-E64C534B4913
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Joe,

I think this will be up to the AD and IESG.

If you (and others) want to work on a major update, I am happy to share =
the XML.  I hope we don=E2=80=99t end up with can=E2=80=99t move the =
current document forward, and no one wants to do a major update.

Thanks,
Bob

> On Mar 17, 2017, at 3:54 PM, Joe Touch <touch@isi.edu> wrote:
>=20
> Hi, Bob (et al.),
>=20
> Although I appreciate the goal of avoiding a major rewrite, I cannot =
see
> how to advance this document with these substantive errors intact.
> Moving forward in its current state propagates these errors.
>=20
> Note that there are also two points below that you did not address:
>=20
> - item #4 about ECMP
>=20
> - the minor issue bullet point about the need for fragmentation
>=20
> I'll hold off suggesting text as requested below until you decide how =
to
> proceed.
>=20
> Joe
>=20
>=20
> On 3/17/2017 2:57 PM, Bob Hinden wrote:
>> Joe,
>>=20
>> Thanks for the detailed review.
>>=20
>> Several of the reviews have suggested significant changes to this =
document.  The working group was trying to make a few changes to bring =
it into alignment with some changes to rfc2460bis (based on updating =
documents).  It was not attempting a major rewrite when advancing it to =
Internet Standard.  The alternative that the working group discussed was =
to file errata on RFC1981 and leave it to a future document update.
>>=20
>> I don=E2=80=99t think many of these changes can be done and still =
advance it to Internet Standard. If we can=E2=80=99t advance the current =
document, then the w.g. may want to just do the errata and withdraw the =
advancement request.  Of course, if people want to work on a revision of =
IPv6 Path MTU Discovery, it would be welcomed, but it won=E2=80=99t be =
able to advanced to Internet Standard.
>>=20
>> Comments below.
>>=20
>> Thanks,
>> Bob
>>=20
>>> On Feb 15, 2017, at 1:51 PM, Joe Touch <touch@isi.edu> wrote:
>>>=20
>>> Document: draft-ietf-6man-rfc1981bis-04
>>> Reviewer: Joe Touch
>>> Review Date: February 15, 2017
>>> IETF LC End Date: March 3, 2017
>>> IESG Telechat date: February 28, 2017
>>>=20
>>> Review result: significant issues
>>>=20
>>> NOTE: some of this review is informed by tracking some of the issues =
raised by others on the IETF list, notably Gorry Fairhurst.
>> In my response to Gorry, I proposed some changes to the document.
>>=20
>>> Major issues:
>>>=20
>>> 1) the current text is insufficiently realistic about the =
(in)ability of this mechanism to operate in current networks, regardless =
of the support for generating ICMPs at routers or PMTUD support at =
endpoints, due to ICMP filtering for security reasons. [this comment is =
already being addressed by consensus text]
>>=20
>> As far as I can tell, we don=E2=80=99t have much much information on =
how much ICMPv6 PTB messages is filter or not.  It=E2=80=99s clearly a =
problem with IPv4 ICMP PTB, but I haven=E2=80=99t see any recent data =
regarding ICMPv6 PTB messages.  IPv6 deployment has increased =
significantly since the last data I saw and it may or may not be a =
significant problem.
>>=20
>>=20
>>> 2) the current text is insufficiently clear on on the difference =
between the path MTU, which determines the largest supported IPv6 =
fragment, vs. the effective MTU to receive (EMTU_R), which determines =
the largest IP packet that can transit between the source and =
destination. The document should be more explicit throughput about its =
goal being to manage or avoid IPv6 source fragmentation rather than =
about source to destination packet maximums, and in specific in clearly =
referring to maximum fragments or atomic packets rather than maximum =
packets.
>>>=20
>>> E.g.: see the following text, which is incorrect in its current =
form:
>>>   Nodes not implementing Path MTU Discovery use the IPv6 minimum =
link
>>>   MTU defined in [
>>> I-D.ietf-6man-rfc2460bis
>>> ] as the maximum packet size.
>>>=20
>>> The value used by either Path MTU Discovery or its default =
represents the path MTU, which is the largest IPv6 *fragment* (or atomic =
packet, see RFC6864) that can be supported on the path between the =
endpoints. The maximum IP packet size is limited by the effective MTU to =
receive (EMTU_R) [RFC1122], which is at least 1500 bytes for IPv6 and =
not necessarily related to the link MTUs. The text should also clearly =
indicate that there is no ICMP mechanism for determining larger EMTU_R =
support.
>>>=20
>>> E.g., the following text is also incorrect in its current form:
>>>   The value sent in the TCP MSS option is independent of the PMTU.
>>>   This MSS option value is used by the other end of the connection,
>>>   which may be using an unrelated PMTU value.
>>>=20
>>> The first sentence is correct because TCP MSS is related to EMTU_R =
(and needs to account for headers, as per RFC6691), and EMTU_R is not =
directly related to the PMTU (except that it would never be smaller than =
the PMTU). The MSS option is calculated from EMTU_R, not PMTU.
>>>=20
>>> In addition, it should be noted that ICMPv6 PTB messages are NOT =
sent when source fragmentation is enabled.
>> I think these are all good issues to cover in a rewrite, but I =
don=E2=80=99t see how they can be done now.
>>=20
>>> 3. need verification of current support for some features, esp. =
regarding TCP and NFS interactions
>>> See Gorry's note of 2/14/17
>> Please see my responses to his review.
>>=20
>>> 4. the concept of a single path MTU value between two IP addresses =
does not account for multipath routing, e.g., ECMP (as currently =
deployed, noted in RFC7690, which should be cited) or BANANA (and its =
solutions in development) See Fred Templin's posts on this on 2/15/17
>>>=20
>>> Minor issues:
>>>=20
>>> - some of the updates and/or current text could be updated to =
reflect current terminology or practice. See Gorry Fairhursts's post of =
2/14/17
>> I suggest some changes to address some of the issues he raised.
>>=20
>>> - fragmentation, while considered harmful and costly, is absolutely =
necessary to support tunnels even in the presence of PMTUD. The text on =
this issue should reflect this reality.
>>>=20
>>> - the requirement that transports be notified of PTB messages might =
usefully cite the corresponding IPv4, TCP, and UDP sections of RFC1122
>> I think that is doable.  Please suggest some specific text.
>>=20
>>=20
>>> - section 5.4 should cite and include context from RFC6691, =
especially including a discussion of the impact of variable IP EHs on =
the interaction between TCP MSS and ICMP PTB
>>>=20
>> Please suggest some specific text.
>>=20
>>=20
>>=20
>>=20
>>> --
>>>=20
>>>=20
>>>=20
>>>=20
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>=20
>=20


--Apple-Mail=_7CD741D0-B121-4CF5-9FE3-E64C534B4913
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJYzHHUAAoJEK7rdBF357uo3GcH/jgaDZirgLr/JBK0UOgCJ7ty
f2eChUEe4LHSOCBbZetm1WKb+xC89MWmvCUEDjakAJ9eC36dXIIie5cGrCZl5Q8n
eP4F9X4Xh2ROavU+o1CjP1XSfGCtbreY03j9ZiK4Pee32uJY+gj/edWIxvvoM8r+
0xkECuLu+euYR6Yg/w/+Tu2AoYSWLaQH/pkxyUN+YKSaR1Hk5P2iCw3oxyslb5L9
8q830RMCgTaeUPynAm/jYV29iQYlGD6zGFVuYeDkQjbPdHcM2K2gX+s9mc616xzi
GXxJjStgfhyKG5Gdn+UAXnHpOlJlGYUXluwgFxptbV/DFXwDAuiTGcPusudsvLA=
=aTsp
-----END PGP SIGNATURE-----

--Apple-Mail=_7CD741D0-B121-4CF5-9FE3-E64C534B4913--


From nobody Fri Mar 17 17:36:44 2017
Return-Path: <touch@isi.edu>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E571129630; Fri, 17 Mar 2017 17:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TlnkGvLfMqOs; Fri, 17 Mar 2017 17:36:35 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9755912966D; Fri, 17 Mar 2017 17:36:30 -0700 (PDT)
Received: from [128.9.184.195] ([128.9.184.195]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v2I0aEnw029134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 17 Mar 2017 17:36:14 -0700 (PDT)
To: Bob Hinden <bob.hinden@gmail.com>
References: <48bfa3a1-e53c-6b31-69b0-2645ddd5937f@isi.edu> <41A44496-F222-40D5-95FE-5CE142C3827F@gmail.com> <46d7ae23-cf3d-570d-3d79-9d915663cf16@isi.edu> <8D6CA1F7-CB01-4FCD-B81C-ECBEFC088EAE@gmail.com>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, IESG <iesg@ietf.org>, IPv6 List <ipv6@ietf.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <e55e095b-b5c6-56e8-d4be-0b438c61ae67@isi.edu>
Date: Fri, 17 Mar 2017 17:36:14 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <8D6CA1F7-CB01-4FCD-B81C-ECBEFC088EAE@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-MailScanner-ID: v2I0aEnw029134
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/oLiTa08tXKBmH1k37MOJwMicqMQ>
Subject: Re: [Tsv-art] TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Mar 2017 00:36:37 -0000

On 3/17/2017 4:31 PM, Bob Hinden wrote:
> Joe,
>
> I think this will be up to the AD and IESG.
OK - I'll wait for them to respond.
> If you (and others) want to work on a major update, I am happy to share the XML.  I hope we don’t end up with can’t move the current document forward, and no one wants to do a major update.
I'd certainly prefer to have this doc address these issues.

One question - if a major update occurred, would that be at the same
standard level? If so, and if these issues are of concern, I'd be glad
to take that on.

If a major rev is a standards-level setback, that would be less useful.

I'd like to hear their views...

Joe


From nobody Sat Mar 18 09:03:29 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 079D31288B8; Sat, 18 Mar 2017 09:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HhLKRg6aFsOY; Sat, 18 Mar 2017 09:03:18 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66529127201; Sat, 18 Mar 2017 09:03:18 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id o4so69445853ywd.3; Sat, 18 Mar 2017 09:03:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CYd41GsBRU9bg4nbp8k6MK5Nn2nw0NHjuswljVs6zeA=; b=Tz/btiUWz1EgG1o9Mx1uIBEY6Rzrt3cxLJL8Fm1jW1kCs2uY4vQQuPUrN0ZBxWwVMo s09vALZmrnHi5k4fz8OOdMS7o2GpN9R2o8u/3OFjoe763vkh/zVkBVzGlRo/lK7fd2AF v/SDIqV28EqXdG9jGrKwnhil8wUXEeLyC2UaMEiVLDBlLFm9e+0iNPqITHAKFPj7Fs71 QnXoP50GlnS7E8ryoXA+hbki/PCIGzPqmsEouJW0DWNPqaZ0drtA1aNjX52W4Fc7PXO/ CqmFyXpbbkimBPlugWWK9sJb2nrGQEES7hq9ETfN7PKzF9qAUEeKoyA3VEHZ8qZwdWRt nVXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CYd41GsBRU9bg4nbp8k6MK5Nn2nw0NHjuswljVs6zeA=; b=TNDzWG6YFsGVLVlRKhYo2RHlF0Z8nxGG8Gt2C5fjvuu6kprY794eIOPjkySm6jM8oD NI8UXN+7VtPUxbCJtaalAwJuAPNa5rStWQIJw/4P1/UBjkQZFsk8xUfw0x8qRkoekFsV OKE0f+iHBF9HHVa6LT91id/6HUtP0i8559ulQisAXxEndTxrNgEFmJUVPpuG1MKmWQDb cDIiiHcQ/aSOU91z4s5jNeRU+jLuoRWWI91at8u9kO+CfaGiCWDBpwlXjjIao39Xs0jb yFzGyGzut/KSWST4F0/u8X+/6httRk7fuRAA3W1EpkfRpQwFVmw1/5baFRxvQ73Z3pb4 c68Q==
X-Gm-Message-State: AFeK/H0+bOucIxMfI2TBFkXROxsLErNiLEF1+Rk3rgRqQCzOBh62BYD+9ApHxYLzvu94/SPwWbq6v2lghSfS7A==
X-Received: by 10.37.125.196 with SMTP id y187mr8460939ybc.22.1489852997496; Sat, 18 Mar 2017 09:03:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.77.197 with HTTP; Sat, 18 Mar 2017 09:03:17 -0700 (PDT)
Received: by 10.37.77.197 with HTTP; Sat, 18 Mar 2017 09:03:17 -0700 (PDT)
In-Reply-To: <e55e095b-b5c6-56e8-d4be-0b438c61ae67@isi.edu>
References: <48bfa3a1-e53c-6b31-69b0-2645ddd5937f@isi.edu> <41A44496-F222-40D5-95FE-5CE142C3827F@gmail.com> <46d7ae23-cf3d-570d-3d79-9d915663cf16@isi.edu> <8D6CA1F7-CB01-4FCD-B81C-ECBEFC088EAE@gmail.com> <e55e095b-b5c6-56e8-d4be-0b438c61ae67@isi.edu>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sat, 18 Mar 2017 11:03:17 -0500
Message-ID: <CAKKJt-eqbA65wiyP575Kbni4b31Jo37uZ0n=0UGn62A_n30H8Q@mail.gmail.com>
To: Joe Touch <touch@isi.edu>
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, IESG <iesg@ietf.org>,  "tsv-art@ietf.org" <tsv-art@ietf.org>
Content-Type: multipart/alternative; boundary=001a114dd3c6aefbf8054b036e4c
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/uCaLtPU6p_BQZdGfwF0EemI7x2E>
Subject: Re: [Tsv-art] TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Mar 2017 16:03:21 -0000

--001a114dd3c6aefbf8054b036e4c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I may not be answering the question Joe asked, but ...

On Mar 17, 2017 19:36, "Joe Touch" <touch@isi.edu> wrote:



On 3/17/2017 4:31 PM, Bob Hinden wrote:
> Joe,
>
> I think this will be up to the AD and IESG.
OK - I'll wait for them to respond.
> If you (and others) want to work on a major update, I am happy to share
the XML.  I hope we don=E2=80=99t end up with can=E2=80=99t move the curren=
t document
forward, and no one wants to do a major update.
I'd certainly prefer to have this doc address these issues.

One question - if a major update occurred, would that be at the same
standard level? If so, and if these issues are of concern, I'd be glad
to take that on.

If a major rev is a standards-level setback, that would be less useful.

I'd like to hear their views...


So, RFC 1981 is a Draft Standard, which is theoretically a bigger deal than
a Proposed Standard. If a replacement to RFC 1981 doesn't work the same way
that RFC 1981 works, I don't see how it would also be a Draft Standard,
based on the standards level of the RFC it would be replacing. Do others
see something I'm missing?

However.

Assuming that a replacement for RFC 1981 Path MTU Discovery doesn't have
the issues we've been talking about in these threads, I would hope that we
could publish that replacement at Proposed Standard (not at Experimental).

Given that we don't use the Draft Standard level for advancing standards
track RFCs any more (post https://datatracker.ietf.org/doc/rfc6410/), would
publishing a replacement that works better than RFC 1981 at Proposed
Standard be a bad thing?

Curiously yours,

Spencer


Joe

_______________________________________________
Tsv-art mailing list
Tsv-art@ietf.org
https://www.ietf.org/mailman/listinfo/tsv-art

--001a114dd3c6aefbf8054b036e4c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>I may not be answering the question Joe asked, but .=
..<br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mar 17, =
2017 19:36, &quot;Joe Touch&quot; &lt;<a href=3D"mailto:touch@isi.edu">touc=
h@isi.edu</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
div class=3D"quoted-text"><br>
<br>
On 3/17/2017 4:31 PM, Bob Hinden wrote:<br>
&gt; Joe,<br>
&gt;<br>
</div><div class=3D"quoted-text">&gt; I think this will be up to the AD and=
 IESG.<br>
</div>OK - I&#39;ll wait for them to respond.<br>
<div class=3D"quoted-text">&gt; If you (and others) want to work on a major=
 update, I am happy to share the XML.=C2=A0 I hope we don=E2=80=99t end up =
with can=E2=80=99t move the current document forward, and no one wants to d=
o a major update.<br>
</div>I&#39;d certainly prefer to have this doc address these issues.<br>
<br>
One question - if a major update occurred, would that be at the same<br>
standard level? If so, and if these issues are of concern, I&#39;d be glad<=
br>
to take that on.<br>
<br>
If a major rev is a standards-level setback, that would be less useful.<br>
<br>
I&#39;d like to hear their views...<br></blockquote></div></div></div><div =
dir=3D"auto"><br></div><div dir=3D"auto">So, RFC 1981 is a Draft Standard, =
which is theoretically a bigger deal than a Proposed Standard. If a replace=
ment to RFC 1981 doesn&#39;t work the same way that RFC 1981 works, I don&#=
39;t see how it would also be a Draft Standard, based on the standards leve=
l of the RFC it would be replacing. Do others see something I&#39;m missing=
?</div><div dir=3D"auto"><br></div><div dir=3D"auto">However.</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">Assuming that a replacement for RFC 1=
981 Path MTU Discovery doesn&#39;t have the issues we&#39;ve been talking a=
bout in these threads, I would hope that we could publish that replacement =
at Proposed Standard (not at Experimental).</div><div dir=3D"auto"><br></di=
v><div dir=3D"auto">Given that we don&#39;t use the Draft Standard level fo=
r advancing standards track RFCs any more (post <a href=3D"https://datatrac=
ker.ietf.org/doc/rfc6410/">https://datatracker.ietf.org/doc/rfc6410/</a>), =
would publishing a replacement that works better than RFC 1981 at Proposed =
Standard be a bad thing?</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>Curiously yours,</div><div dir=3D"auto"><br></div><div dir=3D"auto">Spence=
r</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_ex=
tra"><div class=3D"gmail_quote"><blockquote class=3D"quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font color=3D"#888888"><br>
Joe<br>
</font><div class=3D"elided-text"><br>
______________________________<wbr>_________________<br>
Tsv-art mailing list<br>
<a href=3D"mailto:Tsv-art@ietf.org">Tsv-art@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tsv-art" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tsv-art</a><=
br>
</div></blockquote></div><br></div></div></div>

--001a114dd3c6aefbf8054b036e4c--


From nobody Sat Mar 18 09:27:55 2017
Return-Path: <touch@isi.edu>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05ABA1288B8; Sat, 18 Mar 2017 09:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mPzjNrrtT4KO; Sat, 18 Mar 2017 09:27:36 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2D2F1277BB; Sat, 18 Mar 2017 09:27:36 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v2IGQgkX011175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 18 Mar 2017 09:26:44 -0700 (PDT)
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
References: <48bfa3a1-e53c-6b31-69b0-2645ddd5937f@isi.edu> <41A44496-F222-40D5-95FE-5CE142C3827F@gmail.com> <46d7ae23-cf3d-570d-3d79-9d915663cf16@isi.edu> <8D6CA1F7-CB01-4FCD-B81C-ECBEFC088EAE@gmail.com> <e55e095b-b5c6-56e8-d4be-0b438c61ae67@isi.edu> <CAKKJt-eqbA65wiyP575Kbni4b31Jo37uZ0n=0UGn62A_n30H8Q@mail.gmail.com>
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, IESG <iesg@ietf.org>, "tsv-art@ietf.org" <tsv-art@ietf.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <01fc4067-6825-9343-7735-86f9bf77bebe@isi.edu>
Date: Sat, 18 Mar 2017 09:26:43 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAKKJt-eqbA65wiyP575Kbni4b31Jo37uZ0n=0UGn62A_n30H8Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------6F495733573D7217B70CDADB"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/u5ejEUlazc2XlH4kJSVYgSMi8V4>
Subject: Re: [Tsv-art] TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Mar 2017 16:27:39 -0000

This is a multi-part message in MIME format.
--------------6F495733573D7217B70CDADB
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

FWIW, I was thinking of an update that focused on the description issue
below.

Nothing functionally would change.

Joe


On 3/18/2017 9:03 AM, Spencer Dawkins at IETF wrote:
> I may not be answering the question Joe asked, but ...
>
> On Mar 17, 2017 19:36, "Joe Touch" <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>
>
>
>     On 3/17/2017 4:31 PM, Bob Hinden wrote:
>     > Joe,
>     >
>     > I think this will be up to the AD and IESG.
>     OK - I'll wait for them to respond.
>     > If you (and others) want to work on a major update, I am happy
>     to share the XML.  I hope we don’t end up with can’t move the
>     current document forward, and no one wants to do a major update.
>     I'd certainly prefer to have this doc address these issues.
>
>     One question - if a major update occurred, would that be at the same
>     standard level? If so, and if these issues are of concern, I'd be glad
>     to take that on.
>
>     If a major rev is a standards-level setback, that would be less
>     useful.
>
>     I'd like to hear their views...
>
>
> So, RFC 1981 is a Draft Standard, which is theoretically a bigger deal
> than a Proposed Standard. If a replacement to RFC 1981 doesn't work
> the same way that RFC 1981 works, I don't see how it would also be a
> Draft Standard, based on the standards level of the RFC it would be
> replacing. Do others see something I'm missing?
>
> However.
>
> Assuming that a replacement for RFC 1981 Path MTU Discovery doesn't
> have the issues we've been talking about in these threads, I would
> hope that we could publish that replacement at Proposed Standard (not
> at Experimental).
>
> Given that we don't use the Draft Standard level for advancing
> standards track RFCs any more (post
> https://datatracker.ietf.org/doc/rfc6410/), would publishing a
> replacement that works better than RFC 1981 at Proposed Standard be a
> bad thing?
>
> Curiously yours,
>
> Spencer
>
>
>     Joe
>
>     _______________________________________________
>     Tsv-art mailing list
>     Tsv-art@ietf.org <mailto:Tsv-art@ietf.org>
>     https://www.ietf.org/mailman/listinfo/tsv-art
>     <https://www.ietf.org/mailman/listinfo/tsv-art>
>
>


--------------6F495733573D7217B70CDADB
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>FWIW, I was thinking of an update that focused on the description
      issue below.</p>
    <p>Nothing functionally would change.</p>
    <p>Joe<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 3/18/2017 9:03 AM, Spencer Dawkins
      at IETF wrote:<br>
    </div>
    <blockquote
cite="mid:CAKKJt-eqbA65wiyP575Kbni4b31Jo37uZ0n=0UGn62A_n30H8Q@mail.gmail.com"
      type="cite">
      <div dir="auto">
        <div>I may not be answering the question Joe asked, but ...<br>
          <div class="gmail_extra"><br>
            <div class="gmail_quote">On Mar 17, 2017 19:36, "Joe Touch"
              &lt;<a moz-do-not-send="true" href="mailto:touch@isi.edu">touch@isi.edu</a>&gt;
              wrote:<br type="attribution">
              <blockquote class="quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div class="quoted-text"><br>
                  <br>
                  On 3/17/2017 4:31 PM, Bob Hinden wrote:<br>
                  &gt; Joe,<br>
                  &gt;<br>
                </div>
                <div class="quoted-text">&gt; I think this will be up to
                  the AD and IESG.<br>
                </div>
                OK - I'll wait for them to respond.<br>
                <div class="quoted-text">&gt; If you (and others) want
                  to work on a major update, I am happy to share the
                  XML.  I hope we don’t end up with can’t move the
                  current document forward, and no one wants to do a
                  major update.<br>
                </div>
                I'd certainly prefer to have this doc address these
                issues.<br>
                <br>
                One question - if a major update occurred, would that be
                at the same<br>
                standard level? If so, and if these issues are of
                concern, I'd be glad<br>
                to take that on.<br>
                <br>
                If a major rev is a standards-level setback, that would
                be less useful.<br>
                <br>
                I'd like to hear their views...<br>
              </blockquote>
            </div>
          </div>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">So, RFC 1981 is a Draft Standard, which is
          theoretically a bigger deal than a Proposed Standard. If a
          replacement to RFC 1981 doesn't work the same way that RFC
          1981 works, I don't see how it would also be a Draft Standard,
          based on the standards level of the RFC it would be replacing.
          Do others see something I'm missing?</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">However.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Assuming that a replacement for RFC 1981 Path
          MTU Discovery doesn't have the issues we've been talking about
          in these threads, I would hope that we could publish that
          replacement at Proposed Standard (not at Experimental).</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Given that we don't use the Draft Standard level
          for advancing standards track RFCs any more (post <a
            moz-do-not-send="true"
            href="https://datatracker.ietf.org/doc/rfc6410/">https://datatracker.ietf.org/doc/rfc6410/</a>),
          would publishing a replacement that works better than RFC 1981
          at Proposed Standard be a bad thing?</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Curiously yours,</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Spencer</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">
          <div class="gmail_extra">
            <div class="gmail_quote">
              <blockquote class="quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <font color="#888888"><br>
                  Joe<br>
                </font>
                <div class="elided-text"><br>
                  ______________________________<wbr>_________________<br>
                  Tsv-art mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:Tsv-art@ietf.org">Tsv-art@ietf.org</a><br>
                  <a moz-do-not-send="true"
                    href="https://www.ietf.org/mailman/listinfo/tsv-art"
                    rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/tsv-art</a><br>
                </div>
              </blockquote>
            </div>
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------6F495733573D7217B70CDADB--


From nobody Sat Mar 18 09:29:39 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D216F128990; Sat, 18 Mar 2017 09:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BGtviaYnT_Lm; Sat, 18 Mar 2017 09:29:34 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C7B8126C23; Sat, 18 Mar 2017 09:29:34 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id p77so69459934ywg.1; Sat, 18 Mar 2017 09:29:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QP7Ad3xw5AaIL8XecERqqwciyXhHBh/db/9NXreMeP8=; b=J44VsjLHUxEibJ+kwDAWenhRXZXFp/JlTHhtcpdNCKL27I+GoUr6u8/DyOHxlJ4q+G 42E1scEhPAflsiyn/fiHunMTVyIfaa/badVu2cDNgsJRaDxXSacKD2fEYSC27yj4obcL 7vY106qLmxsSwXr1U2Bk+fahSVKeqyT19oRlFP6UDpI5l1MxCnTGY4bTJQKni1aeOyiT uTHCxWXpDcYB6J75dQKpOV2b6JFcdJ8zUaI1uOp0jybj+zS1aRqhUDAHniGN0eGlERHS yEbCWzx8BngOvAsEmlZZ3Pr9o1mSnk33osYhM5FF25R2OsTXjxaJtn2D8xU8IqkTNQ+S fZeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QP7Ad3xw5AaIL8XecERqqwciyXhHBh/db/9NXreMeP8=; b=nFwQ6Es9PLj2S/wY4sorJSHKfmueavSVFL7eowt+i/eYldPyeN+S3TrKsQRImjSt3C C37BvJBEihLMy7/sq4fl35YmpTOqJnYR6VRSZoSg9RhFxMGtvqcCgf2OnBwnn+lM7Bu1 eODIIgDkjDaNuyqAXOdwy0e9biz/mu/SFXOziHnBUHTKYAa14PLgeQwfc5Ob44L0p2Mt ouWZZzSad/TPywqLrg5MXUXg4LfCVPr3iil+BPcp2gzrK9Ouvs8ESmYSsMSW6AYsbO13 d6v8VD2Yjpz6rrg+0IL3uDghFS9PRQi/0nk1fLcQC6ApDXNJFXNLZTZ/G7T5u+3MAfAh NK/g==
X-Gm-Message-State: AFeK/H0RJYPKVJsOE/GPQ4czLYRXFYPXJy89io8OcjlLHpaS6i1iyE9NMODdctR46RX9AagPhYWDULpmXZUSWQ==
X-Received: by 10.13.243.197 with SMTP id c188mr7737842ywf.248.1489854573543;  Sat, 18 Mar 2017 09:29:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.77.197 with HTTP; Sat, 18 Mar 2017 09:29:32 -0700 (PDT)
Received: by 10.37.77.197 with HTTP; Sat, 18 Mar 2017 09:29:32 -0700 (PDT)
In-Reply-To: <01fc4067-6825-9343-7735-86f9bf77bebe@isi.edu>
References: <48bfa3a1-e53c-6b31-69b0-2645ddd5937f@isi.edu> <41A44496-F222-40D5-95FE-5CE142C3827F@gmail.com> <46d7ae23-cf3d-570d-3d79-9d915663cf16@isi.edu> <8D6CA1F7-CB01-4FCD-B81C-ECBEFC088EAE@gmail.com> <e55e095b-b5c6-56e8-d4be-0b438c61ae67@isi.edu> <CAKKJt-eqbA65wiyP575Kbni4b31Jo37uZ0n=0UGn62A_n30H8Q@mail.gmail.com> <01fc4067-6825-9343-7735-86f9bf77bebe@isi.edu>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sat, 18 Mar 2017 11:29:32 -0500
Message-ID: <CAKKJt-fh5r+ENsZA28W+XRqoVLBUNbk-SsQpV3KwWUrDic2CEQ@mail.gmail.com>
To: Joe Touch <touch@isi.edu>
Cc: tsv-art@ietf.org, iesg@ietf.org, Bob Hinden <bob.hinden@gmail.com>, ipv6@ietf.org
Content-Type: multipart/alternative; boundary=94eb2c0356909f8a4b054b03ccd5
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/3yF1FG3DO5FBvLLNkMpf8U1B-dg>
Subject: Re: [Tsv-art] TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Mar 2017 16:29:37 -0000

--94eb2c0356909f8a4b054b03ccd5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, Joe,

On Mar 18, 2017 11:27, "Joe Touch" <touch@isi.edu> wrote:

FWIW, I was thinking of an update that focused on the description issue
below.

Nothing functionally would change.

Ah - I'm glad I asked!

Thanks,

Spencer

Joe

On 3/18/2017 9:03 AM, Spencer Dawkins at IETF wrote:

I may not be answering the question Joe asked, but ...

On Mar 17, 2017 19:36, "Joe Touch" <touch@isi.edu> wrote:



On 3/17/2017 4:31 PM, Bob Hinden wrote:
> Joe,
>
> I think this will be up to the AD and IESG.
OK - I'll wait for them to respond.
> If you (and others) want to work on a major update, I am happy to share
the XML.  I hope we don=E2=80=99t end up with can=E2=80=99t move the curren=
t document
forward, and no one wants to do a major update.
I'd certainly prefer to have this doc address these issues.

One question - if a major update occurred, would that be at the same
standard level? If so, and if these issues are of concern, I'd be glad
to take that on.

If a major rev is a standards-level setback, that would be less useful.

I'd like to hear their views...


So, RFC 1981 is a Draft Standard, which is theoretically a bigger deal than
a Proposed Standard. If a replacement to RFC 1981 doesn't work the same way
that RFC 1981 works, I don't see how it would also be a Draft Standard,
based on the standards level of the RFC it would be replacing. Do others
see something I'm missing?

However.

Assuming that a replacement for RFC 1981 Path MTU Discovery doesn't have
the issues we've been talking about in these threads, I would hope that we
could publish that replacement at Proposed Standard (not at Experimental).

Given that we don't use the Draft Standard level for advancing standards
track RFCs any more (post https://datatracker.ietf.org/doc/rfc6410/), would
publishing a replacement that works better than RFC 1981 at Proposed
Standard be a bad thing?

Curiously yours,

Spencer


Joe

_______________________________________________
Tsv-art mailing list
Tsv-art@ietf.org
https://www.ietf.org/mailman/listinfo/tsv-art

--94eb2c0356909f8a4b054b03ccd5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Hi, Joe,<br><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Mar 18, 2017 11:27, &quot;Joe Touch&quot; &lt;<a href=
=3D"mailto:touch@isi.edu">touch@isi.edu</a>&gt; wrote:<br type=3D"attributi=
on"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>FWIW, I was thinking of an update that focused on the description
      issue below.</p>
    <p>Nothing functionally would change.</p></div></blockquote></div></div=
></div><div dir=3D"auto">Ah - I&#39;m glad I asked!</div><div dir=3D"auto">=
<br></div><div dir=3D"auto">Thanks,</div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">Spencer</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div=
 class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"elided-text">
    Joe</div></div></blockquote></div></div></div><div dir=3D"auto"><div cl=
ass=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"elided-text">
    <div class=3D"m_-5434665501110645424moz-cite-prefix">On 3/18/2017 9:03 =
AM, Spencer Dawkins
      at IETF wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"auto">
        <div>I may not be answering the question Joe asked, but ...<br>
          <div class=3D"gmail_extra"><br>
            <div class=3D"gmail_quote">On Mar 17, 2017 19:36, &quot;Joe Tou=
ch&quot;
              &lt;<a href=3D"mailto:touch@isi.edu" target=3D"_blank">touch@=
isi.edu</a>&gt;
              wrote:<br type=3D"attribution">
              <blockquote class=3D"m_-5434665501110645424quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div class=3D"m_-5434665501110645424quoted-text"><br>
                  <br>
                  On 3/17/2017 4:31 PM, Bob Hinden wrote:<br>
                  &gt; Joe,<br>
                  &gt;<br>
                </div>
                <div class=3D"m_-5434665501110645424quoted-text">&gt; I thi=
nk this will be up to
                  the AD and IESG.<br>
                </div>
                OK - I&#39;ll wait for them to respond.<br>
                <div class=3D"m_-5434665501110645424quoted-text">&gt; If yo=
u (and others) want
                  to work on a major update, I am happy to share the
                  XML.=C2=A0 I hope we don=E2=80=99t end up with can=E2=80=
=99t move the
                  current document forward, and no one wants to do a
                  major update.<br>
                </div>
                I&#39;d certainly prefer to have this doc address these
                issues.<br>
                <br>
                One question - if a major update occurred, would that be
                at the same<br>
                standard level? If so, and if these issues are of
                concern, I&#39;d be glad<br>
                to take that on.<br>
                <br>
                If a major rev is a standards-level setback, that would
                be less useful.<br>
                <br>
                I&#39;d like to hear their views...<br>
              </blockquote>
            </div>
          </div>
        </div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">So, RFC 1981 is a Draft Standard, which is
          theoretically a bigger deal than a Proposed Standard. If a
          replacement to RFC 1981 doesn&#39;t work the same way that RFC
          1981 works, I don&#39;t see how it would also be a Draft Standard=
,
          based on the standards level of the RFC it would be replacing.
          Do others see something I&#39;m missing?</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">However.</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">Assuming that a replacement for RFC 1981 Path
          MTU Discovery doesn&#39;t have the issues we&#39;ve been talking =
about
          in these threads, I would hope that we could publish that
          replacement at Proposed Standard (not at Experimental).</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">Given that we don&#39;t use the Draft Standard le=
vel
          for advancing standards track RFCs any more (post <a href=3D"http=
s://datatracker.ietf.org/doc/rfc6410/" target=3D"_blank">https://datatracke=
r.ietf.org/<wbr>doc/rfc6410/</a>),
          would publishing a replacement that works better than RFC 1981
          at Proposed Standard be a bad thing?</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">Curiously yours,</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">Spencer</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">
          <div class=3D"gmail_extra">
            <div class=3D"gmail_quote">
              <blockquote class=3D"m_-5434665501110645424quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <font color=3D"#888888"><br>
                  Joe<br>
                </font>
                <div class=3D"m_-5434665501110645424elided-text"><br>
                  ______________________________<wbr>_________________<br>
                  Tsv-art mailing list<br>
                  <a href=3D"mailto:Tsv-art@ietf.org" target=3D"_blank">Tsv=
-art@ietf.org</a><br>
                  <a href=3D"https://www.ietf.org/mailman/listinfo/tsv-art"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>is=
tinfo/tsv-art</a><br>
                </div>
              </blockquote>
            </div>
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </div></div>

</blockquote></div><br></div></div></div>

--94eb2c0356909f8a4b054b03ccd5--


From nobody Sun Mar 26 18:55:27 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D859B1270A0; Sun, 26 Mar 2017 18:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0frC-KXKSJdG; Sun, 26 Mar 2017 18:55:23 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17B9D127977; Sun, 26 Mar 2017 18:55:21 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id i203so21977012ywc.3; Sun, 26 Mar 2017 18:55:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=vFdTB14HD0ceRg6wtghwsG89QiKQCp2Z/GjyT2X1Okc=; b=emJ48TYLkSqzVzVjZZWHmUb82ki4bSak+eln2TlZW9kiYL6TJJAV4g0Vkki1WJvHRq eQCs4Ft/xdXUSqfUWlEZYc35g/Tgr5M8BG1KtjHjPYYRoz+QAeeuqcKDnFPRjce2kO9B Bdm/nEF3iaQqREyogh3zeIcwTIYby2v21FlDC+Vbzg664X4YykZqAOUNQBlW/7i0WVgz 6Ly3WmI6ok5Jh/LKloGHdqy/D1GrCKjfA3jVVQRYwHOeoMXKy4W1Pc8kdJ0gkDy67IUc XL+ORebygZ8R84eCPDdAIwSPzDoUytLk32g9dkv9kBz2S3IIrt1feyrWEpP+so+nkETN IN8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=vFdTB14HD0ceRg6wtghwsG89QiKQCp2Z/GjyT2X1Okc=; b=JUbLPWIvOc6gaFCnwzswcPYS9Xpm7OIiucOeTOOu3sePR0b9Y5XAO/8i85qumBfvHk wL8uKB7GCjEVO8gl9m1Ry7m9jIqOCyNf5CB6jmsnFjip9pQQv8blxvmKKqP37J22tz9S zwmotBXKMEW+tWQKLKB0LCnAie/Fo8xCCLsCs20qrCO5Ybi3okkT5XGnIyOB3BIDrSrj +W8rRyTEqx2TTYygjMV5kb+kpajaySOQ2gjcNEjeW3tfo0hq/mK3jRl2XerONlMyMJjl NDYgAxUkE29JyBdA+GjBzSeSR0/9OvBImY0zQVlr1nZUkAVdsCc773zoJQSbuOxN81Us g9CA==
X-Gm-Message-State: AFeK/H3IHRytnzIWOOSQvQxvLwhaZRob3XsHeMHQ+YTtA6ZwyWRC4sDE+jh53Y1jN6a8UFWOC97TeujBcT1eBg==
X-Received: by 10.13.235.151 with SMTP id u145mr15189008ywe.19.1490579720134;  Sun, 26 Mar 2017 18:55:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.73.129 with HTTP; Sun, 26 Mar 2017 18:55:19 -0700 (PDT)
Received: by 10.37.73.129 with HTTP; Sun, 26 Mar 2017 18:55:19 -0700 (PDT)
In-Reply-To: <CAKKJt-eAVj7a-M7o33xmqnE3AqW=+XbGxYKMyVzHyUQgwbQGqA@mail.gmail.com>
References: <CAKKJt-fcEwGKPo+_HzY1ytfKZrTsw977A0bxWoB1wyLAhLDmHw@mail.gmail.com> <CAKKJt-fXMgPKhfPERGqfCJfRFZQiQLADfCSiyKKXJte=GXStWQ@mail.gmail.com> <CAKKJt-dNBB9-+3dxbcUxg3e-kOY0y_Uq5QqDiRak+nUMMS5rVQ@mail.gmail.com> <CAKKJt-fpzFJxA9N3t3H8cjWek3styYsiyKD8zfz86R1fGTzu4g@mail.gmail.com> <CAKKJt-cyTkpq2BcQKjBCiqhRWWOnOsHF9mcQs=DjMHfHEAxHcA@mail.gmail.com> <CAKKJt-fC-BU4sicfWuw8KRVY-+o=7WcunX45CXUBwidtFCCLvg@mail.gmail.com> <CAKKJt-e25Oduoy7GiLMzjhzFX1kQBLNPWhGcrB9fgqLRshghCA@mail.gmail.com> <CAKKJt-f8XWkXuU1trH7=JL9pGyP8XdaMURiwXtqDU0opsfSeeA@mail.gmail.com> <CAKKJt-edEAOWd3n3omhtPTqnjFrMgFQ=bAUMQkDxr5mqXZcScg@mail.gmail.com> <CAKKJt-f3MMzaKGYZ2vSTyrshLN57o5k25Zfp9teoZP+JS_qw8Q@mail.gmail.com> <CAKKJt-d2vu6-+bnpRnfL5Z0hPD1Pyr2mJKW_gOqFo5=0H6T87g@mail.gmail.com> <CAKKJt-e7fStDE=zvTsWXfZcRski-33ehsOLdM7tU-re2Lg9GzQ@mail.gmail.com> <CAKKJt-eG_vB6DJn1qjWd35bMQNa+UB1Ap2govvynj_2BJVgnCA@mail.gmail.com> <CAKKJt-eAVj7a-M7o33xmqnE3AqW=+XbGxYKMyVzHyUQgwbQGqA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 26 Mar 2017 20:55:19 -0500
Message-ID: <CAKKJt-dbw6MUWHXKV=TmjqkAnx8-KrMV2zuyP-56R5k5Hp1NFQ@mail.gmail.com>
To: tsv-art@ietf.org, tsv-chairs@ietf.org
Content-Type: multipart/alternative; boundary=94eb2c06c390ba773a054baca27f
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/Q40vQE0VRX3fv0mW0bneJsRe4as>
Subject: [Tsv-art] Logistics for TSV dinner
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2017 01:55:26 -0000

--94eb2c06c390ba773a054baca27f
Content-Type: text/plain; charset=UTF-8

Dear RSVP folks.

We have a winner. We will have our TSV dinner on Monday night at 7:30 pm.

Thanks, Mirja, for finding us a private/semi-private space!

I'll plan to leave from the Swissotel lobby at 7:00 pm.

The restaurant will be https://atwoodrestaurant.com.

The Yelp page is at https://www.yelp.com/biz/atwood-chicago.

Directions are at https://goo.gl/maps/RGute59T5ft.

If you did not RSVP in the Doodle poll but are suddenly interested, please
contact the ADs and we'll try to expand our reservation.

Thanks!

Spencer

--94eb2c06c390ba773a054baca27f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Dear RSVP folks.<div dir=3D"auto"><br></div><div dir=3D"a=
uto">We have a winner. We will have our TSV dinner on Monday night at 7:30 =
pm.<div dir=3D"auto"><br></div><div dir=3D"auto">Thanks, Mirja, for finding=
 us a private/semi-private space!<br><div dir=3D"auto"><br></div><div dir=
=3D"auto">I&#39;ll plan to leave from the Swissotel lobby at 7:00 pm.<br><d=
iv dir=3D"auto"><br></div><div dir=3D"auto">The restaurant will be=C2=A0<a =
href=3D"https://atwoodrestaurant.com">https://atwoodrestaurant.com</a>.</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">The Yelp page is at <a href=
=3D"https://www.yelp.com/biz/atwood-chicago">https://www.yelp.com/biz/atwoo=
d-chicago</a>.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Direction=
s are at <a href=3D"https://goo.gl/maps/RGute59T5ft">https://goo.gl/maps/RG=
ute59T5ft</a>.</div><div dir=3D"auto"><br></div><div dir=3D"auto">If you di=
d not RSVP in the Doodle poll but are suddenly interested, please contact t=
he ADs and we&#39;ll try to expand our reservation.</div><div dir=3D"auto">=
<br></div><div dir=3D"auto">Thanks!</div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">Spencer</div></div></div></div></div>

--94eb2c06c390ba773a054baca27f--

