
From d3e3e3@gmail.com  Fri Jun  1 08:46:21 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6ADE21F8B38; Fri,  1 Jun 2012 08:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.233
X-Spam-Level: 
X-Spam-Status: No, score=-102.233 tagged_above=-999 required=5 tests=[AWL=-0.934, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NgXkeR9PrKWL; Fri,  1 Jun 2012 08:46:20 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5A88421F8B3A; Fri,  1 Jun 2012 08:46:20 -0700 (PDT)
Received: by yhq56 with SMTP id 56so1978691yhq.31 for <multiple recipients>; Fri, 01 Jun 2012 08:46:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=3SrWxgz4JzCQG0DAWAHWabO2CemWwugsLuYlXUsDRcE=; b=bumQNY8oJv5Pe7UPZozUcSlW5O1zXvDkoegjh9XQxlDCWr0jk6sqBeG26vYykNr981 Mf2TpVrG3gP+tL4vHgj8ak8r5eg07dOWt6i4pI5P6wDurlPnujr8aLF9VspKvN+jPIoK RLL2J0Fst0kERy2E7V+gQrImS4kfVdYVfzskp16cyU2nVPZyHBHF8A5AVNF+FhmbSTUH 9t4nVsAvy/bN4Vjn/UyX4Y8yADuhrvu2cuPZg4IO88klN/KDdBE0wDvHTyZ/i37YFy+E HzzuTQJeLceMcO5+tliN7DZxR4DlCSNefmhZqtEgBbKavbTXewXdoBverluzufP2fopj n5Xg==
Received: by 10.50.212.98 with SMTP id nj2mr2038781igc.35.1338565578568; Fri, 01 Jun 2012 08:46:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.99.228 with HTTP; Fri, 1 Jun 2012 08:45:57 -0700 (PDT)
In-Reply-To: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com>
References: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 1 Jun 2012 11:45:57 -0400
Message-ID: <CAF4+nEESCSkUgM2Wzr5MXfW5su5Og_XA0dyO+gksfN2LAzCCWw@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-ietf-trill-rbridge-extension.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat review of draft-ietf-trill-rbridge-extension-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 15:46:22 -0000

Hi Ben,

Thanks for your review. See responses below.

On Thu, May 31, 2012 at 6:08 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document: draft-ietf-trill-rbridge-extension-04
> Reviewer: Ben Campbell
> Review Date: 2012-05-31
> IETF LC End Date: 2012-06-07
> IESG Telechat date: 2012-06-07
>
> Note: Since this draft is on the agenda of the IESG Telechat on the
> same day that the IETF last call expires, this review is intended
> for both purposes.
>
> Summary:
>
> This draft is almost ready for publication as a proposed standard,
> but I have some clarification questions and comments that should be
> considered prior to publication.
>
> Major issues:
>
> None
>
> Minor issues:
>
> -- section 2, general:
>
> Do the authors assume that all TRILL extensions will follow this
> spec? Since RFC6325 already specifies an extension mechanism, what
> stops an extension from ignoring this spec and doing something
> different? Does it hurt if they do?

I am not aware of any conflicts between this draft and RFC 6325. RFC
6325 provides the broadest header option framework, for example
specifying the field for the length of the options area and the
initial two critical summary bits. This document fills in the
structure and allocation mechanism of the remaining bits in the first
4-byte word of the options area, consistent with and repeating some
material from RFC 6325, but leaving specification of the remainder of
the options area for future documents, which should be consistent with
both RFC 6325 and this document. (For example, some future version of
draft-ietf-trill-rbridge-options.)

However, neither RFC 6325 nor this document can actually actually bind
the IETF against adopting future standards describing extensions that
do not conform. If future changes do not follow RFC 6325 or this
document, for example changing the location or interpretation of the
option length field in the TRILL Header or changing the interpretation
of the critical summary bits in the first word of the options area,
then this would break hardware and software implementations that
depend on RFC 6325 and/or this document. But I trust the IETF to
adhere to its usually high standards for backwards compatibility.

Perhaps this draft should, in the first page header, say "Updates:
6325", not in the sense that it makes a change but in the sense that
it fills in more details.

> -- section 2, 3rd paragraph from end: "Non-critical extensions can
>    be safely ignored."
>
> Is that intended to be normative? (Seems like it should be, since
> behavior for critical extensions is normative).

I think of it as more like the definition of "non-critical".

> -- section 2.1, 1st paragraph, last sentence:
>
> Redundant with normative language in previous section.

? There is a normative requirement to discard frames with any
unimplemented critical hop-by-hop options present, which might be
thought to require examination of all options (something manifestly
impossible since the format of options beyond the first word of the
options area is not yet normatively specified). The sentence to which
you refer just clarifies that testing the appropriate crtical summary
bit(s) in the first word of the options area, if that word is present,
is all that is required.

> -- section 2.3, first paragraph:
>
> Is the first sentence intended as normative?

Yes. When one is describing part of a protocol and you say that some
particular contiguous block of bits is some particular field (and then
possibly describe the sub-structure of that field) isn't that always
normative?

> -- section 6, last paragraph:
>
> No security implications of this are mentioned. Is it really a
> security consideration?
>
> Also, is this more likely to be set incorrectly than all the other
> things that some implementation might screw up, so that it warrants
> special treatment?

I tend to think that a discussion of what happens if bits are
corrupted or incorrectly set is something reasonable for the Security
Considerations section, although it could be elsewhere. The second
paragraph/sentence of this section says that security considerations
for any bits in the first word of the options area will be in the
document specifying those bits. This document specifies the critical
summary bits and the RBridge Channel Alert bits so there is text on
both of those in its Security Considerations Section.

> Nits/editorial comments:
>
> -- section 1:
>
> Please expand TRILL on first mention in the body of the document
> (i.e. not just in the Abstract.)

Sure. And all the other acronym expansions requested below are fine so
I won't respond individually to them below although I agree with them.

> -- section 2:
>
> Please expand RBridge and IS-IS on first mention.
>
> -- section 2, bullet list, 2nd bullet: " ... which would only
>    necessarily affect the RBridge(s) where a TRILL frame is
>    decapsulated"
>
> Does that mean it always affects the decapsulating RBridge but might
> effect transit RBridges as well?

Yes.

> -- section 2, first paragraph after bullet list: "critical
>    hop-by-hop extension"
>
> I assume this means an extension with the critical flag set? If so,
> it would be more precise to say that.

This draft was split out of a more general draft that covered
extensions in general. The three paragraphs after the bullet list on
critical / non-critical extensions apply to all extensions as well as
the flag bits in the first word of the options area. So this means
critical header extensions flags and any other types of critical
options specified in the future.

> -- section 2.1, 1st paragraph:
>
> I'm a little confused by a citation for "future documents". Do you
> mean the cited document as an example of something that might do
> this (in which case a "for example" would help), or do you mean to
> say that document will do this?

Yes, the cited work-in-progress references are examples. I'm fine with
adding "for example".

> -- section 2.2, 1st paragraph:
>
> Please expand PDU on first mention.
>
> -- section 2.3, first paragraph:
>
> s/modifictions/modifications

OK. Thanks.

> -- section 5:
>
> Since section 3 is entirely composed of the referenced table, and
> seems to exist mostly if not entirely for the purpose of this
> reference, why not just move the table to the IANA considerations
> section.

(Looking at Section 3, I believe the reference there to the IANA
Considerations Section should be to Section 5 rather than Section 6.)

I guess I don't actually see any problem with the current document
structure that I think flows better for someone reading it from the
start. I suppose it imposes a tiny burden on someone who is just
looking at the IANA Considerations Section. I don't see why it would
be better to make it a tiny bit easier for someone just looking at the
IANA Considerations Section while imposing a tiny burdne on those
reading through the document from the start.

Hope the above responses help with the clarification,
Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

From ben@nostrum.com  Fri Jun  1 12:18:10 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3788E11E80AD; Fri,  1 Jun 2012 12:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.08
X-Spam-Level: 
X-Spam-Status: No, score=-101.08 tagged_above=-999 required=5 tests=[AWL=-0.780, BAYES_00=-2.599, MANGLED_LIST=2.3, SPF_PASS=-0.001,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id td9g-XnJUZz3; Fri,  1 Jun 2012 12:18:09 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 313EB11E80A4; Fri,  1 Jun 2012 12:18:08 -0700 (PDT)
Received: from frankenstein.test.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q51JI3ZX082589 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 1 Jun 2012 14:18:05 -0500 (CDT) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <CAF4+nEESCSkUgM2Wzr5MXfW5su5Og_XA0dyO+gksfN2LAzCCWw@mail.gmail.com>
Date: Fri, 1 Jun 2012 14:18:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <69241DCD-C349-4D15-8B92-58D05F216BF5@nostrum.com>
References: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com> <CAF4+nEESCSkUgM2Wzr5MXfW5su5Og_XA0dyO+gksfN2LAzCCWw@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1278)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: draft-ietf-trill-rbridge-extension.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat review of draft-ietf-trill-rbridge-extension-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 19:18:10 -0000

Thanks for the quick response. Further comments inline. I deleted =
sections that do not appear to need further discussion.

Thanks!

Ben.

On Jun 1, 2012, at 10:45 AM, Donald Eastlake wrote:

> Hi Ben,
>=20
> Thanks for your review. See responses below.
>=20
> On Thu, May 31, 2012 at 6:08 PM, Ben Campbell <ben@nostrum.com> wrote:
>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please wait for direction from your document shepherd
>> or AD before posting a new version of the draft.
>>=20
>> Document: draft-ietf-trill-rbridge-extension-04
>> Reviewer: Ben Campbell
>> Review Date: 2012-05-31
>> IETF LC End Date: 2012-06-07
>> IESG Telechat date: 2012-06-07
>>=20
>> Note: Since this draft is on the agenda of the IESG Telechat on the
>> same day that the IETF last call expires, this review is intended
>> for both purposes.
>>=20
>> Summary:
>>=20
>> This draft is almost ready for publication as a proposed standard,
>> but I have some clarification questions and comments that should be
>> considered prior to publication.
>>=20
>> Major issues:
>>=20
>> None
>>=20
>> Minor issues:
>>=20
>> -- section 2, general:
>>=20
>> Do the authors assume that all TRILL extensions will follow this
>> spec? Since RFC6325 already specifies an extension mechanism, what
>> stops an extension from ignoring this spec and doing something
>> different? Does it hurt if they do?
>=20
> I am not aware of any conflicts between this draft and RFC 6325. RFC
> 6325 provides the broadest header option framework, for example
> specifying the field for the length of the options area and the
> initial two critical summary bits. This document fills in the
> structure and allocation mechanism of the remaining bits in the first
> 4-byte word of the options area, consistent with and repeating some
> material from RFC 6325, but leaving specification of the remainder of
> the options area for future documents, which should be consistent with
> both RFC 6325 and this document. (For example, some future version of
> draft-ietf-trill-rbridge-options.)

I agree there is no conflict--this draft adds details, but doesn't seem =
to contradict anything in the RFC.

>=20
> However, neither RFC 6325 nor this document can actually actually bind
> the IETF against adopting future standards describing extensions that
> do not conform.

Certainly. Nothing can do that. The IETF can always update a protocol to =
change normative language, no matter how strongly it was stated =
originally :-)

> If future changes do not follow RFC 6325 or this
> document, for example changing the location or interpretation of the
> option length field in the TRILL Header or changing the interpretation
> of the critical summary bits in the first word of the options area,
> then this would break hardware and software implementations that
> depend on RFC 6325 and/or this document. But I trust the IETF to
> adhere to its usually high standards for backwards compatibility.
>=20
> Perhaps this draft should, in the first page header, say "Updates:
> 6325", not in the sense that it makes a change but in the sense that
> it fills in more details.
>=20

Assuming the additional details in this draft comprise preferred =
extension mechanism, then I think it makes sense to say that somewhere =
(perhaps a SHOULD strength), and also mark it as updating 6325. Adding =
details is still an update.


>> -- section 2, 3rd paragraph from end: "Non-critical extensions can
>>   be safely ignored."
>>=20
>> Is that intended to be normative? (Seems like it should be, since
>> behavior for critical extensions is normative).
>=20
> I think of it as more like the definition of "non-critical".

Sure--I mainly mention it to be consistent with the text for "critical" =
extensions, since it did use normative language about dropping frames.

>=20
>> -- section 2.1, 1st paragraph, last sentence:
>>=20
>> Redundant with normative language in previous section.
>=20
> ? There is a normative requirement to discard frames with any
> unimplemented critical hop-by-hop options present, which might be
> thought to require examination of all options (something manifestly
> impossible since the format of options beyond the first word of the
> options area is not yet normatively specified). The sentence to which
> you refer just clarifies that testing the appropriate crtical summary
> bit(s) in the first word of the options area, if that word is present,
> is all that is required.

section 2 says "Any RBridge receiving a frame with a critical hop-by-hop =
extension  that it does not implement MUST discard the frame...". =
Section 2.1 says "If an RBridge does not implement all critical flags in =
a TRILL Data frame, it MUST discard the frame..." These really seem like =
the same MUST (i.e, if you updated one but not the other, you would have =
an ambiguous state). The same is true for the egress bit.

I understand that you want to draw the connection between a "critical =
extension" and "critical flags", but it's better to avoid having =
multiple bits of authoritative text for the same normative requirement. =
Perhaps it might be better to say something like "If the RBridge does =
not implement all critical flags... it MUST treat the frame as having an =
unimplemented critical extension as described in section 2"



>=20
>> -- section 2.3, first paragraph:
>>=20
>> Is the first sentence intended as normative?
>=20
> Yes. When one is describing part of a protocol and you say that some
> particular contiguous block of bits is some particular field (and then
> possibly describe the sub-structure of that field) isn't that always
> normative?

Never mind, I misread the sentence. Sorry for the confusion.

>=20
>> -- section 6, last paragraph:
>>=20
>> No security implications of this are mentioned. Is it really a
>> security consideration?
>>=20
>> Also, is this more likely to be set incorrectly than all the other
>> things that some implementation might screw up, so that it warrants
>> special treatment?
>=20
> I tend to think that a discussion of what happens if bits are
> corrupted or incorrectly set is something reasonable for the Security
> Considerations section, although it could be elsewhere. The second
> paragraph/sentence of this section says that security considerations
> for any bits in the first word of the options area will be in the
> document specifying those bits. This document specifies the critical
> summary bits and the RBridge Channel Alert bits so there is text on
> both of those in its Security Considerations Section.

On re-reading the paragraph, I can see interpreting it to mean that =
incorrectly set flags explicitly do not cause a security problem, which =
I agree is reasonable to say in the security considerations. So, never =
mind :-)

[...]


>>=20
>> -- section 2, bullet list, 2nd bullet: " ... which would only
>>   necessarily affect the RBridge(s) where a TRILL frame is
>>   decapsulated"
>>=20
>> Does that mean it always affects the decapsulating RBridge but might
>> effect transit RBridges as well?
>=20
> Yes.
>=20

Okay, no problem.

>> -- section 2, first paragraph after bullet list: "critical
>>   hop-by-hop extension"
>>=20
>> I assume this means an extension with the critical flag set? If so,
>> it would be more precise to say that.
>=20
> This draft was split out of a more general draft that covered
> extensions in general. The three paragraphs after the bullet list on
> critical / non-critical extensions apply to all extensions as well as
> the flag bits in the first word of the options area. So this means
> critical header extensions flags and any other types of critical
> options specified in the future.

Okay

[...]


>=20
>> -- section 5:
>>=20
>> Since section 3 is entirely composed of the referenced table, and
>> seems to exist mostly if not entirely for the purpose of this
>> reference, why not just move the table to the IANA considerations
>> section.
>=20
> (Looking at Section 3, I believe the reference there to the IANA
> Considerations Section should be to Section 5 rather than Section 6.)
>=20
> I guess I don't actually see any problem with the current document
> structure that I think flows better for someone reading it from the
> start. I suppose it imposes a tiny burden on someone who is just
> looking at the IANA Considerations Section. I don't see why it would
> be better to make it a tiny bit easier for someone just looking at the
> IANA Considerations Section while imposing a tiny burdne on those
> reading through the document from the start.
>=20

Okay. I was interpreting it as existing entirely for the IANA =
registration--but if you believe it adds value to the "body" of the =
text, I am okay with it.

[...]


From elwynd@dial.pipex.com  Sun Jun  3 06:39:56 2012
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 477F821F856D for <gen-art@ietfa.amsl.com>; Sun,  3 Jun 2012 06:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XY+Npm9aIE4C for <gen-art@ietfa.amsl.com>; Sun,  3 Jun 2012 06:39:55 -0700 (PDT)
Received: from auth.b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id B532F21F853E for <gen-art@ietf.org>; Sun,  3 Jun 2012 06:39:55 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[81.187.254.250]) by b.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1SbB29-0006k4-CQ; Sun, 03 Jun 2012 14:39:53 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Sun, 03 Jun 2012 14:39:49 +0100
Message-Id: <1338730789.31554.15774.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-codec-opus.all@tools.ietf.org
Subject: [Gen-art] Gen-art telechat review of draft-ietf-codec-opus-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 13:39:56 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-codec-opus-14
Reviewer: Elwyn Davies
Review Date: 3 June 2012
IETF LC End Date:
IESG Telechat date: 7 June 2012

Summary:
As far as the textual part of the document is concerned this version
addressed my last call comments and apparently adequately describes the
structure of the codec.

My review at last call was concentrated on this textual part and I did
not have time to significantly dip into the large body of code that
makes up the normative part of the draft.  I cannot therefore say that
there is an exact correspondence between the description and the code,
but the description does seem to give a good view (significantly better
then before Last Call IMO) of the way the codec operates.  I would like
to thank the authors for the speedy and effective way that they
addressed the comments that I made - to an uninformed neophyte in codecs
this seems to be an excellent piece of work.

Having had a little time to dip into code since doing the last call, the
one serious comment that I would make is that it is a great pity that
the code did not incorporate Doxygen or similar code documentation
comments.  Being able to extract a Doxygen comment document would
significantly enhance the understandability of some very complex code
and potentially allow the code to be tied back to the textual comments
in a way that would (I suspect) help future implementors trying to
generate alternative versions.  I appreciate that is a lot of work at
this late stage but it would  help a lot.

Regards,
Elwyn Davies




From d3e3e3@gmail.com  Sun Jun  3 06:44:01 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6DB21F8570; Sun,  3 Jun 2012 06:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.17
X-Spam-Level: 
X-Spam-Status: No, score=-102.17 tagged_above=-999 required=5 tests=[AWL=-0.871, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50b8S2+YvV9I; Sun,  3 Jun 2012 06:44:00 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3D71821F856D; Sun,  3 Jun 2012 06:44:00 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so3187714ghb.31 for <multiple recipients>; Sun, 03 Jun 2012 06:43:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=kGeZky1e46ToxtZmAoTyz83ypNSEXm4SsuMZC4tpVhk=; b=s5+KB5GcFWGD178RlZTswLZrynRF/o0gvLwbSFE5RfvVSEqvuf7oUpg6t/WRuZ6X04 VTRi2TXRyTfg1TegaKMSTETdsTyizC2Kpjskz442PBmEvSXuLs3swcBOS51NeE1tyZ43 c4Ic+p9ox9Jl8WCGso65sWTGT5XH4rJ9qx8+qeJvMUAkGkDen5MuRZaUoGPjdc12MKvX AoIByiIyUCVQw/Alr7/QfIkhwCtQSSQPpC8trYPXx7ye33nqlGgO32nrBs1TCZRAqZlG 1j8Kw/N33ru5u921tyNBZYVC0gbmBYNWiHKCgZ/1UI4iEQcku1ROCPmYf0DrhrkWa2Jx PLmw==
Received: by 10.50.196.201 with SMTP id io9mr5636621igc.58.1338731039264; Sun, 03 Jun 2012 06:43:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.99.228 with HTTP; Sun, 3 Jun 2012 06:43:39 -0700 (PDT)
In-Reply-To: <69241DCD-C349-4D15-8B92-58D05F216BF5@nostrum.com>
References: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com> <CAF4+nEESCSkUgM2Wzr5MXfW5su5Og_XA0dyO+gksfN2LAzCCWw@mail.gmail.com> <69241DCD-C349-4D15-8B92-58D05F216BF5@nostrum.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 3 Jun 2012 09:43:39 -0400
Message-ID: <CAF4+nEH0G-8JD5XuSBRp2xcWtdFUmh0x0nw=Q-9gV4Jtkp74iw@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: draft-ietf-trill-rbridge-extension.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat review of draft-ietf-trill-rbridge-extension-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 13:44:01 -0000

Hi Ben,

On Fri, Jun 1, 2012 at 3:18 PM, Ben Campbell <ben@nostrum.com> wrote:
> Thanks for the quick response. Further comments inline. I deleted section=
s that do not appear to need further discussion.
>
> Thanks!
>
> Ben.
>
> On Jun 1, 2012, at 10:45 AM, Donald Eastlake wrote:
>
>> Hi Ben,
>>
>> Thanks for your review. See responses below.
>>
>> On Thu, May 31, 2012 at 6:08 PM, Ben Campbell <ben@nostrum.com> wrote:
>>
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>> Please wait for direction from your document shepherd
>>> or AD before posting a new version of the draft.
>>>
>>> Document: draft-ietf-trill-rbridge-extension-04
>>> Reviewer: Ben Campbell
>>> Review Date: 2012-05-31
>>> IETF LC End Date: 2012-06-07
>>> IESG Telechat date: 2012-06-07
>>>
>>> Note: Since this draft is on the agenda of the IESG Telechat on the
>>> same day that the IETF last call expires, this review is intended
>>> for both purposes.
>>>
>>> Summary:
>>>
>>> This draft is almost ready for publication as a proposed standard,
>>> but I have some clarification questions and comments that should be
>>> considered prior to publication.
>>>
>>> Major issues:
>>>
>>> None
>>>
>>> Minor issues:
>>>
>>> -- section 2, general:
>>>
>>> Do the authors assume that all TRILL extensions will follow this
>>> spec? Since RFC6325 already specifies an extension mechanism, what
>>> stops an extension from ignoring this spec and doing something
>>> different? Does it hurt if they do?
>>
>> I am not aware of any conflicts between this draft and RFC 6325. RFC
>> 6325 provides the broadest header option framework, for example
>> specifying the field for the length of the options area and the
>> initial two critical summary bits. This document fills in the
>> structure and allocation mechanism of the remaining bits in the first
>> 4-byte word of the options area, consistent with and repeating some
>> material from RFC 6325, but leaving specification of the remainder of
>> the options area for future documents, which should be consistent with
>> both RFC 6325 and this document. (For example, some future version of
>> draft-ietf-trill-rbridge-options.)
>
> I agree there is no conflict--this draft adds details, but doesn't seem t=
o contradict anything in the RFC.
>
>>
>> However, neither RFC 6325 nor this document can actually actually bind
>> the IETF against adopting future standards describing extensions that
>> do not conform.
>
> Certainly. Nothing can do that. The IETF can always update a protocol to =
change normative language, no matter how strongly it was stated originally =
:-)
>
>> If future changes do not follow RFC 6325 or this
>> document, for example changing the location or interpretation of the
>> option length field in the TRILL Header or changing the interpretation
>> of the critical summary bits in the first word of the options area,
>> then this would break hardware and software implementations that
>> depend on RFC 6325 and/or this document. But I trust the IETF to
>> adhere to its usually high standards for backwards compatibility.
>>
>> Perhaps this draft should, in the first page header, say "Updates:
>> 6325", not in the sense that it makes a change but in the sense that
>> it fills in more details.
>>
>
> Assuming the additional details in this draft comprise preferred extensio=
n mechanism, then I think it makes sense to say that somewhere (perhaps a S=
HOULD strength), and also mark it as updating 6325. Adding details is still=
 an update.

OK.

>>> -- section 2, 3rd paragraph from end: "Non-critical extensions can
>>> =A0 be safely ignored."
>>>
>>> Is that intended to be normative? (Seems like it should be, since
>>> behavior for critical extensions is normative).
>>
>> I think of it as more like the definition of "non-critical".
>
> Sure--I mainly mention it to be consistent with the text for "critical" e=
xtensions, since it did use normative language about dropping frames.
>
>>
>>> -- section 2.1, 1st paragraph, last sentence:
>>>
>>> Redundant with normative language in previous section.
>>
>> ? There is a normative requirement to discard frames with any
>> unimplemented critical hop-by-hop options present, which might be
>> thought to require examination of all options (something manifestly
>> impossible since the format of options beyond the first word of the
>> options area is not yet normatively specified). The sentence to which
>> you refer just clarifies that testing the appropriate crtical summary
>> bit(s) in the first word of the options area, if that word is present,
>> is all that is required.
>
> section 2 says "Any RBridge receiving a frame with a critical hop-by-hop =
extension =A0that it does not implement MUST discard the frame...". Section=
 2.1 says "If an RBridge does not implement all critical flags in a TRILL D=
ata frame, it MUST discard the frame..." These really seem like the same MU=
ST (i.e, if you updated one but not the other, you would have an ambiguous =
state). The same is true for the egress bit.
>
> I understand that you want to draw the connection between a "critical ext=
ension" and "critical flags", but it's better to avoid having multiple bits=
 of authoritative text for the same normative requirement. Perhaps it might=
 be better to say something like "If the RBridge does not implement all cri=
tical flags... it MUST treat the frame as having an unimplemented critical =
extension as described in section 2"

I'm OK with your suggested wording.

>>
>>> -- section 2.3, first paragraph:
>>>
>>> Is the first sentence intended as normative?
>>
>> Yes. When one is describing part of a protocol and you say that some
>> particular contiguous block of bits is some particular field (and then
>> possibly describe the sub-structure of that field) isn't that always
>> normative?
>
> Never mind, I misread the sentence. Sorry for the confusion.
>
>>
>>> -- section 6, last paragraph:
>>>
>>> No security implications of this are mentioned. Is it really a
>>> security consideration?
>>>
>>> Also, is this more likely to be set incorrectly than all the other
>>> things that some implementation might screw up, so that it warrants
>>> special treatment?
>>
>> I tend to think that a discussion of what happens if bits are
>> corrupted or incorrectly set is something reasonable for the Security
>> Considerations section, although it could be elsewhere. The second
>> paragraph/sentence of this section says that security considerations
>> for any bits in the first word of the options area will be in the
>> document specifying those bits. This document specifies the critical
>> summary bits and the RBridge Channel Alert bits so there is text on
>> both of those in its Security Considerations Section.
>
> On re-reading the paragraph, I can see interpreting it to mean that incor=
rectly set flags explicitly do not cause a security problem, which I agree =
is reasonable to say in the security considerations. So, never mind :-)
>
> [...]
>
>
>>>
>>> -- section 2, bullet list, 2nd bullet: " ... which would only
>>> =A0 necessarily affect the RBridge(s) where a TRILL frame is
>>> =A0 decapsulated"
>>>
>>> Does that mean it always affects the decapsulating RBridge but might
>>> effect transit RBridges as well?
>>
>> Yes.
>>
>
> Okay, no problem.
>
>>> -- section 2, first paragraph after bullet list: "critical
>>> =A0 hop-by-hop extension"
>>>
>>> I assume this means an extension with the critical flag set? If so,
>>> it would be more precise to say that.
>>
>> This draft was split out of a more general draft that covered
>> extensions in general. The three paragraphs after the bullet list on
>> critical / non-critical extensions apply to all extensions as well as
>> the flag bits in the first word of the options area. So this means
>> critical header extensions flags and any other types of critical
>> options specified in the future.
>
> Okay
>
> [...]
>
>
>>
>>> -- section 5:
>>>
>>> Since section 3 is entirely composed of the referenced table, and
>>> seems to exist mostly if not entirely for the purpose of this
>>> reference, why not just move the table to the IANA considerations
>>> section.
>>
>> (Looking at Section 3, I believe the reference there to the IANA
>> Considerations Section should be to Section 5 rather than Section 6.)
>>
>> I guess I don't actually see any problem with the current document
>> structure that I think flows better for someone reading it from the
>> start. I suppose it imposes a tiny burden on someone who is just
>> looking at the IANA Considerations Section. I don't see why it would
>> be better to make it a tiny bit easier for someone just looking at the
>> IANA Considerations Section while imposing a tiny burdne on those
>> reading through the document from the start.
>>
>
> Okay. I was interpreting it as existing entirely for the IANA registratio=
n--but if you believe it adds value to the "body" of the text, I am okay wi=
th it.
>
> [...]

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

From d3e3e3@gmail.com  Sun Jun  3 11:36:09 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A768021F8599 for <gen-art@ietfa.amsl.com>; Sun,  3 Jun 2012 11:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -59.461
X-Spam-Level: 
X-Spam-Status: No, score=-59.461 tagged_above=-999 required=5 tests=[AWL=-43.463, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_AVOID=2.3, MANGLED_BELOW=2.3, MANGLED_BEST=2.3, MANGLED_BODY=2.3, MANGLED_CABLE=2.3, MANGLED_DELETE=2.3, MANGLED_EFFEX=2.3, MANGLED_EXTEND=2.3, MANGLED_EXTNSN=2.3, MANGLED_FORM=2.3, MANGLED_FROM=2.3, MANGLED_FULL=2.3, MANGLED_HERE=2.3, MANGLED_INCLDN=2.3, MANGLED_INITAL=2.3, MANGLED_LICNSD=2.3, MANGLED_LIMITD=2.3, MANGLED_LINKS=2.3, MANGLED_LIST=2.3, MANGLED_LOW=2.3, MANGLED_MEDS=2.3, MANGLED_MEN=2.3, MANGLED_MILFS=2.3, MANGLED_OFF=2.3, MANGLED_PERFRM=2.3, MANGLED_PLEASE=2.3, MANGLED_RATES=2.3, MANGLED_SEX=2.3, MANGLED_SIDE=2.3, MANGLED_SPICE=2.3, MANGLED_TEXT=2.3, MANGLED_TIME=2.3, MANGLED_TOOL=2.3, MANGLED_WHILE=2.3, MANGLED_WORKNG=2.3, MANGLED_WORKS=2.3, MANGLED_YOUR=2.3, MIME_ASCII0=1.5, RCVD_IN_DNSWL_LOW=-1, SARE_OEM_OBFU=1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UkJFbu7cie-T for <gen-art@ietfa.amsl.com>; Sun,  3 Jun 2012 11:36:04 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id A7EC921F8598 for <gen-art@ietf.org>; Sun,  3 Jun 2012 11:36:03 -0700 (PDT)
Received: by yhq56 with SMTP id 56so2790766yhq.31 for <gen-art@ietf.org>; Sun, 03 Jun 2012 11:36:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=8e47GCPFNTlDYSX0v+sfdMUcwoDCb/Nk+R+c2bSK4Aw=; b=NFvqacqXVL8VDgHtU+Cvrd49fqAa2jN5F3iKUfSdhSHhHyzVWRQNtDpOdHvXm2918L oSJ/QLNmzo6AsDam8IOw++SRautRCk9ExKkrBLGdDZQ4s5F+dp8VyblRg1g0jBPHUE4L q/V4Y559JArDHhUFs5j5HusfClqgGZOiJwYa0oS9v7oQXGF+mF+ePTY6PYzvoq2aqfbt Z1iE0YGMgj0Uz0p+/U+u+ZSvO+0pMb7pJBCamNS+ie2XiP2BdGDVU3JyHjWCTfOKxWmW fMpt35Hm4UTFmRN8i2ePhPdpOyFzfaMxzo6oBKzeAqaIs8zL78uGUIr8mMwL0p/AtnXe WxKQ==
Received: by 10.50.196.232 with SMTP id ip8mr6120736igc.50.1338748562841; Sun, 03 Jun 2012 11:36:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.99.228 with HTTP; Sun, 3 Jun 2012 11:35:42 -0700 (PDT)
In-Reply-To: <CAF4+nEH0G-8JD5XuSBRp2xcWtdFUmh0x0nw=Q-9gV4Jtkp74iw@mail.gmail.com>
References: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com> <CAF4+nEESCSkUgM2Wzr5MXfW5su5Og_XA0dyO+gksfN2LAzCCWw@mail.gmail.com> <69241DCD-C349-4D15-8B92-58D05F216BF5@nostrum.com> <CAF4+nEH0G-8JD5XuSBRp2xcWtdFUmh0x0nw=Q-9gV4Jtkp74iw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 3 Jun 2012 14:35:42 -0400
Message-ID: <CAF4+nEG_ciDC6Gz8BEFmwTi2qUZwXuKxAKv_jDe7v4v8OfX4Lg@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/mixed; boundary=14dae9341241881f6e04c195b0c1
Cc: Vishwas Manral <vishwas.ietf@gmail.com>, draft-ietf-trill-rbridge-extension.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat review of draft-ietf-trill-rbridge-extension-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 18:36:09 -0000

--14dae9341241881f6e04c195b0c1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Ben,

Attached is a version incorporating changes to resolve your comments
and a wdiff against the current -04 version. However, given the
proximity to the IESG tele chat, I do not plan to upload this version
before that call.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com


On Sun, Jun 3, 2012 at 9:43 AM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> Hi Ben,
>
> On Fri, Jun 1, 2012 at 3:18 PM, Ben Campbell <ben@nostrum.com> wrote:
>> Thanks for the quick response. Further comments inline. I deleted sectio=
ns that do not appear to need further discussion.
>>
>> Thanks!
>>
>> Ben.
>>
>> On Jun 1, 2012, at 10:45 AM, Donald Eastlake wrote:
>>
>>> Hi Ben,
>>>
>>> Thanks for your review. See responses below.
>>>
>>> On Thu, May 31, 2012 at 6:08 PM, Ben Campbell <ben@nostrum.com> wrote:
>>>
>>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>>> Gen-ART, please see the FAQ at
>>>> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>
>>>> Please wait for direction from your document shepherd
>>>> or AD before posting a new version of the draft.
>>>>
>>>> Document: draft-ietf-trill-rbridge-extension-04
>>>> Reviewer: Ben Campbell
>>>> Review Date: 2012-05-31
>>>> IETF LC End Date: 2012-06-07
>>>> IESG Telechat date: 2012-06-07
>>>>
>>>> Note: Since this draft is on the agenda of the IESG Telechat on the
>>>> same day that the IETF last call expires, this review is intended
>>>> for both purposes.
>>>>
>>>> Summary:
>>>>
>>>> This draft is almost ready for publication as a proposed standard,
>>>> but I have some clarification questions and comments that should be
>>>> considered prior to publication.
>>>>
>>>> Major issues:
>>>>
>>>> None
>>>>
>>>> Minor issues:
>>>>
>>>> -- section 2, general:
>>>>
>>>> Do the authors assume that all TRILL extensions will follow this
>>>> spec? Since RFC6325 already specifies an extension mechanism, what
>>>> stops an extension from ignoring this spec and doing something
>>>> different? Does it hurt if they do?
>>>
>>> I am not aware of any conflicts between this draft and RFC 6325. RFC
>>> 6325 provides the broadest header option framework, for example
>>> specifying the field for the length of the options area and the
>>> initial two critical summary bits. This document fills in the
>>> structure and allocation mechanism of the remaining bits in the first
>>> 4-byte word of the options area, consistent with and repeating some
>>> material from RFC 6325, but leaving specification of the remainder of
>>> the options area for future documents, which should be consistent with
>>> both RFC 6325 and this document. (For example, some future version of
>>> draft-ietf-trill-rbridge-options.)
>>
>> I agree there is no conflict--this draft adds details, but doesn't seem =
to contradict anything in the RFC.
>>
>>>
>>> However, neither RFC 6325 nor this document can actually actually bind
>>> the IETF against adopting future standards describing extensions that
>>> do not conform.
>>
>> Certainly. Nothing can do that. The IETF can always update a protocol to=
 change normative language, no matter how strongly it was stated originally=
 :-)
>>
>>> If future changes do not follow RFC 6325 or this
>>> document, for example changing the location or interpretation of the
>>> option length field in the TRILL Header or changing the interpretation
>>> of the critical summary bits in the first word of the options area,
>>> then this would break hardware and software implementations that
>>> depend on RFC 6325 and/or this document. But I trust the IETF to
>>> adhere to its usually high standards for backwards compatibility.
>>>
>>> Perhaps this draft should, in the first page header, say "Updates:
>>> 6325", not in the sense that it makes a change but in the sense that
>>> it fills in more details.
>>>
>>
>> Assuming the additional details in this draft comprise preferred extensi=
on mechanism, then I think it makes sense to say that somewhere (perhaps a =
SHOULD strength), and also mark it as updating 6325. Adding details is stil=
l an update.
>
> OK.
>
>>>> -- section 2, 3rd paragraph from end: "Non-critical extensions can
>>>> =A0 be safely ignored."
>>>>
>>>> Is that intended to be normative? (Seems like it should be, since
>>>> behavior for critical extensions is normative).
>>>
>>> I think of it as more like the definition of "non-critical".
>>
>> Sure--I mainly mention it to be consistent with the text for "critical" =
extensions, since it did use normative language about dropping frames.
>>
>>>
>>>> -- section 2.1, 1st paragraph, last sentence:
>>>>
>>>> Redundant with normative language in previous section.
>>>
>>> ? There is a normative requirement to discard frames with any
>>> unimplemented critical hop-by-hop options present, which might be
>>> thought to require examination of all options (something manifestly
>>> impossible since the format of options beyond the first word of the
>>> options area is not yet normatively specified). The sentence to which
>>> you refer just clarifies that testing the appropriate crtical summary
>>> bit(s) in the first word of the options area, if that word is present,
>>> is all that is required.
>>
>> section 2 says "Any RBridge receiving a frame with a critical hop-by-hop=
 extension =A0that it does not implement MUST discard the frame...". Sectio=
n 2.1 says "If an RBridge does not implement all critical flags in a TRILL =
Data frame, it MUST discard the frame..." These really seem like the same M=
UST (i.e, if you updated one but not the other, you would have an ambiguous=
 state). The same is true for the egress bit.
>>
>> I understand that you want to draw the connection between a "critical ex=
tension" and "critical flags", but it's better to avoid having multiple bit=
s of authoritative text for the same normative requirement. Perhaps it migh=
t be better to say something like "If the RBridge does not implement all cr=
itical flags... it MUST treat the frame as having an unimplemented critical=
 extension as described in section 2"
>
> I'm OK with your suggested wording.
>
>>>
>>>> -- section 2.3, first paragraph:
>>>>
>>>> Is the first sentence intended as normative?
>>>
>>> Yes. When one is describing part of a protocol and you say that some
>>> particular contiguous block of bits is some particular field (and then
>>> possibly describe the sub-structure of that field) isn't that always
>>> normative?
>>
>> Never mind, I misread the sentence. Sorry for the confusion.
>>
>>>
>>>> -- section 6, last paragraph:
>>>>
>>>> No security implications of this are mentioned. Is it really a
>>>> security consideration?
>>>>
>>>> Also, is this more likely to be set incorrectly than all the other
>>>> things that some implementation might screw up, so that it warrants
>>>> special treatment?
>>>
>>> I tend to think that a discussion of what happens if bits are
>>> corrupted or incorrectly set is something reasonable for the Security
>>> Considerations section, although it could be elsewhere. The second
>>> paragraph/sentence of this section says that security considerations
>>> for any bits in the first word of the options area will be in the
>>> document specifying those bits. This document specifies the critical
>>> summary bits and the RBridge Channel Alert bits so there is text on
>>> both of those in its Security Considerations Section.
>>
>> On re-reading the paragraph, I can see interpreting it to mean that inco=
rrectly set flags explicitly do not cause a security problem, which I agree=
 is reasonable to say in the security considerations. So, never mind :-)
>>
>> [...]
>>
>>
>>>>
>>>> -- section 2, bullet list, 2nd bullet: " ... which would only
>>>> =A0 necessarily affect the RBridge(s) where a TRILL frame is
>>>> =A0 decapsulated"
>>>>
>>>> Does that mean it always affects the decapsulating RBridge but might
>>>> effect transit RBridges as well?
>>>
>>> Yes.
>>>
>>
>> Okay, no problem.
>>
>>>> -- section 2, first paragraph after bullet list: "critical
>>>> =A0 hop-by-hop extension"
>>>>
>>>> I assume this means an extension with the critical flag set? If so,
>>>> it would be more precise to say that.
>>>
>>> This draft was split out of a more general draft that covered
>>> extensions in general. The three paragraphs after the bullet list on
>>> critical / non-critical extensions apply to all extensions as well as
>>> the flag bits in the first word of the options area. So this means
>>> critical header extensions flags and any other types of critical
>>> options specified in the future.
>>
>> Okay
>>
>> [...]
>>
>>
>>>
>>>> -- section 5:
>>>>
>>>> Since section 3 is entirely composed of the referenced table, and
>>>> seems to exist mostly if not entirely for the purpose of this
>>>> reference, why not just move the table to the IANA considerations
>>>> section.
>>>
>>> (Looking at Section 3, I believe the reference there to the IANA
>>> Considerations Section should be to Section 5 rather than Section 6.)
>>>
>>> I guess I don't actually see any problem with the current document
>>> structure that I think flows better for someone reading it from the
>>> start. I suppose it imposes a tiny burden on someone who is just
>>> looking at the IANA Considerations Section. I don't see why it would
>>> be better to make it a tiny bit easier for someone just looking at the
>>> IANA Considerations Section while imposing a tiny burdne on those
>>> reading through the document from the start.
>>>
>>
>> Okay. I was interpreting it as existing entirely for the IANA registrati=
on--but if you believe it adds value to the "body" of the text, I am okay w=
ith it.
>>
>> [...]
>
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> =A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
> =A0155 Beaver Street,=A0Milford, MA 01757 USA
> =A0d3e3e3@gmail.com

--14dae9341241881f6e04c195b0c1
Content-Type: text/plain; charset=US-ASCII; name="re31fftoc.txt"
Content-Disposition: attachment; filename="re31fftoc.txt"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_h30gaqp80

ClRSSUxMIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IERvbmFsZCBFYXN0bGFrZQpJTlRFUk5FVC1EUkFGVCAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICBIdWF3ZWkKSW50ZW5kZWQgc3RhdHVzOiBQcm9wb3Nl
ZCBTdGFuZGFyZCAgICAgICAgICAgICAgICAgICAgICAgIEFub29wIEdoYW53YW5pClVwZGF0ZXM6
IDYzMjUgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgRGVsbAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgVmlzaHdhcyBNYW5yYWwKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEhQCiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFlpemhvdSBMaQog
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBIdWF3ZWkKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgQ2FpdGxpbiBCZXN0bGVyCiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUXVhbnR1bQpFeHBpcmVzOiBE
ZWNlbWJlciAyLCAyMDEyICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBKdW5lIDMs
IDIwMTIKCiAgICAgICAgICAgICAgICAgICAgICAgIFRSSUxMOiBIZWFkZXIgRXh0ZW5zaW9uCiAg
ICAgICAgICA8ZHJhZnQtaWV0Zi10cmlsbC1yYnJpZGdlLWV4dGVuc2lvbi0wNWNhbmRpZGF0ZS50
eHQ+CgoKQWJzdHJhY3QKCiAgIFRoZSBJRVRGIFRSSUxMIChUcmFuc3BhcmVudCBJbnRlcmNvbm5l
Y3Rpb24gb2YgTG90cyBvZiBMaW5rcykgYmFzZQogICBwcm90b2NvbCBzcGVjaWZpZXMgbWluaW1h
bCBob29rcyB0byBzYWZlbHkgc3VwcG9ydCBUUklMTCBIZWFkZXIKICAgZXh0ZW5zaW9ucy4gVGhp
cyBkb2N1bWVudCBzcGVjaWZpZXMgYW4gaW5pdGlhbCBleHRlbnNpb24gcHJvdmlkaW5nCiAgIGFk
ZGl0aW9uYWwgZmxhZyBiaXRzIGFuZCBzcGVjaWZpZXMgdHdvIG9mIHRob3NlIGJpdHMuIEl0IHVw
ZGF0ZXMgUkZDCiAgIDYzMjUuCgoKU3RhdHVzIG9mIFRoaXMgTWVtbwoKICAgVGhpcyBJbnRlcm5l
dC1EcmFmdCBpcyBzdWJtaXR0ZWQgdG8gSUVURiBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggdGhl
CiAgIHByb3Zpc2lvbnMgb2YgQkNQIDc4IGFuZCBCQ1AgNzkuCgogICBEaXN0cmlidXRpb24gb2Yg
dGhpcyBkb2N1bWVudCBpcyB1bmxpbWl0ZWQuIENvbW1lbnRzIHNob3VsZCBiZSBzZW50CiAgIHRv
IHRoZSBUUklMTCB3b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdCA8cmJyaWRnZUBwb3N0ZWwub3Jn
Pi4KCiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVy
bmV0IEVuZ2luZWVyaW5nCiAgIFRhc2sgRm9yY2UgKElFVEYpLCBpdHMgYXJlYXMsIGFuZCBpdHMg
d29ya2luZyBncm91cHMuICBOb3RlIHRoYXQKICAgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3Ry
aWJ1dGUgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQtCiAgIERyYWZ0cy4KCiAgIEludGVy
bmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4
IG1vbnRocwogICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkg
b3RoZXIgZG9jdW1lbnRzIGF0IGFueQogICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0ZSB0byB1
c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZQogICBtYXRlcmlhbCBvciB0byBjaXRlIHRo
ZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iCgogICBUaGUgbGlzdCBvZiBjdXJy
ZW50IEludGVybmV0LURyYWZ0cyBjYW4gYmUgYWNjZXNzZWQgYXQKICAgaHR0cDovL3d3dy5pZXRm
Lm9yZy8xaWQtYWJzdHJhY3RzLmh0bWwuIFRoZSBsaXN0IG9mIEludGVybmV0LURyYWZ0CiAgIFNo
YWRvdyBEaXJlY3RvcmllcyBjYW4gYmUgYWNjZXNzZWQgYXQKICAgaHR0cDovL3d3dy5pZXRmLm9y
Zy9zaGFkb3cuaHRtbC4KCgoKCgoKCgpELiBFYXN0bGFrZSwgZXQgYWwgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgW1BhZ2UgMV0KDApJTlRFUk5FVC1EUkFGVCAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgVFJJTEw6IEhlYWRlciBFeHRlbnNpb24K
CgpUYWJsZSBvZiBDb250ZW50cwoKICAgICAgMS4gSW50cm9kdWN0aW9uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4zCiAgICAgIDEuMSBDb252ZW50aW9ucyB1c2Vk
IGluIHRoaXMgZG9jdW1lbnQuLi4uLi4uLi4uLi4uLi4uLi4uLi4uMwoKICAgICAgMi4gVFJJTEwg
SGVhZGVyIEV4dGVuc2lvbnMuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi40CiAgICAg
IDIuMSBSQnJpZGdlIEV4dGVuZGVkIEZsYWcgSGFuZGxpbmcgUmVxdWlyZW1lbnRzLi4uLi4uLi4u
Li4uNQogICAgICAyLjIgTm8gQ3JpdGljYWwgU3VycHJpc2VzLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLjUKICAgICAgMi4zIEV4dGVuZGVkIEhlYWRlciBGbGFncy4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi42CiAgICAgIDIuMy4xIENyaXRpY2FsIFN1bW1hcnkgQml0
cy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uNwogICAgICAyLjQgQ29uZmxpY3Qgb2Yg
RXh0ZW5zaW9ucy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjgKCiAgICAgIDMuIFNw
ZWNpZmljIEV4dGVuZGVkIEhlYWRlciBGbGFncy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uOQog
ICAgICAzLjEgVGhlIFJCcmlkZ2UgQ2hhbm5lbCBBbGVydCBFeHRlbmRlZCBGbGFncy4uLi4uLi4u
Li4uLi4uLjkKCiAgICAgIDQuIEFkZGl0aW9ucyB0byBJUy1JUy4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4xMAoKICAgICAgNS4gSUFOQSBDb25zaWRlcmF0aW9ucy4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjEwCiAgICAgIDYuIFNlY3VyaXR5IENvbnNpZGVy
YXRpb25zLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4xMQogICAgICA3LiBBY2tub3ds
ZWRnZW1lbnRzLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uMTEKICAgICAg
OC4gTm9ybWF0aXZlIFJlZmVyZW5jZXMuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
LjEyCiAgICAgIDkuIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMuLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4xMgoKICAgICAgQ2hhbmdlIEhpc3RvcnkuLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLjEzCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgpELiBF
YXN0bGFrZSwgZXQgYWwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgW1BhZ2UgMl0KDApJTlRFUk5FVC1EUkFGVCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgVFJJTEw6IEhlYWRlciBFeHRlbnNpb24KCgoxLiBJbnRyb2R1Y3Rpb24KCiAgIFRoZSBi
YXNlIElFVEYgVFJJTEwgKFRyYW5zcGFyZW50IEludGVyY29ubmVjdGlvbiBvZiBMb3RzIG9mIExp
bmtzKQogICBwcm90b2NvbCBbUkZDNjMyNV0gW1JGQzYzMjZiaXNdIHByb3ZpZGVzIGEgVFJJTEwg
SGVhZGVyIGV4dGVuc2lvbgogICBmZWF0dXJlIGFuZCBkZXNjcmliZXMgbWluaW1hbCBob29rcyB0
byBzYWZlbHkgc3VwcG9ydCBoZWFkZXIKICAgZXh0ZW5zaW9uLiAoVGhpcyBmZWF0dXJlIGlzIGNh
bGxlZCAib3B0aW9ucyIgaW4gU2VjdGlvbiAzLjggb2YKICAgW1JGQzYzMjVdLikgQnV0LCBleGNl
cHQgZm9yIHRoZSBmaXJzdCB0d28gYml0cywgdGhlIGJhc2UgVFJJTEwKICAgcHJvdG9jb2wgZG9l
cyBub3Qgc3BlY2lmeSB0aGUgc3RydWN0dXJlIG9mIGV4dGVuc2lvbnMgdG8gdGhlIFRSSUxMCiAg
IEhlYWRlciBub3IgdGhlIGRldGFpbHMgb2YgYW55IHBhcnRpY3VsYXIgZXh0ZW5zaW9uLiBUaGlz
IGRvY3VtZW50CiAgIHNwZWNpZmllcyBhbiBpbml0aWFsIGV4dGVuc2lvbiBwcm92aWRpbmcgYWRk
aXRpb25hbCBmbGFnIGJpdHMgYW5kCiAgIHNwZWNpZmllcyBvbmUgb2YgdGhvc2UgYml0cy4gQWRk
aXRpb25hbCBleHRlbnNpb25zLCBpbmNsdWRpbmcgVExWCiAgIChUeXBlLCBMZW5ndGgsIFZhbHVl
KSBlbmNvZGVkIG9wdGlvbnMsIG1heSBiZSBzcGVjaWZpZWQgaW4gbGF0ZXIKICAgZG9jdW1lbnRz
LgoKICAgU2VjdGlvbiAyIGJlbG93IGRlc2NyaWJlcyBzb21lIGdlbmVyYWwgcHJpbmNpcGxlcyBv
ZiBUUklMTCBoZWFkZXIKICAgZXh0ZW5zaW9ucyBhbmQgYW4gaW5pdGlhbCBleHRlbnNpb24uICBT
ZWN0aW9uIDMgc3BlY2lmaWVzIHBhaXIgb2YKICAgZmxhZ3MgaW4gdGhpcyBpbml0aWFsIGV4dGVu
c2lvbi4KCgoKMS4xIENvbnZlbnRpb25zIHVzZWQgaW4gdGhpcyBkb2N1bWVudAoKICAgVGhlIHRl
cm1pbm9sb2d5IGFuZCBhY3JvbnltcyBkZWZpbmVkIGluIFtSRkM2MzI1XSBhcmUgdXNlZCBoZXJl
aW4KICAgd2l0aCB0aGUgc2FtZSBtZWFuaW5nLiBEZXZpY2VzIGltcGxlbWVudGluZyB0aGUgVFJJ
TEwgcHJvdG9jb2wgYXJlCiAgIHJlZmVycmVkIHRvIGFzIFJCcmlkZ2VzIChSb3V0aW5nIEJyaWRn
ZXMpIG9yIFRSSUxMIFN3aXRjaGVzLgoKICAgVGhlIGtleSB3b3JkcyAiTVVTVCIsICJNVVNUIE5P
VCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLAogICAiU0hPVUxEIiwgIlNIT1VM
RCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJT05BTCIgaW4gdGhpcwogICBk
b2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFtSRkMyMTE5XS4K
CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgpELiBFYXN0bGFrZSwgZXQgYWwgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgW1BhZ2UgM10KDApJTlRFUk5FVC1EUkFGVCAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgVFJJTEw6IEhlYWRlciBFeHRlbnNpb24K
CgoyLiBUUklMTCBIZWFkZXIgRXh0ZW5zaW9ucwoKICAgVGhlIGJhc2UgVFJJTEwgUHJvdG9jb2wg
aW5jbHVkZXMgYSBmZWF0dXJlIGZvciBleHRlbnNpb24gb2YgdGhlIFRSSUxMCiAgIEhlYWRlciAo
c2VlIFtSRkM2MzI1XSBTZWN0aW9ucyAzLjUgYW5kIDMuOCkuICBUaGUgNS1iaXQgT3AtTGVuZ3Ro
CiAgIGhlYWRlciBmaWVsZCBnaXZlcyB0aGUgbGVuZ3RoIG9mIHRoZSBleHRlbnNpb25zIHRvIHRo
ZSBUUklMTCBIZWFkZXIKICAgaW4gdW5pdHMgb2YgNCBvY3RldHMsIHdoaWNoIGFsbG93cyB1cCB0
byAxMjQgb2N0ZXRzIG9mIGhlYWRlcgogICBleHRlbnNpb24uIElmIE9wLUxlbmd0aCBpcyB6ZXJv
IHRoZXJlIGFyZSBubyBoZWFkZXIgZXh0ZW5zaW9ucwogICBwcmVzZW50OyBlbHNlLCB0aGUgZXh0
ZW5zaW9uIGFyZWEgZm9sbG93cyBpbW1lZGlhdGVseSBhZnRlciB0aGUKICAgSW5ncmVzcyBSQnJp
ZGdlIChSb3V0aW5nIEJyaWRnZSkgTmlja25hbWUgZmllbGQgb2YgdGhlIFRSSUxMIEhlYWRlci4K
ICAgVGhlIGZpcnN0IDMyLWJpdCB3b3JkIG9mIHRoZSBvcHRpb25hbCBleHRlbnNpb25zIGFyZWEg
Y29uc2lzdHMgb2YgYW4KICAgZXh0ZW5kZWQgZmxhZ3MgYXJlYSBhbmQgY3JpdGljYWwgc3VtbWFy
eSBiaXRzIGFzIHNwZWNpZmllZCBpbiB0aGlzCiAgIGRvY3VtZW50LgoKICAgQXMgZGVzY3JpYmVk
IGJlbG93LCBwcm92aXNpb24gaXMgbWFkZSBmb3IKCiAgICAgIG8gIGhvcC1ieS1ob3AgZmxhZ3Ms
IHdoaWNoIG1pZ2h0IGFmZmVjdCBhbnkgUkJyaWRnZSB0aGF0IHJlY2VpdmVzCiAgICAgICAgIGEg
VFJJTEwgRGF0YSBmcmFtZSB3aXRoIHN1Y2ggYSBmbGFnIHNldCwKCiAgICAgIG8gIGluZ3Jlc3Mt
dG8tZWdyZXNzIGZsYWdzLCB3aGljaCB3b3VsZCBvbmx5IG5lY2Vzc2FyaWx5IGFmZmVjdAogICAg
ICAgICB0aGUgUkJyaWRnZShzKSB3aGVyZSBhIFRSSUxMIGZyYW1lIGlzIGRlY2Fwc3VsYXRlZCwK
CiAgICAgIG8gIGZsYWdzIGFmZmVjdGluZyBhbiBhcyB5ZXQgdW5zcGVjaWZpZWQgY2xhc3Mgb2Yg
UkJyaWRnZXMsIGZvcgogICAgICAgICBleGFtcGxlIGJvcmRlciBSQnJpZGdlcyBpbiBhIFRSSUxM
IGNhbXB1cyBleHRlbmRlZCB0byBzdXBwb3J0CiAgICAgICAgIG11bHRpLWxldmVsIElTLUlTIChJ
bnRlcm1lZGlhdGUgU3lzdGVtIHRvIEludGVybWVkaWF0ZSBTeXN0ZW0pLAogICAgICAgICBhbmQK
CiAgICAgIG8gIGJvdGggImNyaXRpY2FsIiBhbmQgIm5vbi1jcml0aWNhbCIgZmxhZ3MuCgogICBB
bnkgUkJyaWRnZSByZWNlaXZpbmcgYSBmcmFtZSB3aXRoIGEgY3JpdGljYWwgaG9wLWJ5LWhvcCBl
eHRlbnNpb24KICAgdGhhdCBpdCBkb2VzIG5vdCBpbXBsZW1lbnQgTVVTVCBkaXNjYXJkIHRoZSBm
cmFtZSBiZWNhdXNlIGl0IGlzCiAgIHVuc2FmZSB0byBwcm9jZXNzIHRoZSBmcmFtZSB3aXRob3V0
IHVuZGVyc3RhbmRpbmcgc3VjaCBhIGNyaXRpY2FsCiAgIGV4dGVuc2lvbi4KCiAgIEFueSBlZ3Jl
c3MgUkJyaWRnZSByZWNlaXZpbmcgYSBmcmFtZSB3aXRoIGEgY3JpdGljYWwgaW5ncmVzcy10by0K
ICAgZWdyZXNzIGV4dGVuc2lvbiBpdCBkb2VzIG5vdCBpbXBsZW1lbnQgTVVTVCBkcm9wIHRoZSBm
cmFtZSBpZiBpdCBpcyBhCiAgIGtub3duIHVuaWNhc3QgZnJhbWU7IGlmIGl0IGlzIGEgbXVsdGkt
ZGVzdGluYXRpb24gVFJJTEwgRGF0YSBmcmFtZSwKICAgdGhlbiBpdCBNVVNUIE5PVCBiZSBlZ3Jl
c3NlZCBhdCB0aGF0IFJCcmlkZ2UgYnV0IHRoZSBlZ3Jlc3MgUkJyaWRnZQogICBzdGlsbCBmb3J3
YXJkcyBzdWNoIGEgZnJhbWUgb24gdGhlIGRpc3RyaWJ1dGlvbiB0cmVlLgoKICAgTm9uLWNyaXRp
Y2FsIGV4dGVuc2lvbnMgY2FuIGJlIHNhZmVseSBpZ25vcmVkLgoKICAgQW55IGV4dGVuZGVkIGZs
YWcgaW5kaWNhdGluZyBhIHNpZ25pZmljYW50IGNoYW5nZSBpbiB0aGUgc3RydWN0dXJlIG9yCiAg
IGludGVycHJldGF0aW9uIG9mIGxhdGVyIHBhcnRzIG9mIHRoZSBmcmFtZSB3aGljaCwgaWYgdGhl
IGV4dGVuZGVkCiAgIGZsYWcgd2VyZSBpZ25vcmVkLCBjb3VsZCBjYXVzZSBhIGZhaWx1cmUgb2Yg
c2VydmljZSBvciB2aW9sYXRpb24gb2YKICAgc2VjdXJpdHkgcG9saWN5IE1VU1QgYmUgYSBjcml0
aWNhbCBleHRlbnNpb24uIElmIHN1Y2ggYW4gZXh0ZW5kZWQKICAgZmxhZyBhZmZlY3RzIGFueSBm
aWVsZHMgdGhhdCB0cmFuc2l0IFJCcmlkZ2VzIHdpbGwgZXhhbWluZSwgaXQgTVVTVAogICBiZSBh
IGhvcC1ieS1ob3AgY3JpdGljYWwgZXh0ZW5kZWQgZmxhZy4KCiAgICAgIE5vdGU6IE1vc3QgUkJy
aWRnZXMgaW1wbGVtZW50YXRpb25zIGFyZSBleHBlY3RlZCB0byBiZSBvcHRpbWl6ZWQKICAgICAg
Zm9yIHNpbXBsZSBhbmQgY29tbW9uIGNhc2VzIG9mIGZyYW1lIGZvcndhcmRpbmcgYW5kIHByb2Nl
c3NpbmcuCgoKRC4gRWFzdGxha2UsIGV0IGFsICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIFtQYWdlIDRdCgwKSU5URVJORVQtRFJBRlQgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIFRSSUxMOiBIZWFkZXIgRXh0ZW5zaW9uCgoKICAgICAgQWx0aG91
Z2ggdGhlIGhhcmQgbGltaXQgb24gdGhlIGhlYWRlciBleHRlbnNpb25zIGFyZWEgbGVuZ3RoLCB0
aGUKICAgICAgMzItYml0IGFsaWdubWVudCBvZiB0aGUgZXh0ZW5zaW9uIGFyZWEsIGFuZCB0aGUg
cHJlc2VuY2Ugb2YKICAgICAgY3JpdGljYWwgZXh0ZW5zaW9uIHN1bW1hcnkgYml0cywgYXMgZGVz
Y3JpYmVkIGJlbG93LCBhcmUgaW50ZW5kZWQKICAgICAgdG8gYXNzaXN0IGluIHRoZSBlZmZpY2ll
bnQgaGFyZHdhcmUgcHJvY2Vzc2luZyBvZiBmcmFtZXMgd2l0aCBhCiAgICAgIFRSSUxMIGhlYWRl
ciBleHRlbnNpb25zIGFyZWEsIG5ldmVydGhlbGVzcyB0aGUgaW5jbHVzaW9uIG9mCiAgICAgIGV4
dGVuc2lvbnMgbWF5IGNhdXNlIGZyYW1lIHByb2Nlc3NpbmcgdXNpbmcgYSAic2xvdyBwYXRoIiB3
aXRoCiAgICAgIGluZmVyaW9yIHBlcmZvcm1hbmNlIHRvICJmYXN0IHBhdGgiIHByb2Nlc3Npbmcu
IExpbWl0ZWQgc2xvdyBwYXRoCiAgICAgIHRocm91Z2hwdXQgb2Ygc3VjaCBmcmFtZXMgY291bGQg
Y2F1c2Ugc29tZSBvZiB0aGVtIHRvIGJlCiAgICAgIGRpc2NhcmRlZC4KCgoKMi4xIFJCcmlkZ2Ug
RXh0ZW5kZWQgRmxhZyBIYW5kbGluZyBSZXF1aXJlbWVudHMKCiAgIEFsbCBSQnJpZGdlcyBNVVNU
IGNoZWNrIHdoZXRoZXIgdGhlcmUgYXJlIGFueSBjcml0aWNhbCBmbGFncyBzZXQgdGhhdAogICBh
cmUgbmVjZXNzYXJpbHkgYXBwbGljYWJsZSB0byB0aGVpciBwcm9jZXNzaW5nIG9mIHRoZSBmcmFt
ZS4gVG8KICAgYXNzaXN0IGluIHRoaXMgdGFzaywgY3JpdGljYWwgc3VtbWFyeSBiaXRzIGFyZSBw
cm92aWRlZCB0aGF0IGNvdmVyCiAgIG5vdCBvbmx5IHRoZSBleHRlbmRlZCBmbGFncyBzcGVjaWZp
ZWQgaGVyZWluIGJ1dCB3aWxsIGNvdmVyIGFueQogICBmdXJ0aGVyIGV4dGVuc2lvbnMgdGhhdCBt
YXkgYmUgc3BlY2lmaWVkIGluIGZ1dHVyZSBkb2N1bWVudHMsIGZvcgogICBleGFtcGxlIFtPcHRp
b25zXS4gSWYgYW4gUkJyaWRnZSBkb2VzIG5vdCBpbXBsZW1lbnQgYWxsIGNyaXRpY2FsCiAgIGZs
YWdzIGluIGEgVFJJTEwgRGF0YSBmcmFtZSwgaXQgTVVTVCB0cmVhdCB0aGUgZnJhbWUgYXMgaGF2
aW5nIGFuCiAgIHVuaW1wbGVtZW50ZWQgY3JpdGljYWwgZXh0ZW5zaW9uIGFzIGRlc2NyaWJlZCBp
biBTZWN0aW9uIDIuIEEgdHJhbnNpdAogICBvciBlZ3Jlc3MgUkJyaWRnZSBtYXkgYXNzdW1lIHRo
YXQgdGhlIGNyaXRpY2FsIHN1bW1hcnkgYml0cyBhcmUKICAgY29ycmVjdC4KCiAgIEluIGFkZGl0
aW9uLCBhIHRyYW5zaXQgUkJyaWRnZToKCiAgIG8gIE1BWSBzZXQgb3IgY2xlYXIgaG9wLWJ5LWhv
cCBmbGFncyBhcyBzcGVjaWZpZWQgZm9yIHN1Y2ggZmxhZ3M7CiAgIG8gIE1VU1QgYWRqdXN0IHRo
ZSBsZW5ndGggb2YgdGhlIGV4dGVuc2lvbnMgYXJlYSwgaW5jbHVkaW5nIGNoYW5naW5nCiAgICAg
IE9wLUxlbmd0aCBpbiB0aGUgVFJJTEwgaGVhZGVyLCBhcyBhcHByb3ByaWF0ZSBpZiBpdCBhZGRz
IG9yCiAgICAgIHJlbW92ZXMgdGhlIHdvcmQgb2YgZXh0ZW5kZWQgaGVhZGVyIGZsYWdzOwogICBv
ICBNVVNULCBpZiBpdCBhZGRzIHRoZSB3b3JkIG9mIGV4dGVuZGVkIGhlYWRlciBmbGFncyBvciBj
aGFuZ2VzIGFueQogICAgICBjcml0aWNhbCBmbGFncywgY29ycmVjdGx5IHNldCB0aGUgY3JpdGlj
YWwgc3VtbWFyeSBiaXRzIGluIHRoZQogICAgICBleHRlbmRlZCBoZWFkZXIgZmxhZ3Mgd29yZDsK
ICAgbyAgTVVTVCBOT1QgcmVtb3ZlIHRoZSBleHRlbmRlZCBoZWFkZXIgZmxhZ3Mgd29yZCB1bmxl
c3MgaXQgaXMgYWxsCiAgICAgIHplcm8gKGVpdGhlciBvbiBhcnJpdmFsIG9yIGFmdGVyIHBlcm1p
dHRlZCBtb2RpZmljYXRpb25zKTsKICAgbyAgTVVTVCBOT1Qgc2V0IG9yIGNsZWFyIGluZ3Jlc3Mt
dG8tZWdyZXNzIG9yIHJlc2VydmVkIGV4dGVuZGVkCiAgICAgIGhlYWRlciBmbGFncyBleGNlcHQg
YXMgc3BlY2lmaWNhbGx5IHBlcm1pdHRlZCBpbiB0aGUgc3BlY2lmaWNhdGlvbgogICAgICBvZiBz
dWNoIGZsYWdzLgoKCgoyLjIgTm8gQ3JpdGljYWwgU3VycHJpc2VzCgogICBSQnJpZGdlcyBhZHZl
cnRpc2UgdGhlIGV4dGVuZGVkIGhlYWRlciBmbGFncyB0aGV5IHN1cHBvcnQgaW4gSVMtSVMKICAg
UERVcyAoUHJvdG9jb2wgRGF0YSBVbml0cykgW1JGQzYzMjZiaXNdLiBVbmxlc3MgYW4gUkJyaWRn
ZSBhZHZlcnRpc2VzCiAgIHN1cHBvcnQgZm9yIGEgY3JpdGljYWwgZXh0ZW5kZWQgaGVhZGVyIGZs
YWcsIGl0IHdpbGwgbm90IG5vcm1hbGx5CiAgIHJlY2VpdmUgZnJhbWVzIHdpdGggdGhhdCBmbGFn
IHNldC4gQW4gUkJyaWRnZSBpcyBub3QgcmVxdWlyZWQgdG8KICAgc3VwcG9ydCBhbnkgZXh0ZW5z
aW9ucy4KCgoKRC4gRWFzdGxha2UsIGV0IGFsICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIFtQYWdlIDVdCgwKSU5URVJORVQtRFJBRlQgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIFRSSUxMOiBIZWFkZXIgRXh0ZW5zaW9uCgoKICAgQW4gUkJyaWRn
ZSBTSE9VTEQgTk9UIHNldCBhIGNyaXRpY2FsIGV4dGVuZGVkIGZsYWcgaW4gYSBmcmFtZSB1bmxl
c3MsCgogICAtICBmb3IgYSBjcml0aWNhbCBob3AtYnktaG9wIGV4dGVuZGVkIGhlYWRlciBmbGFn
LCBpdCBoYXMgZGV0ZXJtaW5lZAogICAgICB0aGF0IHRoZSBuZXh0IGhvcCBSQnJpZGdlIG9yIFJC
cmlkZ2VzIHRoYXQgd2lsbCBhY2NlcHQgdGhlIGZyYW1lCiAgICAgIHN1cHBvcnQgdGhhdCBmbGFn
LAogICAtICBmb3IgYSBjcml0aWNhbCBpbmdyZXNzLXRvLWVncmVzcyBleHRlbmRlZCBoZWFkZXIg
ZmxhZywgaXQgaGFzCiAgICAgIGRldGVybWluZWQgdGhhdCB0aGUgUkJyaWRnZSBvciBSQnJpZGdl
cyB0aGF0IHdpbGwgZWdyZXNzIHRoZSBmcmFtZQogICAgICBzdXBwb3J0IHRoYXQgZmxhZywgb3IK
ICAgLSAgZm9yIGEgY3JpdGljYWwgcmVzZXJ2ZWQgZXh0ZW5kZWQgaGVhZGVyIGZsYWcsIGl0IG1h
eSBzZXQgc3VjaCBhCiAgICAgIGZsYWcgb25seSBpZiBpdCB1bmRlcnN0YW5kcyB3aGljaCBSQnJp
ZGdlcyBpdCBpcyBhcHBsaWNhYmxlIHRvIGFuZAogICAgICBoYXMgZGV0ZXJtaW5lZCB0aGF0IHRo
b3NlIFJCcmlkZ2VzIHRoYXQgd2lsbCBhY2NlcHQgdGhlIGZyYW1lCiAgICAgIHN1cHBvcnQgdGhh
dCBmbGFnLgoKICAgIlNIT1VMRCBOT1QiIGlzIHNwZWNpZmllZCBhYm92ZSBzaW5jZSB0aGVyZSBt
YXkgYmUgY2FzZXMgd2hlcmUgaXQgaXMKICAgYWNjZXB0YWJsZSBmb3IgdGhvc2UgZnJhbWVzLCBw
YXJ0aWN1bGFybHkgZm9yIHRoZSBtdWx0aS1kZXN0aW5hdGlvbgogICBjYXNlLCB0byBiZSBkaXNj
YXJkZWQgb3Igbm90IGVncmVzc2VkIGJ5IGFueSBSQnJpZGdlcyB0aGF0IGRvIG5vdAogICBpbXBs
ZW1lbnQgdGhlIGV4dGVuZGVkIGZsYWcuCgoKCjIuMyBFeHRlbmRlZCBIZWFkZXIgRmxhZ3MKCiAg
IElmIGFueSBleHRlbnNpb25zIGFyZSBwcmVzZW50IGluIGEgVFJJTEwgSGVhZGVyLCBhcyBpbmRp
Y2F0ZWQgYnkgYQogICBub24temVybyBPcC1MZW5ndGggZmllbGQsIHRoZSBmaXJzdCAzMiBiaXRz
IG9mIHRoZSBleHRlbnNpb25zIGFyZWEKICAgY29uc2lzdCBvZiBFeHRlbmRlZCBIZWFkZXIgRmxh
Z3MsIGFzIGRlc2NyaWJlZCBiZWxvdy4gVGhlIHJlbWFpbmRlcgogICBvZiB0aGUgZXh0ZW5zaW9u
cyBhcmVhLCBpZiBhbnksIGFmdGVyIHRoaXMgaW5pdGlhbCAzMiBiaXRzLCBtYXkgYmUKICAgc3Bl
Y2lmaWVkIGluIGxhdGVyIGRvY3VtZW50cyBbT3B0aW9uc10uCgogICBBbnkgUkJyaWRnZSBhZGRp
bmcgYW4gZXh0ZW5zaW9ucyBhcmVhIHRvIGEgVFJJTEwgSGVhZGVyIG11c3Qgc2V0IHRoZQogICBm
aXJzdCAzMiBiaXRzIHRvIHplcm8gZXhjZXB0IHdoZW4gcGVybWl0dGVkIG9yIHJlcXVpcmVkIHRv
IHNldCBvbmUgb3IKICAgbW9yZSBvZiB0aG9zZSBiaXRzIGFzIHNwZWNpZmllZC4gRm9yIFRSSUxM
IERhdGEgZnJhbWVzIHdpdGgKICAgZXh0ZW5zaW9ucyBwcmVzZW50LCBhbnkgdHJhbnNpdCBSQnJp
ZGdlIHRoYXQgZG9lcyBub3QgZGlzY2FyZCB0aGUKICAgZnJhbWUgTVVTVCB0cmFuc3BhcmVudGx5
IGNvcHkgdGhlIGV4dGVuZGVkIGZsYWdzIHdvcmQsIGV4Y2VwdCBmb3IKICAgbW9kaWZpY2F0aW9u
cyBwZXJtaXR0ZWQgYnkgYW4gZXh0ZW5zaW9uIGltcGxlbWVudGVkIGJ5IHRoYXQgUkJyaWRnZS4K
CiAgIFRoZSB3b3JkIG9mIEV4dGVuZGVkIEhlYWRlciBGbGFncyBpcyBpbGx1c3RyYXRlZCBiZWxv
dyBhbmQgdGhlCiAgIG1lYW5pbmdzIG9mIHRoZXNlIGJpdHMgaXMgZnVydGhlciBkZXNjcmliZWQg
aW4gdGhlIGxpc3QgZm9sbG93aW5nIHRoZQogICBmaWd1cmUuCgogICAgICAgICAgICAgICAgICAg
ICAgICAxIDEgMSAxIDEgMSAxIDEgMSAxIDIgMiAyIDIgMiAyIDIgMiAyIDIgMyAzCiAgICAwIDEg
MiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAw
IDEKICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSsKICAgfENyaXQufCAgQ0hiSCAgIHwgICBOQ0hiSCAgIHxDUlNWIHwgTkNS
U1YgfCAgIENJdEUgICAgfCAgTkNJdEUgIHwKICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsKICAgfCAuLi4gYWRkaXRpb25h
bCBvcHRpb25hbCAzMi1iaXQgYWxpZ25lZCB3b3JkcyBvZiBleHRlbnNpb24gICAgIHwKICAgfCAg
ICAgcG9zc2libHkgaW5jbHVkaW5nIFRMViBleHRlbnNpb25zIC4uLgoKCgoKCgpELiBFYXN0bGFr
ZSwgZXQgYWwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgW1Bh
Z2UgNl0KDApJTlRFUk5FVC1EUkFGVCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
VFJJTEw6IEhlYWRlciBFeHRlbnNpb24KCgogICAoVGhlIGZpcnN0IHR3byBjcml0aWNhbCBzdW1t
YXJ5IGJpdHMgYXJlIGFzIHNwZWNpZmllZCBpbiBbUkZDNjMyNV0uCiAgIEluIHRoaXMgZG9jdW1l
bnQgYW4gIlMiLCBmb3IgU3VtbWFyeSwgaGFzIGJlZW4gYWRkZWQgYXQgdGhlIGVuZCBvZgogICB0
aGVpciBhY3Jvbnltcy4pCgogICBCaXQocykgICBEZXNjcmlwdGlvbgogICAtLS0tLS0tLS0tLS0t
LS0tLS0tLS0KCiAgICAwLTMgIENyaXQuOiBDcml0aWNhbCBzdW1tYXJ5IGJpdHMuCiAgICAgICAg
IDAgQ0hiSFM6IENyaXRpY2FsIEhvcC1ieS1Ib3AgZXh0ZW5zaW9uKHMpIGFyZSBwcmVzZW50Lgog
ICAgICAgICAxIENJdEVTOiBDcml0aWNhbCBJbmdyZXNzLXRvLUVncmVzcyBleHRlbnNpb24ocykg
YXJlIHByZXNlbnQuCiAgICAgICAgIDIgQ1JTVlM6IENyaXRpY2FsIHJlc2VydmVkIGV4dGVuc2lv
bihzKSBhcmUgcHJlc2VudC4KCiAgICAzLTcgICBDSGJIOiBDcml0aWNhbCBIb2ItYnktSG9wIGV4
dGVuZGVkIEZsYWcgYml0cy4KICAgIDgtMTMgIE5DSGJIOiBOb24tY3JpdGljYWwgSG9wLWJ5LUhv
cCBleHRlbmRlZCBGbGFnIGJpdHMuCgogICAgMTQtMTYgQ1JTVjogQ3JpdGljYWwgUmVzZXJ2ZWQg
ZXh0ZW5kZWQgRmxhZyBiaXRzLgogICAgMTctMjAgTkNSU1Y6IE5vbi1jcml0aWNhbCBSZXNlcnZl
ZCBleHRlbmRlZCBGbGFnIGJpdHMuCgogICAgMjEtMjYgQ0l0RTogQ3JpdGljYWwgSW5ncmVzcy10
by1FZ3Jlc3MgZXh0ZW5kZWQgRmxhZyBiaXRzLgogICAgMjctMzEgTkNJdEU6IE5vbi1jcml0aWNh
bCBJbmdyZXNzLXRvLUVncmVzcyBleHRlbmRlZCBGbGFnIGJpdHMuCgoKCjIuMy4xIENyaXRpY2Fs
IFN1bW1hcnkgQml0cwoKICAgVGhlIHRvcCB0aHJlZSBiaXRzIG9mIHRoZSBFeHRlbmRlZCBIZWFk
ZXIgRmxhZ3MgYXJlYSwgYml0cyAwLCAxLCBhbmQKICAgMiBhYm92ZSwgYXJlIGNhbGxlZCB0aGUg
Y3JpdGljYWwgc3VtbWFyeSBiaXRzLiBUaGV5IHN1bW1hcml6ZSB0aGUKICAgcHJlc2VuY2Ugb2Yg
Y3JpdGljYWwgZXh0ZW5zaW9ucyBhcyBmb2xsb3dzOgoKICAgQ0hiSFM6IElmIHRoZSBDSGJIUyAo
Q3JpdGljYWwgSG9wIGJ5IEhvcCBTdW1tYXJ5KSBiaXQgaXMgb25lLCBvbmUgb3IKICAgICAgbW9y
ZSBjcml0aWNhbCBob3AtYnktaG9wIGV4dGVuc2lvbnMgYXJlIHByZXNlbnQuIFRoZXNlIG1pZ2h0
IGJlCiAgICAgIGNyaXRpY2FsIGhvcC1ieS1ob3AgZXh0ZW5kZWQgaGVhZGVyIGZsYWdzIG9yIGNy
aXRpY2FsIGhvcC1ieS1ob3AKICAgICAgZXh0ZW5zaW9ucyBhZnRlciB0aGUgZmlyc3Qgd29yZCBp
biB0aGUgZXh0ZW5zaW9ucyBhcmVhLiBUcmFuc2l0CiAgICAgIFJCcmlkZ2VzIHRoYXQgZG8gbm90
IHN1cHBvcnQgYWxsIG9mIHRoZSBjcml0aWNhbCBob3AtYnktaG9wCiAgICAgIGV4dGVuc2lvbnMg
cHJlc2VudCwgZm9yIGV4YW1wbGUgYW4gUkJyaWRnZSB0aGF0IHN1cHBvcnRlZCBubwogICAgICBj
cml0aWNhbCBob3AtYnktaG9wIGV4dGVuc2lvbnMsIE1VU1QgZHJvcCB0aGUgZnJhbWUuIElmIHRo
ZSBDSGJIUwogICAgICBiaXQgaXMgemVybywgdGhlIGZyYW1lIGlzIHNhZmUsIGZyb20gdGhlIHBv
aW50IG9mIHZpZXcgb2YKICAgICAgZXh0ZW5zaW9ucyBwcm9jZXNzaW5nLCBmb3IgYSB0cmFuc2l0
IFJCcmlkZ2UgdG8gZm9yd2FyZCwKICAgICAgcmVnYXJkbGVzcyBvZiB3aGF0IGV4dGVuc2lvbnMg
dGhhdCBSQnJpZGdlIGRvZXMgb3IgZG9lcyBub3QKICAgICAgc3VwcG9ydC4KCiAgIENJdEVTOiBJ
ZiB0aGUgQ0l0RVMgKENyaXRpY2FsIEluZ3Jlc3MgdG8gRWdyZXNzIFN1bW1hcnkpIGJpdCBpcyBh
CiAgICAgIG9uZSwgb25lIG9yIG1vcmUgY3JpdGljYWwgaW5ncmVzcy10by1lZ3Jlc3MgZXh0ZW5z
aW9ucyBhcmUKICAgICAgcHJlc2VudC4gVGhlc2UgbWlnaHQgYmUgY3JpdGljYWwgaW5ncmVzcy10
by1lZ3Jlc3MgZXh0ZW5kZWQgaGVhZGVyCiAgICAgIGZsYWdzIG9yIGNyaXRpY2FsIGluZ3Jlc3Mt
dG8tZWdyZXNzIGV4dGVuc2lvbnMgYWZ0ZXIgdGhlIGZpcnN0CiAgICAgIHdvcmQgaW4gdGhlIGV4
dGVuc2lvbnMgYXJlYS4gIElmIHRoZSBDSXRFUyBiaXQgaXMgemVybywgbm8gc3VjaAogICAgICBl
eHRlbnNpb25zIGFyZSBwcmVzZW50LiAgSWYgZWl0aGVyIENIYkhTIG9yIENJdEVTIGlzIG5vbi16
ZXJvLAogICAgICBlZ3Jlc3MgUkJyaWRnZXMgdGhhdCBkbyBub3Qgc3VwcG9ydCBhbGwgY3JpdGlj
YWwgZXh0ZW5zaW9ucwogICAgICBwcmVzZW50LCBmb3IgZXhhbXBsZSBhbiBSQnJpZGdlIHRoYXQg
c3VwcG9ydHMgbm8gY3JpdGljYWwKICAgICAgZXh0ZW5zaW9ucywgTVVTVCBkcm9wIHRoZSBmcmFt
ZS4gIElmIGJvdGggQ0hiSFMgYW5kIENJdEVTIGFyZQoKCkQuIEVhc3RsYWtlLCBldCBhbCAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBbUGFnZSA3XQoMCklOVEVS
TkVULURSQUZUICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBUUklMTDogSGVhZGVy
IEV4dGVuc2lvbgoKCiAgICAgIHplcm8sIHRoZSBmcmFtZSBpcyBzYWZlLCBmcm9tIHRoZSBwb2lu
dCBvZiB2aWV3IG9mIGV4dGVuc2lvbnMsIGZvcgogICAgICBhbiBlZ3Jlc3MgUkJyaWRnZSB0byBw
cm9jZXNzLCByZWdhcmRsZXNzIG9mIHdoYXQgZXh0ZW5zaW9ucyB0aGF0CiAgICAgIFJCcmlkZ2Ug
ZG9lcyBvciBkb2VzIG5vdCBzdXBwb3J0LgoKICAgQ1JTVlM6IElmIHRoZSBDUlNWUyAoQ3JpdGlj
YWwgUmVzZXJ2ZWQgU3VtbWFyeSkgYml0IGlzIGEgb25lLCBvbmUgb3IKICAgICAgbW9yZSBjcml0
aWNhbCBleHRlbnNpb25zIGFyZSBwcmVzZW50IHRoYXQgYXJlIHJlc2VydmVkIHRvIGFwcGx5IHRv
CiAgICAgIGEgY2xhc3Mgb2YgUkJyaWRnZXMgdG8gYmUgc3BlY2lmaWVkIGluIHRoZSBmdXR1cmUs
IGZvciBleGFtcGxlCiAgICAgIGJvcmRlciBSQnJpZGdlcyBpbiBhIFRSSUxMIGNhbXB1cyBleHRl
bmRlZCB0byBzdXBwb3J0IG11bHRpLWxldmVsCiAgICAgIElTLUlTLiBUaGlzIGNsYXNzIHdpbGwg
YmUgYSBzdWJzZXQgb2YgdHJhbnNpdCBSQnJpZGdlcy4gUkJyaWRnZXMKICAgICAgaW4gdGhpcyBj
bGFzcyBNVVNUIGRyb3AgZnJhbWVzIHdpdGggdGhlIENSU1ZTIGJpdCBzZXQgdW5sZXNzIHRoZXkK
ICAgICAgaW1wbGVtZW50IGFsbCBjcml0aWNhbCBob3AtYnktaG9wIGFuZCBhbGwgY3JpdGljYWwg
cmVzZXJ2ZWQKICAgICAgZXh0ZW5zaW9ucyBwcmVzZW50IGluIHRoZSBmcmFtZS4KCiAgIFRoZSBj
cml0aWNhbCBzdW1tYXJ5IGJpdHMgZW5hYmxlIHNpbXBsZSBhbmQgZWZmaWNpZW50IHByb2Nlc3Np
bmcgb2YKICAgVFJJTEwgRGF0YSBmcmFtZXMgYnkgZWdyZXNzIFJCcmlkZ2VzIHRoYXQgc3VwcG9y
dCBubyBjcml0aWNhbAogICBleHRlbnNpb25zLCBieSB0cmFuc2l0IFJCcmlkZ2VzIHRoYXQgc3Vw
cG9ydCBubyBjcml0aWNhbCBob3AtYnktaG9wCiAgIGV4dGVuc2lvbnMsIGFuZCBieSBSQnJpZGdl
cyBpbiB0aGUgcmVzZXJ2ZWQgY2xhc3MgdGhhdCBzdXBwb3J0IG5vCiAgIGNyaXRpY2FsIGhvcC1i
eS1ob3Agb3IgcmVzZXJ2ZWQgZXh0ZW5zaW9ucy4gU3VjaCBSQnJpZGdlcyBuZWVkIG9ubHkKICAg
Y2hlY2sgd2hldGhlciBPcC1MZW5ndGggaXMgbm9uLXplcm8gYW5kLCBpZiBpdCBpcywgdGhlIHRv
cCBvbmUsIHR3bywKICAgb3IgdGhyZWUgYml0cyBqdXN0IGFmdGVyIHRoZSBmaXhlZCBwb3J0aW9u
IG9mIHRoZSBUUklMTCBIZWFkZXIuIEJhc2VkCiAgIG9uIHRob3NlIHRocmVlIGJpdHMsIHN1Y2gg
UkJyaWRnZXMgY2FuIGRlY2lkZSB3aGV0aGVyIHRvIGRpc2NhcmQgb3IKICAgZm9yd2FyZCAvIHBy
b2Nlc3MgdGhlIGZyYW1lLgoKCgoyLjQgQ29uZmxpY3Qgb2YgRXh0ZW5zaW9ucwoKICAgRGVmaW5p
bmcgVFJJTEwgZXh0ZW5zaW9ucyBpbmNsdWRpbmcgRXh0ZW5kZWQgSGVhZGVyIEZsYWdzIHRoYXQK
ICAgY29uZmxpY3Qgd2l0aCBlYWNoIG90aGVyIHdvdWxkIGJlIHVuZGVzaXJhYmxlLiBTaG91bGQg
Y29uZmxpY3RpbmcKICAgZXh0ZW5zaW9ucyBhcHBlYXIgaW4gdGhlIHNhbWUgcGFja2V0LCB0aGUg
cmVzdWx0cyB3b3VsZCBiZQogICB1bnByZWRpY3RhYmxlLCBpZiBkaWZmZXJlbnQgaW1wbGVtZW50
YXRpb25zIHByb2Nlc3NlZCB0aGVtIGluCiAgIGRpZmZlcmVudCBvcmRlcnMuIFdoaWxlIHJ1bGVz
IGNvdWxkIGJlIGRlZmluZWQgdG8gc3BlY2lmeSBob3cgdG8KICAgcHJlZGljdGFibHkgcHJvY2Vz
cyBjb25mbGljdGluZyBleHRlbnNpb25zLCBzdWNoIHJ1bGVzIHdvdWxkIGFsc28KICAgbGltaXQg
aW1wbGVtZW50YXRpb24gZmxleGliaWxpdHkgYW5kIGNvdWxkIGltcG9zZSBzdWJzdGFudGlhbAog
ICBwcm9jZXNzaW5nIGJ1cmRlbnMuCgogICBDb25mbGljdGluZyBleHRlbnNpb25zIFNIT1VMRCBO
T1QgYmUgZGVmaW5lZCwgYnV0IGlmIHRoZXkgYXJlLAogICBjYXJlZnVsIHRob3VnaHQgc2hvdWxk
IGJlIGdpdmVuIGFzIHRvIHdoZXRoZXIgYW5kIGhvdyB0byBzcGVjaWZ5IHRoZQogICBoYW5kbGlu
ZyBvZiBjb25mbGljdGluZyBleHRlbnNpb25zLgoKCgoKCgoKCgoKCgoKRC4gRWFzdGxha2UsIGV0
IGFsICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFtQYWdlIDhd
CgwKSU5URVJORVQtRFJBRlQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFRSSUxM
OiBIZWFkZXIgRXh0ZW5zaW9uCgoKMy4gU3BlY2lmaWMgRXh0ZW5kZWQgSGVhZGVyIEZsYWdzCgog
ICBUaGUgdGFibGUgYmVsb3cgc2hvd3MgdGhlIHN0YXRlIG9mIFRSSUxMIEhlYWRlciBleHRlbmRl
ZCBmbGFnCiAgIGFzc2lnbm1lbnRzLiBTZWUgU2VjdGlvbiA1IGZvciBJQU5BIENvbnNpZGVyYXRp
b25zLgoKICAgICAgIEJpdHMgICAgUHVycG9zZSAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IFNlY3Rpb24KICAgICAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tCiAgICAgICAgMC0yICAgIENyaXRpY2FsIFN1bW1hcnkgQml0cyAgICAgICAg
ICAgICAgICAyLjMuMQogICAgICAgIDMtNiAgICBhdmFpbGFibGUgY3JpdGljYWwgaG9wLWJ5LWhv
cCBmbGFncwogICAgICAgIDcgICAgICBDcml0aWNhbCBDaGFubmVsIEFsZXJ0IEZsYWcgICAgICAg
ICAgMy4xCiAgICAgICAgOCAgICAgIE5vbi1jcml0aWNhbCBDaGFubmVsIEFsZXJ0IEZsYWcgICAg
ICAzLjEKICAgICAgICA5LTEzICAgYXZhaWxhYmxlIG5vbi1jcml0aWNhbCBob3AtYnktaG9wIGZs
YWdzCiAgICAgICAxNC0xNiAgIGF2YWlsYWJsZSBjcml0aWNhbCByZXNlcnZlZCBmbGFncwogICAg
ICAgMTctMjAgICBhdmFpbGFibGUgbm9uLWNyaXRpY2FsIHJlc2VydmVkIGZsYWdzCiAgICAgICAy
MS0yNiAgIGF2YWlsYWJsZSBjcml0aWNhbCBpbmdyZXNzLXRvLWVncmVzcyBmbGFncwogICAgICAg
MjctMzEgICBhdmFpbGFibGUgbm9uLWNyaXRpY2FsIGluZ3Jlc3MtdG8tZWdyZXNzIGZsYWdzCgog
ICAgICAgICAgICAgICAgICAgIFRhYmxlIDEuIEV4dGVuZGVkIEhlYWRlciBGbGFncyBBcmVhCgoK
CjMuMSBUaGUgUkJyaWRnZSBDaGFubmVsIEFsZXJ0IEV4dGVuZGVkIEZsYWdzCgogICBUaGUgUkJy
aWRnZSBDaGFubmVsIEFsZXJ0IEV4dGVuZGVkIEZsYWdzIGluZGljYXRlcyB0aGF0IHRoZSBmcmFt
ZSBpcwogICBhbiBSQnJpZGdlIENoYW5uZWwgZnJhbWUgW0NoYW5uZWxdIHRoYXQgcmVxdWVzdHMg
cHJvY2Vzc2luZyBhdCBlYWNoCiAgIGhvcC4KCiAgIElmIHRoZSBjcml0aWNhbCBDaGFubmVsIEFs
ZXJ0IGZsYWcgKGJpdCA3KSBpcyBhIG9uZSBhbmQgdGhlIFJCcmlkZ2UKICAgZG9lcyBub3QgaW1w
bGVtZW50IHRoZSBSQnJpZGdlIENoYW5uZWwgZmVhdHVyZSBvciB0aGUgcGFydGljdWxhcgogICBS
QnJpZGdlIENoYW5uZWwgcHJvdG9jb2wgaW52b2x2ZWQgW0NoYW5uZWxdIG9yIHRoZSBmcmFtZSBk
b2VzIG5vdAogICBhY3R1YWxseSBhcHBlYXIgdG8gYmUgYW4gUkJyaWRnZSBDaGFubmVsIG1lc3Nh
Z2UsIHRoZW4gdGhlIGZyYW1lIGlzCiAgIGRpc2NhcmRlZC4gVGhpcyBwZXJtaXRzIGltcGxlbWVu
dGF0aW9uLCBmb3IgZXhhbXBsZSwgb2YgYSBDaGFubmVsCiAgIG1lc3NhZ2UgcmVxdWlyaW5nIHN0
cmljdCBzb3VyY2Ugcm91dGluZyBvciB0aGUgbGlrZSwgd2l0aCBhc3N1cmFuY2UKICAgdGhhdCBp
dCB3aWxsIGJlIGRpc2NhcmRlZCByYXRoZXIgdGhhbiBkZXZpYXRlIGZyb20gdGhlIGRpcmVjdGVk
IHBhdGguCgogICBJZiB0aGUgZnJhbWUgaXMgbm90IGRpc2NhcmRlZCBhcyBhYm92ZSB0aGVuIHRo
ZSBwcmVzZW5jZSBvZiBlaXRoZXIKICAgdGhlIENyaXRpY2FsIG9yIE5vbi1jcml0aWNhbCBob3At
YnktaG9wIENoYW5uZWwgQWxlcnQgZmxhZyBhbGVydHMKICAgdHJhbnNpdCBSQnJpZGdlcyB0byB0
aGUgcHJlc2VuY2Ugb2YgYW4gUkJyaWRnZSBDaGFubmVsIG1lc3NhZ2UKICAgW0NoYW5uZWxdIHRo
YXQgbWF5IHJlcXVpcmUgc3BlY2lhbCBoYW5kbGluZy4gVGhlIG5vbi1jcml0aWNhbCBhbGVydAog
ICBmbGFnIHN1cHBvcnRzLCBmb3IgZXhhbXBsZSwgYW4gUkJyaWRnZSBDaGFubmVsIHByb3RvY29s
IG1lc3NhZ2UKICAgaW5jbHVkaW5nIGEgInJlY29yZCByb3V0ZSIgZnVuY3Rpb24gd2hlcmUgbm90
IHJlY29yZGluZyB0cmFuc2l0CiAgIFJCcmlkZ2VzIHRoYXQgZG8gbm90IHN1cHBvcnQgdGhpcyBm
dW5jdGlvbiBpcyBhY2NlcHRhYmxlLgoKCgoKCgoKCgoKRC4gRWFzdGxha2UsIGV0IGFsICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFtQYWdlIDldCgwKSU5URVJO
RVQtRFJBRlQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFRSSUxMOiBIZWFkZXIg
RXh0ZW5zaW9uCgoKNC4gQWRkaXRpb25zIHRvIElTLUlTCgogICBSQnJpZGdlcyB1c2UgSVMtSVMg
TFNQIFBEVXMgdG8gaW5mb3JtIG90aGVyIFJCcmlkZ2VzIHdoaWNoIEV4dGVuZGVkCiAgIEhlYWRl
ciBGbGFncyB0aGV5IHN1cHBvcnQuIFRoZSBJUy1JUyBQRFUocyksIFRMVihzKSwgb3Igc3ViLVRM
VihzKQogICB1c2VkIHRvIGVuY29kZSBhbmQgYWR2ZXJ0aXNlIHRoaXMgaW5mb3JtYXRpb24gYXJl
IHNwZWNpZmllZCBpbiBhCiAgIHNlcGFyYXRlIGRvY3VtZW50IFtSRkM2MzI2YmlzXS4KCgoKNS4g
SUFOQSBDb25zaWRlcmF0aW9ucwoKICAgSUFOQSBpcyByZXF1ZXN0ZWQgdG8gY3JlYXRlIGEgc3Vi
cmVnaXN0cnkgd2l0aGluIHRoZSBUUklMTCBQYXJhbWV0ZXJzCiAgIHJlZ2lzdHJ5OiBUaGUgIlRS
SUxMIEV4dGVuZGVkIEhlYWRlciBGbGFncyIgc3VicmVnaXN0cnksIHRoYXQgaXMKICAgaW5pdGlh
bGx5IHBvcHVsYXRlZCBhcyBzcGVjaWZpZWQgaW4gVGFibGUgMSBpbiBTZWN0aW9uIDMuIFJlZmVy
ZW5jZXMKICAgaW4gdGhhdCB0YWJsZSB0byBzZWN0aW9ucyBvZiB0aGlzIGRvY3VtZW50IGFyZSB0
byBiZSByZXBsYWNlZCBpbiB0aGUKICAgSUFOQSBzdWJyZWdpc3RyeSBieSByZWZlcmVuY2VzIHRv
IHRoaXMgZG9jdW1lbnQgYXMgYW4gUkZDLgoKICAgTmV3IFRSSUxMIEV4dGVuZGVkIEhlYWRlciBG
bGFncyBhcmUgYWxsb2NhdGVkIGJ5IFN0YW5kYXJkcyBBY3Rpb24KICAgW1JGQzUyMjZdIGFzIG1v
ZGlmaWVkIGJ5IFtSRkM0MDIwXS4KCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKRC4g
RWFzdGxha2UsIGV0IGFsICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgW1BhZ2UgMTBdCgwKSU5URVJORVQtRFJBRlQgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIFRSSUxMOiBIZWFkZXIgRXh0ZW5zaW9uCgoKNi4gU2VjdXJpdHkgQ29uc2lkZXJhdGlv
bnMKCiAgIEZvciBnZW5lcmFsIFRSSUxMIHByb3RvY29sIHNlY3VyaXR5IGNvbnNpZGVyYXRpb25z
LCBzZWUgW1JGQzYzMjVdLgoKICAgRm9yIHNlY3VyaXR5IGNvbnNpZGVyYXRpb25zIHJlbGF0ZWQg
dG8gZXh0ZW5kZWQgaGVhZGVyIGZsYWdzLCBzZWUgdGhlCiAgIGRvY3VtZW50IHdoZXJlIHRoZSBm
bGFnIGlzIHNwZWNpZmllZC4KCiAgIEl0IGlzIGltcG9ydGFudCB0aGF0IHRoZSBjcml0aWNhbCBz
dW1tYXJ5IGJpdHMgaW4gdGhlIEV4dGVuZGVkIEhlYWRlcgogICBGbGFncyB3b3JkIGJlIHNldCBw
cm9wZXJseS4gSWYgc2V0IHdoZW4gY3JpdGljYWwgZXh0ZW5zaW9ucyBvZiB0aGUKICAgYXBwcm9w
cmlhdGUgY2F0ZWdvcnkgYXJlIG5vdCBwcmVzZW50LCBmcmFtZXMgbWF5IGJlIHVubmVjZXNzYXJp
bHkKICAgZGlzY2FyZGVkLiBJZiBub3Qgc2V0IHdoZW4gY3JpdGljYWwgZXh0ZW5zaW9ucyBhcmUg
cHJlc2VudCwgZnJhbWVzCiAgIG1heSBiZSBtaXNoYW5kbGVkIG9yIGNvcnJ1cHRlZCBhbmQgaW50
ZW5kZWQgc2VjdXJpdHkgcG9saWNpZXMgbWF5IGJlCiAgIHZpb2xhdGVkLgoKICAgVGhlIFJCcmlk
Z2UgQ2hhbm5lbCBBbGVydCBleHRlbmRlZCBmbGFncyBoYXZlIHRoZSBmb2xsb3dpbmcgc2VjdXJp
dHkKICAgY29uc2lkZXJhdGlvbnMuIEltcGxlbWVudGF0aW9ucyBzaG91bGQga2VlcCBpbiBtaW5k
IHRoYXQgdGhleSBtaWdodAogICBiZSBlcnJvbmVvdXNseSBzZXQgaW4gYSBmcmFtZS4gSWYgZWl0
aGVyIFJCcmlkZ2UgQ2hhbm5lbCBBbGVydCBmbGFnCiAgIGlzIGZvdW5kIHNldCBpbiBhIGZyYW1l
IHRoYXQgaXMgbm90IGFuIFJCcmlkZ2UgQ2hhbm5lbCBtZXNzYWdlCiAgIFtDaGFubmVsXSwgdGhl
IGZsYWcgTUFZIGJlIGNsZWFyZWQgYW5kIHNob3VsZCBoYXZlIG5vIGVmZmVjdCBleGNlcHQsCiAg
IHBvc3NpYmx5LCBkZWxheWluZyBwcm9jZXNzaW5nIG9mIHRoZSBmcmFtZS4gSWYgZWl0aGVyIENo
YW5uZWwgQWxlcnQKICAgZmxhZyBpcyBlcnJvbmVvdXNseSBvbWl0dGVkIGZyb20gYSBmcmFtZSwg
ZGVzaXJlZCBwZXIgaG9wIHByb2Nlc3NpbmcKICAgZm9yIHRoZSBmcmFtZSBtYXkgbm90IG9jY3Vy
LgoKCgo3LiBBY2tub3dsZWRnZW1lbnRzCgogICBUaGUgZm9sbG93aW5nLCBsaXN0ZWQgaW4gYWxw
aGFidGljIG9yZGVyLCBhcmUgdGhhbmtlZCBmb3IgdGhlaXIKICAgdmFsdWFibGUgY29udHJpYnV0
aW9uczogIEJlbiBDYW1wYmVsbCBhbmQgVGhvbWFzIE5hcnRlbi4KCiAgIFRoaXMgZG9jdW1lbnQg
d2FzIHByb2R1Y2VkIHdpdGggcmF3IG5yb2ZmLiBBbGwgbWFjcm9zIHVzZWQgd2VyZQogICBkZWZp
bmVkIGluIHRoZSBzb3VyY2UgZmlsZQoKCgoKCgoKCgoKCgoKCgoKCgoKCkQuIEVhc3RsYWtlLCBl
dCBhbCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFtQYWdlIDEx
XQoMCklOVEVSTkVULURSQUZUICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBUUklM
TDogSGVhZGVyIEV4dGVuc2lvbgoKCjguIE5vcm1hdGl2ZSBSZWZlcmVuY2VzCgogICBbUkZDMjEx
OV0gLSBCcmFkbmVyLCBTLiwgIktleSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5kaWNhdGUK
ICAgICAgICAgUmVxdWlyZW1lbnQgTGV2ZWxzIiwgQkNQIDE0LCBSRkMgMjExOSwgTWFyY2ggMTk5
Ny4KCiAgIFtSRkM0MDIwXSAtIEtvbXBlbGxhLCBLLiBhbmQgQS4gWmluaW4sICJFYXJseSBJQU5B
IEFsbG9jYXRpb24gb2YKICAgICAgICAgU3RhbmRhcmRzIFRyYWNrIENvZGUgUG9pbnRzIiwgQkNQ
IDEwMCwgUkZDIDQwMjAsIEZlYnJ1YXJ5IDIwMDUuCgogICBbUkZDNTIyNl0gLSBOYXJ0ZW4sIFQu
IGFuZCBILiBBbHZlc3RyYW5kLCAiR3VpZGVsaW5lcyBmb3IgV3JpdGluZyBhbgogICAgICAgICBJ
QU5BIENvbnNpZGVyYXRpb25zIFNlY3Rpb24gaW4gUkZDcyIsIEJDUCAyNiwgUkZDIDUyMjYsIE1h
eQogICAgICAgICAyMDA4LgoKICAgW1JGQzYzMjVdIC0gUGVybG1hbiwgUi4sIEQuIEVhc3RsYWtl
LCBELiBEdXR0LCBTLiBHYWksIGFuZCBBLgogICAgICAgICBHaGFud2FuaSwgIlJvdXRpbmcgQnJp
ZGdlcyAoUkJyaWRnZXMpOiBCYXNlIFByb3RvY29sCiAgICAgICAgIFNwZWNpZmljYXRpb24iLCBK
dWx5IDIwMTEuCgogICBbQ2hhbm5lbF0gLSBkcmFmdC1pZXRmLXRyaWxsLXJicmlkZ2UtY2hhbm5l
bCwgd29yayBpbiBwcm9ncmVzcy4KCiAgIFtSRkM2MzI2YmlzXSAtIGRyYWZ0LWVhc3RsYWtlLWlz
aXMtcmZjNjMyNmJpcywgd29yayBpbiBwcm9ncmVzcy4KCgoKOS4gSW5mb3JtYXRpdmUgUmVmZXJl
bmNlcwoKICAgW09wdGlvbnNdIC0gZHJhZnQtaWV0Zi10cmlsbC1yYnJpZGdlLW9wdGlvbnMsIHdv
cmsgaW4gcHJvZ3Jlc3MuCiAgICAgICAgIC0gZHJhZnQtZWFzdGxha2UtdHJpbGwtcmJyaWRnZS1t
b3JlLW9wdGlvbnMsIHdvcmsgaW4gcHJvZ3Jlc3MuCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoK
RC4gRWFzdGxha2UsIGV0IGFsICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgW1BhZ2UgMTJdCgwKSU5URVJORVQtRFJBRlQgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIFRSSUxMOiBIZWFkZXIgRXh0ZW5zaW9uCgoKQ2hhbmdlIEhpc3RvcnkKCiAgIFRo
ZSBzZWN0aW9ucyBiZWxvdyBzdW1tYXJpemUgY2hhbmdlcyBiZXR3ZWVuIHN1Y2Nlc3NpdmUgdmVy
c2lvbnMgb2YKICAgdGhpcyBkcmFmdC4gUkZDIEVkaXRvcjogUGxlYXNlIGRlbGV0ZSB0aGlzIHNl
Y3Rpb24gYmVmb3JlCiAgIHB1YmxpY2F0aW9uLgoKICAgVmVyc2lvbiAwMCBvZiB0aGlzIGRyYWZ0
IGlzIGFuIGV4dHJhY3QgYW5kIHNpbXBsaWZpY2F0aW9uIG9mIGRyYWZ0LQogICBpZXRmLXRyaWxs
LXJicmlkZ2Utb3B0aW9ucy0wNS50eHQgYXMgZGlzY3Vzc2VkIGF0IHRoZSBUUklMTCBXb3JraW5n
CiAgIEdyb3VwIG1lZXRpbmcgYXQgSUVURiA4MSBhbmQgb24gdGhlIFRSSUxMIFdHIG1haWxpbmcg
bGlzdC4KCgoKRnJvbSAtMDAgdG8gLTAxCgogICAxLiBVcGRhdGUgQXV0aG9yIEFkZHJlc3Nlcy4K
CiAgIDIuIEFzc29ydGVkIGVkaXRvcmlhbCBjaGFuZ2VzLgoKCgpGcm9tIC0wMSB0byAtMDIKCiAg
IDEuIEFkZGl0aW9uIG9mIHRoZSBDcml0aWNhbCBSQnJpZGdlIENoYW5uZWwgQWxlcnQgRmxhZy4K
CiAgIDIuIEFzc29ydGVkIGVkaXRvcmlhbCBhbmQgYXV0aG9yIGNoYW5nZXMuCgoKCkZyb20gLTAy
IHRvIC0wMwoKICAgMS4gUmVwbGFjZW1lbnQgb2YgU2VjdGlvbiAyLjQgdG8gZWxpbWluYXRlIGRl
dGFpbGVkIGNvbnN0cmFpbnRzIG9uCiAgICAgIHRoZSBwcm9jZXNzaW5nIG9mIGNvbmZsaWN0aW5n
IGV4dGVuc2lvbnMgYW5kIHRvIHdhcm4gYWdhaW5zdCB0aGUKICAgICAgZnV0dXJlIHNwZWNpZmlj
YXRpb24gb2YgY29uZmxpY3Rpbmcgb3B0aW9ucy4KCiAgIDIuIE1pbm9yIGVkaXRvcmlhbCBjaGFu
Z2VzLgoKCgpGcm9tIC0wMyB0byAtMDQKCiAgIEVkaXRvcmlhbCBjaGFuZ2VzIGluY2x1ZGluZyB0
aGUgZGVsZXRpb24gb2YgU2VjdGlvbiAyLjMuMiB0aGF0IHdhcwogICBjb21wbGV0ZWx5IHJlZHVu
ZGFudCB3aXRoIGVhcmxpZXIgcGFydHMgb2YgU2VjdGlvbiAyLjMuCgoKCkZyb20gLTA0IHRvIC0w
NQoKICAgMS4gQWRkICJVcGRhdGVzOiA2MzI1IiB0byB0aGUgZmlyc3QgcGFnZSBoZWFkZXIgYXMg
dGhpcyBkb2N1bWVudAogICBwcm92aWRlcyBtb3JlIGRldGFpbHMgb24gdGhlIHRoZSBUUklMTCBI
ZWFkZXIgb3B0aW9ucyBhcmVhLgoKCgpELiBFYXN0bGFrZSwgZXQgYWwgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBbUGFnZSAxM10KDApJTlRFUk5FVC1EUkFGVCAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgVFJJTEw6IEhlYWRlciBFeHRlbnNpb24K
CgoyLiBFeHBhbmQgZmlyc3QgdXNlIG9mIHNvbWUgYWNyb255bXMgYW5kIG90aGVyIGVkaXRvcmlh
bCBjaGFuZ2VzLgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoK
CgoKCgpELiBFYXN0bGFrZSwgZXQgYWwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBbUGFnZSAxNF0KDApJTlRFUk5FVC1EUkFGVCAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgVFJJTEw6IEhlYWRlciBFeHRlbnNpb24KCgpBdXRob3JzJyBBZGRyZXNz
ZXMKCkRvbmFsZCBFYXN0bGFrZQpIdWF3ZWkgUiZEIFVTQQoxNTUgQmVhdmVyIFN0cmVldApNaWxm
b3JkLCBNQSAwMTc1NyBVU0EKClBob25lOiArMS01MDgtMzMzLTIyNzAKZW1haWw6IGQzZTNlM0Bn
bWFpbC5jb20KCgpBbm9vcCBHaGFud2FuaQpEZWxsCjM1MCBIb2xnZXIgV2F5ClNhbiBKb3NlLCBD
QSA5NTEzNCBVU0EKClBob25lOiArMS00MDgtNTcxLTM1MDAKRW1haWw6IGFub29wQGFsdW1uaS5k
dWtlLmVkdQoKClZpc2h3YXMgTWFucmFsCkhQIE5ldHdvcmtpbmcKMTkxMTEgUHJ1bmVyaWRnZSBB
dmVudWUKQ3VwZXJ0aW5vLCBDQSA5NTAxNCBVU0EKClBob25lOiArMS00MDgtNDc3LTAwMDAKRU1h
aWw6IHZpc2h3YXMubWFucmFsQGhwLmNvbQoKCllpemhvdSBMaQpIdWF3ZWkgVGVjaG5vbG9naWVz
CjEwMSBTb2Z0d2FyZSBBdmVudWUsCk5hbmppbmcgMjEwMDEyLCBDaGluYQoKUGhvbmU6ICs4Ni0y
NS01NjYyMjMxMApFbWFpbDogbGl5aXpob3VAaHVhd2VpLmNvbQoKCkNhaXRsaW4gQmVzdGxlcgpR
dWFudHVtCjE2NTAgVGVjaG5vbG9neSBEcml2ZSAsIFN1aXRlIDcwMApTYW4gSm9zZSwgQ0EgOTUx
MTAgVVNBCgpQaG9uZTogKzEtNDA4LTk0NC00MDAwCmVtYWlsOiBjYWl0QGFzb21pLmNvbQoKCgoK
CgoKRC4gRWFzdGxha2UsIGV0IGFsICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgW1BhZ2UgMTVdCgwKSU5URVJORVQtRFJBRlQgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIFRSSUxMOiBIZWFkZXIgRXh0ZW5zaW9uCgoKQ29weXJpZ2h0IGFuZCBJUFIg
UHJvdmlzaW9ucwoKQ29weXJpZ2h0IChjKSAyMDEyIElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25z
IGlkZW50aWZpZWQgYXMgdGhlIGRvY3VtZW50CmF1dGhvcnMuIEFsbCByaWdodHMgcmVzZXJ2ZWQu
CgpUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QgdG8gQkNQIDc4IGFuZCB0aGUgSUVURiBUcnVzdCdz
IExlZ2FsIFByb3Zpc2lvbnMKUmVsYXRpbmcgdG8gSUVURiBEb2N1bWVudHMgKGh0dHA6Ly90cnVz
dGVlLmlldGYub3JnL2xpY2Vuc2UtaW5mbykgaW4KZWZmZWN0IG9uIHRoZSBkYXRlIG9mIHB1Ymxp
Y2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuIFBsZWFzZSByZXZpZXcgdGhlc2UKZG9jdW1lbnRzIGNh
cmVmdWxseSwgYXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQgcmVzdHJpY3Rpb25zIHdp
dGgKcmVzcGVjdCB0byB0aGlzIGRvY3VtZW50LiBDb2RlIENvbXBvbmVudHMgZXh0cmFjdGVkIGZy
b20gdGhpcyBkb2N1bWVudAptdXN0IGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZSB0ZXh0
IGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDQuZSBvZgp0aGUgVHJ1c3QgTGVnYWwgUHJvdmlzaW9u
cyBhbmQgYXJlIHByb3ZpZGVkIHdpdGhvdXQgd2FycmFudHkgYXMKZGVzY3JpYmVkIGluIHRoZSBT
aW1wbGlmaWVkIEJTRCBMaWNlbnNlLiAgVGhlIGRlZmluaXRpdmUgdmVyc2lvbiBvZiBhbgpJRVRG
IERvY3VtZW50IGlzIHRoYXQgcHVibGlzaGVkIGJ5LCBvciB1bmRlciB0aGUgYXVzcGljZXMgb2Ys
IHRoZSBJRVRGLgpWZXJzaW9ucyBvZiBJRVRGIERvY3VtZW50cyB0aGF0IGFyZSBwdWJsaXNoZWQg
YnkgdGhpcmQgcGFydGllcywKaW5jbHVkaW5nIHRob3NlIHRoYXQgYXJlIHRyYW5zbGF0ZWQgaW50
byBvdGhlciBsYW5ndWFnZXMsIHNob3VsZCBub3QgYmUKY29uc2lkZXJlZCB0byBiZSBkZWZpbml0
aXZlIHZlcnNpb25zIG9mIElFVEYgRG9jdW1lbnRzLiBUaGUgZGVmaW5pdGl2ZQp2ZXJzaW9uIG9m
IHRoZXNlIExlZ2FsIFByb3Zpc2lvbnMgaXMgdGhhdCBwdWJsaXNoZWQgYnksIG9yIHVuZGVyIHRo
ZQphdXNwaWNlcyBvZiwgdGhlIElFVEYuIFZlcnNpb25zIG9mIHRoZXNlIExlZ2FsIFByb3Zpc2lv
bnMgdGhhdCBhcmUKcHVibGlzaGVkIGJ5IHRoaXJkIHBhcnRpZXMsIGluY2x1ZGluZyB0aG9zZSB0
aGF0IGFyZSB0cmFuc2xhdGVkIGludG8Kb3RoZXIgbGFuZ3VhZ2VzLCBzaG91bGQgbm90IGJlIGNv
bnNpZGVyZWQgdG8gYmUgZGVmaW5pdGl2ZSB2ZXJzaW9ucyBvZgp0aGVzZSBMZWdhbCBQcm92aXNp
b25zLiAgRm9yIHRoZSBhdm9pZGFuY2Ugb2YgZG91YnQsIGVhY2ggQ29udHJpYnV0b3IgdG8KdGhl
IElFVEYgU3RhbmRhcmRzIFByb2Nlc3MgbGljZW5zZXMgZWFjaCBDb250cmlidXRpb24gdGhhdCBo
ZSBvciBzaGUKbWFrZXMgYXMgcGFydCBvZiB0aGUgSUVURiBTdGFuZGFyZHMgUHJvY2VzcyB0byB0
aGUgSUVURiBUcnVzdCBwdXJzdWFudAp0byB0aGUgcHJvdmlzaW9ucyBvZiBSRkMgNTM3OC4gTm8g
bGFuZ3VhZ2UgdG8gdGhlIGNvbnRyYXJ5LCBvciB0ZXJtcywKY29uZGl0aW9ucyBvciByaWdodHMg
dGhhdCBkaWZmZXIgZnJvbSBvciBhcmUgaW5jb25zaXN0ZW50IHdpdGggdGhlCnJpZ2h0cyBhbmQg
bGljZW5zZXMgZ3JhbnRlZCB1bmRlciBSRkMgNTM3OCwgc2hhbGwgaGF2ZSBhbnkgZWZmZWN0IGFu
ZApzaGFsbCBiZSBudWxsIGFuZCB2b2lkLCB3aGV0aGVyIHB1Ymxpc2hlZCBvciBwb3N0ZWQgYnkg
c3VjaCBDb250cmlidXRvciwKb3IgaW5jbHVkZWQgd2l0aCBvciBpbiBzdWNoIENvbnRyaWJ1dGlv
bi4KCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgpELiBFYXN0bGFrZSwgZXQgYWwgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBbUGFnZSAxNl0KDAo=
--14dae9341241881f6e04c195b0c1
Content-Type: text/html; charset=UTF-16LE; name="wdiffRE-04vInternal31.html"
Content-Disposition: attachment; filename="wdiffRE-04vInternal31.html"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_h30gaw0s1

//4KADwAaAB0AG0AbAA+ADwAaABlAGEAZAA+ADwAdABpAHQAbABlAD4AdwBkAGkAZgBmACAAZABy
AGEAZgB0AC0AaQBlAHQAZgAtAHQAcgBpAGwAbAAtAHIAYgByAGkAZABnAGUALQBlAHgAdABlAG4A
cwBpAG8AbgAtADAANAAuAHQAeAB0ACAAcgBlADMAMQBmAGYAdABvAGMALgB0AHgAdAA8AC8AdABp
AHQAbABlAD4APAAvAGgAZQBhAGQAPgA8AGIAbwBkAHkAPgAKADwAcAByAGUAPgAKAAoAVABSAEkA
TABMACAAVwBvAHIAawBpAG4AZwAgAEcAcgBvAHUAcAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAARABvAG4A
YQBsAGQAIABFAGEAcwB0AGwAYQBrAGUACgBJAE4AVABFAFIATgBFAFQALQBEAFIAQQBGAFQAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABIAHUAYQB3AGUAaQAK
AEkAbgB0AGUAbgBkAGUAZAAgAHMAdABhAHQAdQBzADoAIABQAHIAbwBwAG8AcwBlAGQAIABTAHQA
YQBuAGQAYQByAGQAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAQQBuAG8AbwBwACAARwBoAGEAbgB3AGEAbgBpAAoAPABzAHQAcgBvAG4AZwA+ADwAZgBvAG4A
dAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcAIABzAGkAegBlAD0AIgArADEAIgA+AFUAcABk
AGEAdABlAHMAOgAgADYAMwAyADUAPAAvAGYAbwBuAHQAPgA8AC8AcwB0AHIAbwBuAGcAPgAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAEQAZQBsAGwA
CgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgAFYAaQBzAGgAdwBhAHMAIABNAGEAbgByAGEAbAAKACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAASABQAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAWQBpAHoAaABvAHUAIABMAGkACgAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IABIAHUAYQB3AGUAaQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgAEMAYQBpAHQAbABpAG4AIABCAGUAcwB0AGwAZQByAAoAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgAFEAdQBhAG4AdAB1AG0ACgBFAHgAcABpAHIAZQBzADoAIAA8AHMAdAByAGkAawBlAD4A
PABmAG8AbgB0ACAAYwBvAGwAbwByAD0AJwByAGUAZAAnACAAcwBpAHoAZQA9ACIAKwAxACIAPgBO
AG8AdgBlAG0AYgBlAHIAIAAxACwAIAAyADAAMQAyACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAE0AYQB5ADwALwBm
AG8AbgB0AD4APAAvAHMAdAByAGkAawBlAD4AIAA8AHMAdAByAG8AbgBnAD4APABmAG8AbgB0ACAA
YwBvAGwAbwByAD0AJwBnAHIAZQBlAG4AJwAgAHMAaQB6AGUAPQAiACsAMQAiAD4ARABlAGMAZQBt
AGIAZQByADwALwBmAG8AbgB0AD4APAAvAHMAdAByAG8AbgBnAD4AIAAyACwAIAAyADAAMQAyACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAA8AHMAdAByAG8AbgBnAD4APABmAG8AbgB0ACAAYwBvAGwAbwByAD0AJwBnAHIA
ZQBlAG4AJwAgAHMAaQB6AGUAPQAiACsAMQAiAD4ASgB1AG4AZQAgADMALAAgADIAMAAxADIAPAAv
AGYAbwBuAHQAPgA8AC8AcwB0AHIAbwBuAGcAPgAKAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAVABSAEkATABMADoAIABIAGUAYQBkAGUAcgAgAEUAeAB0
AGUAbgBzAGkAbwBuAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgADwAcwB0AHIAaQBrAGUA
PgA8AGYAbwBuAHQAIABjAG8AbABvAHIAPQAnAHIAZQBkACcAIABzAGkAegBlAD0AIgArADEAIgA+
ACYAbAB0ADsAZAByAGEAZgB0AC0AaQBlAHQAZgAtAHQAcgBpAGwAbAAtAHIAYgByAGkAZABnAGUA
LQBlAHgAdABlAG4AcwBpAG8AbgAtADAANAAuAHQAeAB0ACYAZwB0ADsAPAAvAGYAbwBuAHQAPgA8
AC8AcwB0AHIAaQBrAGUAPgAKACAAIAAgACAAIAAgACAAIAAgACAAPABzAHQAcgBvAG4AZwA+ADwA
ZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcAIABzAGkAegBlAD0AIgArADEAIgA+
ACYAbAB0ADsAZAByAGEAZgB0AC0AaQBlAHQAZgAtAHQAcgBpAGwAbAAtAHIAYgByAGkAZABnAGUA
LQBlAHgAdABlAG4AcwBpAG8AbgAtADAANQBjAGEAbgBkAGkAZABhAHQAZQAuAHQAeAB0ACYAZwB0
ADsAPAAvAGYAbwBuAHQAPgA8AC8AcwB0AHIAbwBuAGcAPgAKAAoAQQBiAHMAdAByAGEAYwB0AAoA
CgAgACAAIABUAGgAZQAgAEkARQBUAEYAIABUAFIASQBMAEwAIAAoAFQAcgBhAG4AcwBwAGEAcgBl
AG4AdAAgAEkAbgB0AGUAcgBjAG8AbgBuAGUAYwB0AGkAbwBuACAAbwBmACAATABvAHQAcwAgAG8A
ZgAgAEwAaQBuAGsAcwApACAAYgBhAHMAZQAKACAAIAAgAHAAcgBvAHQAbwBjAG8AbAAgAHMAcABl
AGMAaQBmAGkAZQBzACAAbQBpAG4AaQBtAGEAbAAgAGgAbwBvAGsAcwAgAHQAbwAgAHMAYQBmAGUA
bAB5ACAAcwB1AHAAcABvAHIAdAAgAFQAUgBJAEwATAAgAEgAZQBhAGQAZQByAAoAIAAgACAAZQB4
AHQAZQBuAHMAaQBvAG4AcwAuACAAVABoAGkAcwAgAGQAbwBjAHUAbQBlAG4AdAAgAHMAcABlAGMA
aQBmAGkAZQBzACAAYQBuACAAaQBuAGkAdABpAGEAbAAgAGUAeAB0AGUAbgBzAGkAbwBuACAAcABy
AG8AdgBpAGQAaQBuAGcACgAgACAAIABhAGQAZABpAHQAaQBvAG4AYQBsACAAZgBsAGEAZwAgAGIA
aQB0AHMAIABhAG4AZAAgAHMAcABlAGMAaQBmAGkAZQBzACAAdAB3AG8AIABvAGYAIAB0AGgAbwBz
AGUAIABiAGkAdABzAC4AIAA8AHMAdAByAG8AbgBnAD4APABmAG8AbgB0ACAAYwBvAGwAbwByAD0A
JwBnAHIAZQBlAG4AJwAgAHMAaQB6AGUAPQAiACsAMQAiAD4ASQB0ACAAdQBwAGQAYQB0AGUAcwAg
AFIARgBDAAoAIAAgACAANgAzADIANQAuADwALwBmAG8AbgB0AD4APAAvAHMAdAByAG8AbgBnAD4A
CgAKAFMAdABhAHQAdQBzACAAbwBmACAAVABoAGkAcwAgAE0AZQBtAG8ACgAKACAAIAAgAFQAaABp
AHMAIABJAG4AdABlAHIAbgBlAHQALQBEAHIAYQBmAHQAIABpAHMAIABzAHUAYgBtAGkAdAB0AGUA
ZAAgAHQAbwAgAEkARQBUAEYAIABpAG4AIABmAHUAbABsACAAYwBvAG4AZgBvAHIAbQBhAG4AYwBl
ACAAdwBpAHQAaAAgAHQAaABlAAoAIAAgACAAcAByAG8AdgBpAHMAaQBvAG4AcwAgAG8AZgAgAEIA
QwBQACAANwA4ACAAYQBuAGQAIABCAEMAUAAgADcAOQAuAAoACgAgACAAIABEAGkAcwB0AHIAaQBi
AHUAdABpAG8AbgAgAG8AZgAgAHQAaABpAHMAIABkAG8AYwB1AG0AZQBuAHQAIABpAHMAIAB1AG4A
bABpAG0AaQB0AGUAZAAuACAAQwBvAG0AbQBlAG4AdABzACAAcwBoAG8AdQBsAGQAIABiAGUAIABz
AGUAbgB0AAoAIAAgACAAdABvACAAdABoAGUAIABUAFIASQBMAEwAIAB3AG8AcgBrAGkAbgBnACAA
ZwByAG8AdQBwACAAbQBhAGkAbABpAG4AZwAgAGwAaQBzAHQAIAAmAGwAdAA7AHIAYgByAGkAZABn
AGUAQABwAG8AcwB0AGUAbAAuAG8AcgBnACYAZwB0ADsALgAKAAoAIAAgACAASQBuAHQAZQByAG4A
ZQB0AC0ARAByAGEAZgB0AHMAIABhAHIAZQAgAHcAbwByAGsAaQBuAGcAIABkAG8AYwB1AG0AZQBu
AHQAcwAgAG8AZgAgAHQAaABlACAASQBuAHQAZQByAG4AZQB0ACAARQBuAGcAaQBuAGUAZQByAGkA
bgBnAAoAIAAgACAAVABhAHMAawAgAEYAbwByAGMAZQAgACgASQBFAFQARgApACwAIABpAHQAcwAg
AGEAcgBlAGEAcwAsACAAYQBuAGQAIABpAHQAcwAgAHcAbwByAGsAaQBuAGcAIABnAHIAbwB1AHAA
cwAuACAAIABOAG8AdABlACAAdABoAGEAdAAKACAAIAAgAG8AdABoAGUAcgAgAGcAcgBvAHUAcABz
ACAAbQBhAHkAIABhAGwAcwBvACAAZABpAHMAdAByAGkAYgB1AHQAZQAgAHcAbwByAGsAaQBuAGcA
IABkAG8AYwB1AG0AZQBuAHQAcwAgAGEAcwAgAEkAbgB0AGUAcgBuAGUAdAAtAAoAIAAgACAARABy
AGEAZgB0AHMALgAKAAoAIAAgACAASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0AHMAIABhAHIA
ZQAgAGQAcgBhAGYAdAAgAGQAbwBjAHUAbQBlAG4AdABzACAAdgBhAGwAaQBkACAAZgBvAHIAIABh
ACAAbQBhAHgAaQBtAHUAbQAgAG8AZgAgAHMAaQB4ACAAbQBvAG4AdABoAHMACgAgACAAIABhAG4A
ZAAgAG0AYQB5ACAAYgBlACAAdQBwAGQAYQB0AGUAZAAsACAAcgBlAHAAbABhAGMAZQBkACwAIABv
AHIAIABvAGIAcwBvAGwAZQB0AGUAZAAgAGIAeQAgAG8AdABoAGUAcgAgAGQAbwBjAHUAbQBlAG4A
dABzACAAYQB0ACAAYQBuAHkACgAgACAAIAB0AGkAbQBlAC4AIAAgAEkAdAAgAGkAcwAgAGkAbgBh
AHAAcAByAG8AcAByAGkAYQB0AGUAIAB0AG8AIAB1AHMAZQAgAEkAbgB0AGUAcgBuAGUAdAAtAEQA
cgBhAGYAdABzACAAYQBzACAAcgBlAGYAZQByAGUAbgBjAGUACgAgACAAIABtAGEAdABlAHIAaQBh
AGwAIABvAHIAIAB0AG8AIABjAGkAdABlACAAdABoAGUAbQAgAG8AdABoAGUAcgAgAHQAaABhAG4A
IABhAHMAIAAiAHcAbwByAGsAIABpAG4AIABwAHIAbwBnAHIAZQBzAHMALgAiAAoACgAgACAAIABU
AGgAZQAgAGwAaQBzAHQAIABvAGYAIABjAHUAcgByAGUAbgB0ACAASQBuAHQAZQByAG4AZQB0AC0A
RAByAGEAZgB0AHMAIABjAGEAbgAgAGIAZQAgAGEAYwBjAGUAcwBzAGUAZAAgAGEAdAAKACAAIAAg
ADwAcwB0AHIAaQBrAGUAPgA8AGYAbwBuAHQAIABjAG8AbABvAHIAPQAnAHIAZQBkACcAIABzAGkA
egBlAD0AIgArADEAIgA+AGgAdAB0AHAAOgAvAC8AdwB3AHcALgBpAGUAdABmAC4AbwByAGcALwAx
AGkAZAAtAGEAYgBzAHQAcgBhAGMAdABzAC4AaAB0AG0AbAA8AC8AZgBvAG4AdAA+ADwALwBzAHQA
cgBpAGsAZQA+AAoAIAAgACAAPABzAHQAcgBvAG4AZwA+ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9
ACcAZwByAGUAZQBuACcAIABzAGkAegBlAD0AIgArADEAIgA+AGgAdAB0AHAAOgAvAC8AdwB3AHcA
LgBpAGUAdABmAC4AbwByAGcALwAxAGkAZAAtAGEAYgBzAHQAcgBhAGMAdABzAC4AaAB0AG0AbAAu
ADwALwBmAG8AbgB0AD4APAAvAHMAdAByAG8AbgBnAD4AIABUAGgAZQAgAGwAaQBzAHQAIABvAGYA
IABJAG4AdABlAHIAbgBlAHQALQBEAHIAYQBmAHQACgAgACAAIABTAGgAYQBkAG8AdwAgAEQAaQBy
AGUAYwB0AG8AcgBpAGUAcwAgAGMAYQBuACAAYgBlACAAYQBjAGMAZQBzAHMAZQBkACAAYQB0AAoA
IAAgACAAPABzAHQAcgBpAGsAZQA+ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAcgBlAGQAJwAg
AHMAaQB6AGUAPQAiACsAMQAiAD4AaAB0AHQAcAA6AC8ALwB3AHcAdwAuAGkAZQB0AGYALgBvAHIA
ZwAvAHMAaABhAGQAbwB3AC4AaAB0AG0AbAA8AC8AZgBvAG4AdAA+ADwALwBzAHQAcgBpAGsAZQA+
AAoAIAAgACAAPABzAHQAcgBvAG4AZwA+ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAZwByAGUA
ZQBuACcAIABzAGkAegBlAD0AIgArADEAIgA+AGgAdAB0AHAAOgAvAC8AdwB3AHcALgBpAGUAdABm
AC4AbwByAGcALwBzAGgAYQBkAG8AdwAuAGgAdABtAGwALgA8AC8AZgBvAG4AdAA+ADwALwBzAHQA
cgBvAG4AZwA+AAoACgBJAE4AVABFAFIATgBFAFQALQBEAFIAQQBGAFQAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAFQA
UgBJAEwATAA6ACAASABlAGEAZABlAHIAIABFAHgAdABlAG4AcwBpAG8AbgAKAAoAVABhAGIAbABl
ACAAbwBmACAAQwBvAG4AdABlAG4AdABzAAoACgAgACAAIAAgACAAIAAxAC4AIABJAG4AdAByAG8A
ZAB1AGMAdABpAG8AbgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4AMwAKACAAIAAgACAA
IAAgADEALgAxACAAQwBvAG4AdgBlAG4AdABpAG8AbgBzACAAdQBzAGUAZAAgAGkAbgAgAHQAaABp
AHMAIABkAG8AYwB1AG0AZQBuAHQALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAzAAoACgAgACAAIAAgACAAIAAyAC4AIABUAFIASQBMAEwAIABIAGUAYQBkAGUAcgAg
AEUAeAB0AGUAbgBzAGkAbwBuAHMALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ANAAKACAAIAAgACAAIAAgADIALgAxACAAUgBC
AHIAaQBkAGcAZQAgAEUAeAB0AGUAbgBkAGUAZAAgAEYAbABhAGcAIABIAGEAbgBkAGwAaQBuAGcA
IABSAGUAcQB1AGkAcgBlAG0AZQBuAHQAcwAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgA1AAoAIAAg
ACAAIAAgACAAMgAuADIAIABOAG8AIABDAHIAaQB0AGkAYwBhAGwAIABTAHUAcgBwAHIAaQBzAGUA
cwAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuADUACgAgACAAIAAgACAAIAAyAC4AMwAgAEUAeAB0AGUAbgBkAGUAZAAgAEgA
ZQBhAGQAZQByACAARgBsAGEAZwBzAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ANgAKACAAIAAgACAAIAAgADIALgAzAC4A
MQAgAEMAcgBpAHQAaQBjAGEAbAAgAFMAdQBtAG0AYQByAHkAIABCAGkAdABzAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgA3AAoA
IAAgACAAIAAgACAAMgAuADQAIABDAG8AbgBmAGwAaQBjAHQAIABvAGYAIABFAHgAdABlAG4AcwBp
AG8AbgBzAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuADgACgAKACAAIAAgACAAIAAgADMALgAgAFMAcABlAGMAaQBmAGkAYwAg
AEUAeAB0AGUAbgBkAGUAZAAgAEgAZQBhAGQAZQByACAARgBsAGEAZwBzAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgA5AAoAIAAgACAAIAAgACAAMwAu
ADEAIABUAGgAZQAgAFIAQgByAGkAZABnAGUAIABDAGgAYQBuAG4AZQBsACAAQQBsAGUAcgB0ACAA
RQB4AHQAZQBuAGQAZQBkACAARgBsAGEAZwBzAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
ADkACgAKACAAIAAgACAAIAAgADQALgAgAEEAZABkAGkAdABpAG8AbgBzACAAdABvACAASQBTAC0A
SQBTAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4AMQAwAAoACgAgACAAIAAgACAAIAA1AC4AIABJAEEATgBBACAA
QwBvAG4AcwBpAGQAZQByAGEAdABpAG8AbgBzAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuADEAMAAKACAAIAAgACAA
IAAgADYALgAgAFMAZQBjAHUAcgBpAHQAeQAgAEMAbwBuAHMAaQBkAGUAcgBhAHQAaQBvAG4AcwAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4AMQAxAAoAIAAgACAAIAAgACAANwAuACAAQQBjAGsAbgBvAHcAbABlAGQAZwBlAG0AZQBu
AHQAcwAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAxADEACgAgACAAIAAgACAAIAA4AC4AIABOAG8AcgBt
AGEAdABpAHYAZQAgAFIAZQBmAGUAcgBlAG4AYwBlAHMALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4A
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuADEAMgAKACAAIAAg
ACAAIAAgADkALgAgAEkAbgBmAG8AcgBtAGEAdABpAHYAZQAgAFIAZQBmAGUAcgBlAG4AYwBlAHMA
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4AMQAyAAoACgAgACAAIAAgACAAIABDAGgAYQBuAGcAZQAgAEgAaQBzAHQAbwByAHkA
LgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu
AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuADEAMwAKAAoASQBOAFQARQBSAE4ARQBUAC0A
RABSAEEARgBUACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIABUAFIASQBMAEwAOgAgAEgAZQBhAGQAZQByACAARQB4AHQA
ZQBuAHMAaQBvAG4ACgAKADEALgAgAEkAbgB0AHIAbwBkAHUAYwB0AGkAbwBuAAoACgAgACAAIABU
AGgAZQAgAGIAYQBzAGUAIABJAEUAVABGACAAVABSAEkATABMACAAPABzAHQAcgBvAG4AZwA+ADwA
ZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcAIABzAGkAegBlAD0AIgArADEAIgA+
ACgAVAByAGEAbgBzAHAAYQByAGUAbgB0ACAASQBuAHQAZQByAGMAbwBuAG4AZQBjAHQAaQBvAG4A
IABvAGYAIABMAG8AdABzACAAbwBmACAATABpAG4AawBzACkAPAAvAGYAbwBuAHQAPgA8AC8AcwB0
AHIAbwBuAGcAPgAKACAAIAAgAHAAcgBvAHQAbwBjAG8AbAAgAFsAUgBGAEMANgAzADIANQBdACAA
WwBSAEYAQwA2ADMAMgA2AGIAaQBzAF0AIABwAHIAbwB2AGkAZABlAHMAIABhACAAVABSAEkATABM
ACAASABlAGEAZABlAHIAIABlAHgAdABlAG4AcwBpAG8AbgAKACAAIAAgAGYAZQBhAHQAdQByAGUA
IABhAG4AZAAgAGQAZQBzAGMAcgBpAGIAZQBzACAAbQBpAG4AaQBtAGEAbAAgAGgAbwBvAGsAcwAg
AHQAbwAgAHMAYQBmAGUAbAB5ACAAcwB1AHAAcABvAHIAdAAgAGgAZQBhAGQAZQByAAoAIAAgACAA
ZQB4AHQAZQBuAHMAaQBvAG4ALgAgACgAVABoAGkAcwAgAGYAZQBhAHQAdQByAGUAIABpAHMAIABj
AGEAbABsAGUAZAAgACIAbwBwAHQAaQBvAG4AcwAiACAAaQBuACAAUwBlAGMAdABpAG8AbgAgADMA
LgA4ACAAbwBmAAoAIAAgACAAWwBSAEYAQwA2ADMAMgA1AF0ALgApACAAQgB1AHQALAAgAGUAeABj
AGUAcAB0ACAAZgBvAHIAIAB0AGgAZQAgAGYAaQByAHMAdAAgAHQAdwBvACAAYgBpAHQAcwAsACAA
dABoAGUAIABiAGEAcwBlACAAVABSAEkATABMAAoAIAAgACAAcAByAG8AdABvAGMAbwBsACAAZABv
AGUAcwAgAG4AbwB0ACAAcwBwAGUAYwBpAGYAeQAgAHQAaABlACAAcwB0AHIAdQBjAHQAdQByAGUA
IABvAGYAIABlAHgAdABlAG4AcwBpAG8AbgBzACAAdABvACAAdABoAGUAIABUAFIASQBMAEwACgAg
ACAAIABIAGUAYQBkAGUAcgAgAG4AbwByACAAdABoAGUAIABkAGUAdABhAGkAbABzACAAbwBmACAA
YQBuAHkAIABwAGEAcgB0AGkAYwB1AGwAYQByACAAZQB4AHQAZQBuAHMAaQBvAG4ALgAgAFQAaABp
AHMAIABkAG8AYwB1AG0AZQBuAHQACgAgACAAIABzAHAAZQBjAGkAZgBpAGUAcwAgAGEAbgAgAGkA
bgBpAHQAaQBhAGwAIABlAHgAdABlAG4AcwBpAG8AbgAgAHAAcgBvAHYAaQBkAGkAbgBnACAAYQBk
AGQAaQB0AGkAbwBuAGEAbAAgAGYAbABhAGcAIABiAGkAdABzACAAYQBuAGQACgAgACAAIABzAHAA
ZQBjAGkAZgBpAGUAcwAgAG8AbgBlACAAbwBmACAAdABoAG8AcwBlACAAYgBpAHQAcwAuACAAQQBk
AGQAaQB0AGkAbwBuAGEAbAAgAGUAeAB0AGUAbgBzAGkAbwBuAHMALAAgAGkAbgBjAGwAdQBkAGkA
bgBnACAAVABMAFYACgAgACAAIAAoAFQAeQBwAGUALAAgAEwAZQBuAGcAdABoACwAIABWAGEAbAB1
AGUAKQAgAGUAbgBjAG8AZABlAGQAIABvAHAAdABpAG8AbgBzACwAIABtAGEAeQAgAGIAZQAgAHMA
cABlAGMAaQBmAGkAZQBkACAAaQBuACAAbABhAHQAZQByAAoAIAAgACAAZABvAGMAdQBtAGUAbgB0
AHMALgAKAAoAIAAgACAAUwBlAGMAdABpAG8AbgAgADIAIABiAGUAbABvAHcAIABkAGUAcwBjAHIA
aQBiAGUAcwAgAHMAbwBtAGUAIABnAGUAbgBlAHIAYQBsACAAcAByAGkAbgBjAGkAcABsAGUAcwAg
AG8AZgAgAFQAUgBJAEwATAAgAGgAZQBhAGQAZQByAAoAIAAgACAAZQB4AHQAZQBuAHMAaQBvAG4A
cwAgAGEAbgBkACAAYQBuACAAaQBuAGkAdABpAGEAbAAgAGUAeAB0AGUAbgBzAGkAbwBuAC4AIAAg
AFMAZQBjAHQAaQBvAG4AIAAzACAAcwBwAGUAYwBpAGYAaQBlAHMAIABwAGEAaQByACAAbwBmAAoA
IAAgACAAZgBsAGEAZwBzACAAaQBuACAAdABoAGkAcwAgAGkAbgBpAHQAaQBhAGwAIABlAHgAdABl
AG4AcwBpAG8AbgAuAAoACgAxAC4AMQAgAEMAbwBuAHYAZQBuAHQAaQBvAG4AcwAgAHUAcwBlAGQA
IABpAG4AIAB0AGgAaQBzACAAZABvAGMAdQBtAGUAbgB0AAoACgAgACAAIABUAGgAZQAgAHQAZQBy
AG0AaQBuAG8AbABvAGcAeQAgAGEAbgBkACAAYQBjAHIAbwBuAHkAbQBzACAAZABlAGYAaQBuAGUA
ZAAgAGkAbgAgAFsAUgBGAEMANgAzADIANQBdACAAYQByAGUAIAB1AHMAZQBkACAAaABlAHIAZQBp
AG4ACgAgACAAIAB3AGkAdABoACAAdABoAGUAIABzAGEAbQBlACAAbQBlAGEAbgBpAG4AZwAuACAA
PABzAHQAcgBvAG4AZwA+ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcAIABz
AGkAegBlAD0AIgArADEAIgA+AEQAZQB2AGkAYwBlAHMAIABpAG0AcABsAGUAbQBlAG4AdABpAG4A
ZwAgAHQAaABlACAAVABSAEkATABMACAAcAByAG8AdABvAGMAbwBsACAAYQByAGUACgAgACAAIABy
AGUAZgBlAHIAcgBlAGQAIAB0AG8AIABhAHMAIABSAEIAcgBpAGQAZwBlAHMAIAAoAFIAbwB1AHQA
aQBuAGcAIABCAHIAaQBkAGcAZQBzACkAIABvAHIAIABUAFIASQBMAEwAIABTAHcAaQB0AGMAaABl
AHMALgA8AC8AZgBvAG4AdAA+ADwALwBzAHQAcgBvAG4AZwA+AAoACgAgACAAIABUAGgAZQAgAGsA
ZQB5ACAAdwBvAHIAZABzACAAIgBNAFUAUwBUACIALAAgACIATQBVAFMAVAAgAE4ATwBUACIALAAg
ACIAUgBFAFEAVQBJAFIARQBEACIALAAgACIAUwBIAEEATABMACIALAAgACIAUwBIAEEATABMACAA
TgBPAFQAIgAsAAoAIAAgACAAIgBTAEgATwBVAEwARAAiACwAIAAiAFMASABPAFUATABEACAATgBP
AFQAIgAsACAAIgBSAEUAQwBPAE0ATQBFAE4ARABFAEQAIgAsACAAIgBNAEEAWQAiACwAIABhAG4A
ZAAgACIATwBQAFQASQBPAE4AQQBMACIAIABpAG4AIAB0AGgAaQBzAAoAIAAgACAAZABvAGMAdQBt
AGUAbgB0ACAAYQByAGUAIAB0AG8AIABiAGUAIABpAG4AdABlAHIAcAByAGUAdABlAGQAIABhAHMA
IABkAGUAcwBjAHIAaQBiAGUAZAAgAGkAbgAgAFsAUgBGAEMAMgAxADEAOQBdAC4ACgAKAEkATgBU
AEUAUgBOAEUAVAAtAEQAUgBBAEYAVAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAVABSAEkATABMADoAIABIAGUAYQBk
AGUAcgAgAEUAeAB0AGUAbgBzAGkAbwBuAAoACgAyAC4AIABUAFIASQBMAEwAIABIAGUAYQBkAGUA
cgAgAEUAeAB0AGUAbgBzAGkAbwBuAHMACgAKACAAIAAgAFQAaABlACAAYgBhAHMAZQAgAFQAUgBJ
AEwATAAgAFAAcgBvAHQAbwBjAG8AbAAgAGkAbgBjAGwAdQBkAGUAcwAgAGEAIABmAGUAYQB0AHUA
cgBlACAAZgBvAHIAIABlAHgAdABlAG4AcwBpAG8AbgAgAG8AZgAgAHQAaABlACAAVABSAEkATABM
AAoAIAAgACAASABlAGEAZABlAHIAIAAoAHMAZQBlACAAWwBSAEYAQwA2ADMAMgA1AF0AIABTAGUA
YwB0AGkAbwBuAHMAIAAzAC4ANQAgAGEAbgBkACAAMwAuADgAKQAuACAAIABUAGgAZQAgADUALQBi
AGkAdAAgAE8AcAAtAEwAZQBuAGcAdABoAAoAIAAgACAAaABlAGEAZABlAHIAIABmAGkAZQBsAGQA
IABnAGkAdgBlAHMAIAB0AGgAZQAgAGwAZQBuAGcAdABoACAAbwBmACAAdABoAGUAIABlAHgAdABl
AG4AcwBpAG8AbgBzACAAdABvACAAdABoAGUAIABUAFIASQBMAEwAIABIAGUAYQBkAGUAcgAKACAA
IAAgAGkAbgAgAHUAbgBpAHQAcwAgAG8AZgAgADQAIABvAGMAdABlAHQAcwAsACAAdwBoAGkAYwBo
ACAAYQBsAGwAbwB3AHMAIAB1AHAAIAB0AG8AIAAxADIANAAgAG8AYwB0AGUAdABzACAAbwBmACAA
aABlAGEAZABlAHIACgAgACAAIABlAHgAdABlAG4AcwBpAG8AbgAuACAASQBmACAATwBwAC0ATABl
AG4AZwB0AGgAIABpAHMAIAB6AGUAcgBvACAAdABoAGUAcgBlACAAYQByAGUAIABuAG8AIABoAGUA
YQBkAGUAcgAgAGUAeAB0AGUAbgBzAGkAbwBuAHMACgAgACAAIABwAHIAZQBzAGUAbgB0ADsAIABl
AGwAcwBlACwAIAB0AGgAZQAgAGUAeAB0AGUAbgBzAGkAbwBuACAAYQByAGUAYQAgAGYAbwBsAGwA
bwB3AHMAIABpAG0AbQBlAGQAaQBhAHQAZQBsAHkAIABhAGYAdABlAHIAIAB0AGgAZQAKACAAIAAg
AEkAbgBnAHIAZQBzAHMAIABSAEIAcgBpAGQAZwBlACAAPABzAHQAcgBvAG4AZwA+ADwAZgBvAG4A
dAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcAIABzAGkAegBlAD0AIgArADEAIgA+ACgAUgBv
AHUAdABpAG4AZwAgAEIAcgBpAGQAZwBlACkAPAAvAGYAbwBuAHQAPgA8AC8AcwB0AHIAbwBuAGcA
PgAgAE4AaQBjAGsAbgBhAG0AZQAgAGYAaQBlAGwAZAAgAG8AZgAgAHQAaABlACAAVABSAEkATABM
ACAASABlAGEAZABlAHIALgAKACAAIAAgAFQAaABlACAAZgBpAHIAcwB0ACAAMwAyAC0AYgBpAHQA
IAB3AG8AcgBkACAAbwBmACAAdABoAGUAIABvAHAAdABpAG8AbgBhAGwAIABlAHgAdABlAG4AcwBp
AG8AbgBzACAAYQByAGUAYQAgAGMAbwBuAHMAaQBzAHQAcwAgAG8AZgAgAGEAbgAKACAAIAAgAGUA
eAB0AGUAbgBkAGUAZAAgAGYAbABhAGcAcwAgAGEAcgBlAGEAIABhAG4AZAAgAGMAcgBpAHQAaQBj
AGEAbAAgAHMAdQBtAG0AYQByAHkAIABiAGkAdABzACAAYQBzACAAcwBwAGUAYwBpAGYAaQBlAGQA
IABpAG4AIAB0AGgAaQBzAAoAIAAgACAAZABvAGMAdQBtAGUAbgB0AC4ACgAKACAAIAAgAEEAcwAg
AGQAZQBzAGMAcgBpAGIAZQBkACAAYgBlAGwAbwB3ACwAIABwAHIAbwB2AGkAcwBpAG8AbgAgAGkA
cwAgAG0AYQBkAGUAIABmAG8AcgAKAAoAIAAgACAAIAAgACAAbwAgACAAaABvAHAALQBiAHkALQBo
AG8AcAAgAGYAbABhAGcAcwAsACAAdwBoAGkAYwBoACAAbQBpAGcAaAB0ACAAYQBmAGYAZQBjAHQA
IABhAG4AeQAgAFIAQgByAGkAZABnAGUAIAB0AGgAYQB0ACAAcgBlAGMAZQBpAHYAZQBzAAoAIAAg
ACAAIAAgACAAIAAgACAAYQAgAFQAUgBJAEwATAAgAEQAYQB0AGEAIABmAHIAYQBtAGUAIAB3AGkA
dABoACAAcwB1AGMAaAAgAGEAIABmAGwAYQBnACAAcwBlAHQALAAKAAoAIAAgACAAIAAgACAAbwAg
ACAAaQBuAGcAcgBlAHMAcwAtAHQAbwAtAGUAZwByAGUAcwBzACAAZgBsAGEAZwBzACwAIAB3AGgA
aQBjAGgAIAB3AG8AdQBsAGQAIABvAG4AbAB5ACAAbgBlAGMAZQBzAHMAYQByAGkAbAB5ACAAYQBm
AGYAZQBjAHQACgAgACAAIAAgACAAIAAgACAAIAB0AGgAZQAgAFIAQgByAGkAZABnAGUAKABzACkA
IAB3AGgAZQByAGUAIABhACAAVABSAEkATABMACAAZgByAGEAbQBlACAAaQBzACAAZABlAGMAYQBw
AHMAdQBsAGEAdABlAGQALAAKAAoAIAAgACAAIAAgACAAbwAgACAAPABzAHQAcgBpAGsAZQA+ADwA
ZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAcgBlAGQAJwAgAHMAaQB6AGUAPQAiACsAMQAiAD4AZgBs
AGEAZwA8AC8AZgBvAG4AdAA+ADwALwBzAHQAcgBpAGsAZQA+ACAAIAA8AHMAdAByAG8AbgBnAD4A
PABmAG8AbgB0ACAAYwBvAGwAbwByAD0AJwBnAHIAZQBlAG4AJwAgAHMAaQB6AGUAPQAiACsAMQAi
AD4AZgBsAGEAZwBzADwALwBmAG8AbgB0AD4APAAvAHMAdAByAG8AbgBnAD4AIABhAGYAZgBlAGMA
dABpAG4AZwAgAGEAbgAgAGEAcwAgAHkAZQB0ACAAdQBuAHMAcABlAGMAaQBmAGkAZQBkACAAYwBs
AGEAcwBzACAAbwBmACAAUgBCAHIAaQBkAGcAZQBzACwAIABmAG8AcgAKACAAIAAgACAAIAAgACAA
IAAgAGUAeABhAG0AcABsAGUAIABiAG8AcgBkAGUAcgAgAFIAQgByAGkAZABnAGUAcwAgAGkAbgAg
AGEAIABUAFIASQBMAEwAIABjAGEAbQBwAHUAcwAgAGUAeAB0AGUAbgBkAGUAZAAgAHQAbwAgAHMA
dQBwAHAAbwByAHQACgAgACAAIAAgACAAIAAgACAAIABtAHUAbAB0AGkALQBsAGUAdgBlAGwAIAA8
AHMAdAByAGkAawBlAD4APABmAG8AbgB0ACAAYwBvAGwAbwByAD0AJwByAGUAZAAnACAAcwBpAHoA
ZQA9ACIAKwAxACIAPgBJAFMALQBJAFMALAA8AC8AZgBvAG4AdAA+ADwALwBzAHQAcgBpAGsAZQA+
ACAAPABzAHQAcgBvAG4AZwA+ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcA
IABzAGkAegBlAD0AIgArADEAIgA+AEkAUwAtAEkAUwAgACgASQBuAHQAZQByAG0AZQBkAGkAYQB0
AGUAIABTAHkAcwB0AGUAbQAgAHQAbwAgAEkAbgB0AGUAcgBtAGUAZABpAGEAdABlACAAUwB5AHMA
dABlAG0AKQAsADwALwBmAG8AbgB0AD4APAAvAHMAdAByAG8AbgBnAD4ACgAgACAAIAAgACAAIAAg
ACAAIABhAG4AZAAKAAoAIAAgACAAIAAgACAAbwAgACAAYgBvAHQAaAAgACIAYwByAGkAdABpAGMA
YQBsACIAIABhAG4AZAAgACIAbgBvAG4ALQBjAHIAaQB0AGkAYwBhAGwAIgAgAGYAbABhAGcAcwAu
AAoACgAgACAAIABBAG4AeQAgAFIAQgByAGkAZABnAGUAIAByAGUAYwBlAGkAdgBpAG4AZwAgAGEA
IABmAHIAYQBtAGUAIAB3AGkAdABoACAAYQAgAGMAcgBpAHQAaQBjAGEAbAAgAGgAbwBwAC0AYgB5
AC0AaABvAHAAIABlAHgAdABlAG4AcwBpAG8AbgAKACAAIAAgAHQAaABhAHQAIABpAHQAIABkAG8A
ZQBzACAAbgBvAHQAIABpAG0AcABsAGUAbQBlAG4AdAAgAE0AVQBTAFQAIABkAGkAcwBjAGEAcgBk
ACAAdABoAGUAIABmAHIAYQBtAGUAIABiAGUAYwBhAHUAcwBlACAAaQB0ACAAaQBzAAoAIAAgACAA
dQBuAHMAYQBmAGUAIAB0AG8AIABwAHIAbwBjAGUAcwBzACAAdABoAGUAIABmAHIAYQBtAGUAIAB3
AGkAdABoAG8AdQB0ACAAdQBuAGQAZQByAHMAdABhAG4AZABpAG4AZwAgAHMAdQBjAGgAIABhACAA
YwByAGkAdABpAGMAYQBsAAoAIAAgACAAZQB4AHQAZQBuAHMAaQBvAG4ALgAKAAoAIAAgACAAQQBu
AHkAIABlAGcAcgBlAHMAcwAgAFIAQgByAGkAZABnAGUAIAByAGUAYwBlAGkAdgBpAG4AZwAgAGEA
IABmAHIAYQBtAGUAIAB3AGkAdABoACAAYQAgAGMAcgBpAHQAaQBjAGEAbAAgAGkAbgBnAHIAZQBz
AHMALQB0AG8ALQAKACAAIAAgAGUAZwByAGUAcwBzACAAZQB4AHQAZQBuAHMAaQBvAG4AIABpAHQA
IABkAG8AZQBzACAAbgBvAHQAIABpAG0AcABsAGUAbQBlAG4AdAAgAE0AVQBTAFQAIABkAHIAbwBw
ACAAdABoAGUAIABmAHIAYQBtAGUAIABpAGYAIABpAHQAIABpAHMAIABhAAoAIAAgACAAawBuAG8A
dwBuACAAdQBuAGkAYwBhAHMAdAAgAGYAcgBhAG0AZQA7ACAAaQBmACAAaQB0ACAAaQBzACAAYQAg
AG0AdQBsAHQAaQAtAGQAZQBzAHQAaQBuAGEAdABpAG8AbgAgAFQAUgBJAEwATAAgAEQAYQB0AGEA
IABmAHIAYQBtAGUALAAKACAAIAAgAHQAaABlAG4AIABpAHQAIABNAFUAUwBUACAATgBPAFQAIABi
AGUAIABlAGcAcgBlAHMAcwBlAGQAIABhAHQAIAB0AGgAYQB0ACAAUgBCAHIAaQBkAGcAZQAgAGIA
dQB0ACAAdABoAGUAIABlAGcAcgBlAHMAcwAgAFIAQgByAGkAZABnAGUACgAgACAAIABzAHQAaQBs
AGwAIABmAG8AcgB3AGEAcgBkAHMAIABzAHUAYwBoACAAYQAgAGYAcgBhAG0AZQAgAG8AbgAgAHQA
aABlACAAZABpAHMAdAByAGkAYgB1AHQAaQBvAG4AIAB0AHIAZQBlAC4ACgAKACAAIAAgAE4AbwBu
AC0AYwByAGkAdABpAGMAYQBsACAAZQB4AHQAZQBuAHMAaQBvAG4AcwAgAGMAYQBuACAAYgBlACAA
cwBhAGYAZQBsAHkAIABpAGcAbgBvAHIAZQBkAC4ACgAKACAAIAAgAEEAbgB5ACAAZQB4AHQAZQBu
AGQAZQBkACAAZgBsAGEAZwAgAGkAbgBkAGkAYwBhAHQAaQBuAGcAIABhACAAcwBpAGcAbgBpAGYA
aQBjAGEAbgB0ACAAYwBoAGEAbgBnAGUAIABpAG4AIAB0AGgAZQAgAHMAdAByAHUAYwB0AHUAcgBl
ACAAbwByAAoAIAAgACAAaQBuAHQAZQByAHAAcgBlAHQAYQB0AGkAbwBuACAAbwBmACAAbABhAHQA
ZQByACAAcABhAHIAdABzACAAbwBmACAAdABoAGUAIABmAHIAYQBtAGUAIAB3AGgAaQBjAGgALAAg
AGkAZgAgAHQAaABlACAAZQB4AHQAZQBuAGQAZQBkAAoAIAAgACAAZgBsAGEAZwAgAHcAZQByAGUA
IABpAGcAbgBvAHIAZQBkACwAIABjAG8AdQBsAGQAIABjAGEAdQBzAGUAIABhACAAZgBhAGkAbAB1
AHIAZQAgAG8AZgAgAHMAZQByAHYAaQBjAGUAIABvAHIAIAB2AGkAbwBsAGEAdABpAG8AbgAgAG8A
ZgAKACAAIAAgAHMAZQBjAHUAcgBpAHQAeQAgAHAAbwBsAGkAYwB5ACAATQBVAFMAVAAgAGIAZQAg
AGEAIABjAHIAaQB0AGkAYwBhAGwAIABlAHgAdABlAG4AcwBpAG8AbgAuACAASQBmACAAcwB1AGMA
aAAgAGEAbgAgAGUAeAB0AGUAbgBkAGUAZAAKACAAIAAgAGYAbABhAGcAIABhAGYAZgBlAGMAdABz
ACAAYQBuAHkAIABmAGkAZQBsAGQAcwAgAHQAaABhAHQAIAB0AHIAYQBuAHMAaQB0ACAAUgBCAHIA
aQBkAGcAZQBzACAAdwBpAGwAbAAgAGUAeABhAG0AaQBuAGUALAAgAGkAdAAgAE0AVQBTAFQACgAg
ACAAIABiAGUAIABhACAAaABvAHAALQBiAHkALQBoAG8AcAAgAGMAcgBpAHQAaQBjAGEAbAAgAGUA
eAB0AGUAbgBkAGUAZAAgAGYAbABhAGcALgAKAAoAIAAgACAAIAAgACAATgBvAHQAZQA6ACAATQBv
AHMAdAAgAFIAQgByAGkAZABnAGUAcwAgAGkAbQBwAGwAZQBtAGUAbgB0AGEAdABpAG8AbgBzACAA
YQByAGUAIABlAHgAcABlAGMAdABlAGQAIAB0AG8AIABiAGUAIABvAHAAdABpAG0AaQB6AGUAZAAK
ACAAIAAgACAAIAAgAGYAbwByACAAcwBpAG0AcABsAGUAIABhAG4AZAAgAGMAbwBtAG0AbwBuACAA
YwBhAHMAZQBzACAAbwBmACAAZgByAGEAbQBlACAAZgBvAHIAdwBhAHIAZABpAG4AZwAgAGEAbgBk
ACAAcAByAG8AYwBlAHMAcwBpAG4AZwAuAAoACgA8AHMAdAByAG8AbgBnAD4APABmAG8AbgB0ACAA
YwBvAGwAbwByAD0AJwBnAHIAZQBlAG4AJwAgAHMAaQB6AGUAPQAiACsAMQAiAD4ASQBOAFQARQBS
AE4ARQBUAC0ARABSAEEARgBUACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABUAFIASQBMAEwAOgAgAEgAZQBhAGQAZQBy
ACAARQB4AHQAZQBuAHMAaQBvAG4APAAvAGYAbwBuAHQAPgA8AC8AcwB0AHIAbwBuAGcAPgAKAAoA
IAAgACAAIAAgACAAQQBsAHQAaABvAHUAZwBoACAAdABoAGUAIABoAGEAcgBkACAAbABpAG0AaQB0
ACAAbwBuACAAdABoAGUAIABoAGUAYQBkAGUAcgAgAGUAeAB0AGUAbgBzAGkAbwBuAHMAIABhAHIA
ZQBhACAAbABlAG4AZwB0AGgALAAgAHQAaABlAAoAIAAgACAAIAAgACAAMwAyAC0AYgBpAHQAIABh
AGwAaQBnAG4AbQBlAG4AdAAgAG8AZgAgAHQAaABlACAAZQB4AHQAZQBuAHMAaQBvAG4AIABhAHIA
ZQBhACwAIABhAG4AZAAgAHQAaABlACAAcAByAGUAcwBlAG4AYwBlACAAbwBmAAoACgA8AHMAdABy
AGkAawBlAD4APABmAG8AbgB0ACAAYwBvAGwAbwByAD0AJwByAGUAZAAnACAAcwBpAHoAZQA9ACIA
KwAxACIAPgBJAE4AVABFAFIATgBFAFQALQBEAFIAQQBGAFQAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAFQAUgBJAEwA
TAA6ACAASABlAGEAZABlAHIAIABFAHgAdABlAG4AcwBpAG8AbgA8AC8AZgBvAG4AdAA+ADwALwBz
AHQAcgBpAGsAZQA+AAoAIAAgACAAIAAgACAAYwByAGkAdABpAGMAYQBsACAAZQB4AHQAZQBuAHMA
aQBvAG4AIABzAHUAbQBtAGEAcgB5ACAAYgBpAHQAcwAsACAAYQBzACAAZABlAHMAYwByAGkAYgBl
AGQAIABiAGUAbABvAHcALAAgAGEAcgBlACAAaQBuAHQAZQBuAGQAZQBkAAoAIAAgACAAIAAgACAA
dABvACAAYQBzAHMAaQBzAHQAIABpAG4AIAB0AGgAZQAgAGUAZgBmAGkAYwBpAGUAbgB0ACAAaABh
AHIAZAB3AGEAcgBlACAAcAByAG8AYwBlAHMAcwBpAG4AZwAgAG8AZgAgAGYAcgBhAG0AZQBzACAA
dwBpAHQAaAAgAGEACgAgACAAIAAgACAAIABUAFIASQBMAEwAIABoAGUAYQBkAGUAcgAgAGUAeAB0
AGUAbgBzAGkAbwBuAHMAIABhAHIAZQBhACwAIABuAGUAdgBlAHIAdABoAGUAbABlAHMAcwAgAHQA
aABlACAAaQBuAGMAbAB1AHMAaQBvAG4AIABvAGYACgAgACAAIAAgACAAIABlAHgAdABlAG4AcwBp
AG8AbgBzACAAbQBhAHkAIABjAGEAdQBzAGUAIABmAHIAYQBtAGUAIABwAHIAbwBjAGUAcwBzAGkA
bgBnACAAdQBzAGkAbgBnACAAYQAgACIAcwBsAG8AdwAgAHAAYQB0AGgAIgAgAHcAaQB0AGgACgAg
ACAAIAAgACAAIABpAG4AZgBlAHIAaQBvAHIAIABwAGUAcgBmAG8AcgBtAGEAbgBjAGUAIAB0AG8A
IAAiAGYAYQBzAHQAIABwAGEAdABoACIAIABwAHIAbwBjAGUAcwBzAGkAbgBnAC4AIABMAGkAbQBp
AHQAZQBkACAAcwBsAG8AdwAgAHAAYQB0AGgACgAgACAAIAAgACAAIAB0AGgAcgBvAHUAZwBoAHAA
dQB0ACAAbwBmACAAcwB1AGMAaAAgAGYAcgBhAG0AZQBzACAAYwBvAHUAbABkACAAYwBhAHUAcwBl
ACAAcwBvAG0AZQAgAG8AZgAgAHQAaABlAG0AIAB0AG8AIABiAGUACgAgACAAIAAgACAAIABkAGkA
cwBjAGEAcgBkAGUAZAAuAAoACgAyAC4AMQAgAFIAQgByAGkAZABnAGUAIABFAHgAdABlAG4AZABl
AGQAIABGAGwAYQBnACAASABhAG4AZABsAGkAbgBnACAAUgBlAHEAdQBpAHIAZQBtAGUAbgB0AHMA
CgAKACAAIAAgAEEAbABsACAAUgBCAHIAaQBkAGcAZQBzACAATQBVAFMAVAAgAGMAaABlAGMAawAg
AHcAaABlAHQAaABlAHIAIAB0AGgAZQByAGUAIABhAHIAZQAgAGEAbgB5ACAAYwByAGkAdABpAGMA
YQBsACAAZgBsAGEAZwBzACAAcwBlAHQAIAB0AGgAYQB0AAoAIAAgACAAYQByAGUAIABuAGUAYwBl
AHMAcwBhAHIAaQBsAHkAIABhAHAAcABsAGkAYwBhAGIAbABlACAAdABvACAAdABoAGUAaQByACAA
cAByAG8AYwBlAHMAcwBpAG4AZwAgAG8AZgAgAHQAaABlACAAZgByAGEAbQBlAC4AIABUAG8ACgAg
ACAAIABhAHMAcwBpAHMAdAAgAGkAbgAgAHQAaABpAHMAIAB0AGEAcwBrACwAIABjAHIAaQB0AGkA
YwBhAGwAIABzAHUAbQBtAGEAcgB5ACAAYgBpAHQAcwAgAGEAcgBlACAAcAByAG8AdgBpAGQAZQBk
ACAAdABoAGEAdAAgAGMAbwB2AGUAcgAKACAAIAAgAG4AbwB0ACAAbwBuAGwAeQAgAHQAaABlACAA
ZQB4AHQAZQBuAGQAZQBkACAAZgBsAGEAZwBzACAAcwBwAGUAYwBpAGYAaQBlAGQAIABoAGUAcgBl
AGkAbgAgAGIAdQB0ACAAdwBpAGwAbAAgAGMAbwB2AGUAcgAgAGEAbgB5AAoAIAAgACAAZgB1AHIA
dABoAGUAcgAgAGUAeAB0AGUAbgBzAGkAbwBuAHMAIAB0AGgAYQB0ACAAbQBhAHkAIABiAGUAIABz
AHAAZQBjAGkAZgBpAGUAZAAgAGkAbgAgAGYAdQB0AHUAcgBlACAAPABzAHQAcgBpAGsAZQA+ADwA
ZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAcgBlAGQAJwAgAHMAaQB6AGUAPQAiACsAMQAiAD4AZABv
AGMAdQBtAGUAbgB0AHMAPAAvAGYAbwBuAHQAPgA8AC8AcwB0AHIAaQBrAGUAPgAgADwAcwB0AHIA
bwBuAGcAPgA8AGYAbwBuAHQAIABjAG8AbABvAHIAPQAnAGcAcgBlAGUAbgAnACAAcwBpAHoAZQA9
ACIAKwAxACIAPgBkAG8AYwB1AG0AZQBuAHQAcwAsACAAZgBvAHIACgAgACAAIABlAHgAYQBtAHAA
bABlADwALwBmAG8AbgB0AD4APAAvAHMAdAByAG8AbgBnAD4AIABbAE8AcAB0AGkAbwBuAHMAXQAu
ACAASQBmACAAYQBuACAAUgBCAHIAaQBkAGcAZQAgAGQAbwBlAHMAIABuAG8AdAAgAGkAbQBwAGwA
ZQBtAGUAbgB0ACAAYQBsAGwAIABjAHIAaQB0AGkAYwBhAGwACgAgACAAIABmAGwAYQBnAHMAIABp
AG4AIABhACAAVABSAEkATABMACAARABhAHQAYQAgAGYAcgBhAG0AZQAsACAAaQB0ACAATQBVAFMA
VAAgADwAcwB0AHIAaQBrAGUAPgA8AGYAbwBuAHQAIABjAG8AbABvAHIAPQAnAHIAZQBkACcAIABz
AGkAegBlAD0AIgArADEAIgA+AGQAaQBzAGMAYQByAGQAPAAvAGYAbwBuAHQAPgA8AC8AcwB0AHIA
aQBrAGUAPgAgADwAcwB0AHIAbwBuAGcAPgA8AGYAbwBuAHQAIABjAG8AbABvAHIAPQAnAGcAcgBl
AGUAbgAnACAAcwBpAHoAZQA9ACIAKwAxACIAPgB0AHIAZQBhAHQAPAAvAGYAbwBuAHQAPgA8AC8A
cwB0AHIAbwBuAGcAPgAgAHQAaABlACAAZgByAGEAbQBlACAAPABzAHQAcgBpAGsAZQA+ADwAZgBv
AG4AdAAgAGMAbwBsAG8AcgA9ACcAcgBlAGQAJwAgAHMAaQB6AGUAPQAiACsAMQAiAD4AbwByACwA
IABpAG4AIABzAG8AbQBlACAAYwBpAHIAYwB1AG0AcwB0AGEAbgBjAGUAcwA8AC8AZgBvAG4AdAA+
ADwALwBzAHQAcgBpAGsAZQA+ACAAPABzAHQAcgBvAG4AZwA+ADwAZgBvAG4AdAAgAGMAbwBsAG8A
cgA9ACcAZwByAGUAZQBuACcAIABzAGkAegBlAD0AIgArADEAIgA+AGEAcwAgAGgAYQB2AGkAbgBn
ACAAYQBuAAoAIAAgACAAdQBuAGkAbQBwAGwAZQBtAGUAbgB0AGUAZAAgAGMAcgBpAHQAaQBjAGEA
bAAgAGUAeAB0AGUAbgBzAGkAbwBuADwALwBmAG8AbgB0AD4APAAvAHMAdAByAG8AbgBnAD4AIABh
AHMAIABkAGUAcwBjAHIAaQBiAGUAZAAgADwAcwB0AHIAaQBrAGUAPgA8AGYAbwBuAHQAIABjAG8A
bABvAHIAPQAnAHIAZQBkACcAIABzAGkAegBlAD0AIgArADEAIgA+AGYAbwByACAAYwBlAHIAdABh
AGkAbgAgAG0AdQBsAHQAaQAtAGQAZQBzAHQAaQBuAGEAdABpAG8AbgAgAGYAcgBhAG0AZQBzACwA
IABjAG8AbgB0AGkAbgB1AGUAIAB0AG8ACgAgACAAIABmAG8AcgB3AGEAcgBkACAAdABoAGUAIABm
AHIAYQBtAGUAIABiAHUAdAAgAE0AVQBTAFQAIABOAE8AVAAgAGUAZwByAGUAcwBzACAAdABoAGUA
IABmAHIAYQBtAGUALgA8AC8AZgBvAG4AdAA+ADwALwBzAHQAcgBpAGsAZQA+ACAAPABzAHQAcgBv
AG4AZwA+ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcAIABzAGkAegBlAD0A
IgArADEAIgA+AGkAbgAgAFMAZQBjAHQAaQBvAG4AIAAyAC4APAAvAGYAbwBuAHQAPgA8AC8AcwB0
AHIAbwBuAGcAPgAgAEEAIAB0AHIAYQBuAHMAaQB0AAoAIAAgACAAbwByACAAZQBnAHIAZQBzAHMA
IABSAEIAcgBpAGQAZwBlACAAbQBhAHkAIABhAHMAcwB1AG0AZQAgAHQAaABhAHQAIAB0AGgAZQAg
AGMAcgBpAHQAaQBjAGEAbAAgAHMAdQBtAG0AYQByAHkAIABiAGkAdABzACAAYQByAGUACgAgACAA
IABjAG8AcgByAGUAYwB0AC4ACgAKACAAIAAgAEkAbgAgAGEAZABkAGkAdABpAG8AbgAsACAAYQAg
AHQAcgBhAG4AcwBpAHQAIABSAEIAcgBpAGQAZwBlADoACgAKACAAIAAgAG8AIAAgAE0AQQBZACAA
cwBlAHQAIABvAHIAIABjAGwAZQBhAHIAIABoAG8AcAAtAGIAeQAtAGgAbwBwACAAZgBsAGEAZwBz
ACAAYQBzACAAcwBwAGUAYwBpAGYAaQBlAGQAIABmAG8AcgAgAHMAdQBjAGgAIABmAGwAYQBnAHMA
OwAKACAAIAAgAG8AIAAgAE0AVQBTAFQAIABhAGQAagB1AHMAdAAgAHQAaABlACAAbABlAG4AZwB0
AGgAIABvAGYAIAB0AGgAZQAgAGUAeAB0AGUAbgBzAGkAbwBuAHMAIABhAHIAZQBhACwAIABpAG4A
YwBsAHUAZABpAG4AZwAgAGMAaABhAG4AZwBpAG4AZwAKACAAIAAgACAAIAAgAE8AcAAtAEwAZQBu
AGcAdABoACAAaQBuACAAdABoAGUAIABUAFIASQBMAEwAIABoAGUAYQBkAGUAcgAsACAAYQBzACAA
YQBwAHAAcgBvAHAAcgBpAGEAdABlACAAaQBmACAAaQB0ACAAYQBkAGQAcwAgAG8AcgAKACAAIAAg
ACAAIAAgAHIAZQBtAG8AdgBlAHMAIAB0AGgAZQAgAHcAbwByAGQAIABvAGYAIABlAHgAdABlAG4A
ZABlAGQAIABoAGUAYQBkAGUAcgAgAGYAbABhAGcAcwA7AAoAIAAgACAAbwAgACAATQBVAFMAVAAs
ACAAaQBmACAAaQB0ACAAYQBkAGQAcwAgAHQAaABlACAAdwBvAHIAZAAgAG8AZgAgAGUAeAB0AGUA
bgBkAGUAZAAgAGgAZQBhAGQAZQByACAAZgBsAGEAZwBzACAAbwByACAAYwBoAGEAbgBnAGUAcwAg
AGEAbgB5AAoAIAAgACAAIAAgACAAYwByAGkAdABpAGMAYQBsACAAZgBsAGEAZwBzACwAIABjAG8A
cgByAGUAYwB0AGwAeQAgAHMAZQB0ACAAdABoAGUAIABjAHIAaQB0AGkAYwBhAGwAIABzAHUAbQBt
AGEAcgB5ACAAYgBpAHQAcwAgAGkAbgAgAHQAaABlAAoAIAAgACAAIAAgACAAZQB4AHQAZQBuAGQA
ZQBkACAAaABlAGEAZABlAHIAIABmAGwAYQBnAHMAIAB3AG8AcgBkADsACgAgACAAIABvACAAIABN
AFUAUwBUACAATgBPAFQAIAByAGUAbQBvAHYAZQAgAHQAaABlACAAZQB4AHQAZQBuAGQAZQBkACAA
aABlAGEAZABlAHIAIABmAGwAYQBnAHMAIAB3AG8AcgBkACAAdQBuAGwAZQBzAHMAIABpAHQAIABp
AHMAIABhAGwAbAAKACAAIAAgACAAIAAgAHoAZQByAG8AIAAoAGUAaQB0AGgAZQByACAAbwBuACAA
YQByAHIAaQB2AGEAbAAgAG8AcgAgAGEAZgB0AGUAcgAgAHAAZQByAG0AaQB0AHQAZQBkACAAbQBv
AGQAaQBmAGkAYwBhAHQAaQBvAG4AcwApADsACgAgACAAIABvACAAIABNAFUAUwBUACAATgBPAFQA
IABzAGUAdAAgAG8AcgAgAGMAbABlAGEAcgAgAGkAbgBnAHIAZQBzAHMALQB0AG8ALQBlAGcAcgBl
AHMAcwAgAG8AcgAgAHIAZQBzAGUAcgB2AGUAZAAgAGUAeAB0AGUAbgBkAGUAZAAKACAAIAAgACAA
IAAgAGgAZQBhAGQAZQByACAAZgBsAGEAZwBzACAAZQB4AGMAZQBwAHQAIABhAHMAIABzAHAAZQBj
AGkAZgBpAGMAYQBsAGwAeQAgAHAAZQByAG0AaQB0AHQAZQBkACAAaQBuACAAdABoAGUAIABzAHAA
ZQBjAGkAZgBpAGMAYQB0AGkAbwBuAAoAIAAgACAAIAAgACAAbwBmACAAcwB1AGMAaAAgAGYAbABh
AGcAcwAuAAoACgAyAC4AMgAgAE4AbwAgAEMAcgBpAHQAaQBjAGEAbAAgAFMAdQByAHAAcgBpAHMA
ZQBzAAoACgAgACAAIABSAEIAcgBpAGQAZwBlAHMAIABhAGQAdgBlAHIAdABpAHMAZQAgAHQAaABl
ACAAZQB4AHQAZQBuAGQAZQBkACAAaABlAGEAZABlAHIAIABmAGwAYQBnAHMAIAB0AGgAZQB5ACAA
cwB1AHAAcABvAHIAdAAgAGkAbgAgAEkAUwAtAEkAUwAKACAAIAAgAFAARABVAHMAIAA8AHMAdABy
AG8AbgBnAD4APABmAG8AbgB0ACAAYwBvAGwAbwByAD0AJwBnAHIAZQBlAG4AJwAgAHMAaQB6AGUA
PQAiACsAMQAiAD4AKABQAHIAbwB0AG8AYwBvAGwAIABEAGEAdABhACAAVQBuAGkAdABzACkAPAAv
AGYAbwBuAHQAPgA8AC8AcwB0AHIAbwBuAGcAPgAgAFsAUgBGAEMANgAzADIANgBiAGkAcwBdAC4A
IABVAG4AbABlAHMAcwAgAGEAbgAgAFIAQgByAGkAZABnAGUAIABhAGQAdgBlAHIAdABpAHMAZQBz
AAoAIAAgACAAcwB1AHAAcABvAHIAdAAgAGYAbwByACAAYQAgAGMAcgBpAHQAaQBjAGEAbAAgAGUA
eAB0AGUAbgBkAGUAZAAgAGgAZQBhAGQAZQByACAAZgBsAGEAZwAsACAAaQB0ACAAdwBpAGwAbAAg
AG4AbwB0ACAAbgBvAHIAbQBhAGwAbAB5AAoAIAAgACAAcgBlAGMAZQBpAHYAZQAgAGYAcgBhAG0A
ZQBzACAAdwBpAHQAaAAgAHQAaABhAHQAIABmAGwAYQBnACAAcwBlAHQALgAgAEEAbgAgAFIAQgBy
AGkAZABnAGUAIABpAHMAIABuAG8AdAAgAHIAZQBxAHUAaQByAGUAZAAgAHQAbwAKACAAIAAgAHMA
dQBwAHAAbwByAHQAIABhAG4AeQAgAGUAeAB0AGUAbgBzAGkAbwBuAHMALgAKAAoAPABzAHQAcgBv
AG4AZwA+ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcAIABzAGkAegBlAD0A
IgArADEAIgA+AEkATgBUAEUAUgBOAEUAVAAtAEQAUgBBAEYAVAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAVABSAEkA
TABMADoAIABIAGUAYQBkAGUAcgAgAEUAeAB0AGUAbgBzAGkAbwBuADwALwBmAG8AbgB0AD4APAAv
AHMAdAByAG8AbgBnAD4ACgAKACAAIAAgAEEAbgAgAFIAQgByAGkAZABnAGUAIABTAEgATwBVAEwA
RAAgAE4ATwBUACAAcwBlAHQAIABhACAAYwByAGkAdABpAGMAYQBsACAAZQB4AHQAZQBuAGQAZQBk
ACAAZgBsAGEAZwAgAGkAbgAgAGEAIABmAHIAYQBtAGUAIAB1AG4AbABlAHMAcwAsAAoACgA8AHMA
dAByAGkAawBlAD4APABmAG8AbgB0ACAAYwBvAGwAbwByAD0AJwByAGUAZAAnACAAcwBpAHoAZQA9
ACIAKwAxACIAPgBJAE4AVABFAFIATgBFAFQALQBEAFIAQQBGAFQAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAFQAUgBJ
AEwATAA6ACAASABlAGEAZABlAHIAIABFAHgAdABlAG4AcwBpAG8AbgA8AC8AZgBvAG4AdAA+ADwA
LwBzAHQAcgBpAGsAZQA+AAoACgAgACAAIAAtACAAIABmAG8AcgAgAGEAIABjAHIAaQB0AGkAYwBh
AGwAIABoAG8AcAAtAGIAeQAtAGgAbwBwACAAZQB4AHQAZQBuAGQAZQBkACAAaABlAGEAZABlAHIA
IABmAGwAYQBnACwAIABpAHQAIABoAGEAcwAgAGQAZQB0AGUAcgBtAGkAbgBlAGQACgAgACAAIAAg
ACAAIAB0AGgAYQB0ACAAdABoAGUAIABuAGUAeAB0ACAAaABvAHAAIABSAEIAcgBpAGQAZwBlACAA
bwByACAAUgBCAHIAaQBkAGcAZQBzACAAdABoAGEAdAAgAHcAaQBsAGwAIABhAGMAYwBlAHAAdAAg
AHQAaABlACAAZgByAGEAbQBlAAoAIAAgACAAIAAgACAAcwB1AHAAcABvAHIAdAAgAHQAaABhAHQA
IABmAGwAYQBnACwACgAgACAAIAAtACAAIABmAG8AcgAgAGEAIABjAHIAaQB0AGkAYwBhAGwAIABp
AG4AZwByAGUAcwBzAC0AdABvAC0AZQBnAHIAZQBzAHMAIABlAHgAdABlAG4AZABlAGQAIABoAGUA
YQBkAGUAcgAgAGYAbABhAGcALAAgAGkAdAAgAGgAYQBzAAoAIAAgACAAIAAgACAAZABlAHQAZQBy
AG0AaQBuAGUAZAAgAHQAaABhAHQAIAB0AGgAZQAgAFIAQgByAGkAZABnAGUAIABvAHIAIABSAEIA
cgBpAGQAZwBlAHMAIAB0AGgAYQB0ACAAdwBpAGwAbAAgAGUAZwByAGUAcwBzACAAdABoAGUAIABm
AHIAYQBtAGUACgAgACAAIAAgACAAIABzAHUAcABwAG8AcgB0ACAAdABoAGEAdAAgAGYAbABhAGcA
LAAgAG8AcgAKACAAIAAgAC0AIAAgAGYAbwByACAAYQAgAGMAcgBpAHQAaQBjAGEAbAAgAHIAZQBz
AGUAcgB2AGUAZAAgAGUAeAB0AGUAbgBkAGUAZAAgAGgAZQBhAGQAZQByACAAZgBsAGEAZwAsACAA
aQB0ACAAbQBhAHkAIABzAGUAdAAgAHMAdQBjAGgAIABhAAoAIAAgACAAIAAgACAAZgBsAGEAZwAg
AG8AbgBsAHkAIABpAGYAIABpAHQAIAB1AG4AZABlAHIAcwB0AGEAbgBkAHMAIAB3AGgAaQBjAGgA
IABSAEIAcgBpAGQAZwBlAHMAIABpAHQAIABpAHMAIABhAHAAcABsAGkAYwBhAGIAbABlACAAdABv
ACAAYQBuAGQACgAgACAAIAAgACAAIABoAGEAcwAgAGQAZQB0AGUAcgBtAGkAbgBlAGQAIAB0AGgA
YQB0ACAAdABoAG8AcwBlACAAUgBCAHIAaQBkAGcAZQBzACAAdABoAGEAdAAgAHcAaQBsAGwAIABh
AGMAYwBlAHAAdAAgAHQAaABlACAAZgByAGEAbQBlAAoAIAAgACAAIAAgACAAcwB1AHAAcABvAHIA
dAAgAHQAaABhAHQAIABmAGwAYQBnAC4ACgAKACAAIAAgACIAUwBIAE8AVQBMAEQAIABOAE8AVAAi
ACAAaQBzACAAcwBwAGUAYwBpAGYAaQBlAGQAIABhAGIAbwB2AGUAIABzAGkAbgBjAGUAIAB0AGgA
ZQByAGUAIABtAGEAeQAgAGIAZQAgAGMAYQBzAGUAcwAgAHcAaABlAHIAZQAgAGkAdAAgAGkAcwAK
ACAAIAAgAGEAYwBjAGUAcAB0AGEAYgBsAGUAIABmAG8AcgAgAHQAaABvAHMAZQAgAGYAcgBhAG0A
ZQBzACwAIABwAGEAcgB0AGkAYwB1AGwAYQByAGwAeQAgAGYAbwByACAAdABoAGUAIABtAHUAbAB0
AGkALQBkAGUAcwB0AGkAbgBhAHQAaQBvAG4ACgAgACAAIABjAGEAcwBlACwAIAB0AG8AIABiAGUA
IABkAGkAcwBjAGEAcgBkAGUAZAAgAG8AcgAgAG4AbwB0ACAAZQBnAHIAZQBzAHMAZQBkACAAYgB5
ACAAYQBuAHkAIABSAEIAcgBpAGQAZwBlAHMAIAB0AGgAYQB0ACAAZABvACAAbgBvAHQACgAgACAA
IABpAG0AcABsAGUAbQBlAG4AdAAgAHQAaABlACAAZQB4AHQAZQBuAGQAZQBkACAAZgBsAGEAZwAu
AAoACgAyAC4AMwAgAEUAeAB0AGUAbgBkAGUAZAAgAEgAZQBhAGQAZQByACAARgBsAGEAZwBzAAoA
CgAgACAAIABJAGYAIABhAG4AeQAgAGUAeAB0AGUAbgBzAGkAbwBuAHMAIABhAHIAZQAgAHAAcgBl
AHMAZQBuAHQAIABpAG4AIABhACAAVABSAEkATABMACAASABlAGEAZABlAHIALAAgAGEAcwAgAGkA
bgBkAGkAYwBhAHQAZQBkACAAYgB5ACAAYQAKACAAIAAgAG4AbwBuAC0AegBlAHIAbwAgAE8AcAAt
AEwAZQBuAGcAdABoACAAZgBpAGUAbABkACwAIAB0AGgAZQAgAGYAaQByAHMAdAAgADMAMgAgAGIA
aQB0AHMAIABvAGYAIAB0AGgAZQAgAGUAeAB0AGUAbgBzAGkAbwBuAHMAIABhAHIAZQBhAAoAIAAg
ACAAYwBvAG4AcwBpAHMAdAAgAG8AZgAgAEUAeAB0AGUAbgBkAGUAZAAgAEgAZQBhAGQAZQByACAA
RgBsAGEAZwBzACwAIABhAHMAIABkAGUAcwBjAHIAaQBiAGUAZAAgAGIAZQBsAG8AdwAuACAAVABo
AGUAIAByAGUAbQBhAGkAbgBkAGUAcgAKACAAIAAgAG8AZgAgAHQAaABlACAAZQB4AHQAZQBuAHMA
aQBvAG4AcwAgAGEAcgBlAGEALAAgAGkAZgAgAGEAbgB5ACwAIABhAGYAdABlAHIAIAB0AGgAaQBz
ACAAaQBuAGkAdABpAGEAbAAgADMAMgAgAGIAaQB0AHMALAAgAG0AYQB5ACAAYgBlAAoAIAAgACAA
cwBwAGUAYwBpAGYAaQBlAGQAIABpAG4AIABsAGEAdABlAHIAIABkAG8AYwB1AG0AZQBuAHQAcwAg
AFsATwBwAHQAaQBvAG4AcwBdAC4ACgAKACAAIAAgAEEAbgB5ACAAUgBCAHIAaQBkAGcAZQAgAGEA
ZABkAGkAbgBnACAAYQBuACAAZQB4AHQAZQBuAHMAaQBvAG4AcwAgAGEAcgBlAGEAIAB0AG8AIABh
ACAAVABSAEkATABMACAASABlAGEAZABlAHIAIABtAHUAcwB0ACAAcwBlAHQAIAB0AGgAZQAKACAA
IAAgAGYAaQByAHMAdAAgADMAMgAgAGIAaQB0AHMAIAB0AG8AIAB6AGUAcgBvACAAZQB4AGMAZQBw
AHQAIAB3AGgAZQBuACAAcABlAHIAbQBpAHQAdABlAGQAIABvAHIAIAByAGUAcQB1AGkAcgBlAGQA
IAB0AG8AIABzAGUAdAAgAG8AbgBlACAAbwByAAoAIAAgACAAbQBvAHIAZQAgAG8AZgAgAHQAaABv
AHMAZQAgAGIAaQB0AHMAIABhAHMAIABzAHAAZQBjAGkAZgBpAGUAZAAuACAARgBvAHIAIABUAFIA
SQBMAEwAIABEAGEAdABhACAAZgByAGEAbQBlAHMAIAB3AGkAdABoAAoAIAAgACAAZQB4AHQAZQBu
AHMAaQBvAG4AcwAgAHAAcgBlAHMAZQBuAHQALAAgAGEAbgB5ACAAdAByAGEAbgBzAGkAdAAgAFIA
QgByAGkAZABnAGUAIAB0AGgAYQB0ACAAZABvAGUAcwAgAG4AbwB0ACAAZABpAHMAYwBhAHIAZAAg
AHQAaABlAAoAIAAgACAAZgByAGEAbQBlACAATQBVAFMAVAAgAHQAcgBhAG4AcwBwAGEAcgBlAG4A
dABsAHkAIABjAG8AcAB5ACAAdABoAGUAIABlAHgAdABlAG4AZABlAGQAIABmAGwAYQBnAHMAIAB3
AG8AcgBkACwAIABlAHgAYwBlAHAAdAAgAGYAbwByAAoAIAAgACAAPABzAHQAcgBpAGsAZQA+ADwA
ZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAcgBlAGQAJwAgAHMAaQB6AGUAPQAiACsAMQAiAD4AbQBv
AGQAaQBmAGkAYwB0AGkAbwBuAHMAPAAvAGYAbwBuAHQAPgA8AC8AcwB0AHIAaQBrAGUAPgAKACAA
IAAgADwAcwB0AHIAbwBuAGcAPgA8AGYAbwBuAHQAIABjAG8AbABvAHIAPQAnAGcAcgBlAGUAbgAn
ACAAcwBpAHoAZQA9ACIAKwAxACIAPgBtAG8AZABpAGYAaQBjAGEAdABpAG8AbgBzADwALwBmAG8A
bgB0AD4APAAvAHMAdAByAG8AbgBnAD4AIABwAGUAcgBtAGkAdAB0AGUAZAAgAGIAeQAgAGEAbgAg
AGUAeAB0AGUAbgBzAGkAbwBuACAAaQBtAHAAbABlAG0AZQBuAHQAZQBkACAAYgB5ACAAdABoAGEA
dAAgAFIAQgByAGkAZABnAGUALgAKAAoAIAAgACAAVABoAGUAIAB3AG8AcgBkACAAbwBmACAARQB4
AHQAZQBuAGQAZQBkACAASABlAGEAZABlAHIAIABGAGwAYQBnAHMAIABpAHMAIABpAGwAbAB1AHMA
dAByAGEAdABlAGQAIABiAGUAbABvAHcAIABhAG4AZAAgAHQAaABlAAoAIAAgACAAbQBlAGEAbgBp
AG4AZwBzACAAbwBmACAAdABoAGUAcwBlACAAYgBpAHQAcwAgAGkAcwAgAGYAdQByAHQAaABlAHIA
IABkAGUAcwBjAHIAaQBiAGUAZAAgAGkAbgAgAHQAaABlACAAbABpAHMAdAAgAGYAbwBsAGwAbwB3
AGkAbgBnACAAdABoAGUACgAgACAAIABmAGkAZwB1AHIAZQAuAAoACgAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAxACAAMQAgADEAIAAxACAAMQAgADEAIAAx
ACAAMQAgADEAIAAxACAAMgAgADIAIAAyACAAMgAgADIAIAAyACAAMgAgADIAIAAyACAAMgAgADMA
IAAzAAoAIAAgACAAIAAwACAAMQAgADIAIAAzACAANAAgADUAIAA2ACAANwAgADgAIAA5ACAAMAAg
ADEAIAAyACAAMwAgADQAIAA1ACAANgAgADcAIAA4ACAAOQAgADAAIAAxACAAMgAgADMAIAA0ACAA
NQAgADYAIAA3ACAAOAAgADkAIAAwACAAMQAKACAAIAAgACsALQArAC0AKwAtACsALQArAC0AKwAt
ACsALQArAC0AKwAtACsALQArAC0AKwAtACsALQArAC0AKwAtACsALQArAC0AKwAtACsALQArAC0A
KwAtACsALQArAC0AKwAtACsALQArAC0AKwAtACsALQArAC0AKwAtACsALQArAC0AKwAKACAAIAAg
AHwAQwByAGkAdAAuAHwAIAAgAEMASABiAEgAIAAgACAAfAAgACAAIABOAEMASABiAEgAIAAgACAA
fABDAFIAUwBWACAAfAAgAE4AQwBSAFMAVgAgAHwAIAAgACAAQwBJAHQARQAgACAAIAAgAHwAIAAg
AE4AQwBJAHQARQAgACAAfAAKACAAIAAgACsALQArAC0AKwAtACsALQArAC0AKwAtACsALQArAC0A
KwAtACsALQArAC0AKwAtACsALQArAC0AKwAtACsALQArAC0AKwAtACsALQArAC0AKwAtACsALQAr
AC0AKwAtACsALQArAC0AKwAtACsALQArAC0AKwAtACsALQArAC0AKwAKACAAIAAgAHwAIAAuAC4A
LgAgAGEAZABkAGkAdABpAG8AbgBhAGwAIABvAHAAdABpAG8AbgBhAGwAIAAzADIALQBiAGkAdAAg
AGEAbABpAGcAbgBlAGQAIAB3AG8AcgBkAHMAIABvAGYAIABlAHgAdABlAG4AcwBpAG8AbgAgACAA
IAAgACAAfAAKACAAIAAgAHwAIAAgACAAIAAgAHAAbwBzAHMAaQBiAGwAeQAgAGkAbgBjAGwAdQBk
AGkAbgBnACAAVABMAFYAIABlAHgAdABlAG4AcwBpAG8AbgBzACAALgAuAC4ACgAKAEkATgBUAEUA
UgBOAEUAVAAtAEQAUgBBAEYAVAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAVABSAEkATABMADoAIABIAGUAYQBkAGUA
cgAgAEUAeAB0AGUAbgBzAGkAbwBuAAoACgAgACAAIAAoAFQAaABlACAAZgBpAHIAcwB0ACAAdAB3
AG8AIABjAHIAaQB0AGkAYwBhAGwAIABzAHUAbQBtAGEAcgB5ACAAYgBpAHQAcwAgAGEAcgBlACAA
YQBzACAAcwBwAGUAYwBpAGYAaQBlAGQAIABpAG4AIABbAFIARgBDADYAMwAyADUAXQAuAAoAIAAg
ACAASQBuACAAdABoAGkAcwAgAGQAbwBjAHUAbQBlAG4AdAAgAGEAbgAgACIAUwAiACwAIABmAG8A
cgAgAFMAdQBtAG0AYQByAHkALAAgAGgAYQBzACAAYgBlAGUAbgAgAGEAZABkAGUAZAAgAGEAdAAg
AHQAaABlACAAZQBuAGQAIABvAGYACgAgACAAIAB0AGgAZQBpAHIAIABhAGMAcgBvAG4AeQBtAHMA
LgApAAoACgAgACAAIABCAGkAdAAoAHMAKQAgACAAIABEAGUAcwBjAHIAaQBwAHQAaQBvAG4ACgAg
ACAAIAAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAKAAoAIAAgACAA
IAAwAC0AMwAgACAAQwByAGkAdAAuADoAIABDAHIAaQB0AGkAYwBhAGwAIABzAHUAbQBtAGEAcgB5
ACAAYgBpAHQAcwAuAAoAIAAgACAAIAAgACAAIAAgACAAMAAgAEMASABiAEgAUwA6ACAAQwByAGkA
dABpAGMAYQBsACAASABvAHAALQBiAHkALQBIAG8AcAAgAGUAeAB0AGUAbgBzAGkAbwBuACgAcwAp
ACAAYQByAGUAIABwAHIAZQBzAGUAbgB0AC4ACgAgACAAIAAgACAAIAAgACAAIAAxACAAQwBJAHQA
RQBTADoAIABDAHIAaQB0AGkAYwBhAGwAIABJAG4AZwByAGUAcwBzAC0AdABvAC0ARQBnAHIAZQBz
AHMAIABlAHgAdABlAG4AcwBpAG8AbgAoAHMAKQAgAGEAcgBlACAAcAByAGUAcwBlAG4AdAAuAAoA
IAAgACAAIAAgACAAIAAgACAAMgAgAEMAUgBTAFYAUwA6ACAAQwByAGkAdABpAGMAYQBsACAAcgBl
AHMAZQByAHYAZQBkACAAZQB4AHQAZQBuAHMAaQBvAG4AKABzACkAIABhAHIAZQAgAHAAcgBlAHMA
ZQBuAHQALgAKAAoAIAAgACAAIAAzAC0ANwAgACAAIABDAEgAYgBIADoAIABDAHIAaQB0AGkAYwBh
AGwAIABIAG8AYgAtAGIAeQAtAEgAbwBwACAAZQB4AHQAZQBuAGQAZQBkACAARgBsAGEAZwAgAGIA
aQB0AHMALgAKACAAIAAgACAAOAAtADEAMwAgACAATgBDAEgAYgBIADoAIABOAG8AbgAtAGMAcgBp
AHQAaQBjAGEAbAAgAEgAbwBwAC0AYgB5AC0ASABvAHAAIABlAHgAdABlAG4AZABlAGQAIABGAGwA
YQBnACAAYgBpAHQAcwAuAAoACgAgACAAIAAgADEANAAtADEANgAgAEMAUgBTAFYAOgAgAEMAcgBp
AHQAaQBjAGEAbAAgAFIAZQBzAGUAcgB2AGUAZAAgAGUAeAB0AGUAbgBkAGUAZAAgAEYAbABhAGcA
IABiAGkAdABzAC4ACgAgACAAIAAgADEANwAtADIAMAAgAE4AQwBSAFMAVgA6ACAATgBvAG4ALQBj
AHIAaQB0AGkAYwBhAGwAIABSAGUAcwBlAHIAdgBlAGQAIABlAHgAdABlAG4AZABlAGQAIABGAGwA
YQBnACAAYgBpAHQAcwAuAAoACgAgACAAIAAgADIAMQAtADIANgAgAEMASQB0AEUAOgAgAEMAcgBp
AHQAaQBjAGEAbAAgAEkAbgBnAHIAZQBzAHMALQB0AG8ALQBFAGcAcgBlAHMAcwAgAGUAeAB0AGUA
bgBkAGUAZAAgAEYAbABhAGcAIABiAGkAdABzAC4ACgAgACAAIAAgADIANwAtADMAMQAgAE4AQwBJ
AHQARQA6ACAATgBvAG4ALQBjAHIAaQB0AGkAYwBhAGwAIABJAG4AZwByAGUAcwBzAC0AdABvAC0A
RQBnAHIAZQBzAHMAIABlAHgAdABlAG4AZABlAGQAIABGAGwAYQBnACAAYgBpAHQAcwAuAAoACgAy
AC4AMwAuADEAIABDAHIAaQB0AGkAYwBhAGwAIABTAHUAbQBtAGEAcgB5ACAAQgBpAHQAcwAKAAoA
IAAgACAAVABoAGUAIAB0AG8AcAAgAHQAaAByAGUAZQAgAGIAaQB0AHMAIABvAGYAIAB0AGgAZQAg
AEUAeAB0AGUAbgBkAGUAZAAgAEgAZQBhAGQAZQByACAARgBsAGEAZwBzACAAYQByAGUAYQAsACAA
YgBpAHQAcwAgADAALAAgADEALAAgAGEAbgBkAAoAIAAgACAAMgAgAGEAYgBvAHYAZQAsACAAYQBy
AGUAIABjAGEAbABsAGUAZAAgAHQAaABlACAAYwByAGkAdABpAGMAYQBsACAAcwB1AG0AbQBhAHIA
eQAgAGIAaQB0AHMALgAgAFQAaABlAHkAIABzAHUAbQBtAGEAcgBpAHoAZQAgAHQAaABlAAoAIAAg
ACAAcAByAGUAcwBlAG4AYwBlACAAbwBmACAAYwByAGkAdABpAGMAYQBsACAAZQB4AHQAZQBuAHMA
aQBvAG4AcwAgAGEAcwAgAGYAbwBsAGwAbwB3AHMAOgAKAAoAIAAgACAAQwBIAGIASABTADoAIABJ
AGYAIAB0AGgAZQAgAEMASABiAEgAUwAgACgAQwByAGkAdABpAGMAYQBsACAASABvAHAAIABiAHkA
IABIAG8AcAAgAFMAdQBtAG0AYQByAHkAKQAgAGIAaQB0ACAAaQBzACAAbwBuAGUALAAgAG8AbgBl
ACAAbwByAAoAIAAgACAAIAAgACAAbQBvAHIAZQAgAGMAcgBpAHQAaQBjAGEAbAAgAGgAbwBwAC0A
YgB5AC0AaABvAHAAIABlAHgAdABlAG4AcwBpAG8AbgBzACAAYQByAGUAIABwAHIAZQBzAGUAbgB0
AC4AIABUAGgAZQBzAGUAIABtAGkAZwBoAHQAIABiAGUACgAgACAAIAAgACAAIABjAHIAaQB0AGkA
YwBhAGwAIABoAG8AcAAtAGIAeQAtAGgAbwBwACAAZQB4AHQAZQBuAGQAZQBkACAAaABlAGEAZABl
AHIAIABmAGwAYQBnAHMAIABvAHIAIABjAHIAaQB0AGkAYwBhAGwAIABoAG8AcAAtAGIAeQAtAGgA
bwBwAAoAIAAgACAAIAAgACAAZQB4AHQAZQBuAHMAaQBvAG4AcwAgAGEAZgB0AGUAcgAgAHQAaABl
ACAAZgBpAHIAcwB0ACAAdwBvAHIAZAAgAGkAbgAgAHQAaABlACAAZQB4AHQAZQBuAHMAaQBvAG4A
cwAgAGEAcgBlAGEALgAgAFQAcgBhAG4AcwBpAHQACgAgACAAIAAgACAAIABSAEIAcgBpAGQAZwBl
AHMAIAB0AGgAYQB0ACAAZABvACAAbgBvAHQAIABzAHUAcABwAG8AcgB0ACAAYQBsAGwAIABvAGYA
IAB0AGgAZQAgAGMAcgBpAHQAaQBjAGEAbAAgAGgAbwBwAC0AYgB5AC0AaABvAHAACgAgACAAIAAg
ACAAIABlAHgAdABlAG4AcwBpAG8AbgBzACAAcAByAGUAcwBlAG4AdAAsACAAZgBvAHIAIABlAHgA
YQBtAHAAbABlACAAYQBuACAAUgBCAHIAaQBkAGcAZQAgAHQAaABhAHQAIABzAHUAcABwAG8AcgB0
AGUAZAAgAG4AbwAKACAAIAAgACAAIAAgAGMAcgBpAHQAaQBjAGEAbAAgAGgAbwBwAC0AYgB5AC0A
aABvAHAAIABlAHgAdABlAG4AcwBpAG8AbgBzACwAIABNAFUAUwBUACAAZAByAG8AcAAgAHQAaABl
ACAAZgByAGEAbQBlAC4AIABJAGYAIAB0AGgAZQAgAEMASABiAEgAUwAKACAAIAAgACAAIAAgAGIA
aQB0ACAAaQBzACAAegBlAHIAbwAsACAAdABoAGUAIABmAHIAYQBtAGUAIABpAHMAIABzAGEAZgBl
ACwAIABmAHIAbwBtACAAdABoAGUAIABwAG8AaQBuAHQAIABvAGYAIAB2AGkAZQB3ACAAbwBmAAoA
IAAgACAAIAAgACAAZQB4AHQAZQBuAHMAaQBvAG4AcwAgAHAAcgBvAGMAZQBzAHMAaQBuAGcALAAg
AGYAbwByACAAYQAgAHQAcgBhAG4AcwBpAHQAIABSAEIAcgBpAGQAZwBlACAAdABvACAAZgBvAHIA
dwBhAHIAZAAsAAoAIAAgACAAIAAgACAAcgBlAGcAYQByAGQAbABlAHMAcwAgAG8AZgAgAHcAaABh
AHQAIABlAHgAdABlAG4AcwBpAG8AbgBzACAAdABoAGEAdAAgAFIAQgByAGkAZABnAGUAIABkAG8A
ZQBzACAAbwByACAAZABvAGUAcwAgAG4AbwB0AAoAIAAgACAAIAAgACAAcwB1AHAAcABvAHIAdAAu
AAoACgAgACAAIABDAEkAdABFAFMAOgAgAEkAZgAgAHQAaABlACAAQwBJAHQARQBTACAAKABDAHIA
aQB0AGkAYwBhAGwAIABJAG4AZwByAGUAcwBzACAAdABvACAARQBnAHIAZQBzAHMAIABTAHUAbQBt
AGEAcgB5ACkAIABiAGkAdAAgAGkAcwAgAGEACgAgACAAIAAgACAAIABvAG4AZQAsACAAbwBuAGUA
IABvAHIAIABtAG8AcgBlACAAYwByAGkAdABpAGMAYQBsACAAaQBuAGcAcgBlAHMAcwAtAHQAbwAt
AGUAZwByAGUAcwBzACAAZQB4AHQAZQBuAHMAaQBvAG4AcwAgAGEAcgBlAAoAIAAgACAAIAAgACAA
cAByAGUAcwBlAG4AdAAuACAAVABoAGUAcwBlACAAbQBpAGcAaAB0ACAAYgBlACAAYwByAGkAdABp
AGMAYQBsACAAaQBuAGcAcgBlAHMAcwAtAHQAbwAtAGUAZwByAGUAcwBzACAAZQB4AHQAZQBuAGQA
ZQBkACAAaABlAGEAZABlAHIACgAgACAAIAAgACAAIABmAGwAYQBnAHMAIABvAHIAIABjAHIAaQB0
AGkAYwBhAGwAIABpAG4AZwByAGUAcwBzAC0AdABvAC0AZQBnAHIAZQBzAHMAIABlAHgAdABlAG4A
cwBpAG8AbgBzACAAYQBmAHQAZQByACAAdABoAGUAIABmAGkAcgBzAHQACgAgACAAIAAgACAAIAB3
AG8AcgBkACAAaQBuACAAdABoAGUAIABlAHgAdABlAG4AcwBpAG8AbgBzACAAYQByAGUAYQAuACAA
IABJAGYAIAB0AGgAZQAgAEMASQB0AEUAUwAgAGIAaQB0ACAAaQBzACAAegBlAHIAbwAsACAAbgBv
ACAAcwB1AGMAaAAKACAAIAAgACAAIAAgAGUAeAB0AGUAbgBzAGkAbwBuAHMAIABhAHIAZQAgAHAA
cgBlAHMAZQBuAHQALgAgACAASQBmACAAZQBpAHQAaABlAHIAIABDAEgAYgBIAFMAIABvAHIAIABD
AEkAdABFAFMAIABpAHMAIABuAG8AbgAtAHoAZQByAG8ALAAKACAAIAAgACAAIAAgAGUAZwByAGUA
cwBzACAAUgBCAHIAaQBkAGcAZQBzACAAdABoAGEAdAAgAGQAbwAgAG4AbwB0ACAAcwB1AHAAcABv
AHIAdAAgAGEAbABsACAAYwByAGkAdABpAGMAYQBsACAAZQB4AHQAZQBuAHMAaQBvAG4AcwAKACAA
IAAgACAAIAAgAHAAcgBlAHMAZQBuAHQALAAgAGYAbwByACAAZQB4AGEAbQBwAGwAZQAgAGEAbgAg
AFIAQgByAGkAZABnAGUAIAB0AGgAYQB0ACAAcwB1AHAAcABvAHIAdABzACAAbgBvACAAYwByAGkA
dABpAGMAYQBsAAoAIAAgACAAIAAgACAAZQB4AHQAZQBuAHMAaQBvAG4AcwAsACAATQBVAFMAVAAg
AGQAcgBvAHAAIAB0AGgAZQAgAGYAcgBhAG0AZQAuACAAIABJAGYAIABiAG8AdABoACAAQwBIAGIA
SABTACAAYQBuAGQAIABDAEkAdABFAFMAIABhAHIAZQAKAAoASQBOAFQARQBSAE4ARQBUAC0ARABS
AEEARgBUACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIABUAFIASQBMAEwAOgAgAEgAZQBhAGQAZQByACAARQB4AHQAZQBu
AHMAaQBvAG4ACgAKACAAIAAgACAAIAAgAHoAZQByAG8ALAAgAHQAaABlACAAZgByAGEAbQBlACAA
aQBzACAAcwBhAGYAZQAsACAAZgByAG8AbQAgAHQAaABlACAAcABvAGkAbgB0ACAAbwBmACAAdgBp
AGUAdwAgAG8AZgAgAGUAeAB0AGUAbgBzAGkAbwBuAHMALAAgAGYAbwByAAoAIAAgACAAIAAgACAA
YQBuACAAZQBnAHIAZQBzAHMAIABSAEIAcgBpAGQAZwBlACAAdABvACAAcAByAG8AYwBlAHMAcwAs
ACAAcgBlAGcAYQByAGQAbABlAHMAcwAgAG8AZgAgAHcAaABhAHQAIABlAHgAdABlAG4AcwBpAG8A
bgBzACAAdABoAGEAdAAKACAAIAAgACAAIAAgAFIAQgByAGkAZABnAGUAIABkAG8AZQBzACAAbwBy
ACAAZABvAGUAcwAgAG4AbwB0ACAAcwB1AHAAcABvAHIAdAAuAAoACgAgACAAIABDAFIAUwBWAFMA
OgAgAEkAZgAgAHQAaABlACAAQwBSAFMAVgBTACAAKABDAHIAaQB0AGkAYwBhAGwAIABSAGUAcwBl
AHIAdgBlAGQAIABTAHUAbQBtAGEAcgB5ACkAIABiAGkAdAAgAGkAcwAgAGEAIABvAG4AZQAsACAA
bwBuAGUAIABvAHIACgAgACAAIAAgACAAIABtAG8AcgBlACAAYwByAGkAdABpAGMAYQBsACAAZQB4
AHQAZQBuAHMAaQBvAG4AcwAgAGEAcgBlACAAcAByAGUAcwBlAG4AdAAgAHQAaABhAHQAIABhAHIA
ZQAgAHIAZQBzAGUAcgB2AGUAZAAgAHQAbwAgAGEAcABwAGwAeQAgAHQAbwAKACAAIAAgACAAIAAg
AGEAIABjAGwAYQBzAHMAIABvAGYAIABSAEIAcgBpAGQAZwBlAHMAIAB0AG8AIABiAGUAIABzAHAA
ZQBjAGkAZgBpAGUAZAAgAGkAbgAgAHQAaABlACAAZgB1AHQAdQByAGUALAAgAGYAbwByACAAZQB4
AGEAbQBwAGwAZQAKACAAIAAgACAAIAAgAGIAbwByAGQAZQByACAAUgBCAHIAaQBkAGcAZQBzACAA
aQBuACAAYQAgAFQAUgBJAEwATAAgAGMAYQBtAHAAdQBzACAAZQB4AHQAZQBuAGQAZQBkACAAdABv
ACAAcwB1AHAAcABvAHIAdAAgAG0AdQBsAHQAaQAtAGwAZQB2AGUAbAAKACAAIAAgACAAIAAgAEkA
UwAtAEkAUwAuACAAVABoAGkAcwAgAGMAbABhAHMAcwAgAHcAaQBsAGwAIABiAGUAIABhACAAcwB1
AGIAcwBlAHQAIABvAGYAIAB0AHIAYQBuAHMAaQB0ACAAUgBCAHIAaQBkAGcAZQBzAC4AIABSAEIA
cgBpAGQAZwBlAHMACgAgACAAIAAgACAAIABpAG4AIAB0AGgAaQBzACAAYwBsAGEAcwBzACAATQBV
AFMAVAAgAGQAcgBvAHAAIABmAHIAYQBtAGUAcwAgAHcAaQB0AGgAIAB0AGgAZQAgAEMAUgBTAFYA
UwAgAGIAaQB0ACAAcwBlAHQAIAB1AG4AbABlAHMAcwAgAHQAaABlAHkACgAgACAAIAAgACAAIABp
AG0AcABsAGUAbQBlAG4AdAAgAGEAbABsACAAYwByAGkAdABpAGMAYQBsACAAaABvAHAALQBiAHkA
LQBoAG8AcAAgAGEAbgBkACAAYQBsAGwAIABjAHIAaQB0AGkAYwBhAGwAIAByAGUAcwBlAHIAdgBl
AGQACgAgACAAIAAgACAAIABlAHgAdABlAG4AcwBpAG8AbgBzACAAcAByAGUAcwBlAG4AdAAgAGkA
bgAgAHQAaABlACAAZgByAGEAbQBlAC4ACgAKACAAIAAgAFQAaABlACAAYwByAGkAdABpAGMAYQBs
ACAAcwB1AG0AbQBhAHIAeQAgAGIAaQB0AHMAIABlAG4AYQBiAGwAZQAgAHMAaQBtAHAAbABlACAA
YQBuAGQAIABlAGYAZgBpAGMAaQBlAG4AdAAgAHAAcgBvAGMAZQBzAHMAaQBuAGcAIABvAGYACgAg
ACAAIABUAFIASQBMAEwAIABEAGEAdABhACAAZgByAGEAbQBlAHMAIABiAHkAIABlAGcAcgBlAHMA
cwAgAFIAQgByAGkAZABnAGUAcwAgAHQAaABhAHQAIABzAHUAcABwAG8AcgB0ACAAbgBvACAAYwBy
AGkAdABpAGMAYQBsAAoAIAAgACAAZQB4AHQAZQBuAHMAaQBvAG4AcwAsACAAYgB5ACAAdAByAGEA
bgBzAGkAdAAgAFIAQgByAGkAZABnAGUAcwAgAHQAaABhAHQAIABzAHUAcABwAG8AcgB0ACAAbgBv
ACAAYwByAGkAdABpAGMAYQBsACAAaABvAHAALQBiAHkALQBoAG8AcAAKACAAIAAgAGUAeAB0AGUA
bgBzAGkAbwBuAHMALAAgAGEAbgBkACAAYgB5ACAAUgBCAHIAaQBkAGcAZQBzACAAaQBuACAAdABo
AGUAIAByAGUAcwBlAHIAdgBlAGQAIABjAGwAYQBzAHMAIAB0AGgAYQB0ACAAcwB1AHAAcABvAHIA
dAAgAG4AbwAKACAAIAAgAGMAcgBpAHQAaQBjAGEAbAAgAGgAbwBwAC0AYgB5AC0AaABvAHAAIABv
AHIAIAByAGUAcwBlAHIAdgBlAGQAIABlAHgAdABlAG4AcwBpAG8AbgBzAC4AIABTAHUAYwBoACAA
UgBCAHIAaQBkAGcAZQBzACAAbgBlAGUAZAAgAG8AbgBsAHkACgAgACAAIABjAGgAZQBjAGsAIAB3
AGgAZQB0AGgAZQByACAATwBwAC0ATABlAG4AZwB0AGgAIABpAHMAIABuAG8AbgAtAHoAZQByAG8A
IABhAG4AZAAsACAAaQBmACAAaQB0ACAAaQBzACwAIAB0AGgAZQAgAHQAbwBwACAAbwBuAGUALAAg
AHQAdwBvACwACgAgACAAIABvAHIAIAB0AGgAcgBlAGUAIABiAGkAdABzACAAagB1AHMAdAAgAGEA
ZgB0AGUAcgAgAHQAaABlACAAZgBpAHgAZQBkACAAcABvAHIAdABpAG8AbgAgAG8AZgAgAHQAaABl
ACAAVABSAEkATABMACAASABlAGEAZABlAHIALgAgAEIAYQBzAGUAZAAKACAAIAAgAG8AbgAgAHQA
aABvAHMAZQAgAHQAaAByAGUAZQAgAGIAaQB0AHMALAAgAHMAdQBjAGgAIABSAEIAcgBpAGQAZwBl
AHMAIABjAGEAbgAgAGQAZQBjAGkAZABlACAAdwBoAGUAdABoAGUAcgAgAHQAbwAgAGQAaQBzAGMA
YQByAGQAIABvAHIACgAgACAAIABmAG8AcgB3AGEAcgBkACAALwAgAHAAcgBvAGMAZQBzAHMAIAB0
AGgAZQAgAGYAcgBhAG0AZQAuAAoACgAyAC4ANAAgAEMAbwBuAGYAbABpAGMAdAAgAG8AZgAgAEUA
eAB0AGUAbgBzAGkAbwBuAHMACgAKACAAIAAgAEQAZQBmAGkAbgBpAG4AZwAgAFQAUgBJAEwATAAg
AGUAeAB0AGUAbgBzAGkAbwBuAHMAIABpAG4AYwBsAHUAZABpAG4AZwAgAEUAeAB0AGUAbgBkAGUA
ZAAgAEgAZQBhAGQAZQByACAARgBsAGEAZwBzACAAdABoAGEAdAAKACAAIAAgAGMAbwBuAGYAbABp
AGMAdAAgAHcAaQB0AGgAIABlAGEAYwBoACAAbwB0AGgAZQByACAAdwBvAHUAbABkACAAYgBlACAA
dQBuAGQAZQBzAGkAcgBhAGIAbABlAC4AIABTAGgAbwB1AGwAZAAgAGMAbwBuAGYAbABpAGMAdABp
AG4AZwAKACAAIAAgAGUAeAB0AGUAbgBzAGkAbwBuAHMAIABhAHAAcABlAGEAcgAgAGkAbgAgAHQA
aABlACAAcwBhAG0AZQAgAHAAYQBjAGsAZQB0ACwAIAB0AGgAZQAgAHIAZQBzAHUAbAB0AHMAIAB3
AG8AdQBsAGQAIABiAGUACgAgACAAIAB1AG4AcAByAGUAZABpAGMAdABhAGIAbABlACwAIABpAGYA
IABkAGkAZgBmAGUAcgBlAG4AdAAgAGkAbQBwAGwAZQBtAGUAbgB0AGEAdABpAG8AbgBzACAAcABy
AG8AYwBlAHMAcwBlAGQAIAB0AGgAZQBtACAAaQBuAAoAIAAgACAAZABpAGYAZgBlAHIAZQBuAHQA
IABvAHIAZABlAHIAcwAuACAAVwBoAGkAbABlACAAcgB1AGwAZQBzACAAYwBvAHUAbABkACAAYgBl
ACAAZABlAGYAaQBuAGUAZAAgAHQAbwAgAHMAcABlAGMAaQBmAHkAIABoAG8AdwAgAHQAbwAKACAA
IAAgAHAAcgBlAGQAaQBjAHQAYQBiAGwAeQAgAHAAcgBvAGMAZQBzAHMAIABjAG8AbgBmAGwAaQBj
AHQAaQBuAGcAIABlAHgAdABlAG4AcwBpAG8AbgBzACwAIABzAHUAYwBoACAAcgB1AGwAZQBzACAA
dwBvAHUAbABkACAAYQBsAHMAbwAKACAAIAAgAGwAaQBtAGkAdAAgAGkAbQBwAGwAZQBtAGUAbgB0
AGEAdABpAG8AbgAgAGYAbABlAHgAaQBiAGkAbABpAHQAeQAgAGEAbgBkACAAYwBvAHUAbABkACAA
aQBtAHAAbwBzAGUAIABzAHUAYgBzAHQAYQBuAHQAaQBhAGwACgAgACAAIABwAHIAbwBjAGUAcwBz
AGkAbgBnACAAYgB1AHIAZABlAG4AcwAuAAoACgAgACAAIABDAG8AbgBmAGwAaQBjAHQAaQBuAGcA
IABlAHgAdABlAG4AcwBpAG8AbgBzACAAUwBIAE8AVQBMAEQAIABOAE8AVAAgAGIAZQAgAGQAZQBm
AGkAbgBlAGQALAAgAGIAdQB0ACAAaQBmACAAdABoAGUAeQAgAGEAcgBlACwACgAgACAAIABjAGEA
cgBlAGYAdQBsACAAdABoAG8AdQBnAGgAdAAgAHMAaABvAHUAbABkACAAYgBlACAAZwBpAHYAZQBu
ACAAYQBzACAAdABvACAAdwBoAGUAdABoAGUAcgAgAGEAbgBkACAAaABvAHcAIAB0AG8AIABzAHAA
ZQBjAGkAZgB5ACAAdABoAGUACgAgACAAIABoAGEAbgBkAGwAaQBuAGcAIABvAGYAIABjAG8AbgBm
AGwAaQBjAHQAaQBuAGcAIABlAHgAdABlAG4AcwBpAG8AbgBzAC4ACgAKAEkATgBUAEUAUgBOAEUA
VAAtAEQAUgBBAEYAVAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAVABSAEkATABMADoAIABIAGUAYQBkAGUAcgAgAEUA
eAB0AGUAbgBzAGkAbwBuAAoACgAzAC4AIABTAHAAZQBjAGkAZgBpAGMAIABFAHgAdABlAG4AZABl
AGQAIABIAGUAYQBkAGUAcgAgAEYAbABhAGcAcwAKAAoAIAAgACAAVABoAGUAIAB0AGEAYgBsAGUA
IABiAGUAbABvAHcAIABzAGgAbwB3AHMAIAB0AGgAZQAgAHMAdABhAHQAZQAgAG8AZgAgAFQAUgBJ
AEwATAAgAEgAZQBhAGQAZQByACAAZQB4AHQAZQBuAGQAZQBkACAAZgBsAGEAZwAKACAAIAAgAGEA
cwBzAGkAZwBuAG0AZQBuAHQAcwAuACAAUwBlAGUAIABTAGUAYwB0AGkAbwBuACAAPABzAHQAcgBp
AGsAZQA+ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAcgBlAGQAJwAgAHMAaQB6AGUAPQAiACsA
MQAiAD4ANgA8AC8AZgBvAG4AdAA+ADwALwBzAHQAcgBpAGsAZQA+ACAAPABzAHQAcgBvAG4AZwA+
ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcAIABzAGkAegBlAD0AIgArADEA
IgA+ADUAPAAvAGYAbwBuAHQAPgA8AC8AcwB0AHIAbwBuAGcAPgAgAGYAbwByACAASQBBAE4AQQAg
AEMAbwBuAHMAaQBkAGUAcgBhAHQAaQBvAG4AcwAuAAoACgAgACAAIAAgACAAIAAgAEIAaQB0AHMA
IAAgACAAIABQAHUAcgBwAG8AcwBlACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgAFMAZQBjAHQAaQBvAG4ACgAgACAAIAAgACAAIAAtAC0A
LQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAt
AC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAtAC0ALQAKACAAIAAgACAA
IAAgACAAIAAwAC0AMgAgACAAIAAgAEMAcgBpAHQAaQBjAGEAbAAgAFMAdQBtAG0AYQByAHkAIABC
AGkAdABzACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAMgAuADMALgAxAAoAIAAgACAA
IAAgACAAIAAgADMALQA2ACAAIAAgACAAYQB2AGEAaQBsAGEAYgBsAGUAIABjAHIAaQB0AGkAYwBh
AGwAIABoAG8AcAAtAGIAeQAtAGgAbwBwACAAZgBsAGEAZwBzAAoAIAAgACAAIAAgACAAIAAgADcA
IAAgACAAIAAgACAAQwByAGkAdABpAGMAYQBsACAAQwBoAGEAbgBuAGUAbAAgAEEAbABlAHIAdAAg
AEYAbABhAGcAIAAgACAAIAAgACAAIAAgACAAIAAzAC4AMQAKACAAIAAgACAAIAAgACAAIAA4ACAA
IAAgACAAIAAgAE4AbwBuAC0AYwByAGkAdABpAGMAYQBsACAAQwBoAGEAbgBuAGUAbAAgAEEAbABl
AHIAdAAgAEYAbABhAGcAIAAgACAAIAAgACAAMwAuADEACgAgACAAIAAgACAAIAAgACAAOQAtADEA
MwAgACAAIABhAHYAYQBpAGwAYQBiAGwAZQAgAG4AbwBuAC0AYwByAGkAdABpAGMAYQBsACAAaABv
AHAALQBiAHkALQBoAG8AcAAgAGYAbABhAGcAcwAKACAAIAAgACAAIAAgACAAMQA0AC0AMQA2ACAA
IAAgAGEAdgBhAGkAbABhAGIAbABlACAAYwByAGkAdABpAGMAYQBsACAAcgBlAHMAZQByAHYAZQBk
ACAAZgBsAGEAZwBzAAoAIAAgACAAIAAgACAAIAAxADcALQAyADAAIAAgACAAYQB2AGEAaQBsAGEA
YgBsAGUAIABuAG8AbgAtAGMAcgBpAHQAaQBjAGEAbAAgAHIAZQBzAGUAcgB2AGUAZAAgAGYAbABh
AGcAcwAKACAAIAAgACAAIAAgACAAMgAxAC0AMgA2ACAAIAAgAGEAdgBhAGkAbABhAGIAbABlACAA
YwByAGkAdABpAGMAYQBsACAAaQBuAGcAcgBlAHMAcwAtAHQAbwAtAGUAZwByAGUAcwBzACAAZgBs
AGEAZwBzAAoAIAAgACAAIAAgACAAIAAyADcALQAzADEAIAAgACAAYQB2AGEAaQBsAGEAYgBsAGUA
IABuAG8AbgAtAGMAcgBpAHQAaQBjAGEAbAAgAGkAbgBnAHIAZQBzAHMALQB0AG8ALQBlAGcAcgBl
AHMAcwAgAGYAbABhAGcAcwAKAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgAFQAYQBiAGwAZQAgADEALgAgAEUAeAB0AGUAbgBkAGUAZAAgAEgAZQBhAGQAZQByACAARgBs
AGEAZwBzACAAQQByAGUAYQAKAAoAMwAuADEAIABUAGgAZQAgAFIAQgByAGkAZABnAGUAIABDAGgA
YQBuAG4AZQBsACAAQQBsAGUAcgB0ACAARQB4AHQAZQBuAGQAZQBkACAARgBsAGEAZwBzAAoACgAg
ACAAIABUAGgAZQAgAFIAQgByAGkAZABnAGUAIABDAGgAYQBuAG4AZQBsACAAQQBsAGUAcgB0ACAA
RQB4AHQAZQBuAGQAZQBkACAARgBsAGEAZwBzACAAaQBuAGQAaQBjAGEAdABlAHMAIAB0AGgAYQB0
ACAAdABoAGUAIABmAHIAYQBtAGUAIABpAHMACgAgACAAIABhAG4AIABSAEIAcgBpAGQAZwBlACAA
QwBoAGEAbgBuAGUAbAAgAGYAcgBhAG0AZQAgAFsAQwBoAGEAbgBuAGUAbABdACAAdABoAGEAdAAg
AHIAZQBxAHUAZQBzAHQAcwAgAHAAcgBvAGMAZQBzAHMAaQBuAGcAIABhAHQAIABlAGEAYwBoAAoA
IAAgACAAaABvAHAALgAKAAoAIAAgACAASQBmACAAdABoAGUAIABjAHIAaQB0AGkAYwBhAGwAIABD
AGgAYQBuAG4AZQBsACAAQQBsAGUAcgB0ACAAZgBsAGEAZwAgACgAYgBpAHQAIAA3ACkAIABpAHMA
IABhACAAbwBuAGUAIABhAG4AZAAgAHQAaABlACAAUgBCAHIAaQBkAGcAZQAKACAAIAAgAGQAbwBl
AHMAIABuAG8AdAAgAGkAbQBwAGwAZQBtAGUAbgB0ACAAdABoAGUAIABSAEIAcgBpAGQAZwBlACAA
QwBoAGEAbgBuAGUAbAAgAGYAZQBhAHQAdQByAGUAIABvAHIAIAB0AGgAZQAgAHAAYQByAHQAaQBj
AHUAbABhAHIACgAgACAAIABSAEIAcgBpAGQAZwBlACAAQwBoAGEAbgBuAGUAbAAgAHAAcgBvAHQA
bwBjAG8AbAAgAGkAbgB2AG8AbAB2AGUAZAAgAFsAQwBoAGEAbgBuAGUAbABdACAAbwByACAAdABo
AGUAIABmAHIAYQBtAGUAIABkAG8AZQBzACAAbgBvAHQACgAgACAAIABhAGMAdAB1AGEAbABsAHkA
IABhAHAAcABlAGEAcgAgAHQAbwAgAGIAZQAgAGEAbgAgAFIAQgByAGkAZABnAGUAIABDAGgAYQBu
AG4AZQBsACAAbQBlAHMAcwBhAGcAZQAsACAAdABoAGUAbgAgAHQAaABlACAAZgByAGEAbQBlACAA
aQBzAAoAIAAgACAAZABpAHMAYwBhAHIAZABlAGQALgAgAFQAaABpAHMAIABwAGUAcgBtAGkAdABz
ACAAaQBtAHAAbABlAG0AZQBuAHQAYQB0AGkAbwBuACwAIABmAG8AcgAgAGUAeABhAG0AcABsAGUA
LAAgAG8AZgAgAGEAIABDAGgAYQBuAG4AZQBsAAoAIAAgACAAbQBlAHMAcwBhAGcAZQAgAHIAZQBx
AHUAaQByAGkAbgBnACAAcwB0AHIAaQBjAHQAIABzAG8AdQByAGMAZQAgAHIAbwB1AHQAaQBuAGcA
IABvAHIAIAB0AGgAZQAgAGwAaQBrAGUALAAgAHcAaQB0AGgAIABhAHMAcwB1AHIAYQBuAGMAZQAK
ACAAIAAgAHQAaABhAHQAIABpAHQAIAB3AGkAbABsACAAYgBlACAAZABpAHMAYwBhAHIAZABlAGQA
IAByAGEAdABoAGUAcgAgAHQAaABhAG4AIABkAGUAdgBpAGEAdABlACAAZgByAG8AbQAgAHQAaABl
ACAAZABpAHIAZQBjAHQAZQBkACAAcABhAHQAaAAuAAoACgAgACAAIABJAGYAIAB0AGgAZQAgAGYA
cgBhAG0AZQAgAGkAcwAgAG4AbwB0ACAAZABpAHMAYwBhAHIAZABlAGQAIABhAHMAIABhAGIAbwB2
AGUAIAB0AGgAZQBuACAAdABoAGUAIABwAHIAZQBzAGUAbgBjAGUAIABvAGYAIABlAGkAdABoAGUA
cgAKACAAIAAgAHQAaABlACAAQwByAGkAdABpAGMAYQBsACAAbwByACAATgBvAG4ALQBjAHIAaQB0
AGkAYwBhAGwAIABoAG8AcAAtAGIAeQAtAGgAbwBwACAAQwBoAGEAbgBuAGUAbAAgAEEAbABlAHIA
dAAgAGYAbABhAGcAIABhAGwAZQByAHQAcwAKACAAIAAgAHQAcgBhAG4AcwBpAHQAIABSAEIAcgBp
AGQAZwBlAHMAIAB0AG8AIAB0AGgAZQAgAHAAcgBlAHMAZQBuAGMAZQAgAG8AZgAgAGEAbgAgAFIA
QgByAGkAZABnAGUAIABDAGgAYQBuAG4AZQBsACAAbQBlAHMAcwBhAGcAZQAKACAAIAAgAFsAQwBo
AGEAbgBuAGUAbABdACAAdABoAGEAdAAgAG0AYQB5ACAAcgBlAHEAdQBpAHIAZQAgAHMAcABlAGMA
aQBhAGwAIABoAGEAbgBkAGwAaQBuAGcALgAgAFQAaABlACAAbgBvAG4ALQBjAHIAaQB0AGkAYwBh
AGwAIABhAGwAZQByAHQACgAgACAAIABmAGwAYQBnACAAcwB1AHAAcABvAHIAdABzACwAIABmAG8A
cgAgAGUAeABhAG0AcABsAGUALAAgAGEAbgAgAFIAQgByAGkAZABnAGUAIABDAGgAYQBuAG4AZQBs
ACAAcAByAG8AdABvAGMAbwBsACAAbQBlAHMAcwBhAGcAZQAKACAAIAAgAGkAbgBjAGwAdQBkAGkA
bgBnACAAYQAgACIAcgBlAGMAbwByAGQAIAByAG8AdQB0AGUAIgAgAGYAdQBuAGMAdABpAG8AbgAg
AHcAaABlAHIAZQAgAG4AbwB0ACAAcgBlAGMAbwByAGQAaQBuAGcAIAB0AHIAYQBuAHMAaQB0AAoA
IAAgACAAUgBCAHIAaQBkAGcAZQBzACAAdABoAGEAdAAgAGQAbwAgAG4AbwB0ACAAcwB1AHAAcABv
AHIAdAAgAHQAaABpAHMAIABmAHUAbgBjAHQAaQBvAG4AIABpAHMAIABhAGMAYwBlAHAAdABhAGIA
bABlAC4ACgAKAEkATgBUAEUAUgBOAEUAVAAtAEQAUgBBAEYAVAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAVABSAEkA
TABMADoAIABIAGUAYQBkAGUAcgAgAEUAeAB0AGUAbgBzAGkAbwBuAAoACgA0AC4AIABBAGQAZABp
AHQAaQBvAG4AcwAgAHQAbwAgAEkAUwAtAEkAUwAKAAoAIAAgACAAUgBCAHIAaQBkAGcAZQBzACAA
dQBzAGUAIABJAFMALQBJAFMAIABMAFMAUAAgAFAARABVAHMAIAB0AG8AIABpAG4AZgBvAHIAbQAg
AG8AdABoAGUAcgAgAFIAQgByAGkAZABnAGUAcwAgAHcAaABpAGMAaAAgAEUAeAB0AGUAbgBkAGUA
ZAAKACAAIAAgAEgAZQBhAGQAZQByACAARgBsAGEAZwBzACAAdABoAGUAeQAgAHMAdQBwAHAAbwBy
AHQALgAgAFQAaABlACAASQBTAC0ASQBTACAAUABEAFUAKABzACkALAAgAFQATABWACgAcwApACwA
IABvAHIAIABzAHUAYgAtAFQATABWACgAcwApAAoAIAAgACAAdQBzAGUAZAAgAHQAbwAgAGUAbgBj
AG8AZABlACAAYQBuAGQAIABhAGQAdgBlAHIAdABpAHMAZQAgAHQAaABpAHMAIABpAG4AZgBvAHIA
bQBhAHQAaQBvAG4AIABhAHIAZQAgAHMAcABlAGMAaQBmAGkAZQBkACAAaQBuACAAYQAKACAAIAAg
AHMAZQBwAGEAcgBhAHQAZQAgAGQAbwBjAHUAbQBlAG4AdAAgAFsAUgBGAEMANgAzADIANgBiAGkA
cwBdAC4ACgAKADUALgAgAEkAQQBOAEEAIABDAG8AbgBzAGkAZABlAHIAYQB0AGkAbwBuAHMACgAK
ACAAIAAgAEkAQQBOAEEAIABpAHMAIAByAGUAcQB1AGUAcwB0AGUAZAAgAHQAbwAgAGMAcgBlAGEA
dABlACAAYQAgAHMAdQBiAHIAZQBnAGkAcwB0AHIAeQAgAHcAaQB0AGgAaQBuACAAdABoAGUAIABU
AFIASQBMAEwAIABQAGEAcgBhAG0AZQB0AGUAcgBzAAoAIAAgACAAcgBlAGcAaQBzAHQAcgB5ADoA
IABUAGgAZQAgACIAVABSAEkATABMACAARQB4AHQAZQBuAGQAZQBkACAASABlAGEAZABlAHIAIABG
AGwAYQBnAHMAIgAgAHMAdQBiAHIAZQBnAGkAcwB0AHIAeQAsACAAdABoAGEAdAAgAGkAcwAKACAA
IAAgAGkAbgBpAHQAaQBhAGwAbAB5ACAAcABvAHAAdQBsAGEAdABlAGQAIABhAHMAIABzAHAAZQBj
AGkAZgBpAGUAZAAgAGkAbgAgAFQAYQBiAGwAZQAgADEAIABpAG4AIABTAGUAYwB0AGkAbwBuACAA
MwAuACAAUgBlAGYAZQByAGUAbgBjAGUAcwAKACAAIAAgAGkAbgAgAHQAaABhAHQAIAB0AGEAYgBs
AGUAIAB0AG8AIABzAGUAYwB0AGkAbwBuAHMAIABvAGYAIAB0AGgAaQBzACAAZABvAGMAdQBtAGUA
bgB0ACAAYQByAGUAIAB0AG8AIABiAGUAIAByAGUAcABsAGEAYwBlAGQAIABpAG4AIAB0AGgAZQAK
ACAAIAAgAEkAQQBOAEEAIABzAHUAYgByAGUAZwBpAHMAdAByAHkAIABiAHkAIAByAGUAZgBlAHIA
ZQBuAGMAZQBzACAAdABvACAAdABoAGkAcwAgAGQAbwBjAHUAbQBlAG4AdAAgAGEAcwAgAGEAbgAg
AFIARgBDAC4ACgAKACAAIAAgAE4AZQB3ACAAVABSAEkATABMACAARQB4AHQAZQBuAGQAZQBkACAA
SABlAGEAZABlAHIAIABGAGwAYQBnAHMAIABhAHIAZQAgAGEAbABsAG8AYwBhAHQAZQBkACAAYgB5
ACAAUwB0AGEAbgBkAGEAcgBkAHMAIABBAGMAdABpAG8AbgAKACAAIAAgAFsAUgBGAEMANQAyADIA
NgBdACAAYQBzACAAbQBvAGQAaQBmAGkAZQBkACAAYgB5ACAAWwBSAEYAQwA0ADAAMgAwAF0ALgAK
AAoASQBOAFQARQBSAE4ARQBUAC0ARABSAEEARgBUACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABUAFIASQBMAEwAOgAg
AEgAZQBhAGQAZQByACAARQB4AHQAZQBuAHMAaQBvAG4ACgAKADYALgAgAFMAZQBjAHUAcgBpAHQA
eQAgAEMAbwBuAHMAaQBkAGUAcgBhAHQAaQBvAG4AcwAKAAoAIAAgACAARgBvAHIAIABnAGUAbgBl
AHIAYQBsACAAVABSAEkATABMACAAcAByAG8AdABvAGMAbwBsACAAcwBlAGMAdQByAGkAdAB5ACAA
YwBvAG4AcwBpAGQAZQByAGEAdABpAG8AbgBzACwAIABzAGUAZQAgAFsAUgBGAEMANgAzADIANQBd
AC4ACgAKACAAIAAgAEYAbwByACAAcwBlAGMAdQByAGkAdAB5ACAAYwBvAG4AcwBpAGQAZQByAGEA
dABpAG8AbgBzACAAcgBlAGwAYQB0AGUAZAAgAHQAbwAgAGUAeAB0AGUAbgBkAGUAZAAgAGgAZQBh
AGQAZQByACAAZgBsAGEAZwBzACwAIABzAGUAZQAgAHQAaABlAAoAIAAgACAAZABvAGMAdQBtAGUA
bgB0ACAAdwBoAGUAcgBlACAAdABoAGUAIABmAGwAYQBnACAAaQBzACAAcwBwAGUAYwBpAGYAaQBl
AGQALgAKAAoAIAAgACAASQB0ACAAaQBzACAAaQBtAHAAbwByAHQAYQBuAHQAIAB0AGgAYQB0ACAA
dABoAGUAIABjAHIAaQB0AGkAYwBhAGwAIABzAHUAbQBtAGEAcgB5ACAAYgBpAHQAcwAgAGkAbgAg
AHQAaABlACAARQB4AHQAZQBuAGQAZQBkACAASABlAGEAZABlAHIACgAgACAAIABGAGwAYQBnAHMA
IAB3AG8AcgBkACAAYgBlACAAcwBlAHQAIABwAHIAbwBwAGUAcgBsAHkALgAgAEkAZgAgAHMAZQB0
ACAAdwBoAGUAbgAgAGMAcgBpAHQAaQBjAGEAbAAgAGUAeAB0AGUAbgBzAGkAbwBuAHMAIABvAGYA
IAB0AGgAZQAKACAAIAAgAGEAcABwAHIAbwBwAHIAaQBhAHQAZQAgAGMAYQB0AGUAZwBvAHIAeQAg
AGEAcgBlACAAbgBvAHQAIABwAHIAZQBzAGUAbgB0ACwAIABmAHIAYQBtAGUAcwAgAG0AYQB5ACAA
YgBlACAAdQBuAG4AZQBjAGUAcwBzAGEAcgBpAGwAeQAKACAAIAAgAGQAaQBzAGMAYQByAGQAZQBk
AC4AIABJAGYAIABuAG8AdAAgAHMAZQB0ACAAdwBoAGUAbgAgAGMAcgBpAHQAaQBjAGEAbAAgAGUA
eAB0AGUAbgBzAGkAbwBuAHMAIABhAHIAZQAgAHAAcgBlAHMAZQBuAHQALAAgAGYAcgBhAG0AZQBz
AAoAIAAgACAAbQBhAHkAIABiAGUAIABtAGkAcwBoAGEAbgBkAGwAZQBkACAAbwByACAAYwBvAHIA
cgB1AHAAdABlAGQAIABhAG4AZAAgAGkAbgB0AGUAbgBkAGUAZAAgAHMAZQBjAHUAcgBpAHQAeQAg
AHAAbwBsAGkAYwBpAGUAcwAgAG0AYQB5ACAAYgBlAAoAIAAgACAAdgBpAG8AbABhAHQAZQBkAC4A
CgAKACAAIAAgAFQAaABlACAAUgBCAHIAaQBkAGcAZQAgAEMAaABhAG4AbgBlAGwAIABBAGwAZQBy
AHQAIABlAHgAdABlAG4AZABlAGQAIABmAGwAYQBnAHMAIABoAGEAdgBlACAAdABoAGUAIABmAG8A
bABsAG8AdwBpAG4AZwAgAHMAZQBjAHUAcgBpAHQAeQAKACAAIAAgAGMAbwBuAHMAaQBkAGUAcgBh
AHQAaQBvAG4AcwAuACAASQBtAHAAbABlAG0AZQBuAHQAYQB0AGkAbwBuAHMAIABzAGgAbwB1AGwA
ZAAgAGsAZQBlAHAAIABpAG4AIABtAGkAbgBkACAAdABoAGEAdAAgAHQAaABlAHkAIABtAGkAZwBo
AHQACgAgACAAIABiAGUAIABlAHIAcgBvAG4AZQBvAHUAcwBsAHkAIABzAGUAdAAgAGkAbgAgAGEA
IABmAHIAYQBtAGUALgAgAEkAZgAgAGUAaQB0AGgAZQByACAAUgBCAHIAaQBkAGcAZQAgAEMAaABh
AG4AbgBlAGwAIABBAGwAZQByAHQAIABmAGwAYQBnAAoAIAAgACAAaQBzACAAZgBvAHUAbgBkACAA
cwBlAHQAIABpAG4AIABhACAAZgByAGEAbQBlACAAdABoAGEAdAAgAGkAcwAgAG4AbwB0ACAAYQBu
ACAAUgBCAHIAaQBkAGcAZQAgAEMAaABhAG4AbgBlAGwAIABtAGUAcwBzAGEAZwBlAAoAIAAgACAA
WwBDAGgAYQBuAG4AZQBsAF0ALAAgAHQAaABlACAAZgBsAGEAZwAgAE0AQQBZACAAYgBlACAAYwBs
AGUAYQByAGUAZAAgAGEAbgBkACAAcwBoAG8AdQBsAGQAIABoAGEAdgBlACAAbgBvACAAZQBmAGYA
ZQBjAHQAIABlAHgAYwBlAHAAdAAsAAoAIAAgACAAcABvAHMAcwBpAGIAbAB5ACwAIABkAGUAbABh
AHkAaQBuAGcAIABwAHIAbwBjAGUAcwBzAGkAbgBnACAAbwBmACAAdABoAGUAIABmAHIAYQBtAGUA
LgAgAEkAZgAgAGUAaQB0AGgAZQByACAAQwBoAGEAbgBuAGUAbAAgAEEAbABlAHIAdAAKACAAIAAg
AGYAbABhAGcAIABpAHMAIABlAHIAcgBvAG4AZQBvAHUAcwBsAHkAIABvAG0AaQB0AHQAZQBkACAA
ZgByAG8AbQAgAGEAIABmAHIAYQBtAGUALAAgAGQAZQBzAGkAcgBlAGQAIABwAGUAcgAgAGgAbwBw
ACAAcAByAG8AYwBlAHMAcwBpAG4AZwAKACAAIAAgAGYAbwByACAAdABoAGUAIABmAHIAYQBtAGUA
IABtAGEAeQAgAG4AbwB0ACAAbwBjAGMAdQByAC4ACgAKADcALgAgAEEAYwBrAG4AbwB3AGwAZQBk
AGcAZQBtAGUAbgB0AHMACgAKACAAIAAgAFQAaABlACAAPABzAHQAcgBpAGsAZQA+ADwAZgBvAG4A
dAAgAGMAbwBsAG8AcgA9ACcAcgBlAGQAJwAgAHMAaQB6AGUAPQAiACsAMQAiAD4AZgBvAGwAbABv
AHcAaQBuAGcAPAAvAGYAbwBuAHQAPgA8AC8AcwB0AHIAaQBrAGUAPgAgADwAcwB0AHIAbwBuAGcA
PgA8AGYAbwBuAHQAIABjAG8AbABvAHIAPQAnAGcAcgBlAGUAbgAnACAAcwBpAHoAZQA9ACIAKwAx
ACIAPgBmAG8AbABsAG8AdwBpAG4AZwAsACAAbABpAHMAdABlAGQAIABpAG4AIABhAGwAcABoAGEA
YgB0AGkAYwAgAG8AcgBkAGUAcgAsADwALwBmAG8AbgB0AD4APAAvAHMAdAByAG8AbgBnAD4AIABh
AHIAZQAgAHQAaABhAG4AawBlAGQAIABmAG8AcgAgAHQAaABlAGkAcgAKACAAIAAgAHYAYQBsAHUA
YQBiAGwAZQAgAGMAbwBuAHQAcgBpAGIAdQB0AGkAbwBuAHMAOgAgACAAPABzAHQAcgBvAG4AZwA+
ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcAIABzAGkAegBlAD0AIgArADEA
IgA+AEIAZQBuACAAQwBhAG0AcABiAGUAbABsACAAYQBuAGQAPAAvAGYAbwBuAHQAPgA8AC8AcwB0
AHIAbwBuAGcAPgAgAFQAaABvAG0AYQBzACAATgBhAHIAdABlAG4ALgAKAAoAIAAgACAAPABzAHQA
cgBvAG4AZwA+ADwAZgBvAG4AdAAgAGMAbwBsAG8AcgA9ACcAZwByAGUAZQBuACcAIABzAGkAegBl
AD0AIgArADEAIgA+AFQAaABpAHMAIABkAG8AYwB1AG0AZQBuAHQAIAB3AGEAcwAgAHAAcgBvAGQA
dQBjAGUAZAAgAHcAaQB0AGgAIAByAGEAdwAgAG4AcgBvAGYAZgAuACAAQQBsAGwAIABtAGEAYwBy
AG8AcwAgAHUAcwBlAGQAIAB3AGUAcgBlAAoAIAAgACAAZABlAGYAaQBuAGUAZAAgAGkAbgAgAHQA
aABlACAAcwBvAHUAcgBjAGUAIABmAGkAbABlADwALwBmAG8AbgB0AD4APAAvAHMAdAByAG8AbgBn
AD4ACgAKAEkATgBUAEUAUgBOAEUAVAAtAEQAUgBBAEYAVAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAVABSAEkATABM
ADoAIABIAGUAYQBkAGUAcgAgAEUAeAB0AGUAbgBzAGkAbwBuAAoACgA4AC4AIABOAG8AcgBtAGEA
dABpAHYAZQAgAFIAZQBmAGUAcgBlAG4AYwBlAHMACgAKACAAIAAgAFsAUgBGAEMAMgAxADEAOQBd
ACAALQAgAEIAcgBhAGQAbgBlAHIALAAgAFMALgAsACAAIgBLAGUAeQAgAHcAbwByAGQAcwAgAGYA
bwByACAAdQBzAGUAIABpAG4AIABSAEYAQwBzACAAdABvACAASQBuAGQAaQBjAGEAdABlAAoAIAAg
ACAAIAAgACAAIAAgACAAUgBlAHEAdQBpAHIAZQBtAGUAbgB0ACAATABlAHYAZQBsAHMAIgAsACAA
QgBDAFAAIAAxADQALAAgAFIARgBDACAAMgAxADEAOQAsACAATQBhAHIAYwBoACAAMQA5ADkANwAu
AAoACgAgACAAIABbAFIARgBDADQAMAAyADAAXQAgAC0AIABLAG8AbQBwAGUAbABsAGEALAAgAEsA
LgAgAGEAbgBkACAAQQAuACAAWgBpAG4AaQBuACwAIAAiAEUAYQByAGwAeQAgAEkAQQBOAEEAIABB
AGwAbABvAGMAYQB0AGkAbwBuACAAbwBmAAoAIAAgACAAIAAgACAAIAAgACAAUwB0AGEAbgBkAGEA
cgBkAHMAIABUAHIAYQBjAGsAIABDAG8AZABlACAAUABvAGkAbgB0AHMAIgAsACAAQgBDAFAAIAAx
ADAAMAAsACAAUgBGAEMAIAA0ADAAMgAwACwAIABGAGUAYgByAHUAYQByAHkAIAAyADAAMAA1AC4A
CgAKACAAIAAgAFsAUgBGAEMANQAyADIANgBdACAALQAgAE4AYQByAHQAZQBuACwAIABUAC4AIABh
AG4AZAAgAEgALgAgAEEAbAB2AGUAcwB0AHIAYQBuAGQALAAgACIARwB1AGkAZABlAGwAaQBuAGUA
cwAgAGYAbwByACAAVwByAGkAdABpAG4AZwAgAGEAbgAKACAAIAAgACAAIAAgACAAIAAgAEkAQQBO
AEEAIABDAG8AbgBzAGkAZABlAHIAYQB0AGkAbwBuAHMAIABTAGUAYwB0AGkAbwBuACAAaQBuACAA
UgBGAEMAcwAiACwAIABCAEMAUAAgADIANgAsACAAUgBGAEMAIAA1ADIAMgA2ACwAIABNAGEAeQAK
ACAAIAAgACAAIAAgACAAIAAgADIAMAAwADgALgAKAAoAIAAgACAAWwBSAEYAQwA2ADMAMgA1AF0A
IAAtACAAUABlAHIAbABtAGEAbgAsACAAUgAuACwAIABEAC4AIABFAGEAcwB0AGwAYQBrAGUALAAg
AEQALgAgAEQAdQB0AHQALAAgAFMALgAgAEcAYQBpACwAIABhAG4AZAAgAEEALgAKACAAIAAgACAA
IAAgACAAIAAgAEcAaABhAG4AdwBhAG4AaQAsACAAIgBSAG8AdQB0AGkAbgBnACAAQgByAGkAZABn
AGUAcwAgACgAUgBCAHIAaQBkAGcAZQBzACkAOgAgAEIAYQBzAGUAIABQAHIAbwB0AG8AYwBvAGwA
CgAgACAAIAAgACAAIAAgACAAIABTAHAAZQBjAGkAZgBpAGMAYQB0AGkAbwBuACIALAAgAEoAdQBs
AHkAIAAyADAAMQAxAC4ACgAKACAAIAAgAFsAQwBoAGEAbgBuAGUAbABdACAALQAgAGQAcgBhAGYA
dAAtAGkAZQB0AGYALQB0AHIAaQBsAGwALQByAGIAcgBpAGQAZwBlAC0AYwBoAGEAbgBuAGUAbAAs
ACAAdwBvAHIAawAgAGkAbgAgAHAAcgBvAGcAcgBlAHMAcwAuAAoACgAgACAAIABbAFIARgBDADYA
MwAyADYAYgBpAHMAXQAgAC0AIABkAHIAYQBmAHQALQBlAGEAcwB0AGwAYQBrAGUALQBpAHMAaQBz
AC0AcgBmAGMANgAzADIANgBiAGkAcwAsACAAdwBvAHIAawAgAGkAbgAgAHAAcgBvAGcAcgBlAHMA
cwAuAAoACgA5AC4AIABJAG4AZgBvAHIAbQBhAHQAaQB2AGUAIABSAGUAZgBlAHIAZQBuAGMAZQBz
AAoACgAgACAAIABbAE8AcAB0AGkAbwBuAHMAXQAgAC0AIABkAHIAYQBmAHQALQBpAGUAdABmAC0A
dAByAGkAbABsAC0AcgBiAHIAaQBkAGcAZQAtAG8AcAB0AGkAbwBuAHMALAAgAHcAbwByAGsAIABp
AG4AIABwAHIAbwBnAHIAZQBzAHMALgAKACAAIAAgACAAIAAgACAAIAAgAC0AIABkAHIAYQBmAHQA
LQBlAGEAcwB0AGwAYQBrAGUALQB0AHIAaQBsAGwALQByAGIAcgBpAGQAZwBlAC0AbQBvAHIAZQAt
AG8AcAB0AGkAbwBuAHMALAAgAHcAbwByAGsAIABpAG4AIABwAHIAbwBnAHIAZQBzAHMALgAKAAoA
SQBOAFQARQBSAE4ARQBUAC0ARABSAEEARgBUACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABUAFIASQBMAEwAOgAgAEgA
ZQBhAGQAZQByACAARQB4AHQAZQBuAHMAaQBvAG4ACgAKAEMAaABhAG4AZwBlACAASABpAHMAdABv
AHIAeQAKAAoAIAAgACAAVABoAGUAIABzAGUAYwB0AGkAbwBuAHMAIABiAGUAbABvAHcAIABzAHUA
bQBtAGEAcgBpAHoAZQAgAGMAaABhAG4AZwBlAHMAIABiAGUAdAB3AGUAZQBuACAAcwB1AGMAYwBl
AHMAcwBpAHYAZQAgAHYAZQByAHMAaQBvAG4AcwAgAG8AZgAKACAAIAAgAHQAaABpAHMAIABkAHIA
YQBmAHQALgAgAFIARgBDACAARQBkAGkAdABvAHIAOgAgAFAAbABlAGEAcwBlACAAZABlAGwAZQB0
AGUAIAB0AGgAaQBzACAAcwBlAGMAdABpAG8AbgAgAGIAZQBmAG8AcgBlAAoAIAAgACAAcAB1AGIA
bABpAGMAYQB0AGkAbwBuAC4ACgAKACAAIAAgAFYAZQByAHMAaQBvAG4AIAAwADAAIABvAGYAIAB0
AGgAaQBzACAAZAByAGEAZgB0ACAAaQBzACAAYQBuACAAZQB4AHQAcgBhAGMAdAAgAGEAbgBkACAA
cwBpAG0AcABsAGkAZgBpAGMAYQB0AGkAbwBuACAAbwBmACAAZAByAGEAZgB0AC0ACgAgACAAIABp
AGUAdABmAC0AdAByAGkAbABsAC0AcgBiAHIAaQBkAGcAZQAtAG8AcAB0AGkAbwBuAHMALQAwADUA
LgB0AHgAdAAgAGEAcwAgAGQAaQBzAGMAdQBzAHMAZQBkACAAYQB0ACAAdABoAGUAIABUAFIASQBM
AEwAIABXAG8AcgBrAGkAbgBnAAoAIAAgACAARwByAG8AdQBwACAAbQBlAGUAdABpAG4AZwAgAGEA
dAAgAEkARQBUAEYAIAA4ADEAIABhAG4AZAAgAG8AbgAgAHQAaABlACAAVABSAEkATABMACAAVwBH
ACAAbQBhAGkAbABpAG4AZwAgAGwAaQBzAHQALgAKAAoARgByAG8AbQAgAC0AMAAwACAAdABvACAA
LQAwADEACgAKACAAIAAgADEALgAgAFUAcABkAGEAdABlACAAQQB1AHQAaABvAHIAIABBAGQAZABy
AGUAcwBzAGUAcwAuAAoACgAgACAAIAAyAC4AIABBAHMAcwBvAHIAdABlAGQAIABlAGQAaQB0AG8A
cgBpAGEAbAAgAGMAaABhAG4AZwBlAHMALgAKAAoARgByAG8AbQAgAC0AMAAxACAAdABvACAALQAw
ADIACgAKACAAIAAgADEALgAgAEEAZABkAGkAdABpAG8AbgAgAG8AZgAgAHQAaABlACAAQwByAGkA
dABpAGMAYQBsACAAUgBCAHIAaQBkAGcAZQAgAEMAaABhAG4AbgBlAGwAIABBAGwAZQByAHQAIABG
AGwAYQBnAC4ACgAKACAAIAAgADIALgAgAEEAcwBzAG8AcgB0AGUAZAAgAGUAZABpAHQAbwByAGkA
YQBsACAAYQBuAGQAIABhAHUAdABoAG8AcgAgAGMAaABhAG4AZwBlAHMALgAKAAoARgByAG8AbQAg
AC0AMAAyACAAdABvACAALQAwADMACgAKACAAIAAgADEALgAgAFIAZQBwAGwAYQBjAGUAbQBlAG4A
dAAgAG8AZgAgAFMAZQBjAHQAaQBvAG4AIAAyAC4ANAAgAHQAbwAgAGUAbABpAG0AaQBuAGEAdABl
ACAAZABlAHQAYQBpAGwAZQBkACAAYwBvAG4AcwB0AHIAYQBpAG4AdABzACAAbwBuAAoAIAAgACAA
IAAgACAAdABoAGUAIABwAHIAbwBjAGUAcwBzAGkAbgBnACAAbwBmACAAYwBvAG4AZgBsAGkAYwB0
AGkAbgBnACAAZQB4AHQAZQBuAHMAaQBvAG4AcwAgAGEAbgBkACAAdABvACAAdwBhAHIAbgAgAGEA
ZwBhAGkAbgBzAHQAIAB0AGgAZQAKACAAIAAgACAAIAAgAGYAdQB0AHUAcgBlACAAcwBwAGUAYwBp
AGYAaQBjAGEAdABpAG8AbgAgAG8AZgAgAGMAbwBuAGYAbABpAGMAdABpAG4AZwAgAG8AcAB0AGkA
bwBuAHMALgAKAAoAIAAgACAAMgAuACAATQBpAG4AbwByACAAZQBkAGkAdABvAHIAaQBhAGwAIABj
AGgAYQBuAGcAZQBzAC4ACgAKAEYAcgBvAG0AIAAtADAAMwAgAHQAbwAgAC0AMAA0AAoACgAgACAA
IABFAGQAaQB0AG8AcgBpAGEAbAAgAGMAaABhAG4AZwBlAHMAIABpAG4AYwBsAHUAZABpAG4AZwAg
AHQAaABlACAAZABlAGwAZQB0AGkAbwBuACAAbwBmACAAUwBlAGMAdABpAG8AbgAgADIALgAzAC4A
MgAgAHQAaABhAHQAIAB3AGEAcwAKACAAIAAgAGMAbwBtAHAAbABlAHQAZQBsAHkAIAByAGUAZAB1
AG4AZABhAG4AdAAgAHcAaQB0AGgAIABlAGEAcgBsAGkAZQByACAAcABhAHIAdABzACAAbwBmACAA
UwBlAGMAdABpAG8AbgAgADIALgAzAC4ACgAKADwAcwB0AHIAbwBuAGcAPgA8AGYAbwBuAHQAIABj
AG8AbABvAHIAPQAnAGcAcgBlAGUAbgAnACAAcwBpAHoAZQA9ACIAKwAxACIAPgBGAHIAbwBtACAA
LQAwADQAIAB0AG8AIAAtADAANQAKAAoAIAAgACAAMQAuACAAQQBkAGQAIAAiAFUAcABkAGEAdABl
AHMAOgAgADYAMwAyADUAIgAgAHQAbwAgAHQAaABlACAAZgBpAHIAcwB0ACAAcABhAGcAZQAgAGgA
ZQBhAGQAZQByACAAYQBzACAAdABoAGkAcwAgAGQAbwBjAHUAbQBlAG4AdAAKACAAIAAgAHAAcgBv
AHYAaQBkAGUAcwAgAG0AbwByAGUAIABkAGUAdABhAGkAbABzACAAbwBuACAAdABoAGUAIAB0AGgA
ZQAgAFQAUgBJAEwATAAgAEgAZQBhAGQAZQByACAAbwBwAHQAaQBvAG4AcwAgAGEAcgBlAGEALgAK
AAoASQBOAFQARQBSAE4ARQBUAC0ARABSAEEARgBUACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABUAFIASQBMAEwAOgAg
AEgAZQBhAGQAZQByACAARQB4AHQAZQBuAHMAaQBvAG4ACgAKADIALgAgAEUAeABwAGEAbgBkACAA
ZgBpAHIAcwB0ACAAdQBzAGUAIABvAGYAIABzAG8AbQBlACAAYQBjAHIAbwBuAHkAbQBzACAAYQBu
AGQAIABvAHQAaABlAHIAIABlAGQAaQB0AG8AcgBpAGEAbAAgAGMAaABhAG4AZwBlAHMALgA8AC8A
ZgBvAG4AdAA+ADwALwBzAHQAcgBvAG4AZwA+AAoACgBJAE4AVABFAFIATgBFAFQALQBEAFIAQQBG
AFQAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgAFQAUgBJAEwATAA6ACAASABlAGEAZABlAHIAIABFAHgAdABlAG4AcwBp
AG8AbgAKAAoAQQB1AHQAaABvAHIAcwAnACAAQQBkAGQAcgBlAHMAcwBlAHMACgAKAEQAbwBuAGEA
bABkACAARQBhAHMAdABsAGEAawBlAAoASAB1AGEAdwBlAGkAIABSACYAYQBtAHAAOwBEACAAVQBT
AEEACgAxADUANQAgAEIAZQBhAHYAZQByACAAUwB0AHIAZQBlAHQACgBNAGkAbABmAG8AcgBkACwA
IABNAEEAIAAwADEANwA1ADcAIABVAFMAQQAKAAoAUABoAG8AbgBlADoAIAArADEALQA1ADAAOAAt
ADMAMwAzAC0AMgAyADcAMAAKAGUAbQBhAGkAbAA6ACAAZAAzAGUAMwBlADMAQABnAG0AYQBpAGwA
LgBjAG8AbQAKAAoAQQBuAG8AbwBwACAARwBoAGEAbgB3AGEAbgBpAAoARABlAGwAbAAKADMANQAw
ACAASABvAGwAZwBlAHIAIABXAGEAeQAKAFMAYQBuACAASgBvAHMAZQAsACAAQwBBACAAOQA1ADEA
MwA0ACAAVQBTAEEACgAKAFAAaABvAG4AZQA6ACAAKwAxAC0ANAAwADgALQA1ADcAMQAtADMANQAw
ADAACgBFAG0AYQBpAGwAOgAgAGEAbgBvAG8AcABAAGEAbAB1AG0AbgBpAC4AZAB1AGsAZQAuAGUA
ZAB1AAoACgBWAGkAcwBoAHcAYQBzACAATQBhAG4AcgBhAGwACgBIAFAAIABOAGUAdAB3AG8AcgBr
AGkAbgBnAAoAMQA5ADEAMQAxACAAUAByAHUAbgBlAHIAaQBkAGcAZQAgAEEAdgBlAG4AdQBlAAoA
QwB1AHAAZQByAHQAaQBuAG8ALAAgAEMAQQAgADkANQAwADEANAAgAFUAUwBBAAoACgBQAGgAbwBu
AGUAOgAgACsAMQAtADQAMAA4AC0ANAA3ADcALQAwADAAMAAwAAoARQBNAGEAaQBsADoAIAB2AGkA
cwBoAHcAYQBzAC4AbQBhAG4AcgBhAGwAQABoAHAALgBjAG8AbQAKAAoAWQBpAHoAaABvAHUAIABM
AGkACgBIAHUAYQB3AGUAaQAgAFQAZQBjAGgAbgBvAGwAbwBnAGkAZQBzAAoAMQAwADEAIABTAG8A
ZgB0AHcAYQByAGUAIABBAHYAZQBuAHUAZQAsAAoATgBhAG4AagBpAG4AZwAgADIAMQAwADAAMQAy
ACwAIABDAGgAaQBuAGEACgAKAFAAaABvAG4AZQA6ACAAKwA4ADYALQAyADUALQA1ADYANgAyADIA
MwAxADAACgBFAG0AYQBpAGwAOgAgAGwAaQB5AGkAegBoAG8AdQBAAGgAdQBhAHcAZQBpAC4AYwBv
AG0ACgAKAEMAYQBpAHQAbABpAG4AIABCAGUAcwB0AGwAZQByAAoAUQB1AGEAbgB0AHUAbQAKADEA
NgA1ADAAIABUAGUAYwBoAG4AbwBsAG8AZwB5ACAARAByAGkAdgBlACAALAAgAFMAdQBpAHQAZQAg
ADcAMAAwAAoAUwBhAG4AIABKAG8AcwBlACwAIABDAEEAIAA5ADUAMQAxADAAIABVAFMAQQAKAAoA
UABoAG8AbgBlADoAIAArADEALQA0ADAAOAAtADkANAA0AC0ANAAwADAAMAAKAGUAbQBhAGkAbAA6
ACAAYwBhAGkAdABAAGEAcwBvAG0AaQAuAGMAbwBtAAoASQBOAFQARQBSAE4ARQBUAC0ARABSAEEA
RgBUACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIABUAFIASQBMAEwAOgAgAEgAZQBhAGQAZQByACAARQB4AHQAZQBuAHMA
aQBvAG4ACgAKAEMAbwBwAHkAcgBpAGcAaAB0ACAAYQBuAGQAIABJAFAAUgAgAFAAcgBvAHYAaQBz
AGkAbwBuAHMACgAKAEMAbwBwAHkAcgBpAGcAaAB0ACAAKABjACkAIAAyADAAMQAyACAASQBFAFQA
RgAgAFQAcgB1AHMAdAAgAGEAbgBkACAAdABoAGUAIABwAGUAcgBzAG8AbgBzACAAaQBkAGUAbgB0
AGkAZgBpAGUAZAAgAGEAcwAgAHQAaABlACAAZABvAGMAdQBtAGUAbgB0AAoAYQB1AHQAaABvAHIA
cwAuACAAQQBsAGwAIAByAGkAZwBoAHQAcwAgAHIAZQBzAGUAcgB2AGUAZAAuAAoACgBUAGgAaQBz
ACAAZABvAGMAdQBtAGUAbgB0ACAAaQBzACAAcwB1AGIAagBlAGMAdAAgAHQAbwAgAEIAQwBQACAA
NwA4ACAAYQBuAGQAIAB0AGgAZQAgAEkARQBUAEYAIABUAHIAdQBzAHQAJwBzACAATABlAGcAYQBs
ACAAUAByAG8AdgBpAHMAaQBvAG4AcwAKAFIAZQBsAGEAdABpAG4AZwAgAHQAbwAgAEkARQBUAEYA
IABEAG8AYwB1AG0AZQBuAHQAcwAgACgAaAB0AHQAcAA6AC8ALwB0AHIAdQBzAHQAZQBlAC4AaQBl
AHQAZgAuAG8AcgBnAC8AbABpAGMAZQBuAHMAZQAtAGkAbgBmAG8AKQAgAGkAbgAKAGUAZgBmAGUA
YwB0ACAAbwBuACAAdABoAGUAIABkAGEAdABlACAAbwBmACAAcAB1AGIAbABpAGMAYQB0AGkAbwBu
ACAAbwBmACAAdABoAGkAcwAgAGQAbwBjAHUAbQBlAG4AdAAuACAAUABsAGUAYQBzAGUAIAByAGUA
dgBpAGUAdwAgAHQAaABlAHMAZQAKAGQAbwBjAHUAbQBlAG4AdABzACAAYwBhAHIAZQBmAHUAbABs
AHkALAAgAGEAcwAgAHQAaABlAHkAIABkAGUAcwBjAHIAaQBiAGUAIAB5AG8AdQByACAAcgBpAGcA
aAB0AHMAIABhAG4AZAAgAHIAZQBzAHQAcgBpAGMAdABpAG8AbgBzACAAdwBpAHQAaAAKAHIAZQBz
AHAAZQBjAHQAIAB0AG8AIAB0AGgAaQBzACAAZABvAGMAdQBtAGUAbgB0AC4AIABDAG8AZABlACAA
QwBvAG0AcABvAG4AZQBuAHQAcwAgAGUAeAB0AHIAYQBjAHQAZQBkACAAZgByAG8AbQAgAHQAaABp
AHMAIABkAG8AYwB1AG0AZQBuAHQACgBtAHUAcwB0ACAAaQBuAGMAbAB1AGQAZQAgAFMAaQBtAHAA
bABpAGYAaQBlAGQAIABCAFMARAAgAEwAaQBjAGUAbgBzAGUAIAB0AGUAeAB0ACAAYQBzACAAZABl
AHMAYwByAGkAYgBlAGQAIABpAG4AIABTAGUAYwB0AGkAbwBuACAANAAuAGUAIABvAGYACgB0AGgA
ZQAgAFQAcgB1AHMAdAAgAEwAZQBnAGEAbAAgAFAAcgBvAHYAaQBzAGkAbwBuAHMAIABhAG4AZAAg
AGEAcgBlACAAcAByAG8AdgBpAGQAZQBkACAAdwBpAHQAaABvAHUAdAAgAHcAYQByAHIAYQBuAHQA
eQAgAGEAcwAKAGQAZQBzAGMAcgBpAGIAZQBkACAAaQBuACAAdABoAGUAIABTAGkAbQBwAGwAaQBm
AGkAZQBkACAAQgBTAEQAIABMAGkAYwBlAG4AcwBlAC4AIAAgAFQAaABlACAAZABlAGYAaQBuAGkA
dABpAHYAZQAgAHYAZQByAHMAaQBvAG4AIABvAGYAIABhAG4ACgBJAEUAVABGACAARABvAGMAdQBt
AGUAbgB0ACAAaQBzACAAdABoAGEAdAAgAHAAdQBiAGwAaQBzAGgAZQBkACAAYgB5ACwAIABvAHIA
IAB1AG4AZABlAHIAIAB0AGgAZQAgAGEAdQBzAHAAaQBjAGUAcwAgAG8AZgAsACAAdABoAGUAIABJ
AEUAVABGAC4ACgBWAGUAcgBzAGkAbwBuAHMAIABvAGYAIABJAEUAVABGACAARABvAGMAdQBtAGUA
bgB0AHMAIAB0AGgAYQB0ACAAYQByAGUAIABwAHUAYgBsAGkAcwBoAGUAZAAgAGIAeQAgAHQAaABp
AHIAZAAgAHAAYQByAHQAaQBlAHMALAAKAGkAbgBjAGwAdQBkAGkAbgBnACAAdABoAG8AcwBlACAA
dABoAGEAdAAgAGEAcgBlACAAdAByAGEAbgBzAGwAYQB0AGUAZAAgAGkAbgB0AG8AIABvAHQAaABl
AHIAIABsAGEAbgBnAHUAYQBnAGUAcwAsACAAcwBoAG8AdQBsAGQAIABuAG8AdAAgAGIAZQAKAGMA
bwBuAHMAaQBkAGUAcgBlAGQAIAB0AG8AIABiAGUAIABkAGUAZgBpAG4AaQB0AGkAdgBlACAAdgBl
AHIAcwBpAG8AbgBzACAAbwBmACAASQBFAFQARgAgAEQAbwBjAHUAbQBlAG4AdABzAC4AIABUAGgA
ZQAgAGQAZQBmAGkAbgBpAHQAaQB2AGUACgB2AGUAcgBzAGkAbwBuACAAbwBmACAAdABoAGUAcwBl
ACAATABlAGcAYQBsACAAUAByAG8AdgBpAHMAaQBvAG4AcwAgAGkAcwAgAHQAaABhAHQAIABwAHUA
YgBsAGkAcwBoAGUAZAAgAGIAeQAsACAAbwByACAAdQBuAGQAZQByACAAdABoAGUACgBhAHUAcwBw
AGkAYwBlAHMAIABvAGYALAAgAHQAaABlACAASQBFAFQARgAuACAAVgBlAHIAcwBpAG8AbgBzACAA
bwBmACAAdABoAGUAcwBlACAATABlAGcAYQBsACAAUAByAG8AdgBpAHMAaQBvAG4AcwAgAHQAaABh
AHQAIABhAHIAZQAKAHAAdQBiAGwAaQBzAGgAZQBkACAAYgB5ACAAdABoAGkAcgBkACAAcABhAHIA
dABpAGUAcwAsACAAaQBuAGMAbAB1AGQAaQBuAGcAIAB0AGgAbwBzAGUAIAB0AGgAYQB0ACAAYQBy
AGUAIAB0AHIAYQBuAHMAbABhAHQAZQBkACAAaQBuAHQAbwAKAG8AdABoAGUAcgAgAGwAYQBuAGcA
dQBhAGcAZQBzACwAIABzAGgAbwB1AGwAZAAgAG4AbwB0ACAAYgBlACAAYwBvAG4AcwBpAGQAZQBy
AGUAZAAgAHQAbwAgAGIAZQAgAGQAZQBmAGkAbgBpAHQAaQB2AGUAIAB2AGUAcgBzAGkAbwBuAHMA
IABvAGYACgB0AGgAZQBzAGUAIABMAGUAZwBhAGwAIABQAHIAbwB2AGkAcwBpAG8AbgBzAC4AIAAg
AEYAbwByACAAdABoAGUAIABhAHYAbwBpAGQAYQBuAGMAZQAgAG8AZgAgAGQAbwB1AGIAdAAsACAA
ZQBhAGMAaAAgAEMAbwBuAHQAcgBpAGIAdQB0AG8AcgAgAHQAbwAKAHQAaABlACAASQBFAFQARgAg
AFMAdABhAG4AZABhAHIAZABzACAAUAByAG8AYwBlAHMAcwAgAGwAaQBjAGUAbgBzAGUAcwAgAGUA
YQBjAGgAIABDAG8AbgB0AHIAaQBiAHUAdABpAG8AbgAgAHQAaABhAHQAIABoAGUAIABvAHIAIABz
AGgAZQAKAG0AYQBrAGUAcwAgAGEAcwAgAHAAYQByAHQAIABvAGYAIAB0AGgAZQAgAEkARQBUAEYA
IABTAHQAYQBuAGQAYQByAGQAcwAgAFAAcgBvAGMAZQBzAHMAIAB0AG8AIAB0AGgAZQAgAEkARQBU
AEYAIABUAHIAdQBzAHQAIABwAHUAcgBzAHUAYQBuAHQACgB0AG8AIAB0AGgAZQAgAHAAcgBvAHYA
aQBzAGkAbwBuAHMAIABvAGYAIABSAEYAQwAgADUAMwA3ADgALgAgAE4AbwAgAGwAYQBuAGcAdQBh
AGcAZQAgAHQAbwAgAHQAaABlACAAYwBvAG4AdAByAGEAcgB5ACwAIABvAHIAIAB0AGUAcgBtAHMA
LAAKAGMAbwBuAGQAaQB0AGkAbwBuAHMAIABvAHIAIAByAGkAZwBoAHQAcwAgAHQAaABhAHQAIABk
AGkAZgBmAGUAcgAgAGYAcgBvAG0AIABvAHIAIABhAHIAZQAgAGkAbgBjAG8AbgBzAGkAcwB0AGUA
bgB0ACAAdwBpAHQAaAAgAHQAaABlAAoAcgBpAGcAaAB0AHMAIABhAG4AZAAgAGwAaQBjAGUAbgBz
AGUAcwAgAGcAcgBhAG4AdABlAGQAIAB1AG4AZABlAHIAIABSAEYAQwAgADUAMwA3ADgALAAgAHMA
aABhAGwAbAAgAGgAYQB2AGUAIABhAG4AeQAgAGUAZgBmAGUAYwB0ACAAYQBuAGQACgBzAGgAYQBs
AGwAIABiAGUAIABuAHUAbABsACAAYQBuAGQAIAB2AG8AaQBkACwAIAB3AGgAZQB0AGgAZQByACAA
cAB1AGIAbABpAHMAaABlAGQAIABvAHIAIABwAG8AcwB0AGUAZAAgAGIAeQAgAHMAdQBjAGgAIABD
AG8AbgB0AHIAaQBiAHUAdABvAHIALAAKAG8AcgAgAGkAbgBjAGwAdQBkAGUAZAAgAHcAaQB0AGgA
IABvAHIAIABpAG4AIABzAHUAYwBoACAAQwBvAG4AdAByAGkAYgB1AHQAaQBvAG4ALgAKADwALwBw
AHIAZQA+AAoAPAAvAGIAbwBkAHkAPgA8AC8AaAB0AG0AbAA+AAoA
--14dae9341241881f6e04c195b0c1--

From ned.freed@mrochek.com  Mon Jun  4 01:05:55 2012
Return-Path: <ned.freed@mrochek.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87EF021F8575 for <gen-art@ietfa.amsl.com>; Mon,  4 Jun 2012 01:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbM6d5Pb54zG for <gen-art@ietfa.amsl.com>; Mon,  4 Jun 2012 01:05:55 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id DB77A21F86DE for <gen-art@ietf.org>; Mon,  4 Jun 2012 01:05:54 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OG9PMY6J0W002PU9@mauve.mrochek.com> for gen-art@ietf.org; Mon, 4 Jun 2012 01:05:48 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OG54121Q0W0006TF@mauve.mrochek.com>; Mon, 4 Jun 2012 01:05:41 -0700 (PDT)
Message-id: <01OG9PMT5FAE0006TF@mauve.mrochek.com>
Date: Mon, 04 Jun 2012 01:02:55 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 30 May 2012 14:59:25 +0200" <201205301259.q4UCxPNL040225@givry.fdupont.fr>
MIME-version: 1.0
References: <201205301259.q4UCxPNL040225@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Cc: gen-art@ietf.org, draft-ietf-appsawg-media-type-regs.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-appsawg-media-type-regs-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 08:05:55 -0000

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

> Please resolve these comments along with any other Last Call comments
> you may receive.

> Document: draft-ietf-appsawg-media-type-regs-10.txt
> Reviewer: Francis Dupont
> Review Date: 20120523
> IETF LC End Date: 20120521
> IESG Telechat date: unknown

> Summary: Ready

> Major issues: None

> Minor issues: None

> Nits/editorial comments:
>  - ToC page 3: Acknowledgements -> Acknowledgments

Autogenerated from section head; see below.

>  - 4.2.5 page 12: missing "." in:
>   understood by implementors The
>                             ^

Nice catch; fixed.

>  - 4.6 page 17: servies -> services

>  - 7 page 26: suffx -> suffix

>  - 8 page 27: Registions -> Registrations
>   and mutiple -> multiple

Fixed this typos as well.

>  - 9 page 27: Acknowledgements -> Acknowledgments
 
I made this change, but as John noted, it may not stick.

> PS: I want to signal the high quality of this document, for instance I got the idea to check
> where the types are case-insensitive and I found it in 10 seconds from the printed version
> (i.e., no grep :-)!

Thanks!

				Ned

From rbarnes@bbn.com  Mon Jun  4 05:33:43 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 484D121F8724; Mon,  4 Jun 2012 05:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UoveCkfK1DfS; Mon,  4 Jun 2012 05:33:41 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id B089321F871C; Mon,  4 Jun 2012 05:33:41 -0700 (PDT)
Received: from ros-dhcp192-1-51-6.bbn.com ([192.1.51.6]:59859) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1SbWT4-0003ZQ-Qa; Mon, 04 Jun 2012 08:33:06 -0400
From: Richard L. Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 4 Jun 2012 08:33:40 -0400
Message-Id: <196B9066-2934-443D-B642-997BDF57948E@bbn.com>
To: ietf@ietf.org, IESG <iesg@ietf.org>, gen-art@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-appsawg-about-uri-scheme-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 12:33:43 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-appsawg-about-uri-scheme-05
Reviewer: Richard Barnes
Review Date: Jun-04-2012
IETF LC End Date: Not known
IESG Telechat date: Jun-07-2012

Summary: Almost ready, couple of questions

MAJOR:=20

*.
I wonder how useful this document is, given that the use of "about:" =
URIs is currently very inconsistent across browsers. (See, for example, =
<http://en.wikipedia.org/wiki/About_URI_scheme>)  Some browsers also use =
alternative URI schemes for essentially the same function ("opera:", =
"chrome:").  Has there been input from the browser vendor community on =
this document? =20


4.
The document correctly notes that "about:" URIs sometimes point to =
sensitive data, and that browsers need to protect them.  However, the =
document fails to specify what the threats are and how to mitigate them. =
 It seems to me that the major risk is cross-site scripting, in the =
sense that a remote web page might include an "about:" URI (e.g., via an =
XMLHttpRequest) in order to access sensitive data.  At a high level, =
then, the mitigation would be to ensure that such URIs are accessible =
only as a result of direct user action (e.g., typing in a URI) or =
trusted browser code (e.g., extensions).


From sm@elandsys.com  Mon Jun  4 10:22:08 2012
Return-Path: <sm@elandsys.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E519C11E8088; Mon,  4 Jun 2012 10:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Pi4OkpL9Fpn; Mon,  4 Jun 2012 10:22:05 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C1C1121F845F; Mon,  4 Jun 2012 10:22:05 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.236.146]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q54HLkDh027717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2012 10:21:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338830521; i=@elandsys.com; bh=ZICT4SsNKoebjID3Jr4J6G6YKzLiu7w9knpVKol53QA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GftnKy+PrvXqCGP4WfDH5JM8fuYuDIXOehj3FyhecmcoqZf19MNvmb7t8GQYntb02 tPw3WrNsf/M1DlzmNhQ76ydkZ+cPOJ/QLn7IOyzfkwWQWKVa7tinvX2BMXtOhr0I/Z onhp34NwPij92ni3xE5CXsWmtKwFhapWmHxllP4A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1338830521; i=@elandsys.com; bh=ZICT4SsNKoebjID3Jr4J6G6YKzLiu7w9knpVKol53QA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1NySZBjGptjCil2uTxP6wdxAF/Uz5oJysiyReUANhxGAGVUbiscpraV77SycgwYjQ lEl+hzRcw7HwonMsLsdwWUFLvGpjgjGxCwSOIXFkmczL+xSRHK54HLORx0ExDdvlTq g7Ai5Wz2KjPlpoa9SEvjD2mV4EgaRJR5Mddr9viw=
Message-Id: <6.2.5.6.2.20120604072443.098cdc28@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 04 Jun 2012 10:00:38 -0700
To: "Richard L. Barnes" <rbarnes@bbn.com>, IESG <iesg@ietf.org>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <196B9066-2934-443D-B642-997BDF57948E@bbn.com>
References: <196B9066-2934-443D-B642-997BDF57948E@bbn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: gen-art@ietf.org, ietf@ietf.org, apps-discuss@ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-appsawg-about-uri-scheme-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 17:22:08 -0000

Hi Richard,

Thanks for the review.  This is an individual comment.

At 05:33 04-06-2012, Richard L. Barnes wrote:
>I wonder how useful this document is, given that the use of "about:" 
>URIs is currently very inconsistent across browsers. (See, for 
>example, <http://en.wikipedia.org/wiki/About_URI_scheme>)  Some 
>browsers also use alternative URI schemes for essentially the same 
>function ("opera:", "chrome:").  Has there been input from the 
>browser vendor community on this document?

One of the editors of draft-ietf-appsawg-about-uri-scheme-04 
affiliated with Opera Software ASA provided input about the draft.

The Wikipedia article mentions that it needs additional citations for 
verification.  Although the "about" URI scheme is well-known, it has 
never been registered.  The document describes the URI scheme and 
registers it in the "URI Schemes".  The document does not seek to 
impose any requirement.  It leaves it to browser vendors to decide 
what to do.

>4.
>The document correctly notes that "about:" URIs sometimes point to 
>sensitive data, and that browsers need to protect them.  However, 
>the document fails to specify what the threats are and how to 
>mitigate them.  It seems to me that the major risk is cross-site 
>scripting, in the sense that a remote web page might include an 
>"about:" URI (e.g., via an XMLHttpRequest) in order to access 
>sensitive data.  At a high level, then, the mitigation would be to 
>ensure that such URIs are accessible only as a result of direct user 
>action (e.g., typing in a URI) or trusted browser code (e.g., extensions).

Section 4 of draft-ietf-appsawg-about-uri-scheme-06 mentions that 
"about" URIs may be used to reference, for example, user passwords 
stored in a cache.  The document does not register such a token 
though. It leaves it to person with expertise to write the 
specification about that token to consider the security 
implications.  Adding text to discuss about cross-site scripting 
might be misconstrued as a recommendation.

Regards,
S. Moonesamy 


From alexey.melnikov@isode.com  Mon Jun  4 11:06:19 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E31E21F8609 for <gen-art@ietfa.amsl.com>; Mon,  4 Jun 2012 11:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.294
X-Spam-Level: 
X-Spam-Status: No, score=-102.294 tagged_above=-999 required=5 tests=[AWL=0.305, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PAV3bj5L9Jfb for <gen-art@ietfa.amsl.com>; Mon,  4 Jun 2012 11:06:19 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 19BE321F8620 for <gen-art@ietf.org>; Mon,  4 Jun 2012 11:06:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1338833177; d=isode.com; s=selector; i=@isode.com; bh=XsI4zpl9dihFNtogiCVRs5r7bDKegUjIWBHXArNuuYE=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=enujMihIjZ9JClmX8G3hIpC4/Ll7H9y65h7+7s+uGVN7wZI4XC20vYgOmov1jql70pu+X0 eTOhG++XrzSwvOUcieJE/IoSepNPRIcoSijsiKekw/hPvH/qfWScgzqIMcWTgz9US+6Y4M ozYgg77kWLeA7zQlP4J3YvkgT5Ozqy8=;
Received: from [172.20.10.2] ((unknown) [212.183.128.204])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T8z5FgAE46ZE@rufus.isode.com>; Mon, 4 Jun 2012 19:06:16 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4FCCF90A.4000204@isode.com>
Date: Mon, 04 Jun 2012 19:06:02 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: draft-ietf-trill-rbridge-bfd.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]  Gen-ART review of draft-ietf-trill-rbridge-bfd-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 18:06:19 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-trill-rbridge-bfd-06
Reviewer: Alexey Melnikov
Review Date: 2012-06-04
IETF LC End Date: 2012-06-06
IESG Telechat date: 2012-06-07

Summary: Ready for publication as a Proposed Standard

Major issues: None

Minor issues: None

Nits/editorial comments: None

From ron.even.tlv@gmail.com  Mon Jun  4 14:23:02 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3C4411E80DF; Mon,  4 Jun 2012 14:23:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhDgSf814vHC; Mon,  4 Jun 2012 14:22:59 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 23D2D11E80EC; Mon,  4 Jun 2012 14:22:58 -0700 (PDT)
Received: by werb13 with SMTP id b13so3605459wer.31 for <multiple recipients>; Mon, 04 Jun 2012 14:22:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=5FGk1VhOrYtA3rMsj8vOwLC415uw9sXew8WnrWZhFik=; b=01L3UtUaaqsaa85rMRGi7Guw9qAGO6QRMo08QzcJ6DaurUFcFyxqDH6roIeiP1l9Px sX4j5JrEScMFfOA8Y0nTAfdca9+Oy2J1t5Htj6dZvEWUyJ+bHhPAkIy+iYS4Hv6Q3pHr +qbKOW5XfAy2PRR/JoXTBZa6UOuiS7QkFXrvd0/+pwgBpnIIO4cg2H3DZa0fuZ6UOf2i Z639Pv4Hul4C89Q6fWyNSG1LoUGSA4YfKHrl4TDHyLnrt9NQLO6EhKnnmvOmLuFjzfV7 2KSjsAQ4JtMH7DC/v7ujI3zfVFHXqzjx1LxNPAA/9KdPvlNhxQeE3yw+8Wj8Cy95lfos Pl1g==
Received: by 10.216.50.80 with SMTP id y58mr6011977web.106.1338844975531; Mon, 04 Jun 2012 14:22:55 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-182-224-219.red.bezeqint.net. [79.182.224.219]) by mx.google.com with ESMTPS id gb9sm22526945wib.8.2012.06.04.14.22.53 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jun 2012 14:22:54 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-nea-pt-tls.all@tools.ietf.org>
Date: Tue, 5 Jun 2012 00:20:26 +0300
Message-ID: <4fcd272e.2968b40a.55d4.ffff9de3@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005B_01CD42B1.032B5AF0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1Cl9xExNAkih6WSYeHA9SkXDOg7g==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>
Subject: [Gen-art] GenART LC review of draft-ietf-nea-pt-tls-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 21:23:02 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_005B_01CD42B1.032B5AF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-ietf-nea-pt-tls-05

Reviewer: Roni Even

Review Date:2012-6-4

IETF LC End Date: 2012-6-13

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

Major issues:

 

Minor issues:

1.       In section 3.2 "Therefore, this specification requests the IANA
reserve a TCP port number for use with the PT-TLS protocol upon publication
of this specification as an Internet standard RFC." I think it will  be
better to have here the assigned port number and instruct the RFC editor to
put the correct value.

2.       In section 3.4.2.2 last paragraph you summarize the text from
section 3.8 while in the paragraph above you provide the reference. Why do
you need the last paragraph if 3.8 is referenced.

3.       In various places you refer to SMI 0 as IETF SMI number while
according to the table it is IANA SMI number.

4.       I assume that all implementations MUST support message type vendor
ID 0. Is this mentioned?

5.       In section 3.5 and 6.1 you propose a policy of "Expert Review with
Specification Required ". I think that according to RFC5226 expert review is
implied if you select a specification required policy.

6.       In section 3.6 on 9+ "Recipients of messages   of type 9 or higher
that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message
Type of a received PT-TLS message MUST respond with a Type Not Supported
PT-TLS error code in a PT-TLS Error message." I think this is true only for
Message Type Vendor ID 0.

7.       In 3.7.1 for Max vers and prefs ver you say that they MUST be set
to 1. I think it will be more correct here to say SHOULD since you explain
afterwards that they may have other values.

8.       In section 3.7.2 "the recipient SHOULD send". Why not make it a
MUST here.

9.       In section 3.7.2 "The version selected MUST be within the Min Vers
to Max Vers inclusive range sent in the Version Request   Message" I was
expecting to see pref ver here.

10.   In section 3.8.3 " The SASL client authentication starts when the NEA
Server  enters the PT-TLS Negotiation phase and its policy indicates  that
an authentication of the NEA Client is necessary but was not performed
during the TLS handshake protocol " my read of  section 3.8 second paragraph
is that it can be done even if was done in the TLS handshake so the last
part of the sentence is not correct, if there is a policy you do it anyhow.
This comment is also for the third paragraph.

11.   In section 3.9 I noticed that you propose to send the entire original
message. Isn't it enough to send only the message identifier. This is based
on the last sentence of this section.

12.   Most of the text in section 6.1 repeats RFC5226 but in your words. Are
you trying to change some of RFC5226 text if not why write it in different
words?

 

 

 

Nits/editorial comments:

 


------=_NextPart_000_005B_01CD42B1.032B5AF0
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-microsoft-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=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 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-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2023900102;
	mso-list-type:hybrid;
	mso-list-template-ids:-625979886 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-=
nea-pt-tls-05<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;6&#8211;4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;6&#8211;13<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as a standard track =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC</span><=
span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.2 </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&#8220;Ther=
efore, this specification requests the IANA reserve a TCP port number =
for use with the PT-TLS protocol upon publication of this specification =
as an Internet standard RFC.&#8221; I think it will&nbsp; be better to =
have here the assigned port number and instruct the RFC editor to put =
the correct value.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.4.2.2 last paragraph you summarize the text from section 3.8 while in =
the paragraph above you provide the reference. Why do you need the last =
paragraph if 3.8 is referenced.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In various =
places you refer to SMI 0 as IETF SMI number while according to the =
table it is IANA SMI number.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I assume =
that all implementations MUST support message type vendor ID 0. Is this =
mentioned?<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.5 and 6.1 you propose a policy of &#8220;Expert Review with =
Specification Required &#8220;. I think that according to RFC5226 expert =
review is implied if you select a specification required =
policy.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.6 on 9+ &#8220;Recipients of messages&nbsp;&nbsp; of type 9 or higher =
that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message =
Type of a received PT-TLS message MUST respond with a Type Not Supported =
PT-TLS error code in a PT-TLS Error message.&#8221; I think this is true =
only for Message Type Vendor ID 0.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In 3.7.1 =
for Max vers and prefs ver you say that they MUST be set to 1. I think =
it will be more correct here to say SHOULD since you explain afterwards =
that they may have other values.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.7.2 &#8220;the recipient SHOULD send&#8221;. Why not make it a MUST =
here.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.7.2 &#8220;The version selected MUST be within the Min Vers to Max =
Vers inclusive range sent in the Version Request&nbsp;&nbsp; =
Message&#8221; I was expecting to see pref ver =
here.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>10.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.8.3 &#8220; The SASL client authentication starts when the NEA =
Server&nbsp; enters the PT-TLS Negotiation phase and its policy =
indicates&nbsp; that an authentication of the NEA Client is necessary =
but was not performed during the TLS handshake protocol &#8220; my read =
of&nbsp; s</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>ection 3.8 =
second paragraph is that it can be done even if was done in the TLS =
handshake so the last part of the sentence is not correct, if there is a =
policy you do it anyhow. This comment is also for the third =
paragraph.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>11.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.9 I noticed that you propose to send the entire original message. =
Isn&#8217;t it enough to send only the message identifier. This is based =
on the last sentence of this section.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>12.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Most of =
the text in section 6.1 repeats RFC5226 but in your words. Are you =
trying to change some of RFC5226 text if not why write it in different =
words?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_005B_01CD42B1.032B5AF0--


From ben@nostrum.com  Mon Jun  4 14:56:58 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C153E21F86D3 for <gen-art@ietfa.amsl.com>; Mon,  4 Jun 2012 14:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.073
X-Spam-Level: 
X-Spam-Status: No, score=-101.073 tagged_above=-999 required=5 tests=[AWL=-0.773, BAYES_00=-2.599, MANGLED_LIST=2.3, SPF_PASS=-0.001,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kuw3mk43v6wn for <gen-art@ietfa.amsl.com>; Mon,  4 Jun 2012 14:56:57 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id AB41A21F86CF for <gen-art@ietf.org>; Mon,  4 Jun 2012 14:56:57 -0700 (PDT)
Received: from dn3-123.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q54LurJU034602 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 4 Jun 2012 16:56:53 -0500 (CDT) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <CAF4+nEG_ciDC6Gz8BEFmwTi2qUZwXuKxAKv_jDe7v4v8OfX4Lg@mail.gmail.com>
Date: Mon, 4 Jun 2012 16:56:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <97385D02-3301-42C8-89C5-014784B44D53@nostrum.com>
References: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com> <CAF4+nEESCSkUgM2Wzr5MXfW5su5Og_XA0dyO+gksfN2LAzCCWw@mail.gmail.com> <69241DCD-C349-4D15-8B92-58D05F216BF5@nostrum.com> <CAF4+nEH0G-8JD5XuSBRp2xcWtdFUmh0x0nw=Q-9gV4Jtkp74iw@mail.gmail.com> <CAF4+nEG_ciDC6Gz8BEFmwTi2qUZwXuKxAKv_jDe7v4v8OfX4Lg@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1278)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: Vishwas Manral <vishwas.ietf@gmail.com>, draft-ietf-trill-rbridge-extension.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat review of draft-ietf-trill-rbridge-extension-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 21:56:58 -0000

This version looks good to me.

Thanks!

Ben.

On Jun 3, 2012, at 1:35 PM, Donald Eastlake wrote:

> Hi Ben,
>=20
> Attached is a version incorporating changes to resolve your comments
> and a wdiff against the current -04 version. However, given the
> proximity to the IESG tele chat, I do not plan to upload this version
> before that call.
>=20
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>=20
>=20
> On Sun, Jun 3, 2012 at 9:43 AM, Donald Eastlake <d3e3e3@gmail.com> =
wrote:
>> Hi Ben,
>>=20
>> On Fri, Jun 1, 2012 at 3:18 PM, Ben Campbell <ben@nostrum.com> wrote:
>>> Thanks for the quick response. Further comments inline. I deleted =
sections that do not appear to need further discussion.
>>>=20
>>> Thanks!
>>>=20
>>> Ben.
>>>=20
>>> On Jun 1, 2012, at 10:45 AM, Donald Eastlake wrote:
>>>=20
>>>> Hi Ben,
>>>>=20
>>>> Thanks for your review. See responses below.
>>>>=20
>>>> On Thu, May 31, 2012 at 6:08 PM, Ben Campbell <ben@nostrum.com> =
wrote:
>>>>=20
>>>>> I am the assigned Gen-ART reviewer for this draft. For background =
on
>>>>> Gen-ART, please see the FAQ at
>>>>> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>>=20
>>>>> Please wait for direction from your document shepherd
>>>>> or AD before posting a new version of the draft.
>>>>>=20
>>>>> Document: draft-ietf-trill-rbridge-extension-04
>>>>> Reviewer: Ben Campbell
>>>>> Review Date: 2012-05-31
>>>>> IETF LC End Date: 2012-06-07
>>>>> IESG Telechat date: 2012-06-07
>>>>>=20
>>>>> Note: Since this draft is on the agenda of the IESG Telechat on =
the
>>>>> same day that the IETF last call expires, this review is intended
>>>>> for both purposes.
>>>>>=20
>>>>> Summary:
>>>>>=20
>>>>> This draft is almost ready for publication as a proposed standard,
>>>>> but I have some clarification questions and comments that should =
be
>>>>> considered prior to publication.
>>>>>=20
>>>>> Major issues:
>>>>>=20
>>>>> None
>>>>>=20
>>>>> Minor issues:
>>>>>=20
>>>>> -- section 2, general:
>>>>>=20
>>>>> Do the authors assume that all TRILL extensions will follow this
>>>>> spec? Since RFC6325 already specifies an extension mechanism, what
>>>>> stops an extension from ignoring this spec and doing something
>>>>> different? Does it hurt if they do?
>>>>=20
>>>> I am not aware of any conflicts between this draft and RFC 6325. =
RFC
>>>> 6325 provides the broadest header option framework, for example
>>>> specifying the field for the length of the options area and the
>>>> initial two critical summary bits. This document fills in the
>>>> structure and allocation mechanism of the remaining bits in the =
first
>>>> 4-byte word of the options area, consistent with and repeating some
>>>> material from RFC 6325, but leaving specification of the remainder =
of
>>>> the options area for future documents, which should be consistent =
with
>>>> both RFC 6325 and this document. (For example, some future version =
of
>>>> draft-ietf-trill-rbridge-options.)
>>>=20
>>> I agree there is no conflict--this draft adds details, but doesn't =
seem to contradict anything in the RFC.
>>>=20
>>>>=20
>>>> However, neither RFC 6325 nor this document can actually actually =
bind
>>>> the IETF against adopting future standards describing extensions =
that
>>>> do not conform.
>>>=20
>>> Certainly. Nothing can do that. The IETF can always update a =
protocol to change normative language, no matter how strongly it was =
stated originally :-)
>>>=20
>>>> If future changes do not follow RFC 6325 or this
>>>> document, for example changing the location or interpretation of =
the
>>>> option length field in the TRILL Header or changing the =
interpretation
>>>> of the critical summary bits in the first word of the options area,
>>>> then this would break hardware and software implementations that
>>>> depend on RFC 6325 and/or this document. But I trust the IETF to
>>>> adhere to its usually high standards for backwards compatibility.
>>>>=20
>>>> Perhaps this draft should, in the first page header, say "Updates:
>>>> 6325", not in the sense that it makes a change but in the sense =
that
>>>> it fills in more details.
>>>>=20
>>>=20
>>> Assuming the additional details in this draft comprise preferred =
extension mechanism, then I think it makes sense to say that somewhere =
(perhaps a SHOULD strength), and also mark it as updating 6325. Adding =
details is still an update.
>>=20
>> OK.
>>=20
>>>>> -- section 2, 3rd paragraph from end: "Non-critical extensions can
>>>>>   be safely ignored."
>>>>>=20
>>>>> Is that intended to be normative? (Seems like it should be, since
>>>>> behavior for critical extensions is normative).
>>>>=20
>>>> I think of it as more like the definition of "non-critical".
>>>=20
>>> Sure--I mainly mention it to be consistent with the text for =
"critical" extensions, since it did use normative language about =
dropping frames.
>>>=20
>>>>=20
>>>>> -- section 2.1, 1st paragraph, last sentence:
>>>>>=20
>>>>> Redundant with normative language in previous section.
>>>>=20
>>>> ? There is a normative requirement to discard frames with any
>>>> unimplemented critical hop-by-hop options present, which might be
>>>> thought to require examination of all options (something manifestly
>>>> impossible since the format of options beyond the first word of the
>>>> options area is not yet normatively specified). The sentence to =
which
>>>> you refer just clarifies that testing the appropriate crtical =
summary
>>>> bit(s) in the first word of the options area, if that word is =
present,
>>>> is all that is required.
>>>=20
>>> section 2 says "Any RBridge receiving a frame with a critical =
hop-by-hop extension  that it does not implement MUST discard the =
frame...". Section 2.1 says "If an RBridge does not implement all =
critical flags in a TRILL Data frame, it MUST discard the frame..." =
These really seem like the same MUST (i.e, if you updated one but not =
the other, you would have an ambiguous state). The same is true for the =
egress bit.
>>>=20
>>> I understand that you want to draw the connection between a =
"critical extension" and "critical flags", but it's better to avoid =
having multiple bits of authoritative text for the same normative =
requirement. Perhaps it might be better to say something like "If the =
RBridge does not implement all critical flags... it MUST treat the frame =
as having an unimplemented critical extension as described in section 2"
>>=20
>> I'm OK with your suggested wording.
>>=20
>>>>=20
>>>>> -- section 2.3, first paragraph:
>>>>>=20
>>>>> Is the first sentence intended as normative?
>>>>=20
>>>> Yes. When one is describing part of a protocol and you say that =
some
>>>> particular contiguous block of bits is some particular field (and =
then
>>>> possibly describe the sub-structure of that field) isn't that =
always
>>>> normative?
>>>=20
>>> Never mind, I misread the sentence. Sorry for the confusion.
>>>=20
>>>>=20
>>>>> -- section 6, last paragraph:
>>>>>=20
>>>>> No security implications of this are mentioned. Is it really a
>>>>> security consideration?
>>>>>=20
>>>>> Also, is this more likely to be set incorrectly than all the other
>>>>> things that some implementation might screw up, so that it =
warrants
>>>>> special treatment?
>>>>=20
>>>> I tend to think that a discussion of what happens if bits are
>>>> corrupted or incorrectly set is something reasonable for the =
Security
>>>> Considerations section, although it could be elsewhere. The second
>>>> paragraph/sentence of this section says that security =
considerations
>>>> for any bits in the first word of the options area will be in the
>>>> document specifying those bits. This document specifies the =
critical
>>>> summary bits and the RBridge Channel Alert bits so there is text on
>>>> both of those in its Security Considerations Section.
>>>=20
>>> On re-reading the paragraph, I can see interpreting it to mean that =
incorrectly set flags explicitly do not cause a security problem, which =
I agree is reasonable to say in the security considerations. So, never =
mind :-)
>>>=20
>>> [...]
>>>=20
>>>=20
>>>>>=20
>>>>> -- section 2, bullet list, 2nd bullet: " ... which would only
>>>>>   necessarily affect the RBridge(s) where a TRILL frame is
>>>>>   decapsulated"
>>>>>=20
>>>>> Does that mean it always affects the decapsulating RBridge but =
might
>>>>> effect transit RBridges as well?
>>>>=20
>>>> Yes.
>>>>=20
>>>=20
>>> Okay, no problem.
>>>=20
>>>>> -- section 2, first paragraph after bullet list: "critical
>>>>>   hop-by-hop extension"
>>>>>=20
>>>>> I assume this means an extension with the critical flag set? If =
so,
>>>>> it would be more precise to say that.
>>>>=20
>>>> This draft was split out of a more general draft that covered
>>>> extensions in general. The three paragraphs after the bullet list =
on
>>>> critical / non-critical extensions apply to all extensions as well =
as
>>>> the flag bits in the first word of the options area. So this means
>>>> critical header extensions flags and any other types of critical
>>>> options specified in the future.
>>>=20
>>> Okay
>>>=20
>>> [...]
>>>=20
>>>=20
>>>>=20
>>>>> -- section 5:
>>>>>=20
>>>>> Since section 3 is entirely composed of the referenced table, and
>>>>> seems to exist mostly if not entirely for the purpose of this
>>>>> reference, why not just move the table to the IANA considerations
>>>>> section.
>>>>=20
>>>> (Looking at Section 3, I believe the reference there to the IANA
>>>> Considerations Section should be to Section 5 rather than Section =
6.)
>>>>=20
>>>> I guess I don't actually see any problem with the current document
>>>> structure that I think flows better for someone reading it from the
>>>> start. I suppose it imposes a tiny burden on someone who is just
>>>> looking at the IANA Considerations Section. I don't see why it =
would
>>>> be better to make it a tiny bit easier for someone just looking at =
the
>>>> IANA Considerations Section while imposing a tiny burdne on those
>>>> reading through the document from the start.
>>>>=20
>>>=20
>>> Okay. I was interpreting it as existing entirely for the IANA =
registration--but if you believe it adds value to the "body" of the =
text, I am okay with it.
>>>=20
>>> [...]
>>=20
>> Thanks,
>> Donald
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>  155 Beaver Street, Milford, MA 01757 USA
>>  d3e3e3@gmail.com
> =
<re31fftoc.txt><wdiffRE-04vInternal31.html>_______________________________=
________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From christer.holmberg@ericsson.com  Mon Jun  4 23:51:47 2012
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B9CC21F86E2 for <gen-art@ietfa.amsl.com>; Mon,  4 Jun 2012 23:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.201
X-Spam-Level: 
X-Spam-Status: No, score=-7.201 tagged_above=-999 required=5 tests=[AWL=1.047,  BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BFiJ6Spasz5b for <gen-art@ietfa.amsl.com>; Mon,  4 Jun 2012 23:51:44 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2CAE321F86EB for <gen-art@ietf.org>; Mon,  4 Jun 2012 23:51:42 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fc66d000006fdc-a4-4fcdac7d2632
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 33.49.28636.D7CADCF4; Tue,  5 Jun 2012 08:51:41 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.250]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Tue, 5 Jun 2012 08:51:40 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-mif-dns-server-selection.all@tools.ietf.org" <draft-ietf-mif-dns-server-selection.all@tools.ietf.org>
Date: Tue, 5 Jun 2012 08:50:39 +0200
Thread-Topic: GenART LC review of draft-ietf-mif-dns-server-selection-09
Thread-Index: Ac1C5ejFgw/cfoF3QxOoZV+SN9Hr2g==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C45A1C8DC@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F2072F1E0DE894DA4B517B93C6A05852C45A1C8DCESESSCMS0356e_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsUyM+JvrW7tmrP+BlPmqVus/PCTzeLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfG/yNP2Qu6HjJWdF5dw9bAeOckYxcjJ4eE gInE5nn32CBsMYkL99YD2VwcQgKnGCUe7b/ADJIQEljAKDF9UWoXIwcHm4CFRPc/bZAaEZDw ou3zwAaxCKhI9Lb9ZQGxhQWcJSZvaGQCsUUEPCT+vVzACGHrSTS9+gg2k1cgXOLQp4fsIDYj 0OLvp9aA1TMLiEvcejKfCeIgAYkle84zQ9iiEi8f/2OFqBeVuNO+nhGiPl9i65YFrBAzBSVO znzCMoFRaBaSUbOQlM1CUgYR15FYsPsTG4StLbFs4WtmGPvMgcdMyOILGNlXMQrnJmbmpJcb 6qUWZSYXF+fn6RWnbmIExsnBLb91dzCeOidyiFGag0VJnJcrab+/kEB6YklqdmpqQWpRfFFp TmrxIUYmDk6pBkYnnohTxzt373OKcPGOFs4p8r5z0vSkZkFAy0qeCQv5nlU+8Gl0EbK1ZKh7 5RGT+VwncsmW9IYpF9e/81KL0Jox9eDen9yhL7Kczyrlr596L72j2++7ode3yLQ88SWLbtxn WKXTKjH5fV7cjA/SKwQ1pJe3ipS0/tewnCSizVZXtPBlj0bxJSWW4oxEQy3mouJEANpYZvVh AgAA
Subject: [Gen-art] GenART LC review of draft-ietf-mif-dns-server-selection-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 06:51:47 -0000

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-mif-dns-server-selection-09.txt
Reviewer: Christer Holmberg
Review Date: 2012-06-05
IETF LC End Date: 2012-06-08
IESG Telechat date: (if known) 2012-06-21

Summary: The document is ready for publication, but there are a number of e=
ditorial nits.

Major issues: -

Minor issues: -

Nits/editorial comments:





General:

----------



Q_GEN-1: Throughout the document, please check whether RFC 2119 style, with=
 capital letters, should be used.





Q_GEN-2: Throughout the document,  there are lots of "a/an" and "the" missi=
ng. It may be a good idea to double check that, but I guess the RFC editor =
will also handle it.





Q_GEN-3: Sometimes the documents say "learned information", and sometimes "=
obtained information". Is it possible to use common terminology?





Section 2.1:

--------------



Q_2_1-1: I suggest to start the section with "In this scenario, a multi-int=
erfaced node is connected to..."





Section 2.2:

--------------



Q_2_2-1: I suggest to change "In the second problem" to "In this scenario".





Q_2_2-2: I suggest to change "Node's" to "The node's"





Section 2.3:

--------------



Q_2_3-1: I would suggest to change the section name to something else, e.g.=
 "Issues with the solution".





Q_2_3-2: Add reference to DNSSEC on first occurance.





Section 3:

------------



Q_3-1: I suggest to modify "First being a Consumer Premises Equipment (CPE)=
 with two or more uplink VLAN connections." to ""The first scenario consist=
s of a Consumer Premises Equipment (CPE) having two or more uplink VLAN con=
nections."





Q_3-2: I suggest to modify "Second scenario involves a cellular device with=
 two uplink Internet connections: WLAN and cellular." to "The second scenar=
io consists of a cellular device with two uplink Internet connections: WLAN=
 and cellular."





Q_3-3: I suggest to modify "Third scenario is for VPNs, where use of local =
RDNSS may be preferred for latency reasons, but enterprise's RDNSS must be =
used to resolve private names used by the enterprise." to "The third scenar=
io consists of VPNs, where use of local RDNSS may be preferred for latency =
reasons, but enterprise's RDNSS must be used to resolve private names used =
by the enterprise."





Q_3-4: I suggest to add the following sentence to the end of the section: "=
The following sections describe the scenarios in detail."







Section 3.1:

--------------





Q_3_1-1: I suggest to modify:



   "In the two uplinks scenario only one uplink connection leads to the Int=
ernet,
   while another uplink connection leads to a private network utilizing
   private namespaces."



...to:



   "One uplink connection leads to the Internet, while the other leads to a=
 private network utilizing private namespaces."





Q_3_1-2: I suggest to modify: "but instead CPE should send default queries"=
 to "but rather sends default queries".





Section 3.2:



Q_3_2-1: I suggest to modify: "In such a case" to "In such cases".





Section 4.1:

--------------



Q_4_1-1: The first sentence, "A resolver SHALL build a priority list of RDN=
SSes it will contact to depending on the query." is difficult to parse. Dep=
ending on the query what?





Q_4_1-2: I suggest to modify "To build the list in an optimal way, a node S=
HOULD ask with DHCP which..." to "To build the list in an optimal way, a no=
de SHOULD ask, using DHCP, which..."





Q_4_1-3: Modify "do so, see Section 4.4 for details." to "do so. See Sectio=
n 4.4 for details."





Q_4_1-4: I suggest to modify:



   "The route must point to the interface each RDNSS
   address was learned on.  This is required to ensure DNS queries are
   sent out via the right network interface."



...to:



   "In order to ensure that DNS queries are sent out via the correct networ=
k interface, the route must point to the interface on which each RDNSS addr=
ess was retrieved."





Q_4_1-5: Modify "on the nature of" to "the nature of".





Q_4_1-6: In the sentence which says "In the case of all other things being =
equal the resolver shall make the prioritization decision based on its inte=
rnal preferences."



...I think it would be good to use some other wording than "other things". =
Maybe something like:



"In case the procedures above result in equal priorities, the resolver shal=
l make the priorization decision based on..."





Q_4_1-7: I suggest to modify:



   "A node SHALL send requests to RDNSSes in the order defined by the
   priority list until an acceptable reply is received, all replies are
   received, or a time out occurs."



...to: "A node SHALL, according to the priority list, send requests to RDNS=
Ses until an acceptable reply is received, until all replies have been rece=
ived, or until a time-out occures".





Section 4.4:

--------------



Q_4_4-1: Would "Limitations of usage" be a better section title?





 Regards,



Christer
























--_000_7F2072F1E0DE894DA4B517B93C6A05852C45A1C8DCESESSCMS0356e_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Tahoma","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>I am the ass=
igned Gen-ART reviewer for this draft. For background on<br>Gen-ART, please=
 see the FAQ at<br>&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/=
wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/=
wiki/GenArtfaq</a>&gt;.<br><br>Please resolve these comments along with any=
 other Last Call comments<br>you may receive.<br><br>Document: draft-ietf-m=
if-dns-server-selection-09.txt<br>Reviewer: Christer Holmberg<br>Review Dat=
e: 2012-06-05<br>IETF LC End Date: 2012-06-08<br>IESG Telechat date: (if kn=
own) 2012-06-21<br><br>Summary: The document is ready for publication, but =
there are a number of editorial nits.<o:p></o:p></span></p><div><p class=3D=
MsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
;color:black'><br>Major issues: -<br><br>Minor issues: -<br><br>Nits/editor=
ial comments:<o:p></o:p></span></p></div><p><span style=3D'font-size:10.0pt=
;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p=
><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color=
:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font=
-family:"Tahoma","sans-serif";color:black'>General:<o:p></o:p></span></p><p=
><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:bl=
ack'>----------<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;fon=
t-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p>=
<span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:bla=
ck'>Q_GEN-1: Throughout the document, please check whether RFC 2119 style, =
with capital letters, should be used.<o:p></o:p></span></p><p><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&n=
bsp;</o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Q_GEN-2:&nbs=
p;Throughout the document, &nbsp;there are lots of &quot;a/an&quot; and &qu=
ot;the&quot; missing. It may be a good idea to double check that, but I gue=
ss the RFC editor will also handle it.<o:p></o:p></span></p><p><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<=
o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Q_GEN-3: Som=
etimes the documents say &quot;learned information&quot;, and sometimes &qu=
ot;obtained information&quot;. Is it possible to use common terminology?<o:=
p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma",=
"sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'fon=
t-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o=
:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans=
-serif";color:black'>Section 2.1:<o:p></o:p></span></p><p><span style=3D'fo=
nt-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>-------------=
-&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family=
:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Q_2_=
1-1: I suggest to start the section with &quot;In this scenario,&nbsp;a mul=
ti-interfaced node&nbsp;is connected to...&quot;<o:p></o:p></span></p><p><s=
pan style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black=
'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-famil=
y:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><span s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Sec=
tion 2.2:<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-fami=
ly:"Tahoma","sans-serif";color:black'>--------------<o:p></o:p></span></p><=
p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:b=
lack'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-f=
amily:"Tahoma","sans-serif";color:black'>Q_2_2-1: I suggest to change &quot=
;In the second problem&quot; to &quot;In this scenario&quot;.<o:p></o:p></s=
pan></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
";color:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0=
pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span><=
/p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";col=
or:black'>Q_2_2-2: I suggest to change &quot;Node's&quot; to &quot;The node=
's&quot;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-famil=
y:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><span s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nb=
sp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif";color:black'>Section 2.3:<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>--=
------------<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-f=
amily:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><sp=
an style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'=
>Q_2_3-1: I would suggest to change the section name to something else, e.g=
. &quot;Issues with the solution&quot;.<o:p></o:p></span></p><p><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<=
o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Q_2_3-2: Add=
 reference to DNSSEC on first occurance.<o:p></o:p></span></p><p><span styl=
e=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;=
<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'=
font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Section 3:<=
o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";color:black'>------------<o:p></o:p></span></p><p><span styl=
e=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;=
<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif";color:black'>Q_3-1: I suggest to&nbsp;modify&nbsp;&quot;Fir=
st being a Consumer Premises Equipment (CPE)&nbsp;with two or more uplink V=
LAN connections.&quot; to &quot;&quot;The first scenario&nbsp;consists of a=
&nbsp;Consumer Premises Equipment (CPE)&nbsp;having two or more uplink VLAN=
 connections.&quot;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt=
;font-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p=
><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color=
:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font=
-family:"Tahoma","sans-serif";color:black'>Q_3-2: I suggest to modify &quot=
;Second scenario involves a cellular device with two uplink Internet connec=
tions: WLAN and cellular.&quot; to &quot;The second scenario&nbsp;consists =
of a cellular device with two uplink Internet connections: WLAN and cellula=
r.&quot;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-famil=
y:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nb=
sp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif";color:black'>Q_3-3: I suggest to modify &quot;Third scen=
ario is for VPNs, where use of local RDNSS may be preferred for latency rea=
sons, but enterprise's RDNSS must be used to resolve private names used by =
the enterprise.&quot; to &quot;The third scenario&nbsp;consists of&nbsp;VPN=
s, where use of local RDNSS may be preferred for latency reasons, but enter=
prise's RDNSS must be used to resolve private names used by the enterprise.=
&quot;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:=
"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span sty=
le=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp=
;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Taho=
ma","sans-serif";color:black'>Q_3-4: I suggest to add the following sentenc=
e to the end of the section: &quot;The following sections describe the scen=
arios in detail.&quot;<o:p></o:p></span></p><p><span style=3D'font-size:10.=
0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span>=
</p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";co=
lor:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;f=
ont-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><=
p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:b=
lack'>Section 3.1:<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;=
font-family:"Tahoma","sans-serif";color:black'>--------------<o:p></o:p></s=
pan></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
";color:black'><o:p>&nbsp;</o:p></span></p><p><span style=3D'font-size:10.0=
pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span><=
/p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";col=
or:black'>Q_3_1-1: I suggest to modify:<o:p></o:p></span></p><p><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<=
o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";color:black'>&nbsp;&nbsp; &quot;In the two uplinks scenario =
only one uplink connection leads to the Internet,<br>&nbsp;&nbsp; while ano=
ther uplink connection leads to a private network utilizing<br>&nbsp;&nbsp;=
 private namespaces.&quot;<o:p></o:p></span></p><p><span style=3D'font-size=
:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></s=
pan></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
";color:black'>...to:<o:p></o:p></span></p><p><span style=3D'font-size:10.0=
pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span><=
/p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";col=
or:black'>&nbsp;&nbsp; &quot;One uplink connection leads to the Internet, w=
hile&nbsp;the other&nbsp;leads to a private network utilizing private names=
paces.&quot;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-f=
amily:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><sp=
an style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'=
>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family=
:"Tahoma","sans-serif";color:black'>Q_3_1-2: I suggest to modify: &quot;but=
 instead CPE should send default queries&quot; to &quot;but rather sends de=
fault queries&quot;.<o:p></o:p></span></p><p><span style=3D'font-size:10.0p=
t;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></=
p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";colo=
r:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;fon=
t-family:"Tahoma","sans-serif";color:black'>Section 3.2:<o:p></o:p></span><=
/p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";col=
or:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;fo=
nt-family:"Tahoma","sans-serif";color:black'>Q_3_2-1: I suggest to modify: =
&quot;In such a case&quot; to &quot;In such cases&quot;.<o:p></o:p></span><=
/p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";col=
or:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;fo=
nt-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p=
><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:bl=
ack'>Section 4.1:<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;f=
ont-family:"Tahoma","sans-serif";color:black'>--------------<o:p></o:p></sp=
an></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
;color:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0p=
t;font-family:"Tahoma","sans-serif";color:black'>Q_4_1-1: The first sentenc=
e, &quot;A resolver SHALL build a priority list of RDNSSes it will contact =
to depending on the query.&quot; is difficult to parse. Depending on the qu=
ery what?<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-fami=
ly:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&n=
bsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"T=
ahoma","sans-serif";color:black'>Q_4_1-2: I suggest to modify &quot;To buil=
d the list in an optimal way, a node SHOULD ask with DHCP which...&quot; to=
 &quot;To build the list in an optimal way, a node SHOULD ask, using DHCP, =
which...&quot;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font=
-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><=
span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:blac=
k'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-fami=
ly:"Tahoma","sans-serif";color:black'>Q_4_1-3: Modify &quot;do so, see Sect=
ion 4.4 for details.&quot; to &quot;do so. See Section 4.4 for details.&quo=
t;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tah=
oma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<=
o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";color:black'>Q_4_1-4: I suggest to modify:<o:p></o:p></span>=
</p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";co=
lor:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;f=
ont-family:"Tahoma","sans-serif";color:black'>&nbsp;&nbsp;&nbsp;&quot;The r=
oute must point to the interface each RDNSS<br>&nbsp;&nbsp; address was lea=
rned on.&nbsp; This is required to ensure DNS queries are<br>&nbsp;&nbsp; s=
ent out via the right network interface.&quot;<o:p></o:p></span></p><p><spa=
n style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:=
"Tahoma","sans-serif";color:black'>...to:<o:p></o:p></span></p><p><span sty=
le=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp=
;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Taho=
ma","sans-serif";color:black'>&nbsp;&nbsp; &quot;In order to ensure that DN=
S queries are sent out via the correct network interface, the route must po=
int to the interface on which each RDNSS address was retrieved.&quot;<o:p><=
/o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sa=
ns-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span style=3D'font-s=
ize:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p>=
</span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-se=
rif";color:black'>Q_4_1-5: Modify &quot;on the nature of&quot; to &quot;the=
 nature of&quot;.<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;f=
ont-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><=
p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:b=
lack'><o:p>&nbsp;</o:p></span></p><p><span style=3D'font-size:10.0pt;font-f=
amily:"Tahoma","sans-serif";color:black'>Q_4_1-6: In the sentence which say=
s &quot;In the case of all other things being equal the resolver shall make=
 the prioritization decision based on its internal preferences.&quot;<o:p><=
/o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sa=
ns-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-s=
ize:10.0pt;font-family:"Tahoma","sans-serif";color:black'>...I think it wou=
ld be good to use some other wording than &quot;other things&quot;. Maybe s=
omething like:<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font=
-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><=
span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:blac=
k'>&quot;In case the procedures above result in equal priorities, the resol=
ver shall make the priorization decision based on...&quot;<o:p></o:p></span=
></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";c=
olor:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;=
font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>=
<p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:=
black'>Q_4_1-7: I suggest to modify:<o:p></o:p></span></p><p><span style=3D=
'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p=
></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif";color:black'>&nbsp;&nbsp; &quot;A node SHALL send requests to R=
DNSSes in the order defined by the<br>&nbsp;&nbsp; priority list until an a=
cceptable reply is received, all replies are<br>&nbsp;&nbsp; received, or a=
 time out occurs.&quot;<o:p></o:p></span></p><p><span style=3D'font-size:10=
.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span=
></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";c=
olor:black'>...to: &quot;A node SHALL, according to the priority list,&nbsp=
;send requests to RDNSSes until an acceptable reply is received, until all =
replies have been received, or until a time-out occures&quot;.<o:p></o:p></=
span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-seri=
f";color:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.=
0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span>=
</p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";co=
lor:black'>Section 4.4:<o:p></o:p></span></p><p><span style=3D'font-size:10=
.0pt;font-family:"Tahoma","sans-serif";color:black'>--------------&nbsp;<o:=
p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma",=
"sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span style=3D'fon=
t-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Q_4_4-1: Would=
 &quot;Limitations of usage&quot; be a better section title?<o:p></o:p></sp=
an></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
;color:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0p=
t;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></=
p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";colo=
r:black'>&nbsp;Regards,<o:p></o:p></span></p><p><span style=3D'font-size:10=
.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span=
></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";c=
olor:black'>Christer<o:p></o:p></span></p><p><span style=3D'font-size:10.0p=
t;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></=
p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";colo=
r:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;fon=
t-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p>=
<span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:bla=
ck'><o:p>&nbsp;</o:p></span></p><p><span style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><span=
 style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"=
Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p style=3D'm=
argin-bottom:12.0pt'><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span style=3D'font=
-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:=
p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-=
serif";color:black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size=
:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></s=
pan></p><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fami=
ly:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p></div></d=
iv></body></html>=

--_000_7F2072F1E0DE894DA4B517B93C6A05852C45A1C8DCESESSCMS0356e_--

From suresh.krishnan@ericsson.com  Tue Jun  5 08:53:19 2012
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 632A221F86FE for <gen-art@ietfa.amsl.com>; Tue,  5 Jun 2012 08:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PgzmgrIfqn+U for <gen-art@ietfa.amsl.com>; Tue,  5 Jun 2012 08:53:18 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3E23421F870E for <gen-art@ietf.org>; Tue,  5 Jun 2012 08:53:18 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q55Fr0uw027105; Tue, 5 Jun 2012 10:53:17 -0500
Received: from [142.133.112.108] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.264.0; Tue, 5 Jun 2012 11:53:16 -0400
Message-ID: <4FCE2B6C.1010704@ericsson.com>
Date: Tue, 5 Jun 2012 11:53:16 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: <draft-ietf-mile-iodef-xmlreg.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-mile-iodef-xmlreg-01.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 15:53:19 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-mile-iodef-xmlreg-01.txt
Reviewer: Suresh Krishnan
Review Date: 2012/06/07
IESG Telechat date: 2012/06/05

Summary: This document is ready for publication as a Proposed Standard 
but I have a comment.

Minor
=====

* Introduction:

The first sentence is too complex and very difficult to parse. Please 
consider breaking it up. I have proposed some changed text, but feel 
free to ignore if it changes the meaning of what you wanted to convey.

OLD:
IODEF extensions via class extension through AdditionalData and
RecordItem elements, as per section 5.2 of [RFC5070], generally
register their namespaces and schemas with the IANA XML Namespace
registry at http://www.iana.org/assignments/xml-registry/ns.html and
the IANA XML Schema registry at
http://www.iana.org/assignments/xml-registry/schema.html,
respectively [RFC3688].

NEW:
The classes of the IODEF data model can be extended by the use of
AdditionalData and RecordItem elements, as per section 5.2 of [RFC5070].
IODEF extensions that use such extended classes register their 
namespaces and schemas with the IANA XML Namespace
registry at http://www.iana.org/assignments/xml-registry/ns.html and
the IANA XML Schema registry at
http://www.iana.org/assignments/xml-registry/schema.html,
respectively [RFC3688].


Thanks
Suresh






From mary.ietf.barnes@gmail.com  Tue Jun  5 12:24:16 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 403D721F8724 for <gen-art@ietfa.amsl.com>; Tue,  5 Jun 2012 12:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.566
X-Spam-Level: 
X-Spam-Status: No, score=-103.566 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61K21gGerq+0 for <gen-art@ietfa.amsl.com>; Tue,  5 Jun 2012 12:24:15 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6054D21F85D7 for <gen-art@ietf.org>; Tue,  5 Jun 2012 12:24:15 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so5165501ghb.31 for <gen-art@ietf.org>; Tue, 05 Jun 2012 12:24:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=4kvcl7poBK9lYqX5bSJyH7UGxj4IvjYPxzoA/8PX3fE=; b=QLVObBXHA+ljmA4+7r3NHiwgkyuMBnCyLP5WU1NarxZ9WH+akNCvW4X4Mt1mH0a151 ANMWMrx2mmlnUj0w/XA7eIlFNenT3NDr2DiuzxQ42ajXCne5E9ndtAiLZUesbAh/l/oK yKkN5QzpPB8tnStsPenMJj3PNUu3u41uLBgID5Hh6UAeVYsPJ1d4c8kJy1QEvJJ2Swbh 7fXQfn4wWoZ6m214dOK6uQHLLf08CDLrsqpLSqXWbMEzBHbCdLmp9wx8fvBWCk/HzQtX iX+Xqw/fQh486vQKEvmM5lDRjzt6MswZP9N0ZCxMip3pFOE9fKjwajH34aVJwy0khYo/ FFWA==
MIME-Version: 1.0
Received: by 10.42.81.17 with SMTP id x17mr12038253ick.5.1338924254615; Tue, 05 Jun 2012 12:24:14 -0700 (PDT)
Received: by 10.231.68.75 with HTTP; Tue, 5 Jun 2012 12:24:14 -0700 (PDT)
In-Reply-To: <CAHBDyN4kYQOG5=gp3J5QrVe+x1vrgU0EL_YziHtX80CqG+EWGQ@mail.gmail.com>
References: <CAHBDyN4kYQOG5=gp3J5QrVe+x1vrgU0EL_YziHtX80CqG+EWGQ@mail.gmail.com>
Date: Tue, 5 Jun 2012 14:24:14 -0500
Message-ID: <CAHBDyN46FvRCB1PnatWVKSJ+Av2-wFnZUFSg8nNTY4+NyYRJLQ@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: gen-art@ietf.org
Content-Type: multipart/alternative; boundary=90e6ba614e5493d9b704c1be988d
Subject: [Gen-art] Fwd: Gen-ART Review:draft-ietf-mpls-ldp-gtsm-08.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 19:24:16 -0000

--90e6ba614e5493d9b704c1be988d
Content-Type: text/plain; charset=ISO-8859-1

Oops - forgot to cc gen-art.

---------- Forwarded message ----------
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Mon, Jun 4, 2012 at 5:34 PM
Subject: Gen-ART Review:draft-ietf-mpls-ldp-gtsm-08.txt
To: draft-ietf-mpls-ldp-gtsm.all@tools.ietf.org


I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at <
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-mpls-ldp-gtsm-08.txt
Reviewer:  Mary Barnes
Review Date:  4 June 2012
IETF LC End Date: 29 May 2012
IESG Telechat Date: 07 June 2012

Summary:  Ready with minor nits

Editorial nits:

1) Section 1:
-  2nd para, last sentence:
This sentence doesn't quite parse - it's not normative, so it should either
be deleted or reworded.  I suggest deleting as I think it's somewhat
superfluous.

- Next to last paragraph - last three sentences - a little verbose &
somewhat redundant.  I think it can be summarized something like the
following:
OLD:
   This document specifies a "built-in dynamic GTSM
   capability negotiation" for LDP to suggest the use of GTSM.  GTSM
   will be used as specified in this document provided both peers on an
   LDP session can detect each others' support for GTSM procedures and
   agree to use it.  That is, the desire to use GTSM (i.e., its
   negotiation mechanics) is enabled by default without any
   configuration.
NEW:
   This document specifies a dynamic GTSM
   capability negotiation mechanism for LDP. This mechanism allows
   both peers on an LDP session to indicate the support and use of GTSM
   without requiring any configuration.

2) Section 2.2, 1st para, last sentence: "and RECOMMENDED" -> "and are
RECOMMENDED"

--90e6ba614e5493d9b704c1be988d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Oops - forgot to cc gen-art.<br><br><div class=3D"gmail_quote">---------- F=
orwarded message ----------<br>From: <b class=3D"gmail_sendername">Mary Bar=
nes</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:mary.ietf.barnes@gmail.com"=
>mary.ietf.barnes@gmail.com</a>&gt;</span><br>
Date: Mon, Jun 4, 2012 at 5:34 PM<br>Subject: Gen-ART Review:draft-ietf-mpl=
s-ldp-gtsm-08.txt<br>To: <a href=3D"mailto:draft-ietf-mpls-ldp-gtsm.all@too=
ls.ietf.org">draft-ietf-mpls-ldp-gtsm.all@tools.ietf.org</a><br><br><br><di=
v>
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq</a>&gt;.</div>

<div><br></div><div>Document: draft-ietf-mpls-ldp-gtsm-08.txt</div><div>Rev=
iewer: =A0Mary Barnes=A0</div><div>Review Date: =A04 June 2012</div><div>IE=
TF LC End Date: 29 May 2012</div><div>IESG Telechat Date: 07 June 2012</div=
>
<div>
<br></div><div>Summary: =A0Ready with minor nits</div><div><br></div><div>E=
ditorial nits:=A0</div><div><br></div><div>1) Section 1:</div><div>- =A02nd=
 para, last sentence:</div><div>This sentence doesn&#39;t quite parse - it&=
#39;s not normative, so it should either be deleted or reworded. =A0I sugge=
st deleting as I think it&#39;s somewhat superfluous.</div>

<div><br></div><div>- Next to last paragraph - last three sentences - a lit=
tle verbose &amp; somewhat redundant. =A0I think it can be summarized somet=
hing like the following:</div><div>OLD:</div><div>=A0 =A0This document spec=
ifies a &quot;built-in dynamic GTSM</div>

<div>=A0 =A0capability negotiation&quot; for LDP to suggest the use of GTSM=
. =A0GTSM</div><div>=A0 =A0will be used as specified in this document provi=
ded both peers on an</div><div>=A0 =A0LDP session can detect each others&#3=
9; support for GTSM procedures and</div>

<div>=A0 =A0agree to use it. =A0That is, the desire to use GTSM (i.e., its<=
/div><div>=A0 =A0negotiation mechanics) is enabled by default without any</=
div><div>=A0 =A0configuration.</div><div>NEW:</div><div>=A0 =A0This documen=
t specifies a dynamic GTSM</div>

<div>=A0 =A0capability negotiation mechanism for LDP. This mechanism allows=
=A0</div><div>=A0 =A0both peers on an LDP session to indicate the support a=
nd use of GTSM=A0</div><div>=A0 =A0without requiring any configuration.=A0<=
/div><div><br>

</div><div>2) Section 2.2, 1st para, last sentence: &quot;and RECOMMENDED&q=
uot; -&gt; &quot;and are RECOMMENDED&quot;</div><div><br></div><div><br></d=
iv><div>=A0 =A0=A0</div><div><br></div>
</div><br>

--90e6ba614e5493d9b704c1be988d--

From mary.ietf.barnes@gmail.com  Tue Jun  5 12:28:06 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3072E21F87B8 for <gen-art@ietfa.amsl.com>; Tue,  5 Jun 2012 12:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.567
X-Spam-Level: 
X-Spam-Status: No, score=-103.567 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d4NMSr9ta+3f for <gen-art@ietfa.amsl.com>; Tue,  5 Jun 2012 12:28:05 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7122021F86B0 for <gen-art@ietf.org>; Tue,  5 Jun 2012 12:28:03 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so5169455ghb.31 for <gen-art@ietf.org>; Tue, 05 Jun 2012 12:28:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=RfCQSObULMks/Fp6kSlFPMn/VKIutdAmaAt6+3fq5xI=; b=IwS+qU/nMH2Ltvprq6E7Ha85g6it52EMAgOiVC1bETV/X4YEL/cQGgQKltne9s+4n6 Y0LCt2Vn4DLfQYrqjqcM0tYv9/f//Bx/lK8AmAxXECC/ORx8+3mooR259nxkcNEYmPd8 kEtbm3wzaFf7tjvB/IOj+fYyLYJEgnMs/awamsPn1xdp0U+wpVx2MT0VixRvvfEBdVFy UnjpW3dT3D+WuQNK2CYYw1Y01ceA8+Mpb8PX+hiP/cKVUhJDlZ4vQm3iX4Hw3DpLgPr8 OHJvhxkb+ZsfpqCX3A1+W44kt02OguNDpezfAswWd/4McxB4q0kh1iqyTC9Pn0UQPmqx NvWw==
MIME-Version: 1.0
Received: by 10.50.104.228 with SMTP id gh4mr4052129igb.71.1338924482690; Tue, 05 Jun 2012 12:28:02 -0700 (PDT)
Received: by 10.231.68.75 with HTTP; Tue, 5 Jun 2012 12:28:02 -0700 (PDT)
In-Reply-To: <B99ED789-C852-499E-9E0A-1848E3699BCB@cisco.com>
References: <CAHBDyN4kYQOG5=gp3J5QrVe+x1vrgU0EL_YziHtX80CqG+EWGQ@mail.gmail.com> <B99ED789-C852-499E-9E0A-1848E3699BCB@cisco.com>
Date: Tue, 5 Jun 2012 14:28:02 -0500
Message-ID: <CAHBDyN6=i=vNffUdf7o7aF5bD2gjVfb5C0NzVyz6KyUcPx8ThA@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: gen-art@ietf.org
Content-Type: multipart/mixed; boundary=e89a8f234cbf2bfc8004c1bea60b
Subject: [Gen-art] Fwd: Gen-ART Review:draft-ietf-mpls-ldp-gtsm-08.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 19:28:06 -0000

--e89a8f234cbf2bfc8004c1bea60b
Content-Type: multipart/alternative; boundary=e89a8f234cbf2bfc7404c1bea609

--e89a8f234cbf2bfc7404c1bea609
Content-Type: text/plain; charset=ISO-8859-1

And, the response didn't make it either, of course.

---------- Forwarded message ----------
From: Carlos Pignataro (cpignata) <cpignata@cisco.com>
Date: Mon, Jun 4, 2012 at 8:11 PM
Subject: Re: Gen-ART Review:draft-ietf-mpls-ldp-gtsm-08.txt
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Cc: "<draft-ietf-mpls-ldp-gtsm.all@tools.ietf.org>" <
draft-ietf-mpls-ldp-gtsm.all@tools.ietf.org>


Mary,

Many thanks for the review! Much appreciated -- please see inline:

On Jun 4, 2012, at 6:34 PM, Mary Barnes wrote:

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at <
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-mpls-ldp-gtsm-08.txt
Reviewer:  Mary Barnes
Review Date:  4 June 2012
IETF LC End Date: 29 May 2012
IESG Telechat Date: 07 June 2012

Summary:  Ready with minor nits

Editorial nits:

1) Section 1:
-  2nd para, last sentence:
This sentence doesn't quite parse - it's not normative, so it should either
be deleted or reworded.  I suggest deleting as I think it's somewhat
superfluous.


Agreed E_PARSE. I recommend we do not delete because it introduces the
concept that this is for Basic Discovery. However, suggest:

   Therefore, GTSM can fully benefit LDP protocol peering session
   established using Basic Discovery.

to:

   Therefore, GTSM can protect an LDP protocol peering session
   established using Basic Discovery.

Thank you.

- Next to last paragraph - last three sentences - a little verbose &
somewhat redundant.  I think it can be summarized something like the
following:
OLD:
   This document specifies a "built-in dynamic GTSM
   capability negotiation" for LDP to suggest the use of GTSM.  GTSM
   will be used as specified in this document provided both peers on an
   LDP session can detect each others' support for GTSM procedures and
   agree to use it.  That is, the desire to use GTSM (i.e., its
   negotiation mechanics) is enabled by default without any
   configuration.
NEW:
   This document specifies a dynamic GTSM
   capability negotiation mechanism for LDP. This mechanism allows
   both peers on an LDP session to indicate the support and use of GTSM
   without requiring any configuration.


This one I prefer to leave as-is, although appears as redundant in the
surface, it is agreed and crafted with some precision.


2) Section 2.2, 1st para, last sentence: "and RECOMMENDED" -> "and are
RECOMMENDED"


Done. Thanks again.

Adrian, I have these editorials in the working copy committed. I can submit
a new rev at your request.

Thanks,

-- Carlos.

--e89a8f234cbf2bfc7404c1bea609
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

And, the response didn&#39;t make it either, of course. =A0<br><br><div cla=
ss=3D"gmail_quote">---------- Forwarded message ----------<br>From: <b clas=
s=3D"gmail_sendername">Carlos Pignataro (cpignata)</b> <span dir=3D"ltr">&l=
t;<a href=3D"mailto:cpignata@cisco.com">cpignata@cisco.com</a>&gt;</span><b=
r>
Date: Mon, Jun 4, 2012 at 8:11 PM<br>Subject: Re: Gen-ART Review:draft-ietf=
-mpls-ldp-gtsm-08.txt<br>To: Mary Barnes &lt;<a href=3D"mailto:mary.ietf.ba=
rnes@gmail.com">mary.ietf.barnes@gmail.com</a>&gt;<br>Cc: &quot;&lt;<a href=
=3D"mailto:draft-ietf-mpls-ldp-gtsm.all@tools.ietf.org">draft-ietf-mpls-ldp=
-gtsm.all@tools.ietf.org</a>&gt;&quot; &lt;<a href=3D"mailto:draft-ietf-mpl=
s-ldp-gtsm.all@tools.ietf.org">draft-ietf-mpls-ldp-gtsm.all@tools.ietf.org<=
/a>&gt;<br>
<br><br><div style=3D"word-wrap:break-word">Mary,<div><br></div><div>Many t=
hanks for the review! Much appreciated -- please see inline:</div><div><br>=
<div><div class=3D"im"><div>On Jun 4, 2012, at 6:34 PM, Mary Barnes wrote:<=
/div>
<br><blockquote type=3D"cite"><div>I am the assigned Gen-ART reviewer for t=
his draft. For background on Gen-ART, please see the FAQ at &lt;<a href=3D"=
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank">=
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.</div>

<div><br></div><div>Document: draft-ietf-mpls-ldp-gtsm-08.txt</div><div>Rev=
iewer: =A0Mary Barnes=A0</div><div>Review Date: =A04 June 2012</div><div>IE=
TF LC End Date: 29 May 2012</div><div>IESG Telechat Date: 07 June 2012</div=
>
<div>
<br></div><div>Summary: =A0Ready with minor nits</div><div><br></div><div>E=
ditorial nits:=A0</div><div><br></div><div>1) Section 1:</div><div>- =A02nd=
 para, last sentence:</div><div>This sentence doesn&#39;t quite parse - it&=
#39;s not normative, so it should either be deleted or reworded. =A0I sugge=
st deleting as I think it&#39;s somewhat superfluous.</div>

<div><br></div></blockquote><div><br></div></div><div>Agreed E_PARSE. I rec=
ommend we do not delete because it introduces the concept that this is for =
Basic Discovery. However, suggest:</div><div><br></div><div><div>=A0 =A0The=
refore, GTSM can fully benefit LDP protocol peering session</div>
<div>=A0 =A0established using Basic Discovery.</div><div><br></div><div>to:=
</div><div><br></div><div><div>=A0 =A0Therefore, GTSM can protect an LDP pr=
otocol peering session</div><div>=A0 =A0established using Basic Discovery.<=
/div></div>
<div><br></div></div><div>Thank you.</div><div class=3D"im"><br><blockquote=
 type=3D"cite"><div>- Next to last paragraph - last three sentences - a lit=
tle verbose &amp; somewhat redundant. =A0I think it can be summarized somet=
hing like the following:</div>
<div>OLD:</div><div>=A0 =A0This document specifies a &quot;built-in dynamic=
 GTSM</div>
<div>=A0 =A0capability negotiation&quot; for LDP to suggest the use of GTSM=
. =A0GTSM</div><div>=A0 =A0will be used as specified in this document provi=
ded both peers on an</div><div>=A0 =A0LDP session can detect each others&#3=
9; support for GTSM procedures and</div>

<div>=A0 =A0agree to use it. =A0That is, the desire to use GTSM (i.e., its<=
/div><div>=A0 =A0negotiation mechanics) is enabled by default without any</=
div><div>=A0 =A0configuration.</div><div>NEW:</div><div>=A0 =A0This documen=
t specifies a dynamic GTSM</div>

<div>=A0 =A0capability negotiation mechanism for LDP. This mechanism allows=
=A0</div><div>=A0 =A0both peers on an LDP session to indicate the support a=
nd use of GTSM=A0</div><div>=A0 =A0without requiring any configuration.=A0<=
/div></blockquote>
<div><br></div></div><div>This one I prefer to leave as-is, although appear=
s as redundant in the surface, it is agreed and crafted with some precision=
.</div><div class=3D"im"><br><blockquote type=3D"cite"><div><br>
</div><div>2) Section 2.2, 1st para, last sentence: &quot;and RECOMMENDED&q=
uot; -&gt; &quot;and are RECOMMENDED&quot;</div><div><br></div></blockquote=
><div><br></div></div>Done. Thanks again.</div><div><br></div><div>Adrian, =
I have these editorials in the working copy committed. I can submit a new r=
ev at your request.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>-- Carlos.</div><div><=
br><blockquote type=3D"cite"><div><br></div><div>=A0 =A0=A0</div><div><br><=
/div>
</blockquote></div><br></div></div></div><br>

--e89a8f234cbf2bfc7404c1bea609--
--e89a8f234cbf2bfc8004c1bea60b
Content-Type: application/pgp-signature; name="signature.asc"
Content-Disposition: attachment; filename="signature.asc"
Content-Transfer-Encoding: base64
X-Attachment-Id: adfbccd46a6236f5_0.1

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZlcnNpb246IEdudVBHL01hY0dQRzIgdjIu
MC4xNyAoRGFyd2luKQ0KDQppRVlFQVJFQ0FBWUZBay9OWE44QUNna1F0ZkRQR1RwM1VTeVQ3Z0Nj
REhpMkFjZHA3RGpLeVNYdVg0cXJlSWdKDQpXS01BbmkxSkEvODFVSlBPcGRlQ1pIcHhpRHFzZjdj
Ng0KPTFTS1UNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K
--e89a8f234cbf2bfc8004c1bea60b--

From brian.e.carpenter@gmail.com  Wed Jun  6 03:36:48 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00A9B21F87F7 for <gen-art@ietfa.amsl.com>; Wed,  6 Jun 2012 03:36:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.149
X-Spam-Level: 
X-Spam-Status: No, score=-103.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NomP45Og+W-w for <gen-art@ietfa.amsl.com>; Wed,  6 Jun 2012 03:36:47 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id C293421F87F9 for <gen-art@ietf.org>; Wed,  6 Jun 2012 03:36:41 -0700 (PDT)
Received: by eekd4 with SMTP id d4so2429508eek.31 for <gen-art@ietf.org>; Wed, 06 Jun 2012 03:36:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=RSGRllJs/zg1dt6pQZE0uHf+JiGR3NrZqRNlmgOeqec=; b=DIFvzINefAvCgV9CiCWL3yzJuqB2W7YqWvmXC3TvYXVielFtnP+KfeWwkmZ0IOk5VI LzNmoSV1G//j2UURzmZfxONysmFlK5BJLdPm4UGQSiavqlvmo2fhoCl3YZRZRHk9tSKc OQRe7lXOGcwIyP6ekwTTt6ygqM69Fq/yvrl9XrxkwPiLbiTjo5f8jO7jgHGGDPqyK4bR SvhXkg3gW8X+JDDcnSAZoNYe8vp2mDElIspZESPQXz7onTfc7Hqz8JLg2xhcDImGQ4JH JGQL/klKzT+4QidFUUaw++NoA3adNfKvzcjV3OFI+LDof7GzHX4X/G6rvldj9PpMJ7g4 Orbg==
Received: by 10.14.186.14 with SMTP id v14mr9164266eem.49.1338979000888; Wed, 06 Jun 2012 03:36:40 -0700 (PDT)
Received: from [128.232.110.88] (c088.al.cl.cam.ac.uk. [128.232.110.88]) by mx.google.com with ESMTPS id s47sm4878169eef.4.2012.06.06.03.36.39 (version=SSLv3 cipher=OTHER); Wed, 06 Jun 2012 03:36:40 -0700 (PDT)
Message-ID: <4FCF32B5.7010102@gmail.com>
Date: Wed, 06 Jun 2012 11:36:37 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-spfbis-experiment.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------070508040606040605060709"
Subject: [Gen-art] Gen-ART LC review of draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 10:36:48 -0000

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

Please see attached review.

--------------070508040606040605060709
Content-Type: text/plain;
 name="draft-ietf-spfbis-experiment-09-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-spfbis-experiment-09-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBM
YXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IGRyYWZ0
LWlldGYtc3BmYmlzLWV4cGVyaW1lbnQtMDkudHh0DQpSZXZpZXdlcjogQnJpYW4gQ2FycGVu
dGVyDQpSZXZpZXcgRGF0ZTogMjAxMi0wNi0wNg0KSUVURiBMQyBFbmQgRGF0ZTogMjAxMi0w
Ni0wOQ0KSUVTRyBUZWxlY2hhdCBkYXRlOiANCg0KU3VtbWFyeTogIEFsbW9zdCByZWFkeQ0K
LS0tLS0tLS0NCg0KQ29tbWVudDoNCi0tLS0tLS0tDQoNCkkgdGhpbmsgdGhlIENvbmNsdXNp
b25zIGFuZCBBcHBlbmRpeCBBIGFyZSBhbG1vc3QgZW50aXJlbHkgY29ycmVjdC4NCg0KTWFq
b3IgaXNzdWVzOg0KLS0tLS0tLS0tLS0tLQ0KDQpJTUhPIHNlY3Rpb24gMy4xIG5lZWRzIHNl
dmVyYWwgY2xhcmlmaWNhdGlvbnM6DQoNCiJUaGVzZSBzdXJ2ZXlzIHNlbGVjdGVkIHN1YnN0
YW50aWFsIHNldHMgb2YgZGlzdGluY3QgZG9tYWluIG5hbWVzLi4uIg0KDQpXZXJlIHRoZXNl
IGV4Y2x1c2l2ZWx5IGRvbWFpbiBuYW1lcyB3aXRoIE1YIHJlY29yZHM/DQoNCkFsc28gaW4g
c2VjdGlvbiAzLjEgdGhlcmUgYXJlIHNldmVyYWwgdGFibGVzIGxpa2U6IA0KDQogICAgIist
LS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0rLS0tLS0tLSsNCiAgICAgfCBEb21haW5z
IHF1ZXJpZWQgIHwgMSwwMDAsMDAwIHwgICAtICAgfA0KICAgICB8IFRYVCByZXBsaWVzICAg
ICAgfCAgIDM5Nyw1MTEgfCAzOS44JSB8DQogICAgIHwgU1BGIHJlcGxpZXMgICAgICB8ICAg
ICA2LDYyNyB8IDwxLjAlIHwNCiAgICAgfCBTUEYrVFhUIHJlcGxpZXMgIHwgICAgIDYsNjAz
IHwgPDEuMCUgfA0KICAgICB8IHNwZjIuMC8qIHJlcGxpZXMgfCAgICAgNSwyOTEgfCA8MS4w
JSB8DQogICAgICstLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0rLS0tLS0tLSsiDQoN
Ckl0IGlzIG5vdCBleHBsYWluZWQgd2hhdCBpcyBtZWFudCBieSAiVFhUIHJlcGxpZXMiIGFu
ZCAiU1BGK1RYVCByZXBsaWVzIi4NCg0KRG9lcyAiVFhUIHJlcGxpZXMiIG1lYW4gKmFueSog
a2luZCBvZiBUWFQgcmVjb3JkLCBvciBvbmx5IFRYVCByZWNvcmRzIHRoYXQNCnN0YXJ0IHdp
dGggInY9c3BmIj8gDQoNCkRvZXMgIlNQRitUWFQgcmVwbGllcyIgbWVhbiB0aGF0IGJvdGgg
YW4gU1BGIGFuZCBhIFRYVCByZWNvcmQgZXhpc3RzIGZvciB0aGVzZQ0KRlFETnM/IElmIHNv
LCBhcmUgdGhleSBpZGVudGljYWw/IChQcmVzdW1hYmx5IHRoZXkgc2hvdWxkIGJlLikNCg0K
QXQgdGhlIG1vbWVudCBJIGNhbid0IGZ1bGx5IHVuZGVyc3RhbmQgdGhlIHNpZ25pZmljYW5j
ZSBvZiB0aGUgcmVzdWx0cy4NCg0KQWxzbywgUkZDNDQwNiBzdGF0ZXMgdGhhdCAiU2VuZGlu
ZyBkb21haW5zIE1BWSBwdWJsaXNoIGVpdGhlciBvciBib3RoIGZvcm1hdHMiDQooaS5lLiBz
cGYxIG9yIHNwZjIuMCkuIFRoYXQgYmVpbmcgc28sIEkgd291bGQgaWRlYWxseSBleHBlY3Qg
dG8gc2VlIG5pbmUgcm93cw0KaW4gdGhlIHJlc3VsdHMgdGFibGU6DQoNClNQRiBSUiBvbmx5
LCBzcGYxIG9ubHkNClNQRiBSUiBvbmx5LCBzcGYyLjAgb25seQ0KU1BGIFJSIG9ubHksIHNw
ZjEgYW5kIHNwZjIuMA0KVFhUIFJSIG9ubHksIHNwZjEgb25seQ0KVFhUIFJSIG9ubHksIHNw
ZjIuMCBvbmx5DQpUWFQgUlIgb25seSwgc3BmMSBhbmQgc3BmMi4wDQpTUEYgYW5kIFRYVCBS
UnMsIHNwZjEgb25seQ0KU1BGIGFuZCBUWFQgUlJzLCBzcGYyLjAgb25seQ0KU1BGIGFuZCBU
WFQgUlJzLCBzcGYxIGFuZCBzcGYyLjANCg0KSXQncyBwb3NzaWJsZSB0aGF0IHNvbWUgb2Yg
dGhlc2UgYXJlIGFsd2F5cyB6ZXJvIGJ1dCB0aGVyZSBpcyBubyB3YXkgZm9yIGEgcmVhZGVy
DQp0byB0ZWxsLiBUaGlzIHJlbGF0ZXMgdG8gdGhlIGJyZWFrYWdlIGluIHRoZSBTUEYgdHJh
bnNpdGlvbiBwbGFuIHRoYXQgdGhlIGRyYWZ0DQpwb2ludHMgb3V0IChBcHBlbmRpeCBBLCBi
dWxsZXQgNCkuDQoNCkZpbmFsbHksIGluIEFwcGVuZGl4IEEgd2UgZmluZDoNCg0KICAiRm9y
dHVuYXRlbHkgaW4gdGhlIGludGVydmVuaW5nIHRpbWUsIHRoZSByZXF1aXJlbWVudHMgZm9y
IG5ldyBSUlRZUEUNCiAgIGFzc2lnbm1lbnRzIHdhcyBjaGFuZ2VkIHRvIEV4cGVydCBSZXZp
ZXcsIGFuZCB0aGUgcG9zdHVyZSBoYXMgYmVjb21lDQogICBtb3JlIHJlbGF4ZWQuIg0KDQpU
aGlzIGlzIHNsaWdodGx5IGluYWNjdXJhdGUuIEFjdHVhbGx5IHRoZSBwb2xpY3kgaGFzIGJl
ZW4gY2hhbmdlZCB0bw0KUkZDNjE5NSwgd2hpY2ggaXMgYSBtb2RpZmllZCBmb3JtIG9mIEV4
cGVydCBSZXZpZXcuIEkgc3VnZ2VzdCBzb21ldGhpbmcNCmxlc3Mgb3BpbmlvbmF0ZWQ6DQoN
CiAgIEZvcnR1bmF0ZWx5IGluIHRoZSBpbnRlcnZlbmluZyB0aW1lLCB0aGUgcmVxdWlyZW1l
bnRzIGZvciBuZXcgUlJUWVBFDQogICBhc3NpZ25tZW50cyB3YXMgY2hhbmdlZCB0byBiZSBs
ZXNzIHN0cmluZ2VudCBbUkZDNjE5NV0uDQoNCk5pdHMNCi0tLS0NCg0KIjkuMS4gIE5vcm1h
dGl2ZSBSZWZlcmVuY2VzDQoNCiAgIFtETlNdICAgICAgTW9ja2FwZXRyaXMsIFAuLCAiRG9t
YWluIG5hbWVzIC0gaW1wbGVtZW50YXRpb24gYW5kDQogICAgICAgICAgICAgIHNwZWNpZmlj
YXRpb24iLCBTVEQgMTMsIFJGQyAxMDM1LCBOb3ZlbWJlciAxOTg3Lg0KDQogICBbUFJBXSAg
ICAgIEx5b24sIEouLCAiUHVycG9ydGVkIFJlc3BvbnNpYmxlIEFkZHJlc3MgaW4gRS1NYWls
DQogICAgICAgICAgICAgIE1lc3NhZ2VzIiwgUkZDIDQ0MDcsIEFwcmlsIDIwMDYuIg0KDQpG
aXJzdGx5LCBpdCdzIHF1aXRlIGluY29udmVuaWVudCBoYXZpbmcgcmVmZXJlbmNlcyBsaWtl
IHRoaXMNCmluc3RlYWQgb2YgW1JGQzEwMzVdIGV0Yy4NCg0KU2Vjb25kbHksIGl0IGRvZXNu
J3Qgc2VlbSByaWdodCB0byBoYXZlIEV4cGVyaW1lbnRhbCBSRkNzIGxpc3RlZA0KYXMgbm9y
bWF0aXZlIHJlZmVyZW5jZXMuIEluIGZhY3QsIHNpbmNlIHRoaXMgZHJhZnQgaXMgbm90IGEg
dGVjaG5pY2FsDQpzcGVjaWZpY2F0aW9uLCBJJ20gbm90IHN1cmUgaXQgbmVlZHMgdG8gaGF2
ZSB0aGUgTm9ybWF0aXZlL0luZm9ybWF0aXZlDQpzcGxpdCBhdCBhbGwuDQoNCg0KDQo=
--------------070508040606040605060709--

From Francis.Dupont@fdupont.fr  Wed Jun  6 14:49:49 2012
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7327B21F8516 for <gen-art@ietfa.amsl.com>; Wed,  6 Jun 2012 14:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uodpbVBLoSJW for <gen-art@ietfa.amsl.com>; Wed,  6 Jun 2012 14:49:49 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id A0AE221F84FE for <gen-art@ietf.org>; Wed,  6 Jun 2012 14:49:48 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id q56LnlJ4086365; Wed, 6 Jun 2012 23:49:47 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201206062149.q56LnlJ4086365@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Wed, 06 Jun 2012 23:49:47 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-v6ops-ra-guard-implementation.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-v6ops-ra-guard-implementation-04.txt (summary)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 21:49:49 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-v6ops-ra-guard-implementation-04.txt
Reviewer: Francis Dupont
Review Date: 20120606
IETF LC End Date: 20120612
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: I am currently at a conference so I have not the time to type
the few comments now.

Thanks

Francis.Dupont@fdupont.fr

From trammell@tik.ee.ethz.ch  Wed Jun  6 15:57:34 2012
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2E4911E8088 for <gen-art@ietfa.amsl.com>; Wed,  6 Jun 2012 15:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52zdHqVsjdEr for <gen-art@ietfa.amsl.com>; Wed,  6 Jun 2012 15:57:34 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 0F1D011E8087 for <gen-art@ietf.org>; Wed,  6 Jun 2012 15:57:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 6EB10D9307; Thu,  7 Jun 2012 00:57:32 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KStrsE2eFrGd; Thu,  7 Jun 2012 00:57:32 +0200 (MEST)
Received: from vpn-global-dhcp3-200.ethz.ch (vpn-global-dhcp3-200.ethz.ch [129.132.210.200]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 3DFC4D9300; Thu,  7 Jun 2012 00:57:30 +0200 (MEST)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <4FCE2B6C.1010704@ericsson.com>
Date: Thu, 7 Jun 2012 00:57:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1EE04451-B5F5-4A55-A1F2-3D9165BF732B@tik.ee.ethz.ch>
References: <4FCE2B6C.1010704@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1278)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mile-iodef-xmlreg.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-mile-iodef-xmlreg-01.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 22:57:34 -0000

Hi, Suresh,

Thanks for the comment; yes, this one is a bit hard to parse (even for =
me, and I tend to write page-length sentences). I've tweaked your =
suggested text somewhat and applied to the current working copy of the =
-02 revision.

Best regards,

Brian

On Jun 5, 2012, at 5:53 PM, Suresh Krishnan wrote:

> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft (for background on Gen-ART, please see
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-mile-iodef-xmlreg-01.txt
> Reviewer: Suresh Krishnan
> Review Date: 2012/06/07
> IESG Telechat date: 2012/06/05
>=20
> Summary: This document is ready for publication as a Proposed Standard =
but I have a comment.
>=20
> Minor
> =3D=3D=3D=3D=3D
>=20
> * Introduction:
>=20
> The first sentence is too complex and very difficult to parse. Please =
consider breaking it up. I have proposed some changed text, but feel =
free to ignore if it changes the meaning of what you wanted to convey.
>=20
> OLD:
> IODEF extensions via class extension through AdditionalData and
> RecordItem elements, as per section 5.2 of [RFC5070], generally
> register their namespaces and schemas with the IANA XML Namespace
> registry at http://www.iana.org/assignments/xml-registry/ns.html and
> the IANA XML Schema registry at
> http://www.iana.org/assignments/xml-registry/schema.html,
> respectively [RFC3688].
>=20
> NEW:
> The classes of the IODEF data model can be extended by the use of
> AdditionalData and RecordItem elements, as per section 5.2 of =
[RFC5070].
> IODEF extensions that use such extended classes register their =
namespaces and schemas with the IANA XML Namespace
> registry at http://www.iana.org/assignments/xml-registry/ns.html and
> the IANA XML Schema registry at
> http://www.iana.org/assignments/xml-registry/schema.html,
> respectively [RFC3688].
>=20
>=20
> Thanks
> Suresh
>=20
>=20
>=20
>=20


From sm@elandsys.com  Wed Jun  6 22:35:07 2012
Return-Path: <sm@elandsys.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEC5511E8106; Wed,  6 Jun 2012 22:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.24
X-Spam-Level: 
X-Spam-Status: No, score=-102.24 tagged_above=-999 required=5 tests=[AWL=-0.241, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W358Ath1yNlg; Wed,  6 Jun 2012 22:35:05 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 904E311E8104; Wed,  6 Jun 2012 22:35:05 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.235.116]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q575YjEA017146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Jun 2012 22:34:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1339047299; i=@elandsys.com; bh=qJi/u4g2/z5hofWlYU4LmfpJQPeXH97x+n5BZZuIbWA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=m/L0QgGEtqg+SIBpvRJY/9Pws0pCfJbTuE5+I6sjCVovGorHG+7SyZjcvhJRaqyoe Yq8xLJyl4e7Hq/GZShiihmJ7WOo1RM93WszokW1P9RYCZAAK7KGEHf3hQpSy8Imnog wctyvT21+NkrB47GPw26gNj3VoQwxmICCklpjHBE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1339047299; i=@elandsys.com; bh=qJi/u4g2/z5hofWlYU4LmfpJQPeXH97x+n5BZZuIbWA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gcpBr/MX8W1Z+1nuNAzm2xdxuBJtgpuckj9osQiIg8C3lIeAtJ+rhYpW3xappCCcn 3iunAMgsHafqQFfTNht1uQFBXjbLS0SwQ22OK7hTpmpH3BK90lbPvZcr1I0qIALia3 DgjBaXI/YU9x85nO+2FNHqQKzV2DkvWSqumSgT9U=
Message-Id: <6.2.5.6.2.20120606215706.0aa1d6c0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 06 Jun 2012 22:28:40 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, General Area Review Team <gen-art@ietf.org>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <4FCF32B5.7010102@gmail.com>
References: <4FCF32B5.7010102@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: spfbis@ietf.org, draft-ietf-spfbis-experiment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 05:35:07 -0000

Hi Brian,
At 03:36 06-06-2012, Brian E Carpenter wrote:
>Please see attached review.

Thanks for the review.

>I think the Conclusions and Appendix A are almost entirely correct.
>
>Major issues:
>-------------
>
>IMHO section 3.1 needs several clarifications:
>
>"These surveys selected substantial sets of distinct domain names..."
>
>Were these exclusively domain names with MX records?

They're domain names seen on incoming email in some way.  Murray 
doesn't believe that it is important to state that.  If you think it 
is important, let me know.

>Also in section 3.1 there are several tables like:
>
>     "+------------------+-----------+-------+
>      | Domains queried  | 1,000,000 |   -   |
>      | TXT replies      |   397,511 | 39.8% |
>      | SPF replies      |     6,627 | <1.0% |
>      | SPF+TXT replies  |     6,603 | <1.0% |
>      | spf2.0/* replies |     5,291 | <1.0% |
>      +------------------+-----------+-------+"
>
>It is not explained what is meant by "TXT replies" and "SPF+TXT replies".
>
>Does "TXT replies" mean *any* kind of TXT record, or only TXT records that
>start with "v=spf"?

It's a fair question.  The draft will be updated to fix that.

>Does "SPF+TXT replies" mean that both an SPF and a TXT record exists for these
>FQDNs? If so, are they identical? (Presumably they should be.)

Yes to the first question.  The working group didn't evaluate the second.

>At the moment I can't fully understand the significance of the results.
>
>Also, RFC4406 states that "Sending domains MAY publish either or both formats"
>(i.e. spf1 or spf2.0). That being so, I would ideally expect to see nine rows
>in the results table:
>
>SPF RR only, spf1 only
>SPF RR only, spf2.0 only
>SPF RR only, spf1 and spf2.0
>TXT RR only, spf1 only
>TXT RR only, spf2.0 only
>TXT RR only, spf1 and spf2.0
>SPF and TXT RRs, spf1 only
>SPF and TXT RRs, spf2.0 only
>SPF and TXT RRs, spf1 and spf2.0

Pete suggests having two tables for each survey: (a) a comparison of 
RRTYPEs, and (b) a comparison of SPF vs. SIDF independent of 
RRTYPE.  Would that be sufficient?

>It's possible that some of these are always zero but there is no way 
>for a reader
>to tell. This relates to the breakage in the SPF transition plan 
>that the draft
>points out (Appendix A, bullet 4).
>
>Finally, in Appendix A we find:
>
>   "Fortunately in the intervening time, the requirements for new RRTYPE
>    assignments was changed to Expert Review, and the posture has become
>    more relaxed."
>
>This is slightly inaccurate. Actually the policy has been changed to
>RFC6195, which is a modified form of Expert Review. I suggest something
>less opinionated:
>
>    Fortunately in the intervening time, the requirements for new RRTYPE
>    assignments was changed to be less stringent [RFC6195].

This is slightly inaccurate.  Actually the policy has been changed to 
RFC6195, which is a modified form of Expert Review. Murray suggests 
something less opinionated:

   Fortunately in the intervening time, the requirements for new RRTYPE
   assignments was changed to be less stringent [RFC6195].

>Nits
>----
>
>"9.1.  Normative References
>
>    [DNS]      Mockapetris, P., "Domain names - implementation and
>               specification", STD 13, RFC 1035, November 1987.
>
>    [PRA]      Lyon, J., "Purported Responsible Address in E-Mail
>               Messages", RFC 4407, April 2006."
>
>Firstly, it's quite inconvenient having references like this
>instead of [RFC1035] etc.

Here's Andrew's response as WG Chair:  This isn't a change anyone 
needs to make, it's a style complaint.  The editor preferred to use 
the symbolic-reference style, and the reviewer prefers the RFC-named 
style.  He also personally prefer the latter, but the RFC Editor 
doesn't have a rule.

Murray finds the mnemonic method in use easier to read.

>Secondly, it doesn't seem right to have Experimental RFCs listed
>as normative references. In fact, since this draft is not a technical
>specification, I'm not sure it needs to have the Normative/Informative
>split at all.

Dave Crocker and Barry Leiba had an discussion about "normative 
references" at 
http://www.ietf.org/mail-archive/web/spfbis/current/msg01426.html.

Even though the draft is not a technical specification, it is 
important that the reader reads the RFCs listed as normative to 
understand the draft.  The Experimental RFCs are not even a downward 
reference in this case as this draft is not being published on the 
Standards Track.

Regards,
S. Moonesamy (as document shepherd) 


From brian.e.carpenter@gmail.com  Thu Jun  7 00:26:40 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC6821F85EA; Thu,  7 Jun 2012 00:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.671
X-Spam-Level: 
X-Spam-Status: No, score=-101.671 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gNgrPI2xtTzG; Thu,  7 Jun 2012 00:26:40 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id A1D8A21F8541; Thu,  7 Jun 2012 00:26:39 -0700 (PDT)
Received: by eekd4 with SMTP id d4so109452eek.31 for <multiple recipients>; Thu, 07 Jun 2012 00:26:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zpbe70X/utG+0dbvqr9dC6TknxtCoG3EDikz6M0giVo=; b=p5+A/c8tBHoCG1nMLC0zOo8g8CeFSjWpGu+qQE4rPrvHWIKdL6c/TZq5n8pWZyTArL fqv9/bZ9IFh0Kn0cXZuw6sY9ZCol7BxVxJsWekYToHVIL54EDPyfovZDSEmYTvQol9kz Mmpv+baPQXkLJqPNEVB2mTMfmoh6vofdWUMCt7irqC0B99+otrJwJWDkjgvea7srIreO 6mq/DzQ9uK7IZ9zhz3+fqHwPY351v/KclFHmRt+EPyzoge+FmvB5xD2dpSxTA8GaUwp9 hfiQbl9wojaskebuhwNoCcdFn6GASLN/NRXkGB3smgpQFtHc4nB7Vbq/jdNp3mgPLBir ghdw==
Received: by 10.14.97.77 with SMTP id s53mr522331eef.104.1339053998746; Thu, 07 Jun 2012 00:26:38 -0700 (PDT)
Received: from [192.168.1.66] (host-2-102-217-102.as13285.net. [2.102.217.102]) by mx.google.com with ESMTPS id c13sm7585924eeb.7.2012.06.07.00.26.36 (version=SSLv3 cipher=OTHER); Thu, 07 Jun 2012 00:26:37 -0700 (PDT)
Message-ID: <4FD057A2.5060909@gmail.com>
Date: Thu, 07 Jun 2012 08:26:26 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
References: <4FCF32B5.7010102@gmail.com> <6.2.5.6.2.20120606081749.0a94ad98@elandnews.com> <CAC4RtVCXvE0htGxpqQfCKiTzgdnofjzLM6SAQz=kwTBu8Ako4g@mail.gmail.com> <6.2.5.6.2.20120606122623.088e6170@elandnews.com>
In-Reply-To: <6.2.5.6.2.20120606122623.088e6170@elandnews.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: spfbis@ietf.org, General Area Review Team <gen-art@ietf.org>, Barry Leiba <barryleiba@computer.org>, draft-ietf-spfbis-experiment.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART LC review of draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 07:26:40 -0000

Restoring the Gen-ART CC since we need the discussion in the archive.

See below...

On 2012-06-06 20:43, S Moonesamy wrote:
> Hi Barry,
> At 12:23 06-06-2012, Barry Leiba wrote:
>> Leaving the entire message below, because Brian doesn't appear to have
>> been copied on it.
> 
> I didn't copy Brian as I thought it better to wait for a WG reply.
> 
>> I don't see why it's not right at all, and please don't make the
>> mistake of thinking that an informational document doesn't have
>> normative references.  I think the original Experimental docs are
>> *absolutely* normative references for this document, and i see nothing
>> wrong with that at all.
> 
> The comment posted by Dave is at
> http://www.ietf.org/mail-archive/web/spfbis/current/msg01426.html
> 
> I generally use the following for guidance:
> 
>   "Normative references specify documents that must be read to
>    understand or implement the technology in the new RFC, or
>    whose technology must be present for the technology in the
>    new RFC to work."

Exactly. This draft does not define new technology, is not a
technical specification (cf RFC 2026), and therefore does not
need normative references.

    Brian

> 
> Regards
> S. Moonesamy
> 
> .
> 

From brian.e.carpenter@gmail.com  Thu Jun  7 00:35:20 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A7BC21F864A; Thu,  7 Jun 2012 00:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.372
X-Spam-Level: 
X-Spam-Status: No, score=-101.372 tagged_above=-999 required=5 tests=[AWL=-0.281, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8MDSWRhwXdax; Thu,  7 Jun 2012 00:35:19 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id B7F1A21F8648; Thu,  7 Jun 2012 00:35:18 -0700 (PDT)
Received: by eaaq13 with SMTP id q13so110889eaa.31 for <multiple recipients>; Thu, 07 Jun 2012 00:35:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UCi8a9fQMU7zs+fINcq4f00hKhTbXC9pA1BqWoIwhoY=; b=STLTta5jFzHg4cbjTtQf0l3ZJAFUzFJI3zYY9fKb4/1BGPNi7EDXI1sPzi3acm6+RN rcVlJee+ncG8R/WnGHzMtWNiB1ch5iSbJor8JiLn3ocbPKbGKn0WVF9+2GybdGsqExnp NzYjoyOiSHFY/blT4AOE8wKjOq1+JMYtJvRvgqL7Q08Kwv9MBhxHAghKcwom7cgMlOb7 ns5EvMiRbM4Ygrxd86aO1ExTw3KYDNdGI9YSl15qPRfFwJrl/+0vxUWLzqnXnsdM6nzu ErsG5cpKnoJULLH3K7stAYhvZ6p5KzD/7tBgS+CQV0L/S2o/mVrg4rOVNW1n+6FJC7gL mAQg==
Received: by 10.14.188.4 with SMTP id z4mr632975eem.228.1339054517813; Thu, 07 Jun 2012 00:35:17 -0700 (PDT)
Received: from [192.168.1.66] (host-2-102-217-102.as13285.net. [2.102.217.102]) by mx.google.com with ESMTPS id c51sm7630278eei.12.2012.06.07.00.35.16 (version=SSLv3 cipher=OTHER); Thu, 07 Jun 2012 00:35:16 -0700 (PDT)
Message-ID: <4FD059B0.9020900@gmail.com>
Date: Thu, 07 Jun 2012 08:35:12 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>
References: <4FCF32B5.7010102@gmail.com>	<6.2.5.6.2.20120606081749.0a94ad98@elandnews.com>	<CAL0qLwayGFRMH29k_Tc6PXUD1zFNs3Uo5j87Eo_HYJVGeuBGsA@mail.gmail.com> <CAL0qLwZn8_PWQsYNnn4VVKRjf5CneyJMTiu0q9KFpqWNELhgVA@mail.gmail.com>
In-Reply-To: <CAL0qLwZn8_PWQsYNnn4VVKRjf5CneyJMTiu0q9KFpqWNELhgVA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: spfbis@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-ietf-spfbis-experiment.all@tools.ietf.org
Subject: Re: [Gen-art] Fwd: [spfbis] Gen-ART LC review of draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 07:35:20 -0000

Restoring the Gen-ART CC since we need the discussion in the archive.

Thanks Murray, see below...

On 2012-06-07 06:12, Murray S. Kucherawy wrote:
> For some reason you were dropped from the Cc: list.  Forwarding for your
> consideration.
> 
> ---------- Forwarded message ----------
> From: Murray S. Kucherawy <superuser@gmail.com>
> Date: Wed, Jun 6, 2012 at 9:50 PM
> Subject: Re: [spfbis] Gen-ART LC review of
> draft-ietf-spfbis-experiment-09.txt
> To: S Moonesamy <sm+ietf@elandsys.com>
> Cc: spfbis@ietf.org, draft-ietf-spfbis-experiment.all@tools.ietf.org
> 
> 
> On Wed, Jun 6, 2012 at 8:30 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 
>> -------------
>>> IMHO section 3.1 needs several clarifications:
>>>
>>> "These surveys selected substantial sets of distinct domain names..."
>>>
>>> Were these exclusively domain names with MX records?
>>>
> Is that an important thing to state?  I don't believe it is.  They're
> domain names seen on incoming email in some way.

OK, it's necessary and sufficient to state that.

> 
>>> Also in section 3.1 there are several tables like:
>>>
>>>    "+------------------+-----------+-------+
>>>     | Domains queried  | 1,000,000 |   -   |
>>>     | TXT replies      |   397,511 | 39.8% |
>>>     | SPF replies      |     6,627 | <1.0% |
>>>     | SPF+TXT replies  |     6,603 | <1.0% |
>>>     | spf2.0/* replies |     5,291 | <1.0% |
>>>     +------------------+-----------+-------+"
>>>
>>> It is not explained what is meant by "TXT replies" and "SPF+TXT replies".
>>>
> The section is discussing RRTYPEs, so TXT refers to TXT RRTYPEs (type 16)
> and SPF refers to SPF RRTYPEs (type 99).

As noted below there are 9 different combinations and you only have 4 rows.
It's ambiguous data.

>>> Does "TXT replies" mean *any* kind of TXT record, or only TXT records that
>>> start with "v=spf"?
>>>
> That's a fair question.  I'll update the draft accordingly.
> 
> 
>>> Does "SPF+TXT replies" mean that both an SPF and a TXT record exists for
>>> these
>>> FQDNs? If so, are they identical? (Presumably they should be.)
>>>
> Yes to the first question.  We didn't evaluate the second.
> 
> 
>>> At the moment I can't fully understand the significance of the results.
>>>
> The picture they're trying to paint is twofold: (a) the uptake of type 99
> records versus type 16 records; and (b) for type 16 records, the number of
> attempts to cause receivers to apply PRA, which is part of Sender ID.
> Substantial uptake of either type 99 records or type 16 records that
> request PRA processing would be an indicator of substantial interest in
> Sender ID.  The data show neither is present.
> 
> 
> 
>>> Also, RFC4406 states that "Sending domains MAY publish either or both
>>> formats"
>>> (i.e. spf1 or spf2.0). That being so, I would ideally expect to see nine
>>> rows
>>> in the results table:
>>>
>>> SPF RR only, spf1 only
>>> SPF RR only, spf2.0 only
>>> SPF RR only, spf1 and spf2.0
>>> TXT RR only, spf1 only
>>> TXT RR only, spf2.0 only
>>> TXT RR only, spf1 and spf2.0
>>> SPF and TXT RRs, spf1 only
>>> SPF and TXT RRs, spf2.0 only
>>> SPF and TXT RRs, spf1 and spf2.0
>>>
> I think this will provide more clutter than clarity.  The answer to the
> over-arching question, namely "Which one has greater uptake?", is already
> available without this breakdown, simply because the number of "spf2.0"
> records is miniscule by comparison to the rest.

Yes, but when presenting data, as in a scientifc paper, you need to be
precise, so that an independent 3rd party could in principle repeat
the measurement and the analysis. That's my problem with the existing
tables.

> So really we need to compare the use of the two RRTYPEs and the use of the
> two protocols independent of the RRTYPEs, since SPF only cared about TXT
> and SIDF could use either.
> 
> Pete suggests having two tables for each survey: (a) a comparison of
> RRTYPEs, and (b) a comparison of SPF vs. SIDF independent of RRTYPE.  Would
> that be sufficient?

Yes, I think that would be much better. I haven't seen Pete's comment
but it sounds as if I would agree with it :-)

   Brian

> 
> 
>>> It's possible that some of these are always zero but there is no way for
>>> a reader
>>> to tell. This relates to the breakage in the SPF transition plan that the
>>> draft
>>> points out (Appendix A, bullet 4).
>>>
>> Major issues:
>>
>>
>> There was a significant comment about Section 3.1 during the AD
>> evaluation.  I'll leave it to Murray to get me the modified text to address
>> this review. :-)
>>
> 
> Right; Pete had roughly the same question but he hasn't asked it on the
> spfbis list yet.  His suggestion is now above, for the record.  :-)
> 
> 
>>  Finally, in Appendix A we find:
>>>  "Fortunately in the intervening time, the requirements for new RRTYPE
>>>   assignments was changed to Expert Review, and the posture has become
>>>   more relaxed."
>>>
>>> This is slightly inaccurate. Actually the policy has been changed to
>>> RFC6195, which is a modified form of Expert Review. I suggest something
>>> less opinionated:
>>>
>>>   Fortunately in the intervening time, the requirements for new RRTYPE
>>>   assignments was changed to be less stringent [RFC6195].
>>>
> OK.
> 
> 
>>> Nits
>>> ----
>>>
>>> "9.1.  Normative References
>>>
>>>   [DNS]      Mockapetris, P., "Domain names - implementation and
>>>              specification", STD 13, RFC 1035, November 1987.
>>>
>>>   [PRA]      Lyon, J., "Purported Responsible Address in E-Mail
>>>              Messages", RFC 4407, April 2006."
>>>
>>> Firstly, it's quite inconvenient having references like this
>>> instead of [RFC1035] etc.
>>>
>> I'll leave it to Andrew to come up with the change to address this. :-)
>>
> 
> I concur with Andrew that this is a stylistic choice.  I find the mnemonic
> method in use easier to read.
> 
> 
>>  Secondly, it doesn't seem right to have Experimental RFCs listed
>>> as normative references. In fact, since this draft is not a technical
>>> specification, I'm not sure it needs to have the Normative/Informative
>>> split at all.
>>>
>> There were some comments about the normative references (see summary at
>> http://www.ietf.org/mail-**archive/web/spfbis/current/**msg01505.html ).
>>  I'll use that as input for the answer if there aren't any comments.
>>
> 
> I concur with Barry's reply to this point.
> 
> -MSK
> 

From hsantos@isdg.net  Thu Jun  7 00:58:14 2012
Return-Path: <hsantos@isdg.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C493321F86AA for <gen-art@ietfa.amsl.com>; Thu,  7 Jun 2012 00:58:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.939
X-Spam-Level: 
X-Spam-Status: No, score=-101.939 tagged_above=-999 required=5 tests=[AWL=0.660, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YOeGeAqkQzHj for <gen-art@ietfa.amsl.com>; Thu,  7 Jun 2012 00:58:13 -0700 (PDT)
Received: from dkim.winserver.com (groups.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id A25E121F8661 for <gen-art@ietf.org>; Thu,  7 Jun 2012 00:58:13 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2465; t=1339055887; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=7A4uiNEzXFiJgPvM7PG6lerFXco=; b=vScTiLVWJhydVWW+CI1z 7PLuPe+Qd2Tm4aArm4MraRCqETT1PZSavZegJ0XuoTQB62g4z3s2LhutOVpgk6ay CHJRQvoLR8GGxd9C1NhPRxgn0EU2O9/dX5LGnGWupiFIWxCenp0ia+fH1ehJhn5E ii37JgZbv8OyiCCOSV1WFts=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for gen-art@ietf.org; Thu, 07 Jun 2012 03:58:07 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3667693180.1481.4780; Thu, 07 Jun 2012 03:58:06 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2465; t=1339055825; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=JKBI5XS TPwUtUPaP9jN7mAfzgodecsblXjV5aGhAEhs=; b=sk1tx18w4ACL3R9K3tLGAQn lGrQ4R9vL4wwwiLoMKSfgrfjuT1ZxO9l/zuP7oQIGY1MyfLsTbhuK8dZZVC+3pJs aREjF6Lq7iTmCfGFOs7LCN3rq8U+DK8sbNiAUNUTDu20yexKzFDKlU1Dyp2DOmkY znINFiutKXvniV1sfq8o=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for gen-art@ietf.org; Thu, 07 Jun 2012 03:57:05 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4266558191.7.7508; Thu, 07 Jun 2012 03:57:04 -0400
Message-ID: <4FD05F2D.8010200@isdg.net>
Date: Thu, 07 Jun 2012 03:58:37 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
References: <4FCF32B5.7010102@gmail.com> <6.2.5.6.2.20120606215706.0aa1d6c0@elandnews.com>
In-Reply-To: <6.2.5.6.2.20120606215706.0aa1d6c0@elandnews.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 07 Jun 2012 02:26:08 -0700
Cc: spfbis@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-ietf-spfbis-experiment.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART LC review of	draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 07:58:14 -0000

S Moonesamy wrote:

>> Brian Carpenter wrote:
>> Also, RFC4406 states that "Sending domains MAY publish either or both 
>> formats" (i.e. spf1 or spf2.0). That being so, I would ideally expect to see 
>> nine rows in the results table:
>>
>> SPF RR only, spf1 only
>> SPF RR only, spf2.0 only
>> SPF RR only, spf1 and spf2.0
>> TXT RR only, spf1 only
>> TXT RR only, spf2.0 only
>> TXT RR only, spf1 and spf2.0
>> SPF and TXT RRs, spf1 only
>> SPF and TXT RRs, spf2.0 only
>> SPF and TXT RRs, spf1 and spf2.0
> 
> Pete suggests having two tables for each survey: (a) a comparison of 
> RRTYPEs, and (b) a comparison of SPF vs. SIDF independent of RRTYPE.  
> Would that be sufficient?

I don't see where this is headed. The report was looking for something 
that was already there and know and I guess it trying to get a 
justification to eliminate something.

What are we looking for?

   Elimination of SPF RR lookups?
   Elimination of SPF2.0 content in the SPF or TXT records?

I hate to revert back to the original design presumptions in MARID, 
but everyone was working on the basis that one day DNS servers, ALL OF 
THEM, CROSS THE OS BOARD, would inevitably be updated to support 
RFC3597 Handling of Unknown DNS Resource Record (RR) Types.  But that 
has not been the case, MS DNS 5.0 was only updated to support SVR, 
DNSSEC. But not the passthru query recursive requirements necessary 
for RFC3597.

So supporting any unnamed RR type is simply not practical today. 
However, as predicted, the migration advice did materialize, abeit in 
short numbers.  So IMO, we need to make a decision if its still 
feasible to pursue unnamed RR type support.

Second and finally, the results of SPF2.0 record is irrelevant because 
this REPORT is not doing anything towards or does it have any business 
in eliminating or providing the "illusion" of eliminating Sender ID or 
SIDF (Sender ID Framework) which includes PRA and SUBMITTER protocol 
support.

This Report has failed to consider the original EXPERIMENTAL questions 
of the so call conflicts that were cited, ones I have failed to see 
since its inception in early 2000s.

Address the real technical issues so that deployments of many years 
can learn what do  do with the mix support of SPF vs SIDF and also TXT 
vs SPF RRs.  The data in this report has not provided any engineering 
insight whatsoever other than the fact that clients DO support both 
SIDF and SPF RRs.

-- 
HLS



From brian.e.carpenter@gmail.com  Thu Jun  7 06:28:13 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6472321F8702; Thu,  7 Jun 2012 06:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.661
X-Spam-Level: 
X-Spam-Status: No, score=-101.661 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f8bORCiq3DiL; Thu,  7 Jun 2012 06:28:13 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD0421F8700; Thu,  7 Jun 2012 06:28:12 -0700 (PDT)
Received: by eekd4 with SMTP id d4so283977eek.31 for <multiple recipients>; Thu, 07 Jun 2012 06:28:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/ENRrTyPclIPcdzvqrUrdD2jUNnIRIHcxnaCh5M/El4=; b=wU3A5Lg471CriDNnhm+p4zUpVyAKUapnr17FuUV4v+S5WNYUuOn2jbAPcN4wL0ciJs rgf9yqNl6M8Xjh51Atx/HeGl3STLJuOT+lg4HRtFkYX0jgQ+pTteHDhwZP0afgsUN3W1 cZhKopPT9/bcBolZ4hgQm7UDXDeXk3KlCvGLntQNKR6oijM+EKMmdc3IVSATb+qXAFwg yzGe1Xp0xqYkoStBt5MTcYGtBnhkn+TIU6ARXO3KWHGgZsfRJp4D1ol68V3EaRSyL2kd 3NQq8JYwl7Bq37eM1rcizNH/45tfw/EbpUdT0W/jlR2UW1VBmctV3h8f2tdJdaG7749h uPgw==
Received: by 10.14.189.14 with SMTP id b14mr1233236een.141.1339075691501; Thu, 07 Jun 2012 06:28:11 -0700 (PDT)
Received: from [192.168.1.66] (host-2-102-217-102.as13285.net. [2.102.217.102]) by mx.google.com with ESMTPS id m5sm10884565eeh.17.2012.06.07.06.28.09 (version=SSLv3 cipher=OTHER); Thu, 07 Jun 2012 06:28:10 -0700 (PDT)
Message-ID: <4FD0AC66.50602@gmail.com>
Date: Thu, 07 Jun 2012 14:28:06 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hector Santos <hsantos@isdg.net>
References: <4FCF32B5.7010102@gmail.com> <6.2.5.6.2.20120606215706.0aa1d6c0@elandnews.com> <4FD05F2D.8010200@isdg.net>
In-Reply-To: <4FD05F2D.8010200@isdg.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: spfbis@ietf.org, General Area Review Team <gen-art@ietf.org>, S Moonesamy <sm+ietf@elandsys.com>, draft-ietf-spfbis-experiment.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART LC review of	draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 13:28:13 -0000

On 2012-06-07 08:58, Hector Santos wrote:
> S Moonesamy wrote:
> 
>>> Brian Carpenter wrote:
>>> Also, RFC4406 states that "Sending domains MAY publish either or both
>>> formats" (i.e. spf1 or spf2.0). That being so, I would ideally expect
>>> to see nine rows in the results table:
>>>
>>> SPF RR only, spf1 only
>>> SPF RR only, spf2.0 only
>>> SPF RR only, spf1 and spf2.0
>>> TXT RR only, spf1 only
>>> TXT RR only, spf2.0 only
>>> TXT RR only, spf1 and spf2.0
>>> SPF and TXT RRs, spf1 only
>>> SPF and TXT RRs, spf2.0 only
>>> SPF and TXT RRs, spf1 and spf2.0
>>
>> Pete suggests having two tables for each survey: (a) a comparison of
>> RRTYPEs, and (b) a comparison of SPF vs. SIDF independent of RRTYPE. 
>> Would that be sufficient?
> 
> I don't see where this is headed. The report was looking for something
> that was already there and know and I guess it trying to get a
> justification to eliminate something.
> 
> What are we looking for?

I am looking for clear presentation of the observed data, nothing more,
as I do whenever I read a data-based document. As my review stated,
I have no problem with the conclusions drawn in the draft.

   Brian

> 
>   Elimination of SPF RR lookups?
>   Elimination of SPF2.0 content in the SPF or TXT records?
> 
> I hate to revert back to the original design presumptions in MARID, but
> everyone was working on the basis that one day DNS servers, ALL OF THEM,
> CROSS THE OS BOARD, would inevitably be updated to support RFC3597
> Handling of Unknown DNS Resource Record (RR) Types.  But that has not
> been the case, MS DNS 5.0 was only updated to support SVR, DNSSEC. But
> not the passthru query recursive requirements necessary for RFC3597.
> 
> So supporting any unnamed RR type is simply not practical today.
> However, as predicted, the migration advice did materialize, abeit in
> short numbers.  So IMO, we need to make a decision if its still feasible
> to pursue unnamed RR type support.
> 
> Second and finally, the results of SPF2.0 record is irrelevant because
> this REPORT is not doing anything towards or does it have any business
> in eliminating or providing the "illusion" of eliminating Sender ID or
> SIDF (Sender ID Framework) which includes PRA and SUBMITTER protocol
> support.
> 
> This Report has failed to consider the original EXPERIMENTAL questions
> of the so call conflicts that were cited, ones I have failed to see
> since its inception in early 2000s.
> 
> Address the real technical issues so that deployments of many years can
> learn what do  do with the mix support of SPF vs SIDF and also TXT vs
> SPF RRs.  The data in this report has not provided any engineering
> insight whatsoever other than the fact that clients DO support both SIDF
> and SPF RRs.
> 

From ale.whop@gmail.com  Thu Jun  7 09:35:33 2012
Return-Path: <ale.whop@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4FA21F8826; Thu,  7 Jun 2012 09:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tUSBNfv9GkQQ; Thu,  7 Jun 2012 09:35:32 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 8180821F86E3; Thu,  7 Jun 2012 09:35:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1339086929; bh=OorTusqV7QEn6jyyKRtywtY3DaEV3s731gNMSmlYvwo=; l=651; h=Message-ID:Date:From:MIME-Version:To:CC:References:In-Reply-To: Content-Transfer-Encoding; b=lrgXo7bVVsTc9B/oTHQXUY83dDuhU6fzsyl4Llex7ImFAbw6QOzrNCdL0g8fnuA0e E0RlMHzq8PpNKZk3E1C61E1L+ueSdmAupTuXF3PNex/V4MTImAcSMVS/kOdJS1+kfO UhIGoh9bMl7D+IXIZuS4DEBjgm1+8A3lS+OZbu6w=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Thu, 07 Jun 2012 18:35:29 +0200 id 00000000005DC039.000000004FD0D851.00007F7C
Message-ID: <4FD0D850.8040404@gmail.com>
Date: Thu, 07 Jun 2012 18:35:28 +0200
From: Alessandro Vesely <ale.whop@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
References: <4FCF32B5.7010102@gmail.com> <6.2.5.6.2.20120606215706.0aa1d6c0@elandnews.com>
In-Reply-To: <6.2.5.6.2.20120606215706.0aa1d6c0@elandnews.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 07 Jun 2012 10:06:48 -0700
Cc: spfbis@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-ietf-spfbis-experiment.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART LC review of draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 16:35:33 -0000

On Thu 07/Jun/2012 07:28:40 +0200 S Moonesamy wrote:

>> Does "SPF+TXT replies" mean that both an SPF and a TXT record exists
>> for these FQDNs? If so, are they identical? (Presumably they should be.)
> 
> Yes to the first question.  The working group didn't evaluate the second.

Actually, Philip evaluated the second question as well, mentioning
that some 17% of type99 records differ from the corresponding type16.
http://www.ietf.org/mail-archive/web/spfbis/current/msg00354.html

FWIW, I repeated a similar test for 24,853 domains in the DNSWL list,
and found that only 3% of the 587 domains that use both types had such
difference.

From mahoney@nostrum.com  Thu Jun  7 14:08:20 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA4F921F8704 for <gen-art@ietfa.amsl.com>; Thu,  7 Jun 2012 14:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ThhnxGPsWZRr for <gen-art@ietfa.amsl.com>; Thu,  7 Jun 2012 14:08:20 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id E393521F86FE for <gen-art@ietf.org>; Thu,  7 Jun 2012 14:08:19 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-51-177.dllstx.fios.verizon.net [173.71.51.177]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q57L8JT6008819 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 7 Jun 2012 16:08:19 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FD11843.4050006@nostrum.com>
Date: Thu, 07 Jun 2012 16:08:19 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.51.177 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-06-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 21:08:20 -0000

Hi all,

The following reviewers have assignments:

Reviewer              LC end      Draft

Alexey Melnikov     2012-06-14    draft-ietf-geopriv-dhcp-lbyr-uri-option

Allyn Romanow       2012-06-29    draft-sandlund-rfc4996bis

Ben Campbell        2012-06-15    draft-ietf-6man-rfc3484bis

Brian Carpenter     2012-06-15    RFC2818 **

Christer Holmberg   2012-06-15    draft-ietf-idr-rfc4893bis

Elwyn Davies        2012-06-15    draft-ietf-pwe3-cbit-negotiation

Francis Dupont      2012-07-02    draft-farrell-decade-ni

Joel Halpern        2012-06-18    draft-ietf-vcarddav-oma-cab-extensions

Kathleen Moriarty   2012-06-18    draft-ietf-6man-lineid

Martin Thomson      2012-07-02    draft-melnikov-smtp-priority-tunneling

Meral Shirazipour T 2012-06-20    draft-ietf-trill-clear-correct

Miguel Garcia     T 2012-06-20    draft-ietf-trill-rbridge-channel


T - on an upcoming Telechat (June 21)
** Since it's an RFC, it's not in the review tool.

The assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

And I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From brian.e.carpenter@gmail.com  Fri Jun  8 00:33:38 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E1B221F86D7 for <gen-art@ietfa.amsl.com>; Fri,  8 Jun 2012 00:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.662
X-Spam-Level: 
X-Spam-Status: No, score=-101.662 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yVN4+6GL0zQw for <gen-art@ietfa.amsl.com>; Fri,  8 Jun 2012 00:33:38 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id C06A521F86D4 for <gen-art@ietf.org>; Fri,  8 Jun 2012 00:33:37 -0700 (PDT)
Received: by eekd4 with SMTP id d4so1021774eek.31 for <gen-art@ietf.org>; Fri, 08 Jun 2012 00:33:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=P/8iE5lqeZS93coKAz64RigWInNseZKnixYlKAFWxBw=; b=oMVBwhFyyAsgWlegynteX48CgKjgP8npdIMv/UGtgtibfNhgzyiwI6DQ0IKbofN6I0 dTkurXweXIoOOKZ1SDSV7oaZKk8JqltDEryfO6NxvSbNKR6OMCwMsRS9nEejplA24Hbf ggAHm6czfj6BBNHt/KmrVytqupdozm7DsOWJs//Lks877O5y1Ow3S0CMQEqjNhjh/lXy syL1cYVQhBOCCIuLcxoClgPsUGtslyXnJPTpAJejKMAV+LhtxgmOZ61v3/hF/7Ga71qx MnegUXdKHkpsSFDsTRFH0ljq4ORTdOP5p0oTExaD2XgPYrBEcNxuGaAZDaDkv/6RGQAs ubeg==
Received: by 10.14.28.66 with SMTP id f42mr3516061eea.63.1339140816870; Fri, 08 Jun 2012 00:33:36 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-219-250.as13285.net. [2.102.219.250]) by mx.google.com with ESMTPS id c13sm19047455eeb.7.2012.06.08.00.33.34 (version=SSLv3 cipher=OTHER); Fri, 08 Jun 2012 00:33:35 -0700 (PDT)
Message-ID: <4FD1AAC6.1000308@gmail.com>
Date: Fri, 08 Jun 2012 08:33:26 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, Eric Rescorla <ekr@rtfm.com>, "Joseph A. Salowey" <jsalowey@cisco.com>, Sean Turner <turners@ieca.com>
Content-Type: multipart/mixed; boundary="------------030307090501060706080506"
Subject: [Gen-art] Gen-ART LC review of RFC2818
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 07:33:38 -0000

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

Please see attached review. I haven't cc'ed the IETF or IESG since
my comment is only a process issue, but this can be forwarded as you
think fit. If the IESG can see a way round it consistent with RFC 2026,
that would be fine by me.

   Brian


--------------030307090501060706080506
Content-Type: text/plain;
 name="RFC2818-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="RFC2818-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkb2N1bWVudC4g
Rm9yIGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0
dHA6Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+
Lg0KDQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhl
ciBMYXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IFJG
QzI4MTgudHh0DQpSZXZpZXdlcjogQnJpYW4gQ2FycGVudGVyDQpSZXZpZXcgRGF0ZTogMjAx
Mi0wNi0wOA0KSUVURiBMQyBFbmQgRGF0ZTogMjAxMi0wNi0xNQ0KSUVTRyBUZWxlY2hhdCBk
YXRlOiANCg0KU3VtbWFyeTogIFRlY2huaWNhbGx5IHJlYWR5IGJ1dCB0aGVyZSdzIGEgcHJv
Y2VzcyBpc3N1ZS4NCi0tLS0tLS0tDQoNCkNvbW1lbnQ6DQotLS0tLS0tLQ0KDQpUaGUgcHJv
cG9zZWQgYWN0aW9uIGlzIHRvIHJlY2xhc3NpZnkgUkZDIDI4MTggKEhUVFAgT3ZlciBUTFMp
IHRvIFByb3Bvc2VkIFN0YW5kYXJkLg0KVGhpcyBzZWVtcyBlbnRpcmVseSBhcHByb3ByaWF0
ZSBmcm9tIGEgdGVjaG5pY2FsIHBvaW50IG9mIHZpZXcuDQoNClByb2Nlc3MgaXNzdWU6DQot
LS0tLS0tLS0tLS0tLQ0KDQpJIGFtIG5vdCBzdXJlIHRoaXMgY2FuIGJlIGRvbmUgd2l0aG91
dCBhIG5ldyBSRkMuIEZpcnN0bHksIFJGQyAyODE4IGNhcnJpZXMNCkluZm9ybWF0aW9uYWwg
Ym9pbGVycGxhdGUsIGJ1dCBtb3JlIHNlcmlvdXNseSwgaXQgd2FzIGZvcm1hbGx5IHVwZGF0
ZWQgYnkNClJGQyA1Nzg1LiBVbmZvcnR1bmF0ZWx5LCBSRkMgNTc4NSBkb2VzIG5vdCBjb250
YWluIGFueSBpbnRlcm5hbCByZWZlcmVuY2UNCnRvIFJGQyAyODE4LCBzbyBpdCBpcyBoYXJk
IHRvIHRlbGwgd2hhdCBhc3BlY3Qgb2YgUkZDIDI4MTggaXMgdXBkYXRlZC4gSW4gYW55DQpj
YXNlLCB0aGF0IGRvZXMgdGVsbCBtZSB0aGF0IHNvbWV0aGluZyBpbiBSRkMgMjgxOCBpcyBv
dXQgb2YgZGF0ZSwgYnV0IGFzIGENCm5haXZlIHJlYWRlciwgSSBjYW4ndCB0ZWxsIHdoYXQg
aXQgaXMuDQoNClRoZSBzaW1wbGVzdCBzb2x1dGlvbiB3b3VsZCBiZSBhIHNob3J0IHN0YW5k
YXJkcyB0cmFjayBSRkMgdGhhdCBjaXRlcyBSRkMgMjgxOA0KYXMgYSBub3JtYXRpdmUgcmVm
ZXJlbmNlICh2aWEgdGhlIGV4aXN0aW5nIHByb2NlZHVyZSBmb3Igc3VjaCBleGNlcHRpb25z
KSBhbmQNCnNwZWxscyBvdXQgdGhlIHVwZGF0ZSBjYXVzZWQgYnkgUkZDIDU3ODUuDQoNCihU
byBiZSBjbGVhciwgdGhlIHNwZWNpZmljIHByb3Zpc2lvbiBvZiBSRkMgMjAyNiB0aGF0IGxl
YWRzIG1lIHRvIHRoaXMgaXMNCmluIHNlY3Rpb24gNi4yOg0KDQogICJDaGFuZ2Ugb2Ygc3Rh
dHVzIHNoYWxsIHJlc3VsdCBpbiByZXB1YmxpY2F0aW9uIG9mIHRoZSBzcGVjaWZpY2F0aW9u
DQogICBhcyBhbiBSRkMsIGV4Y2VwdCBpbiB0aGUgcmFyZSBjYXNlIHRoYXQgdGhlcmUgaGF2
ZSBiZWVuIG5vIGNoYW5nZXMgYXQNCiAgIGFsbCBpbiB0aGUgc3BlY2lmaWNhdGlvbiBzaW5j
ZSB0aGUgbGFzdCBwdWJsaWNhdGlvbi4iDQoNCkluIHRoaXMgY2FzZSwgUkZDIDU3ODUgYXBw
YXJlbnRseSBkb2VzIGNoYW5nZSB0aGUgc3BlY2lmaWNhdGlvbiBpbiBzb21lIHdheSwNCnNv
IHRoZSBleGNlcHRpb24gZG9lcyBub3QgYXBwbHkuKQ0KDQo=
--------------030307090501060706080506--

From jmh@joelhalpern.com  Fri Jun  8 09:52:10 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60C9621F86FF for <gen-art@ietfa.amsl.com>; Fri,  8 Jun 2012 09:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.265
X-Spam-Level: 
X-Spam-Status: No, score=-103.265 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x17Mv5i-lagQ for <gen-art@ietfa.amsl.com>; Fri,  8 Jun 2012 09:52:09 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 8761421F8703 for <gen-art@ietf.org>; Fri,  8 Jun 2012 09:52:08 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 4D86AA395C for <gen-art@ietf.org>; Fri,  8 Jun 2012 09:52:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 4227B1BD27DD; Fri,  8 Jun 2012 09:52:07 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.1.25] (unknown [96.245.81.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id C8B9B1BD27D6; Fri,  8 Jun 2012 09:52:06 -0700 (PDT)
Message-ID: <4FD22DAC.6080507@joelhalpern.com>
Date: Fri, 08 Jun 2012 12:51:56 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4FD11843.4050006@nostrum.com>
In-Reply-To: <4FD11843.4050006@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Simon Perreault <simon.perreault@viagenie.ca>, gen-art@ietf.org
Subject: Re: [Gen-art] A *new* batch of IETF LC reviews - 2012-06-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 16:52:10 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: vCard Format extension : represent vCard extensions
            defined by the Open Mobile Alliance (OMA)
            Converged Address Book (CAB) group
Reviewer: Joel M. Halpern
Review Date: 8-June-2012
IETF LC End Date: 18-June-2012
IESG Telechat date: N/A

Summary: This document is ready for publications as a Proposed Standard RFC

Major issues: None

Minor issues:
     The documents needs text on normative terminology and a reference 
two RFC 2119. (There is one explicit MUST.)


Nits/editorial comments:

From martin.thomson@gmail.com  Fri Jun  8 10:47:53 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E57821F8818 for <gen-art@ietfa.amsl.com>; Fri,  8 Jun 2012 10:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.385
X-Spam-Level: 
X-Spam-Status: No, score=-4.385 tagged_above=-999 required=5 tests=[AWL=-0.786, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0D63cDLgqBo7 for <gen-art@ietfa.amsl.com>; Fri,  8 Jun 2012 10:47:52 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 833E021F881A for <gen-art@ietf.org>; Fri,  8 Jun 2012 10:47:46 -0700 (PDT)
Received: by bkty8 with SMTP id y8so2339142bkt.31 for <gen-art@ietf.org>; Fri, 08 Jun 2012 10:47:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=ceYEjBMxS/Ntvta55ZRKtzdgZAVlc/l7tBqeLT2BXnI=; b=opSPk8SekGOi6tJFqxAE9/f+BCq7gZ1BJaIuK6zyihShyByCGBKZw4Bn/1tn+t1rtE wZ4Ug9thf6UFkbdA5PFtvBssDK2+J/pdNiUcdSBYyjCG2JfevlRGI4Wy2JaZNHrvVPev dMEVdNd1UyezeYy6PiRXQ7nU284R2n8Vxi3pImxxKnyR8bNaycLt5rE/t2jonP/N8ZVJ 4Un6UfANt0hDBcTBGAL2P7K67aasg1xR6Ndmg0A2zkViVUTXCVu1lk0Jdh53zq5UtTe7 P6i8mwnSDDy7B/KlueJr5wizWEvdhn3l57Rv0cB9WV1A1iA14l34PT1ftHP4V/5nTmM/ sKpw==
MIME-Version: 1.0
Received: by 10.204.150.84 with SMTP id x20mr6586185bkv.26.1339177665601; Fri, 08 Jun 2012 10:47:45 -0700 (PDT)
Received: by 10.204.66.4 with HTTP; Fri, 8 Jun 2012 10:47:45 -0700 (PDT)
Date: Fri, 8 Jun 2012 10:47:45 -0700
Message-ID: <CABkgnnXjDdsu2m-8ocGdEoA761qUAV_KctXJCsecNg3H+R1bbA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-melnikov-smtp-priority-tunneling.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART review of draft-melnikov-smtp-priority-tunneling-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 17:47:53 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-melnikov-smtp-priority-tunneling-02
Reviewer: Martin Thomson
Review Date: 2012-06-08
IETF LC End Date: 2012-07-02
IESG Telechat date: (if known)

Summary: This document is ready for publication as an Experimental
RFC, with one question.

Major issues: None

Minor issues:
I'm not sure that I agree with the SHOULD strength requirement on MSAs
or MTAs to strip mt-priority headers.  There's a marked difference
between failure to meet local preconditions for compliance and
whatever conditions some other MTA might place on mt-priority
observance.  GIven that each hop is expected to make their own
determination about priority anyway, what benefit is there in removing
information that might inform that choice?

Nits/editorial comments:
Section 7, check grammar: "within a close environment) ."
Section 7.1: I don't like statements like "has pros and cons" without
any guidance.  The pros and cons are probably easy to describe (they
seem intuitively obvious), so they are either important enough to
describe or not worth mentioning at all.  Either is better than the
tease.

From martin.thomson@gmail.com  Fri Jun  8 11:25:30 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7945C21F87CC for <gen-art@ietfa.amsl.com>; Fri,  8 Jun 2012 11:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.356
X-Spam-Level: 
X-Spam-Status: No, score=-4.356 tagged_above=-999 required=5 tests=[AWL=-0.757, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RxZFSIVah3-j for <gen-art@ietfa.amsl.com>; Fri,  8 Jun 2012 11:25:30 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id ADFA921F87CA for <gen-art@ietf.org>; Fri,  8 Jun 2012 11:25:29 -0700 (PDT)
Received: by bkty8 with SMTP id y8so2368457bkt.31 for <gen-art@ietf.org>; Fri, 08 Jun 2012 11:25:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QTBVcU0i6DTtWOUqGVkuHl6SiQVnzLA1a7MwDHW9KII=; b=JS2f6k7IpVjVEOO4nKXY2zAmeoItX+AyvE4OweZEx4ZYuJdjlJYPHTsR++m7iD1+Ig Lg9INnq+rhtfj/k7srro7XHGRhV46OpWVa2+y8uzORxYcOI8zhAVkYZs3RK8CYZ3RVW4 QHYjn8d9Ec5hJUH2LVpwjn/uwfu27McPMJFC+ngYMA6gUloKXCoIqL7jm2rER1i0C0LV AUr0cQaGmBT3Iyxq/NwxGAmSqBisQw6RKTPyoug+2E/tbrUmi3rBAio1H+n/tAMweGID JQJxN94tszvVOzO1PRaVSWBW1M9E559X6S2ZVQx2Idgap9lJz6ZKp4Y/9ql5nAIpYx3l aPJA==
MIME-Version: 1.0
Received: by 10.205.33.136 with SMTP id so8mr6643518bkb.1.1339179928731; Fri, 08 Jun 2012 11:25:28 -0700 (PDT)
Received: by 10.204.66.4 with HTTP; Fri, 8 Jun 2012 11:25:28 -0700 (PDT)
In-Reply-To: <4FD1AAC6.1000308@gmail.com>
References: <4FD1AAC6.1000308@gmail.com>
Date: Fri, 8 Jun 2012 11:25:28 -0700
Message-ID: <CABkgnnU7k8shmbBQAZJ4TG1R6O9c8OYdeKOyP9=+M-c_gPW-UA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: General Area Review Team <gen-art@ietf.org>, "Joseph A. Salowey" <jsalowey@cisco.com>, Eric Rescorla <ekr@rtfm.com>
Subject: Re: [Gen-art] Gen-ART LC review of RFC2818
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 18:25:30 -0000

On 8 June 2012 00:33, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> Please see attached review. I haven't cc'ed the IETF or IESG since
> my comment is only a process issue, but this can be forwarded as you
> think fit. If the IESG can see a way round it consistent with RFC 2026,
> that would be fine by me.

The "Updates" in RFC 5785 is an error, as noted in an erratum on that document.

From brian.e.carpenter@gmail.com  Sat Jun  9 00:35:15 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F22C221F87C9 for <gen-art@ietfa.amsl.com>; Sat,  9 Jun 2012 00:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.663
X-Spam-Level: 
X-Spam-Status: No, score=-101.663 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lx1FyULgK6PU for <gen-art@ietfa.amsl.com>; Sat,  9 Jun 2012 00:35:15 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 401A621F87B9 for <gen-art@ietf.org>; Sat,  9 Jun 2012 00:35:15 -0700 (PDT)
Received: by eaaq13 with SMTP id q13so1909973eaa.31 for <gen-art@ietf.org>; Sat, 09 Jun 2012 00:35:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=x9zFsW9HPJhWxjMW9dftoEspajisBdhVb41QQSIyq5Y=; b=BOZztv0ddqRFzNA3PhaUAsfccVnzmtPhS/VKa98S7prhueldlGkIn1eqlBYMnDKp7q YZkWbaX4ennreMjAYmjA2xZh/agdV9kIp6ZE/pVQMGQHaLs7fRVAaIQpxlM3uAU1/Wq0 cYesiCdHQooWtx8RiNq6SuHfZ8Xpp+05rhBeX7Ah/foNlbWeA3gdJh5QFegm5RBBcgag VC0VbWGOKVN3G67iZ+sgbI90Ip2CN1Qn6oUmbQzGRXDRu44s8F7dUsRYxIDolqWQXuTj cP8VKxOuXwhf9QJCtXPImiSJLSeiaobsZWuIbwdqwPDBNehYLHhuZ8X/06x3V/P0dWnq B14g==
Received: by 10.14.188.129 with SMTP id a1mr4535714een.183.1339227314311; Sat, 09 Jun 2012 00:35:14 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-248.as13285.net. [2.102.216.248]) by mx.google.com with ESMTPS id y54sm30035261eef.10.2012.06.09.00.35.12 (version=SSLv3 cipher=OTHER); Sat, 09 Jun 2012 00:35:13 -0700 (PDT)
Message-ID: <4FD2FCAA.2050706@gmail.com>
Date: Sat, 09 Jun 2012 08:35:06 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <4FD1AAC6.1000308@gmail.com> <CABkgnnU7k8shmbBQAZJ4TG1R6O9c8OYdeKOyP9=+M-c_gPW-UA@mail.gmail.com>
In-Reply-To: <CABkgnnU7k8shmbBQAZJ4TG1R6O9c8OYdeKOyP9=+M-c_gPW-UA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, "Joseph A. Salowey" <jsalowey@cisco.com>, Eric Rescorla <ekr@rtfm.com>
Subject: Re: [Gen-art] Gen-ART LC review of RFC2818
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 07:35:16 -0000

Aaargh. My head hurts.

Thanks Martin. I will update my review.

Regards
   Brian Carpenter

On 2012-06-08 19:25, Martin Thomson wrote:
> On 8 June 2012 00:33, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> Please see attached review. I haven't cc'ed the IETF or IESG since
>> my comment is only a process issue, but this can be forwarded as you
>> think fit. If the IESG can see a way round it consistent with RFC 2026,
>> that would be fine by me.
> 
> The "Updates" in RFC 5785 is an error, as noted in an erratum on that document.
> 

From brian.e.carpenter@gmail.com  Sat Jun  9 00:36:47 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C7921F89B2 for <gen-art@ietfa.amsl.com>; Sat,  9 Jun 2012 00:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.664
X-Spam-Level: 
X-Spam-Status: No, score=-101.664 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FyLKgXqKkmwf for <gen-art@ietfa.amsl.com>; Sat,  9 Jun 2012 00:36:46 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 31FB421F87B9 for <gen-art@ietf.org>; Sat,  9 Jun 2012 00:36:46 -0700 (PDT)
Received: by eekd4 with SMTP id d4so1933326eek.31 for <gen-art@ietf.org>; Sat, 09 Jun 2012 00:36:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=9rtIl/ytV3ATB5LnhB8SIV4f/CvC8udOk92pf5Wv7kY=; b=g9xlB47w1/jgq6oMP5pX/VT/bf2Rv1vc2Xb/wiLScbGpKP6Wo1TT3/tmcm4R9etBIX GdeLG62YZL3hZmNHgThR3MBcGfevSBUq1VEDXdmrGKclH+/MLIBzREI4+8AWuX6cbh6j CtMbV7wxiMyPlB5+ylfKOGN2XWQaDUMQkNcqKbLuq46LPeg1ZEmGzKxyqRFIDragSN6S oHGiPjU6IimnKyXLxBfv9NFKrxXAUeP1BcM1jdiHrx2Q+4blIsl01m9bYgsCfdJQGVMY M+a3YysOpu1q0xxYow72lMiUbOnibGRCMj38T1BYKJm3X3MEsjULrE0JlsQk9HFduGRn 2AAw==
Received: by 10.14.96.10 with SMTP id q10mr4436447eef.14.1339227405246; Sat, 09 Jun 2012 00:36:45 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-248.as13285.net. [2.102.216.248]) by mx.google.com with ESMTPS id h53sm30099489eea.1.2012.06.09.00.36.43 (version=SSLv3 cipher=OTHER); Sat, 09 Jun 2012 00:36:44 -0700 (PDT)
Message-ID: <4FD2FD0A.1090900@gmail.com>
Date: Sat, 09 Jun 2012 08:36:42 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, Eric Rescorla <ekr@rtfm.com>, "Joseph A. Salowey" <jsalowey@cisco.com>, Sean Turner <turners@ieca.com>
Content-Type: multipart/mixed; boundary="------------040708010007040808060606"
Subject: [Gen-art] Gen-ART LC review of RFC2818 (updated)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 07:36:47 -0000

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

Please see attached review. I haven't cc'ed the IETF or IESG since
my comment is only a *minor* process issue, but this can be forwarded as you
think fit. If the IESG can see a way round it consistent with RFC 2026,
that would be fine by me.

   Brian



--------------040708010007040808060606
Content-Type: text/plain;
 name="RFC2818-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="RFC2818-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkb2N1bWVudC4g
Rm9yIGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0
dHA6Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+
Lg0KDQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhl
ciBMYXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IFJG
QzI4MTgudHh0DQpSZXZpZXdlcjogQnJpYW4gQ2FycGVudGVyDQpSZXZpZXcgRGF0ZTogMjAx
Mi0wNi0wOSAodXBkYXRlZCkNCklFVEYgTEMgRW5kIERhdGU6IDIwMTItMDYtMTUNCklFU0cg
VGVsZWNoYXQgZGF0ZTogDQoNClN1bW1hcnk6ICBUZWNobmljYWxseSByZWFkeSBidXQgdGhl
cmUncyBhIG1pbm9yIHByb2Nlc3MgaXNzdWUuDQotLS0tLS0tLQ0KDQpDb21tZW50Og0KLS0t
LS0tLS0NCg0KVGhlIHByb3Bvc2VkIGFjdGlvbiBpcyB0byByZWNsYXNzaWZ5IFJGQyAyODE4
IChIVFRQIE92ZXIgVExTKSB0byBQcm9wb3NlZCBTdGFuZGFyZC4NClRoaXMgc2VlbXMgZW50
aXJlbHkgYXBwcm9wcmlhdGUgZnJvbSBhIHRlY2huaWNhbCBwb2ludCBvZiB2aWV3Lg0KDQpQ
cm9jZXNzIGlzc3VlOg0KLS0tLS0tLS0tLS0tLS0NCg0KUkZDIDI4MTggY2FycmllcyBJbmZv
cm1hdGlvbmFsIGJvaWxlcnBsYXRlLiBJIGNhbid0IGZpbmQgYW55dGhpbmcgaW4gUkZDIDIw
MjYNCnRoYXQgbWFrZXMgaXQgaW1wb3NzaWJsZSB0byBwcm9tb3RlIGEgZG9jdW1lbnQgdG8g
c3RhbmRhcmRzIHRyYWNrIGZvcg0KdGhpcyByZWFzb24sIGJ1dCBpdCBtYXkgY29uZnVzZSBw
ZW9wbGUgYW5kIFJGQyAxNzk2IGRvZXNuJ3QgaGVscCwgYmVjYXVzZQ0KaXQgc2F5cyB0aGF0
ICJ0aGUgc3RhdHVzIGlzIHJlcHJvZHVjZWQgb24gdGhlIGZpcnN0IHBhZ2Ugb2YgdGhlIFJG
QyBpdHNlbGYiLg0KDQpOLkIuIFJGQyA1Nzg1IGVycm9uZW91c2x5IGNsYWltcyB0byB1cGRh
dGUgUkZDIDI2MTYgYW5kIDI4MTguIENvdWxkIHRoZSBSRkMgRWRpdG9yIGJlDQphc2tlZCB0
byBkZWxldGUgdGhlc2UgbWlzdGFrZXMgZnJvbSB0aGUgUkZDIGluZGV4ZXM/IA0KDQogICAg
QnJpYW4NCg0K
--------------040708010007040808060606--

From presnick@qualcomm.com  Sat Jun  9 08:29:43 2012
Return-Path: <presnick@qualcomm.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C757421F884C; Sat,  9 Jun 2012 08:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.32
X-Spam-Level: 
X-Spam-Status: No, score=-106.32 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b32DEjHAnBs6; Sat,  9 Jun 2012 08:29:43 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 0644B21F884E; Sat,  9 Jun 2012 08:29:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1339255782; x=1370791782; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; bh=o7j3t5LDSOiaYc9iTC/8yz+Pbz6zrvUWIw1cqPBgF14=; b=XWomJ3W392N+AWtyot9XguUmnpfgILoURAsK/t63TFCGr9C11BzX7tj6 ZU5p3cy2kNsxyyeWtMkABjjX+IrCiMZ5I4dSrcL0rq4pzqlP3hnvv8jJJ 2uusO1XWizBgWa/dK88WeREG1hJhmwvuqXsx+tOLvLc4nx7MqKQH23GTC w=;
X-IronPort-AV: E=McAfee;i="5400,1158,6736"; a="197130514"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 09 Jun 2012 08:29:38 -0700
X-IronPort-AV: E=Sophos;i="4.75,741,1330934400"; d="scan'208";a="263793785"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Jun 2012 08:29:38 -0700
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.283.3; Sat, 9 Jun 2012 08:29:37 -0700
Message-ID: <4FD36BDE.5010502@qualcomm.com>
Date: Sat, 9 Jun 2012 10:29:34 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4FCF32B5.7010102@gmail.com>	<6.2.5.6.2.20120606215706.0aa1d6c0@elandnews.com>	<4FD05F2D.8010200@isdg.net> <4FD0AC66.50602@gmail.com>
In-Reply-To: <4FD0AC66.50602@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: spfbis@ietf.org, General Area Review Team <gen-art@ietf.org>, Hector Santos <hsantos@isdg.net>, S Moonesamy <sm+ietf@elandsys.com>, draft-ietf-spfbis-experiment.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART LC review	of	draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 15:29:43 -0000

Brian,

On 6/7/12 8:28 AM, Brian E Carpenter wrote:

>> S Moonesamy wrote:
>>
>>      
>>>> Brian Carpenter wrote:
>>>> Also, RFC4406 states that "Sending domains MAY publish either or both
>>>> formats" (i.e. spf1 or spf2.0). That being so, I would ideally expect
>>>> to see nine rows in the results table:
>>>>
>>>> SPF RR only, spf1 only
>>>> SPF RR only, spf2.0 only
>>>> SPF RR only, spf1 and spf2.0
>>>> TXT RR only, spf1 only
>>>> TXT RR only, spf2.0 only
>>>> TXT RR only, spf1 and spf2.0
>>>> SPF and TXT RRs, spf1 only
>>>> SPF and TXT RRs, spf2.0 only
>>>> SPF and TXT RRs, spf1 and spf2.0
>>>>          
>>> Pete suggests having two tables for each survey: (a) a comparison of
>>> RRTYPEs, and (b) a comparison of SPF vs. SIDF independent of RRTYPE.
>>> Would that be sufficient?
>>>        
> I am looking for clear presentation of the observed data, nothing more,
> as I do whenever I read a data-based document. As my review stated,
> I have no problem with the conclusions drawn in the draft.
>    

I'm afraid you got distracted by Hector's question and didn't answer 
SM's. Please do.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From brian.e.carpenter@gmail.com  Sat Jun  9 08:35:35 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48DF221F864C; Sat,  9 Jun 2012 08:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZNjF-s186ncE; Sat,  9 Jun 2012 08:35:34 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4431C21F864D; Sat,  9 Jun 2012 08:35:34 -0700 (PDT)
Received: by eekd4 with SMTP id d4so2076392eek.31 for <multiple recipients>; Sat, 09 Jun 2012 08:35:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BuPPQWkfJPYWwxSkDyhNvHzqblzX2oQVensQL4tJ6pE=; b=LjGaUh8UJ1N1jwfHiufT0j6lLikf+YZSjNBCKd92uY4tp2Sdr/UvR2c+zMgzUTamWM dTKAggtswNPQap1V80naRzzOJeacBuPZ+UjBjc0+699B56JOj5TrBiqtk99+piHJ9ZHy +kQiyxHuoAu3a83Fgb/ld3WqYSLUHfJm+x28m9q+tMod6mnl3e8czpHkc4YAJCY0nHVW eVvZiQMjHoBM9VltxM/pkoWyQkVWS9EO1sDezvEZfjd3M1JXhynwfqTd0FNDlmb3zTaa UVc3jJnUSnL64pJQRPjFkkpsakpFsdUA0YMzTlooj1oO8AHCi1ERr/YKNDEiAkn1AeZ7 H4Bg==
Received: by 10.14.127.130 with SMTP id d2mr4989554eei.82.1339256133424; Sat, 09 Jun 2012 08:35:33 -0700 (PDT)
Received: from [192.168.1.68] (host-2-101-189-72.as13285.net. [2.101.189.72]) by mx.google.com with ESMTPS id q53sm33294846eef.8.2012.06.09.08.35.31 (version=SSLv3 cipher=OTHER); Sat, 09 Jun 2012 08:35:32 -0700 (PDT)
Message-ID: <4FD36D42.2080308@gmail.com>
Date: Sat, 09 Jun 2012 16:35:30 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
References: <4FCF32B5.7010102@gmail.com>	<6.2.5.6.2.20120606215706.0aa1d6c0@elandnews.com>	<4FD05F2D.8010200@isdg.net> <4FD0AC66.50602@gmail.com> <4FD36BDE.5010502@qualcomm.com>
In-Reply-To: <4FD36BDE.5010502@qualcomm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: spfbis@ietf.org, General Area Review Team <gen-art@ietf.org>, Hector Santos <hsantos@isdg.net>, S Moonesamy <sm+ietf@elandsys.com>, draft-ietf-spfbis-experiment.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART LC review	of	draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 15:35:35 -0000

Hi Pete,

On 2012-06-09 16:29, Pete Resnick wrote:
> Brian,
> 
> On 6/7/12 8:28 AM, Brian E Carpenter wrote:
> 
>>> S Moonesamy wrote:
>>>
>>>     
>>>>> Brian Carpenter wrote:
>>>>> Also, RFC4406 states that "Sending domains MAY publish either or both
>>>>> formats" (i.e. spf1 or spf2.0). That being so, I would ideally expect
>>>>> to see nine rows in the results table:
>>>>>
>>>>> SPF RR only, spf1 only
>>>>> SPF RR only, spf2.0 only
>>>>> SPF RR only, spf1 and spf2.0
>>>>> TXT RR only, spf1 only
>>>>> TXT RR only, spf2.0 only
>>>>> TXT RR only, spf1 and spf2.0
>>>>> SPF and TXT RRs, spf1 only
>>>>> SPF and TXT RRs, spf2.0 only
>>>>> SPF and TXT RRs, spf1 and spf2.0
>>>>>          
>>>> Pete suggests having two tables for each survey: (a) a comparison of
>>>> RRTYPEs, and (b) a comparison of SPF vs. SIDF independent of RRTYPE.
>>>> Would that be sufficient?
>>>>        
>> I am looking for clear presentation of the observed data, nothing more,
>> as I do whenever I read a data-based document. As my review stated,
>> I have no problem with the conclusions drawn in the draft.
>>    
> 
> I'm afraid you got distracted by Hector's question and didn't answer
> SM's. Please do.

Sorry - yes, I think those two tables would be fine.

    Brian

From alexey.melnikov@isode.com  Sat Jun  9 09:47:27 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D07021F87D1; Sat,  9 Jun 2012 09:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.856
X-Spam-Level: 
X-Spam-Status: No, score=-102.856 tagged_above=-999 required=5 tests=[AWL=-0.257, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GJJOAuutpOr5; Sat,  9 Jun 2012 09:47:26 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 87FB121F8783; Sat,  9 Jun 2012 09:47:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1339260445; d=isode.com; s=selector; i=@isode.com; bh=jp71fRvKlk5rYaTwrHr99GBIQX/cibP+V7SWi3RV3tc=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=AAElZeFeFplyo8Ls4bnsuSNV262nc8DG4qUEMQ3VNzhm8ywFZo89oIy44QIqkFfpHsVHsH 7zneF7GiY9oVJaDWkIMlhJSsFCY+2PGrc3fErCN6OWMFGGIKL06ETzS2eN/4nRbq+/z5XA dsa9qDufSg2+IzQx9Ec2cDIfmkIJFxM=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T9N-HAAE47Bf@rufus.isode.com>; Sat, 9 Jun 2012 17:47:25 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4FD37E36.9080203@isode.com>
Date: Sat, 09 Jun 2012 17:47:50 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: draft-ietf-geopriv-dhcp-lbyr-uri-option.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, The IESG <iesg@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-geopriv-dhcp-lbyr-uri-option-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 16:47:27 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-geopriv-dhcp-lbyr-uri-option-15
Reviewer: Alexey Melnikov
Review Date: 2012-06-09
IETF LC End Date: 2012-06-14
IESG Telechat date: (if known)

Summary: This document is nearly ready for publication as a Proposed 
Standard.

Major issues: None

Minor issues:

In Section 1: the first reference to URI needs a Normative reference. 
The whole document is about passing URIs and they are not defined anywhere.

In Section 2.3: LuriType =1 description says that the value is UTF-8. 
This is not correct, URIs never contain non-ASCII values. So please 
either say ASCII, or use IRI if you really meant UTF-8 (but use of IRIs 
would be horrible, so don't).

LuriType=2: in network byte order?

In Section 3.2: "data:" URI needs an Informative reference (RFC 2397).

In Section 3.3: all media types mentioned (two?) need Normative references.


Nits/editorial comments:

In Section 3, 2nd to the last para: s/deference/dereference ?


From superuser@gmail.com  Sun Jun 10 14:14:21 2012
Return-Path: <superuser@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F46B21F8549; Sun, 10 Jun 2012 14:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.623
X-Spam-Level: 
X-Spam-Status: No, score=-2.623 tagged_above=-999 required=5 tests=[AWL=0.975,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AT9MMPZsWDxr; Sun, 10 Jun 2012 14:14:20 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 306A221F8547; Sun, 10 Jun 2012 14:14:19 -0700 (PDT)
Received: by lagv3 with SMTP id v3so3620995lag.31 for <multiple recipients>; Sun, 10 Jun 2012 14:14:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AOJaObAvZFyrf059XhpnzTzogyAi7lN0ubtIXZi9tM0=; b=d+TREdMuv44HjmNLSdPamdWXro114wXQcaASE2DFod7OqQRcX6bl9h/OChKkVA1Mhf 82AlRD1Oxyac57GgLQfMjfKRo3WVhKqCl6nc/TXjaWpWIDLZxE5X5N+PakshX8mg3eje V7ge6+42MBAt6XvXuIo1e56nEuygoNWqR24ddYj1B5f6bRT/n5Uk1nhEWeGVGxyDhm2T WZtX3ko2j1eGokK3DKTmgLzCFiJ7nIcddmQsanTDh/28nkvsF4dRWLl/APJhRZqnuQXj lD8YFAUsh/D0RPyaThUBYqPXHOcycjCRmoVUhTvQVhY1T8oQ3QJGjGTeYZZ0UjXu4c+g t3XQ==
MIME-Version: 1.0
Received: by 10.112.84.168 with SMTP id a8mr2270633lbz.92.1339362858995; Sun, 10 Jun 2012 14:14:18 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Sun, 10 Jun 2012 14:14:18 -0700 (PDT)
In-Reply-To: <4FD36D42.2080308@gmail.com>
References: <4FCF32B5.7010102@gmail.com> <6.2.5.6.2.20120606215706.0aa1d6c0@elandnews.com> <4FD05F2D.8010200@isdg.net> <4FD0AC66.50602@gmail.com> <4FD36BDE.5010502@qualcomm.com> <4FD36D42.2080308@gmail.com>
Date: Sun, 10 Jun 2012 14:14:18 -0700
Message-ID: <CAL0qLwbH_7YwjNuEvg7LT=LZEJxU+Le4n8EuEixNOzECYo_eBA@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, spfbis@ietf.org
Content-Type: multipart/alternative; boundary=f46d04016cad6f911004c224b72e
X-Mailman-Approved-At: Sun, 10 Jun 2012 19:14:43 -0700
Cc: General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] [spfbis] Gen-ART LC review of draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jun 2012 21:14:21 -0000

--f46d04016cad6f911004c224b72e
Content-Type: text/plain; charset=ISO-8859-1

I have a revised version with the requested changes stuck in submission
tool limbo.  I'll get it posted as soon as the Secretariat can fix it.

-MSK

--f46d04016cad6f911004c224b72e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I have a revised version with the requested changes stuck in submission too=
l limbo.=A0 I&#39;ll get it posted as soon as the Secretariat can fix it.<b=
r><br>-MSK<br>=A0

--f46d04016cad6f911004c224b72e--

From miguel.a.garcia@ericsson.com  Mon Jun 11 00:30:45 2012
Return-Path: <miguel.a.garcia@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1741421F8484 for <gen-art@ietfa.amsl.com>; Mon, 11 Jun 2012 00:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QPgK0jAajL2a for <gen-art@ietfa.amsl.com>; Mon, 11 Jun 2012 00:30:44 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 23DBB21F846A for <gen-art@ietf.org>; Mon, 11 Jun 2012 00:30:43 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fc66d000006fdc-11-4fd59ea299e6
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 30.75.28636.2AE95DF4; Mon, 11 Jun 2012 09:30:42 +0200 (CEST)
Received: from [159.107.105.100] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.264.0; Mon, 11 Jun 2012 09:30:42 +0200
Message-ID: <4FD59EA1.9030008@ericsson.com>
Date: Mon, 11 Jun 2012 09:30:41 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: draft-ietf-pim-ecmp.authors@tools.ietf.org, mmcbride7@gmail.com,  pim-chairs@tools.ietf.org, Adrian Farrel <adrian@olddog.co.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprELMWRmVeSWpSXmKPExsUyM+Jvre6ieVf9DQ7c1bf40XOD2WLzq8WM FldffWax+HpvLpPFz4ZzzA6sHjtn3WX3WLLkJ5PHis0rGT2+XP7MFsASxWWTkpqTWZZapG+X wJWx9qVKwRPeirYF69gbGF9zdTFyckgImEhMv7CSCcIWk7hwbz1bFyMXh5DAKUaJd7f2skA4 axkl3t64ywZSxSugLTH9wSl2EJtFQFXi1r4WsG42AXOJ1o0bweKiAsES87pvskDUC0qcnPkE bJCIQBujxObpd8AamAX0JY782Q1mCwuYSizZ0coGEbeVuDDnOguELS+x/e0cZhBbSEBTYvLN pcwTGPlnIZk7C0nLLCQtCxiZVzEK5yZm5qSXG+qlFmUmFxfn5+kVp25iBIbrwS2/dXcwnjon cohRmoNFSZyXK2m/v5BAemJJanZqakFqUXxRaU5q8SFGJg5OqQbGDtuPJrGZ6/Kr5hhNfLLp ++t3vxcZBlk9uPr70O6F3XExdmc+xml+l1/aelnMpI6xI+ljQPj05M//fJy41y9XFul/pdKR dE9u9sxHhs/fHhdZX7+Y726nksXeJx6Pgormb7sQJX57xV6D66tfbhJ4O8spwrj+rYHqkj45 Z1mddD/vjx8mOTMrKLEUZyQaajEXFScCABcBJX8lAgAA
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-pim-ecmp-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 07:30:45 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft. For background on Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other comments you may receive.

Document: draft-ietf-pim-ecmp-03.txt
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 2012-06-11
IETF LC End Date: 2012-06-12
IESG Telechat date: 2012-06-21

Summary: The document is ready for publication as a standards track RFC.

Major issues: none

Minor issues: none

Nits/editorial comments:

- The Abstract should not include references. Just delete "[RFC4601]".

- Perhaps this is a matter of personal taste... but Section 3.5.2 is 
devoted to describe the format of the PIM ECMP Redirect message. I think 
this is a section where you should describe the format, but you shouldn't 
write normative statements as for what to do with those fields. For 
example, I am referring to statements like:

       Address of desired upstream
       neighbor where the downstream receiver SHOULD redirect PIM
       Joins

       the receiving
       router of this message MUST use the "Interface ID", instead of
       "Neighbor Address", to identify the new RPF neighbor

       an ECMP
       Redirect message MUST be discarded if the "Interface ID" field...

I think all these sentences including a normative MUST, SHOULD, etc. 
should be written in Sections 3.1. or 3.2 (Procedures). This means that 
the format (current section 3.5) should be moved to a place prior to 3.1 
and 3.2, because the procedures needs to explain what to do with all 
these fields.

/Miguel
-- 
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain

From suresh.krishnan@ericsson.com  Mon Jun 11 09:34:40 2012
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3F7421F85F6 for <gen-art@ietfa.amsl.com>; Mon, 11 Jun 2012 09:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VbfSwUpkfBLa for <gen-art@ietfa.amsl.com>; Mon, 11 Jun 2012 09:34:39 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6876D21F8656 for <gen-art@ietf.org>; Mon, 11 Jun 2012 09:34:39 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q5BGYajh012190; Mon, 11 Jun 2012 11:34:38 -0500
Received: from [142.133.112.108] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.264.0; Mon, 11 Jun 2012 12:34:31 -0400
Message-ID: <4FD61E17.3050608@ericsson.com>
Date: Mon, 11 Jun 2012 12:34:31 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
References: <4FCE2B6C.1010704@ericsson.com> <1EE04451-B5F5-4A55-A1F2-3D9165BF732B@tik.ee.ethz.ch>
In-Reply-To: <1EE04451-B5F5-4A55-A1F2-3D9165BF732B@tik.ee.ethz.ch>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-mile-iodef-xmlreg.all@tools.ietf.org" <draft-ietf-mile-iodef-xmlreg.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-mile-iodef-xmlreg-01.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 16:34:40 -0000

On 06/06/2012 06:57 PM, Brian Trammell wrote:
> Hi, Suresh,
> 
> Thanks for the comment; yes, this one is a bit hard to parse (even for me, and I tend to write page-length sentences). I've tweaked your suggested text somewhat and applied to the current working copy of the -02 revision.

Thanks Brian. I will look over the new text when it is available.

Regards
Suresh


From meral.shirazipour@ericsson.com  Mon Jun 11 12:38:01 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B2CE11E80AD for <gen-art@ietfa.amsl.com>; Mon, 11 Jun 2012 12:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VQykTTF-NVjl for <gen-art@ietfa.amsl.com>; Mon, 11 Jun 2012 12:38:00 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 117C011E80A1 for <gen-art@ietf.org>; Mon, 11 Jun 2012 12:37:59 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q5BJboAS020299; Mon, 11 Jun 2012 14:37:59 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.57]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Mon, 11 Jun 2012 15:37:52 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-grow-simple-va.all@tools.ietf.org" <draft-ietf-grow-simple-va.all@tools.ietf.org>
Date: Mon, 11 Jun 2012 15:37:50 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-grow-simple-va-09.txt
Thread-Index: Ac1ICZj+aqpXkVFyRu+On8/htcBzeQ==
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E699D6A6D95@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_25DC600D0CC1F2479C7053ADEB93004E699D6A6D95EUSAACMS0703e_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-grow-simple-va-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 19:38:01 -0000

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

I am the assigned Gen-ART reviewer for draft-ietf-grow-simple-va-09.txt. Fo=
r background on Gen-ART, please see the FAQ at  <http://www.alvestrand.no/i=
etf/gen/art/gen-art-FAQ.html>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-grow-simple-va-09
Reviewer: Meral Shirazipour
Review Date: June-11-2012
IETF LC End Date: June-12-2012
IESG Telechat date: June-21-2012

Summary:
This draft is almost ready to be published as Informational RFC but I do ha=
ve some comments.

Minor issues:
-[Page 1], Abstract, not clear what is the simplification of S-VA in compar=
ison to VA. Suggestion: a sentence or two in the abstract could clarify thi=
s
"In contracts to VA, S-VA reduces operational complexity by ..."

Nits/editorial comments:
-Consistency: [Page 4], 2nd to last paragraph: "core routers, to ABRs", exp=
and "ABRs"-->"Area Border Routers (ABRs)"
-Consistency: [Page 4], 2nd to last paragraph: "to the ASBR routers", expan=
d "ASBR"-->"to AS Border Routers (ASBRs)"
-Typo: [Page 5], Section 1: "rather then"--> "rather than"
-Clarity: [Page 5], Section 1, same sentence as above typo, add commas afte=
r "can" and "RIB":
"In configurations where BGP routes are used to resolve other routes
or where BGP routes are redistributed to other protocols which both
happen via RIB simple-va can[,] rather then suppressing routes before
they are installed in global RIB[,] flag them as "suppress eligible".
"
-Consistency: Perhaps run over draft and change all: "loc-RIB"-->"Loc-RIB"
-Consistency: Perhaps run over draft and change all: "simple-va"-->"S-VA"
-Clarity: [Page 6],"product of SPF"-->"product of Shortest Path First (SPF)=
"
-Clarity: [Page 6],Section 2, last paragraph: "scenarios for S-VA - "-->"sc=
enarios for S-VA : "
-Consistency: [Page 7], Figure should have a caption (and last paragraph p.=
7 should refer to Figure 1)
-Consistency: [Page 7]&[Page 8], spell out EP and EBGP when first use.
-Clarity: [Page 8] paragraph 1, "suppression routes"-->"suppression of all =
routes"
-Clarity: [Page 8],last paragraph: "needs to pointed"-->"needs to be pointe=
d"
-Typo: [Page 8],last sentence: "more then"-->"more than"
-Clarity: [Page 8][Page 9], point form after "the following solutions could=
 be considered:", it is not clear what is a title, what is the explanation.
Please correct this.(Suggestion, perhaps use ":" after the title, before th=
e explanation.)
-Typo: [Page 9], "etc .."--> "etc."


Thanks,
Meral

---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

--_000_25DC600D0CC1F2479C7053ADEB93004E699D6A6D95EUSAACMS0703e_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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=3DEN-CA link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the assigne=
d Gen-ART reviewer for draft-ietf-grow-simple-va-09.txt. For background on =
Gen-ART, please see the FAQ at &nbsp;&lt;http://www.alvestrand.no/ietf/gen/=
art/gen-art-FAQ.html&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p><p class=3DMsoNormal>Please resolve these comments along with any ot=
her Last Call comments you may receive.<o:p></o:p></p><p class=3DMsoNormal>=
<o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Document: draft-ietf-grow-simple-=
va-09<o:p></o:p></p><p class=3DMsoNormal>Reviewer: Meral Shirazipour<o:p></=
o:p></p><p class=3DMsoNormal>Review Date: June-11-2012<o:p></o:p></p><p cla=
ss=3DMsoNormal>IETF LC End Date: June-12-2012<o:p></o:p></p><p class=3DMsoN=
ormal>IESG Telechat date: June-21-2012<o:p></o:p></p><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Summary:<o:p></o:p></p><p class=3D=
MsoNormal>This draft is almost ready to be published as Informational RFC b=
ut I do have some comments.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><p class=3DMsoNormal>Minor issues:<o:p></o:p></p><p class=3DMsoNor=
mal>-[Page 1], Abstract, not clear what is the simplification of S-VA in co=
mparison to VA. Suggestion: a sentence or two in the abstract could clarify=
 this <o:p></o:p></p><p class=3DMsoNormal>&quot;In contracts to VA, S-VA re=
duces operational complexity by ...&quot;<o:p></o:p></p><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Nits/editorial comments:<o:p></=
o:p></p><p class=3DMsoNormal>-Consistency: [Page 4], 2nd to last paragraph:=
 &quot;core routers, to ABRs&quot;, expand &quot;ABRs&quot;--&gt;&quot;Area=
 Border Routers (ABRs)&quot;<o:p></o:p></p><p class=3DMsoNormal>-Consistenc=
y: [Page 4], 2nd to last paragraph: &quot;to the ASBR routers&quot;, expand=
 &quot;ASBR&quot;--&gt;&quot;to AS Border Routers (ASBRs)&quot;<o:p></o:p><=
/p><p class=3DMsoNormal>-Typo: [Page 5], Section 1: &quot;rather then&quot;=
--&gt; &quot;rather than&quot;<o:p></o:p></p><p class=3DMsoNormal>-Clarity:=
 [Page 5], Section 1, same sentence as above typo, add commas after &quot;c=
an&quot; and &quot;RIB&quot;:<o:p></o:p></p><p class=3DMsoNormal>&quot;In c=
onfigurations where BGP routes are used to resolve other routes<o:p></o:p><=
/p><p class=3DMsoNormal>or where BGP routes are redistributed to other prot=
ocols which both<o:p></o:p></p><p class=3DMsoNormal>happen via RIB simple-v=
a can[,] rather then suppressing routes before<o:p></o:p></p><p class=3DMso=
Normal>they are installed in global RIB[,] flag them as &quot;suppress elig=
ible&quot;.<o:p></o:p></p><p class=3DMsoNormal>&quot;<o:p></o:p></p><p clas=
s=3DMsoNormal>-Consistency: Perhaps run over draft and change all: &quot;lo=
c-RIB&quot;--&gt;&quot;Loc-RIB&quot;<o:p></o:p></p><p class=3DMsoNormal>-Co=
nsistency: Perhaps run over draft and change all: &quot;simple-va&quot;--&g=
t;&quot;S-VA&quot;<o:p></o:p></p><p class=3DMsoNormal>-Clarity: [Page 6],&q=
uot;product of SPF&quot;--&gt;&quot;product of Shortest Path First (SPF)&qu=
ot;<o:p></o:p></p><p class=3DMsoNormal>-Clarity: [Page 6],Section 2, last p=
aragraph: &quot;scenarios for S-VA - &quot;--&gt;&quot;scenarios for S-VA :=
 &quot;<o:p></o:p></p><p class=3DMsoNormal>-Consistency: [Page 7], Figure s=
hould have a caption (and last paragraph p.7 should refer to Figure 1) <o:p=
></o:p></p><p class=3DMsoNormal>-Consistency: [Page 7]&amp;[Page 8], spell =
out EP and EBGP when first use.<o:p></o:p></p><p class=3DMsoNormal>-Clarity=
: [Page 8] paragraph 1, &quot;suppression routes&quot;--&gt;&quot;suppressi=
on of all routes&quot;<o:p></o:p></p><p class=3DMsoNormal>-Clarity: [Page 8=
],last paragraph: &quot;needs to pointed&quot;--&gt;&quot;needs to be point=
ed&quot;<o:p></o:p></p><p class=3DMsoNormal>-Typo: [Page 8],last sentence: =
&quot;more then&quot;--&gt;&quot;more than&quot;<o:p></o:p></p><p class=3DM=
soNormal>-Clarity: [Page 8][Page 9], point form after &quot;the following s=
olutions could be considered:&quot;, it is not clear what is a title, what =
is the explanation.<o:p></o:p></p><p class=3DMsoNormal>Please correct this.=
(Suggestion, perhaps use &quot;:&quot; after the title, before the explanat=
ion.)<o:p></o:p></p><p class=3DMsoNormal><span lang=3DFR>-Typo: [Page 9], &=
quot;etc ..&quot;--&gt; &quot;etc.&quot;<o:p></o:p></span></p><p class=3DMs=
oNormal><span lang=3DFR><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan lang=3DFR><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=
=3DFR>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal>Meral<o:p></o:p></p=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>---<o:p></o=
:p></p><p class=3DMsoNormal>Meral Shirazipour<o:p></o:p></p><p class=3DMsoN=
ormal>Ericsson<o:p></o:p></p><p class=3DMsoNormal>Research<o:p></o:p></p><p=
 class=3DMsoNormal>www.ericsson.com<o:p></o:p></p></div></body></html>=

--_000_25DC600D0CC1F2479C7053ADEB93004E699D6A6D95EUSAACMS0703e_--

From brian.e.carpenter@gmail.com  Tue Jun 12 00:36:39 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1ED421F85AF; Tue, 12 Jun 2012 00:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.136
X-Spam-Level: 
X-Spam-Status: No, score=-101.136 tagged_above=-999 required=5 tests=[AWL=0.555, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3TRVgJSF572R; Tue, 12 Jun 2012 00:36:39 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id BEC9621F850D; Tue, 12 Jun 2012 00:36:38 -0700 (PDT)
Received: by eaaq13 with SMTP id q13so2903193eaa.31 for <multiple recipients>; Tue, 12 Jun 2012 00:36:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=CDITGxRyHThtw7EmEr1FuE4AopLFoGb2pCk6HpEIz64=; b=W0f+dKzT/WiL25xdPjDjDRUFkuOp/LSJqfp4SxYE7Tn21b/Guclb2mQYWt3cpJWN3c bcSqSTJsrrYFqgMovk4dvGPxfSOeWMSaY6dveWEKsZFaUyZinp0HK9wfLuIuB6Miozh8 jOweCPKbuG6FcaY/lnhyi8XAYtlSG5sqSIHHrCKC116m5uK3lHos2R4MhoHDqBi+sfma luiX5uj7nP4htdbT2KyXIM7KLiR4zCckmMzVw3Gv8AkIGiM4LGMqYTft80EaLBFDNGw4 6awYoz79WHo6UMfRlbHg4UieCTkoQO4g0DKH3h9nK+Ww3mYuBY4tz1LmVgzV0xcg4kZ6 Nz6w==
Received: by 10.14.37.12 with SMTP id x12mr6523552eea.161.1339486597862; Tue, 12 Jun 2012 00:36:37 -0700 (PDT)
Received: from [192.168.1.67] (host-2-102-219-50.as13285.net. [2.102.219.50]) by mx.google.com with ESMTPS id p41sm61059430eef.5.2012.06.12.00.36.35 (version=SSLv3 cipher=OTHER); Tue, 12 Jun 2012 00:36:37 -0700 (PDT)
Message-ID: <4FD6F180.8010401@gmail.com>
Date: Tue, 12 Jun 2012 08:36:32 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>
References: <4FCF32B5.7010102@gmail.com>	<6.2.5.6.2.20120606215706.0aa1d6c0@elandnews.com>	<4FD05F2D.8010200@isdg.net> <4FD0AC66.50602@gmail.com> <4FD36BDE.5010502@qualcomm.com> <4FD36D42.2080308@gmail.com>
In-Reply-To: <4FD36D42.2080308@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, spfbis@ietf.org, S Moonesamy <sm+ietf@elandsys.com>, draft-ietf-spfbis-experiment.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART LC review of draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 07:36:40 -0000

I've looked at the changes in the -10 version, and it's
much clearer to me, thanks. If I'm asked to review it again
it will be "Ready".

Regards
   Brian

On 2012-06-09 16:35, Brian E Carpenter wrote:
> Hi Pete,
> 
> On 2012-06-09 16:29, Pete Resnick wrote:
>> Brian,
>>
>> On 6/7/12 8:28 AM, Brian E Carpenter wrote:
>>
>>>> S Moonesamy wrote:
>>>>
>>>>     
>>>>>> Brian Carpenter wrote:
>>>>>> Also, RFC4406 states that "Sending domains MAY publish either or both
>>>>>> formats" (i.e. spf1 or spf2.0). That being so, I would ideally expect
>>>>>> to see nine rows in the results table:
>>>>>>
>>>>>> SPF RR only, spf1 only
>>>>>> SPF RR only, spf2.0 only
>>>>>> SPF RR only, spf1 and spf2.0
>>>>>> TXT RR only, spf1 only
>>>>>> TXT RR only, spf2.0 only
>>>>>> TXT RR only, spf1 and spf2.0
>>>>>> SPF and TXT RRs, spf1 only
>>>>>> SPF and TXT RRs, spf2.0 only
>>>>>> SPF and TXT RRs, spf1 and spf2.0
>>>>>>          
>>>>> Pete suggests having two tables for each survey: (a) a comparison of
>>>>> RRTYPEs, and (b) a comparison of SPF vs. SIDF independent of RRTYPE.
>>>>> Would that be sufficient?
>>>>>        
>>> I am looking for clear presentation of the observed data, nothing more,
>>> as I do whenever I read a data-based document. As my review stated,
>>> I have no problem with the conclusions drawn in the draft.
>>>    
>> I'm afraid you got distracted by Hector's question and didn't answer
>> SM's. Please do.
> 
> Sorry - yes, I think those two tables would be fine.
> 
>     Brian
> 

From christer.holmberg@ericsson.com  Tue Jun 12 08:38:31 2012
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E119821F86AB for <gen-art@ietfa.amsl.com>; Tue, 12 Jun 2012 08:38:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level: 
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t1a9tmY6eY9Q for <gen-art@ietfa.amsl.com>; Tue, 12 Jun 2012 08:38:31 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id E951121F86A4 for <gen-art@ietf.org>; Tue, 12 Jun 2012 08:38:30 -0700 (PDT)
X-AuditID: c1b4fb30-b7f606d0000002be-56-4fd76275cbca
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 91.D2.00702.57267DF4; Tue, 12 Jun 2012 17:38:29 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.62]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Tue, 12 Jun 2012 17:38:29 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-idr-rfc4893bis.all@tools.ietf.org" <draft-ietf-idr-rfc4893bis.all@tools.ietf.org>
Date: Tue, 12 Jun 2012 17:38:28 +0200
Thread-Topic: GenART LC review of draft-ietf-idr-rfc4893bis-06
Thread-Index: AQHNSLDCyyw+LJNkLEqwSg90U/4QGg==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C47149A6E@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrELMWRmVeSWpSXmKPExsUyM+JvrW5p0nV/g69/zSx+9y9ltbj66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJUxZfd25oJlnBWP5h9jb2C8zdbFyMkhIWAi 0fv4ApQtJnHh3nogm4tDSOAUo8SHE3eZQRJCAgsYJRbcqupi5OBgE7CQ6P6nDVIjItDDKNH7 8CYTSJxFQFXickMESLmwgKXE3xmHGUFsEQE7ic/nPrCAlIgI6Em8+C8IEuYVCJeY1j0dbDoj 0Nrvp9YwgdjMAuISt57MZ4I4R0BiyZ7zzBC2qMTLx/9YIepFJe60r2eEqNeTuDF1ChuErS2x bOFrZoj5ghInZz5hmcAoPAvJ2FlIWmYhaZmFpGUBI8sqRuHcxMyc9HJzvdSizOTi4vw8veLU TYzAcD+45bfBDsZN98UOMUpzsCiJ8+qp7vcXEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwDjV MfBrxw7hPBmW7w4zF880ey7CM92lcK3jl57CjDsfr+ge3PlMcH3NSpejGs77Zv9cs+DIFMZ6 scI5/KH/vx6a+aEtoOzypyfMlX9N/jcZNAqLlftmezh+UlWPvi6Va80g/7XqggTzH+eO6LYJ v42u1ryew5HX99T0goTrLXvJJR3+N7nENiuxFGckGmoxFxUnAgBBO0tRRQIAAA==
Subject: [Gen-art] GenART LC review of draft-ietf-idr-rfc4893bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 15:38:32 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:                             draft-ietf-idr-rfc4893bis-06.txt
Reviewer:                               Christer Holmberg
Review Date:                          2012-06-12
IETF LC End Date:                   2012-06-15
IESG Telechat date: (if known)

Summary:  The draft is ready for publication, with a couple of minor editor=
ial nits.

Major issues: -

Minor issues: -

Nits/editorial comments:



GENERAL:



Q_GEN-1: Sometimes the text says "AS number", and sometimes "Autonomous Sys=
tem number". Please use consistant terminology.



Q_GEN-2: Sometimes the text says "2-octet", and sometimes "two-octet". Plea=
se use consistant terminology.



Q_GEN-3: Sometimes the text says "4-octet", and sometimes "four-octet". Ple=
ase use consistant terminology.



SECTION 4.2.1:



Q_4_2_1-1: I suggest to replace "OLD one" with "OLD BGP speaker".





Regards,



Christer



From Paul_Sangster@symantec.com  Wed Jun 13 09:53:57 2012
Return-Path: <Paul_Sangster@symantec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56E3521F8539; Wed, 13 Jun 2012 09:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V+rP1tMCVig4; Wed, 13 Jun 2012 09:53:53 -0700 (PDT)
Received: from ecl1mtaoutpex02.symantec.com (ecl1mtaoutpex02.symantec.com [166.98.1.210]) by ietfa.amsl.com (Postfix) with ESMTP id CA19421F858A; Wed, 13 Jun 2012 09:53:50 -0700 (PDT)
X-AuditID: a66201d2-b7f6b6d000005fd4-11-4fd8c599508c
Received: from ecl1mtahubpin02.ges.symantec.com (ECL1MTAHUBPIN02.ges.symantec.com [10.48.69.202]) by ecl1mtaoutpex02.symantec.com (Symantec Messaging Gateway) with SMTP id 76.B9.24532.995C8DF4; Wed, 13 Jun 2012 16:53:45 +0000 (GMT)
Received: from [155.64.220.139] (helo=TUS1XCHHUBPIN03.SYMC.SYMANTEC.COM) by ecl1mtahubpin02.ges.symantec.com with esmtp (Exim 4.76) (envelope-from <Paul_Sangster@symantec.com>) id 1SeqpF-0000L1-7p; Wed, 13 Jun 2012 16:53:45 +0000
Received: from TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM ([155.64.220.150]) by TUS1XCHHUBPIN03.SYMC.SYMANTEC.COM ([155.64.220.139]) with mapi; Wed, 13 Jun 2012 09:53:44 -0700
From: Paul Sangster <Paul_Sangster@symantec.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-nea-pt-tls.all@tools.ietf.org" <draft-ietf-nea-pt-tls.all@tools.ietf.org>
Date: Wed, 13 Jun 2012 09:55:55 -0700
Thread-Topic: GenART LC review of draft-ietf-nea-pt-tls-05
Thread-Index: Ac1Cl9xExNAkih6WSYeHA9SkXDOg7gG388dg
Message-ID: <6E79D623502C70419A9EAB18E4D274252B8B06102F@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
References: <4fcd272e.2968b40a.55d4.ffff9de3@mx.google.com>
In-Reply-To: <4fcd272e.2968b40a.55d4.ffff9de3@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_6E79D623502C70419A9EAB18E4D274252B8B06102FTUS1XCHEVSPIN_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKIsWRmVeSWpSXmKPExsXCZeB6Snfm0Rv+BofWaFjMvTiB3eLqq88s Fs82zmex+Py2wuJvO7MDq8fOWXfZPZYs+cnk8eXyZ7YA5igum5TUnMyy1CJ9uwSujOtPlQom vGCsWPL+InsD4/vTjF2MHBwSAiYSjbequxg5gUwxiQv31rN1MXJxCAm8ZJSYvH4FM0hCSOA1 o8SanekQiVWMEp+2zmUESbAJGEjsPHKKHSQhItDIKPF1yRywDmaBJInjMzawgNgsAqoSV483 sYPYwgKWElO+TwKLiwhYSSz9MJEJwjaSaL73EizOKxAl0f1rJyvEZmuJ/ZeWgi3jFLCR2Hfl OFicEejU76fWMEHsEpe49WQ+E8QLAhJL9pxnhrBFJV4+/gdVLypxp3092MfMAvkSU85aQqwS lDg58wnLBEaxWUgmzUKomoWkCqJER2LB7k9sELa2xLKFr5lh7DMHHjMhiy9gZF/FKJOanGOY W5KYX1pSkFphYKRXXJmbCIzaZL3k/NxNjMDIXZbEeGkH4/3DuocYBTgYlXh42ffd8BdiTSwD qjzEKMHBrCTCu3olUIg3JbGyKrUoP76oNCe1+BCjNAeLkjjvhV1b/YUE0hNLUrNTUwtSi2Cy TBycUg2M2aFnX/Mf7DSawXywW6Zo0ZxzPLenH77Ad0BTKyv6wv4NaWs6zktHSFusELd6Pkd2 XSlbpnqYynnXP/1eVf32k39oZxeuflK9d3vastca5gl3n81o+yyyT2+FRHbNz+r1psmyK9KW rMnTUWc69eWVVIeOswBX4xTe7s+rOphNbugp5BlKLL6pxFKckWioxVxUnAgAH0ARXtgCAAA=
X-Mailman-Approved-At: Wed, 13 Jun 2012 09:54:46 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "nea@ietf.org" <nea@ietf.org>, 'IETF' <ietf@ietf.org>
Subject: Re: [Gen-art] GenART LC review of draft-ietf-nea-pt-tls-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 16:53:57 -0000

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

Thanks for the detailed review, comments are in-lined...

From: Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: Monday, June 04, 2012 2:20 PM
To: draft-ietf-nea-pt-tls.all@tools.ietf.org
Cc: 'IETF'; gen-art@ietf.org
Subject: GenART LC review of draft-ietf-nea-pt-tls-05

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.



Document: draft-ietf-nea-pt-tls-05

Reviewer: Roni Even

Review Date:2012-6-4

IETF LC End Date: 2012-6-13

IESG Telechat date:



Summary: This draft is almost ready for publication as a standard track RFC=
.



Major issues:



Minor issues:

1.       In section 3.2 "Therefore, this specification requests the IANA re=
serve a TCP port number for use with the PT-TLS protocol upon publication o=
f this specification as an Internet standard RFC." I think it will  be bett=
er to have here the assigned port number and instruct the RFC editor to put=
 the correct value.



[PS:] Ok, we can reword this in hopes of getting a particular value (race c=
ondition with other upcoming RFCs).



2.       In section 3.4.2.2 last paragraph you summarize the text from sect=
ion 3.8 while in the paragraph above you provide the reference. Why do you =
need the last paragraph if 3.8 is referenced.



[PS:] The goal of this section is to introduce and summarize the different =
phases of PT-TLS.  We felt a brief discussion of the general message flow w=
as helpful to the reader to understand what occurs during this phase (simil=
ar to what we did in the other sub-sections).  Your correct that this infor=
mation is covered later in more detail.



3.       In various places you refer to SMI 0 as IETF SMI number while acco=
rding to the table it is IANA SMI number.



[PS:] I presume this is about the PEN 0 being for the IETF.  Correct, it's =
the IETF's name space that administered by the IANA.  What text would you l=
ike to see to make this more clear?  Can we do it in one place, for example=
 stating that the IETF name space is administered by the IANA?



4.       I assume that all implementations MUST support message type vendor=
 ID 0. Is this mentioned?



[PS:] The purpose of this section was just to summarize and enumerate the m=
essage types for vendor id 0.   I don't think it's a general rule that any =
message type defined in the IETF (IANA :)) name space must (or should be) s=
upported by all implementations.  It will vary depending on the purpose of =
the message so that normative language is included in the descriptions of t=
he message.



5.       In section 3.5 and 6.1 you propose a policy of "Expert Review with=
 Specification Required ". I think that according to RFC5226 expert review =
is implied if you select a specification required policy.



[PS:] I agree, it says "Specification Required also implies use of a Design=
ated Expert".  The policy is just "Specification Required" so we could remo=
ve the "Expert Review with" and make it clear it's the Specification Requir=
ed IANA policy.



6.       In section 3.6 on 9+ "Recipients of messages   of type 9 or higher=
 that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message T=
ype of a received PT-TLS message MUST respond with a Type Not Supported PT-=
TLS error code in a PT-TLS Error message." I think this is true only for Me=
ssage Type Vendor ID 0.



[PS:] Thanks will reword this section to make it more clear.



7.       In 3.7.1 for Max vers and prefs ver you say that they MUST be set =
to 1. I think it will be more correct here to say SHOULD since you explain =
afterwards that they may have other values.



[PS:] I think this is a MUST.  The next sentence just points out that this =
normative text might change in a future revision (which is not currently pl=
anned).



8.       In section 3.7.2 "the recipient SHOULD send". Why not make it a MU=
ST here.



[PS:] I ok with making this change, let's see what others think ...



9.       In section 3.7.2 "The version selected MUST be within the Min Vers=
 to Max Vers inclusive range sent in the Version Request   Message" I was e=
xpecting to see pref ver here.



[PS:] Perf is just an informational (hint) preference.



10.   In section 3.8.3 " The SASL client authentication starts when the NEA=
 Server  enters the PT-TLS Negotiation phase and its policy indicates  that=
 an authentication of the NEA Client is necessary but was not performed dur=
ing the TLS handshake protocol " my read of  section 3.8 second paragraph i=
s that it can be done even if was done in the TLS handshake so the last par=
t of the sentence is not correct, if there is a policy you do it anyhow. Th=
is comment is also for the third paragraph.



[PS:] Thanks, this was supposed to be an example.  Will fix these.



11.   In section 3.9 I noticed that you propose to send the entire original=
 message. Isn't it enough to send only the message identifier. This is base=
d on the last sentence of this section.



[PS:] Not "the entire original message" as its at most the first 1024 bytes=
 of the offending message.  This allows the recipient to either caches rece=
ntly sent messages and/or message identifiers when determining what caused =
the error.  We thought this flexibility was useful and had very little cost=
.



12.   Most of the text in section 6.1 repeats RFC5226 but in your words. Ar=
e you trying to change some of RFC5226 text if not why write it in differen=
t words?



[PS:] We were hoping to emphasize the aspects of 5226 that are most importa=
nt to this specification.  We weren't trying to change how the IANA policy =
was interpreted.  Did you think we did so?  Is there a portion of this text=
 that is most troubling or was this just a question?









Nits/editorial comments:


--_000_6E79D623502C70419A9EAB18E4D274252B8B06102FTUS1XCHEVSPIN_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@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;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2023900102;
	mso-list-type:hybrid;
	mso-list-template-ids:-625979886 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Thanks for the detailed review, comments are in-lined&#8230;<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'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:s=
olid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D=
'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><sp=
an style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even =
[mailto:ron.even.tlv@gmail.com] <br><b>Sent:</b> Monday, June 04, 2012 2:20=
 PM<br><b>To:</b> draft-ietf-nea-pt-tls.all@tools.ietf.org<br><b>Cc:</b> 'I=
ETF'; gen-art@ietf.org<br><b>Subject:</b> GenART LC review of draft-ietf-ne=
a-pt-tls-05<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p><p class=3DMsoNormal>I am the assigned Gen-ART reviewer for thi=
s draft. For background on Gen-ART, please see the FAQ at &lt;<a href=3D"ht=
tp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank">ht=
tp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Please res=
olve these comments along with any other Last Call comments you may receive=
.<o:p></o:p></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
PlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif=
"'>Document: draft-ietf-nea-pt-tls-05<o:p></o:p></span></p><p class=3DMsoPl=
ainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'=
>Reviewer: Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review Date:2012=
&#8211;6&#8211;4<o:p></o:p></span></p><p class=3DMsoPlainText><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC End Date: =
2012&#8211;6&#8211;13<o:p></o:p></span></p><p class=3DMsoPlainText><span st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG Telechat d=
ate:<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:=
11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p c=
lass=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","=
sans-serif"'>Summary: This draft is almost ready for publication as a stand=
ard track RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'=
font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"=
Calibri","sans-serif"'>Major issues:<o:p></o:p></span></p><p class=3DMsoPla=
inText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif"'>Minor issues:<o:p></o:p></span=
></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;m=
so-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>1.<sp=
an style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; </span></span></span><![endif]><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif"'>In section 3.2 &#8220;Therefore, this specifica=
tion requests the IANA reserve a TCP port number for use with the PT-TLS pr=
otocol upon publication of this specification as an Internet standard RFC.&=
#8221; I think it will&nbsp; be better to have here the assigned port numbe=
r and instruct the RFC editor to put the correct value.<o:p></o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
PlainText><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>[PS:] Ok, we can reword this in hopes of getting a p=
articular value (race condition with other upcoming RFCs).<o:p></o:p></span=
></i></b></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:=
l0 level1 lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>2.<span style=
=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </sp=
an></span></span><![endif]><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif"'>In section 3.4.2.2 last paragraph you summarize the tex=
t from section 3.8 while in the paragraph above you provide the reference. =
Why do you need the last paragraph if 3.8 is referenced.<o:p></o:p></span><=
/p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oPlainText><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'>[PS:] The goal of this section is to introduce and =
summarize the different phases of PT-TLS.&nbsp; We felt a brief discussion =
of the general message flow was helpful to the reader to understand what oc=
curs during this phase (similar to what we did in the other sub-sections).&=
nbsp; Your correct that this information is covered later in more detail.<o=
:p></o:p></span></i></b></p><p class=3DMsoPlainText><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-=
.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore=
'>3.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; </span></span></span><![endif]><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif"'>In various places you refer to SMI 0 as =
IETF SMI number while according to the table it is IANA SMI number.<o:p></o=
:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'>[PS:] I presume this is about the PEN 0 =
being for the IETF.&nbsp; Correct, it&#8217;s the IETF&#8217;s name space t=
hat administered by the IANA. &nbsp;What text would you like to see to make=
 this more clear?&nbsp; Can we do it in one place, for example stating that=
 the IETF name space is administered by the IANA?<o:p></o:p></span></i></b>=
</p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DM=
soPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1=
 lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif"'><span style=3D'mso-list:Ignore'>4.<span style=3D'font:=
7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span=
></span><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif"'>I assume that all implementations MUST support message type vend=
or ID 0. Is this mentioned?<o:p></o:p></span></p><p class=3DMsoPlainText><s=
pan style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F4=
97D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:=
] The purpose of this section was just to summarize and enumerate the messa=
ge types for vendor id 0.&nbsp; &nbsp;I don&#8217;t think it&#8217;s a gene=
ral rule that any message type defined in the IETF (IANA </span></i></b><b>=
<i><span style=3D'font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</=
span></i></b><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>) name space must (or should be) supported by all=
 implementations.&nbsp; It will vary depending on the purpose of the messag=
e so that normative language is included in the descriptions of the message=
.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-inden=
t:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ign=
ore'>5.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; </span></span></span><![endif]><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif"'>In section 3.5 and 6.1 you propose a =
policy of &#8220;Expert Review with Specification Required &#8220;. I think=
 that according to RFC5226 expert review is implied if you select a specifi=
cation required policy.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] I a=
gree, it says &#8220;Specification Required also implies use of a Designate=
d Expert&#8221;.&nbsp; The policy is just &#8220;Specification Required&#82=
21; so we could remove the &#8220;Expert Review with&#8221; and make it cle=
ar it&#8217;s the Specification Required IANA policy. <o:p></o:p></span></i=
></b></p><p class=3DMsoPlainText style=3D'margin-left:10.5pt'><b><i><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>=
<o:p>&nbsp;</o:p></span></i></b></p><p class=3DMsoPlainText style=3D'margin=
-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New Roman"'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 3.6 o=
n 9+ &#8220;Recipients of messages&nbsp;&nbsp; of type 9 or higher that do =
not support the PT-TLS Message Type Vendor ID and PT-TLS Message Type of a =
received PT-TLS message MUST respond with a Type Not Supported PT-TLS error=
 code in a PT-TLS Error message.&#8221; I think this is true only for Messa=
ge Type Vendor ID 0.<o:p></o:p></span></p><p class=3DMsoPlainText><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] Thanks=
 will reword this section to make it more clear.<o:p></o:p></span></i></b><=
/p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif"'><span style=3D'mso-list:Ignore'>7.<span style=3D'font:7=
.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>=
</span><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif"'>In 3.7.1 for Max vers and prefs ver you say that they MUST be set=
 to 1. I think it will be more correct here to say SHOULD since you explain=
 afterwards that they may have other values.<o:p></o:p></span></p><p class=
=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText>=
<b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";co=
lor:#1F497D'>[PS:] I think this is a MUST.&nbsp; The next sentence just poi=
nts out that this normative text might change in a future revision (which i=
s not currently planned).<o:p></o:p></span></i></b></p><p class=3DMsoPlainT=
ext><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";colo=
r:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=3D'mar=
gin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLis=
ts]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><sp=
an style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New Roman"'=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 3.=
7.2 &#8220;the recipient SHOULD send&#8221;. Why not make it a MUST here.<o=
:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>[PS:] I ok with making this change=
, let&#8217;s see what others think &#8230;<o:p></o:p></span></i></b></p><p=
 class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlai=
nText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'=
><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif"'><span style=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt =
"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></spa=
n><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-ser=
if"'>In section 3.7.2 &#8220;The version selected MUST be within the Min Ve=
rs to Max Vers inclusive range sent in the Version Request&nbsp;&nbsp; Mess=
age&#8221; I was expecting to see pref ver here.<o:p></o:p></span></p><p cl=
ass=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainTe=
xt><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"=
;color:#1F497D'>[PS:] Perf is just an informational (hint) preference.<o:p>=
</o:p></span></i></b></p><p class=3DMsoPlainText><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25=
in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>1=
0.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span><=
/span><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif"'>In section 3.8.3 &#8220; The SASL client authentication starts whe=
n the NEA Server&nbsp; enters the PT-TLS Negotiation phase and its policy i=
ndicates&nbsp; that an authentication of the NEA Client is necessary but wa=
s not performed during the TLS handshake protocol &#8220; my read of&nbsp; =
section 3.8 second paragraph is that it can be done even if was done in the=
 TLS handshake so the last part of the sentence is not correct, if there is=
 a policy you do it anyhow. This comment is also for the third paragraph.<o=
:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>[PS:] Thanks, this was supposed to=
 be an example.&nbsp; Will fix these.<o:p></o:p></span></i></b></p><p class=
=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if=
 !supportLists]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif"'><span style=3D'mso-list:Ignore'>11.<span style=3D'font:7.0pt "Time=
s New Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 3.9 I noticed=
 that you propose to send the entire original message. Isn&#8217;t it enoug=
h to send only the message identifier. This is based on the last sentence o=
f this section.<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&n=
bsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] Not &#8220;=
the entire original message&#8221; as its at most the first 1024 bytes of t=
he offending message.&nbsp; This allows the recipient to either caches rece=
ntly sent messages and/or message identifiers when determining what caused =
the error. &nbsp;We thought this flexibility was useful and had very little=
 cost.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span style=3D'=
font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-=
indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'=
font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-lis=
t:Ignore'>12.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </sp=
an></span></span><![endif]><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif"'>Most of the text in section 6.1 repeats RFC5226 but in =
your words. Are you trying to change some of RFC5226 text if not why write =
it in different words?<o:p></o:p></span></p><p class=3DMsoPlainText><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] We w=
ere hoping to emphasize the aspects of 5226 that are most important to this=
 specification.&nbsp; We weren&#8217;t trying to change how the IANA policy=
 was interpreted.&nbsp; Did you think we did so?&nbsp; Is there a portion o=
f this text that is most troubling or was this just a question?<o:p></o:p><=
/span></i></b></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f"'>Nits/editorial comments:<o:p></o:p></span></p><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p></div></div></body></html>=

--_000_6E79D623502C70419A9EAB18E4D274252B8B06102FTUS1XCHEVSPIN_--

From mccap@petoni.org  Wed Jun 13 18:08:47 2012
Return-Path: <mccap@petoni.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D40AE11E80C2 for <gen-art@ietfa.amsl.com>; Wed, 13 Jun 2012 18:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jltvE0AU9bo3 for <gen-art@ietfa.amsl.com>; Wed, 13 Jun 2012 18:08:47 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id E704611E80AC for <gen-art@ietf.org>; Wed, 13 Jun 2012 18:08:46 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so807211qcs.31 for <gen-art@ietf.org>; Wed, 13 Jun 2012 18:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=gCLV3UDpx65DGPOm8Oc+jx05M8S9B6iTd63/4c9gvl0=; b=GGcz6yV/P6DCeLqmLF+K6+JOLj9PY/yjY/oMLh1PdNxk9gMkA5q+RWp8XVfI8UGgH8 uaiqvZicnzjU8j4fN9WJzBz2S5bHxBh0b65DA9VJYlPyMKejpMpXbmt5nKgZaKS/T/eQ 5lM0p8udYFMqNqTILnu6rj2wpEoTxa6fUOaGE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=gCLV3UDpx65DGPOm8Oc+jx05M8S9B6iTd63/4c9gvl0=; b=A8RKrlM7BM4FsqKuhj2/f8yzrd4EhK2WLBCfzZB0bqlz3oxv8x/Rg/B3ZBZ87r7CHx 6LOsrUhJm6hAOpDqBFtWTMSEAs66KoYPc25gPHYWPpnf80WPK5XHkwz7mMGcBnZgK+Jt 3a3fa1salgvwCfFt1/EVO6sKxZhD+WDf9hnUMQYt7oJPQa0kb6RWEIIU/EQU6BfjgBch Ine9PwGuqaQOCS5SOWUnurUyHn9tEdsPtlq62/yeUejHjVKaIP0Yz1m5QcWA68SWDsMF m69g4NxJlYiuLydVDnT942QVjM/AYo+LpXt9ddTi5IaEt/FymA/IiIe03K2AZzgE3K3T 0XkA==
MIME-Version: 1.0
Received: by 10.224.176.148 with SMTP id be20mr965743qab.64.1339636125674; Wed, 13 Jun 2012 18:08:45 -0700 (PDT)
Received: by 10.229.232.138 with HTTP; Wed, 13 Jun 2012 18:08:45 -0700 (PDT)
X-Originating-IP: [68.45.157.93]
Date: Wed, 13 Jun 2012 21:08:45 -0400
Message-ID: <CACvMsLHFbjPVk0m05c51BgDFAxFVvDErE8wETdZVn4Qd-iaisA@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org,  draft-camarillo-rai-media-policy-dataset.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlAfqZ5kkpCTPctRMfNUbZECTBEJ5aNhRs88ewW75qdWP+W9nyBYXsBa30xnjZzeo9qT2Hy
Subject: [Gen-art] Gen-ART Last Call Review of draft-camarillo-rai-media-policy-dataset-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 01:08:47 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-camarillo-rai-media-policy-dataset-01
Reviewer: Peter McCann
Review Date: 2012-06-13
IETF LC End Date: 2012-06-11
IESG Telechat date: (if known)

Summary: Ready

Major issues: none

Minor issues: none

Nits/editorial comments:

Section 5.1.2:
   encoding
   of profile
SHOULD BE:
   encoding
   or profile

Section 9:
   those face policies
SHOULD BE:
   those fake policies

From ben@nostrum.com  Thu Jun 14 14:58:48 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9200F11E8080; Thu, 14 Jun 2012 14:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QsveMV+FzJQ1; Thu, 14 Jun 2012 14:58:47 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id B930F21F84AC; Thu, 14 Jun 2012 14:58:47 -0700 (PDT)
Received: from frankenstein.test.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q5ELwk8X082296 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 14 Jun 2012 16:58:47 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Thu, 14 Jun 2012 16:58:46 -0500
Message-Id: <C8476C40-FE78-4712-B76A-88C324715579@nostrum.com>
To: draft-ietf-6man-rfc3484bis.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-6man-rfc3484bis-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 21:58:48 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-6man-rfc3484bis-05
Reviewer: Ben Campbell=09
Review Date: 2012-06-14
IETF LC End Date: 2012-06-15

Summary: This draft is almost ready for publication as a proposed =
standard. I have one security consideration question that should be =
addressed first. I also have some editorial comments that might be worth =
addressing if there is a revision prior to publication.

Note: As always, reviewing a "bis" draft is difficult for someone who =
has not been involved in its creation, as one may comment on issues =
inherited from the original RFC that were not in scope to be fixed in a =
particular "bis" draft. Apologies in advance if I run afoul of such =
things.

Major issues:

None


Minor issues:

-- security considerations, 1st paragraph: "This document has no direct =
impact on Internet infrastructure security."

Can source and/or destination address selection could influence whether =
data is sent over and encrypted path? In particularly true since section =
7 allows the address selection to influence interface selection? If so, =
it's worth mentioning the fact, and considering whether an encrypted =
path vs unencrypted path should be considered in the selection rules. =
Perhaps such decisions should be made prior to following the rules in =
this draft--but if so it would be helpful to explicitly say that.

Nits/editorial comments:

-- section 3/5, last paragraph: "Whether or not an address is designated =
a home address or care-of address is outside the scope of this =
document."

This sentence is confusing since the previous sentence indicated that =
"... it is sufficient to know whether or not one=92s own addresses are =
designated as home addresses or care-of addresses." Is the point that =
the _mechanism_ for making that designation is out of scope, even though =
one needs to know the _results_? Or is this a question about talking =
about one's own addresses vs the destination addresses?

-- section 4, third paragraph: (starting with "Discussion: ..."

I tend to expect indented paragraphs like this to be parenthetical =
notes. The "discussion" label reinforces this. It seems like normative =
statements don't belong in such paragraphs. Can this be promoted to a =
normal paragraph? (Note that this occurs in several other "discussion" =
paragraphs as well.)

-- section 4. last paragraph:

Please expand SIIT on first mention.

-- section 5, general:

It would be helpful to define SA, SB prior to use. ( I note that the =
destination section does this for DA and DB.)

-- section 5, last paragraph:

Since this talks about Rule 2, perhaps it should be moved to immediately =
after rule 2?

-- section 6, discussion paragraph after Rule 7:

Please expand 6RD and ISATAP on first mention.

-- section 10.6, first paragraph:

Please expand ULAs on first mention.



--=20





From mahoney@nostrum.com  Thu Jun 14 16:49:50 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0680D21F8526 for <gen-art@ietfa.amsl.com>; Thu, 14 Jun 2012 16:49:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lyWS4+ZMCZ6S for <gen-art@ietfa.amsl.com>; Thu, 14 Jun 2012 16:49:49 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 598FD21F8510 for <gen-art@ietf.org>; Thu, 14 Jun 2012 16:49:48 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([4.30.77.1]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q5ENneGD087600 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 14 Jun 2012 18:49:44 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FDA7893.9050906@nostrum.com>
Date: Thu, 14 Jun 2012 18:49:39 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-06-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 23:49:50 -0000

Hi all,

The following reviewers have assignments:

Reviewer              LC end      Draft

Alexey Melnikov   2012-06-27    draft-ietf-oauth-v2-bearer-20 *

David Black       2012-06-28    draft-ietf-bliss-shared-appearances-11

Mary Barnes       2012-07-11    draft-krishnan-nomcom-tools-01

Peter McCann      2012-06-26    draft-ietf-bmwg-2544-as-04

Peter Yee         2012-06-28    draft-ietf-ippm-twamp-value-added-octets-03

Richard Barnes    2012-06-28    draft-ietf-nfsv4-federated-fs-admin-11

* 2nd LC


I will make assignments in the review tool and update the webdav when 
the services become available again (TBD) and send out a note.

The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mahoney@nostrum.com  Thu Jun 14 16:50:49 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF22B21F852D for <gen-art@ietfa.amsl.com>; Thu, 14 Jun 2012 16:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tt8zKsVmotuS for <gen-art@ietfa.amsl.com>; Thu, 14 Jun 2012 16:50:49 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 082A121F852B for <gen-art@ietf.org>; Thu, 14 Jun 2012 16:50:48 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([4.30.77.1]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q5ENomr2087745 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 14 Jun 2012 18:50:48 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FDA78D8.6020505@nostrum.com>
Date: Thu, 14 Jun 2012 18:50:48 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-06-21 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 23:50:49 -0000

Hi all,

The following reviewers have assignments:

Reviewer                 LC end      Draft

Allyn Romanow           2012-05-28   draft-polk-ipr-disclosure-04

Ben Campbell            2012-06-12   draft-ietf-6man-rfc3484bis-05

Brian Carpenter         2012-06-09   draft-ietf-spfbis-experiment-11 *

Christer Holmberg       2012-06-08   
draft-ietf-mif-dns-server-selection-09 **

David Black             2012-06-04   draft-kucherawy-marf-source-ports-04 *

Joel Halpern            2012-06-18   
draft-ietf-vcarddav-oma-cab-extensions -02
Joel Halpern            2012-06-04 draft-farrresnickel-ipr-sanctions-06*

Meral Shirazipour       2012-06-20   draft-ietf-trill-clear-correct-03
Meral Shirazipour       2012-06-12   draft-ietf-grow-simple-va-09 **

Miguel Garcia           2012-06-12   draft-ietf-pim-ecmp -03 **
Miguel Garcia           2012-06-20   draft-ietf-trill-rbridge-channel-06

Peter McCann            2012-06-12   draft-ietf-pim-pop-count-06
Peter McCann            2012-04-26   draft-templin-aero-11 *

Vijay Gurbani           2012-06-06   
draft-ietf-nfsv4-pnfs-block-disk-protection-02 **

Wassim Haddad           2012-06-06   draft-ietf-cdni-problem-statement-06


* Earlier draft reviewed
** Already reviewed


I will update the review tool and the spreadsheets when the services 
become available again.

For your convenience, the review boilerplate template is included below.

Note that reviews should ideally be posted to the gen-art mailing list
by COB on Tuesday:
http://wiki.tools.ietf.org/area/gen/trac/wiki/

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From david.black@emc.com  Fri Jun 15 15:03:10 2012
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB2CC21F846F for <gen-art@ietfa.amsl.com>; Fri, 15 Jun 2012 15:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BIEHeaA0x9+4 for <gen-art@ietfa.amsl.com>; Fri, 15 Jun 2012 15:03:10 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0764321F846E for <gen-art@ietf.org>; Fri, 15 Jun 2012 15:03:09 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5FM2PNQ004276 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Jun 2012 18:02:29 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 15 Jun 2012 18:02:11 -0400
Received: from mxhub28.corp.emc.com (mxhub28.corp.emc.com [10.254.110.184]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5FM2Afp032549; Fri, 15 Jun 2012 18:02:10 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub28.corp.emc.com ([10.254.110.184]) with mapi; Fri, 15 Jun 2012 18:02:10 -0400
From: <david.black@emc.com>
To: <richard.clayton@cl.cam.ac.uk>, <superuser@gmail.com>, <gen-art@ietf.org>
Date: Fri, 15 Jun 2012 18:02:08 -0400
Thread-Topic: Gen-ART review of draft-kucherawy-marf-source-ports-04
Thread-Index: Ac0yxioEDxACVAT4RWGXKh8wSGTOFwYfBinA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208C13E64@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712057151FA@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712057151FA@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: johnl@iecc.com, barryleiba@computer.org
Subject: Re: [Gen-art] Gen-ART review of draft-kucherawy-marf-source-ports-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 22:03:11 -0000

The -04 version of this draft addresses the two nits noted in the Gen-ART
review of the -03 version of this draft.  It's ready for publication as a
Proposed Standard RFC.

Thanks,
--David


> -----Original Message-----
> From: Black, David
> Sent: Tuesday, May 15, 2012 2:12 PM
> To: richard.clayton@cl.cam.ac.uk; msk@cloudmark.com; gen-art@ietf.org
> Cc: Black, David; johnl@iecc.com; barryleiba@computer.org
> Subject: Gen-ART review of draft-kucherawy-marf-source-ports-03
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-kucherawy-marf-source-ports-03
> Reviewer: David L. Black
> Review Date: May 15, 2012
> IETF LC End Date: June 4, 2012
>=20
> This is a short draft that adds source ports to the Abuse Reporting Forma=
t for
> mail abuse reporting.
>=20
> Summary:
> This draft is basically ready for publication, but has nits that should b=
e
> fixed before publication.
>=20
> Major issues: None.
>=20
> Minor issues: None.
>=20
> Nits/editorial comments:
>=20
>   In section 3, please summarize what the "CFWS" ABNF element represents
> (comments and folding white space).
>=20
>   Typo in last paragraph of section 3: "RECOMMENED" -> "RECOMMENDED"
>=20
>   idnits 2.12.13 didn't find anything that requires attention.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From jmh@joelhalpern.com  Sat Jun 16 10:42:06 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E027821F848F for <gen-art@ietfa.amsl.com>; Sat, 16 Jun 2012 10:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.275
X-Spam-Level: 
X-Spam-Status: No, score=-102.275 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KBRKYBZW2xbh for <gen-art@ietfa.amsl.com>; Sat, 16 Jun 2012 10:42:06 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFD121F847E for <gen-art@ietf.org>; Sat, 16 Jun 2012 10:42:06 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 21D94558123 for <gen-art@ietf.org>; Sat, 16 Jun 2012 10:42:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id E673B1BCE56B; Sat, 16 Jun 2012 10:42:03 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.105] (pool-71-161-51-75.clppva.btas.verizon.net [71.161.51.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 613611BCE56D; Sat, 16 Jun 2012 10:42:03 -0700 (PDT)
Message-ID: <4FDCC565.7000307@joelhalpern.com>
Date: Sat, 16 Jun 2012 13:41:57 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4FAC34F6.20700@nostrum.com>
In-Reply-To: <4FAC34F6.20700@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]   review: draft-farrresnickel-ipr-sanctions-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 17:42:07 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-farrresnickel-ipr-sanctions-06.txt
     Sanctions Available for Application to Violators of IETF IPR Policy
Reviewer: Joel M. Halpern
Review Date: 16-June-2012
IETF LC End Date: 04-June-2012
IESG Telechat date: 21-June-2012

Summary: This document is ready for publication as an Informational RFC.

Issues: None
    The changes in this last revision significantly improve the document.

From jmh@joelhalpern.com  Sat Jun 16 10:44:07 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B06321F848F for <gen-art@ietfa.amsl.com>; Sat, 16 Jun 2012 10:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HrZHVG1uT-SS for <gen-art@ietfa.amsl.com>; Sat, 16 Jun 2012 10:44:06 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id DCAF421F847E for <gen-art@ietf.org>; Sat, 16 Jun 2012 10:44:06 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id CC8FCA3990 for <gen-art@ietf.org>; Sat, 16 Jun 2012 10:44:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 6A1071BCE59D; Sat, 16 Jun 2012 10:44:06 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.105] (pool-71-161-51-75.clppva.btas.verizon.net [71.161.51.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id BA08E1BCE596; Sat, 16 Jun 2012 10:44:05 -0700 (PDT)
Message-ID: <4FDCC5E0.9040702@joelhalpern.com>
Date: Sat, 16 Jun 2012 13:44:00 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4FD11843.4050006@nostrum.com>
In-Reply-To: <4FD11843.4050006@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Simon Perreault <simon.perreault@viagenie.ca>, gen-art@ietf.org
Subject: [Gen-art] [Gen-Art] Review: draft-ietf-vcarddav-oma-cab-extensions-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2012 17:44:07 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-vcarddav-oma-cab-extensions-02
vCard Format extension : represent vCard extensions
            defined by the Open Mobile Alliance (OMA)
            Converged Address Book (CAB) group
Reviewer: Joel M. Halpern
Review Date: 8-June-2012
IETF LC End Date: 18-June-2012
IESG Telechat date: N/A

Summary: This document is ready for publications as a Proposed Standard RFC

Major issues: None

Minor issues:
     The documents needs text on normative terminology and a reference 
two RFC 2119. (There is one explicit MUST.)


Nits/editorial comments:
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art


From brian.e.carpenter@gmail.com  Sun Jun 17 01:17:30 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C86621F85F7 for <gen-art@ietfa.amsl.com>; Sun, 17 Jun 2012 01:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.378
X-Spam-Level: 
X-Spam-Status: No, score=-101.378 tagged_above=-999 required=5 tests=[AWL=0.313, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BpUdYoeB6zvO for <gen-art@ietfa.amsl.com>; Sun, 17 Jun 2012 01:17:29 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 41FF421F85F6 for <gen-art@ietf.org>; Sun, 17 Jun 2012 01:17:29 -0700 (PDT)
Received: by eaaq13 with SMTP id q13so1412714eaa.31 for <gen-art@ietf.org>; Sun, 17 Jun 2012 01:17:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=1IGoc3YpC0S8GfD3p+2WFVCLS9K6hcMxHwf5PfqZ630=; b=c92VwPs2K0SaTIfAQK1/ZtKZn68e/9X4INR4GiwoKVGR6Kr54akks2EeYYJ+/SFPXg Y4cL07onFP8Y8JajQm8ujwAMBoguQ/uqP+H9Oh6cuTJpH0Z1plm5a5Tl4+ngxnZ1k/// 1YCGIluc/9rsCK2xwrH/2JNs7tc/bNJEcRZbArLWjg5WQ2oKHOXwjfyphNMT8dd2lBe6 7PGg/0H1RvCvSchZRfcaiI6KnuawPPZJw0cvgT344cm8n9RmN5ziLVkur4uQ3WnxPti7 ifAx8SNbcYo+npwBClPHL9jiS7lZSnfl61S7GABK19YSqzMCzza5M6agzzNn6RjP1Qr4 ZsIA==
Received: by 10.14.127.132 with SMTP id d4mr2640148eei.116.1339921047869; Sun, 17 Jun 2012 01:17:27 -0700 (PDT)
Received: from [192.168.1.66] (host-2-102-218-189.as13285.net. [2.102.218.189]) by mx.google.com with ESMTPS id e45sm48508917eeb.6.2012.06.17.01.17.26 (version=SSLv3 cipher=OTHER); Sun, 17 Jun 2012 01:17:26 -0700 (PDT)
Message-ID: <4FDD9294.3090900@gmail.com>
Date: Sun, 17 Jun 2012 09:17:24 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-spfbis-experiment.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------090509070408090707090204"
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-spfbis-experiment-11.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 08:17:30 -0000

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

Please see attached review.


--------------090509070408090707090204
Content-Type: text/plain;
 name="draft-ietf-spfbis-experiment-11-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-spfbis-experiment-11-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZyb20geW91ciBkb2N1bWVudCBzaGVwaGVy
ZA0Kb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuIA0K
DQpEb2N1bWVudDogZHJhZnQtaWV0Zi1zcGZiaXMtZXhwZXJpbWVudC0xMS50eHQNClJldmll
d2VyOiBCcmlhbiBDYXJwZW50ZXINClJldmlldyBEYXRlOiAyMDEyLTA2LTE3DQpJRVRGIExD
IEVuZCBEYXRlOiAyMDEyLTA2LTA5DQpJRVNHIFRlbGVjaGF0IGRhdGU6IDIwMTItMDYtMjEN
Cg0KU3VtbWFyeTogIFJlYWR5DQotLS0tLS0tLQ0KDQpDb21tZW50czoNCi0tLS0tLS0tLQ0K
DQpNeSBMYXN0IENhbGwgY29tbWVudHMgaGF2ZSBiZWVuIGFkZHJlc3NlZCwgdGhhbmtzLg0K
DQo=
--------------090509070408090707090204--

From mahoney@nostrum.com  Mon Jun 18 08:30:17 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4228A21F86FA for <gen-art@ietfa.amsl.com>; Mon, 18 Jun 2012 08:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4s6LG3Zsx6kn for <gen-art@ietfa.amsl.com>; Mon, 18 Jun 2012 08:30:16 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 86E0321F86F9 for <gen-art@ietf.org>; Mon, 18 Jun 2012 08:30:15 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-51-177.dllstx.fios.verizon.net [173.71.51.177]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q5IFUE6f073210 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Mon, 18 Jun 2012 10:30:15 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FDF4986.509@nostrum.com>
Date: Mon, 18 Jun 2012 10:30:14 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
References: <4FDA78D8.6020505@nostrum.com>
In-Reply-To: <4FDA78D8.6020505@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.51.177 is authenticated by a trusted mechanism)
Subject: Re: [Gen-art] Assignments for the 2012-06-21 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 15:30:17 -0000

Hi all,

Although the review tool is still down, the webDAV is back up.

The latest LC and telechat assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

I'll send out an update on the tool's status when I receive it.

Thanks!

Jean


On 6/14/12 6:50 PM, A. Jean Mahoney wrote:
> Hi all,
>
> The following reviewers have assignments:
>
> Reviewer                 LC end      Draft
>
> Allyn Romanow           2012-05-28   draft-polk-ipr-disclosure-04
>
> Ben Campbell            2012-06-12   draft-ietf-6man-rfc3484bis-05
>
> Brian Carpenter         2012-06-09   draft-ietf-spfbis-experiment-11 *
>
> Christer Holmberg       2012-06-08   
> draft-ietf-mif-dns-server-selection-09 **
>
> David Black             2012-06-04   
> draft-kucherawy-marf-source-ports-04 *
>
> Joel Halpern            2012-06-18   
> draft-ietf-vcarddav-oma-cab-extensions -02
> Joel Halpern            2012-06-04 draft-farrresnickel-ipr-sanctions-06*
>
> Meral Shirazipour       2012-06-20   draft-ietf-trill-clear-correct-03
> Meral Shirazipour       2012-06-12   draft-ietf-grow-simple-va-09 **
>
> Miguel Garcia           2012-06-12   draft-ietf-pim-ecmp -03 **
> Miguel Garcia           2012-06-20   draft-ietf-trill-rbridge-channel-06
>
> Peter McCann            2012-06-12   draft-ietf-pim-pop-count-06
> Peter McCann            2012-04-26   draft-templin-aero-11 *
>
> Vijay Gurbani           2012-06-06   
> draft-ietf-nfsv4-pnfs-block-disk-protection-02 **
>
> Wassim Haddad           2012-06-06   draft-ietf-cdni-problem-statement-06
>
>
> * Earlier draft reviewed
> ** Already reviewed
>
>
> I will update the review tool and the spreadsheets when the services 
> become available again.
>
> For your convenience, the review boilerplate template is included below.
>
> Note that reviews should ideally be posted to the gen-art mailing list
> by COB on Tuesday:
> http://wiki.tools.ietf.org/area/gen/trac/wiki/
>
> Jean
>
> -------------------------------------------------------------------
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document:
> Reviewer:
> Review Date:
> IETF LC End Date:
> IESG Telechat date: (if known)
>
> Summary:
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From miguel.a.garcia@ericsson.com  Tue Jun 19 00:26:40 2012
Return-Path: <miguel.a.garcia@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A6F021F84D9 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 00:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UnDnGOYznHtE for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 00:26:39 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id E5F3621F85E6 for <gen-art@ietf.org>; Tue, 19 Jun 2012 00:26:38 -0700 (PDT)
X-AuditID: c1b4fb25-b7fbf6d000002e5d-3d-4fe029ad8397
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 35.20.11869.DA920EF4; Tue, 19 Jun 2012 09:26:37 +0200 (CEST)
Received: from [159.107.24.226] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.264.0; Tue, 19 Jun 2012 09:26:36 +0200
Message-ID: <4FE029AB.6060108@ericsson.com>
Date: Tue, 19 Jun 2012 09:26:35 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: draft-ietf-trill-rbridge-channel.authors@tools.ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupgluLIzCtJLcpLzFFi42KZGfG3Vnet5gN/g4W/hC0urK2xuPrqM4tF /9SdTBaN1/pYHVg8Ll/x9tg56y67x5IlP5k8vlz+zBbAEsVlk5Kak1mWWqRvl8CV8WTKGuaC 3zwVN282sDUwXufsYuTkkBAwkVh15y4LhC0mceHeejYQW0jgFKPE0acZXYxcQPYaRonHR26z gyR4BbQlZh26zNzFyMHBIqAqsXapPEiYTcBconXjRrASUYFgiTOf1kOVC0qcnPkEbL6IgLXE 5mstTCA2s0CmxKqJz5hAxggLOEnM+iUPEbaVuDDnOguELS+x/e0cZohzNCUm31zKPIGRfxaS qbOQtMxC0rKAkXkVo3BuYmZOermRXmpRZnJxcX6eXnHqJkZgaB7c8lt1B+OdcyKHGKU5WJTE ea237vEXEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwFjB90ykctojb8c3oa0Cq/kO/XguNX/W k18i8ZFSjRuTe4XsFhw85Myy5O2+CxNPft8TsPz8bNMpxpPlfimcseO+Hb/4ZEnydg5Bn+vB hWoMWmK3t8hXnQ0XNdrz7elv2atbHic7WPc+EuA+7bfxfPPbaN8yMXHB3g3+1T76+ZOUlSfs XRfQl6DEUpyRaKjFXFScCAAfgXxGGwIAAA==
Cc: nordmark@acm.org, General Area Review Team <gen-art@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-trill-rbridge-channel-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 07:26:40 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft. For background on Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other comments you may receive.

Document: draft-ietf-trill-rbridge-channel-06.txt
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 2012-06-19
IETF LC End Date: 2012-06-20
IESG Telechat date: 2012-06-21

Summary: This document is ready for publication as a standards track RFC

Major issues: none

Minor issues: none

Nits/editorial comments:

The document is well written and easy to read. Congratulations to the 
authors.

I have some minor editorial comments.

- All the figures that represent bits on the wire do not follow the 
convention of numbering the bits. I would suggest to add the bit number 
as per the RFC style guide. This means adding these two lines to most 
figures in the document:


        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1


- Also, related to figures. I would suggest to add a caption to each 
figure, for example, under the figure in Section 2.1:

       Figure 2: RBridge Channel Message inner frame

This allows other documents to easily refer to the figure by number 
(e.g., "Figure 2 in RFC xxxx").



- Section 2.1.1: s/species/specifies

- Section 4. There are 5 bullet points. Something is wrong with the 
indentation of the third bullet point.




/Miguel
-- 
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain

From gonzalo.camarillo@ericsson.com  Tue Jun 19 00:42:41 2012
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA7621F86D5 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 00:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MlotcXVyrrno for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 00:42:37 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0372F21F86D4 for <gen-art@ietf.org>; Tue, 19 Jun 2012 00:42:36 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fc66d000006fdc-aa-4fe02d6b3424
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id C9.AA.28636.B6D20EF4; Tue, 19 Jun 2012 09:42:35 +0200 (CEST)
Received: from [131.160.126.197] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.264.0; Tue, 19 Jun 2012 09:42:35 +0200
Message-ID: <4FE02D6A.6070101@ericsson.com>
Date: Tue, 19 Jun 2012 10:42:34 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <4FC7D2D2.9060008@bell-labs.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C07386A45@xmb-sjc-234.amer.cisco.com> <A0778DDE5E0445E0AEAA5A21A523D53A@china.huawei.com>
In-Reply-To: <A0778DDE5E0445E0AEAA5A21A523D53A@china.huawei.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsUyM+JvrW627gN/g4PfNCwez13AarHgcqLF pllf2CyuvvrMYvH70DxWi4Y1cg5sHn2XXTym/N7I6tFy5C2rx5IlP5k8ei7NZvT4cvkzWwBb FJdNSmpOZllqkb5dAldG57ljLAWbxCpe7N7O2MA4X6iLkZNDQsBE4v2qTkYIW0ziwr31bF2M XBxCAqcYJVYtfcIC4axllPj95hY7SBWvgLbEj7e/wTpYBFQlOr7NYQOx2QQsJLbcus8CYosK BEvM677JAlEvKHFy5hMwW0RAXqJh811GkKHMAiuYJH7tXAY2SFjAS+LApIuMENuWMUr82rEV qIODg1PAQeL14lCI8yQl7rWvBlvGLKAnMeVqCyOELS+x/e0cZhBbCOi45c9aWCYwCs1CsnsW kpZZSFoWMDKvYhTOTczMSS831EstykwuLs7P0ytO3cQIjIiDW37r7mA8dU7kEKM0B4uSOC9X 0n5/IYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYxsO7ctTd/v4ScR6l2dVBLmJXr0SM3klQet F938H7XixHTl9x22/9f2cYc48Pc2nizNfHJNMoHjv1NS7hbOYNvsm8LVIrvuuiw+UPtawC5j QdjF/xa1F/b9WF/gMEPaqOHAj+Ur1l12LplTk1X2LkGVY9PBreeu5HqUxVv5BiY/vL7whvU0 KwclluKMREMt5qLiRAADvYvmVgIAAA==
Cc: Shida Schubert <shida@ntt-at.com>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org>, "Charles Eckel \(eckelcu\)" <eckelcu@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 07:42:41 -0000

Authors,

at this point (the IETF LC is over), could you please revise the draft
in order to address Vijay's comment?

Thanks,

Gonzalo

On 01/06/2012 4:27 AM, Qin Wu wrote:
> Agree, Thanks!
> 
> Regards!
> -Qin
> ----- Original Message ----- 
> From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
> To: "Vijay K. Gurbani" <vkg@bell-labs.com>; <draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org>
> Cc: "General Area Review Team" <gen-art@ietf.org>; "Shida Schubert" <shida@ntt-at.com>; "Gonzalo Camarillo" <gonzalo.camarillo@ericsson.com>
> Sent: Friday, June 01, 2012 4:51 AM
> Subject: RE: Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
> 
> 
> Hi Vijay,
> 
> Thank you for your review. I agree with your comment. It was actually
> one of the WGLC comments:
> http://www.ietf.org/mail-archive/web/xrblock/current/msg00395.html
> 
> This comment in particular seems to have fallen through the cracks.
> Thanks for catching it.
> 
> Cheers,
> Charles
> 
>> -----Original Message-----
>> From: Vijay K. Gurbani [mailto:vkg@bell-labs.com]
>> Sent: Thursday, May 31, 2012 1:22 PM
>> To: draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org
>> Cc: General Area Review Team; Charles Eckel (eckelcu); Shida Schubert;
>> Gonzalo Camarillo
>> Subject: Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
>>
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-xrblock-rtcp-xr-meas-identity-06
>> Reviewer: Vijay K. Gurbani
>> Review Date: May-31-2012
>> IETF LC End Date: June-14-2012
>> IESG Telechat date: Not known
>>
>> Summary: This draft is ready as a Proposed Standard; it has one minor
>> comment that should be fixed before publication.
>>
>> Major: 0
>> Minor: 1
>> Nits: 0
>>
>> Minor:
>>
>> - In S6, the text says that "... the use of security mechanisms with
>>   RTP, as documented in Section 9 of [RFC3550] SHOULD apply."
>>
>>   I am puzzled by the normative language here.  Won't it be more
> proper
>>   to simply say that "... the use of security mechanisms with RTP, as
>>   documented in Section 9 of [RFC3550] apply."
>>
>>   The use of SHOULD seem to indicate that there are certain cases
>>   during measurement reporting where the security considerations do
> not
>>   apply.  Surely you do not mean that, do you?
>>
>> Thanks,
>>
>> - vijay
>> --
>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
>> Web:   http://ect.bell-labs.com/who/vkg/
> 


From bill.wu@huawei.com  Tue Jun 19 01:00:04 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C47A521F864A for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 01:00:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.804
X-Spam-Level: 
X-Spam-Status: No, score=-4.804 tagged_above=-999 required=5 tests=[AWL=0.042,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I-9rY7L2CK7C for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 01:00:03 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id B92BD21F86E5 for <gen-art@ietf.org>; Tue, 19 Jun 2012 01:00:03 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHH94778; Tue, 19 Jun 2012 04:00:03 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 19 Jun 2012 00:58:43 -0700
Received: from SZXEML423-HUB.china.huawei.com (10.82.67.162) by dfweml408-hub.china.huawei.com (10.193.5.134) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 19 Jun 2012 00:58:46 -0700
Received: from w53375 (10.138.41.149) by szxeml423-hub.china.huawei.com (10.82.67.162) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 19 Jun 2012 15:58:39 +0800
Message-ID: <3CCE1436233A413C89DFAAE9C141AFEA@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
References: <4FC7D2D2.9060008@bell-labs.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C07386A45@xmb-sjc-234.amer.cisco.com> <A0778DDE5E0445E0AEAA5A21A523D53A@china.huawei.com> <4FE02D6A.6070101@ericsson.com>
Date: Tue, 19 Jun 2012 15:58:39 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Cc: Shida Schubert <shida@ntt-at.com>, General Area Review Team <gen-art@ietf.org>, draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org, "Charles Eckel \(eckelcu\)" <eckelcu@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 08:00:04 -0000

RG9uZSwgdGhhbmsgZm9yIHlvdXIgcmVtaW5kaW5nLg0KRGlmZjoNCmh0dHA6Ly90b29scy5pZXRm
Lm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3AteHItbWVhcy1pZGVudGl0
eS0wNw0KDQpSZWdhcmRzIQ0KLVFpbiBXVQ0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSAN
CkZyb206ICJHb256YWxvIENhbWFyaWxsbyIgPEdvbnphbG8uQ2FtYXJpbGxvQGVyaWNzc29uLmNv
bT4NClRvOiAiUWluIFd1IiA8YmlsbC53dUBodWF3ZWkuY29tPg0KQ2M6ICJDaGFybGVzIEVja2Vs
IChlY2tlbGN1KSIgPGVja2VsY3VAY2lzY28uY29tPjsgIlZpamF5IEsuIEd1cmJhbmkiIDx2a2dA
YmVsbC1sYWJzLmNvbT47IDxkcmFmdC1pZXRmLXhyYmxvY2stcnRjcC14ci1tZWFzLWlkZW50aXR5
QHRvb2xzLmlldGYub3JnPjsgIkdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbSIgPGdlbi1hcnRAaWV0
Zi5vcmc+OyAiU2hpZGEgU2NodWJlcnQiIDxzaGlkYUBudHQtYXQuY29tPg0KU2VudDogVHVlc2Rh
eSwgSnVuZSAxOSwgMjAxMiAzOjQyIFBNDQpTdWJqZWN0OiBSZTogR2VuLUFSVCByZXZpZXcgb2Yg
ZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3AteHItbWVhcy1pZGVudGl0eS0wNg0KDQoNCj4gQXV0aG9y
cywNCj4gDQo+IGF0IHRoaXMgcG9pbnQgKHRoZSBJRVRGIExDIGlzIG92ZXIpLCBjb3VsZCB5b3Ug
cGxlYXNlIHJldmlzZSB0aGUgZHJhZnQNCj4gaW4gb3JkZXIgdG8gYWRkcmVzcyBWaWpheSdzIGNv
bW1lbnQ/DQo+IA0KPiBUaGFua3MsDQo+IA0KPiBHb256YWxvDQo+IA0KPiBPbiAwMS8wNi8yMDEy
IDQ6MjcgQU0sIFFpbiBXdSB3cm90ZToNCj4+IEFncmVlLCBUaGFua3MhDQo+PiANCj4+IFJlZ2Fy
ZHMhDQo+PiAtUWluDQo+PiAtLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KPj4gRnJvbTog
IkNoYXJsZXMgRWNrZWwgKGVja2VsY3UpIiA8ZWNrZWxjdUBjaXNjby5jb20+DQo+PiBUbzogIlZp
amF5IEsuIEd1cmJhbmkiIDx2a2dAYmVsbC1sYWJzLmNvbT47IDxkcmFmdC1pZXRmLXhyYmxvY2st
cnRjcC14ci1tZWFzLWlkZW50aXR5QHRvb2xzLmlldGYub3JnPg0KPj4gQ2M6ICJHZW5lcmFsIEFy
ZWEgUmV2aWV3IFRlYW0iIDxnZW4tYXJ0QGlldGYub3JnPjsgIlNoaWRhIFNjaHViZXJ0IiA8c2hp
ZGFAbnR0LWF0LmNvbT47ICJHb256YWxvIENhbWFyaWxsbyIgPGdvbnphbG8uY2FtYXJpbGxvQGVy
aWNzc29uLmNvbT4NCj4+IFNlbnQ6IEZyaWRheSwgSnVuZSAwMSwgMjAxMiA0OjUxIEFNDQo+PiBT
dWJqZWN0OiBSRTogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3AteHIt
bWVhcy1pZGVudGl0eS0wNg0KPj4gDQo+PiANCj4+IEhpIFZpamF5LA0KPj4gDQo+PiBUaGFuayB5
b3UgZm9yIHlvdXIgcmV2aWV3LiBJIGFncmVlIHdpdGggeW91ciBjb21tZW50LiBJdCB3YXMgYWN0
dWFsbHkNCj4+IG9uZSBvZiB0aGUgV0dMQyBjb21tZW50czoNCj4+IGh0dHA6Ly93d3cuaWV0Zi5v
cmcvbWFpbC1hcmNoaXZlL3dlYi94cmJsb2NrL2N1cnJlbnQvbXNnMDAzOTUuaHRtbA0KPj4gDQo+
PiBUaGlzIGNvbW1lbnQgaW4gcGFydGljdWxhciBzZWVtcyB0byBoYXZlIGZhbGxlbiB0aHJvdWdo
IHRoZSBjcmFja3MuDQo+PiBUaGFua3MgZm9yIGNhdGNoaW5nIGl0Lg0KPj4gDQo+PiBDaGVlcnMs
DQo+PiBDaGFybGVzDQo+PiANCj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4+IEZy
b206IFZpamF5IEsuIEd1cmJhbmkgW21haWx0bzp2a2dAYmVsbC1sYWJzLmNvbV0NCj4+PiBTZW50
OiBUaHVyc2RheSwgTWF5IDMxLCAyMDEyIDE6MjIgUE0NCj4+PiBUbzogZHJhZnQtaWV0Zi14cmJs
b2NrLXJ0Y3AteHItbWVhcy1pZGVudGl0eUB0b29scy5pZXRmLm9yZw0KPj4+IENjOiBHZW5lcmFs
IEFyZWEgUmV2aWV3IFRlYW07IENoYXJsZXMgRWNrZWwgKGVja2VsY3UpOyBTaGlkYSBTY2h1YmVy
dDsNCj4+PiBHb256YWxvIENhbWFyaWxsbw0KPj4+IFN1YmplY3Q6IEdlbi1BUlQgcmV2aWV3IG9m
IGRyYWZ0LWlldGYteHJibG9jay1ydGNwLXhyLW1lYXMtaWRlbnRpdHktMDYNCj4+Pg0KPj4+IEkg
YW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZvciBiYWNr
Z3JvdW5kIG9uDQo+Pj4gR2VuLUFSVCwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQo+Pj4gPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0KPj4+
DQo+Pj4gUGxlYXNlIHJlc29sdmUgdGhlc2UgY29tbWVudHMgYWxvbmcgd2l0aCBhbnkgb3RoZXIg
TGFzdCBDYWxsIGNvbW1lbnRzDQo+Pj4geW91IG1heSByZWNlaXZlLg0KPj4+DQo+Pj4gRG9jdW1l
bnQ6IGRyYWZ0LWlldGYteHJibG9jay1ydGNwLXhyLW1lYXMtaWRlbnRpdHktMDYNCj4+PiBSZXZp
ZXdlcjogVmlqYXkgSy4gR3VyYmFuaQ0KPj4+IFJldmlldyBEYXRlOiBNYXktMzEtMjAxMg0KPj4+
IElFVEYgTEMgRW5kIERhdGU6IEp1bmUtMTQtMjAxMg0KPj4+IElFU0cgVGVsZWNoYXQgZGF0ZTog
Tm90IGtub3duDQo+Pj4NCj4+PiBTdW1tYXJ5OiBUaGlzIGRyYWZ0IGlzIHJlYWR5IGFzIGEgUHJv
cG9zZWQgU3RhbmRhcmQ7IGl0IGhhcyBvbmUgbWlub3INCj4+PiBjb21tZW50IHRoYXQgc2hvdWxk
IGJlIGZpeGVkIGJlZm9yZSBwdWJsaWNhdGlvbi4NCj4+Pg0KPj4+IE1ham9yOiAwDQo+Pj4gTWlu
b3I6IDENCj4+PiBOaXRzOiAwDQo+Pj4NCj4+PiBNaW5vcjoNCj4+Pg0KPj4+IC0gSW4gUzYsIHRo
ZSB0ZXh0IHNheXMgdGhhdCAiLi4uIHRoZSB1c2Ugb2Ygc2VjdXJpdHkgbWVjaGFuaXNtcyB3aXRo
DQo+Pj4gICBSVFAsIGFzIGRvY3VtZW50ZWQgaW4gU2VjdGlvbiA5IG9mIFtSRkMzNTUwXSBTSE9V
TEQgYXBwbHkuIg0KPj4+DQo+Pj4gICBJIGFtIHB1enpsZWQgYnkgdGhlIG5vcm1hdGl2ZSBsYW5n
dWFnZSBoZXJlLiAgV29uJ3QgaXQgYmUgbW9yZQ0KPj4gcHJvcGVyDQo+Pj4gICB0byBzaW1wbHkg
c2F5IHRoYXQgIi4uLiB0aGUgdXNlIG9mIHNlY3VyaXR5IG1lY2hhbmlzbXMgd2l0aCBSVFAsIGFz
DQo+Pj4gICBkb2N1bWVudGVkIGluIFNlY3Rpb24gOSBvZiBbUkZDMzU1MF0gYXBwbHkuIg0KPj4+
DQo+Pj4gICBUaGUgdXNlIG9mIFNIT1VMRCBzZWVtIHRvIGluZGljYXRlIHRoYXQgdGhlcmUgYXJl
IGNlcnRhaW4gY2FzZXMNCj4+PiAgIGR1cmluZyBtZWFzdXJlbWVudCByZXBvcnRpbmcgd2hlcmUg
dGhlIHNlY3VyaXR5IGNvbnNpZGVyYXRpb25zIGRvDQo+PiBub3QNCj4+PiAgIGFwcGx5LiAgU3Vy
ZWx5IHlvdSBkbyBub3QgbWVhbiB0aGF0LCBkbyB5b3U/DQo+Pj4NCj4+PiBUaGFua3MsDQo+Pj4N
Cj4+PiAtIHZpamF5DQo+Pj4gLS0NCj4+PiBWaWpheSBLLiBHdXJiYW5pLCBCZWxsIExhYm9yYXRv
cmllcywgQWxjYXRlbC1MdWNlbnQNCj4+PiAxOTYwIEx1Y2VudCBMYW5lLCBSbS4gOUMtNTMzLCBO
YXBlcnZpbGxlLCBJbGxpbm9pcyA2MDU2MyAoVVNBKQ0KPj4+IEVtYWlsOiB2a2dAe2JlbGwtbGFi
cy5jb20sYWNtLm9yZ30gLyB2aWpheS5ndXJiYW5pQGFsY2F0ZWwtbHVjZW50LmNvbQ0KPj4+IFdl
YjogICBodHRwOi8vZWN0LmJlbGwtbGFicy5jb20vd2hvL3ZrZy8NCj4+IA0KPiANCj4=


From gonzalo.camarillo@ericsson.com  Tue Jun 19 01:04:39 2012
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A15A221F8613 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 01:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id prmdMesJ9lC7 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 01:04:38 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 31FA221F8596 for <gen-art@ietf.org>; Tue, 19 Jun 2012 01:04:38 -0700 (PDT)
X-AuditID: c1b4fb30-b7f606d0000002be-1f-4fe03294a1eb
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 15.AA.00702.49230EF4; Tue, 19 Jun 2012 10:04:36 +0200 (CEST)
Received: from [131.160.126.197] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.264.0; Tue, 19 Jun 2012 10:04:35 +0200
Message-ID: <4FE03293.6020606@ericsson.com>
Date: Tue, 19 Jun 2012 11:04:35 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <4FC7D2D2.9060008@bell-labs.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C07386A45@xmb-sjc-234.amer.cisco.com> <A0778DDE5E0445E0AEAA5A21A523D53A@china.huawei.com> <4FE02D6A.6070101@ericsson.com> <3CCE1436233A413C89DFAAE9C141AFEA@china.huawei.com>
In-Reply-To: <3CCE1436233A413C89DFAAE9C141AFEA@china.huawei.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUyM+Jvre4Uowf+Bsc3yVs8nruA1WLB5USL TbO+sFlcffWZxeL3oXmsFg1r5BzYPPouu3hM+b2R1aPlyFtWjyVLfjJ59Fyazejx5fJntgC2 KC6blNSczLLUIn27BK6MrVv3sBdMk6uYd+YEUwNjo2QXIyeHhICJxNaHv5ggbDGJC/fWs3Ux cnEICZxilPj56iorSEJIYC2jxMXbPCA2r4C2RE/nPmYQm0VAVeLT3qtgNpuAhcSWW/dZQGxR gWCJed03WSDqBSVOznwCZosIyEs0bL7LCLKAWWAFk8SvncsYQRLCAl4SByZdZITY/ItR4seP G+xdjBwcnAIOEo92OUNcJylxr301G4jNLKAnMeVqCyOELS+x/e0cZohDtSWWP2thmcAoNAvJ 7llIWmYhaVnAyLyKUTg3MTMnvdxcL7UoM7m4OD9Przh1EyMwHg5u+W2wg3HTfbFDjNIcLEri vHqq+/2FBNITS1KzU1MLUovii0pzUosPMTJxcEo1MMb+2yTU3vmhPy6k3fiNprnVy4MLTvp9 K7d9Pr20UKdShnf1/Zbrx1ZLHP5aM8lP277nn63oCU5xY5XSlklsYdOWtN07IPs2v+vrHn5n HzbWbDvW8BkftP6uMdS+uuKoSMhys3N5+6wfzm7eu8jnvdSLpjf7Sx4YJUtXeP/QKG+wEd0n /5apW4mlOCPRUIu5qDgRAK9AdM5VAgAA
Cc: Shida Schubert <shida@ntt-at.com>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org>, "Charles Eckel \(eckelcu\)" <eckelcu@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 08:04:39 -0000

Hi,

thanks for your quick response. I have put this draft on the agenda of
the July 5th IESG telechat.

Cheers,

Gonzalo

On 19/06/2012 10:58 AM, Qin Wu wrote:
> Done, thank for your reminding.
> Diff:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-xrblock-rtcp-xr-meas-identity-07
> 
> Regards!
> -Qin WU
> ----- Original Message ----- 
> From: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>
> To: "Qin Wu" <bill.wu@huawei.com>
> Cc: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>; "Vijay K. Gurbani" <vkg@bell-labs.com>; <draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org>; "General Area Review Team" <gen-art@ietf.org>; "Shida Schubert" <shida@ntt-at.com>
> Sent: Tuesday, June 19, 2012 3:42 PM
> Subject: Re: Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
> 
> 
>> Authors,
>>
>> at this point (the IETF LC is over), could you please revise the draft
>> in order to address Vijay's comment?
>>
>> Thanks,
>>
>> Gonzalo
>>
>> On 01/06/2012 4:27 AM, Qin Wu wrote:
>>> Agree, Thanks!
>>>
>>> Regards!
>>> -Qin
>>> ----- Original Message ----- 
>>> From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
>>> To: "Vijay K. Gurbani" <vkg@bell-labs.com>; <draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org>
>>> Cc: "General Area Review Team" <gen-art@ietf.org>; "Shida Schubert" <shida@ntt-at.com>; "Gonzalo Camarillo" <gonzalo.camarillo@ericsson.com>
>>> Sent: Friday, June 01, 2012 4:51 AM
>>> Subject: RE: Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
>>>
>>>
>>> Hi Vijay,
>>>
>>> Thank you for your review. I agree with your comment. It was actually
>>> one of the WGLC comments:
>>> http://www.ietf.org/mail-archive/web/xrblock/current/msg00395.html
>>>
>>> This comment in particular seems to have fallen through the cracks.
>>> Thanks for catching it.
>>>
>>> Cheers,
>>> Charles
>>>
>>>> -----Original Message-----
>>>> From: Vijay K. Gurbani [mailto:vkg@bell-labs.com]
>>>> Sent: Thursday, May 31, 2012 1:22 PM
>>>> To: draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org
>>>> Cc: General Area Review Team; Charles Eckel (eckelcu); Shida Schubert;
>>>> Gonzalo Camarillo
>>>> Subject: Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
>>>>
>>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>>> Gen-ART, please see the FAQ at
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>
>>>> Please resolve these comments along with any other Last Call comments
>>>> you may receive.
>>>>
>>>> Document: draft-ietf-xrblock-rtcp-xr-meas-identity-06
>>>> Reviewer: Vijay K. Gurbani
>>>> Review Date: May-31-2012
>>>> IETF LC End Date: June-14-2012
>>>> IESG Telechat date: Not known
>>>>
>>>> Summary: This draft is ready as a Proposed Standard; it has one minor
>>>> comment that should be fixed before publication.
>>>>
>>>> Major: 0
>>>> Minor: 1
>>>> Nits: 0
>>>>
>>>> Minor:
>>>>
>>>> - In S6, the text says that "... the use of security mechanisms with
>>>>   RTP, as documented in Section 9 of [RFC3550] SHOULD apply."
>>>>
>>>>   I am puzzled by the normative language here.  Won't it be more
>>> proper
>>>>   to simply say that "... the use of security mechanisms with RTP, as
>>>>   documented in Section 9 of [RFC3550] apply."
>>>>
>>>>   The use of SHOULD seem to indicate that there are certain cases
>>>>   during measurement reporting where the security considerations do
>>> not
>>>>   apply.  Surely you do not mean that, do you?
>>>>
>>>> Thanks,
>>>>
>>>> - vijay
>>>> --
>>>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>>>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>>>> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
>>>> Web:   http://ect.bell-labs.com/who/vkg/
>>>
>>
>>


From ron.even.tlv@gmail.com  Tue Jun 19 02:19:16 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03CDD21F8618; Tue, 19 Jun 2012 02:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IGQ-RRkv8ry0; Tue, 19 Jun 2012 02:19:11 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id D027421F860F; Tue, 19 Jun 2012 02:19:10 -0700 (PDT)
Received: by wibhn6 with SMTP id hn6so2235993wib.13 for <multiple recipients>; Tue, 19 Jun 2012 02:19:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=g0EcFfQrBnG3uPD774u0vmT2+lvD4+Ub2zDnXbZEWyk=; b=iltcSzC0ZYmpgYPjctDBqhtmvi+bvhCuU5eOlJPDEd8/+TQg7F5SwXAdcV6Mte0D7U FVN19SQdvjkbCXzyfGquOY122IShx42yO23NvLZgZCs4W3XCmUpgBSZFWQ2JrBtVCm2K HGLJHjK/HXJYa6o8KKSURBewhaQxlwyAT3b7foh9aIiX0yU8swHNumgg9BpisGWtepKx tDnMHDxpxiKZ5jo1jAryFZxQIs7nCPZOXLLbxx/ycKDy+LVgbr2o4jw5sLCiDUbHIZwt HPkUU4bW245HwqhGgu36mtgUN6SPGznwD4htBZ8rUUmT3JIKKgNVCHeC16ExZX4OAd5i Z7WQ==
Received: by 10.180.86.194 with SMTP id r2mr1643274wiz.15.1340097549696; Tue, 19 Jun 2012 02:19:09 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-177-104-121.red.bezeqint.net. [79.177.104.121]) by mx.google.com with ESMTPS id bn9sm31214527wib.5.2012.06.19.02.19.03 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Jun 2012 02:19:07 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Paul Sangster'" <Paul_Sangster@symantec.com>, <draft-ietf-nea-pt-tls.all@tools.ietf.org>
References: <4fcd272e.2968b40a.55d4.ffff9de3@mx.google.com> <6E79D623502C70419A9EAB18E4D274252B8B06102F@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
In-Reply-To: <6E79D623502C70419A9EAB18E4D274252B8B06102F@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
Date: Tue, 19 Jun 2012 12:16:19 +0300
Message-ID: <4fe0440b.6959b40a.7a49.6095@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0223_01CD4E15.57B56D80"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1Cl9xExNAkih6WSYeHA9SkXDOg7gG388dgASA4xdA=
Content-Language: en-us
Cc: gen-art@ietf.org, nea@ietf.org, 'IETF' <ietf@ietf.org>
Subject: Re: [Gen-art] GenART LC review of draft-ietf-nea-pt-tls-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 09:19:16 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0223_01CD4E15.57B56D80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

I am OK with your responses. The only thing I am not sure is about using PEN
0 defined in the registry.

 

Decimal

| Organization

| | Contact

| | | Email

| | | |

0

  Reserved

    Internet Assigned Numbers Authority

      iana&iana.org

 

I was wondering how this enterprise number should be specified since it
appears as "Reserved" in the registry. I have no specific suggestion

Roni

 

 

From: Paul Sangster [mailto:Paul_Sangster@symantec.com] 
Sent: Wednesday, June 13, 2012 7:56 PM
To: Roni Even; draft-ietf-nea-pt-tls.all@tools.ietf.org
Cc: 'IETF'; gen-art@ietf.org; nea@ietf.org
Subject: RE: GenART LC review of draft-ietf-nea-pt-tls-05

 

Thanks for the detailed review, comments are in-lined.

 

From: Roni Even [mailto:ron.even.tlv@gmail.com] 
Sent: Monday, June 04, 2012 2:20 PM
To: draft-ietf-nea-pt-tls.all@tools.ietf.org
Cc: 'IETF'; gen-art@ietf.org
Subject: GenART LC review of draft-ietf-nea-pt-tls-05

 

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-ietf-nea-pt-tls-05

Reviewer: Roni Even

Review Date:2012-6-4

IETF LC End Date: 2012-6-13

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

Major issues:

 

Minor issues:

1.       In section 3.2 "Therefore, this specification requests the IANA
reserve a TCP port number for use with the PT-TLS protocol upon publication
of this specification as an Internet standard RFC." I think it will  be
better to have here the assigned port number and instruct the RFC editor to
put the correct value.

 

[PS:] Ok, we can reword this in hopes of getting a particular value (race
condition with other upcoming RFCs).

 

2.       In section 3.4.2.2 last paragraph you summarize the text from
section 3.8 while in the paragraph above you provide the reference. Why do
you need the last paragraph if 3.8 is referenced.

 

[PS:] The goal of this section is to introduce and summarize the different
phases of PT-TLS.  We felt a brief discussion of the general message flow
was helpful to the reader to understand what occurs during this phase
(similar to what we did in the other sub-sections).  Your correct that this
information is covered later in more detail.

 

3.       In various places you refer to SMI 0 as IETF SMI number while
according to the table it is IANA SMI number.

 

[PS:] I presume this is about the PEN 0 being for the IETF.  Correct, it's
the IETF's name space that administered by the IANA.  What text would you
like to see to make this more clear?  Can we do it in one place, for example
stating that the IETF name space is administered by the IANA?

 

4.       I assume that all implementations MUST support message type vendor
ID 0. Is this mentioned?

 

[PS:] The purpose of this section was just to summarize and enumerate the
message types for vendor id 0.   I don't think it's a general rule that any
message type defined in the IETF (IANA J) name space must (or should be)
supported by all implementations.  It will vary depending on the purpose of
the message so that normative language is included in the descriptions of
the message.

 

5.       In section 3.5 and 6.1 you propose a policy of "Expert Review with
Specification Required ". I think that according to RFC5226 expert review is
implied if you select a specification required policy.

 

[PS:] I agree, it says "Specification Required also implies use of a
Designated Expert".  The policy is just "Specification Required" so we could
remove the "Expert Review with" and make it clear it's the Specification
Required IANA policy. 

 

6.       In section 3.6 on 9+ "Recipients of messages   of type 9 or higher
that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message
Type of a received PT-TLS message MUST respond with a Type Not Supported
PT-TLS error code in a PT-TLS Error message." I think this is true only for
Message Type Vendor ID 0.

 

[PS:] Thanks will reword this section to make it more clear.

 

7.       In 3.7.1 for Max vers and prefs ver you say that they MUST be set
to 1. I think it will be more correct here to say SHOULD since you explain
afterwards that they may have other values.

 

[PS:] I think this is a MUST.  The next sentence just points out that this
normative text might change in a future revision (which is not currently
planned).

 

8.       In section 3.7.2 "the recipient SHOULD send". Why not make it a
MUST here.

 

[PS:] I ok with making this change, let's see what others think .

 

9.       In section 3.7.2 "The version selected MUST be within the Min Vers
to Max Vers inclusive range sent in the Version Request   Message" I was
expecting to see pref ver here.

 

[PS:] Perf is just an informational (hint) preference.

 

10.   In section 3.8.3 " The SASL client authentication starts when the NEA
Server  enters the PT-TLS Negotiation phase and its policy indicates  that
an authentication of the NEA Client is necessary but was not performed
during the TLS handshake protocol " my read of  section 3.8 second paragraph
is that it can be done even if was done in the TLS handshake so the last
part of the sentence is not correct, if there is a policy you do it anyhow.
This comment is also for the third paragraph.

 

[PS:] Thanks, this was supposed to be an example.  Will fix these.

 

11.   In section 3.9 I noticed that you propose to send the entire original
message. Isn't it enough to send only the message identifier. This is based
on the last sentence of this section.

 

[PS:] Not "the entire original message" as its at most the first 1024 bytes
of the offending message.  This allows the recipient to either caches
recently sent messages and/or message identifiers when determining what
caused the error.  We thought this flexibility was useful and had very
little cost.

 

12.   Most of the text in section 6.1 repeats RFC5226 but in your words. Are
you trying to change some of RFC5226 text if not why write it in different
words?

 

[PS:] We were hoping to emphasize the aspects of 5226 that are most
important to this specification.  We weren't trying to change how the IANA
policy was interpreted.  Did you think we did so?  Is there a portion of
this text that is most troubling or was this just a question?

 

 

 

 

Nits/editorial comments:

 


------=_NextPart_000_0223_01CD4E15.57B56D80
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-microsoft-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=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@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-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
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";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
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;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2023900102;
	mso-list-type:hybrid;
	mso-list-template-ids:-625979886 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I am OK with your =
responses. The only thing I am not sure is about using PEN 0 defined in =
the registry.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Decimal<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>| =
Organization<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>| | =
Contact<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>| | | =
Email<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>| | | =
|<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New"'>0<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp; =
Reserved<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp; Internet Assigned Numbers =
Authority<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
iana&amp;iana.org<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I was wondering how this =
enterprise number should be specified since it appears as =
&quot;Reserved&quot; in the registry. I have no specific =
suggestion<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'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=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Paul Sangster [mailto:Paul_Sangster@symantec.com] <br><b>Sent:</b> =
Wednesday, June 13, 2012 7:56 PM<br><b>To:</b> Roni Even; =
draft-ietf-nea-pt-tls.all@tools.ietf.org<br><b>Cc:</b> 'IETF'; =
gen-art@ietf.org; nea@ietf.org<br><b>Subject:</b> RE: GenART LC review =
of draft-ietf-nea-pt-tls-05<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks for the detailed review, comments are =
in-lined&#8230;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'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=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Roni Even [<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Sent:</b> Monday, June 04, 2012 2:20 PM<br><b>To:</b> <a =
href=3D"mailto:draft-ietf-nea-pt-tls.all@tools.ietf.org">draft-ietf-nea-p=
t-tls.all@tools.ietf.org</a><br><b>Cc:</b> 'IETF'; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
GenART LC review of =
draft-ietf-nea-pt-tls-05<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
draft-ietf-nea-pt-tls-05<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;6&#8211;4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;6&#8211;13<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as a standard track =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.2 &#8220;Therefore, this specification requests the IANA reserve a TCP =
port number for use with the PT-TLS protocol upon publication of this =
specification as an Internet standard RFC.&#8221; I think it will&nbsp; =
be better to have here the assigned port number and instruct the RFC =
editor to put the correct value.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] Ok, we can reword this in hopes of getting a particular value =
(race condition with other upcoming =
RFCs).<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.4.2.2 last paragraph you summarize the text from section 3.8 while in =
the paragraph above you provide the reference. Why do you need the last =
paragraph if 3.8 is referenced.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] The goal of this section is to introduce and summarize the =
different phases of PT-TLS.&nbsp; We felt a brief discussion of the =
general message flow was helpful to the reader to understand what occurs =
during this phase (similar to what we did in the other =
sub-sections).&nbsp; Your correct that this information is covered later =
in more detail.<o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In various =
places you refer to SMI 0 as IETF SMI number while according to the =
table it is IANA SMI number.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] I presume this is about the PEN 0 being for the IETF.&nbsp; =
Correct, it&#8217;s the IETF&#8217;s name space that administered by the =
IANA. &nbsp;What text would you like to see to make this more =
clear?&nbsp; Can we do it in one place, for example stating that the =
IETF name space is administered by the =
IANA?<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I assume =
that all implementations MUST support message type vendor ID 0. Is this =
mentioned?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] The purpose of this section was just to summarize and enumerate =
the message types for vendor id 0.&nbsp; &nbsp;I don&#8217;t think =
it&#8217;s a general rule that any message type defined in the IETF =
(IANA </span></i></b><b><i><span =
style=3D'font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span></=
i></b><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>) name space must (or should be) supported by all =
implementations.&nbsp; It will vary depending on the purpose of the =
message so that normative language is included in the descriptions of =
the message.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.5 and 6.1 you propose a policy of &#8220;Expert Review with =
Specification Required &#8220;. I think that according to RFC5226 expert =
review is implied if you select a specification required =
policy.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] I agree, it says &#8220;Specification Required also implies use =
of a Designated Expert&#8221;.&nbsp; The policy is just =
&#8220;Specification Required&#8221; so we could remove the =
&#8220;Expert Review with&#8221; and make it clear it&#8217;s the =
Specification Required IANA policy. <o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText style=3D'margin-left:10.5pt'><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></i></b></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.6 on 9+ &#8220;Recipients of messages&nbsp;&nbsp; of type 9 or higher =
that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message =
Type of a received PT-TLS message MUST respond with a Type Not Supported =
PT-TLS error code in a PT-TLS Error message.&#8221; I think this is true =
only for Message Type Vendor ID 0.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] Thanks will reword this section to make it more =
clear.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In 3.7.1 =
for Max vers and prefs ver you say that they MUST be set to 1. I think =
it will be more correct here to say SHOULD since you explain afterwards =
that they may have other values.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] I think this is a MUST.&nbsp; The next sentence just points out =
that this normative text might change in a future revision (which is not =
currently planned).<o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.7.2 &#8220;the recipient SHOULD send&#8221;. Why not make it a MUST =
here.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] I ok with making this change, let&#8217;s see what others think =
&#8230;<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.7.2 &#8220;The version selected MUST be within the Min Vers to Max =
Vers inclusive range sent in the Version Request&nbsp;&nbsp; =
Message&#8221; I was expecting to see pref ver =
here.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] Perf is just an informational (hint) =
preference.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>10.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.8.3 &#8220; The SASL client authentication starts when the NEA =
Server&nbsp; enters the PT-TLS Negotiation phase and its policy =
indicates&nbsp; that an authentication of the NEA Client is necessary =
but was not performed during the TLS handshake protocol &#8220; my read =
of&nbsp; section 3.8 second paragraph is that it can be done even if was =
done in the TLS handshake so the last part of the sentence is not =
correct, if there is a policy you do it anyhow. This comment is also for =
the third paragraph.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] Thanks, this was supposed to be an example.&nbsp; Will fix =
these.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>11.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.9 I noticed that you propose to send the entire original message. =
Isn&#8217;t it enough to send only the message identifier. This is based =
on the last sentence of this section.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] Not &#8220;the entire original message&#8221; as its at most =
the first 1024 bytes of the offending message.&nbsp; This allows the =
recipient to either caches recently sent messages and/or message =
identifiers when determining what caused the error. &nbsp;We thought =
this flexibility was useful and had very little =
cost.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>12.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Most of =
the text in section 6.1 repeats RFC5226 but in your words. Are you =
trying to change some of RFC5226 text if not why write it in different =
words?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[PS:] We were hoping to emphasize the aspects of 5226 that are most =
important to this specification.&nbsp; We weren&#8217;t trying to change =
how the IANA policy was interpreted.&nbsp; Did you think we did =
so?&nbsp; Is there a portion of this text that is most troubling or was =
this just a question?<o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_0223_01CD4E15.57B56D80--


From d3e3e3@gmail.com  Tue Jun 19 04:55:33 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C387121F85EF for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 04:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.413
X-Spam-Level: 
X-Spam-Status: No, score=-103.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSjNu-TYzdkV for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 04:55:33 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2D51B21F85E6 for <gen-art@ietf.org>; Tue, 19 Jun 2012 04:55:33 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so5002059ggn.31 for <gen-art@ietf.org>; Tue, 19 Jun 2012 04:55:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=udXbyiANVdNsPiYYB6U7asi2+aklf9PM0/Qm4s6vmds=; b=VgwoYsd/U/t+qX7oiApF7Nq6SFMU8yx507bPq/XfuvYGTQh0XSuRMSJj50PRz+rSpW vF5Dcfz9zXkn5FeE4i4BblQteV1VWGpJRWZmoynNQyHZxf6583ZfMpF6EVfG952otUOd yWv7iqrj+b6XJ1inEIWDhjucN9qlbMFd8TNvpaQv4fVc32pqd8FYMoTv4YJiHyqqRuuX 57Ic8hXz/jy92zg5RvUpR2VsF8xfQPvXValF9LbtUi2mKWh9NBlNahhFW6Q8LsVJr8NM 2WXVXfSibNz3z4FLpMr3xhsG+ZKppW0pEzxhtwXC2pwTOcb8ookVuD4DPEAT+jEgfZmy sLBQ==
Received: by 10.50.194.200 with SMTP id hy8mr743690igc.58.1340106932343; Tue, 19 Jun 2012 04:55:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.16.227 with HTTP; Tue, 19 Jun 2012 04:55:12 -0700 (PDT)
In-Reply-To: <4FE029AB.6060108@ericsson.com>
References: <4FE029AB.6060108@ericsson.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 19 Jun 2012 07:55:12 -0400
Message-ID: <CAF4+nEEhS=unKAe1L7k+3=Kk4RLk6yV+SdUYEXSMso8mvnoPAA@mail.gmail.com>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: nordmark@acm.org, General Area Review Team <gen-art@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, draft-ietf-trill-rbridge-channel.authors@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-rbridge-channel-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 11:55:33 -0000

Hi Miguel,

On Tue, Jun 19, 2012 at 3:26 AM, Miguel A. Garcia
<Miguel.A.Garcia@ericsson.com> wrote:
> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft. For background on Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>
> Please resolve these comments along with any other comments you may recei=
ve.
>
> Document: draft-ietf-trill-rbridge-channel-06.txt
> Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
> Review Date: 2012-06-19
> IETF LC End Date: 2012-06-20
> IESG Telechat date: 2012-06-21
>
> Summary: This document is ready for publication as a standards track RFC
>
> Major issues: none
>
> Minor issues: none
>
> Nits/editorial comments:
>
> The document is well written and easy to read. Congratulations to the
> authors.

Thanks.

> I have some minor editorial comments.
>
> - All the figures that represent bits on the wire do not follow the
> convention of numbering the bits. I would suggest to add the bit number a=
s
> per the RFC style guide. This means adding these two lines to most figure=
s
> in the document:
>
>
> =A0 =A0 =A0 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 3
> =A0 =A0 =A0 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0=
 1

OK. I believe there are two figures where this should be added.

> - Also, related to figures. I would suggest to add a caption to each figu=
re,
> for example, under the figure in Section 2.1:
>
> =A0 =A0 =A0Figure 2: RBridge Channel Message inner frame
>
> This allows other documents to easily refer to the figure by number (e.g.=
,
> "Figure 2 in RFC xxxx").

OK.

> - Section 2.1.1: s/species/specifies

Thanks for spotting that.

> - Section 4. There are 5 bullet points. Something is wrong with the
> indentation of the third bullet point.

OK.

Thanks for the review,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

> /Miguel
> --
> Miguel A. Garcia
> +34-91-339-3608
> Ericsson Spain

From elwynd@folly.org.uk  Tue Jun 19 05:12:23 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5DFE21F855F for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 05:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.273
X-Spam-Level: 
X-Spam-Status: No, score=0.273 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_EQ_IP_ADDR=1.119, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mfE5lfA8GmD2 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 05:12:23 -0700 (PDT)
Received: from a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id CB83321F856F for <gen-art@ietf.org>; Tue, 19 Jun 2012 05:12:22 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[81.187.254.250]) by a.painless.aa.net.uk with esmtp (Exim 4.77) (envelope-from <elwynd@folly.org.uk>) id 1SgxIC-0003YD-44; Tue, 19 Jun 2012 13:12:20 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Organization: Folly Consulting
Date: Tue, 19 Jun 2012 13:12:17 +0100
Message-Id: <1340107937.31554.33318.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org
Subject: [Gen-art] Gen-art last call review of draft-ietf-pwe3-cbit-negotiation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 12:12:24 -0000

I am the assigned Gen-ART reviewer for this draft. For background on 
Gen-ART, please see the FAQ at 
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>. 

Please resolve these comments along with any other Last Call comments 
you may receive. 

Document: draft-ietf-pwe3-cbit-negotiation-04.txt
Reviewer: Elwyn Davies
Review Date: 19 June 2012
IETF LC End Date: 15 June 2012
IESG Telechat date: 21 June 2012

Summary: 
Not ready. The proposal for the NOT PREFERRED to PREFERRED transition
case does not appear to be compatible with the existing RFC 4447
standard in the way stated and there are a number of other minor issues.
The draft is also in need of an editing pass by an author whose mother
tongue is English as there are parts where the syntax is misleading
rather than just clumsy.

Apologies for the late submission of the review.

Major issues: 
s3: The discussion of the NOT PREFERRED to PREFERRED transition case
(buried at the end of s3 - causing me to ask 'what about this case?'
during reading of s2 and most of s3)  implies that some existing RFC
4447 procedure applies. Clearly, if the PW is not using the control word
then there is nothing to do.  On the other hand, inspection of s6.2 of
RFC4447 indicates that once the two PEs have agreed on c = 1, 'setup is
complete' and Label Mapping messages would therefore be
'unexpected' (see item '-i' in second set of bullets in s6.2 of RFC
4447). So, what procedure is to be used? And what implications does this
have for backwards compatibility?  Wouldn't it be generally simpler to
apply the PREFERRED to NOT PREFERRED mechanism to all case?

Minor issues: 
s3: Has there been any discussion on possible race conditions?  Changing
the configuration value during the message exchange strikes me as
dangerous - it is probably sufficient to note that changes should be
suppressed during the Label Mapping message exchange but I am not
totally sure about this.

s3, bullet '-i':  I completely misparsed this section on first reading
and I am still not absolutely sure what message sequence is being
specified.  Working back from later sections I *think* that the
intention is:
IF Mapping sent THEN { send Withdraw; send Release;}
Wait to receive Release
The implication at present is that a Mapping might not have been sent
and then only a Release is needed: is this a possibility? Please
clarify.
The picture in Appendix A suffers from the same problem.

s3, discussion of multi-segment PWs: The statement that S-PE's SHOULD
assume an initial passive role seems to have several problems:
- Does this mean that changing the configuration of an S-PE would not
provoke the new mechanisms?
- The passive role situation is only specified for some sorts of linked
FECs in RFC 6073 - what about other cases?
- What are the consequences for ignoring the SHOULD in this case? (I
have to say I am unsure that RFC 6073 deals with this problem either.)


Nits/editorial comments: 
General: In RFC 4447, the label message names use title case (e.g.,
Label Mapping).  For consistency this should be followed throughout this
document.
 
Abstract:  Should not contain references.  Best to give full title of
RFC and number in round brackets.
Abstract: s/problem of control/ the problem with control/ (if there is
just one)
Abstract: The second two sentences say the same thing in different ways 
OLD
   Based on the problem analysis, a
   message exchanging mechanism is introduced to solve this control word
   negotiation issue.  This document is to update [RFC4447] control word
   negotiation mechanism.
NEW
Based on the problem analysis, this document introduces a modified message exchange 
sequence updating the control word negotiation mechanism in RFC 4447.

This issue also applies to s1.

s1: Subtle distinction - this is a practical problem with the mechanism defined in RFC 4447 rather 
than the abstract problem of how to do control word negotiation:
 s/the problem of control word negotiation/problems identified in the control word negotiation/

s1: Expand acronym PW.

s2: Expand acronym PE.
s2, 2nd sentence: s/configurable/configured/
s2, 3rd and 4th sentences: I *think* this text is trying to say: 
  The intention of the control word negotiation is that the control word
will be used when both endpoints are configured with control word usage
PREFERRED.  However if one endpoint is initially configured with control
word usage NOT PREFERRED but later changes to PREFERRED, a PW between
the endpoints will not transition to usage of the control word as
explained below. 

s2, bullet #2: s/PE1 send label mapping with C bit=0 finally./ultimately
PE1 sends a Label Mapping message with the C bit set to 0./

s2, bullet #4: s/send label withdraw/send a Label Withdraw/

s2, bullet #5: s/the received/the previously received/, 
s/indicates C bit=0/carried the C bit set to 0/, 
s/send label mapping with C bit=0/send a label mapping message with the
C bit set to 0/

s3: It would be much clearer if s3 was divided into 3 sub-sections
(possibly reordered):
- PREFERRED to NOT PREFERRED transition
- NOT PREFERRED to PREFERRED transition
- Multi-segment case (which should refer to both previous cases)
The pointer to the diagram in Appendix A could usefully occur in the
introduction to s3.  If this was adopted s3.1 could either be a fourth
sub-section or a sub-sub-section of the PREFERRED to NOT PREFERRED
section.

s3, Various acronyms need expanding: FEC, T-PE, S-PE

s3, para 1: s/adding label request/adding a new label request/

s3 bullets '-i' to '-iii': s/Local PE/The local PE/, s/remote PR/the
remote peer PE/.  Also a more usual labeling of the bullets would be
appropriate (e.g., just i, ii and iii).

s3, para 2: s/When Local/When the local/,
s/the remote label mapping message with C bit=0, additional procedure
will be added as follow:/a label mapping message from the PW peer with
the C bits set to 0, the following additional procedure will be acrried
out:/
 
s3, bullet '-i': s/wait until receiving a label release/wait until it
has received a Label Release message/ (but general clarification and
rewording needed - see issues section above).

s3, bullet '-ii':
OLD:
      Local PE MUST send a label request message to remote PE, and
      wait until receiving a label mapping message containing the remote
      PE locally configured preference for use of control word.
NEW:
      The local PE MUST send a Label Mapping message to the peer PE with the
      C bit set to 1, and then wait until a Label Mapping message is received 
      containing the peer's current configured preference for usage of the 
      control word.

s3, para sfter item '-iii': s/successfully/has successfully/
The following implies that there is memory of previous action although
the label binding has been destroyed. Better would be:
OLD:
>    ...and removed the remote label binding, it MUST reset
>    its use of control word with the locally configured preference, and
>    send label mapping as a response of label request with locally
>    configured preference for use of control word.
NEW:
...and removed the remote label binding, subsequent Label Requests will
naturally be treated as new requests and processed as described in
Section 6 of RFC 4447.

s3, discussion of multi-segment PWs: s/case for T-PE is same./case for a
T-PE operates similarly./

s3, last para/Appendix A:  The diagram doesn't cover the PREFERRED to
NOT PREFERRED transition.

s3.1: The wording in this section is generally  rather 'loose'.  A more
formal style would be helpful.



From lizhong.jin@zte.com.cn  Tue Jun 19 06:49:19 2012
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E72821F8599 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 06:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.838
X-Spam-Level: 
X-Spam-Status: No, score=-101.838 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qjr7No7uuse5 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 06:49:17 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 8DA1121F8597 for <gen-art@ietf.org>; Tue, 19 Jun 2012 06:49:16 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 514961878467102; Tue, 19 Jun 2012 21:47:47 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 52926.4447640030; Tue, 19 Jun 2012 21:49:12 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q5JDn3u6055522; Tue, 19 Jun 2012 21:49:03 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <1340107937.31554.33318.camel@mightyatom.folly.org.uk>
To: Elwyn Davies <elwynd@folly.org.uk>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF319FFFC1.1C25C6E9-ON48257A22.0044F3CB-48257A22.004BE855@zte.com.cn>
From: Lizhong Jin<lizhong.jin@zte.com.cn>
Date: Tue, 19 Jun 2012 21:48:26 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-06-19 21:49:06, Serialize complete at 2012-06-19 21:49:06
Content-Type: multipart/alternative; boundary="=_alternative 004BE85448257A22_="
X-MAIL: mse01.zte.com.cn q5JDn3u6055522
X-Mailman-Approved-At: Tue, 19 Jun 2012 06:51:23 -0700
Cc: draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-pwe3-cbit-negotiation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 13:49:19 -0000

This is a multipart message in MIME format.
--=_alternative 004BE85448257A22_=
Content-Type: text/plain; charset="US-ASCII"

Hi Elwyn,
Thank you for the review. It seems you are reviewing v-03, not v-04, but 
some comments are for v-04. I am confused. See my reply inline below.

Regards
Lizhong
 

Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/19 20:12:17:

> I am the assigned Gen-ART reviewer for this draft. For background on 
> Gen-ART, please see the FAQ at 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>. 
> 
> Please resolve these comments along with any other Last Call comments 
> you may receive. 
> 
> Document: draft-ietf-pwe3-cbit-negotiation-04.txt
> Reviewer: Elwyn Davies
> Review Date: 19 June 2012
> IETF LC End Date: 15 June 2012
> IESG Telechat date: 21 June 2012
> 
> Summary: 
> Not ready. The proposal for the NOT PREFERRED to PREFERRED transition
> case does not appear to be compatible with the existing RFC 4447
> standard in the way stated and there are a number of other minor issues.
> The draft is also in need of an editing pass by an author whose mother
> tongue is English as there are parts where the syntax is misleading
> rather than just clumsy.
[Lizhong] We have two editors, and both Raymond and I are editing this 
document. Hope the below reply will make it clear.
> 
> Apologies for the late submission of the review.
> 
> Major issues: 
> s3: The discussion of the NOT PREFERRED to PREFERRED transition case
> (buried at the end of s3 - causing me to ask 'what about this case?'
> during reading of s2 and most of s3)  implies that some existing RFC
> 4447 procedure applies. Clearly, if the PW is not using the control word
> then there is nothing to do.  On the other hand, inspection of s6.2 of
> RFC4447 indicates that once the two PEs have agreed on c = 1, 'setup is
> complete' and Label Mapping messages would therefore be
> 'unexpected' (see item '-i' in second set of bullets in s6.2 of RFC
> 4447). So, what procedure is to be used? And what implications does this
> have for backwards compatibility?  Wouldn't it be generally simpler to
> apply the PREFERRED to NOT PREFERRED mechanism to all case?
[Lizhong] this draft is to solve the case to change a PW from c=0 to c=1, 
that means one PE should change its use of control word from NOT PREFERRED 
to PREFERRED. RFC4447 is already there and deployed, and the PE will not 
always send its locally configured preferrence according RFC4447, see PE1 
behavior in section 2 step 1&2. That's why we could not simply apply the 
mechanism at the end of section 3. Hope it is clear.

> 
> Minor issues: 
> s3: Has there been any discussion on possible race conditions?  Changing
> the configuration value during the message exchange strikes me as
> dangerous - it is probably sufficient to note that changes should be
> suppressed during the Label Mapping message exchange but I am not
> totally sure about this.
[Lizhong] The message would be processed in sequence in TCP-based LDP 
session. I do not see a problem here. But we do have a note in section 3 
for multi-segment PW for sequence processing.

> 
> s3, bullet '-i':  I completely misparsed this section on first reading
> and I am still not absolutely sure what message sequence is being
> specified.  Working back from later sections I *think* that the
> intention is:
> IF Mapping sent THEN { send Withdraw; send Release;}
> Wait to receive Release
> The implication at present is that a Mapping might not have been sent
> and then only a Release is needed: is this a possibility? Please
> clarify.
> The picture in Appendix A suffers from the same problem.
[Lizhong] Adrian raise the same comment, and I change it as below:
       -i.  PE MUST send a Label Release message to remote PE. If a PE
            has previously sent a Label Mapping message to a remote PE, 
            it MUST also send a Label Withdraw message to the remote PE, 
            and wait until it receives a Label Release message from the
            remote PE.

> 
> s3, discussion of multi-segment PWs: The statement that S-PE's SHOULD
> assume an initial passive role seems to have several problems:
> - Does this mean that changing the configuration of an S-PE would not
> provoke the new mechanisms?
> - The passive role situation is only specified for some sorts of linked
> FECs in RFC 6073 - what about other cases?
> - What are the consequences for ignoring the SHOULD in this case? (I
> have to say I am unsure that RFC 6073 deals with this problem either.)
[Lizhong] we follow RFC6073, and passive role is only applied for the PW 
FEC, other cases are out of scope. SHOULD means highly recommended. We do 
not meet any problem when implementing RFC6073. Do you suggest to change 
this to MUST? 

> 
> 
> Nits/editorial comments: 
> General: In RFC 4447, the label message names use title case (e.g.,
> Label Mapping).  For consistency this should be followed throughout this
> document.
[Lizhong] yes, and thank you and Adrian.
> 
> Abstract:  Should not contain references.  Best to give full title of
> RFC and number in round brackets.
[Lizhong] I removed brackets and do not intend to contain citations here. 
It seems the citations are generated automatically by IETF. Could the 
round brackets solve this? Or are you referring v-03?

> Abstract: s/problem of control/ the problem with control/ (if there is
> just one)
[Lizhong] are you reviewing v-03 of the draft? In v-04, the abstract has 
been revised in v-04.

> Abstract: The second two sentences say the same thing in different ways 
> OLD
>    Based on the problem analysis, a
>    message exchanging mechanism is introduced to solve this control word
>    negotiation issue.  This document is to update [RFC4447] control word
>    negotiation mechanism.
> NEW
> Based on the problem analysis, this document introduces a modified 
> message exchange 
> sequence updating the control word negotiation mechanism in RFC 4447.
> 
> This issue also applies to s1.
[Lizhong] are you reviewing v-03 of the draft? In v-04, the abstract has 
been revised in v-04.

> 
> s1: Subtle distinction - this is a practical problem with the 
> mechanism defined in RFC 4447 rather 
> than the abstract problem of how to do control word negotiation:
>  s/the problem of control word negotiation/problems identified in 
> the control word negotiation/
[Lizhong] has been revised in v-04.
> 
> s1: Expand acronym PW.
[Lizhong] has been revised in v-04.
> 
> s2: Expand acronym PE.
[Lizhong] accept

> s2, 2nd sentence: s/configurable/configured/
[Lizhong] configurable is right.

> s2, 3rd and 4th sentences: I *think* this text is trying to say: 
>   The intention of the control word negotiation is that the control word
> will be used when both endpoints are configured with control word usage
> PREFERRED.  However if one endpoint is initially configured with control
> word usage NOT PREFERRED but later changes to PREFERRED, a PW between
> the endpoints will not transition to usage of the control word as
> explained below. 
[Lizhong] no, the case is that operator deploys PW with control word used 
in the first phase. In the second phase, they want to upgrade their PW 
service to use control word. Two different deployment timeframes.

> 
> s2, bullet #2: s/PE1 send label mapping with C bit=0 finally./ultimately
> PE1 sends a Label Mapping message with the C bit set to 0./
[Lizhong] accept
> 
> s2, bullet #4: s/send label withdraw/send a Label Withdraw/
[Lizhong] accept
> 
> s2, bullet #5: s/the received/the previously received/, 
> s/indicates C bit=0/carried the C bit set to 0/, 
> s/send label mapping with C bit=0/send a label mapping message with the
> C bit set to 0/
[Lizhong] accept
> 
> s3: It would be much clearer if s3 was divided into 3 sub-sections
> (possibly reordered):
> - PREFERRED to NOT PREFERRED transition
> - NOT PREFERRED to PREFERRED transition
> - Multi-segment case (which should refer to both previous cases)
> The pointer to the diagram in Appendix A could usefully occur in the
> introduction to s3.  If this was adopted s3.1 could either be a fourth
> sub-section or a sub-sub-section of the PREFERRED to NOT PREFERRED
> section.
[Lizhong] PREFERRED to NOT PREFERRED does not introduce any new. 
Multi-segment case is fully inherited from single-segment case. It would 
be redundancy to have sub-sections here.

> 
> s3, Various acronyms need expanding: FEC, T-PE, S-PE
[Lizhong] accept
> 
> s3, para 1: s/adding label request/adding a new label request/
[Lizhong] much difference here?
> 
> s3 bullets '-i' to '-iii': s/Local PE/The local PE/, s/remote PR/the
> remote peer PE/.  Also a more usual labeling of the bullets would be
> appropriate (e.g., just i, ii and iii).
[Lizhong] accept, and I do not see "remote PR".
> 
> s3, para 2: s/When Local/When the local/,
> s/the remote label mapping message with C bit=0, additional procedure
> will be added as follow:/a label mapping message from the PW peer with
> the C bits set to 0, the following additional procedure will be acrried
> out:/
[Lizhong] accept
> 
> s3, bullet '-i': s/wait until receiving a label release/wait until it
> has received a Label Release message/ (but general clarification and
> rewording needed - see issues section above).
[Lizhong] do not see much difference here. Of couse the "label release" 
should be capitalized.
> 
> s3, bullet '-ii':
> OLD:
>       Local PE MUST send a label request message to remote PE, and
>       wait until receiving a label mapping message containing the remote
>       PE locally configured preference for use of control word.
> NEW:
>       The local PE MUST send a Label Mapping message to the peer PE with 
the
>       C bit set to 1, and then wait until a Label Mapping message 
isreceived 
>       containing the peer's current configured preference for usage of 
the 
>       control word.
[Lizhong] no, the procedure here is not right. The local PE MUST send a 
label request message, not label mapping.
> 
> s3, para sfter item '-iii': s/successfully/has successfully/
[Lizhong] accept

> The following implies that there is memory of previous action although
> the label binding has been destroyed. Better would be:
> OLD:
> >    ...and removed the remote label binding, it MUST reset
> >    its use of control word with the locally configured preference, and
> >    send label mapping as a response of label request with locally
> >    configured preference for use of control word.
> NEW:
> ...and removed the remote label binding, subsequent Label Requests will
> naturally be treated as new requests and processed as described in
> Section 6 of RFC 4447.
[Lizhong] we got similar comments from Adrian, and will update this.

> 
> s3, discussion of multi-segment PWs: s/case for T-PE is same./case for a
> T-PE operates similarly./
[Lizhong] accept
> 
> s3, last para/Appendix A:  The diagram doesn't cover the PREFERRED to
> NOT PREFERRED transition.
[Lizhong] no, there is a "no" branch under "NOT Preferred to Preferred" to 
cover "PREFERRED to NOT PREFERRED". Anyway, the diagram discription should 
be "NOT Preferred to Preferred" which is wrong in v-04.

> 
> s3.1: The wording in this section is generally  rather 'loose'.  A more
> formal style would be helpful.
[Lizhong] this is a usecase to give an example, so we make it "loose".
> 
> 
> 

--=_alternative 004BE85448257A22_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Elwyn,</font>
<br><font size=2 face="sans-serif">Thank you for the review. It seems you
are reviewing v-03, not v-04, but some comments are for v-04. I am confused.
See my reply inline below.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br><font size=2><tt>Elwyn Davies &lt;elwynd@folly.org.uk&gt; wrote 2012/06/19
20:12:17:<br>
<br>
&gt; I am the assigned Gen-ART reviewer for this draft. For background
on <br>
&gt; Gen-ART, please see the FAQ at <br>
&gt; &lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;. <br>
&gt; <br>
&gt; Please resolve these comments along with any other Last Call comments
<br>
&gt; you may receive. <br>
&gt; <br>
&gt; Document: draft-ietf-pwe3-cbit-negotiation-04.txt<br>
&gt; Reviewer: Elwyn Davies<br>
&gt; Review Date: 19 June 2012<br>
&gt; IETF LC End Date: 15 June 2012<br>
&gt; IESG Telechat date: 21 June 2012<br>
&gt; <br>
&gt; Summary: <br>
&gt; Not ready. The proposal for the NOT PREFERRED to PREFERRED transition<br>
&gt; case does not appear to be compatible with the existing RFC 4447<br>
&gt; standard in the way stated and there are a number of other minor issues.<br>
&gt; The draft is also in need of an editing pass by an author whose mother<br>
&gt; tongue is English as there are parts where the syntax is misleading<br>
&gt; rather than just clumsy.</tt></font>
<br><font size=2><tt>[Lizhong] We have two editors, and both Raymond and
I are editing this document. Hope the below reply will make it clear.<br>
&gt; <br>
&gt; Apologies for the late submission of the review.<br>
&gt; <br>
&gt; Major issues: <br>
&gt; s3: The discussion of the NOT PREFERRED to PREFERRED transition case<br>
&gt; (buried at the end of s3 - causing me to ask 'what about this case?'<br>
&gt; during reading of s2 and most of s3) &nbsp;implies that some existing
RFC<br>
&gt; 4447 procedure applies. Clearly, if the PW is not using the control
word<br>
&gt; then there is nothing to do. &nbsp;On the other hand, inspection of
s6.2 of<br>
&gt; RFC4447 indicates that once the two PEs have agreed on c = 1, 'setup
is<br>
&gt; complete' and Label Mapping messages would therefore be<br>
&gt; 'unexpected' (see item '-i' in second set of bullets in s6.2 of RFC<br>
&gt; 4447). So, what procedure is to be used? And what implications does
this<br>
&gt; have for backwards compatibility? &nbsp;Wouldn't it be generally simpler
to<br>
&gt; apply the PREFERRED to NOT PREFERRED mechanism to all case?</tt></font>
<br><font size=2><tt>[Lizhong] this draft is to solve the case to change
a PW from c=0 to c=1, that means one PE should change its use of control
word from NOT PREFERRED to PREFERRED. RFC4447 is already there and deployed,
and the PE will not always send its locally configured preferrence according
RFC4447, see PE1 behavior in section 2 step 1&amp;2. That's why we could
not simply apply the mechanism at the end of section 3. Hope it is clear.</tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; Minor issues: <br>
&gt; s3: Has there been any discussion on possible race conditions? &nbsp;Changing<br>
&gt; the configuration value during the message exchange strikes me as<br>
&gt; dangerous - it is probably sufficient to note that changes should
be<br>
&gt; suppressed during the Label Mapping message exchange but I am not<br>
&gt; totally sure about this.</tt></font>
<br><font size=2><tt>[Lizhong] The message would be processed in sequence
in TCP-based LDP session. I do not see a problem here. But we do have a
note in section 3 for multi-segment PW for sequence processing.</tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; s3, bullet '-i': &nbsp;I completely misparsed this section on first
reading<br>
&gt; and I am still not absolutely sure what message sequence is being<br>
&gt; specified. &nbsp;Working back from later sections I *think* that the<br>
&gt; intention is:<br>
&gt; IF Mapping sent THEN { send Withdraw; send Release;}<br>
&gt; Wait to receive Release<br>
&gt; The implication at present is that a Mapping might not have been sent<br>
&gt; and then only a Release is needed: is this a possibility? Please<br>
&gt; clarify.<br>
&gt; The picture in Appendix A suffers from the same problem.</tt></font>
<br><font size=2><tt>[Lizhong] Adrian raise the same comment, and I change
it as below:</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp;-i. &nbsp;PE MUST send
a Label Release message to remote PE. If a PE</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; has previously
sent a Label Mapping message to a remote PE, </tt></font>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; it MUST
also send a Label Withdraw message to the remote PE, </tt></font>
<br><font size=2><tt>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and wait
until it receives a Label Release message from the<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;remote PE.</tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; s3, discussion of multi-segment PWs: The statement that S-PE's SHOULD<br>
&gt; assume an initial passive role seems to have several problems:<br>
&gt; - Does this mean that changing the configuration of an S-PE would
not<br>
&gt; provoke the new mechanisms?<br>
&gt; - The passive role situation is only specified for some sorts of linked<br>
&gt; FECs in RFC 6073 - what about other cases?<br>
&gt; - What are the consequences for ignoring the SHOULD in this case?
(I<br>
&gt; have to say I am unsure that RFC 6073 deals with this problem either.)</tt></font>
<br><font size=2><tt>[Lizhong] we follow RFC6073, and passive role is only
applied for the PW FEC, other cases are out of scope. SHOULD means highly
recommended. We do not meet any problem when implementing RFC6073. Do you
suggest to change this to MUST? </tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; <br>
&gt; Nits/editorial comments: <br>
&gt; General: In RFC 4447, the label message names use title case (e.g.,<br>
&gt; Label Mapping). &nbsp;For consistency this should be followed throughout
this<br>
&gt; document.</tt></font>
<br><font size=2><tt>[Lizhong] yes, and thank you and Adrian.<br>
&gt; &nbsp;<br>
&gt; Abstract: &nbsp;Should not contain references. &nbsp;Best to give
full title of<br>
&gt; RFC and number in round brackets.</tt></font>
<br><font size=2><tt>[Lizhong] I removed brackets and do not intend to
contain citations here. It seems the citations are generated automatically
by IETF. Could the round brackets solve this? Or are you referring v-03?</tt></font>
<br><font size=2><tt><br>
&gt; Abstract: s/problem of control/ the problem with control/ (if there
is<br>
&gt; just one)</tt></font>
<br><font size=2><tt>[Lizhong] are you reviewing v-03 of the draft? In
v-04, the abstract has been revised in v-04.</tt></font>
<br><font size=2><tt><br>
&gt; Abstract: The second two sentences say the same thing in different
ways <br>
&gt; OLD<br>
&gt; &nbsp; &nbsp;Based on the problem analysis, a<br>
&gt; &nbsp; &nbsp;message exchanging mechanism is introduced to solve this
control word<br>
&gt; &nbsp; &nbsp;negotiation issue. &nbsp;This document is to update [RFC4447]
control word<br>
&gt; &nbsp; &nbsp;negotiation mechanism.<br>
&gt; NEW<br>
&gt; Based on the problem analysis, this document introduces a modified
<br>
&gt; message exchange <br>
&gt; sequence updating the control word negotiation mechanism in RFC 4447.<br>
&gt; <br>
&gt; This issue also applies to s1.</tt></font>
<br><font size=2><tt>[Lizhong] are you reviewing v-03 of the draft? In
v-04, the abstract has been revised in v-04.</tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; s1: Subtle distinction - this is a practical problem with the <br>
&gt; mechanism defined in RFC 4447 rather <br>
&gt; than the abstract problem of how to do control word negotiation:<br>
&gt; &nbsp;s/the problem of control word negotiation/problems identified
in <br>
&gt; the control word negotiation/</tt></font>
<br><font size=2><tt>[Lizhong] has been revised in v-04.<br>
&gt; <br>
&gt; s1: Expand acronym PW.</tt></font>
<br><font size=2><tt>[Lizhong] has been revised in v-04.<br>
&gt; <br>
&gt; s2: Expand acronym PE.</tt></font>
<br><font size=2><tt>[Lizhong] accept</tt></font>
<br><font size=2><tt><br>
&gt; s2, 2nd sentence: s/configurable/configured/</tt></font>
<br><font size=2><tt>[Lizhong] configurable is right.</tt></font>
<br><font size=2><tt><br>
&gt; s2, 3rd and 4th sentences: I *think* this text is trying to say: <br>
&gt; &nbsp; The intention of the control word negotiation is that the control
word<br>
&gt; will be used when both endpoints are configured with control word
usage<br>
&gt; PREFERRED. &nbsp;However if one endpoint is initially configured with
control<br>
&gt; word usage NOT PREFERRED but later changes to PREFERRED, a PW between<br>
&gt; the endpoints will not transition to usage of the control word as<br>
&gt; explained below. </tt></font>
<br><font size=2><tt>[Lizhong] no, the case is that operator deploys PW
with control word used in the first phase. In the second phase, they want
to upgrade their PW service to use control word. Two different deployment
timeframes.</tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; s2, bullet #2: s/PE1 send label mapping with C bit=0 finally./ultimately<br>
&gt; PE1 sends a Label Mapping message with the C bit set to 0./</tt></font>
<br><font size=2><tt>[Lizhong] accept<br>
&gt; <br>
&gt; s2, bullet #4: s/send label withdraw/send a Label Withdraw/</tt></font>
<br><font size=2><tt>[Lizhong] accept<br>
&gt; <br>
&gt; s2, bullet #5: s/the received/the previously received/, <br>
&gt; s/indicates C bit=0/carried the C bit set to 0/, <br>
&gt; s/send label mapping with C bit=0/send a label mapping message with
the<br>
&gt; C bit set to 0/</tt></font>
<br><font size=2><tt>[Lizhong] accept<br>
&gt; <br>
&gt; s3: It would be much clearer if s3 was divided into 3 sub-sections<br>
&gt; (possibly reordered):<br>
&gt; - PREFERRED to NOT PREFERRED transition<br>
&gt; - NOT PREFERRED to PREFERRED transition<br>
&gt; - Multi-segment case (which should refer to both previous cases)<br>
&gt; The pointer to the diagram in Appendix A could usefully occur in the<br>
&gt; introduction to s3. &nbsp;If this was adopted s3.1 could either be
a fourth<br>
&gt; sub-section or a sub-sub-section of the PREFERRED to NOT PREFERRED<br>
&gt; section.</tt></font>
<br><font size=2><tt>[Lizhong] PREFERRED to NOT PREFERRED does not introduce
any new. Multi-segment case is fully inherited from single-segment case.
It would be redundancy to have sub-sections here.</tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; s3, Various acronyms need expanding: FEC, T-PE, S-PE</tt></font>
<br><font size=2><tt>[Lizhong] accept<br>
&gt; <br>
&gt; s3, para 1: s/adding label request/adding a new label request/</tt></font>
<br><font size=2><tt>[Lizhong] much difference here?<br>
&gt; <br>
&gt; s3 bullets '-i' to '-iii': s/Local PE/The local PE/, s/remote PR/the<br>
&gt; remote peer PE/. &nbsp;Also a more usual labeling of the bullets would
be<br>
&gt; appropriate (e.g., just i, ii and iii).</tt></font>
<br><font size=2><tt>[Lizhong] accept, and I do not see &quot;remote PR&quot;.<br>
&gt; <br>
&gt; s3, para 2: s/When Local/When the local/,<br>
&gt; s/the remote label mapping message with C bit=0, additional procedure<br>
&gt; will be added as follow:/a label mapping message from the PW peer
with<br>
&gt; the C bits set to 0, the following additional procedure will be acrried<br>
&gt; out:/</tt></font>
<br><font size=2><tt>[Lizhong] accept<br>
&gt; &nbsp;<br>
&gt; s3, bullet '-i': s/wait until receiving a label release/wait until
it<br>
&gt; has received a Label Release message/ (but general clarification and<br>
&gt; rewording needed - see issues section above).</tt></font>
<br><font size=2><tt>[Lizhong] do not see much difference here. Of couse
the &quot;label release&quot; should be capitalized.<br>
&gt; <br>
&gt; s3, bullet '-ii':<br>
&gt; OLD:<br>
&gt; &nbsp; &nbsp; &nbsp; Local PE MUST send a label request message to
remote PE, and<br>
&gt; &nbsp; &nbsp; &nbsp; wait until receiving a label mapping message
containing the remote<br>
&gt; &nbsp; &nbsp; &nbsp; PE locally configured preference for use of control
word.<br>
&gt; NEW:<br>
&gt; &nbsp; &nbsp; &nbsp; The local PE MUST send a Label Mapping message
to the peer PE with the<br>
&gt; &nbsp; &nbsp; &nbsp; C bit set to 1, and then wait until a Label Mapping
message isreceived <br>
&gt; &nbsp; &nbsp; &nbsp; containing the peer's current configured preference
for usage of the <br>
&gt; &nbsp; &nbsp; &nbsp; control word.</tt></font>
<br><font size=2><tt>[Lizhong] no, the procedure here is not right. The
local PE MUST send a label request message, not label mapping.<br>
&gt; <br>
&gt; s3, para sfter item '-iii': s/successfully/has successfully/</tt></font>
<br><font size=2><tt>[Lizhong] accept</tt></font>
<br><font size=2><tt><br>
&gt; The following implies that there is memory of previous action although<br>
&gt; the label binding has been destroyed. Better would be:<br>
&gt; OLD:<br>
&gt; &gt; &nbsp; &nbsp;...and removed the remote label binding, it MUST
reset<br>
&gt; &gt; &nbsp; &nbsp;its use of control word with the locally configured
preference, and<br>
&gt; &gt; &nbsp; &nbsp;send label mapping as a response of label request
with locally<br>
&gt; &gt; &nbsp; &nbsp;configured preference for use of control word.<br>
&gt; NEW:<br>
&gt; ...and removed the remote label binding, subsequent Label Requests
will<br>
&gt; naturally be treated as new requests and processed as described in<br>
&gt; Section 6 of RFC 4447.</tt></font>
<br><font size=2><tt>[Lizhong] we got similar comments from Adrian, and
will update this.</tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; s3, discussion of multi-segment PWs: s/case for T-PE is same./case
for a<br>
&gt; T-PE operates similarly./</tt></font>
<br><font size=2><tt>[Lizhong] accept<br>
&gt; <br>
&gt; s3, last para/Appendix A: &nbsp;The diagram doesn't cover the PREFERRED
to<br>
&gt; NOT PREFERRED transition.</tt></font>
<br><font size=2><tt>[Lizhong] no, there is a &quot;no&quot; branch under
&quot;NOT Preferred to Preferred&quot; to cover &quot;PREFERRED to NOT
PREFERRED&quot;. Anyway, the diagram discription should be &quot;NOT Preferred
to Preferred&quot; which is wrong in v-04.</tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; s3.1: The wording in this section is generally &nbsp;rather 'loose'.
&nbsp;A more<br>
&gt; formal style would be helpful.</tt></font>
<br><font size=2><tt>[Lizhong] this is a usecase to give an example, so
we make it &quot;loose&quot;.<br>
&gt; <br>
&gt; <br>
&gt; <br>
</tt></font>
--=_alternative 004BE85448257A22_=--


From elwynd@folly.org.uk  Tue Jun 19 08:16:25 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 422B411E8086 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 08:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.273
X-Spam-Level: 
X-Spam-Status: No, score=0.273 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_EQ_IP_ADDR=1.119, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 671a7-ZLw52w for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 08:16:23 -0700 (PDT)
Received: from auth.b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA9D11E807F for <gen-art@ietf.org>; Tue, 19 Jun 2012 08:16:23 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[81.187.254.250]) by b.painless.aa.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1Sh0A6-0004iP-2S; Tue, 19 Jun 2012 16:16:10 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: Lizhong Jin <lizhong.jin@zte.com.cn>
In-Reply-To: <OF319FFFC1.1C25C6E9-ON48257A22.0044F3CB-48257A22.004BE855@zte.com.cn>
References: <OF319FFFC1.1C25C6E9-ON48257A22.0044F3CB-48257A22.004BE855@zte.com.cn>
Content-Type: text/plain
Organization: Folly Consulting
Date: Tue, 19 Jun 2012 16:16:08 +0100
Message-Id: <1340118968.31554.33576.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-pwe3-cbit-negotiation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 15:16:25 -0000

Hi, Lizhong.

On Tue, 2012-06-19 at 21:48 +0800, Lizhong Jin wrote:
> 
> Hi Elwyn, 
> Thank you for the review. It seems you are reviewing v-03, not v-04,
> but some comments are for v-04. I am confused.
Yes, I started reviewing v03 but had to stop because of other tasks and
came back to v04.  I though I had revisited all my old commnets and
updated them, but clearly not.
>  See my reply inline below. 
> 
> Regards 
> Lizhong 
>   
> 
> Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/19 20:12:17:
> 
> > I am the assigned Gen-ART reviewer for this draft. For background
> on 
> > Gen-ART, please see the FAQ at 
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>. 
> > 
> > Please resolve these comments along with any other Last Call
> comments 
> > you may receive. 
> > 
> > Document: draft-ietf-pwe3-cbit-negotiation-04.txt
> > Reviewer: Elwyn Davies
> > Review Date: 19 June 2012
> > IETF LC End Date: 15 June 2012
> > IESG Telechat date: 21 June 2012
> > 
> > Summary: 
> > Not ready. The proposal for the NOT PREFERRED to PREFERRED
> transition
> > case does not appear to be compatible with the existing RFC 4447
> > standard in the way stated and there are a number of other minor
> issues.
> > The draft is also in need of an editing pass by an author whose
> mother
> > tongue is English as there are parts where the syntax is misleading
> > rather than just clumsy. 
> [Lizhong] We have two editors, and both Raymond and I are editing this
> document. Hope the below reply will make it clear.

> > 
> > Apologies for the late submission of the review.
> > 
> > Major issues: 
> > s3: The discussion of the NOT PREFERRED to PREFERRED transition case
> > (buried at the end of s3 - causing me to ask 'what about this case?'
> > during reading of s2 and most of s3)  implies that some existing RFC
> > 4447 procedure applies. Clearly, if the PW is not using the control
> word
> > then there is nothing to do.  On the other hand, inspection of s6.2
> of
> > RFC4447 indicates that once the two PEs have agreed on c = 1, 'setup
> is
> > complete' and Label Mapping messages would therefore be
> > 'unexpected' (see item '-i' in second set of bullets in s6.2 of RFC
> > 4447). So, what procedure is to be used? And what implications does
> this
> > have for backwards compatibility?  Wouldn't it be generally simpler
> to
> > apply the PREFERRED to NOT PREFERRED mechanism to all case? 
> [Lizhong] this draft is to solve the case to change a PW from c=0 to
> c=1, that means one PE should change its use of control word from NOT
> PREFERRED to PREFERRED. RFC4447 is already there and deployed, and the
> PE will not always send its locally configured preferrence according
> RFC4447, see PE1 behavior in section 2 step 1&2. That's why we could
> not simply apply the mechanism at the end of section 3. Hope it is
> clear. 
There are two issues here:
- Clarity: RFC 4447 does not have any discussion of what might happen if
the configuration value changes.  The draft focusses on on transition
direction but does not mention the other except for one paragaph right
at the end of s3.  It is therefore reasonable that somebody looking at
this draft would wonder 'what about the other transition direction?'.
Whether or not anything needs to be done it would save people wondering
if you put in a sentence in the introduction to explain that the other
direction is not (or is) a problem.
- Technical: The paragraph in s3 implies that the PREFERRED to NOT
PREFERRED direction will result in some part of the RFC 4447 protocol
being (re-)invoked.  What part is not made very clear.  As far as I can
see sending more messages other than Label Release or Label Withdraw for
this PW is not part of the RFC 4447 protocol and hence will cause an
error.  Alternatively if it isn't reinvoked, the PW will continue to use
control words.  Please explain what is going on here.  The fact that RFC
4447 has been deployed doesn't explain what is going on.
> 
> > 
> > Minor issues: 
> > s3: Has there been any discussion on possible race conditions?
>  Changing
> > the configuration value during the message exchange strikes me as
> > dangerous - it is probably sufficient to note that changes should be
> > suppressed during the Label Mapping message exchange but I am not
> > totally sure about this. 
> [Lizhong] The message would be processed in sequence in TCP-based LDP
> session. I do not see a problem here. But we do have a note in section
> 3 for multi-segment PW for sequence processing. 
There are several network round trips in the message exchanges.  The
protocol and the configuration mechanism in a PE are potentially
separate threads.  There is scope, depending on the implementation, for
the user at the 'remote' PE to change the configuration during the
message exchange making for a potential race condition.
> 
> > 
> > s3, bullet '-i':  I completely misparsed this section on first
> reading
> > and I am still not absolutely sure what message sequence is being
> > specified.  Working back from later sections I *think* that the
> > intention is:
> > IF Mapping sent THEN { send Withdraw; send Release;}
> > Wait to receive Release
> > The implication at present is that a Mapping might not have been
> sent
> > and then only a Release is needed: is this a possibility? Please
> > clarify.
> > The picture in Appendix A suffers from the same problem. 
> [Lizhong] Adrian raise the same comment, and I change it as below: 
>        -i.  PE MUST send a Label Release message to remote PE. If a
> PE 
>             has previously sent a Label Mapping message to a remote
> PE, 
>             it MUST also send a Label Withdraw message to the remote
> PE, 
>             and wait until it receives a Label Release message from
> the
>            remote PE. 
What does it send first if both must be sent?  The text in the rest of
the document implies withdraw then release.  This new text sort of
implies release then withdraw but isn't really clear.
> 
> > 
> > s3, discussion of multi-segment PWs: The statement that S-PE's
> SHOULD
> > assume an initial passive role seems to have several problems:
> > - Does this mean that changing the configuration of an S-PE would
> not
> > provoke the new mechanisms?
> > - The passive role situation is only specified for some sorts of
> linked
> > FECs in RFC 6073 - what about other cases?
> > - What are the consequences for ignoring the SHOULD in this case? (I
> > have to say I am unsure that RFC 6073 deals with this problem
> either.) 
> [Lizhong] we follow RFC6073, and passive role is only applied for the
> PW FEC, other cases are out of scope. 
Why? This needs an explanation. Also this doesn't cover the point about
whether reconfig of an S-PE is allowed and how this squares with the
passive role.
> SHOULD means highly recommended. We do not meet any problem when
> implementing RFC6073. Do you suggest to change this to MUST? 
Whenever a specification includes a 'SHOULD' the question arises of what
alternatives there might be and what is the reason for preferring the
suggested solution.  In the original setup, it is fairly clear that life
is easier letting setup progress from  one end to the other (although
this is not spelt out - I would have argued for this had  I reviewed the
doc).  For the configuration change this is less obvious.  Regarding the
point about reconfig of the  S-PE, it is going to make life more
complicated if the S-PE has to tell the T-PE to be active so it can be
passive.  I would therefore argue that probably the notion of passivity
is irrelevant to the transition use case.  Whether it should be SHOULD
or MUST is therefore moot.

> > 
> > 
> > Nits/editorial comments: 
> > General: In RFC 4447, the label message names use title case (e.g.,
> > Label Mapping).  For consistency this should be followed throughout
> this
> > document. 
> [Lizhong] yes, and thank you and Adrian.
> >  
> > Abstract:  Should not contain references.  Best to give full title
> of
> > RFC and number in round brackets. 
> [Lizhong] I removed brackets and do not intend to contain citations
> here. It seems the citations are generated automatically by IETF.
> Could the round brackets solve this? Or are you referring v-03? 
(leftover from 03)
> 
> > Abstract: s/problem of control/ the problem with control/ (if there
> is
> > just one) 
> [Lizhong] are you reviewing v-03 of the draft? In v-04, the abstract
> has been revised in v-04.
(leftover from 03)
>  
> 
> > Abstract: The second two sentences say the same thing in different
> ways 
> > OLD
> >    Based on the problem analysis, a
> >    message exchanging mechanism is introduced to solve this control
> word
> >    negotiation issue.  This document is to update [RFC4447] control
> word
> >    negotiation mechanism.
> > NEW
> > Based on the problem analysis, this document introduces a modified 
> > message exchange 
> > sequence updating the control word negotiation mechanism in RFC
> 4447.
> > 
> > This issue also applies to s1. 
> [Lizhong] are you reviewing v-03 of the draft? In v-04, the abstract
> has been revised in v-04.
(leftover from 03)
>  
> 
> > 
> > s1: Subtle distinction - this is a practical problem with the 
> > mechanism defined in RFC 4447 rather 
> > than the abstract problem of how to do control word negotiation:
> >  s/the problem of control word negotiation/problems identified in 
> > the control word negotiation/ 
> [Lizhong] has been revised in v-04.
> > 
yes.
> > s1: Expand acronym PW. 
> [Lizhong] has been revised in v-04.
Not as far as I can see.
> > 
> > s2: Expand acronym PE. 
> [Lizhong] accept 
> 
> > s2, 2nd sentence: s/configurable/configured/ 
> [Lizhong] configurable is right. 
Leave that one to the RFc Editor.
> 
> > s2, 3rd and 4th sentences: I *think* this text is trying to say: 
> >   The intention of the control word negotiation is that the control
> word
> > will be used when both endpoints are configured with control word
> usage
> > PREFERRED.  However if one endpoint is initially configured with
> control
> > word usage NOT PREFERRED but later changes to PREFERRED, a PW
> between
> > the endpoints will not transition to usage of the control word as
> > explained below. 
> [Lizhong] no, the case is that operator deploys PW with control word
> used in the first phase. In the second phase, they want to upgrade
> their PW service to use control word. Two different deployment
> timeframes.
That is what my sentence says.
>  
> 
> > 
> > s2, bullet #2: s/PE1 send label mapping with C bit=0
> finally./ultimately
> > PE1 sends a Label Mapping message with the C bit set to 0./ 
> [Lizhong] accept
> > 
> > s2, bullet #4: s/send label withdraw/send a Label Withdraw/ 
> [Lizhong] accept
> > 
> > s2, bullet #5: s/the received/the previously received/, 
> > s/indicates C bit=0/carried the C bit set to 0/, 
> > s/send label mapping with C bit=0/send a label mapping message with
> the
> > C bit set to 0/ 
> [Lizhong] accept
> > 
> > s3: It would be much clearer if s3 was divided into 3 sub-sections
> > (possibly reordered):
> > - PREFERRED to NOT PREFERRED transition
> > - NOT PREFERRED to PREFERRED transition
> > - Multi-segment case (which should refer to both previous cases)
> > The pointer to the diagram in Appendix A could usefully occur in the
> > introduction to s3.  If this was adopted s3.1 could either be a
> fourth
> > sub-section or a sub-sub-section of the PREFERRED to NOT PREFERRED
> > section. 
> [Lizhong] PREFERRED to NOT PREFERRED does not introduce any new.
> Multi-segment case is fully inherited from single-segment case. It
> would be redundancy to have sub-sections here. 
I disagree strongly.  The multi-segment case affects the other RFC and
needs to be made to stand out so that implementors can see where the
changes occur.  The PREFERRED to NOT PREFERRED case also ought to be
separated whether or not I am right about this case. 
> 
> > 
> > s3, Various acronyms need expanding: FEC, T-PE, S-PE 
> [Lizhong] accept
> > 
> > s3, para 1: s/adding label request/adding a new label request/ 
> [Lizhong] much difference here?
Yes. How it reads in English.  There are many missing definite articles
and indefinite articles that make the text read very badly for a native
English speaker.  I understand that this is a very difficult aspect for
someone who has a first language that does not employ articles in the
way that English does.
> > 
> > s3 bullets '-i' to '-iii': s/Local PE/The local PE/, s/remote PR/the
> > remote peer PE/.  Also a more usual labeling of the bullets would be
> > appropriate (e.g., just i, ii and iii). 
> [Lizhong] accept, and I do not see "remote PR".
should have been 'remote PE'.
> > 
> > s3, para 2: s/When Local/When the local/,
> > s/the remote label mapping message with C bit=0, additional
> procedure
> > will be added as follow:/a label mapping message from the PW peer
> with
> > the C bits set to 0, the following additional procedure will be
> acrried
> > out:/ 
> [Lizhong] accept
> >  
> > s3, bullet '-i': s/wait until receiving a label release/wait until
> it
> > has received a Label Release message/ (but general clarification and
> > rewording needed - see issues section above). 
> [Lizhong] do not see much difference here. Of couse the "label
> release" should be capitalized.
Your form implies that that the action can occur as soon as the message
starts to be received (as in 'the radio is receiving a programme').
This is not the case - the action can occur only when the whole message
has been received.  
> > 
> > s3, bullet '-ii':
> > OLD:
> >       Local PE MUST send a label request message to remote PE, and
> >       wait until receiving a label mapping message containing the
> remote
> >       PE locally configured preference for use of control word.
> > NEW:
> >       The local PE MUST send a Label Mapping message to the peer PE
> with the
> >       C bit set to 1, and then wait until a Label Mapping message
> isreceived 
> >       containing the peer's current configured preference for usage
> of the 
> >       control word. 
> [Lizhong] no, the procedure here is not right. The local PE MUST send
> a label request message, not label mapping.
Try:
The local PE MUST send a Label Request message to the peer PE  and then
wait until a Label Mapping message is received containing the peer's
current configured preference for usage of the control word. 
> > 
> > s3, para sfter item '-iii': s/successfully/has successfully/ 
> [Lizhong] accept 
> 
> > The following implies that there is memory of previous action
> although
> > the label binding has been destroyed. Better would be:
> > OLD:
> > >    ...and removed the remote label binding, it MUST reset
> > >    its use of control word with the locally configured preference,
> and
> > >    send label mapping as a response of label request with locally
> > >    configured preference for use of control word.
> > NEW:
> > ...and removed the remote label binding, subsequent Label Requests
> will
> > naturally be treated as new requests and processed as described in
> > Section 6 of RFC 4447. 
> [Lizhong] we got similar comments from Adrian, and will update this. 
> 
> > 
> > s3, discussion of multi-segment PWs: s/case for T-PE is same./case
> for a
> > T-PE operates similarly./ 
> [Lizhong] accept
> > 
> > s3, last para/Appendix A:  The diagram doesn't cover the PREFERRED
> to
> > NOT PREFERRED transition. 
> [Lizhong] no, there is a "no" branch under "NOT Preferred to
> Preferred" to cover "PREFERRED to NOT PREFERRED". Anyway, the diagram
> discription should be "NOT Preferred to Preferred" which is wrong in
> v-04. 
> 
> > 
> > s3.1: The wording in this section is generally  rather 'loose'.  A
> more
> > formal style would be helpful. 
> [Lizhong] this is a usecase to give an example, so we make it "loose".
> > 
> > 
> > 


From Paul_Sangster@symantec.com  Tue Jun 19 08:24:21 2012
Return-Path: <Paul_Sangster@symantec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD3211E808F; Tue, 19 Jun 2012 08:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AoiOk4cvj95A; Tue, 19 Jun 2012 08:24:15 -0700 (PDT)
Received: from tus1smtoutpex02.symantec.com (tus1smtoutpex02.symantec.com [216.10.195.242]) by ietfa.amsl.com (Postfix) with ESMTP id D267021F8566; Tue, 19 Jun 2012 08:24:04 -0700 (PDT)
X-AuditID: d80ac3f2-b7f806d0000068dc-a0-4fe099945643
Received: from tus1opsmtapin02.ges.symantec.com (tus1opsmtapin02.ges.symantec.com [192.168.214.44]) by tus1smtoutpex02.symantec.com (Symantec Brightmail Gateway out) with SMTP id 55.26.26844.49990EF4; Tue, 19 Jun 2012 15:24:04 +0000 (GMT)
Received: from [155.64.220.138] (helo=TUS1XCHHUBPIN02.SYMC.SYMANTEC.COM) by tus1opsmtapin02.ges.symantec.com with esmtp (Exim 4.76) (envelope-from <Paul_Sangster@symantec.com>) id 1Sh0Hk-0001GD-0W; Tue, 19 Jun 2012 15:24:04 +0000
Received: from TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM ([155.64.220.150]) by TUS1XCHHUBPIN02.SYMC.SYMANTEC.COM ([172.24.185.246]) with mapi; Tue, 19 Jun 2012 08:24:04 -0700
From: Paul Sangster <Paul_Sangster@symantec.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-nea-pt-tls.all@tools.ietf.org" <draft-ietf-nea-pt-tls.all@tools.ietf.org>
Date: Tue, 19 Jun 2012 08:25:43 -0700
Thread-Topic: GenART LC review of draft-ietf-nea-pt-tls-05
Thread-Index: Ac1Cl9xExNAkih6WSYeHA9SkXDOg7gG388dgASA4xdAADb42MA==
Message-ID: <6E79D623502C70419A9EAB18E4D274252B8B2C397F@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
References: <4fcd272e.2968b40a.55d4.ffff9de3@mx.google.com> <6E79D623502C70419A9EAB18E4D274252B8B06102F@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM> <4fe0440b.6959b40a.7a49.6095@mx.google.com>
In-Reply-To: <4fe0440b.6959b40a.7a49.6095@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_6E79D623502C70419A9EAB18E4D274252B8B2C397FTUS1XCHEVSPIN_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNIsWRmVeSWpSXmKPExsVyYMU1Hd0pMx/4G2y+zm4x9+IEdourrz6z WDzbOJ/F4vPbCou/7cwOrB47Z91l91iy5CeTx5fLn9kCmKO4bFJSczLLUov07RK4Mp5Mvsxe sH4uU8WE6YsZGxi//mbsYuTkkBAwkbh8dx4bhC0mceHeeiCbi0NI4AOjxJ3dh9khnNeMEl2r mpkhnFWMEr/fLgRrZxMwkNh55BRYlYhAI6PE1yVzmEESzAJJEsdnbGABsVkEVCXW35zCDmIL C1hKTPk+CSwuImAlsfTDRCYI20niyrnjYDavQJTE3Om7oFbvYpRY8/QpWDOngIXExg23WEFs RqBjv59awwSxTFzi1pP5TBBPCEgs2XOeGcIWlXj5+B9UvajEnfb1jBD1+RIP1pxih1gmKHFy 5hOWCYxis5CMmoWkbBaSMoi4jsSC3Z/YIGxtiWULXzPD2GcOPGZCFl/AyL6KUaaktNiwOLck v7SkILXCwEivuDI3ERjByXrJ+bmbGIFRfIPr8KcdjDeWKh5iFOBgVOLh3TDpgb8Qa2IZUOUh RgkOZiUR3roZQCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8H3Zv9RcSSE8sSc1OTS1ILYLJMnFw SjUwTvO/mqp7O39hgQfrf+aqiQt1Qu0NZRetP2zSfOsJU3XDpjcHZ9kei3OJ7T/B/Lp2XdrV dSdXOP5/xXf55sPca523a9SKnKdUbWleKGJZrLBRZz1r1UTpx/P3CrWkdVwWF9vJFvDY4lyB uuxL4faQHFHH8Fe7FQzMg8L59j9+kME0w3jJW1EjJZbijERDLeai4kQAludT5d4CAAA=
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "nea@ietf.org" <nea@ietf.org>, 'IETF' <ietf@ietf.org>
Subject: Re: [Gen-art] GenART LC review of draft-ietf-nea-pt-tls-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 15:24:21 -0000

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

NEA has 2 existing RFCs (PA and PB protocols) that use the PEN of 0 in exac=
tly the same way as PT-TLS.  One option might be to change "Reserved" to "R=
eserved for IETF Use".
From: Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: Tuesday, June 19, 2012 2:16 AM
To: Paul Sangster; draft-ietf-nea-pt-tls.all@tools.ietf.org
Cc: 'IETF'; gen-art@ietf.org; nea@ietf.org
Subject: RE: GenART LC review of draft-ietf-nea-pt-tls-05

Hi,
I am OK with your responses. The only thing I am not sure is about using PE=
N 0 defined in the registry.

Decimal
| Organization
| | Contact
| | | Email
| | | |
0
  Reserved
    Internet Assigned Numbers Authority
      iana&iana.org

I was wondering how this enterprise number should be specified since it app=
ears as "Reserved" in the registry. I have no specific suggestion
Roni


From: Paul Sangster [mailto:Paul_Sangster@symantec.com]
Sent: Wednesday, June 13, 2012 7:56 PM
To: Roni Even; draft-ietf-nea-pt-tls.all@tools.ietf.org
Cc: 'IETF'; gen-art@ietf.org; nea@ietf.org
Subject: RE: GenART LC review of draft-ietf-nea-pt-tls-05

Thanks for the detailed review, comments are in-lined...

From: Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: Monday, June 04, 2012 2:20 PM
To: draft-ietf-nea-pt-tls.all@tools.ietf.org<mailto:draft-ietf-nea-pt-tls.a=
ll@tools.ietf.org>
Cc: 'IETF'; gen-art@ietf.org<mailto:gen-art@ietf.org>
Subject: GenART LC review of draft-ietf-nea-pt-tls-05

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.



Document: draft-ietf-nea-pt-tls-05

Reviewer: Roni Even

Review Date:2012-6-4

IETF LC End Date: 2012-6-13

IESG Telechat date:



Summary: This draft is almost ready for publication as a standard track RFC=
.



Major issues:



Minor issues:

1.       In section 3.2 "Therefore, this specification requests the IANA re=
serve a TCP port number for use with the PT-TLS protocol upon publication o=
f this specification as an Internet standard RFC." I think it will  be bett=
er to have here the assigned port number and instruct the RFC editor to put=
 the correct value.



[PS:] Ok, we can reword this in hopes of getting a particular value (race c=
ondition with other upcoming RFCs).



2.       In section 3.4.2.2 last paragraph you summarize the text from sect=
ion 3.8 while in the paragraph above you provide the reference. Why do you =
need the last paragraph if 3.8 is referenced.



[PS:] The goal of this section is to introduce and summarize the different =
phases of PT-TLS.  We felt a brief discussion of the general message flow w=
as helpful to the reader to understand what occurs during this phase (simil=
ar to what we did in the other sub-sections).  Your correct that this infor=
mation is covered later in more detail.



3.       In various places you refer to SMI 0 as IETF SMI number while acco=
rding to the table it is IANA SMI number.



[PS:] I presume this is about the PEN 0 being for the IETF.  Correct, it's =
the IETF's name space that administered by the IANA.  What text would you l=
ike to see to make this more clear?  Can we do it in one place, for example=
 stating that the IETF name space is administered by the IANA?



4.       I assume that all implementations MUST support message type vendor=
 ID 0. Is this mentioned?



[PS:] The purpose of this section was just to summarize and enumerate the m=
essage types for vendor id 0.   I don't think it's a general rule that any =
message type defined in the IETF (IANA :)) name space must (or should be) s=
upported by all implementations.  It will vary depending on the purpose of =
the message so that normative language is included in the descriptions of t=
he message.



5.       In section 3.5 and 6.1 you propose a policy of "Expert Review with=
 Specification Required ". I think that according to RFC5226 expert review =
is implied if you select a specification required policy.



[PS:] I agree, it says "Specification Required also implies use of a Design=
ated Expert".  The policy is just "Specification Required" so we could remo=
ve the "Expert Review with" and make it clear it's the Specification Requir=
ed IANA policy.



6.       In section 3.6 on 9+ "Recipients of messages   of type 9 or higher=
 that do not support the PT-TLS Message Type Vendor ID and PT-TLS Message T=
ype of a received PT-TLS message MUST respond with a Type Not Supported PT-=
TLS error code in a PT-TLS Error message." I think this is true only for Me=
ssage Type Vendor ID 0.



[PS:] Thanks will reword this section to make it more clear.



7.       In 3.7.1 for Max vers and prefs ver you say that they MUST be set =
to 1. I think it will be more correct here to say SHOULD since you explain =
afterwards that they may have other values.



[PS:] I think this is a MUST.  The next sentence just points out that this =
normative text might change in a future revision (which is not currently pl=
anned).



8.       In section 3.7.2 "the recipient SHOULD send". Why not make it a MU=
ST here.



[PS:] I ok with making this change, let's see what others think ...



9.       In section 3.7.2 "The version selected MUST be within the Min Vers=
 to Max Vers inclusive range sent in the Version Request   Message" I was e=
xpecting to see pref ver here.



[PS:] Perf is just an informational (hint) preference.



10.   In section 3.8.3 " The SASL client authentication starts when the NEA=
 Server  enters the PT-TLS Negotiation phase and its policy indicates  that=
 an authentication of the NEA Client is necessary but was not performed dur=
ing the TLS handshake protocol " my read of  section 3.8 second paragraph i=
s that it can be done even if was done in the TLS handshake so the last par=
t of the sentence is not correct, if there is a policy you do it anyhow. Th=
is comment is also for the third paragraph.



[PS:] Thanks, this was supposed to be an example.  Will fix these.



11.   In section 3.9 I noticed that you propose to send the entire original=
 message. Isn't it enough to send only the message identifier. This is base=
d on the last sentence of this section.



[PS:] Not "the entire original message" as its at most the first 1024 bytes=
 of the offending message.  This allows the recipient to either caches rece=
ntly sent messages and/or message identifiers when determining what caused =
the error.  We thought this flexibility was useful and had very little cost=
.



12.   Most of the text in section 6.1 repeats RFC5226 but in your words. Ar=
e you trying to change some of RFC5226 text if not why write it in differen=
t words?



[PS:] We were hoping to emphasize the aspects of 5226 that are most importa=
nt to this specification.  We weren't trying to change how the IANA policy =
was interpreted.  Did you think we did so?  Is there a portion of this text=
 that is most troubling or was this just a question?









Nits/editorial comments:


--_000_6E79D623502C70419A9EAB18E4D274252B8B2C397FTUS1XCHEVSPIN_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@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;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
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";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2023900102;
	mso-list-type:hybrid;
	mso-list-template-ids:-625979886 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>NEA has 2 existing RFCs (PA and PB protocols) that use the PE=
N of 0 in exactly the same way as PT-TLS.&nbsp; One option might be to chan=
ge &#8220;Reserved&#8221; to &#8220;Reserved for IETF Use&#8221;.<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=3DMsoNormal style=3D'margin-botto=
m:0in;margin-bottom:.0001pt;line-height:normal'><b><span style=3D'font-size=
:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even [mailto:ron.e=
ven.tlv@gmail.com] <br><b>Sent:</b> Tuesday, June 19, 2012 2:16 AM<br><b>To=
:</b> Paul Sangster; draft-ietf-nea-pt-tls.all@tools.ietf.org<br><b>Cc:</b>=
 'IETF'; gen-art@ietf.org; nea@ietf.org<br><b>Subject:</b> RE: GenART LC re=
view of draft-ietf-nea-pt-tls-05<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'color=
:#1F497D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'colo=
r:#1F497D'>I am OK with your responses. The only thing I am not sure is abo=
ut using PEN 0 defined in the registry.<o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:n=
ormal'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>Decimal<o=
:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:0in;margin-=
bottom:.0001pt;line-height:normal'><span style=3D'font-size:10.0pt;font-fam=
ily:"Courier New"'>| Organization<o:p></o:p></span></p><p class=3DMsoNormal=
 style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span=
 style=3D'font-size:10.0pt;font-family:"Courier New"'>| | Contact<o:p></o:p=
></span></p><p class=3DMsoNormal style=3D'margin-bottom:0in;margin-bottom:.=
0001pt;line-height:normal'><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New"'>| | | Email<o:p></o:p></span></p><p class=3DMsoNormal style=3D'm=
argin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New"'>| | | |<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-hei=
ght:normal'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>0<o:=
p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:0in;margin-b=
ottom:.0001pt;line-height:normal'><span style=3D'font-size:10.0pt;font-fami=
ly:"Courier New"'>&nbsp; Reserved<o:p></o:p></span></p><p class=3DMsoNormal=
 style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span=
 style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;&nbsp; In=
ternet Assigned Numbers Authority<o:p></o:p></span></p><p class=3DMsoNormal=
 style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span=
 style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; iana&amp;iana.org<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><=
span style=3D'color:#1F497D'>I was wondering how this enterprise number sho=
uld be specified since it appears as &quot;Reserved&quot; in the registry. =
I have no specific suggestion<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorm=
al><span style=3D'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><d=
iv style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0i=
n 0in'><p class=3DMsoNormal style=3D'margin-bottom:0in;margin-bottom:.0001p=
t;line-height:normal'><b><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-famil=
y:"Tahoma","sans-serif"'> Paul Sangster [mailto:Paul_Sangster@symantec.com]=
 <br><b>Sent:</b> Wednesday, June 13, 2012 7:56 PM<br><b>To:</b> Roni Even;=
 draft-ietf-nea-pt-tls.all@tools.ietf.org<br><b>Cc:</b> 'IETF'; gen-art@iet=
f.org; nea@ietf.org<br><b>Subject:</b> RE: GenART LC review of draft-ietf-n=
ea-pt-tls-05<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>Thanks for =
the detailed review, comments are in-lined&#8230;<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'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;paddin=
g:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'margin-bottom:0in;margin=
-bottom:.0001pt;line-height:normal'><b><span style=3D'font-size:10.0pt;font=
-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.=
0pt;font-family:"Tahoma","sans-serif"'> Roni Even [<a href=3D"mailto:ron.ev=
en.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>] <br><b>Sent:</b> Monda=
y, June 04, 2012 2:20 PM<br><b>To:</b> <a href=3D"mailto:draft-ietf-nea-pt-=
tls.all@tools.ietf.org">draft-ietf-nea-pt-tls.all@tools.ietf.org</a><br><b>=
Cc:</b> 'IETF'; <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br=
><b>Subject:</b> GenART LC review of draft-ietf-nea-pt-tls-05<o:p></o:p></s=
pan></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMs=
oNormal>I am the assigned Gen-ART reviewer for this draft. For background o=
n Gen-ART, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p><p class=3DMsoNormal>Please resolve these comments along=
 with any other Last Call comments you may receive.<o:p></o:p></p><p class=
=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: draft-ietf-=
nea-pt-tls-05<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: Roni Even<o:p=
></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif"'>Review Date:2012&#8211;6&#8211;4<o:p></o=
:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif"'>IETF LC End Date: 2012&#8211;6&#8211;13<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif"'>IESG Telechat date:<o:p></o:p></span></p>=
<p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: This=
 draft is almost ready for publication as a standard track RFC.<o:p></o:p><=
/span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainT=
ext><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Maj=
or issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif"'>Minor issues:<o:p></o:p></span></p><p class=3DMsoPlainTe=
xt style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><!=
[if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif"'><span style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Ti=
mes New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><=
![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"=
'>In section 3.2 &#8220;Therefore, this specification requests the IANA res=
erve a TCP port number for use with the PT-TLS protocol upon publication of=
 this specification as an Internet standard RFC.&#8221; I think it will&nbs=
p; be better to have here the assigned port number and instruct the RFC edi=
tor to put the correct value.<o:p></o:p></span></p><p class=3DMsoPlainText>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS=
:] Ok, we can reword this in hopes of getting a particular value (race cond=
ition with other upcoming RFCs).<o:p></o:p></span></i></b></p><p class=3DMs=
oPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=
=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !sup=
portLists]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f"'><span style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In sec=
tion 3.4.2.2 last paragraph you summarize the text from section 3.8 while i=
n the paragraph above you provide the reference. Why do you need the last p=
aragraph if 3.8 is referenced.<o:p></o:p></span></p><p class=3DMsoPlainText=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[P=
S:] The goal of this section is to introduce and summarize the different ph=
ases of PT-TLS.&nbsp; We felt a brief discussion of the general message flo=
w was helpful to the reader to understand what occurs during this phase (si=
milar to what we did in the other sub-sections).&nbsp; Your correct that th=
is information is covered later in more detail.<o:p></o:p></span></i></b></=
p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
PlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 l=
fo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif"'><span style=3D'mso-list:Ignore'>3.<span style=3D'font:7.=
0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><=
/span><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif"'>In various places you refer to SMI 0 as IETF SMI number while acco=
rding to the table it is IANA SMI number.<o:p></o:p></span></p><p class=3DM=
soPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-ser=
if";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><=
i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'>[PS:] I presume this is about the PEN 0 being for the IETF.&nbsp; =
Correct, it&#8217;s the IETF&#8217;s name space that administered by the IA=
NA. &nbsp;What text would you like to see to make this more clear?&nbsp; Ca=
n we do it in one place, for example stating that the IETF name space is ad=
ministered by the IANA?<o:p></o:p></span></i></b></p><p class=3DMsoPlainTex=
t><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=3D'margi=
n-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists=
]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span=
 style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New Roman"'>&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I assume that a=
ll implementations MUST support message type vendor ID 0. Is this mentioned=
?<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.=
0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></sp=
an></p><p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>[PS:] The purpose of this secti=
on was just to summarize and enumerate the message types for vendor id 0.&n=
bsp; &nbsp;I don&#8217;t think it&#8217;s a general rule that any message t=
ype defined in the IETF (IANA </span></i></b><b><i><span style=3D'font-size=
:11.0pt;font-family:Wingdings;color:#1F497D'>J</span></i></b><b><i><span st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>)=
 name space must (or should be) supported by all implementations.&nbsp; It =
will vary depending on the purpose of the message so that normative languag=
e is included in the descriptions of the message.<o:p></o:p></span></i></b>=
</p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DM=
soPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1=
 lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif"'><span style=3D'mso-list:Ignore'>5.<span style=3D'font:=
7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span=
></span><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif"'>In section 3.5 and 6.1 you propose a policy of &#8220;Expert Rev=
iew with Specification Required &#8220;. I think that according to RFC5226 =
expert review is implied if you select a specification required policy.<o:p=
></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></=
p><p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-family=
:"Calibri","sans-serif";color:#1F497D'>[PS:] I agree, it says &#8220;Specif=
ication Required also implies use of a Designated Expert&#8221;.&nbsp; The =
policy is just &#8220;Specification Required&#8221; so we could remove the =
&#8220;Expert Review with&#8221; and make it clear it&#8217;s the Specifica=
tion Required IANA policy. <o:p></o:p></span></i></b></p><p class=3DMsoPlai=
nText style=3D'margin-left:10.5pt'><b><i><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></i=
></b></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25=
in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>6=
.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; </span></span></span><![endif]><span style=3D'font-size:11.0pt;font=
-family:"Calibri","sans-serif"'>In section 3.6 on 9+ &#8220;Recipients of m=
essages&nbsp;&nbsp; of type 9 or higher that do not support the PT-TLS Mess=
age Type Vendor ID and PT-TLS Message Type of a received PT-TLS message MUS=
T respond with a Type Not Supported PT-TLS error code in a PT-TLS Error mes=
sage.&#8221; I think this is true only for Message Type Vendor ID 0.<o:p></=
o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font=
-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><=
p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-family:"C=
alibri","sans-serif";color:#1F497D'>[PS:] Thanks will reword this section t=
o make it more clear.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=3D'margin-=
left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span s=
tyle=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times New Roman"'>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In 3.7.1 for Max =
vers and prefs ver you say that they MUST be set to 1. I think it will be m=
ore correct here to say SHOULD since you explain afterwards that they may h=
ave other values.<o:p></o:p></span></p><p class=3DMsoPlainText><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'font-s=
ize:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] I think =
this is a MUST.&nbsp; The next sentence just points out that this normative=
 text might change in a future revision (which is not currently planned).<o=
:p></o:p></span></i></b></p><p class=3DMsoPlainText><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-=
.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore=
'>8.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; </span></span></span><![endif]><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif"'>In section 3.7.2 &#8220;the recipient SH=
OULD send&#8221;. Why not make it a MUST here.<o:p></o:p></span></p><p clas=
s=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText=
><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#1F497D'>[PS:] I ok with making this change, let&#8217;s see what othe=
rs think &#8230;<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=3D'margin-left:=
.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style=
=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 3.7.2 &#82=
20;The version selected MUST be within the Min Vers to Max Vers inclusive r=
ange sent in the Version Request&nbsp;&nbsp; Message&#8221; I was expecting=
 to see pref ver here.<o:p></o:p></span></p><p class=3DMsoPlainText><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[PS:] Perf=
 is just an informational (hint) preference.<o:p></o:p></span></i></b></p><=
p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPla=
inText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2=
'><![if !supportLists]><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif"'><span style=3D'mso-list:Ignore'>10.<span style=3D'font:7.0p=
t "Times New Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 3.8.3 =
&#8220; The SASL client authentication starts when the NEA Server&nbsp; ent=
ers the PT-TLS Negotiation phase and its policy indicates&nbsp; that an aut=
hentication of the NEA Client is necessary but was not performed during the=
 TLS handshake protocol &#8220; my read of&nbsp; section 3.8 second paragra=
ph is that it can be done even if was done in the TLS handshake so the last=
 part of the sentence is not correct, if there is a policy you do it anyhow=
. This comment is also for the third paragraph.<o:p></o:p></span></p><p cla=
ss=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainTex=
t><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'>[PS:] Thanks, this was supposed to be an example.&nbsp; Will=
 fix these.<o:p></o:p></span></i></b></p><p class=3DMsoPlainText><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:=
p>&nbsp;</o:p></span></p><p class=3DMsoPlainText style=3D'margin-left:.5in;=
text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style=3D'ms=
o-list:Ignore'>11.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;=
 </span></span></span><![endif]><span style=3D'font-size:11.0pt;font-family=
:"Calibri","sans-serif"'>In section 3.9 I noticed that you propose to send =
the entire original message. Isn&#8217;t it enough to send only the message=
 identifier. This is based on the last sentence of this section.<o:p></o:p>=
</span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p cl=
ass=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'>[PS:] Not &#8220;the entire original messag=
e&#8221; as its at most the first 1024 bytes of the offending message.&nbsp=
; This allows the recipient to either caches recently sent messages and/or =
message identifiers when determining what caused the error. &nbsp;We though=
t this flexibility was useful and had very little cost.<o:p></o:p></span></=
i></b></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p cla=
ss=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>12.<span style=
=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span></span><![endi=
f]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Most=
 of the text in section 6.1 repeats RFC5226 but in your words. Are you tryi=
ng to change some of RFC5226 text if not why write it in different words?<o=
:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoPlainText><b><i><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>[PS:] We were hoping to emphasize =
the aspects of 5226 that are most important to this specification.&nbsp; We=
 weren&#8217;t trying to change how the IANA policy was interpreted.&nbsp; =
Did you think we did so?&nbsp; Is there a portion of this text that is most=
 troubling or was this just a question?<o:p></o:p></span></i></b></p><p cla=
ss=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainTex=
t><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>=
&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.=
0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p clas=
s=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editorial com=
ments:<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
></div></div></div></body></html>=

--_000_6E79D623502C70419A9EAB18E4D274252B8B2C397FTUS1XCHEVSPIN_--

From rbarnes@bbn.com  Tue Jun 19 08:31:46 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F04821F8522; Tue, 19 Jun 2012 08:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 309x36VYmpwj; Tue, 19 Jun 2012 08:31:45 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 1558B21F8508; Tue, 19 Jun 2012 08:31:44 -0700 (PDT)
Received: from ros-dhcp192-1-51-6.bbn.com ([192.1.51.6]:54956) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Sh0OW-0004gM-WF; Tue, 19 Jun 2012 11:31:05 -0400
From: Richard L. Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Jun 2012 11:31:42 -0400
Message-Id: <D48790C9-D5B0-407E-A917-DC6D5BC42D9D@bbn.com>
To: ietf@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org, gen-art@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: [Gen-art] Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 15:31:46 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-nfsv4-federated-fs-admin-11
Reviewer: Richard Barnes
Review Date: Jun-19-2012
IETF LC End Date: Not known
IESG Telechat date: Jun-28-2012

Summary: Almost ready, couple of issues

MAJOR:=20

4. / 7.
This protocol allows for the provisioning of security information as =
part of the FedFsNsdbParams, in the form of a certificate to be used in =
verifying a TLS server certificate.  There are two notable issues with =
how the document does this now:
1. Section 4 does not adequately specify how the certificate in the =
FedFsNsdbParams should be used in the verification process.  Is it to be =
used as a trust anchor, so that any subordinate certificate is =
considered valid?  Or perhaps it is to be matched against the end-entity =
certificate.  In either case, it seems like it would be sufficient to =
provision a certificate fingerprint (or even a public key fingerprint) =
instead of the whole certificate.
2. In the security considerations, the document should discuss the =
implications of provisioning trust information in this way (depending on =
how it is used), and any requirements for security mechanisms to be used =
in these cases.


MINOR:

2.=20
It's not clear what the difference is between utf8string_cs and =
utf8string_cis.  Should you mention at some point that these MUST be =
UTF-8, even though the XDR won't enforce that?  (Say, at the beginning =
of Section 4?)

3.
It's not clear to me how FEDFS_ERR_PERM differs from FEDFS_ERR_ACCESS.  =
I don't see it called out for use anywhere in the procedure calls.  =
Perhaps this is a legacy of prior versions that should be deleted?


EDITORIAL:=20

3.=20
The definition of FEDFS_ERR_LOOP isn't actually related to looping.  It =
seems like this should either detect a loop (e.g., via a repeated name), =
or be renamed something like FEDFS_ERR_TOOMANYREFERS.

4. "The port is the NSDB transport port for the LDAP interface"
Suggest rewording to clarify that this is an LDAP/TCP port (I initially =
wondered if other transports could be used), e.g.:
"The port value in the FedFsNsdbName indicates the LDAP port on the =
NSDB"


From kathleen.moriarty@emc.com  Tue Jun 19 08:34:01 2012
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14F1311E80AD; Tue, 19 Jun 2012 08:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a1K-wgCgt+u3; Tue, 19 Jun 2012 08:33:59 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9651F11E80A4; Tue, 19 Jun 2012 08:33:52 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5JFXg9T024981 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Jun 2012 11:33:43 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 19 Jun 2012 11:33:25 -0400
Received: from mxhub15.corp.emc.com (mxhub15.corp.emc.com [128.222.70.236]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5JFXG9K029697; Tue, 19 Jun 2012 11:33:23 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub15.corp.emc.com ([128.222.70.236]) with mapi; Tue, 19 Jun 2012 11:33:20 -0400
From: <kathleen.moriarty@emc.com>
To: <draft-ietf-6man-lineid.all@tools.ietf.org>, <gen-art@ietf.org>, <iesg@ietf.org>
Date: Tue, 19 Jun 2012 11:33:19 -0400
Thread-Topic: Gen-Art review of draft-ietf-6man-lineid-05
Thread-Index: Ac1OMNqBZrrv/OGyQ7qTft9DNdHspw==
Message-ID: <F5063677821E3B4F81ACFB7905573F2403949010@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F5063677821E3B4F81ACFB7905573F2403949010MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: sven.ooghe@alcatel-lucent.com, nordmark@cisco.com, alan.kavanagh@ericsson.com, balazs.a.varga@ericsson.com
Subject: [Gen-art] Gen-Art review of draft-ietf-6man-lineid-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 15:34:01 -0000

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

 Document: draft-ietf-6man-lineid-05
 Reviewer: Kathleen Moriarty
 Review Date: June 19, 2012
 IETF LC End Date: June 18, 2012
 IESG Telechat date: (if known)

 Summary:  This document is read for publication.  I only found one tiny ni=
t on acronyms noted below.

Abstract:  In Ethernet based aggregation networks, several subscriber premi=
ses
   may be logically connected to the same interface of an edge router.
   This document proposes a method for the edge router to identify the
   subscriber premises using the contents of the received Router
   Solicitation messages.  The applicability is limited to broadband
   network deployment scenarios where multiple user ports are mapped to
   the same virtual interface on the Edge Router.


 Major issues:

 Minor issues:

 Nits/editorial comments:

Figure 1: Some of the acronyms used in the diagram are not expanded upon in=
 the introduction section, RG for instance (it is in the terminology sectio=
n, but is the only acronym not spelled out near figure 1).  It may also be =
confusing to see AN for Access Node next to Aggregation Network.  It may he=
lp to expand AN?  It is in the Introduction, so not a big deal.




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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Consolas, monospace" size=3D"2">
<div>I am the assigned Gen-ART reviewer for this draft. For background on</=
div>
<div>Gen-ART, please see the FAQ at</div>
<div>&lt; <a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfa=
q"><font color=3D"#0000FF"><u>http://wiki.tools.ietf.org/area/gen/trac/wiki=
/GenArtfaq</u></font></a>&gt;.</div>
<div>&nbsp;</div>
<div>Please wait for direction from your document shepherd</div>
<div>or AD before posting a new version of the draft.</div>
<div>&nbsp;</div>
<div> Document: draft-ietf-6man-lineid-05</div>
<div> Reviewer: Kathleen Moriarty</div>
<div> Review Date: June 19, 2012</div>
<div> IETF LC End Date: June 18, 2012</div>
<div> IESG Telechat date: (if known)</div>
<div>&nbsp;</div>
<div> Summary:&nbsp; This document is read for publication.&nbsp; I only fo=
und one tiny nit on acronyms noted below.</div>
<div>&nbsp;</div>
<div><font face=3D"Courier New, monospace" size=3D"2">Abstract:&nbsp; In Et=
hernet based aggregation networks, several subscriber premises</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; may be l=
ogically connected to the same interface of an edge router.</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; This doc=
ument proposes a method for the edge router to identify the</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; subscrib=
er premises using the contents of the received Router</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; Solicita=
tion messages.&nbsp; The applicability is limited to broadband</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; network =
deployment scenarios where multiple user ports are mapped to</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; the same=
 virtual interface on the Edge Router.</font></div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div> Major issues:</div>
<div>&nbsp;</div>
<div> Minor issues:</div>
<div>&nbsp;</div>
<div> Nits/editorial comments:</div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">Figure 1: Some of the ac=
ronyms used in the diagram are not expanded upon in the introduction sectio=
n, RG for instance (it is in the terminology section, but is the only acron=
ym not spelled out near figure 1).&nbsp;
It may also be confusing to see AN for Access Node next to Aggregation Netw=
ork.&nbsp; It may help to expand AN?&nbsp; It is in the Introduction, so no=
t a big deal. </font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
</font>
</body>
</html>

--_000_F5063677821E3B4F81ACFB7905573F2403949010MX15Acorpemccom_--

From meral.shirazipour@ericsson.com  Tue Jun 19 08:51:42 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1FFC21F84FB for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 08:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id saf2-yeTMJxC for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 08:51:41 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 760AC21F842B for <gen-art@ietf.org>; Tue, 19 Jun 2012 08:51:41 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q5JFpX0T011169; Tue, 19 Jun 2012 10:51:40 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.57]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 19 Jun 2012 11:51:38 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-trill-clear-correct.all@tools.ietf.org" <draft-ietf-trill-clear-correct.all@tools.ietf.org>
Date: Tue, 19 Jun 2012 11:51:36 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-trill-clear-correct-03.txt
Thread-Index: Ac1OMzo/7aFkPCKFRJ6j7B88Rtrs5A==
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7EUSAACMS0703e_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-trill-clear-correct-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 15:51:42 -0000

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

I am the assigned Gen-ART reviewer for draft-ietf-trill-clear-correct-03.tx=
t. For background on Gen-ART, please see the FAQ at <http://www.alvestrand.=
no/ietf/gen/art/gen-art-FAQ.html>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.


Document: draft-ietf-trill-clear-correct-03
Reviewer: Meral Shirazipour
Review Date: June-18-2012
IETF LC End Date: June-20-2012
IESG Telechat date: June-21-2012

Summary:
The document is ready for publication as a standards track RFC, however I h=
ave a few comments.



Minor issues:
TRILL-PORT-VER sub-TLV should be "PORT-TRILL-VER" sub-TLV.(there are a few =
occurrences)


Nits/editorial comments:
- Suggestion: [Page 6], line 2, spell out first occurrence LSP

- Suggestion: [Page 6], line 5, "overload bit on" ----> "overload bit set"

- Clarification:[Page 6], Section 2.1, line 5, add a comma "," after "traff=
ic engineered frames"

- Typo:[Page 6], last word, "contain" --missing s--> "contains"

- Suggestion: [Page 7], Section 2.2, line 2, spell out first occurrence of =
"Reverse Path Forwarding Check" and then use "RPFC" in the rest of the docu=
ment.

- Clarification:[Page 10], Section 2.4.2.3, line 5, sentence starting with =
"RB2 MUST advertise ...": we could omit the second occurrence of "it might =
use" in that sentence.

- Clarification:[Page 10], Section 2.4.2.3, 3rd line from last, "end statio=
ns connected to RB": "a RB" or "RBs"?

- Typo: [Page 11], Section 3.1,"( j, k)" --remove extra space--> "(j, k)"

- Suggestion: [Page 11], Section 3.2, "already in flight" ----> "already in=
 transmission"

- Typo [Page 12]:"many multi-destination frame"--missing s--> "many multi-d=
estination frames"

- Clarification:[Page 13], Point 4. , Sentence 2: suggested clarification:
"It does so by checking LSPs it receives and updating its link state databa=
se for any of its nicknames held with higher priority by another TRILL Swit=
ch that is IS-IS reachable."

- Typo [Page 14]:"unicast Channel message"--missing s-->"unicast Channel me=
ssages"

- Typo [Page 16]: Section 5.2,"Routeing" ----> "Routing"

- Suggestion:[Page 16],last sentence, suggestion: "This safety margin is ca=
lled "Margin" below."

- Typo [Page 18]:"a specified in [RFC6325]"--missing s-->"as specified in [=
RFC6325]"

- Suggestion: [Page 19], spell out first occurrence of EISS

- Suggestion:[Page 21], Point 1, not clear what the new text becomes. Sugge=
stion: refer to last paragraph of section 3.1 instead of paragraph before 3=
.2, and propose the new sentence.

- Clarification:[Page 21], Point 2, it is not clear what the change is to s=
ection 3.2 of RFC6327.

- Clarification:[Page 21], Point 3, it would be clearer to say "bullet A9 i=
s added" (if this is an event like the rest of the bullets in section 3.3 o=
f RFC6327)

- Clarification:[Page 22], section 10.1,"disagreement over the Designated V=
LAN or the like". Suggestion: replace the term "or the like" with other exa=
mples or remove the term.

-Typo: [Page 22], section 10.1, "each others frames"---->"each other's fram=
es"

-Typo: [Page 24], "DRB SHOULD NOT appointed"---->"DRB SHOULD NOT appoint", =
"an VLAN"---->"a VLAN", "RBridged"---->"RBridge"

-Clarification:[Page 25], Section 11, Point 1, "The previously reserved", r=
eference to document.

- Clarification: [page 19/page 27], Informative References, reference [802]=
, to verify which standard we want to refer to for Canonical Format Indicat=
or:
If it is "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan Area =
Networks: Overview and Architecture", then the date should be 7 February 20=
01."
However this specific document does not define CIF. You may want to refer t=
o 802.1Q-2005.




Thanks,
Meral

---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

--_000_25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7EUSAACMS0703e_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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=3DEN-CA link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the assigne=
d Gen-ART reviewer for draft-ietf-trill-clear-correct-03.txt. For backgroun=
d on Gen-ART, please see the FAQ at &lt;http://www.alvestrand.no/ietf/gen/a=
rt/gen-art-FAQ.html&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:=
p></p><p class=3DMsoNormal>Please resolve these comments along with any oth=
er Last Call comments you may receive.<o:p></o:p></p><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMs=
oNormal>Document: draft-ietf-trill-clear-correct-03<o:p></o:p></p><p class=
=3DMsoNormal>Reviewer: Meral Shirazipour<o:p></o:p></p><p class=3DMsoNormal=
>Review Date: June-18-2012<o:p></o:p></p><p class=3DMsoNormal>IETF LC End D=
ate: June-20-2012<o:p></o:p></p><p class=3DMsoNormal>IESG Telechat date: Ju=
ne-21-2012<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>Summary:<o:p></o:p></p><p class=3DMsoNormal>The document is re=
ady for publication as a standards track RFC, however I have a few comments=
.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>Minor issues:<o:p></o:p></p><p class=3DMsoNormal>TRILL-PORT-VE=
R sub-TLV should be &quot;PORT-TRILL-VER&quot; sub-TLV.(there are a few occ=
urrences)<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Nits/editorial comme=
nts:<o:p></o:p></p><p class=3DMsoNormal>- Suggestion: [Page 6], line 2, spe=
ll out first occurrence LSP<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><p class=3DMsoNormal>- Suggestion: [Page 6], line 5, &quot;overloa=
d bit on&quot; ----&gt; &quot;overload bit set&quot;<o:p></o:p></p><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>- Clarification:[Pag=
e 6], Section 2.1, line 5, add a comma &quot;,&quot; after &quot;traffic en=
gineered frames&quot;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p><p class=3DMsoNormal>- Typo:[Page 6], last word, &quot;contain&quot; --m=
issing s--&gt; &quot;contains&quot;<o:p></o:p></p><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p><p class=3DMsoNormal>- Suggestion: [Page 7], Section 2.2, =
line 2, spell out first occurrence of &quot;Reverse Path Forwarding Check&q=
uot; and then use &quot;RPFC&quot; in the rest of the document.<o:p></o:p><=
/p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>- Clarifi=
cation:[Page 10], Section 2.4.2.3, line 5, sentence starting with &quot;RB2=
 MUST advertise ...&quot;: we could omit the second occurrence of &quot;it =
might use&quot; in that sentence.<o:p></o:p></p><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p><p class=3DMsoNormal>- Clarification:[Page 10], Section 2.4.=
2.3, 3rd line from last, &quot;end stations connected to RB&quot;: &quot;a =
RB&quot; or &quot;RBs&quot;?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;=
</o:p></p><p class=3DMsoNormal>- Typo: [Page 11], Section 3.1,&quot;( j, k)=
&quot; --remove extra space--&gt; &quot;(j, k)&quot;<o:p></o:p></p><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>- Suggestion: [Page =
11], Section 3.2, &quot;already in flight&quot; ----&gt; &quot;already in t=
ransmission&quot;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
p class=3DMsoNormal>- Typo [Page 12]:&quot;many multi-destination frame&quo=
t;--missing s--&gt; &quot;many multi-destination frames&quot;<o:p></o:p></p=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>- Clarifica=
tion:[Page 13], Point 4. , Sentence 2: suggested clarification:<o:p></o:p><=
/p><p class=3DMsoNormal>&quot;It does so by checking LSPs it receives and u=
pdating its link state database for any of its nicknames held with higher p=
riority by another TRILL Switch that is IS-IS reachable.&quot;<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>- Typo [Pa=
ge 14]:&quot;unicast Channel message&quot;--missing s--&gt;&quot;unicast Ch=
annel messages&quot;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p><p class=3DMsoNormal>- Typo [Page 16]: Section 5.2,&quot;Routeing&quot; -=
---&gt; &quot;Routing&quot;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><p class=3DMsoNormal>- Suggestion:[Page 16],last sentence, suggest=
ion: &quot;This safety margin is called &quot;Margin&quot; below.&quot;<o:p=
></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>-=
 Typo [Page 18]:&quot;a specified in [RFC6325]&quot;--missing s--&gt;&quot;=
as specified in [RFC6325]&quot;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p><p class=3DMsoNormal>- Suggestion: [Page 19], spell out first =
occurrence of EISS<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p>=
<p class=3DMsoNormal>- Suggestion:[Page 21], Point 1, not clear what the ne=
w text becomes. Suggestion: refer to last paragraph of section 3.1 instead =
of paragraph before 3.2, and propose the new sentence.<o:p></o:p></p><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>- Clarification:[P=
age 21], Point 2, it is not clear what the change is to section 3.2 of RFC6=
327.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMso=
Normal>- Clarification:[Page 21], Point 3, it would be clearer to say &quot=
;bullet A9 is added&quot; (if this is an event like the rest of the bullets=
 in section 3.3 of RFC6327)<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><p class=3DMsoNormal>- Clarification:[Page 22], section 10.1,&quot=
;disagreement over the Designated VLAN or the like&quot;. Suggestion: repla=
ce the term &quot;or the like&quot; with other examples or remove the term.=
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorm=
al>-Typo: [Page 22], section 10.1, &quot;each others frames&quot;----&gt;&q=
uot;each other's frames&quot;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p><p class=3DMsoNormal>-Typo: [Page 24], &quot;DRB SHOULD NOT appo=
inted&quot;----&gt;&quot;DRB SHOULD NOT appoint&quot;, &quot;an VLAN&quot;-=
---&gt;&quot;a VLAN&quot;, &quot;RBridged&quot;----&gt;&quot;RBridge&quot;<=
o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorma=
l>-Clarification:[Page 25], Section 11, Point 1, &quot;The previously reser=
ved&quot;, reference to document.<o:p></o:p></p><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p><p class=3DMsoNormal>- Clarification: [page 19/page 27], Inf=
ormative References, reference [802], to verify which standard we want to r=
efer to for Canonical Format Indicator: <o:p></o:p></p><p class=3DMsoNormal=
>If it is &quot;IEEE Std 802-2001: IEEE Standard for Local and Metropolitan=
 Area Networks: Overview and Architecture&quot;, then the date should be 7 =
February 2001.&quot;<o:p></o:p></p><p class=3DMsoNormal>However this specif=
ic document does not define CIF. You may want to refer to 802.1Q-2005.<o:p>=
</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thanks,<o:p></o:p></p><p c=
lass=3DMsoNormal>Meral<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p>=
</p><p class=3DMsoNormal>---<o:p></o:p></p><p class=3DMsoNormal>Meral Shira=
zipour<o:p></o:p></p><p class=3DMsoNormal>Ericsson<o:p></o:p></p><p class=
=3DMsoNormal>Research<o:p></o:p></p><p class=3DMsoNormal>www.ericsson.com<o=
:p></o:p></p></div></body></html>=

--_000_25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7EUSAACMS0703e_--

From lizhong.jin@zte.com.cn  Tue Jun 19 10:18:17 2012
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 435CC21F8517 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 10:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.487
X-Spam-Level: 
X-Spam-Status: No, score=-101.487 tagged_above=-999 required=5 tests=[AWL=0.351, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ipvLMQ0E5C2 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 10:18:14 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id AF94821F8522 for <gen-art@ietf.org>; Tue, 19 Jun 2012 10:18:13 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 286201878467102; Wed, 20 Jun 2012 01:14:51 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 99854.4447640030; Wed, 20 Jun 2012 01:17:59 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q5JHI1nl071634; Wed, 20 Jun 2012 01:18:01 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <1340118968.31554.33576.camel@mightyatom.folly.org.uk>
To: Elwyn Davies <elwynd@folly.org.uk>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFAAEAB3D5.D300977C-ON48257A22.00581007-48257A22.005F0A02@zte.com.cn>
From: Lizhong Jin<lizhong.jin@zte.com.cn>
Date: Wed, 20 Jun 2012 01:17:20 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-06-20 01:18:04, Serialize complete at 2012-06-20 01:18:04
Content-Type: multipart/alternative; boundary="=_alternative 005F0A0048257A22_="
X-MAIL: mse01.zte.com.cn q5JHI1nl071634
Cc: draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-pwe3-cbit-negotiation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 17:18:17 -0000

This is a multipart message in MIME format.
--=_alternative 005F0A0048257A22_=
Content-Type: text/plain; charset="US-ASCII"

Hi Elwyn,
Thank you for the prompt reply. See inline below.

Lizhong
 

Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/19 23:16:08:

> Hi, Lizhong.
> 
> On Tue, 2012-06-19 at 21:48 +0800, Lizhong Jin wrote:
> > 
> > Hi Elwyn, 
> > Thank you for the review. It seems you are reviewing v-03, not v-04,
> > but some comments are for v-04. I am confused.
> Yes, I started reviewing v03 but had to stop because of other tasks and
> came back to v04.  I though I had revisited all my old commnets and
> updated them, but clearly not.
> >  See my reply inline below. 
> > 
> > Regards 
> > Lizhong 
> > 
> > 
> > Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/19 20:12:17:
> > 
> > > I am the assigned Gen-ART reviewer for this draft. For background
> > on 
> > > Gen-ART, please see the FAQ at 
> > > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>. 
> > > 
> > > Please resolve these comments along with any other Last Call
> > comments 
> > > you may receive. 
> > > 
> > > Document: draft-ietf-pwe3-cbit-negotiation-04.txt
> > > Reviewer: Elwyn Davies
> > > Review Date: 19 June 2012
> > > IETF LC End Date: 15 June 2012
> > > IESG Telechat date: 21 June 2012
> > > 
> > > Summary: 
> > > Not ready. The proposal for the NOT PREFERRED to PREFERRED
> > transition
> > > case does not appear to be compatible with the existing RFC 4447
> > > standard in the way stated and there are a number of other minor
> > issues.
> > > The draft is also in need of an editing pass by an author whose
> > mother
> > > tongue is English as there are parts where the syntax is misleading
> > > rather than just clumsy. 
> > [Lizhong] We have two editors, and both Raymond and I are editing this
> > document. Hope the below reply will make it clear.
> 
> > > 
> > > Apologies for the late submission of the review.
> > > 
> > > Major issues: 
> > > s3: The discussion of the NOT PREFERRED to PREFERRED transition case
> > > (buried at the end of s3 - causing me to ask 'what about this case?'
> > > during reading of s2 and most of s3)  implies that some existing RFC
> > > 4447 procedure applies. Clearly, if the PW is not using the control
> > word
> > > then there is nothing to do.  On the other hand, inspection of s6.2
> > of
> > > RFC4447 indicates that once the two PEs have agreed on c = 1, 'setup
> > is
> > > complete' and Label Mapping messages would therefore be
> > > 'unexpected' (see item '-i' in second set of bullets in s6.2 of RFC
> > > 4447). So, what procedure is to be used? And what implications does
> > this
> > > have for backwards compatibility?  Wouldn't it be generally simpler
> > to
> > > apply the PREFERRED to NOT PREFERRED mechanism to all case? 
> > [Lizhong] this draft is to solve the case to change a PW from c=0 to
> > c=1, that means one PE should change its use of control word from NOT
> > PREFERRED to PREFERRED. RFC4447 is already there and deployed, and the
> > PE will not always send its locally configured preferrence according
> > RFC4447, see PE1 behavior in section 2 step 1&2. That's why we could
> > not simply apply the mechanism at the end of section 3. Hope it is
> > clear. 
> There are two issues here:
> - Clarity: RFC 4447 does not have any discussion of what might happen if
> the configuration value changes.  The draft focusses on on transition
> direction but does not mention the other except for one paragaph right
> at the end of s3.  It is therefore reasonable that somebody looking at
> this draft would wonder 'what about the other transition direction?'.
> Whether or not anything needs to be done it would save people wondering
> if you put in a sentence in the introduction to explain that the other
> direction is not (or is) a problem.
[Lizhong] accept. Add following:
When PE changes the preference for the use of control word from PREFERRED 
to NOT PREFERRED, it should follow [RFC4447], and there is no problem.

> - Technical: The paragraph in s3 implies that the PREFERRED to NOT
> PREFERRED direction will result in some part of the RFC 4447 protocol
> being (re-)invoked.  What part is not made very clear.  As far as I can
> see sending more messages other than Label Release or Label Withdraw for
> this PW is not part of the RFC 4447 protocol and hence will cause an
> error.  Alternatively if it isn't reinvoked, the PW will continue to use
> control words.  Please explain what is going on here.  The fact that RFC
> 4447 has been deployed doesn't explain what is going on.
[Lizhong] now I understand you concern. The last sentance of s3 is not 
clear. How about the following:
In that case, local PE will always send Label Withdraw message if already 
sending Label Mapping message, and then send new Label Mapping message 
with C-bit value following the procedures defined in [RFC4447].

> > 
> > > 
> > > Minor issues: 
> > > s3: Has there been any discussion on possible race conditions?
> >  Changing
> > > the configuration value during the message exchange strikes me as
> > > dangerous - it is probably sufficient to note that changes should be
> > > suppressed during the Label Mapping message exchange but I am not
> > > totally sure about this. 
> > [Lizhong] The message would be processed in sequence in TCP-based LDP
> > session. I do not see a problem here. But we do have a note in section
> > 3 for multi-segment PW for sequence processing. 
> There are several network round trips in the message exchanges.  The
> protocol and the configuration mechanism in a PE are potentially
> separate threads.  There is scope, depending on the implementation, for
> the user at the 'remote' PE to change the configuration during the
> message exchange making for a potential race condition. 
[Lizhong] we discussed the race condition on the PWE3 maillist from Spike, 
and for multi-segment PW, we add a note to ensure the sequence processing 
for implementation.

> > 
> > > 
> > > s3, bullet '-i':  I completely misparsed this section on first
> > reading
> > > and I am still not absolutely sure what message sequence is being
> > > specified.  Working back from later sections I *think* that the
> > > intention is:
> > > IF Mapping sent THEN { send Withdraw; send Release;}
> > > Wait to receive Release
> > > The implication at present is that a Mapping might not have been
> > sent
> > > and then only a Release is needed: is this a possibility? Please
> > > clarify.
> > > The picture in Appendix A suffers from the same problem. 
> > [Lizhong] Adrian raise the same comment, and I change it as below: 
> >        -i.  PE MUST send a Label Release message to remote PE. If a
> > PE 
> >             has previously sent a Label Mapping message to a remote
> > PE, 
> >             it MUST also send a Label Withdraw message to the remote
> > PE, 
> >             and wait until it receives a Label Release message from
> > the
> >            remote PE. 
> What does it send first if both must be sent?  The text in the rest of
> the document implies withdraw then release.  This new text sort of
> implies release then withdraw but isn't really clear.
[Lizhong] both should be sent, and does not require the sending sequence. 
The two messages does not have dependence.

> > 
> > > 
> > > s3, discussion of multi-segment PWs: The statement that S-PE's
> > SHOULD
> > > assume an initial passive role seems to have several problems:
> > > - Does this mean that changing the configuration of an S-PE would
> > not
> > > provoke the new mechanisms?
> > > - The passive role situation is only specified for some sorts of
> > linked
> > > FECs in RFC 6073 - what about other cases?
> > > - What are the consequences for ignoring the SHOULD in this case? (I
> > > have to say I am unsure that RFC 6073 deals with this problem
> > either.) 
> > [Lizhong] we follow RFC6073, and passive role is only applied for the
> > PW FEC, other cases are out of scope. 
> Why? This needs an explanation. Also this doesn't cover the point about
> whether reconfig of an S-PE is allowed and how this squares with the
> passive role.
> > SHOULD means highly recommended. We do not meet any problem when
> > implementing RFC6073. Do you suggest to change this to MUST? 
> Whenever a specification includes a 'SHOULD' the question arises of what
> alternatives there might be and what is the reason for preferring the
> suggested solution.  In the original setup, it is fairly clear that life
> is easier letting setup progress from  one end to the other (although
> this is not spelt out - I would have argued for this had  I reviewed the
> doc).  For the configuration change this is less obvious.  Regarding the
> point about reconfig of the  S-PE, it is going to make life more
> complicated if the S-PE has to tell the T-PE to be active so it can be
> passive.  I would therefore argue that probably the notion of passivity
> is irrelevant to the transition use case.  Whether it should be SHOULD
> or MUST is therefore moot.
[Lizhong] how about the following? Because we just refer to RFC6073, and 
does not add anything new.
An initial passive role is defined in [RFC6073] for S-PE.

> 
> > > 
> > > 
> > > Nits/editorial comments: 
> > > General: In RFC 4447, the label message names use title case (e.g.,
> > > Label Mapping).  For consistency this should be followed throughout
> > this
> > > document. 
> > [Lizhong] yes, and thank you and Adrian.
> > > 
> > > Abstract:  Should not contain references.  Best to give full title
> > of
> > > RFC and number in round brackets. 
> > [Lizhong] I removed brackets and do not intend to contain citations
> > here. It seems the citations are generated automatically by IETF.
> > Could the round brackets solve this? Or are you referring v-03? 
> (leftover from 03)
> > 
> > > Abstract: s/problem of control/ the problem with control/ (if there
> > is
> > > just one) 
> > [Lizhong] are you reviewing v-03 of the draft? In v-04, the abstract
> > has been revised in v-04.
> (leftover from 03)
> > 
> > 
> > > Abstract: The second two sentences say the same thing in different
> > ways 
> > > OLD
> > >    Based on the problem analysis, a
> > >    message exchanging mechanism is introduced to solve this control
> > word
> > >    negotiation issue.  This document is to update [RFC4447] control
> > word
> > >    negotiation mechanism.
> > > NEW
> > > Based on the problem analysis, this document introduces a modified 
> > > message exchange 
> > > sequence updating the control word negotiation mechanism in RFC
> > 4447.
> > > 
> > > This issue also applies to s1. 
> > [Lizhong] are you reviewing v-03 of the draft? In v-04, the abstract
> > has been revised in v-04.
> (leftover from 03)
> > 
> > 
> > > 
> > > s1: Subtle distinction - this is a practical problem with the 
> > > mechanism defined in RFC 4447 rather 
> > > than the abstract problem of how to do control word negotiation:
> > >  s/the problem of control word negotiation/problems identified in 
> > > the control word negotiation/ 
> > [Lizhong] has been revised in v-04.
> > > 
> yes.
> > > s1: Expand acronym PW. 
> > [Lizhong] has been revised in v-04.
> Not as far as I can see.
[Lizhong] write "pseudowire" directly in the text, not PW.

> > > 
> > > s2: Expand acronym PE. 
> > [Lizhong] accept 
> > 
> > > s2, 2nd sentence: s/configurable/configured/ 
> > [Lizhong] configurable is right. 
> Leave that one to the RFc Editor.
> > 
> > > s2, 3rd and 4th sentences: I *think* this text is trying to say: 
> > >   The intention of the control word negotiation is that the control
> > word
> > > will be used when both endpoints are configured with control word
> > usage
> > > PREFERRED.  However if one endpoint is initially configured with
> > control
> > > word usage NOT PREFERRED but later changes to PREFERRED, a PW
> > between
> > > the endpoints will not transition to usage of the control word as
> > > explained below. 
> > [Lizhong] no, the case is that operator deploys PW with control word
> > used in the first phase. In the second phase, they want to upgrade
> > their PW service to use control word. Two different deployment
> > timeframes.
> That is what my sentence says.
[Lizhong] ok.

> > 
> > 
> > > 
> > > s2, bullet #2: s/PE1 send label mapping with C bit=0
> > finally./ultimately
> > > PE1 sends a Label Mapping message with the C bit set to 0./ 
> > [Lizhong] accept
> > > 
> > > s2, bullet #4: s/send label withdraw/send a Label Withdraw/ 
> > [Lizhong] accept
> > > 
> > > s2, bullet #5: s/the received/the previously received/, 
> > > s/indicates C bit=0/carried the C bit set to 0/, 
> > > s/send label mapping with C bit=0/send a label mapping message with
> > the
> > > C bit set to 0/ 
> > [Lizhong] accept
> > > 
> > > s3: It would be much clearer if s3 was divided into 3 sub-sections
> > > (possibly reordered):
> > > - PREFERRED to NOT PREFERRED transition
> > > - NOT PREFERRED to PREFERRED transition
> > > - Multi-segment case (which should refer to both previous cases)
> > > The pointer to the diagram in Appendix A could usefully occur in the
> > > introduction to s3.  If this was adopted s3.1 could either be a
> > fourth
> > > sub-section or a sub-sub-section of the PREFERRED to NOT PREFERRED
> > > section. 
> > [Lizhong] PREFERRED to NOT PREFERRED does not introduce any new.
> > Multi-segment case is fully inherited from single-segment case. It
> > would be redundancy to have sub-sections here. 
> I disagree strongly.  The multi-segment case affects the other RFC and
> needs to be made to stand out so that implementors can see where the
> changes occur.  The PREFERRED to NOT PREFERRED case also ought to be
> separated whether or not I am right about this case. 
[Lizhong] how about only divide multi-segment? The case of PREFERRED to 
NOT PREFERRED case is only for reference, and the text is not many.
> > 
> > > 
> > > s3, Various acronyms need expanding: FEC, T-PE, S-PE 
> > [Lizhong] accept
> > > 
> > > s3, para 1: s/adding label request/adding a new label request/ 
> > [Lizhong] much difference here?
> Yes. How it reads in English.  There are many missing definite articles
> and indefinite articles that make the text read very badly for a native
> English speaker.  I understand that this is a very difficult aspect for
> someone who has a first language that does not employ articles in the
> way that English does.
[Lizhong] ok
> > > 
> > > s3 bullets '-i' to '-iii': s/Local PE/The local PE/, s/remote PR/the
> > > remote peer PE/.  Also a more usual labeling of the bullets would be
> > > appropriate (e.g., just i, ii and iii). 
> > [Lizhong] accept, and I do not see "remote PR".
> should have been 'remote PE'.
[Lizhong] ok
> > > 
> > > s3, para 2: s/When Local/When the local/,
> > > s/the remote label mapping message with C bit=0, additional
> > procedure
> > > will be added as follow:/a label mapping message from the PW peer
> > with
> > > the C bits set to 0, the following additional procedure will be
> > acrried
> > > out:/ 
> > [Lizhong] accept
> > > 
> > > s3, bullet '-i': s/wait until receiving a label release/wait until
> > it
> > > has received a Label Release message/ (but general clarification and
> > > rewording needed - see issues section above). 
> > [Lizhong] do not see much difference here. Of couse the "label
> > release" should be capitalized.
> Your form implies that that the action can occur as soon as the message
> starts to be received (as in 'the radio is receiving a programme').
> This is not the case - the action can occur only when the whole message
> has been received. 
[Lizhong] ok, thanks.

> > > 
> > > s3, bullet '-ii':
> > > OLD:
> > >       Local PE MUST send a label request message to remote PE, and
> > >       wait until receiving a label mapping message containing the
> > remote
> > >       PE locally configured preference for use of control word.
> > > NEW:
> > >       The local PE MUST send a Label Mapping message to the peer PE
> > with the
> > >       C bit set to 1, and then wait until a Label Mapping message
> > isreceived 
> > >       containing the peer's current configured preference for usage
> > of the 
> > >       control word. 
> > [Lizhong] no, the procedure here is not right. The local PE MUST send
> > a label request message, not label mapping.
> Try:
> The local PE MUST send a Label Request message to the peer PE  and then
> wait until a Label Mapping message is received containing the peer's
> current configured preference for usage of the control word. 
[Lizhong] ok

> > > 
> > > s3, para sfter item '-iii': s/successfully/has successfully/ 
> > [Lizhong] accept 
> > 
> > > The following implies that there is memory of previous action
> > although
> > > the label binding has been destroyed. Better would be:
> > > OLD:
> > > >    ...and removed the remote label binding, it MUST reset
> > > >    its use of control word with the locally configured preference,
> > and
> > > >    send label mapping as a response of label request with locally
> > > >    configured preference for use of control word.
> > > NEW:
> > > ...and removed the remote label binding, subsequent Label Requests
> > will
> > > naturally be treated as new requests and processed as described in
> > > Section 6 of RFC 4447. 
> > [Lizhong] we got similar comments from Adrian, and will update this. 
> > 
> > > 
> > > s3, discussion of multi-segment PWs: s/case for T-PE is same./case
> > for a
> > > T-PE operates similarly./ 
> > [Lizhong] accept
> > > 
> > > s3, last para/Appendix A:  The diagram doesn't cover the PREFERRED
> > to
> > > NOT PREFERRED transition. 
> > [Lizhong] no, there is a "no" branch under "NOT Preferred to
> > Preferred" to cover "PREFERRED to NOT PREFERRED". Anyway, the diagram
> > discription should be "NOT Preferred to Preferred" which is wrong in
> > v-04. 
> > 
> > > 
> > > s3.1: The wording in this section is generally  rather 'loose'.  A
> > more
> > > formal style would be helpful. 
> > [Lizhong] this is a usecase to give an example, so we make it "loose".
> > > 
> > > 
> > > 
> 
> 

--=_alternative 005F0A0048257A22_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Elwyn,</font>
<br><font size=2 face="sans-serif">Thank you for the prompt reply. See
inline below.</font>
<br>
<br><font size=2 face="sans-serif">Lizhong</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br><font size=2><tt>Elwyn Davies &lt;elwynd@folly.org.uk&gt; wrote 2012/06/19
23:16:08:<br>
<br>
&gt; Hi, Lizhong.<br>
&gt; <br>
&gt; On Tue, 2012-06-19 at 21:48 +0800, Lizhong Jin wrote:<br>
&gt; &gt; <br>
&gt; &gt; Hi Elwyn, <br>
&gt; &gt; Thank you for the review. It seems you are reviewing v-03, not
v-04,<br>
&gt; &gt; but some comments are for v-04. I am confused.<br>
&gt; Yes, I started reviewing v03 but had to stop because of other tasks
and<br>
&gt; came back to v04. &nbsp;I though I had revisited all my old commnets
and<br>
&gt; updated them, but clearly not.<br>
&gt; &gt; &nbsp;See my reply inline below. <br>
&gt; &gt; <br>
&gt; &gt; Regards <br>
&gt; &gt; Lizhong <br>
&gt; &gt; &nbsp; <br>
&gt; &gt; <br>
&gt; &gt; Elwyn Davies &lt;elwynd@folly.org.uk&gt; wrote 2012/06/19 20:12:17:<br>
&gt; &gt; <br>
&gt; &gt; &gt; I am the assigned Gen-ART reviewer for this draft. For background<br>
&gt; &gt; on <br>
&gt; &gt; &gt; Gen-ART, please see the FAQ at <br>
&gt; &gt; &gt; &lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.
<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Please resolve these comments along with any other Last
Call<br>
&gt; &gt; comments <br>
&gt; &gt; &gt; you may receive. <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Document: draft-ietf-pwe3-cbit-negotiation-04.txt<br>
&gt; &gt; &gt; Reviewer: Elwyn Davies<br>
&gt; &gt; &gt; Review Date: 19 June 2012<br>
&gt; &gt; &gt; IETF LC End Date: 15 June 2012<br>
&gt; &gt; &gt; IESG Telechat date: 21 June 2012<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Summary: <br>
&gt; &gt; &gt; Not ready. The proposal for the NOT PREFERRED to PREFERRED<br>
&gt; &gt; transition<br>
&gt; &gt; &gt; case does not appear to be compatible with the existing
RFC 4447<br>
&gt; &gt; &gt; standard in the way stated and there are a number of other
minor<br>
&gt; &gt; issues.<br>
&gt; &gt; &gt; The draft is also in need of an editing pass by an author
whose<br>
&gt; &gt; mother<br>
&gt; &gt; &gt; tongue is English as there are parts where the syntax is
misleading<br>
&gt; &gt; &gt; rather than just clumsy. <br>
&gt; &gt; [Lizhong] We have two editors, and both Raymond and I are editing
this<br>
&gt; &gt; document. Hope the below reply will make it clear.<br>
&gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Apologies for the late submission of the review.<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Major issues: <br>
&gt; &gt; &gt; s3: The discussion of the NOT PREFERRED to PREFERRED transition
case<br>
&gt; &gt; &gt; (buried at the end of s3 - causing me to ask 'what about
this case?'<br>
&gt; &gt; &gt; during reading of s2 and most of s3) &nbsp;implies that
some existing RFC<br>
&gt; &gt; &gt; 4447 procedure applies. Clearly, if the PW is not using
the control<br>
&gt; &gt; word<br>
&gt; &gt; &gt; then there is nothing to do. &nbsp;On the other hand, inspection
of s6.2<br>
&gt; &gt; of<br>
&gt; &gt; &gt; RFC4447 indicates that once the two PEs have agreed on c
= 1, 'setup<br>
&gt; &gt; is<br>
&gt; &gt; &gt; complete' and Label Mapping messages would therefore be<br>
&gt; &gt; &gt; 'unexpected' (see item '-i' in second set of bullets in
s6.2 of RFC<br>
&gt; &gt; &gt; 4447). So, what procedure is to be used? And what implications
does<br>
&gt; &gt; this<br>
&gt; &gt; &gt; have for backwards compatibility? &nbsp;Wouldn't it be generally
simpler<br>
&gt; &gt; to<br>
&gt; &gt; &gt; apply the PREFERRED to NOT PREFERRED mechanism to all case?
<br>
&gt; &gt; [Lizhong] this draft is to solve the case to change a PW from
c=0 to<br>
&gt; &gt; c=1, that means one PE should change its use of control word
from NOT<br>
&gt; &gt; PREFERRED to PREFERRED. RFC4447 is already there and deployed,
and the<br>
&gt; &gt; PE will not always send its locally configured preferrence according<br>
&gt; &gt; RFC4447, see PE1 behavior in section 2 step 1&amp;2. That's why
we could<br>
&gt; &gt; not simply apply the mechanism at the end of section 3. Hope
it is<br>
&gt; &gt; clear. <br>
&gt; There are two issues here:<br>
&gt; - Clarity: RFC 4447 does not have any discussion of what might happen
if<br>
&gt; the configuration value changes. &nbsp;The draft focusses on on transition<br>
&gt; direction but does not mention the other except for one paragaph right<br>
&gt; at the end of s3. &nbsp;It is therefore reasonable that somebody looking
at<br>
&gt; this draft would wonder 'what about the other transition direction?'.<br>
&gt; Whether or not anything needs to be done it would save people wondering<br>
&gt; if you put in a sentence in the introduction to explain that the other<br>
&gt; direction is not (or is) a problem.</tt></font>
<br><font size=2><tt>[Lizhong] accept. Add following:</tt></font>
<br><font size=2><tt>When PE changes the preference for the use of control
word from PREFERRED to NOT PREFERRED, it should follow [RFC4447], and there
is no problem.</tt></font>
<br><font size=2><tt><br>
&gt; - Technical: The paragraph in s3 implies that the PREFERRED to NOT<br>
&gt; PREFERRED direction will result in some part of the RFC 4447 protocol<br>
&gt; being (re-)invoked. &nbsp;What part is not made very clear. &nbsp;As
far as I can<br>
&gt; see sending more messages other than Label Release or Label Withdraw
for<br>
&gt; this PW is not part of the RFC 4447 protocol and hence will cause
an<br>
&gt; error. &nbsp;Alternatively if it isn't reinvoked, the PW will continue
to use<br>
&gt; control words. &nbsp;Please explain what is going on here. &nbsp;The
fact that RFC<br>
&gt; 4447 has been deployed doesn't explain what is going on.</tt></font>
<br><font size=2><tt>[Lizhong] now I understand you concern. The last sentance
of s3 is not clear. How about the following:</tt></font>
<br><font size=2><tt>In that case, local PE will always send Label Withdraw
message if already sending Label Mapping message, and then send new Label
Mapping message with C-bit value following the procedures defined in [RFC4447].</tt></font>
<br><font size=2><tt><br>
&gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Minor issues: <br>
&gt; &gt; &gt; s3: Has there been any discussion on possible race conditions?<br>
&gt; &gt; &nbsp;Changing<br>
&gt; &gt; &gt; the configuration value during the message exchange strikes
me as<br>
&gt; &gt; &gt; dangerous - it is probably sufficient to note that changes
should be<br>
&gt; &gt; &gt; suppressed during the Label Mapping message exchange but
I am not<br>
&gt; &gt; &gt; totally sure about this. <br>
&gt; &gt; [Lizhong] The message would be processed in sequence in TCP-based
LDP<br>
&gt; &gt; session. I do not see a problem here. But we do have a note in
section<br>
&gt; &gt; 3 for multi-segment PW for sequence processing. <br>
&gt; There are several network round trips in the message exchanges. &nbsp;The<br>
&gt; protocol and the configuration mechanism in a PE are potentially<br>
&gt; separate threads. &nbsp;There is scope, depending on the implementation,
for<br>
&gt; the user at the 'remote' PE to change the configuration during the<br>
&gt; message exchange making for a potential race condition. </tt></font>
<br><font size=2><tt>[Lizhong] we discussed the race condition on the PWE3
maillist from Spike, and for multi-segment PW, we add a note to ensure
the sequence processing for implementation.</tt></font>
<br><font size=2><tt><br>
&gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3, bullet '-i': &nbsp;I completely misparsed this section
on first<br>
&gt; &gt; reading<br>
&gt; &gt; &gt; and I am still not absolutely sure what message sequence
is being<br>
&gt; &gt; &gt; specified. &nbsp;Working back from later sections I *think*
that the<br>
&gt; &gt; &gt; intention is:<br>
&gt; &gt; &gt; IF Mapping sent THEN { send Withdraw; send Release;}<br>
&gt; &gt; &gt; Wait to receive Release<br>
&gt; &gt; &gt; The implication at present is that a Mapping might not have
been<br>
&gt; &gt; sent<br>
&gt; &gt; &gt; and then only a Release is needed: is this a possibility?
Please<br>
&gt; &gt; &gt; clarify.<br>
&gt; &gt; &gt; The picture in Appendix A suffers from the same problem.
<br>
&gt; &gt; [Lizhong] Adrian raise the same comment, and I change it as below:
<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;-i. &nbsp;PE MUST send a Label Release
message to remote PE. If a<br>
&gt; &gt; PE <br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; has previously sent
a Label Mapping message to a remote<br>
&gt; &gt; PE, <br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; it MUST also send a
Label Withdraw message to the remote<br>
&gt; &gt; PE, <br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and wait until it receives
a Label Release message from<br>
&gt; &gt; the<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;remote PE. <br>
&gt; What does it send first if both must be sent? &nbsp;The text in the
rest of<br>
&gt; the document implies withdraw then release. &nbsp;This new text sort
of<br>
&gt; implies release then withdraw but isn't really clear.</tt></font>
<br><font size=2><tt>[Lizhong] both should be sent, and does not require
the sending sequence. The two messages does not have dependence.</tt></font>
<br><font size=2><tt><br>
&gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3, discussion of multi-segment PWs: The statement that
S-PE's<br>
&gt; &gt; SHOULD<br>
&gt; &gt; &gt; assume an initial passive role seems to have several problems:<br>
&gt; &gt; &gt; - Does this mean that changing the configuration of an S-PE
would<br>
&gt; &gt; not<br>
&gt; &gt; &gt; provoke the new mechanisms?<br>
&gt; &gt; &gt; - The passive role situation is only specified for some
sorts of<br>
&gt; &gt; linked<br>
&gt; &gt; &gt; FECs in RFC 6073 - what about other cases?<br>
&gt; &gt; &gt; - What are the consequences for ignoring the SHOULD in this
case? (I<br>
&gt; &gt; &gt; have to say I am unsure that RFC 6073 deals with this problem<br>
&gt; &gt; either.) <br>
&gt; &gt; [Lizhong] we follow RFC6073, and passive role is only applied
for the<br>
&gt; &gt; PW FEC, other cases are out of scope. <br>
&gt; Why? This needs an explanation. Also this doesn't cover the point
about<br>
&gt; whether reconfig of an S-PE is allowed and how this squares with the<br>
&gt; passive role.<br>
&gt; &gt; SHOULD means highly recommended. We do not meet any problem when<br>
&gt; &gt; implementing RFC6073. Do you suggest to change this to MUST?
<br>
&gt; Whenever a specification includes a 'SHOULD' the question arises of
what<br>
&gt; alternatives there might be and what is the reason for preferring
the<br>
&gt; suggested solution. &nbsp;In the original setup, it is fairly clear
that life<br>
&gt; is easier letting setup progress from &nbsp;one end to the other (although<br>
&gt; this is not spelt out - I would have argued for this had &nbsp;I reviewed
the<br>
&gt; doc). &nbsp;For the configuration change this is less obvious. &nbsp;Regarding
the<br>
&gt; point about reconfig of the &nbsp;S-PE, it is going to make life more<br>
&gt; complicated if the S-PE has to tell the T-PE to be active so it can
be<br>
&gt; passive. &nbsp;I would therefore argue that probably the notion of
passivity<br>
&gt; is irrelevant to the transition use case. &nbsp;Whether it should
be SHOULD<br>
&gt; or MUST is therefore moot.</tt></font>
<br><font size=2><tt>[Lizhong] how about the following? Because we just
refer to RFC6073, and does not add anything new.</tt></font>
<br><font size=2><tt>An initial passive role is defined in [RFC6073] for
S-PE.</tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Nits/editorial comments: <br>
&gt; &gt; &gt; General: In RFC 4447, the label message names use title
case (e.g.,<br>
&gt; &gt; &gt; Label Mapping). &nbsp;For consistency this should be followed
throughout<br>
&gt; &gt; this<br>
&gt; &gt; &gt; document. <br>
&gt; &gt; [Lizhong] yes, and thank you and Adrian.<br>
&gt; &gt; &gt; &nbsp;<br>
&gt; &gt; &gt; Abstract: &nbsp;Should not contain references. &nbsp;Best
to give full title<br>
&gt; &gt; of<br>
&gt; &gt; &gt; RFC and number in round brackets. <br>
&gt; &gt; [Lizhong] I removed brackets and do not intend to contain citations<br>
&gt; &gt; here. It seems the citations are generated automatically by IETF.<br>
&gt; &gt; Could the round brackets solve this? Or are you referring v-03?
<br>
&gt; (leftover from 03)<br>
&gt; &gt; <br>
&gt; &gt; &gt; Abstract: s/problem of control/ the problem with control/
(if there<br>
&gt; &gt; is<br>
&gt; &gt; &gt; just one) <br>
&gt; &gt; [Lizhong] are you reviewing v-03 of the draft? In v-04, the abstract<br>
&gt; &gt; has been revised in v-04.<br>
&gt; (leftover from 03)<br>
&gt; &gt; &nbsp;<br>
&gt; &gt; <br>
&gt; &gt; &gt; Abstract: The second two sentences say the same thing in
different<br>
&gt; &gt; ways <br>
&gt; &gt; &gt; OLD<br>
&gt; &gt; &gt; &nbsp; &nbsp;Based on the problem analysis, a<br>
&gt; &gt; &gt; &nbsp; &nbsp;message exchanging mechanism is introduced
to solve this control<br>
&gt; &gt; word<br>
&gt; &gt; &gt; &nbsp; &nbsp;negotiation issue. &nbsp;This document is to
update [RFC4447] control<br>
&gt; &gt; word<br>
&gt; &gt; &gt; &nbsp; &nbsp;negotiation mechanism.<br>
&gt; &gt; &gt; NEW<br>
&gt; &gt; &gt; Based on the problem analysis, this document introduces
a modified <br>
&gt; &gt; &gt; message exchange <br>
&gt; &gt; &gt; sequence updating the control word negotiation mechanism
in RFC<br>
&gt; &gt; 4447.<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; This issue also applies to s1. <br>
&gt; &gt; [Lizhong] are you reviewing v-03 of the draft? In v-04, the abstract<br>
&gt; &gt; has been revised in v-04.<br>
&gt; (leftover from 03)<br>
&gt; &gt; &nbsp;<br>
&gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s1: Subtle distinction - this is a practical problem with
the <br>
&gt; &gt; &gt; mechanism defined in RFC 4447 rather <br>
&gt; &gt; &gt; than the abstract problem of how to do control word negotiation:<br>
&gt; &gt; &gt; &nbsp;s/the problem of control word negotiation/problems
identified in <br>
&gt; &gt; &gt; the control word negotiation/ <br>
&gt; &gt; [Lizhong] has been revised in v-04.<br>
&gt; &gt; &gt; <br>
&gt; yes.<br>
&gt; &gt; &gt; s1: Expand acronym PW. <br>
&gt; &gt; [Lizhong] has been revised in v-04.<br>
&gt; Not as far as I can see.</tt></font>
<br><font size=2><tt>[Lizhong] write &quot;pseudowire&quot; directly in
the text, not PW.</tt></font>
<br><font size=2><tt><br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s2: Expand acronym PE. <br>
&gt; &gt; [Lizhong] accept <br>
&gt; &gt; <br>
&gt; &gt; &gt; s2, 2nd sentence: s/configurable/configured/ <br>
&gt; &gt; [Lizhong] configurable is right. <br>
&gt; Leave that one to the RFc Editor.<br>
&gt; &gt; <br>
&gt; &gt; &gt; s2, 3rd and 4th sentences: I *think* this text is trying
to say: <br>
&gt; &gt; &gt; &nbsp; The intention of the control word negotiation is
that the control<br>
&gt; &gt; word<br>
&gt; &gt; &gt; will be used when both endpoints are configured with control
word<br>
&gt; &gt; usage<br>
&gt; &gt; &gt; PREFERRED. &nbsp;However if one endpoint is initially configured
with<br>
&gt; &gt; control<br>
&gt; &gt; &gt; word usage NOT PREFERRED but later changes to PREFERRED,
a PW<br>
&gt; &gt; between<br>
&gt; &gt; &gt; the endpoints will not transition to usage of the control
word as<br>
&gt; &gt; &gt; explained below. <br>
&gt; &gt; [Lizhong] no, the case is that operator deploys PW with control
word<br>
&gt; &gt; used in the first phase. In the second phase, they want to upgrade<br>
&gt; &gt; their PW service to use control word. Two different deployment<br>
&gt; &gt; timeframes.<br>
&gt; That is what my sentence says.</tt></font>
<br><font size=2><tt>[Lizhong] ok.</tt></font>
<br><font size=2><tt><br>
&gt; &gt; &nbsp;<br>
&gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s2, bullet #2: s/PE1 send label mapping with C bit=0<br>
&gt; &gt; finally./ultimately<br>
&gt; &gt; &gt; PE1 sends a Label Mapping message with the C bit set to
0./ <br>
&gt; &gt; [Lizhong] accept<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s2, bullet #4: s/send label withdraw/send a Label Withdraw/
<br>
&gt; &gt; [Lizhong] accept<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s2, bullet #5: s/the received/the previously received/,
<br>
&gt; &gt; &gt; s/indicates C bit=0/carried the C bit set to 0/, <br>
&gt; &gt; &gt; s/send label mapping with C bit=0/send a label mapping message
with<br>
&gt; &gt; the<br>
&gt; &gt; &gt; C bit set to 0/ <br>
&gt; &gt; [Lizhong] accept<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3: It would be much clearer if s3 was divided into 3 sub-sections<br>
&gt; &gt; &gt; (possibly reordered):<br>
&gt; &gt; &gt; - PREFERRED to NOT PREFERRED transition<br>
&gt; &gt; &gt; - NOT PREFERRED to PREFERRED transition<br>
&gt; &gt; &gt; - Multi-segment case (which should refer to both previous
cases)<br>
&gt; &gt; &gt; The pointer to the diagram in Appendix A could usefully
occur in the<br>
&gt; &gt; &gt; introduction to s3. &nbsp;If this was adopted s3.1 could
either be a<br>
&gt; &gt; fourth<br>
&gt; &gt; &gt; sub-section or a sub-sub-section of the PREFERRED to NOT
PREFERRED<br>
&gt; &gt; &gt; section. <br>
&gt; &gt; [Lizhong] PREFERRED to NOT PREFERRED does not introduce any new.<br>
&gt; &gt; Multi-segment case is fully inherited from single-segment case.
It<br>
&gt; &gt; would be redundancy to have sub-sections here. <br>
&gt; I disagree strongly. &nbsp;The multi-segment case affects the other
RFC and<br>
&gt; needs to be made to stand out so that implementors can see where the<br>
&gt; changes occur. &nbsp;The PREFERRED to NOT PREFERRED case also ought
to be<br>
&gt; separated whether or not I am right about this case. </tt></font>
<br><font size=2><tt>[Lizhong] how about only divide multi-segment? The
case of PREFERRED to NOT PREFERRED case is only for reference, and the
text is not many.<br>
&gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3, Various acronyms need expanding: FEC, T-PE, S-PE <br>
&gt; &gt; [Lizhong] accept<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3, para 1: s/adding label request/adding a new label request/
<br>
&gt; &gt; [Lizhong] much difference here?<br>
&gt; Yes. How it reads in English. &nbsp;There are many missing definite
articles<br>
&gt; and indefinite articles that make the text read very badly for a native<br>
&gt; English speaker. &nbsp;I understand that this is a very difficult
aspect for<br>
&gt; someone who has a first language that does not employ articles in
the<br>
&gt; way that English does.</tt></font>
<br><font size=2><tt>[Lizhong] ok<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3 bullets '-i' to '-iii': s/Local PE/The local PE/, s/remote
PR/the<br>
&gt; &gt; &gt; remote peer PE/. &nbsp;Also a more usual labeling of the
bullets would be<br>
&gt; &gt; &gt; appropriate (e.g., just i, ii and iii). <br>
&gt; &gt; [Lizhong] accept, and I do not see &quot;remote PR&quot;.<br>
&gt; should have been 'remote PE'.</tt></font>
<br><font size=2><tt>[Lizhong] ok<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3, para 2: s/When Local/When the local/,<br>
&gt; &gt; &gt; s/the remote label mapping message with C bit=0, additional<br>
&gt; &gt; procedure<br>
&gt; &gt; &gt; will be added as follow:/a label mapping message from the
PW peer<br>
&gt; &gt; with<br>
&gt; &gt; &gt; the C bits set to 0, the following additional procedure
will be<br>
&gt; &gt; acrried<br>
&gt; &gt; &gt; out:/ <br>
&gt; &gt; [Lizhong] accept<br>
&gt; &gt; &gt; &nbsp;<br>
&gt; &gt; &gt; s3, bullet '-i': s/wait until receiving a label release/wait
until<br>
&gt; &gt; it<br>
&gt; &gt; &gt; has received a Label Release message/ (but general clarification
and<br>
&gt; &gt; &gt; rewording needed - see issues section above). <br>
&gt; &gt; [Lizhong] do not see much difference here. Of couse the &quot;label<br>
&gt; &gt; release&quot; should be capitalized.<br>
&gt; Your form implies that that the action can occur as soon as the message<br>
&gt; starts to be received (as in 'the radio is receiving a programme').<br>
&gt; This is not the case - the action can occur only when the whole message<br>
&gt; has been received. &nbsp;</tt></font>
<br><font size=2><tt>[Lizhong] ok, thanks.</tt></font>
<br><font size=2><tt><br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3, bullet '-ii':<br>
&gt; &gt; &gt; OLD:<br>
&gt; &gt; &gt; &nbsp; &nbsp; &nbsp; Local PE MUST send a label request
message to remote PE, and<br>
&gt; &gt; &gt; &nbsp; &nbsp; &nbsp; wait until receiving a label mapping
message containing the<br>
&gt; &gt; remote<br>
&gt; &gt; &gt; &nbsp; &nbsp; &nbsp; PE locally configured preference for
use of control word.<br>
&gt; &gt; &gt; NEW:<br>
&gt; &gt; &gt; &nbsp; &nbsp; &nbsp; The local PE MUST send a Label Mapping
message to the peer PE<br>
&gt; &gt; with the<br>
&gt; &gt; &gt; &nbsp; &nbsp; &nbsp; C bit set to 1, and then wait until
a Label Mapping message<br>
&gt; &gt; isreceived <br>
&gt; &gt; &gt; &nbsp; &nbsp; &nbsp; containing the peer's current configured
preference for usage<br>
&gt; &gt; of the <br>
&gt; &gt; &gt; &nbsp; &nbsp; &nbsp; control word. <br>
&gt; &gt; [Lizhong] no, the procedure here is not right. The local PE MUST
send<br>
&gt; &gt; a label request message, not label mapping.<br>
&gt; Try:<br>
&gt; The local PE MUST send a Label Request message to the peer PE &nbsp;and
then<br>
&gt; wait until a Label Mapping message is received containing the peer's<br>
&gt; current configured preference for usage of the control word. </tt></font>
<br><font size=2><tt>[Lizhong] ok</tt></font>
<br><font size=2><tt><br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3, para sfter item '-iii': s/successfully/has successfully/
<br>
&gt; &gt; [Lizhong] accept <br>
&gt; &gt; <br>
&gt; &gt; &gt; The following implies that there is memory of previous action<br>
&gt; &gt; although<br>
&gt; &gt; &gt; the label binding has been destroyed. Better would be:<br>
&gt; &gt; &gt; OLD:<br>
&gt; &gt; &gt; &gt; &nbsp; &nbsp;...and removed the remote label binding,
it MUST reset<br>
&gt; &gt; &gt; &gt; &nbsp; &nbsp;its use of control word with the locally
configured preference,<br>
&gt; &gt; and<br>
&gt; &gt; &gt; &gt; &nbsp; &nbsp;send label mapping as a response of label
request with locally<br>
&gt; &gt; &gt; &gt; &nbsp; &nbsp;configured preference for use of control
word.<br>
&gt; &gt; &gt; NEW:<br>
&gt; &gt; &gt; ...and removed the remote label binding, subsequent Label
Requests<br>
&gt; &gt; will<br>
&gt; &gt; &gt; naturally be treated as new requests and processed as described
in<br>
&gt; &gt; &gt; Section 6 of RFC 4447. <br>
&gt; &gt; [Lizhong] we got similar comments from Adrian, and will update
this. <br>
&gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3, discussion of multi-segment PWs: s/case for T-PE is
same./case<br>
&gt; &gt; for a<br>
&gt; &gt; &gt; T-PE operates similarly./ <br>
&gt; &gt; [Lizhong] accept<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3, last para/Appendix A: &nbsp;The diagram doesn't cover
the PREFERRED<br>
&gt; &gt; to<br>
&gt; &gt; &gt; NOT PREFERRED transition. <br>
&gt; &gt; [Lizhong] no, there is a &quot;no&quot; branch under &quot;NOT
Preferred to<br>
&gt; &gt; Preferred&quot; to cover &quot;PREFERRED to NOT PREFERRED&quot;.
Anyway, the diagram<br>
&gt; &gt; discription should be &quot;NOT Preferred to Preferred&quot;
which is wrong in<br>
&gt; &gt; v-04. <br>
&gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; s3.1: The wording in this section is generally &nbsp;rather
'loose'. &nbsp;A<br>
&gt; &gt; more<br>
&gt; &gt; &gt; formal style would be helpful. <br>
&gt; &gt; [Lizhong] this is a usecase to give an example, so we make it
&quot;loose&quot;.<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; <br>
&gt; <br>
</tt></font>
--=_alternative 005F0A0048257A22_=--


From d3e3e3@gmail.com  Tue Jun 19 11:19:05 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAD1111E811A for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 11:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.453
X-Spam-Level: 
X-Spam-Status: No, score=-103.453 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iv+ms2AE9bD4 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 11:19:05 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id CDF7911E810E for <gen-art@ietf.org>; Tue, 19 Jun 2012 11:19:04 -0700 (PDT)
Received: by yenq13 with SMTP id q13so5565512yen.31 for <gen-art@ietf.org>; Tue, 19 Jun 2012 11:19:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=7O3yoj061pxpp/lXiJTTOvmJwBR4b7CWG2Rs0EG9Q2c=; b=Xx4fwRh3rGpxU1mw3fE3caDRstdB7rnDPw0q7yiXtTM6VtoxKEwBaWkqHZY1jo8f67 KqgXGD/vMicvOpEwCMu7g68P7Juf3aIvczoNco/4AT4pxAZybJZxMdcSvqgKtXpcbq39 f90xSJUV3l+E03sgCVW8LsRs+OgTuG7/+GSP+Hlb4EW66FueabqVa4rcDkNaCpPF60/4 Mmyr0fRDh84lwy/XTB+gHZx7ZrkNtDDQg3Y+lEyRjOvw7wca2sbQRXJLwDRK5MYEGS+f exsI9QZN8PCyK8OPY6istVR4DBwjXnoa5GVgAJXd4MS55/4XM4P1BAm7Pq8KYqUGIIHt 0dHw==
Received: by 10.50.236.97 with SMTP id ut1mr2216959igc.50.1340129943778; Tue, 19 Jun 2012 11:19:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.16.227 with HTTP; Tue, 19 Jun 2012 11:18:43 -0700 (PDT)
In-Reply-To: <25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7@EUSAACMS0703.eamcs.ericsson.se>
References: <25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7@EUSAACMS0703.eamcs.ericsson.se>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 19 Jun 2012 14:18:43 -0400
Message-ID: <CAF4+nEH3XmK=b0nN8Pcozc_6LB2vxajJ6OM4t7VvZ1Q-Fx13hQ@mail.gmail.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-trill-clear-correct.all@tools.ietf.org" <draft-ietf-trill-clear-correct.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-trill-clear-correct-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 18:19:06 -0000

Hi Meral,

Thanks for your review. See below:

On Tue, Jun 19, 2012 at 11:51 AM, Meral Shirazipour
<meral.shirazipour@ericsson.com> wrote:
> I am the assigned Gen-ART reviewer for
> draft-ietf-trill-clear-correct-03.txt. For background on Gen-ART, please =
see
> the FAQ at <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.
>
> Please resolve these comments along with any other Last Call comments you
> may receive.
>
>
> Document: draft-ietf-trill-clear-correct-03
> Reviewer: Meral Shirazipour
> Review Date: June-18-2012
> IETF LC End Date: June-20-2012
> IESG Telechat date: June-21-2012
>
>
> Summary:
> The document is ready for publication as a standards track RFC, however I
> have a few comments.
>
>
>
> Minor issues:
>
> TRILL-PORT-VER sub-TLV should be "PORT-TRILL-VER" sub-TLV.(there are a fe=
w
> occurrences)



>
> Nits/editorial comments:
>
> - Suggestion: [Page 6], line 2, spell out first occurrence LSP
>
>
>
> - Suggestion: [Page 6], line 5, "overload bit on" ----> "overload bit set=
"
>
>
>
> - Clarification:[Page 6], Section 2.1, line 5, add a comma "," after
> "traffic engineered frames"
>
>
>
> - Typo:[Page 6], last word, "contain" --missing s--> "contains"
>
>
>
> - Suggestion: [Page 7], Section 2.2, line 2, spell out first occurrence o=
f
> "Reverse Path Forwarding Check" and then use "RPFC" in the rest of the
> document.
>
>
>
> - Clarification:[Page 10], Section 2.4.2.3, line 5, sentence starting wit=
h
> "RB2 MUST advertise ...": we could omit the second occurrence of "it migh=
t
> use" in that sentence.
>
>
>
> - Clarification:[Page 10], Section 2.4.2.3, 3rd line from last, "end
> stations connected to RB": "a RB" or "RBs"?
>
>
>
> - Typo: [Page 11], Section 3.1,"( j, k)" --remove extra space--> "(j, k)"
>
>
>
> - Suggestion: [Page 11], Section 3.2, "already in flight" ----> "already =
in
> transmission"
>
>
>
> - Typo [Page 12]:"many multi-destination frame"--missing s--> "many
> multi-destination frames"
>
>
>
> - Clarification:[Page 13], Point 4. , Sentence 2: suggested clarification=
:
>
> "It does so by checking LSPs it receives and updating its link state
> database for any of its nicknames held with higher priority by another TR=
ILL
> Switch that is IS-IS reachable."
>
>
>
> - Typo [Page 14]:"unicast Channel message"--missing s-->"unicast Channel
> messages"
>
>
>
> - Typo [Page 16]: Section 5.2,"Routeing" ----> "Routing"
>
>
>
> - Suggestion:[Page 16],last sentence, suggestion: "This safety margin is
> called "Margin" below."
>
>
>
> - Typo [Page 18]:"a specified in [RFC6325]"--missing s-->"as specified in
> [RFC6325]"
>
>
>
> - Suggestion: [Page 19], spell out first occurrence of EISS
>
>
>
> - Suggestion:[Page 21], Point 1, not clear what the new text becomes.
> Suggestion: refer to last paragraph of section 3.1 instead of paragraph
> before 3.2, and propose the new sentence.
>
>
>
> - Clarification:[Page 21], Point 2, it is not clear what the change is to
> section 3.2 of RFC6327.
>
>
>
> - Clarification:[Page 21], Point 3, it would be clearer to say "bullet A9=
 is
> added" (if this is an event like the rest of the bullets in section 3.3 o=
f
> RFC6327)
>
>
>
> - Clarification:[Page 22], section 10.1,"disagreement over the Designated
> VLAN or the like". Suggestion: replace the term "or the like" with other
> examples or remove the term.
>
>
>
> -Typo: [Page 22], section 10.1, "each others frames"---->"each other's
> frames"
>
>
>
> -Typo: [Page 24], "DRB SHOULD NOT appointed"---->"DRB SHOULD NOT appoint"=
,
> "an VLAN"---->"a VLAN", "RBridged"---->"RBridge"
>
>
>
> -Clarification:[Page 25], Section 11, Point 1, "The previously reserved",
> reference to document.
>
>
>
> - Clarification: [page 19/page 27], Informative References, reference [80=
2],
> to verify which standard we want to refer to for Canonical Format Indicat=
or:
>
> If it is "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan Are=
a
> Networks: Overview and Architecture", then the date should be 7 February
> 2001."
>
> However this specific document does not define CIF. You may want to refer=
 to
> 802.1Q-2005.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

> Thanks,
> Meral
>
>
> ---
> Meral Shirazipour
> Ericsson
> Research
> www.ericsson.com

From d3e3e3@gmail.com  Tue Jun 19 11:20:26 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1010911E811F for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 11:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.462
X-Spam-Level: 
X-Spam-Status: No, score=-103.462 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id doHUYXxh2Rv8 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 11:20:25 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id E7AF711E8121 for <gen-art@ietf.org>; Tue, 19 Jun 2012 11:20:24 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so5446541ghb.31 for <gen-art@ietf.org>; Tue, 19 Jun 2012 11:20:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=tzlewXsaTrICyjC7FBxVuxYQIoPyRSiS0oX6fxh/fqM=; b=ZhFPhhXRFyvhQViSFjPaXk6XNie1iT7SisUn0W/3oc3Nppi/c0AJD86v1k3YNVrFBM nAHIbYP04jcIvb1jSn8a8MZwM4unEYCNXJywWCFbZpL1iy/1VKsxRcb8jV81Y15kDVzE TNVmyF3PqlQgRYagJXdDryy0l3wHuZUodjbet60zofPiZKBZbee8v3LswUeihli9lvXa JQfycjzlY3wwjEUW8FZUrnxYTxDJq36PfF2yQ12hEju2MyIQv9OaBLnWyG9BJY2JjCnv 7sQTxDS8FkJxC4nVrElBKdyblvzbxRJtiHIxUWY3X7++8GMnuywr7yvNi3AVJWSSFmu7 C96Q==
Received: by 10.50.196.232 with SMTP id ip8mr2221921igc.50.1340130023996; Tue, 19 Jun 2012 11:20:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.16.227 with HTTP; Tue, 19 Jun 2012 11:20:03 -0700 (PDT)
In-Reply-To: <CAF4+nEH3XmK=b0nN8Pcozc_6LB2vxajJ6OM4t7VvZ1Q-Fx13hQ@mail.gmail.com>
References: <25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7@EUSAACMS0703.eamcs.ericsson.se> <CAF4+nEH3XmK=b0nN8Pcozc_6LB2vxajJ6OM4t7VvZ1Q-Fx13hQ@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 19 Jun 2012 14:20:03 -0400
Message-ID: <CAF4+nEGs9sjB6TaSxOtSgq9XndReZtAPfu8P8p+bWOzPq=4qiQ@mail.gmail.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-trill-clear-correct.all@tools.ietf.org" <draft-ietf-trill-clear-correct.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-trill-clear-correct-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 18:20:26 -0000

Sorry, ignore below, hit send by mistake....

On Tue, Jun 19, 2012 at 2:18 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> Hi Meral,
>
> Thanks for your review. See below:
>
> On Tue, Jun 19, 2012 at 11:51 AM, Meral Shirazipour
> <meral.shirazipour@ericsson.com> wrote:
>> I am the assigned Gen-ART reviewer for
>> draft-ietf-trill-clear-correct-03.txt. For background on Gen-ART, please=
 see
>> the FAQ at <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.
>>
>> Please resolve these comments along with any other Last Call comments yo=
u
>> may receive.
>>
>>
>> Document: draft-ietf-trill-clear-correct-03
>> Reviewer: Meral Shirazipour
>> Review Date: June-18-2012
>> IETF LC End Date: June-20-2012
>> IESG Telechat date: June-21-2012
>>
>>
>> Summary:
>> The document is ready for publication as a standards track RFC, however =
I
>> have a few comments.
>>
>>
>>
>> Minor issues:
>>
>> TRILL-PORT-VER sub-TLV should be "PORT-TRILL-VER" sub-TLV.(there are a f=
ew
>> occurrences)
>
>
>
>>
>> Nits/editorial comments:
>>
>> - Suggestion: [Page 6], line 2, spell out first occurrence LSP
>>
>>
>>
>> - Suggestion: [Page 6], line 5, "overload bit on" ----> "overload bit se=
t"
>>
>>
>>
>> - Clarification:[Page 6], Section 2.1, line 5, add a comma "," after
>> "traffic engineered frames"
>>
>>
>>
>> - Typo:[Page 6], last word, "contain" --missing s--> "contains"
>>
>>
>>
>> - Suggestion: [Page 7], Section 2.2, line 2, spell out first occurrence =
of
>> "Reverse Path Forwarding Check" and then use "RPFC" in the rest of the
>> document.
>>
>>
>>
>> - Clarification:[Page 10], Section 2.4.2.3, line 5, sentence starting wi=
th
>> "RB2 MUST advertise ...": we could omit the second occurrence of "it mig=
ht
>> use" in that sentence.
>>
>>
>>
>> - Clarification:[Page 10], Section 2.4.2.3, 3rd line from last, "end
>> stations connected to RB": "a RB" or "RBs"?
>>
>>
>>
>> - Typo: [Page 11], Section 3.1,"( j, k)" --remove extra space--> "(j, k)=
"
>>
>>
>>
>> - Suggestion: [Page 11], Section 3.2, "already in flight" ----> "already=
 in
>> transmission"
>>
>>
>>
>> - Typo [Page 12]:"many multi-destination frame"--missing s--> "many
>> multi-destination frames"
>>
>>
>>
>> - Clarification:[Page 13], Point 4. , Sentence 2: suggested clarificatio=
n:
>>
>> "It does so by checking LSPs it receives and updating its link state
>> database for any of its nicknames held with higher priority by another T=
RILL
>> Switch that is IS-IS reachable."
>>
>>
>>
>> - Typo [Page 14]:"unicast Channel message"--missing s-->"unicast Channel
>> messages"
>>
>>
>>
>> - Typo [Page 16]: Section 5.2,"Routeing" ----> "Routing"
>>
>>
>>
>> - Suggestion:[Page 16],last sentence, suggestion: "This safety margin is
>> called "Margin" below."
>>
>>
>>
>> - Typo [Page 18]:"a specified in [RFC6325]"--missing s-->"as specified i=
n
>> [RFC6325]"
>>
>>
>>
>> - Suggestion: [Page 19], spell out first occurrence of EISS
>>
>>
>>
>> - Suggestion:[Page 21], Point 1, not clear what the new text becomes.
>> Suggestion: refer to last paragraph of section 3.1 instead of paragraph
>> before 3.2, and propose the new sentence.
>>
>>
>>
>> - Clarification:[Page 21], Point 2, it is not clear what the change is t=
o
>> section 3.2 of RFC6327.
>>
>>
>>
>> - Clarification:[Page 21], Point 3, it would be clearer to say "bullet A=
9 is
>> added" (if this is an event like the rest of the bullets in section 3.3 =
of
>> RFC6327)
>>
>>
>>
>> - Clarification:[Page 22], section 10.1,"disagreement over the Designate=
d
>> VLAN or the like". Suggestion: replace the term "or the like" with other
>> examples or remove the term.
>>
>>
>>
>> -Typo: [Page 22], section 10.1, "each others frames"---->"each other's
>> frames"
>>
>>
>>
>> -Typo: [Page 24], "DRB SHOULD NOT appointed"---->"DRB SHOULD NOT appoint=
",
>> "an VLAN"---->"a VLAN", "RBridged"---->"RBridge"
>>
>>
>>
>> -Clarification:[Page 25], Section 11, Point 1, "The previously reserved"=
,
>> reference to document.
>>
>>
>>
>> - Clarification: [page 19/page 27], Informative References, reference [8=
02],
>> to verify which standard we want to refer to for Canonical Format Indica=
tor:
>>
>> If it is "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan Ar=
ea
>> Networks: Overview and Architecture", then the date should be 7 February
>> 2001."
>>
>> However this specific document does not define CIF. You may want to refe=
r to
>> 802.1Q-2005.
>
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> =A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
> =A0155 Beaver Street,=A0Milford, MA 01757 USA
> =A0d3e3e3@gmail.com
>
>> Thanks,
>> Meral
>>
>>
>> ---
>> Meral Shirazipour
>> Ericsson
>> Research
>> www.ericsson.com

From wassim.haddad@ericsson.com  Tue Jun 19 11:44:34 2012
Return-Path: <wassim.haddad@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A72AD11E8142 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 11:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LiDpj909LIMS for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 11:44:34 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1B03D11E813D for <gen-art@ietf.org>; Tue, 19 Jun 2012 11:44:34 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q5JIiW58020619; Tue, 19 Jun 2012 13:44:33 -0500
Received: from [147.117.67.72] (147.117.20.214) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.3.264.0; Tue, 19 Jun 2012 14:44:25 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Jun 2012 14:44:53 -0400
Message-ID: <A4CC8CCA-8B2A-4E82-BF83-4B1A718329A5@ericsson.com>
To: Gen-art <gen-art@ietf.org>
MIME-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Cc: draft-ietf-cdni-problem-statement.all@tools.ietf.org
Subject: [Gen-art]  Gen-ART review of draft-ietf-cdni-problem-statement-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 18:44:34 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at =
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq.

Please resolve these comments along with any other comments you may =
receive.

Document:  draft-ietf-cdni-problem-statement-06
Reviewer: Wassim Haddad
Review Date: 2012-06-19
IETF LC End Date: 2012-06-06
IESG Telechat date: 2012-06-21

Summary: This draft is ready for publication as informational standard =
but one (helpful) addition is suggested.

Major issues: None

Minor issues:=20

- Sectiom 1.1: suggest defining "Quality of Experience" (mentioned 4 =
times in the document)


Regards,

Wassim H.


From mccap@petoni.org  Tue Jun 19 17:08:33 2012
Return-Path: <mccap@petoni.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCA5211E80F6 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 17:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DJZ+ND-AyCNM for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 17:08:33 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3ACD711E80A0 for <gen-art@ietf.org>; Tue, 19 Jun 2012 17:08:33 -0700 (PDT)
Received: by dacx6 with SMTP id x6so9179329dac.31 for <gen-art@ietf.org>; Tue, 19 Jun 2012 17:08:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=Yl8U37D13j0eaSGMTSBNc5RylvCaAKpncdmPk72BPUM=; b=SlHRL6AdkDvZnq4a74wZyLNLpOQK6OJWT3FHXld1hBxspmA1S+Fmj+gF0kPvMSd6kE OBC+hWwCC/iiUBSZyQJmBwpz9Gqp017VThLYJqb1DheDBMgnSmLXvX0EDAXp4+fsqlB2 zAqLczLIO7mgoALxNXZ280mled2+v0HB9Ao5c=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=Yl8U37D13j0eaSGMTSBNc5RylvCaAKpncdmPk72BPUM=; b=UuCTDVqyjHAOWZ+nw/vl3wOGb4QIvNfBNnKQ5aNNWf9Bgk4Kj5AtMotoDJf7H3Apso lpv1Q96ucNkRnj+33q0ypm9Z6di2MGOUtu8oIotMBMgalemERyDh1xFpeOQTeYClOfL9 ETJsdfP126I/FJYVzQclGOIw+y/GlRYJa72LURHAcQT4I862eX57W0gj4y7BNcZOZCBg i+FDO3qrjLIdBUjTIRblc9s+EUFpeWqLC9+RNdKXhGpm5/0Pj0A6lWaWzWRzNzajoTpN sUr4I0SRHnc7oFWz++4oq7sKMKRSWNo8iTRiFODJivhaSia2DgxPtBK4SfzXQOnes9pq VU5A==
MIME-Version: 1.0
Received: by 10.68.191.201 with SMTP id ha9mr70292047pbc.75.1340150912967; Tue, 19 Jun 2012 17:08:32 -0700 (PDT)
Received: by 10.68.213.99 with HTTP; Tue, 19 Jun 2012 17:08:32 -0700 (PDT)
X-Originating-IP: [68.45.157.93]
Date: Tue, 19 Jun 2012 20:08:32 -0400
Message-ID: <CACvMsLHQKYm41iw85cJzoF1rOs6DXW7jhJH9L9Tdy5cD3UjjMw@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-pim-pop-count.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlBqY2BR8s6sABJTt4f1q+W8IRALgRUpJlmpgls3v2rE7A/DC9zN8DFYY3jAMhzyYbGG0bF
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-pim-pop-count-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 00:08:34 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-pim-pop-count-06
Reviewer: Peter McCann
Review Date: 2012-06-19
IETF LC End Date: 2012-06-12
IESG Telechat date: 2012-06-21

Summary: 2 minor issues

Major issues: none

Minor issues:

The Transit and Stub oif-List counts are only 2 octets.  Will these
fields be large enough to contain
the totals for a large multicast distribution tree?

Are there any alignment constraints on the options?  It looks like all
the two-octet options come first
and the single-octet options come last.  However, is this a
requirement for any future options that may
be defined?


Nits/editorial comments:

The descriptions of how the counts are maintained could use a little
clarification.  For example,
when you say:

   Transit Oif-List Count:   This is filled in by a router sending a
      Join/Prune message which is equal to the number of oifs (outgoing
      interfaces) for the multicast route that has been joined by PIM.
      This indicates the transit branches on a multicast distribution
      tree (no members on the links between this router and joining
      routers).  This is added to the value advertised by all downstream
      PIM routers that have joined on this oif.  Length 2 octets.

it isn't clear what you mean by "which is equal to". Literally, you
are saying the Join/Prune message
is equal to something.  I don't think that's quite right.  Did you
mean "with a number that is equal to"?
Maybe, "with a number that is equal to the number of oifs (outgoing
interfaces) for the multicast
route that has been joined by PIM, plus the values advertised by all
downstream PIM routers that
have joined this oif."



-Pete

From lwei@cisco.com  Tue Jun 19 18:05:56 2012
Return-Path: <lwei@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC0D11E8121 for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 18:05:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bDzxG6FXM9RC for <gen-art@ietfa.amsl.com>; Tue, 19 Jun 2012 18:05:56 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id F2E5811E8117 for <gen-art@ietf.org>; Tue, 19 Jun 2012 18:05:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lwei@cisco.com; l=2525; q=dns/txt; s=iport; t=1340154355; x=1341363955; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=iB3chPjbItwN/texCcSs/hEQCRP0sJOEnKYgerw+kMI=; b=AonhXfsAj8yC1+Ed2z/SqoCGaV/58U1UtE0LMnm9n8V1+B4yKr/afGHd lBThiga+Fh9Pg0kZSnD6tweLy8VBT7jcR5aPGSk2Cd3xJa+Si3+mgRKom crArrq0mHamGhyc7gGTKGqRdwQTdtUkvODtekHEeESonCDL4rk7M9z00E M=;
X-IronPort-AV: E=Sophos;i="4.77,439,1336348800"; d="scan'208";a="46442159"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 20 Jun 2012 01:05:55 +0000
Received: from lwei-mac.local ([10.155.34.217]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q5K15tLU019458; Wed, 20 Jun 2012 01:05:55 GMT
Message-ID: <4FE12294.4000008@cisco.com>
Date: Tue, 19 Jun 2012 18:08:36 -0700
From: Liming Wei <lwei@cisco.com>
Organization: cisco systems Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
References: <4FD59EA1.9030008@ericsson.com>
In-Reply-To: <4FD59EA1.9030008@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 19 Jun 2012 18:14:15 -0700
Cc: "draft-ietf-pim-ecmp.authors@tools.ietf.org" <draft-ietf-pim-ecmp.authors@tools.ietf.org>, Adrian Farrel <adrian@olddog.co.uk>, "mmcbride7@gmail.com" <mmcbride7@gmail.com>, General Area Review Team <gen-art@ietf.org>, "pim-chairs@tools.ietf.org" <pim-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pim-ecmp-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 01:05:56 -0000

Hi Miguel,

Response to your comments inline..

On 6/11/12 12:30 AM, Miguel A. Garcia wrote:
> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft. For background on Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>
> Please resolve these comments along with any other comments you may receive.
>
> Document: draft-ietf-pim-ecmp-03.txt
> Reviewer: Miguel Garcia<Miguel.A.Garcia@ericsson.com>
> Review Date: 2012-06-11
> IETF LC End Date: 2012-06-12
> IESG Telechat date: 2012-06-21
>
> Summary: The document is ready for publication as a standards track RFC.
>
> Major issues: none
>
> Minor issues: none
>
> Nits/editorial comments:
>
> - The Abstract should not include references. Just delete "[RFC4601]".

Will remove "[RFC4601]".

>
> - Perhaps this is a matter of personal taste... but Section 3.5.2 is
> devoted to describe the format of the PIM ECMP Redirect message. I think
> this is a section where you should describe the format, but you shouldn't
> write normative statements as for what to do with those fields. For
> example, I am referring to statements like:
>
>         Address of desired upstream
>         neighbor where the downstream receiver SHOULD redirect PIM
>         Joins
>
>         the receiving
>         router of this message MUST use the "Interface ID", instead of
>         "Neighbor Address", to identify the new RPF neighbor
>
>         an ECMP
>         Redirect message MUST be discarded if the "Interface ID" field...
>
> I think all these sentences including a normative MUST, SHOULD, etc.
> should be written in Sections 3.1. or 3.2 (Procedures). This means that
> the format (current section 3.5) should be moved to a place prior to 3.1
> and 3.2, because the procedures needs to explain what to do with all
> these fields.

Good point. Our original consideration was that when a protocol
implementer refers to the packet format and the fields,
it is more convenient for them to see that type of explanation
in the same place, as opposed to scattered in other parts of the spec.  
On the
other hand, doing what you suggested makes the spec look "cleaner", as the
format does not explain the protocol behavior, and the explanations occur in
places they are supposed to be explained.

So, we will move the explanation for the "Neighbor Address", and the 
"Interface
ID" to the end of section 3.1.

  Thanks,

-Liming Wei


/Miguel


From d3e3e3@gmail.com  Wed Jun 20 12:24:38 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE88621F86FA for <gen-art@ietfa.amsl.com>; Wed, 20 Jun 2012 12:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.491
X-Spam-Level: 
X-Spam-Status: No, score=-103.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sqkOSrtngifR for <gen-art@ietfa.amsl.com>; Wed, 20 Jun 2012 12:24:37 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 87E4321F85C5 for <gen-art@ietf.org>; Wed, 20 Jun 2012 12:24:37 -0700 (PDT)
Received: by yhq56 with SMTP id 56so6759330yhq.31 for <gen-art@ietf.org>; Wed, 20 Jun 2012 12:24:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=WQ2476ue7dLOZ/l/iytp0F7mmZvCxiRP1ELt/5dniHQ=; b=dsKpViUHf0nF4YZEkCUzefvwsCXqr43c5DzrPziE8hdp9cCHrwEAMCWLXWP42uYJ6F 530KPCI/YORWhsQS0sAsOw8sUMbJVFxhrAjI8Fr4sKXizqL31Ap9TM+Zgtrn6+SZhu5F JnA3YjUYMft0uIiOQ8iy1KRygw7IurZ1fv/14YQDRKT5JRtMSfzxX/m34xWMTY/TP50o iltT/tmGPX1ElXdOOi6R7ENidnjU1lOk1B+B5y87o5ICluVwqY5VQh18dQIYqJ2oAAy/ HHuYcZoghWzdaj4TSzfd20L9yPt77FDQEqPqfW48OOIvnsA9VQIayww5h9AnCWciFJqF zf7g==
Received: by 10.50.212.98 with SMTP id nj2mr5637882igc.35.1340220276830; Wed, 20 Jun 2012 12:24:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.16.227 with HTTP; Wed, 20 Jun 2012 12:24:16 -0700 (PDT)
In-Reply-To: <CAF4+nEH3XmK=b0nN8Pcozc_6LB2vxajJ6OM4t7VvZ1Q-Fx13hQ@mail.gmail.com>
References: <25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7@EUSAACMS0703.eamcs.ericsson.se> <CAF4+nEH3XmK=b0nN8Pcozc_6LB2vxajJ6OM4t7VvZ1Q-Fx13hQ@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 20 Jun 2012 15:24:16 -0400
Message-ID: <CAF4+nEEr7Ys4rZt7Ja97ygzy3bQwQ7J6ap2QW90rfi36Xv=X-w@mail.gmail.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-trill-clear-correct.all@tools.ietf.org" <draft-ietf-trill-clear-correct.all@tools.ietf.org>, Ayan Banerjee <ayabaner@gmail.com>
Subject: [Gen-art] Fwd: Gen-ART Last Call review of draft-ietf-trill-clear-correct-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 19:24:38 -0000

Hi Meral,

A real response this time...

Thanks for your thorough review. See below:

On Tue, Jun 19, 2012 at 11:51 AM, Meral Shirazipour
<meral.shirazipour@ericsson.com> wrote:
> I am the assigned Gen-ART reviewer for
> draft-ietf-trill-clear-correct-03.txt. For background on Gen-ART, please =
see
> the FAQ at <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.
>
> Please resolve these comments along with any other Last Call comments you
> may receive.
>
>
> Document: draft-ietf-trill-clear-correct-03
> Reviewer: Meral Shirazipour
> Review Date: June-18-2012
> IETF LC End Date: June-20-2012
> IESG Telechat date: June-21-2012
>
>
> Summary:
> The document is ready for publication as a standards track RFC, however I
> have a few comments.

Thanks.

> Minor issues:
>
> TRILL-PORT-VER sub-TLV should be "PORT-TRILL-VER" sub-TLV.(there are a fe=
w
> occurrences)

Yes, thanks for spotting that.

> Nits/editorial comments:
>
> - Suggestion: [Page 6], line 2, spell out first occurrence LSP

OK.

> - Suggestion: [Page 6], line 5, "overload bit on" ----> "overload bit set=
"

OK.

> - Clarification:[Page 6], Section 2.1, line 5, add a comma "," after
> "traffic engineered frames"

OK.

> - Typo:[Page 6], last word, "contain" --missing s--> "contains"

I believe the current wording is correct.

> - Suggestion: [Page 7], Section 2.2, line 2, spell out first occurrence o=
f
> "Reverse Path Forwarding Check" and then use "RPFC" in the rest of the
> document.

It depends a little on the context but  agree that most can be changed to R=
PFC.

> - Clarification:[Page 10], Section 2.4.2.3, line 5, sentence starting wit=
h
> "RB2 MUST advertise ...": we could omit the second occurrence of "it migh=
t
> use" in that sentence.

OK.

> - Clarification:[Page 10], Section 2.4.2.3, 3rd line from last, "end
> stations connected to RB": "a RB" or "RBs"?

Should be "end stations connected to RB3".

> - Typo: [Page 11], Section 3.1,"( j, k)" --remove extra space--> "(j, k)"

OK.

> - Suggestion: [Page 11], Section 3.2, "already in flight" ----> "already =
in
> transmission"

I think the current wording is better.

> - Typo [Page 12]:"many multi-destination frame"--missing s--> "many
> multi-destination frames"

OK.

> - Clarification:[Page 13], Point 4. , Sentence 2: suggested clarification=
:
>
> "It does so by checking LSPs it receives and updating its link state
> database for any of its nicknames held with higher priority by another TR=
ILL
> Switch that is IS-IS reachable."

I have no problem dropping "in" so it says "...checking LSPs..."
rather than "...checking in LSPs..." but I think the rest of the
change you suggest makes it slightly wrong and so would prefer to keep
the rest of the wording of that sentence.

> - Typo [Page 14]:"unicast Channel message"--missing s-->"unicast Channel
> messages"

OK.

> - Typo [Page 16]: Section 5.2,"Routeing" ----> "Routing"

The spelling used in the ISO 10589:2002 standard's title and the
naming of this field therein includes the "e".

> - Suggestion:[Page 16],last sentence, suggestion: "This safety margin is
> called "Margin" below."

OK.

> - Typo [Page 18]:"a specified in [RFC6325]"--missing s-->"as specified in
> [RFC6325]"

OK.

> - Suggestion: [Page 19], spell out first occurrence of EISS

OK.

> - Suggestion:[Page 21], Point 1, not clear what the new text becomes.
> Suggestion: refer to last paragraph of section 3.1 instead of paragraph
> before 3.2, and propose the new sentence.

OK.

> - Clarification:[Page 21], Point 2, it is not clear what the change is to
> section 3.2 of RFC6327.

OK.

> - Clarification:[Page 21], Point 3, it would be clearer to say "bullet A9=
 is
> added" (if this is an event like the rest of the bullets in section 3.3 o=
f
> RFC6327)

Guess this does need clarification as its not an event, its a "o
..." type bullet item "after the list of events". I'll clarify.

> - Clarification:[Page 22], section 10.1,"disagreement over the Designated
> VLAN or the like". Suggestion: replace the term "or the like" with other
> examples or remove the term.

How about replacing "... in the face of partitioned VLANs or
disagreement over the Designated VLAN or the like in a link." with
"... in the face of decreased VLAN connectivity in a link such as
partitioned VLANs, many VLANs disabled on ports, or disagreement over
the Designated VLAN."

> -Typo: [Page 22], section 10.1, "each others frames"---->"each other's
> frames"

OK.

> -Typo: [Page 24], "DRB SHOULD NOT appointed"---->"DRB SHOULD NOT appoint"=
,
> "an VLAN"---->"a VLAN", "RBridged"---->"RBridge"

OK.

> -Clarification:[Page 25], Section 11, Point 1, "The previously reserved",
> reference to document.

OK. The block of nicknames from 0xFFC0 through 0xFFFE is reserved by
the TRILL base protocol document [RFC6325].

> - Clarification: [page 19/page 27], Informative References, reference [80=
2],
> to verify which standard we want to refer to for Canonical Format Indicat=
or:
>
> If it is "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan Are=
a
> Networks: Overview and Architecture", then the date should be 7 February
> 2001."

All copies I have seen clearly say 8 March 2001 on the cover.

> However this specific document does not define CIF. You may want to refer=
 to
> 802.1Q-2005.
[Should be CFI above.]

While "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan
Area Networks: Overview and Architecture" does not define the acronym
CFI, it does define "canonical format" and "noncanonical format".
There is no IEEE Std 802.1Q-2005 any more, it having been replaced by
IEEE Std 802.1Q-2011 which does not define the acronym CFI. Doing some
searches, although 802.1Q-2011 replaces the CFI bit in Customer VLAN
tags with the DEI bit, there are a few occurrences of "canonical" left
in 802.1Q-2011, most to say that bridges conformant to 802.1Q-2011
will interoperate with bridges that believe in the CFI bit as long as
those bridges don't actually have any Token Ring interfaces so they
will always set the CF bit to zero. Quoting from page 3 of
802.1Q-2011: "The meanings of the terms Canonical format and
Noncanonical format are discussed in IEEE Std 802.".

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

> Thanks,
> Meral
>
> ---
> Meral Shirazipour
> Ericsson
> Research
> www.ericsson.com

From meral.shirazipour@ericsson.com  Wed Jun 20 13:32:24 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41EA111E808D for <gen-art@ietfa.amsl.com>; Wed, 20 Jun 2012 13:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aqi7PQUctwFK for <gen-art@ietfa.amsl.com>; Wed, 20 Jun 2012 13:32:22 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2ED11E8083 for <gen-art@ietf.org>; Wed, 20 Jun 2012 13:32:22 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q5KKWIKY010714; Wed, 20 Jun 2012 15:32:19 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.57]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Wed, 20 Jun 2012 16:32:13 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 20 Jun 2012 16:32:12 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-trill-clear-correct-03.txt
Thread-Index: Ac1PGl0GO98nEpWKRQ2CurBSrjkPBAAAZuFA
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E699DB9D54C@EUSAACMS0703.eamcs.ericsson.se>
References: <25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7@EUSAACMS0703.eamcs.ericsson.se> <CAF4+nEH3XmK=b0nN8Pcozc_6LB2vxajJ6OM4t7VvZ1Q-Fx13hQ@mail.gmail.com> <CAF4+nEEr7Ys4rZt7Ja97ygzy3bQwQ7J6ap2QW90rfi36Xv=X-w@mail.gmail.com>
In-Reply-To: <CAF4+nEEr7Ys4rZt7Ja97ygzy3bQwQ7J6ap2QW90rfi36Xv=X-w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-trill-clear-correct.all@tools.ietf.org" <draft-ietf-trill-clear-correct.all@tools.ietf.org>, Ayan Banerjee <ayabaner@gmail.com>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-trill-clear-correct-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 20:32:24 -0000

Hi Donald,
   Thank you for considering the comments. Please see below.

Best Regards,
Meral

---
Meral Shirazipour
Ericsson
Research
www.ericsson.com



-----Original Message-----
From: Donald Eastlake [mailto:d3e3e3@gmail.com]=20
Sent: June-20-12 15:24
To: Meral Shirazipour
Cc: draft-ietf-trill-clear-correct.all@tools.ietf.org; gen-art@ietf.org; Ay=
an Banerjee
Subject: Fwd: Gen-ART Last Call review of draft-ietf-trill-clear-correct-03=
.txt

Hi Meral,

A real response this time...

Thanks for your thorough review. See below:

On Tue, Jun 19, 2012 at 11:51 AM, Meral Shirazipour <meral.shirazipour@eric=
sson.com> wrote:
> I am the assigned Gen-ART reviewer for=20
> draft-ietf-trill-clear-correct-03.txt. For background on Gen-ART,=20
> please see the FAQ at <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.=
html>.
>
> Please resolve these comments along with any other Last Call comments=20
> you may receive.
>
>
> Document: draft-ietf-trill-clear-correct-03
> Reviewer: Meral Shirazipour
> Review Date: June-18-2012
> IETF LC End Date: June-20-2012
> IESG Telechat date: June-21-2012
>
>
> Summary:
> The document is ready for publication as a standards track RFC,=20
> however I have a few comments.

Thanks.

> Minor issues:
>
> TRILL-PORT-VER sub-TLV should be "PORT-TRILL-VER" sub-TLV.(there are a=20
> few
> occurrences)

Yes, thanks for spotting that.

> Nits/editorial comments:
>
> - Suggestion: [Page 6], line 2, spell out first occurrence LSP

OK.

> - Suggestion: [Page 6], line 5, "overload bit on" ----> "overload bit set=
"

OK.

> - Clarification:[Page 6], Section 2.1, line 5, add a comma "," after=20
> "traffic engineered frames"

OK.

> - Typo:[Page 6], last word, "contain" --missing s--> "contains"

I believe the current wording is correct.

[msh] sorry about that.

> - Suggestion: [Page 7], Section 2.2, line 2, spell out first=20
> occurrence of "Reverse Path Forwarding Check" and then use "RPFC" in=20
> the rest of the document.

It depends a little on the context but  agree that most can be changed to R=
PFC.
[msh] ok

> - Clarification:[Page 10], Section 2.4.2.3, line 5, sentence starting=20
> with
> "RB2 MUST advertise ...": we could omit the second occurrence of "it=20
> might use" in that sentence.

OK.

> - Clarification:[Page 10], Section 2.4.2.3, 3rd line from last, "end=20
> stations connected to RB": "a RB" or "RBs"?

Should be "end stations connected to RB3".

[msh] ok

> - Typo: [Page 11], Section 3.1,"( j, k)" --remove extra space--> "(j, k)"

OK.

> - Suggestion: [Page 11], Section 3.2, "already in flight" ---->=20
> "already in transmission"

I think the current wording is better.

[msh] ok

> - Typo [Page 12]:"many multi-destination frame"--missing s--> "many=20
> multi-destination frames"

OK.

> - Clarification:[Page 13], Point 4. , Sentence 2: suggested clarification=
:
>
> "It does so by checking LSPs it receives and updating its link state=20
> database for any of its nicknames held with higher priority by another=20
> TRILL Switch that is IS-IS reachable."

I have no problem dropping "in" so it says "...checking LSPs..."
rather than "...checking in LSPs..." but I think the rest of the change you=
 suggest makes it slightly wrong and so would prefer to keep the rest of th=
e wording of that sentence.

[msh] In this case I think keeping the "in" is actually better. I understan=
d the sentence but had to read it a few times.

> - Typo [Page 14]:"unicast Channel message"--missing s-->"unicast=20
> Channel messages"

OK.

> - Typo [Page 16]: Section 5.2,"Routeing" ----> "Routing"

The spelling used in the ISO 10589:2002 standard's title and the naming of =
this field therein includes the "e".

[msh] ok

> - Suggestion:[Page 16],last sentence, suggestion: "This safety margin=20
> is called "Margin" below."

OK.

> - Typo [Page 18]:"a specified in [RFC6325]"--missing s-->"as specified=20
> in [RFC6325]"

OK.

> - Suggestion: [Page 19], spell out first occurrence of EISS

OK.

> - Suggestion:[Page 21], Point 1, not clear what the new text becomes.
> Suggestion: refer to last paragraph of section 3.1 instead of=20
> paragraph before 3.2, and propose the new sentence.

OK.

> - Clarification:[Page 21], Point 2, it is not clear what the change is=20
> to section 3.2 of RFC6327.

OK.

> - Clarification:[Page 21], Point 3, it would be clearer to say "bullet=20
> A9 is added" (if this is an event like the rest of the bullets in=20
> section 3.3 of
> RFC6327)

Guess this does need clarification as its not an event, its a "o ..." type =
bullet item "after the list of events". I'll clarify.

[msh]ok

> - Clarification:[Page 22], section 10.1,"disagreement over the=20
> Designated VLAN or the like". Suggestion: replace the term "or the=20
> like" with other examples or remove the term.

How about replacing "... in the face of partitioned VLANs or disagreement o=
ver the Designated VLAN or the like in a link." with "... in the face of de=
creased VLAN connectivity in a link such as partitioned VLANs, many VLANs d=
isabled on ports, or disagreement over the Designated VLAN."

[msh] ok

> -Typo: [Page 22], section 10.1, "each others frames"---->"each other's=20
> frames"

OK.

> -Typo: [Page 24], "DRB SHOULD NOT appointed"---->"DRB SHOULD NOT=20
> appoint", "an VLAN"---->"a VLAN", "RBridged"---->"RBridge"

OK.

> -Clarification:[Page 25], Section 11, Point 1, "The previously=20
> reserved", reference to document.

OK. The block of nicknames from 0xFFC0 through 0xFFFE is reserved by the TR=
ILL base protocol document [RFC6325].

> - Clarification: [page 19/page 27], Informative References, reference=20
> [802], to verify which standard we want to refer to for Canonical Format =
Indicator:
>
> If it is "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan=20
> Area
> Networks: Overview and Architecture", then the date should be 7=20
> February 2001."

All copies I have seen clearly say 8 March 2001 on the cover.

[msh] ok, since the reference is only for a definition. I made a typo too, =
it is 7 Feb 2002 that I saw-maybe I looked at the wrong document: http://st=
andards.ieee.org/about/get/802/802.html ? )


> However this specific document does not define CIF. You may want to=20
> refer to 802.1Q-2005.
[Should be CFI above.]

[msh] ok

While "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan Area Net=
works: Overview and Architecture" does not define the acronym CFI, it does =
define "canonical format" and "noncanonical format".
There is no IEEE Std 802.1Q-2005 any more, it having been replaced by IEEE =
Std 802.1Q-2011 which does not define the acronym CFI. Doing some searches,=
 although 802.1Q-2011 replaces the CFI bit in Customer VLAN tags with the D=
EI bit, there are a few occurrences of "canonical" left in 802.1Q-2011, mos=
t to say that bridges conformant to 802.1Q-2011 will interoperate with brid=
ges that believe in the CFI bit as long as those bridges don't actually hav=
e any Token Ring interfaces so they will always set the CF bit to zero. Quo=
ting from page 3 of
802.1Q-2011: "The meanings of the terms Canonical format and Noncanonical f=
ormat are discussed in IEEE Std 802.".

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

> Thanks,
> Meral
>
> ---
> Meral Shirazipour
> Ericsson
> Research
> www.ericsson.com

From enkechen@cisco.com  Wed Jun 20 15:50:39 2012
Return-Path: <enkechen@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53F1011E80CE for <gen-art@ietfa.amsl.com>; Wed, 20 Jun 2012 15:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.513
X-Spam-Level: 
X-Spam-Status: No, score=-10.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOc89lLOLaOl for <gen-art@ietfa.amsl.com>; Wed, 20 Jun 2012 15:50:37 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 552B411E80BF for <gen-art@ietf.org>; Wed, 20 Jun 2012 15:50:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=enkechen@cisco.com; l=1531; q=dns/txt; s=iport; t=1340232637; x=1341442237; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=xpSAceEX/YHYTr71hYhcEqkbl67hFDfuq846e9yevWY=; b=aPzLPlcMfwlTcdt3+8MU/lSbV6oQDRe9802lPr3EpesOYR4m+YTZJYet G8gGkUTNwqaPfIWDTFkHZK7JYNqrDjaGFZ0A+BvfcNBAxH90b4cWesQzt QdAuXVZQ7M6cXJdOJyHwEhfOXTNZdwc50lNe5Amov+1v+oXzyS9qVTeds o=;
X-IronPort-AV: E=Sophos;i="4.77,447,1336348800"; d="scan'208";a="47079253"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 20 Jun 2012 22:50:37 +0000
Received: from dhcp-171-71-139-24.cisco.com (dhcp-171-71-139-24.cisco.com [171.71.139.24]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q5KMoam1003217; Wed, 20 Jun 2012 22:50:37 GMT
Message-ID: <4FE25411.4070707@cisco.com>
Date: Wed, 20 Jun 2012 15:52:01 -0700
From: Enke Chen <enkechen@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7F2072F1E0DE894DA4B517B93C6A05852C47149A6E@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852C47149A6E@ESESSCMS0356.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 20 Jun 2012 15:58:20 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, Enke Chen <enkechen@cisco.com>, "draft-ietf-idr-rfc4893bis.all@tools.ietf.org" <draft-ietf-idr-rfc4893bis.all@tools.ietf.org>
Subject: Re: [Gen-art] GenART LC review of draft-ietf-idr-rfc4893bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 22:50:39 -0000

Hi, Christer:

Thanks for your review.  The review comments are accepted and will be 
addressed in the respin.

Please note, though, the terminology changes will result in a larger 
diff between the versions.

-- Enke

On 6/12/12 8:38 AM, Christer Holmberg wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document:                             draft-ietf-idr-rfc4893bis-06.txt
> Reviewer:                               Christer Holmberg
> Review Date:                          2012-06-12
> IETF LC End Date:                   2012-06-15
> IESG Telechat date: (if known)
>
> Summary:  The draft is ready for publication, with a couple of minor editorial nits.
>
> Major issues: -
>
> Minor issues: -
>
> Nits/editorial comments:
>
>
>
> GENERAL:
>
>
>
> Q_GEN-1: Sometimes the text says "AS number", and sometimes "Autonomous System number". Please use consistant terminology.
>
>
>
> Q_GEN-2: Sometimes the text says "2-octet", and sometimes "two-octet". Please use consistant terminology.
>
>
>
> Q_GEN-3: Sometimes the text says "4-octet", and sometimes "four-octet". Please use consistant terminology.
>
>
>
> SECTION 4.2.1:
>
>
>
> Q_4_2_1-1: I suggest to replace "OLD one" with "OLD BGP speaker".
>
>
>
>
>
> Regards,
>
>
>
> Christer
>
>


From elwynd@folly.org.uk  Thu Jun 21 05:38:46 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1ADC21F855E for <gen-art@ietfa.amsl.com>; Thu, 21 Jun 2012 05:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.273
X-Spam-Level: 
X-Spam-Status: No, score=0.273 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_EQ_IP_ADDR=1.119, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zEvOuUfJN2As for <gen-art@ietfa.amsl.com>; Thu, 21 Jun 2012 05:38:44 -0700 (PDT)
Received: from auth.b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 19D5F21F8552 for <gen-art@ietf.org>; Thu, 21 Jun 2012 05:38:44 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[81.187.254.250]) by b.painless.aa.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1Shgeb-0002KA-E8; Thu, 21 Jun 2012 13:38:29 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: Lizhong Jin <lizhong.jin@zte.com.cn>
In-Reply-To: <OFAAEAB3D5.D300977C-ON48257A22.00581007-48257A22.005F0A02@zte.com.cn>
References: <OFAAEAB3D5.D300977C-ON48257A22.00581007-48257A22.005F0A02@zte.com.cn>
Content-Type: text/plain
Organization: Folly Consulting
Date: Thu, 21 Jun 2012 13:38:27 +0100
Message-Id: <1340282307.31554.36408.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-pwe3-cbit-negotiation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 12:38:46 -0000

Hi, Lizhong.

I have removed the bits that we are agreed on to shorten the mail a bit.

I don't think we have converged just yet.

Regards,
Elwyn

On Wed, 2012-06-20 at 01:17 +0800, Lizhong Jin wrote:
> 
> Hi Elwyn, 
> Thank you for the prompt reply. See inline below. 
> 
> Lizhong 
>   
> 
> Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/19 23:16:08:
> > > > Document: draft-ietf-pwe3-cbit-negotiation-04.txt
> > > > Reviewer: Elwyn Davies
> > > > Review Date: 19 June 2012
> > > > IETF LC End Date: 15 June 2012
> > > > IESG Telechat date: 21 June 2012
> > > > 
> > > > Summary: 
> > > > Not ready. The proposal for the NOT PREFERRED to PREFERRED
> > > transition
> > > > case does not appear to be compatible with the existing RFC 4447
> > > > standard in the way stated and there are a number of other minor
> > > issues.
> > > > The draft is also in need of an editing pass by an author whose
> > > mother
> > > > tongue is English as there are parts where the syntax is misleading
> > > > Major issues: 
> > > > s3: The discussion of the NOT PREFERRED to PREFERRED transition case
> > > > (buried at the end of s3 - causing me to ask 'what about this case?'
> > > > during reading of s2 and most of s3)  implies that some existing RFC
> > > > 4447 procedure applies. Clearly, if the PW is not using the control
> > > word
> > > > then there is nothing to do.  On the other hand, inspection of s6.2
> > > of
> > > > RFC4447 indicates that once the two PEs have agreed on c = 1, 'setup
> > > is
> > > > complete' and Label Mapping messages would therefore be
> > > > 'unexpected' (see item '-i' in second set of bullets in s6.2 of RFC
> > > > 4447). So, what procedure is to be used? And what implications does
> > > this
> > > > have for backwards compatibility?  Wouldn't it be generally simpler
> > > to
> > > > apply the PREFERRED to NOT PREFERRED mechanism to all case? 
> > > [Lizhong] this draft is to solve the case to change a PW from c=0 to
> > > c=1, that means one PE should change its use of control word from NOT
> > > PREFERRED to PREFERRED. RFC4447 is already there and deployed, and the
> > > PE will not always send its locally configured preferrence according
> > > RFC4447, see PE1 behavior in section 2 step 1&2. That's why we could
> > > not simply apply the mechanism at the end of section 3. Hope it is
> > > clear. 
> > There are two issues here:
> > - Clarity: RFC 4447 does not have any discussion of what might happen if
> > the configuration value changes.  The draft focusses on on transition
> > direction but does not mention the other except for one paragaph right
> > at the end of s3.  It is therefore reasonable that somebody looking at
> > this draft would wonder 'what about the other transition direction?'.
> > Whether or not anything needs to be done it would save people wondering
> > if you put in a sentence in the introduction to explain that the other
> > direction is not (or is) a problem. 
> [Lizhong] accept. Add following: 
> When PE changes the preference for the use of control word from
> PREFERRED to NOT PREFERRED, it should follow [RFC4447], and there is
> no problem. 

See below...
> 
> > - Technical: The paragraph in s3 implies that the PREFERRED to NOT
> > PREFERRED direction will result in some part of the RFC 4447 protocol
> > being (re-)invoked.  What part is not made very clear.  As far as I can
> > see sending more messages other than Label Release or Label Withdraw for
> > this PW is not part of the RFC 4447 protocol and hence will cause an
> > error.  Alternatively if it isn't reinvoked, the PW will continue to use
> > control words.  Please explain what is going on here.  The fact that RFC
> > 4447 has been deployed doesn't explain what is going on. 
> [Lizhong] now I understand you concern. The last sentance of s3 is not
> clear. How about the following: 
> In that case, local PE will always send Label Withdraw message if
> already sending Label Mapping message, and then send new Label Mapping
> message with C-bit value following the procedures defined in
> [RFC4447]. 

I think we have reached the heart of the issue here:  RFC 4447 does not
mention changing the control word configuration.  The combination of the
existing text in the draft and what you have just weittrn above
indicates that *in both transition directions* the PE changing
configuration notifies its peer by sending a Label Withdraw. It is not
immediately obvious to me that you could deduce this from RFC 4447 - if
it is then there needs to be a pointer to the relevant section in RFC
4447 to enlighten the ignorant like me.  Otherwise the PREFERRED to NOT
PREFERRED transition is *not* just 'follow the RFC 4447 procedures'.

If I now understand correctly, the situation is as follows:
- in both cases when there is a control word preference transition, send
a Label Withdraw.
- in the NOT PREFERRED to PREFERRED case send Label Release also (order
not important), wait for a responses from peer, then send Label Request
and negotiate use of control word using Label Mapping C bit as for a new
PW (might result in either using or not using control word depending on
state in peer).
- in the PREFERRED to NOT PREFERRED case, just negotiate C bit to 0
using Label Mapping - label will be maintained. [Need to check that RFC
4447 is expecting/will allow this sequence.]

If I have this straight, I think that the PREFERRED to NOT PREFERRED
case needs some more words in s3 and an introduction in s2. (And it
would be easier to understand with this case in a separate sub-section -
sorry to harp on about this).   

> > > 
> > > > 
> > > > Minor issues: 
> > > > s3: Has there been any discussion on possible race conditions?
> > >  Changing
> > > > the configuration value during the message exchange strikes me as
> > > > dangerous - it is probably sufficient to note that changes should be
> > > > suppressed during the Label Mapping message exchange but I am not
> > > > totally sure about this. 
> > > [Lizhong] The message would be processed in sequence in TCP-based LDP
> > > session. I do not see a problem here. But we do have a note in section
> > > 3 for multi-segment PW for sequence processing. 
> > There are several network round trips in the message exchanges.  The
> > protocol and the configuration mechanism in a PE are potentially
> > separate threads.  There is scope, depending on the implementation, for
> > the user at the 'remote' PE to change the configuration during the
> > message exchange making for a potential race condition. 
> [Lizhong] we discussed the race condition on the PWE3 maillist from
> Spike, and for multi-segment PW, we add a note to ensure the sequence
> processing for implementation.
I look forward to the revised text.
>  
> 
> > > 
> > > > 
> > > > s3, bullet '-i':  I completely misparsed this section on first
> > > reading
> > > > and I am still not absolutely sure what message sequence is being
> > > > specified.  Working back from later sections I *think* that the
> > > > intention is:
> > > > IF Mapping sent THEN { send Withdraw; send Release;}
> > > > Wait to receive Release
> > > > The implication at present is that a Mapping might not have been
> > > sent
> > > > and then only a Release is needed: is this a possibility? Please
> > > > clarify.
> > > > The picture in Appendix A suffers from the same problem. 
> > > [Lizhong] Adrian raise the same comment, and I change it as below: 
> > >        -i.  PE MUST send a Label Release message to remote PE. If a
> > > PE 
> > >             has previously sent a Label Mapping message to a remote
> > > PE, 
> > >             it MUST also send a Label Withdraw message to the remote
> > > PE, 
> > >             and wait until it receives a Label Release message from
> > > the
> > >            remote PE. 
> > What does it send first if both must be sent?  The text in the rest of
> > the document implies withdraw then release.  This new text sort of
> > implies release then withdraw but isn't really clear. 
> [Lizhong] both should be sent, and does not require the sending
> sequence. The two messages does not have dependence. 
In that case, it is important to say so.
> 
> > > 
> > > > 
> > > > s3, discussion of multi-segment PWs: The statement that S-PE's
> > > SHOULD
> > > > assume an initial passive role seems to have several problems:
> > > > - Does this mean that changing the configuration of an S-PE would
> > > not
> > > > provoke the new mechanisms?
> > > > - The passive role situation is only specified for some sorts of
> > > linked
> > > > FECs in RFC 6073 - what about other cases?
> > > > - What are the consequences for ignoring the SHOULD in this case? (I
> > > > have to say I am unsure that RFC 6073 deals with this problem
> > > either.) 
> > > [Lizhong] we follow RFC6073, and passive role is only applied for the
> > > PW FEC, other cases are out of scope. 
> > Why? This needs an explanation. Also this doesn't cover the point about
> > whether reconfig of an S-PE is allowed and how this squares with the
> > passive role.
> > > SHOULD means highly recommended. We do not meet any problem when
> > > implementing RFC6073. Do you suggest to change this to MUST? 
> > Whenever a specification includes a 'SHOULD' the question arises of what
> > alternatives there might be and what is the reason for preferring the
> > suggested solution.  In the original setup, it is fairly clear that life
> > is easier letting setup progress from  one end to the other (although
> > this is not spelt out - I would have argued for this had  I reviewed the
> > doc).  For the configuration change this is less obvious.  Regarding the
> > point about reconfig of the  S-PE, it is going to make life more
> > complicated if the S-PE has to tell the T-PE to be active so it can be
> > passive.  I would therefore argue that probably the notion of passivity
> > is irrelevant to the transition use case.  Whether it should be SHOULD
> > or MUST is therefore moot. 
> [Lizhong] how about the following? Because we just refer to RFC6073, and does not add anything new. 
> An initial passive role is defined in [RFC6073] for S-PE.
I can't see that this really helps.
There are still two points at issue here:
- Why are the cases other than the one in RFC 4447 that refers to a
passive S-PE out of scope?  There aren't any statements to this effect
in the document.
- It is difficult for a S-PE that has its control word configuration
change to act passively.  If it is really passive than nothing will
happen until the label is withdrawn.  Otherwise it can't be descibed as
passive for this action.  The text in the current draft actually
describes what is specified in RFC 6073 when talking 'passive' rather
than explaining what happens when the control word configuration
changes.
>  
> > > [Lizhong] has been revised in v-04.
> > Not as far as I can see. 
> [Lizhong] write "pseudowire" directly in the text, not PW. 
There are lots of instances of PW still left in v04. Expand acronym =>
define what it means on first usage i.e pseudowire (PW).  Same for the
various other acronyms that aren't defined in the text.
> 
> > > > 
> > > > s2: Expand acronym PE. 
> > > [Lizhong] accept 
> > > 
> > > > s2, 2nd sentence: s/configurable/configured/ 
> > > [Lizhong] configurable is right. 
> > Leave that one to the RFc Editor.
> > > 
> > > > s2, 3rd and 4th sentences: I *think* this text is trying to say: 
> > > >   The intention of the control word negotiation is that the control
> > > word
> > > > will be used when both endpoints are configured with control word
> > > usage
> > > > PREFERRED.  However if one endpoint is initially configured with
> > > control
> > > > word usage NOT PREFERRED but later changes to PREFERRED, a PW
> > > between
> > > > the endpoints will not transition to usage of the control word as
> > > > explained below. 
> > > [Lizhong] no, the case is that operator deploys PW with control word
> > > used in the first phase. In the second phase, they want to upgrade
> > > their PW service to use control word. Two different deployment
> > > timeframes.
> > That is what my sentence says. 
> [Lizhong] ok. 
> 

> > > > s3: It would be much clearer if s3 was divided into 3 sub-sections
> > > > (possibly reordered):
> > > > - PREFERRED to NOT PREFERRED transition
> > > > - NOT PREFERRED to PREFERRED transition
> > > > - Multi-segment case (which should refer to both previous cases)
> > > > The pointer to the diagram in Appendix A could usefully occur in the
> > > > introduction to s3.  If this was adopted s3.1 could either be a
> > > fourth
> > > > sub-section or a sub-sub-section of the PREFERRED to NOT PREFERRED
> > > > section. 
> > > [Lizhong] PREFERRED to NOT PREFERRED does not introduce any new.
> > > Multi-segment case is fully inherited from single-segment case. It
> > > would be redundancy to have sub-sections here. 
> > I disagree strongly.  The multi-segment case affects the other RFC and
> > needs to be made to stand out so that implementors can see where the
> > changes occur.  The PREFERRED to NOT PREFERRED case also ought to be
> > separated whether or not I am right about this case. 
> [Lizhong] how about only divide multi-segment? The case of PREFERRED to 
> NOT PREFERRED case is only for reference, and the text is not many.
That is so, but it is a change of subject and the fact that it will then
be in the table of contents makes it easier for implementors to find the
relevant text.  I wouldn't call it 'redundant'.

> > > > s3, last para/Appendix A:  The diagram doesn't cover the PREFERRED
> > > to
> > > > NOT PREFERRED transition. 
> > > [Lizhong] no, there is a "no" branch under "NOT Preferred to
> > > Preferred" to cover "PREFERRED to NOT PREFERRED". Anyway, the diagram
> > > discription should be "NOT Preferred to Preferred" which is wrong in
> > > v-04. 
Need to check it reflects the Label Withdraw message needed in the
PREFERRED to NOT PREFERRED case. 



From stbryant@cisco.com  Thu Jun 21 06:56:27 2012
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8E7C21F86B5; Thu, 21 Jun 2012 06:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kWljcwnA9NqY; Thu, 21 Jun 2012 06:56:26 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 4793621F866B; Thu, 21 Jun 2012 06:56:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=14440; q=dns/txt; s=iport; t=1340286986; x=1341496586; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=RXruekzt2+pbMOWk2YFIWR9iuOnjtrT+vcxol+n+kgc=; b=ASVR0DNPM+xKHZEu3wis2Dp4h4PMdJ6RTzY+ZjN1TZSpmWux5Q84dZf4 xeLGsWLjGATmAwNIwErO7FM7kNNnQM3tpFoXdp4ZNmCZ2uY12n4mQCxOM S8OmfYjbxzBj3ulv7xif0lv2LBmVpIkmXPNPNkL3/9FY52kMiMP9cc52f o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EANYn40+rRDoJ/2dsb2JhbABFtVSBB4IYAQEBBBIBAiNAARALFAQJFg8JAwIBAgFFBg0BBQIBARUCB4doAQuaAoNIEJw7iy4ahgMDkU2DXY4bgQRigmCBVQcC
X-IronPort-AV: E=Sophos;i="4.77,451,1336348800"; d="scan'208";a="49725329"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 21 Jun 2012 13:56:12 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q5LDuAXO028602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jun 2012 13:56:12 GMT
Received: from dhcp-bdlk10-data-vlan300-64-103-106-107.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q5LDu75S016416; Thu, 21 Jun 2012 14:56:08 +0100 (BST)
Message-ID: <4FE327F7.4000008@cisco.com>
Date: Thu, 21 Jun 2012 14:56:07 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Elwyn Davies <elwynd@folly.org.uk>
References: <OFAAEAB3D5.D300977C-ON48257A22.00581007-48257A22.005F0A02@zte.com.cn> <1340282307.31554.36408.camel@mightyatom.folly.org.uk>
In-Reply-To: <1340282307.31554.36408.camel@mightyatom.folly.org.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Lizhong Jin <lizhong.jin@zte.com.cn>, pwe3 <pwe3@ietf.org>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-pwe3-cbit-negotiation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 13:56:27 -0000

Bringing this to the attention of the PWE3 WG
since that need to know that this discussion is happening
and will have a view as to what is already well
known in terms of RFC4447 behavior and what
needs clarification via this draft.

Stewart

On 21/06/2012 13:38, Elwyn Davies wrote:
> Hi, Lizhong.
>
> I have removed the bits that we are agreed on to shorten the mail a bit.
>
> I don't think we have converged just yet.
>
> Regards,
> Elwyn
>
> On Wed, 2012-06-20 at 01:17 +0800, Lizhong Jin wrote:
>> Hi Elwyn,
>> Thank you for the prompt reply. See inline below.
>>
>> Lizhong
>>    
>>
>> Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/19 23:16:08:
>>>>> Document: draft-ietf-pwe3-cbit-negotiation-04.txt
>>>>> Reviewer: Elwyn Davies
>>>>> Review Date: 19 June 2012
>>>>> IETF LC End Date: 15 June 2012
>>>>> IESG Telechat date: 21 June 2012
>>>>>
>>>>> Summary:
>>>>> Not ready. The proposal for the NOT PREFERRED to PREFERRED
>>>> transition
>>>>> case does not appear to be compatible with the existing RFC 4447
>>>>> standard in the way stated and there are a number of other minor
>>>> issues.
>>>>> The draft is also in need of an editing pass by an author whose
>>>> mother
>>>>> tongue is English as there are parts where the syntax is misleading
>>>>> Major issues:
>>>>> s3: The discussion of the NOT PREFERRED to PREFERRED transition case
>>>>> (buried at the end of s3 - causing me to ask 'what about this case?'
>>>>> during reading of s2 and most of s3)  implies that some existing RFC
>>>>> 4447 procedure applies. Clearly, if the PW is not using the control
>>>> word
>>>>> then there is nothing to do.  On the other hand, inspection of s6.2
>>>> of
>>>>> RFC4447 indicates that once the two PEs have agreed on c = 1, 'setup
>>>> is
>>>>> complete' and Label Mapping messages would therefore be
>>>>> 'unexpected' (see item '-i' in second set of bullets in s6.2 of RFC
>>>>> 4447). So, what procedure is to be used? And what implications does
>>>> this
>>>>> have for backwards compatibility?  Wouldn't it be generally simpler
>>>> to
>>>>> apply the PREFERRED to NOT PREFERRED mechanism to all case?
>>>> [Lizhong] this draft is to solve the case to change a PW from c=0 to
>>>> c=1, that means one PE should change its use of control word from NOT
>>>> PREFERRED to PREFERRED. RFC4447 is already there and deployed, and the
>>>> PE will not always send its locally configured preferrence according
>>>> RFC4447, see PE1 behavior in section 2 step 1&2. That's why we could
>>>> not simply apply the mechanism at the end of section 3. Hope it is
>>>> clear.
>>> There are two issues here:
>>> - Clarity: RFC 4447 does not have any discussion of what might happen if
>>> the configuration value changes.  The draft focusses on on transition
>>> direction but does not mention the other except for one paragaph right
>>> at the end of s3.  It is therefore reasonable that somebody looking at
>>> this draft would wonder 'what about the other transition direction?'.
>>> Whether or not anything needs to be done it would save people wondering
>>> if you put in a sentence in the introduction to explain that the other
>>> direction is not (or is) a problem.
>> [Lizhong] accept. Add following:
>> When PE changes the preference for the use of control word from
>> PREFERRED to NOT PREFERRED, it should follow [RFC4447], and there is
>> no problem.
> See below...
>>> - Technical: The paragraph in s3 implies that the PREFERRED to NOT
>>> PREFERRED direction will result in some part of the RFC 4447 protocol
>>> being (re-)invoked.  What part is not made very clear.  As far as I can
>>> see sending more messages other than Label Release or Label Withdraw for
>>> this PW is not part of the RFC 4447 protocol and hence will cause an
>>> error.  Alternatively if it isn't reinvoked, the PW will continue to use
>>> control words.  Please explain what is going on here.  The fact that RFC
>>> 4447 has been deployed doesn't explain what is going on.
>> [Lizhong] now I understand you concern. The last sentance of s3 is not
>> clear. How about the following:
>> In that case, local PE will always send Label Withdraw message if
>> already sending Label Mapping message, and then send new Label Mapping
>> message with C-bit value following the procedures defined in
>> [RFC4447].
> I think we have reached the heart of the issue here:  RFC 4447 does not
> mention changing the control word configuration.  The combination of the
> existing text in the draft and what you have just weittrn above
> indicates that *in both transition directions* the PE changing
> configuration notifies its peer by sending a Label Withdraw. It is not
> immediately obvious to me that you could deduce this from RFC 4447 - if
> it is then there needs to be a pointer to the relevant section in RFC
> 4447 to enlighten the ignorant like me.  Otherwise the PREFERRED to NOT
> PREFERRED transition is *not* just 'follow the RFC 4447 procedures'.
>
> If I now understand correctly, the situation is as follows:
> - in both cases when there is a control word preference transition, send
> a Label Withdraw.
> - in the NOT PREFERRED to PREFERRED case send Label Release also (order
> not important), wait for a responses from peer, then send Label Request
> and negotiate use of control word using Label Mapping C bit as for a new
> PW (might result in either using or not using control word depending on
> state in peer).
> - in the PREFERRED to NOT PREFERRED case, just negotiate C bit to 0
> using Label Mapping - label will be maintained. [Need to check that RFC
> 4447 is expecting/will allow this sequence.]
>
> If I have this straight, I think that the PREFERRED to NOT PREFERRED
> case needs some more words in s3 and an introduction in s2. (And it
> would be easier to understand with this case in a separate sub-section -
> sorry to harp on about this).
>
>>>>> Minor issues:
>>>>> s3: Has there been any discussion on possible race conditions?
>>>>   Changing
>>>>> the configuration value during the message exchange strikes me as
>>>>> dangerous - it is probably sufficient to note that changes should be
>>>>> suppressed during the Label Mapping message exchange but I am not
>>>>> totally sure about this.
>>>> [Lizhong] The message would be processed in sequence in TCP-based LDP
>>>> session. I do not see a problem here. But we do have a note in section
>>>> 3 for multi-segment PW for sequence processing.
>>> There are several network round trips in the message exchanges.  The
>>> protocol and the configuration mechanism in a PE are potentially
>>> separate threads.  There is scope, depending on the implementation, for
>>> the user at the 'remote' PE to change the configuration during the
>>> message exchange making for a potential race condition.
>> [Lizhong] we discussed the race condition on the PWE3 maillist from
>> Spike, and for multi-segment PW, we add a note to ensure the sequence
>> processing for implementation.
> I look forward to the revised text.
>>   
>>
>>>>> s3, bullet '-i':  I completely misparsed this section on first
>>>> reading
>>>>> and I am still not absolutely sure what message sequence is being
>>>>> specified.  Working back from later sections I *think* that the
>>>>> intention is:
>>>>> IF Mapping sent THEN { send Withdraw; send Release;}
>>>>> Wait to receive Release
>>>>> The implication at present is that a Mapping might not have been
>>>> sent
>>>>> and then only a Release is needed: is this a possibility? Please
>>>>> clarify.
>>>>> The picture in Appendix A suffers from the same problem.
>>>> [Lizhong] Adrian raise the same comment, and I change it as below:
>>>>         -i.  PE MUST send a Label Release message to remote PE. If a
>>>> PE
>>>>              has previously sent a Label Mapping message to a remote
>>>> PE,
>>>>              it MUST also send a Label Withdraw message to the remote
>>>> PE,
>>>>              and wait until it receives a Label Release message from
>>>> the
>>>>             remote PE.
>>> What does it send first if both must be sent?  The text in the rest of
>>> the document implies withdraw then release.  This new text sort of
>>> implies release then withdraw but isn't really clear.
>> [Lizhong] both should be sent, and does not require the sending
>> sequence. The two messages does not have dependence.
> In that case, it is important to say so.
>>>>> s3, discussion of multi-segment PWs: The statement that S-PE's
>>>> SHOULD
>>>>> assume an initial passive role seems to have several problems:
>>>>> - Does this mean that changing the configuration of an S-PE would
>>>> not
>>>>> provoke the new mechanisms?
>>>>> - The passive role situation is only specified for some sorts of
>>>> linked
>>>>> FECs in RFC 6073 - what about other cases?
>>>>> - What are the consequences for ignoring the SHOULD in this case? (I
>>>>> have to say I am unsure that RFC 6073 deals with this problem
>>>> either.)
>>>> [Lizhong] we follow RFC6073, and passive role is only applied for the
>>>> PW FEC, other cases are out of scope.
>>> Why? This needs an explanation. Also this doesn't cover the point about
>>> whether reconfig of an S-PE is allowed and how this squares with the
>>> passive role.
>>>> SHOULD means highly recommended. We do not meet any problem when
>>>> implementing RFC6073. Do you suggest to change this to MUST?
>>> Whenever a specification includes a 'SHOULD' the question arises of what
>>> alternatives there might be and what is the reason for preferring the
>>> suggested solution.  In the original setup, it is fairly clear that life
>>> is easier letting setup progress from  one end to the other (although
>>> this is not spelt out - I would have argued for this had  I reviewed the
>>> doc).  For the configuration change this is less obvious.  Regarding the
>>> point about reconfig of the  S-PE, it is going to make life more
>>> complicated if the S-PE has to tell the T-PE to be active so it can be
>>> passive.  I would therefore argue that probably the notion of passivity
>>> is irrelevant to the transition use case.  Whether it should be SHOULD
>>> or MUST is therefore moot.
>> [Lizhong] how about the following? Because we just refer to RFC6073, and does not add anything new.
>> An initial passive role is defined in [RFC6073] for S-PE.
> I can't see that this really helps.
> There are still two points at issue here:
> - Why are the cases other than the one in RFC 4447 that refers to a
> passive S-PE out of scope?  There aren't any statements to this effect
> in the document.
> - It is difficult for a S-PE that has its control word configuration
> change to act passively.  If it is really passive than nothing will
> happen until the label is withdrawn.  Otherwise it can't be descibed as
> passive for this action.  The text in the current draft actually
> describes what is specified in RFC 6073 when talking 'passive' rather
> than explaining what happens when the control word configuration
> changes.
>>   
>>>> [Lizhong] has been revised in v-04.
>>> Not as far as I can see.
>> [Lizhong] write "pseudowire" directly in the text, not PW.
> There are lots of instances of PW still left in v04. Expand acronym =>
> define what it means on first usage i.e pseudowire (PW).  Same for the
> various other acronyms that aren't defined in the text.
>>>>> s2: Expand acronym PE.
>>>> [Lizhong] accept
>>>>
>>>>> s2, 2nd sentence: s/configurable/configured/
>>>> [Lizhong] configurable is right.
>>> Leave that one to the RFc Editor.
>>>>> s2, 3rd and 4th sentences: I *think* this text is trying to say:
>>>>>    The intention of the control word negotiation is that the control
>>>> word
>>>>> will be used when both endpoints are configured with control word
>>>> usage
>>>>> PREFERRED.  However if one endpoint is initially configured with
>>>> control
>>>>> word usage NOT PREFERRED but later changes to PREFERRED, a PW
>>>> between
>>>>> the endpoints will not transition to usage of the control word as
>>>>> explained below.
>>>> [Lizhong] no, the case is that operator deploys PW with control word
>>>> used in the first phase. In the second phase, they want to upgrade
>>>> their PW service to use control word. Two different deployment
>>>> timeframes.
>>> That is what my sentence says.
>> [Lizhong] ok.
>>
>>>>> s3: It would be much clearer if s3 was divided into 3 sub-sections
>>>>> (possibly reordered):
>>>>> - PREFERRED to NOT PREFERRED transition
>>>>> - NOT PREFERRED to PREFERRED transition
>>>>> - Multi-segment case (which should refer to both previous cases)
>>>>> The pointer to the diagram in Appendix A could usefully occur in the
>>>>> introduction to s3.  If this was adopted s3.1 could either be a
>>>> fourth
>>>>> sub-section or a sub-sub-section of the PREFERRED to NOT PREFERRED
>>>>> section.
>>>> [Lizhong] PREFERRED to NOT PREFERRED does not introduce any new.
>>>> Multi-segment case is fully inherited from single-segment case. It
>>>> would be redundancy to have sub-sections here.
>>> I disagree strongly.  The multi-segment case affects the other RFC and
>>> needs to be made to stand out so that implementors can see where the
>>> changes occur.  The PREFERRED to NOT PREFERRED case also ought to be
>>> separated whether or not I am right about this case.
>> [Lizhong] how about only divide multi-segment? The case of PREFERRED to
>> NOT PREFERRED case is only for reference, and the text is not many.
> That is so, but it is a change of subject and the fact that it will then
> be in the table of contents makes it easier for implementors to find the
> relevant text.  I wouldn't call it 'redundant'.
>
>>>>> s3, last para/Appendix A:  The diagram doesn't cover the PREFERRED
>>>> to
>>>>> NOT PREFERRED transition.
>>>> [Lizhong] no, there is a "no" branch under "NOT Preferred to
>>>> Preferred" to cover "PREFERRED to NOT PREFERRED". Anyway, the diagram
>>>> discription should be "NOT Preferred to Preferred" which is wrong in
>>>> v-04.
> Need to check it reflects the Label Withdraw message needed in the
> PREFERRED to NOT PREFERRED case.
>
>
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From lizhong.jin@zte.com.cn  Thu Jun 21 07:45:04 2012
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4364F21F8703 for <gen-art@ietfa.amsl.com>; Thu, 21 Jun 2012 07:45:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.588
X-Spam-Level: 
X-Spam-Status: No, score=-101.588 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rD5NqouQOFC8 for <gen-art@ietfa.amsl.com>; Thu, 21 Jun 2012 07:45:01 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA6121F8700 for <gen-art@ietf.org>; Thu, 21 Jun 2012 07:44:59 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 286201878467102; Thu, 21 Jun 2012 22:41:17 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 52926.6222168083; Thu, 21 Jun 2012 22:44:51 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q5LEik5H064754; Thu, 21 Jun 2012 22:44:46 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <1340282307.31554.36408.camel@mightyatom.folly.org.uk>
To: Elwyn Davies <elwynd@folly.org.uk>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF6E7B2A91.233F1F7A-ON48257A24.004B6705-48257A24.005100EB@zte.com.cn>
From: Lizhong Jin<lizhong.jin@zte.com.cn>
Date: Thu, 21 Jun 2012 22:43:54 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-06-21 22:44:49, Serialize complete at 2012-06-21 22:44:49
Content-Type: multipart/alternative; boundary="=_alternative 005100E948257A24_="
X-MAIL: mse01.zte.com.cn q5LEik5H064754
Cc: draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-pwe3-cbit-negotiation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 14:45:04 -0000

This is a multipart message in MIME format.
--=_alternative 005100E948257A24_=
Content-Type: text/plain; charset="US-ASCII"

Hi Elwyn,
Please see inline below.

Thanks
Lizhong


Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/21 20:38:27:

> Hi, Lizhong.
> 
> I have removed the bits that we are agreed on to shorten the mail a bit.
> 
> I don't think we have converged just yet.
> 
> Regards,
> Elwyn
> 
> On Wed, 2012-06-20 at 01:17 +0800, Lizhong Jin wrote:
> > 
> > Hi Elwyn, 
> > Thank you for the prompt reply. See inline below. 
> > 
> > Lizhong 
> > 
> > 
> > Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/19 23:16:08:
> > > > > Document: draft-ietf-pwe3-cbit-negotiation-04.txt
> > > > > Reviewer: Elwyn Davies
> > > > > Review Date: 19 June 2012
> > > > > IETF LC End Date: 15 June 2012
> > > > > IESG Telechat date: 21 June 2012
> > > > > 
> > > > > Summary: 
> > > > > Not ready. The proposal for the NOT PREFERRED to PREFERRED
> > > > transition
> > > > > case does not appear to be compatible with the existing RFC 4447
> > > > > standard in the way stated and there are a number of other minor
> > > > issues.
> > > > > The draft is also in need of an editing pass by an author whose
> > > > mother
> > > > > tongue is English as there are parts where the syntax is 
misleading
> > > > > Major issues: 
> > > > > s3: The discussion of the NOT PREFERRED to PREFERRED transition 
case
> > > > > (buried at the end of s3 - causing me to ask 'what about this 
case?'
> > > > > during reading of s2 and most of s3)  implies that some existing 
RFC
> > > > > 4447 procedure applies. Clearly, if the PW is not using the 
control
> > > > word
> > > > > then there is nothing to do.  On the other hand, inspection of 
s6.2
> > > > of
> > > > > RFC4447 indicates that once the two PEs have agreed on c = 1, 
'setup
> > > > is
> > > > > complete' and Label Mapping messages would therefore be
> > > > > 'unexpected' (see item '-i' in second set of bullets in s6.2 of 
RFC
> > > > > 4447). So, what procedure is to be used? And what implications 
does
> > > > this
> > > > > have for backwards compatibility?  Wouldn't it be generally 
simpler
> > > > to
> > > > > apply the PREFERRED to NOT PREFERRED mechanism to all case? 
> > > > [Lizhong] this draft is to solve the case to change a PW from c=0 
to
> > > > c=1, that means one PE should change its use of control word from 
NOT
> > > > PREFERRED to PREFERRED. RFC4447 is already there and deployed, and 
the
> > > > PE will not always send its locally configured preferrence 
according
> > > > RFC4447, see PE1 behavior in section 2 step 1&2. That's why we 
could
> > > > not simply apply the mechanism at the end of section 3. Hope it is
> > > > clear. 
> > > There are two issues here:
> > > - Clarity: RFC 4447 does not have any discussion of what might 
happen if
> > > the configuration value changes.  The draft focusses on on 
transition
> > > direction but does not mention the other except for one paragaph 
right
> > > at the end of s3.  It is therefore reasonable that somebody looking 
at
> > > this draft would wonder 'what about the other transition 
direction?'.
> > > Whether or not anything needs to be done it would save people 
wondering
> > > if you put in a sentence in the introduction to explain that the 
other
> > > direction is not (or is) a problem. 
> > [Lizhong] accept. Add following: 
> > When PE changes the preference for the use of control word from
> > PREFERRED to NOT PREFERRED, it should follow [RFC4447], and there is
> > no problem. 
> 
> See below...
> > 
> > > - Technical: The paragraph in s3 implies that the PREFERRED to NOT
> > > PREFERRED direction will result in some part of the RFC 4447 
protocol
> > > being (re-)invoked.  What part is not made very clear.  As far as I 
can
> > > see sending more messages other than Label Release or Label Withdraw 
for
> > > this PW is not part of the RFC 4447 protocol and hence will cause an
> > > error.  Alternatively if it isn't reinvoked, the PW will continue to 
use
> > > control words.  Please explain what is going on here.  The fact that 
RFC
> > > 4447 has been deployed doesn't explain what is going on. 
> > [Lizhong] now I understand you concern. The last sentance of s3 is not
> > clear. How about the following: 
> > In that case, local PE will always send Label Withdraw message if
> > already sending Label Mapping message, and then send new Label Mapping
> > message with C-bit value following the procedures defined in
> > [RFC4447]. 
> 
> I think we have reached the heart of the issue here:  RFC 4447 does not
> mention changing the control word configuration.  The combination of the
> existing text in the draft and what you have just weittrn above
> indicates that *in both transition directions* the PE changing
> configuration notifies its peer by sending a Label Withdraw. It is not
> immediately obvious to me that you could deduce this from RFC 4447 - if
> it is then there needs to be a pointer to the relevant section in RFC
> 4447 to enlighten the ignorant like me.  Otherwise the PREFERRED to NOT
> PREFERRED transition is *not* just 'follow the RFC 4447 procedures'.
[Lizhong] as an engineer, I interpret the configuration changing as 
deleting and configuring again. Control word configuration changing means 
deleting the old control word, and then configuring the new control word, 
that means deleting PW configuration, and configuring new PW configuration 
again. RFC4447 section 5.4.1 describe the procedure of PW deletion and 
configuration. When you apply the above procedure to PREFERRED to NOT 
PREFERRED transition, it works well, while for NOT PREFERRED to PREFERRED 
transition, there is a problem.
What if I add some description of the meaning of control word changing at 
the end of s3, so as to make it clear?

> 
> If I now understand correctly, the situation is as follows:
> - in both cases when there is a control word preference transition, send
> a Label Withdraw.
> - in the NOT PREFERRED to PREFERRED case send Label Release also (order
> not important), wait for a responses from peer, then send Label Request
> and negotiate use of control word using Label Mapping C bit as for a new
> PW (might result in either using or not using control word depending on
> state in peer).
> - in the PREFERRED to NOT PREFERRED case, just negotiate C bit to 0
> using Label Mapping - label will be maintained. [Need to check that RFC
> 4447 is expecting/will allow this sequence.]
> 
> If I have this straight, I think that the PREFERRED to NOT PREFERRED
> case needs some more words in s3 and an introduction in s2. (And it
> would be easier to understand with this case in a separate sub-section -
> sorry to harp on about this). 
[Lizhong] your above description is totally right. How about changing the 
end of s3 as below:
When Local PE changes the use of control word from PREFERRED to NOT 
PREFERRED, the local PE would be able to negotiate the Control Word to be 
not used by deleting the PW configuration with PREFERRED use of control 
word,  and configuring the PW again with NOT PREFERRED use of control 
word. All of these procedures have been defined in [RFC4447] section 
5.4.1.

> 
> > > > 
> > > > > 
> > > > > Minor issues: 
> > > > > s3: Has there been any discussion on possible race conditions?
> > > >  Changing
> > > > > the configuration value during the message exchange strikes me 
as
> > > > > dangerous - it is probably sufficient to note that changes 
should be
> > > > > suppressed during the Label Mapping message exchange but I am 
not
> > > > > totally sure about this. 
> > > > [Lizhong] The message would be processed in sequence in TCP-based 
LDP
> > > > session. I do not see a problem here. But we do have a note in 
section
> > > > 3 for multi-segment PW for sequence processing. 
> > > There are several network round trips in the message exchanges.  The
> > > protocol and the configuration mechanism in a PE are potentially
> > > separate threads.  There is scope, depending on the implementation, 
for
> > > the user at the 'remote' PE to change the configuration during the
> > > message exchange making for a potential race condition. 
> > [Lizhong] we discussed the race condition on the PWE3 maillist from
> > Spike, and for multi-segment PW, we add a note to ensure the sequence
> > processing for implementation.
> I look forward to the revised text.
[Lizhong] How about add the following in s3: for the local PE, before 
processing new configuration changing, the above message exchange process 
should be finished.

> > 
> > 
> > > > 
> > > > > 
> > > > > s3, bullet '-i':  I completely misparsed this section on first
> > > > reading
> > > > > and I am still not absolutely sure what message sequence is 
being
> > > > > specified.  Working back from later sections I *think* that the
> > > > > intention is:
> > > > > IF Mapping sent THEN { send Withdraw; send Release;}
> > > > > Wait to receive Release
> > > > > The implication at present is that a Mapping might not have been
> > > > sent
> > > > > and then only a Release is needed: is this a possibility? Please
> > > > > clarify.
> > > > > The picture in Appendix A suffers from the same problem. 
> > > > [Lizhong] Adrian raise the same comment, and I change it as below: 

> > > >        -i.  PE MUST send a Label Release message to remote PE. If 
a
> > > > PE 
> > > >             has previously sent a Label Mapping message to a 
remote
> > > > PE, 
> > > >             it MUST also send a Label Withdraw message to the 
remote
> > > > PE, 
> > > >             and wait until it receives a Label Release message 
from
> > > > the
> > > >            remote PE. 
> > > What does it send first if both must be sent?  The text in the rest 
of
> > > the document implies withdraw then release.  This new text sort of
> > > implies release then withdraw but isn't really clear. 
> > [Lizhong] both should be sent, and does not require the sending
> > sequence. The two messages does not have dependence. 
> In that case, it is important to say so.
[Lizhong] I will add a sentence in point "i" to say so. How about below:
Note: above Label Release message and Label Withdraw message sending does 
not require specific sequence.

> > 
> > > > 
> > > > > 
> > > > > s3, discussion of multi-segment PWs: The statement that S-PE's
> > > > SHOULD
> > > > > assume an initial passive role seems to have several problems:
> > > > > - Does this mean that changing the configuration of an S-PE 
would
> > > > not
> > > > > provoke the new mechanisms?
> > > > > - The passive role situation is only specified for some sorts of
> > > > linked
> > > > > FECs in RFC 6073 - what about other cases?
> > > > > - What are the consequences for ignoring the SHOULD in this 
case? (I
> > > > > have to say I am unsure that RFC 6073 deals with this problem
> > > > either.) 
> > > > [Lizhong] we follow RFC6073, and passive role is only applied for 
the
> > > > PW FEC, other cases are out of scope. 
> > > Why? This needs an explanation. Also this doesn't cover the point 
about
> > > whether reconfig of an S-PE is allowed and how this squares with the
> > > passive role.
> > > > SHOULD means highly recommended. We do not meet any problem when
> > > > implementing RFC6073. Do you suggest to change this to MUST? 
> > > Whenever a specification includes a 'SHOULD' the question arises of 
what
> > > alternatives there might be and what is the reason for preferring 
the
> > > suggested solution.  In the original setup, it is fairly clear that 
life
> > > is easier letting setup progress from  one end to the other 
(although
> > > this is not spelt out - I would have argued for this had  I reviewed 
the
> > > doc).  For the configuration change this is less obvious.  Regarding 
the
> > > point about reconfig of the  S-PE, it is going to make life more
> > > complicated if the S-PE has to tell the T-PE to be active so it can 
be
> > > passive.  I would therefore argue that probably the notion of 
passivity
> > > is irrelevant to the transition use case.  Whether it should be 
SHOULD
> > > or MUST is therefore moot. 
> > [Lizhong] how about the following? Because we just refer to 
> RFC6073, and does not add anything new. 
> > An initial passive role is defined in [RFC6073] for S-PE.
> I can't see that this really helps.
> There are still two points at issue here:
> - Why are the cases other than the one in RFC 4447 that refers to a
> passive S-PE out of scope?  There aren't any statements to this effect
> in the document.
[Lizhong] the passive role is not for any specific cases. The passive role 
is for the processing of message (e.g, label mapping, label request). I 
will explicitly say that in the section.

> - It is difficult for a S-PE that has its control word configuration
> change to act passively.  If it is really passive than nothing will
> happen until the label is withdrawn.  Otherwise it can't be descibed as
> passive for this action.  The text in the current draft actually
> describes what is specified in RFC 6073 when talking 'passive' rather
> than explaining what happens when the control word configuration
> changes.
[Lizhong] the control word configuration changing talking about in this 
draft only happens on T-PE, not S-PE. The S-PE is a passive role for the 
message processing. I will make this clear in the draft.

> > 
> > > > [Lizhong] has been revised in v-04.
> > > Not as far as I can see. 
> > [Lizhong] write "pseudowire" directly in the text, not PW. 
> There are lots of instances of PW still left in v04. Expand acronym =>
> define what it means on first usage i.e pseudowire (PW).  Same for the
> various other acronyms that aren't defined in the text.
[Lizhong] accept
> > 
> > > > > 
> > > > > s2: Expand acronym PE. 
> > > > [Lizhong] accept 
> > > > 
> > > > > s2, 2nd sentence: s/configurable/configured/ 
> > > > [Lizhong] configurable is right. 
> > > Leave that one to the RFc Editor.
> > > > 
> > > > > s2, 3rd and 4th sentences: I *think* this text is trying to say: 

> > > > >   The intention of the control word negotiation is that the 
control
> > > > word
> > > > > will be used when both endpoints are configured with control 
word
> > > > usage
> > > > > PREFERRED.  However if one endpoint is initially configured with
> > > > control
> > > > > word usage NOT PREFERRED but later changes to PREFERRED, a PW
> > > > between
> > > > > the endpoints will not transition to usage of the control word 
as
> > > > > explained below. 
> > > > [Lizhong] no, the case is that operator deploys PW with control 
word
> > > > used in the first phase. In the second phase, they want to upgrade
> > > > their PW service to use control word. Two different deployment
> > > > timeframes.
> > > That is what my sentence says. 
> > [Lizhong] ok. 
> > 
> 
> > > > > s3: It would be much clearer if s3 was divided into 3 
sub-sections
> > > > > (possibly reordered):
> > > > > - PREFERRED to NOT PREFERRED transition
> > > > > - NOT PREFERRED to PREFERRED transition
> > > > > - Multi-segment case (which should refer to both previous cases)
> > > > > The pointer to the diagram in Appendix A could usefully occur in 
the
> > > > > introduction to s3.  If this was adopted s3.1 could either be a
> > > > fourth
> > > > > sub-section or a sub-sub-section of the PREFERRED to NOT 
PREFERRED
> > > > > section. 
> > > > [Lizhong] PREFERRED to NOT PREFERRED does not introduce any new.
> > > > Multi-segment case is fully inherited from single-segment case. It
> > > > would be redundancy to have sub-sections here. 
> > > I disagree strongly.  The multi-segment case affects the other RFC 
and
> > > needs to be made to stand out so that implementors can see where the
> > > changes occur.  The PREFERRED to NOT PREFERRED case also ought to be
> > > separated whether or not I am right about this case. 
> > [Lizhong] how about only divide multi-segment? The case of PREFERRED 
to 
> > NOT PREFERRED case is only for reference, and the text is not many.
> That is so, but it is a change of subject and the fact that it will then
> be in the table of contents makes it easier for implementors to find the
> relevant text.  I wouldn't call it 'redundant'.
> 
> > > > > s3, last para/Appendix A:  The diagram doesn't cover the 
PREFERRED
> > > > to
> > > > > NOT PREFERRED transition. 
> > > > [Lizhong] no, there is a "no" branch under "NOT Preferred to
> > > > Preferred" to cover "PREFERRED to NOT PREFERRED". Anyway, the 
diagram
> > > > discription should be "NOT Preferred to Preferred" which is wrong 
in
> > > > v-04. 
> Need to check it reflects the Label Withdraw message needed in the
> PREFERRED to NOT PREFERRED case. 
[Lizhong] ok, I could add Label Withdraw there.
> 
> 
> 

--=_alternative 005100E948257A24_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Elwyn,</font>
<br><font size=2 face="sans-serif">Please see inline below.</font>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br>
<br>
<br><font size=2 face="sans-serif">Elwyn Davies &lt;elwynd@folly.org.uk&gt;
wrote 2012/06/21 20:38:27:<br>
<br>
&gt; Hi, Lizhong.<br>
&gt; <br>
&gt; I have removed the bits that we are agreed on to shorten the mail
a bit.<br>
&gt; <br>
&gt; I don't think we have converged just yet.<br>
&gt; <br>
&gt; Regards,<br>
&gt; Elwyn<br>
&gt; <br>
&gt; On Wed, 2012-06-20 at 01:17 +0800, Lizhong Jin wrote:<br>
&gt; &gt; <br>
&gt; &gt; Hi Elwyn, <br>
&gt; &gt; Thank you for the prompt reply. See inline below. <br>
&gt; &gt; <br>
&gt; &gt; Lizhong <br>
&gt; &gt; &nbsp; <br>
&gt; &gt; <br>
&gt; &gt; Elwyn Davies &lt;elwynd@folly.org.uk&gt; wrote 2012/06/19 23:16:08:<br>
&gt; &gt; &gt; &gt; &gt; Document: draft-ietf-pwe3-cbit-negotiation-04.txt<br>
&gt; &gt; &gt; &gt; &gt; Reviewer: Elwyn Davies<br>
&gt; &gt; &gt; &gt; &gt; Review Date: 19 June 2012<br>
&gt; &gt; &gt; &gt; &gt; IETF LC End Date: 15 June 2012<br>
&gt; &gt; &gt; &gt; &gt; IESG Telechat date: 21 June 2012<br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; Summary: <br>
&gt; &gt; &gt; &gt; &gt; Not ready. The proposal for the NOT PREFERRED
to PREFERRED<br>
&gt; &gt; &gt; &gt; transition<br>
&gt; &gt; &gt; &gt; &gt; case does not appear to be compatible with the
existing RFC 4447<br>
&gt; &gt; &gt; &gt; &gt; standard in the way stated and there are a number
of other minor<br>
&gt; &gt; &gt; &gt; issues.<br>
&gt; &gt; &gt; &gt; &gt; The draft is also in need of an editing pass by
an author whose<br>
&gt; &gt; &gt; &gt; mother<br>
&gt; &gt; &gt; &gt; &gt; tongue is English as there are parts where the
syntax is misleading<br>
&gt; &gt; &gt; &gt; &gt; Major issues: <br>
&gt; &gt; &gt; &gt; &gt; s3: The discussion of the NOT PREFERRED to PREFERRED
transition case<br>
&gt; &gt; &gt; &gt; &gt; (buried at the end of s3 - causing me to ask 'what
about this case?'<br>
&gt; &gt; &gt; &gt; &gt; during reading of s2 and most of s3) &nbsp;implies
that some existing RFC<br>
&gt; &gt; &gt; &gt; &gt; 4447 procedure applies. Clearly, if the PW is
not using the control<br>
&gt; &gt; &gt; &gt; word<br>
&gt; &gt; &gt; &gt; &gt; then there is nothing to do. &nbsp;On the other
hand, inspection of s6.2<br>
&gt; &gt; &gt; &gt; of<br>
&gt; &gt; &gt; &gt; &gt; RFC4447 indicates that once the two PEs have agreed
on c = 1, 'setup<br>
&gt; &gt; &gt; &gt; is<br>
&gt; &gt; &gt; &gt; &gt; complete' and Label Mapping messages would therefore
be<br>
&gt; &gt; &gt; &gt; &gt; 'unexpected' (see item '-i' in second set of bullets
in s6.2 of RFC<br>
&gt; &gt; &gt; &gt; &gt; 4447). So, what procedure is to be used? And what
implications does<br>
&gt; &gt; &gt; &gt; this<br>
&gt; &gt; &gt; &gt; &gt; have for backwards compatibility? &nbsp;Wouldn't
it be generally simpler<br>
&gt; &gt; &gt; &gt; to<br>
&gt; &gt; &gt; &gt; &gt; apply the PREFERRED to NOT PREFERRED mechanism
to all case? <br>
&gt; &gt; &gt; &gt; [Lizhong] this draft is to solve the case to change
a PW from c=0 to<br>
&gt; &gt; &gt; &gt; c=1, that means one PE should change its use of control
word from NOT<br>
&gt; &gt; &gt; &gt; PREFERRED to PREFERRED. RFC4447 is already there and
deployed, and the<br>
&gt; &gt; &gt; &gt; PE will not always send its locally configured preferrence
according<br>
&gt; &gt; &gt; &gt; RFC4447, see PE1 behavior in section 2 step 1&amp;2.
That's why we could<br>
&gt; &gt; &gt; &gt; not simply apply the mechanism at the end of section
3. Hope it is<br>
&gt; &gt; &gt; &gt; clear. <br>
&gt; &gt; &gt; There are two issues here:<br>
&gt; &gt; &gt; - Clarity: RFC 4447 does not have any discussion of what
might happen if<br>
&gt; &gt; &gt; the configuration value changes. &nbsp;The draft focusses
on on transition<br>
&gt; &gt; &gt; direction but does not mention the other except for one
paragaph right<br>
&gt; &gt; &gt; at the end of s3. &nbsp;It is therefore reasonable that
somebody looking at<br>
&gt; &gt; &gt; this draft would wonder 'what about the other transition
direction?'.<br>
&gt; &gt; &gt; Whether or not anything needs to be done it would save people
wondering<br>
&gt; &gt; &gt; if you put in a sentence in the introduction to explain
that the other<br>
&gt; &gt; &gt; direction is not (or is) a problem. <br>
&gt; &gt; [Lizhong] accept. Add following: <br>
&gt; &gt; When PE changes the preference for the use of control word from<br>
&gt; &gt; PREFERRED to NOT PREFERRED, it should follow [RFC4447], and there
is<br>
&gt; &gt; no problem. <br>
&gt; <br>
&gt; See below...<br>
&gt; &gt; <br>
&gt; &gt; &gt; - Technical: The paragraph in s3 implies that the PREFERRED
to NOT<br>
&gt; &gt; &gt; PREFERRED direction will result in some part of the RFC
4447 protocol<br>
&gt; &gt; &gt; being (re-)invoked. &nbsp;What part is not made very clear.
&nbsp;As far as I can<br>
&gt; &gt; &gt; see sending more messages other than Label Release or Label
Withdraw for<br>
&gt; &gt; &gt; this PW is not part of the RFC 4447 protocol and hence will
cause an<br>
&gt; &gt; &gt; error. &nbsp;Alternatively if it isn't reinvoked, the PW
will continue to use<br>
&gt; &gt; &gt; control words. &nbsp;Please explain what is going on here.
&nbsp;The fact that RFC<br>
&gt; &gt; &gt; 4447 has been deployed doesn't explain what is going on.
<br>
&gt; &gt; [Lizhong] now I understand you concern. The last sentance of
s3 is not<br>
&gt; &gt; clear. How about the following: <br>
&gt; &gt; In that case, local PE will always send Label Withdraw message
if<br>
&gt; &gt; already sending Label Mapping message, and then send new Label
Mapping<br>
&gt; &gt; message with C-bit value following the procedures defined in<br>
&gt; &gt; [RFC4447]. <br>
&gt; <br>
&gt; I think we have reached the heart of the issue here: &nbsp;RFC 4447
does not<br>
&gt; mention changing the control word configuration. &nbsp;The combination
of the<br>
&gt; existing text in the draft and what you have just weittrn above<br>
&gt; indicates that *in both transition directions* the PE changing<br>
&gt; configuration notifies its peer by sending a Label Withdraw. It is
not<br>
&gt; immediately obvious to me that you could deduce this from RFC 4447
- if<br>
&gt; it is then there needs to be a pointer to the relevant section in
RFC<br>
&gt; 4447 to enlighten the ignorant like me. &nbsp;Otherwise the PREFERRED
to NOT<br>
&gt; PREFERRED transition is *not* just 'follow the RFC 4447 procedures'.</font>
<br><font size=2 face="sans-serif">[Lizhong] as an engineer, I interpret
the configuration changing as deleting and configuring again. Control word
configuration changing means deleting the old control word, and then configuring
the new control word, that means deleting PW configuration, and configuring
new PW configuration again. RFC4447 section 5.4.1 describe the procedure
of PW deletion and configuration. When you apply the above procedure to
PREFERRED to NOT PREFERRED transition, it works well, while for NOT PREFERRED
to PREFERRED transition, there is a problem.</font>
<br><font size=2 face="sans-serif">What if I add some description of the
meaning of control word changing at the end of s3, so as to make it clear?</font>
<br><font size=2 face="sans-serif"><br>
&gt; <br>
&gt; If I now understand correctly, the situation is as follows:<br>
&gt; - in both cases when there is a control word preference transition,
send<br>
&gt; a Label Withdraw.<br>
&gt; - in the NOT PREFERRED to PREFERRED case send Label Release also (order<br>
&gt; not important), wait for a responses from peer, then send Label Request<br>
&gt; and negotiate use of control word using Label Mapping C bit as for
a new<br>
&gt; PW (might result in either using or not using control word depending
on<br>
&gt; state in peer).<br>
&gt; - in the PREFERRED to NOT PREFERRED case, just negotiate C bit to
0<br>
&gt; using Label Mapping - label will be maintained. [Need to check that
RFC<br>
&gt; 4447 is expecting/will allow this sequence.]<br>
&gt; <br>
&gt; If I have this straight, I think that the PREFERRED to NOT PREFERRED<br>
&gt; case needs some more words in s3 and an introduction in s2. (And it<br>
&gt; would be easier to understand with this case in a separate sub-section
-<br>
&gt; sorry to harp on about this). &nbsp; </font>
<br><font size=2 face="sans-serif">[Lizhong] your above description is
totally right. How about changing the end of s3 as below:</font>
<br><font size=2 face="sans-serif">When Local PE changes the use of control
word from PREFERRED to NOT PREFERRED, the local PE would be able to negotiate
the Control Word to be not used by deleting the PW configuration with PREFERRED
use of control word, &nbsp;and configuring the PW again with NOT PREFERRED
use of control word. All of these procedures have been defined in [RFC4447]
section 5.4.1.</font>
<br><font size=2 face="sans-serif"><br>
&gt; <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; Minor issues: <br>
&gt; &gt; &gt; &gt; &gt; s3: Has there been any discussion on possible
race conditions?<br>
&gt; &gt; &gt; &gt; &nbsp;Changing<br>
&gt; &gt; &gt; &gt; &gt; the configuration value during the message exchange
strikes me as<br>
&gt; &gt; &gt; &gt; &gt; dangerous - it is probably sufficient to note
that changes should be<br>
&gt; &gt; &gt; &gt; &gt; suppressed during the Label Mapping message exchange
but I am not<br>
&gt; &gt; &gt; &gt; &gt; totally sure about this. <br>
&gt; &gt; &gt; &gt; [Lizhong] The message would be processed in sequence
in TCP-based LDP<br>
&gt; &gt; &gt; &gt; session. I do not see a problem here. But we do have
a note in section<br>
&gt; &gt; &gt; &gt; 3 for multi-segment PW for sequence processing. <br>
&gt; &gt; &gt; There are several network round trips in the message exchanges.
&nbsp;The<br>
&gt; &gt; &gt; protocol and the configuration mechanism in a PE are potentially<br>
&gt; &gt; &gt; separate threads. &nbsp;There is scope, depending on the
implementation, for<br>
&gt; &gt; &gt; the user at the 'remote' PE to change the configuration
during the<br>
&gt; &gt; &gt; message exchange making for a potential race condition.
<br>
&gt; &gt; [Lizhong] we discussed the race condition on the PWE3 maillist
from<br>
&gt; &gt; Spike, and for multi-segment PW, we add a note to ensure the
sequence<br>
&gt; &gt; processing for implementation.<br>
&gt; I look forward to the revised text.</font>
<br><font size=2 face="sans-serif">[Lizhong] How about add the following
in s3: for the local PE, before processing new configuration changing,
the above message exchange process should be finished.</font>
<br><font size=2 face="sans-serif"><br>
&gt; &gt; &nbsp;<br>
&gt; &gt; <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; s3, bullet '-i': &nbsp;I completely misparsed
this section on first<br>
&gt; &gt; &gt; &gt; reading<br>
&gt; &gt; &gt; &gt; &gt; and I am still not absolutely sure what message
sequence is being<br>
&gt; &gt; &gt; &gt; &gt; specified. &nbsp;Working back from later sections
I *think* that the<br>
&gt; &gt; &gt; &gt; &gt; intention is:<br>
&gt; &gt; &gt; &gt; &gt; IF Mapping sent THEN { send Withdraw; send Release;}<br>
&gt; &gt; &gt; &gt; &gt; Wait to receive Release<br>
&gt; &gt; &gt; &gt; &gt; The implication at present is that a Mapping might
not have been<br>
&gt; &gt; &gt; &gt; sent<br>
&gt; &gt; &gt; &gt; &gt; and then only a Release is needed: is this a possibility?
Please<br>
&gt; &gt; &gt; &gt; &gt; clarify.<br>
&gt; &gt; &gt; &gt; &gt; The picture in Appendix A suffers from the same
problem. <br>
&gt; &gt; &gt; &gt; [Lizhong] Adrian raise the same comment, and I change
it as below: <br>
&gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;-i. &nbsp;PE MUST send a
Label Release message to remote PE. If a<br>
&gt; &gt; &gt; &gt; PE <br>
&gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; has previously
sent a Label Mapping message to a remote<br>
&gt; &gt; &gt; &gt; PE, <br>
&gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; it MUST also
send a Label Withdraw message to the remote<br>
&gt; &gt; &gt; &gt; PE, <br>
&gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and wait
until it receives a Label Release message from<br>
&gt; &gt; &gt; &gt; the<br>
&gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;remote PE.
<br>
&gt; &gt; &gt; What does it send first if both must be sent? &nbsp;The
text in the rest of<br>
&gt; &gt; &gt; the document implies withdraw then release. &nbsp;This new
text sort of<br>
&gt; &gt; &gt; implies release then withdraw but isn't really clear. <br>
&gt; &gt; [Lizhong] both should be sent, and does not require the sending<br>
&gt; &gt; sequence. The two messages does not have dependence. <br>
&gt; In that case, it is important to say so.</font>
<br><font size=2 face="sans-serif">[Lizhong] I will add a sentence in point
&quot;i&quot; to say so. How about below:</font>
<br><font size=2 face="sans-serif">Note: above Label Release message and
Label Withdraw message sending does not require specific sequence.</font>
<br><font size=2 face="sans-serif"><br>
&gt; &gt; <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; s3, discussion of multi-segment PWs: The statement
that S-PE's<br>
&gt; &gt; &gt; &gt; SHOULD<br>
&gt; &gt; &gt; &gt; &gt; assume an initial passive role seems to have several
problems:<br>
&gt; &gt; &gt; &gt; &gt; - Does this mean that changing the configuration
of an S-PE would<br>
&gt; &gt; &gt; &gt; not<br>
&gt; &gt; &gt; &gt; &gt; provoke the new mechanisms?<br>
&gt; &gt; &gt; &gt; &gt; - The passive role situation is only specified
for some sorts of<br>
&gt; &gt; &gt; &gt; linked<br>
&gt; &gt; &gt; &gt; &gt; FECs in RFC 6073 - what about other cases?<br>
&gt; &gt; &gt; &gt; &gt; - What are the consequences for ignoring the SHOULD
in this case? (I<br>
&gt; &gt; &gt; &gt; &gt; have to say I am unsure that RFC 6073 deals with
this problem<br>
&gt; &gt; &gt; &gt; either.) <br>
&gt; &gt; &gt; &gt; [Lizhong] we follow RFC6073, and passive role is only
applied for the<br>
&gt; &gt; &gt; &gt; PW FEC, other cases are out of scope. <br>
&gt; &gt; &gt; Why? This needs an explanation. Also this doesn't cover
the point about<br>
&gt; &gt; &gt; whether reconfig of an S-PE is allowed and how this squares
with the<br>
&gt; &gt; &gt; passive role.<br>
&gt; &gt; &gt; &gt; SHOULD means highly recommended. We do not meet any
problem when<br>
&gt; &gt; &gt; &gt; implementing RFC6073. Do you suggest to change this
to MUST? <br>
&gt; &gt; &gt; Whenever a specification includes a 'SHOULD' the question
arises of what<br>
&gt; &gt; &gt; alternatives there might be and what is the reason for preferring
the<br>
&gt; &gt; &gt; suggested solution. &nbsp;In the original setup, it is fairly
clear that life<br>
&gt; &gt; &gt; is easier letting setup progress from &nbsp;one end to the
other (although<br>
&gt; &gt; &gt; this is not spelt out - I would have argued for this had
&nbsp;I reviewed the<br>
&gt; &gt; &gt; doc). &nbsp;For the configuration change this is less obvious.
&nbsp;Regarding the<br>
&gt; &gt; &gt; point about reconfig of the &nbsp;S-PE, it is going to make
life more<br>
&gt; &gt; &gt; complicated if the S-PE has to tell the T-PE to be active
so it can be<br>
&gt; &gt; &gt; passive. &nbsp;I would therefore argue that probably the
notion of passivity<br>
&gt; &gt; &gt; is irrelevant to the transition use case. &nbsp;Whether
it should be SHOULD<br>
&gt; &gt; &gt; or MUST is therefore moot. <br>
&gt; &gt; [Lizhong] how about the following? Because we just refer to <br>
&gt; RFC6073, and does not add anything new. <br>
&gt; &gt; An initial passive role is defined in [RFC6073] for S-PE.<br>
&gt; I can't see that this really helps.<br>
&gt; There are still two points at issue here:<br>
&gt; - Why are the cases other than the one in RFC 4447 that refers to
a<br>
&gt; passive S-PE out of scope? &nbsp;There aren't any statements to this
effect<br>
&gt; in the document.</font>
<br><font size=2 face="sans-serif">[Lizhong] the passive role is not for
any specific cases. The passive role is for the processing of message (e.g,
label mapping, label request). I will explicitly say that in the section.</font>
<br><font size=2 face="sans-serif"><br>
&gt; - It is difficult for a S-PE that has its control word configuration<br>
&gt; change to act passively. &nbsp;If it is really passive than nothing
will<br>
&gt; happen until the label is withdrawn. &nbsp;Otherwise it can't be descibed
as<br>
&gt; passive for this action. &nbsp;The text in the current draft actually<br>
&gt; describes what is specified in RFC 6073 when talking 'passive' rather<br>
&gt; than explaining what happens when the control word configuration<br>
&gt; changes.</font>
<br><font size=2 face="sans-serif">[Lizhong] the control word configuration
changing talking about in this draft only happens on T-PE, not S-PE. The
S-PE is a passive role for the message processing. I will make this clear
in the draft.</font>
<br><font size=2 face="sans-serif"><br>
&gt; &gt; &nbsp;<br>
&gt; &gt; &gt; &gt; [Lizhong] has been revised in v-04.<br>
&gt; &gt; &gt; Not as far as I can see. <br>
&gt; &gt; [Lizhong] write &quot;pseudowire&quot; directly in the text,
not PW. <br>
&gt; There are lots of instances of PW still left in v04. Expand acronym
=&gt;<br>
&gt; define what it means on first usage i.e pseudowire (PW). &nbsp;Same
for the<br>
&gt; various other acronyms that aren't defined in the text.</font>
<br><font size=2 face="sans-serif">[Lizhong] accept<br>
&gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; s2: Expand acronym PE. <br>
&gt; &gt; &gt; &gt; [Lizhong] accept <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; s2, 2nd sentence: s/configurable/configured/ <br>
&gt; &gt; &gt; &gt; [Lizhong] configurable is right. <br>
&gt; &gt; &gt; Leave that one to the RFc Editor.<br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; s2, 3rd and 4th sentences: I *think* this text
is trying to say: <br>
&gt; &gt; &gt; &gt; &gt; &nbsp; The intention of the control word negotiation
is that the control<br>
&gt; &gt; &gt; &gt; word<br>
&gt; &gt; &gt; &gt; &gt; will be used when both endpoints are configured
with control word<br>
&gt; &gt; &gt; &gt; usage<br>
&gt; &gt; &gt; &gt; &gt; PREFERRED. &nbsp;However if one endpoint is initially
configured with<br>
&gt; &gt; &gt; &gt; control<br>
&gt; &gt; &gt; &gt; &gt; word usage NOT PREFERRED but later changes to
PREFERRED, a PW<br>
&gt; &gt; &gt; &gt; between<br>
&gt; &gt; &gt; &gt; &gt; the endpoints will not transition to usage of
the control word as<br>
&gt; &gt; &gt; &gt; &gt; explained below. <br>
&gt; &gt; &gt; &gt; [Lizhong] no, the case is that operator deploys PW
with control word<br>
&gt; &gt; &gt; &gt; used in the first phase. In the second phase, they
want to upgrade<br>
&gt; &gt; &gt; &gt; their PW service to use control word. Two different
deployment<br>
&gt; &gt; &gt; &gt; timeframes.<br>
&gt; &gt; &gt; That is what my sentence says. <br>
&gt; &gt; [Lizhong] ok. <br>
&gt; &gt; <br>
&gt; <br>
&gt; &gt; &gt; &gt; &gt; s3: It would be much clearer if s3 was divided
into 3 sub-sections<br>
&gt; &gt; &gt; &gt; &gt; (possibly reordered):<br>
&gt; &gt; &gt; &gt; &gt; - PREFERRED to NOT PREFERRED transition<br>
&gt; &gt; &gt; &gt; &gt; - NOT PREFERRED to PREFERRED transition<br>
&gt; &gt; &gt; &gt; &gt; - Multi-segment case (which should refer to both
previous cases)<br>
&gt; &gt; &gt; &gt; &gt; The pointer to the diagram in Appendix A could
usefully occur in the<br>
&gt; &gt; &gt; &gt; &gt; introduction to s3. &nbsp;If this was adopted
s3.1 could either be a<br>
&gt; &gt; &gt; &gt; fourth<br>
&gt; &gt; &gt; &gt; &gt; sub-section or a sub-sub-section of the PREFERRED
to NOT PREFERRED<br>
&gt; &gt; &gt; &gt; &gt; section. <br>
&gt; &gt; &gt; &gt; [Lizhong] PREFERRED to NOT PREFERRED does not introduce
any new.<br>
&gt; &gt; &gt; &gt; Multi-segment case is fully inherited from single-segment
case. It<br>
&gt; &gt; &gt; &gt; would be redundancy to have sub-sections here. <br>
&gt; &gt; &gt; I disagree strongly. &nbsp;The multi-segment case affects
the other RFC and<br>
&gt; &gt; &gt; needs to be made to stand out so that implementors can see
where the<br>
&gt; &gt; &gt; changes occur. &nbsp;The PREFERRED to NOT PREFERRED case
also ought to be<br>
&gt; &gt; &gt; separated whether or not I am right about this case. <br>
&gt; &gt; [Lizhong] how about only divide multi-segment? The case of PREFERRED
to <br>
&gt; &gt; NOT PREFERRED case is only for reference, and the text is not
many.<br>
&gt; That is so, but it is a change of subject and the fact that it will
then<br>
&gt; be in the table of contents makes it easier for implementors to find
the<br>
&gt; relevant text. &nbsp;I wouldn't call it 'redundant'.<br>
&gt; <br>
&gt; &gt; &gt; &gt; &gt; s3, last para/Appendix A: &nbsp;The diagram doesn't
cover the PREFERRED<br>
&gt; &gt; &gt; &gt; to<br>
&gt; &gt; &gt; &gt; &gt; NOT PREFERRED transition. <br>
&gt; &gt; &gt; &gt; [Lizhong] no, there is a &quot;no&quot; branch under
&quot;NOT Preferred to<br>
&gt; &gt; &gt; &gt; Preferred&quot; to cover &quot;PREFERRED to NOT PREFERRED&quot;.
Anyway, the diagram<br>
&gt; &gt; &gt; &gt; discription should be &quot;NOT Preferred to Preferred&quot;
which is wrong in<br>
&gt; &gt; &gt; &gt; v-04. <br>
&gt; Need to check it reflects the Label Withdraw message needed in the<br>
&gt; PREFERRED to NOT PREFERRED case. </font>
<br><font size=2 face="sans-serif">[Lizhong] ok, I could add Label Withdraw
there.<br>
&gt; <br>
&gt; <br>
&gt; <br>
</font>
--=_alternative 005100E948257A24_=--


From stbryant@cisco.com  Thu Jun 21 08:08:46 2012
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87FA21F86E1; Thu, 21 Jun 2012 08:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zjo9GX8LbNbv; Thu, 21 Jun 2012 08:08:43 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1087A21F86F2; Thu, 21 Jun 2012 08:08:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=47224; q=dns/txt; s=iport; t=1340291322; x=1341500922; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=0P4x1SRaiEhvMShBMQ8sdxxthPa941Y4V77IJLVFEeU=; b=W+EOMWwDhMfT3GE5vHmg6h2dPjFyKYSRiOBX1Bi8DcnafBf+cSrv4T9c oYulEVgsyui2pz2ZQkUHpCbiPHp4AtZaHvyGCnXGzN++L8DlJCp+1SEYb yizHKBw6AuzanT6XF0lHkR9MVBOcnC5g6fcH1x7u6uhV1a6elpirUbiX/ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAFE440+rRDoI/2dsb2JhbABFizeqHIEHghgBAQEDARIBAgUBUA0BBQsLFAQJFgEBDQkDAgECAUUGDQEFAgEBFQIHh2QEAQuaCoNIEJxAiy4JEYYDA5FNg12OG4EEYoJggVUHAg
X-IronPort-AV: E=Sophos;i="4.77,451,1336348800"; d="scan'208,217";a="49731013"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 21 Jun 2012 15:08:40 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q5LF8cI2007118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jun 2012 15:08:40 GMT
Received: from dhcp-bdlk10-data-vlan300-64-103-106-107.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q5LF8aic021226; Thu, 21 Jun 2012 16:08:37 +0100 (BST)
Message-ID: <4FE338F5.9070504@cisco.com>
Date: Thu, 21 Jun 2012 16:08:37 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Lizhong Jin <lizhong.jin@zte.com.cn>
References: <OF6E7B2A91.233F1F7A-ON48257A24.004B6705-48257A24.005100EB@zte.com.cn>
In-Reply-To: <OF6E7B2A91.233F1F7A-ON48257A24.004B6705-48257A24.005100EB@zte.com.cn>
Content-Type: multipart/alternative; boundary="------------080708080409040104010706"
Cc: draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org, pwe3 <pwe3@ietf.org>, General Area Review Team <gen-art@ietf.org>, Elwyn Davies <elwynd@folly.org.uk>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-pwe3-cbit-negotiation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 15:08:47 -0000

This is a multi-part message in MIME format.
--------------080708080409040104010706
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Please can you continue this conversation with the PWE3
WG in the cc list so that it has the correct level of expert
oversight.

Thanks

Stewart

On 21/06/2012 15:43, Lizhong Jin wrote:
>
> Hi Elwyn,
> Please see inline below.
>
> Thanks
> Lizhong
>
>
> Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/21 20:38:27:
>
> > Hi, Lizhong.
> >
> > I have removed the bits that we are agreed on to shorten the mail a bit.
> >
> > I don't think we have converged just yet.
> >
> > Regards,
> > Elwyn
> >
> > On Wed, 2012-06-20 at 01:17 +0800, Lizhong Jin wrote:
> > >
> > > Hi Elwyn,
> > > Thank you for the prompt reply. See inline below.
> > >
> > > Lizhong
> > >
> > >
> > > Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/19 23:16:08:
> > > > > > Document: draft-ietf-pwe3-cbit-negotiation-04.txt
> > > > > > Reviewer: Elwyn Davies
> > > > > > Review Date: 19 June 2012
> > > > > > IETF LC End Date: 15 June 2012
> > > > > > IESG Telechat date: 21 June 2012
> > > > > >
> > > > > > Summary:
> > > > > > Not ready. The proposal for the NOT PREFERRED to PREFERRED
> > > > > transition
> > > > > > case does not appear to be compatible with the existing RFC 4447
> > > > > > standard in the way stated and there are a number of other minor
> > > > > issues.
> > > > > > The draft is also in need of an editing pass by an author whose
> > > > > mother
> > > > > > tongue is English as there are parts where the syntax is 
> misleading
> > > > > > Major issues:
> > > > > > s3: The discussion of the NOT PREFERRED to PREFERRED 
> transition case
> > > > > > (buried at the end of s3 - causing me to ask 'what about 
> this case?'
> > > > > > during reading of s2 and most of s3)  implies that some 
> existing RFC
> > > > > > 4447 procedure applies. Clearly, if the PW is not using the 
> control
> > > > > word
> > > > > > then there is nothing to do.  On the other hand, inspection 
> of s6.2
> > > > > of
> > > > > > RFC4447 indicates that once the two PEs have agreed on c = 
> 1, 'setup
> > > > > is
> > > > > > complete' and Label Mapping messages would therefore be
> > > > > > 'unexpected' (see item '-i' in second set of bullets in s6.2 
> of RFC
> > > > > > 4447). So, what procedure is to be used? And what 
> implications does
> > > > > this
> > > > > > have for backwards compatibility?  Wouldn't it be generally 
> simpler
> > > > > to
> > > > > > apply the PREFERRED to NOT PREFERRED mechanism to all case?
> > > > > [Lizhong] this draft is to solve the case to change a PW from 
> c=0 to
> > > > > c=1, that means one PE should change its use of control word 
> from NOT
> > > > > PREFERRED to PREFERRED. RFC4447 is already there and deployed, 
> and the
> > > > > PE will not always send its locally configured preferrence 
> according
> > > > > RFC4447, see PE1 behavior in section 2 step 1&2. That's why we 
> could
> > > > > not simply apply the mechanism at the end of section 3. Hope it is
> > > > > clear.
> > > > There are two issues here:
> > > > - Clarity: RFC 4447 does not have any discussion of what might 
> happen if
> > > > the configuration value changes.  The draft focusses on on 
> transition
> > > > direction but does not mention the other except for one paragaph 
> right
> > > > at the end of s3.  It is therefore reasonable that somebody 
> looking at
> > > > this draft would wonder 'what about the other transition 
> direction?'.
> > > > Whether or not anything needs to be done it would save people 
> wondering
> > > > if you put in a sentence in the introduction to explain that the 
> other
> > > > direction is not (or is) a problem.
> > > [Lizhong] accept. Add following:
> > > When PE changes the preference for the use of control word from
> > > PREFERRED to NOT PREFERRED, it should follow [RFC4447], and there is
> > > no problem.
> >
> > See below...
> > >
> > > > - Technical: The paragraph in s3 implies that the PREFERRED to NOT
> > > > PREFERRED direction will result in some part of the RFC 4447 
> protocol
> > > > being (re-)invoked.  What part is not made very clear.  As far 
> as I can
> > > > see sending more messages other than Label Release or Label 
> Withdraw for
> > > > this PW is not part of the RFC 4447 protocol and hence will cause an
> > > > error.  Alternatively if it isn't reinvoked, the PW will 
> continue to use
> > > > control words.  Please explain what is going on here.  The fact 
> that RFC
> > > > 4447 has been deployed doesn't explain what is going on.
> > > [Lizhong] now I understand you concern. The last sentance of s3 is not
> > > clear. How about the following:
> > > In that case, local PE will always send Label Withdraw message if
> > > already sending Label Mapping message, and then send new Label Mapping
> > > message with C-bit value following the procedures defined in
> > > [RFC4447].
> >
> > I think we have reached the heart of the issue here:  RFC 4447 does not
> > mention changing the control word configuration.  The combination of the
> > existing text in the draft and what you have just weittrn above
> > indicates that *in both transition directions* the PE changing
> > configuration notifies its peer by sending a Label Withdraw. It is not
> > immediately obvious to me that you could deduce this from RFC 4447 - if
> > it is then there needs to be a pointer to the relevant section in RFC
> > 4447 to enlighten the ignorant like me.  Otherwise the PREFERRED to NOT
> > PREFERRED transition is *not* just 'follow the RFC 4447 procedures'.
> [Lizhong] as an engineer, I interpret the configuration changing as 
> deleting and configuring again. Control word configuration changing 
> means deleting the old control word, and then configuring the new 
> control word, that means deleting PW configuration, and configuring 
> new PW configuration again. RFC4447 section 5.4.1 describe the 
> procedure of PW deletion and configuration. When you apply the above 
> procedure to PREFERRED to NOT PREFERRED transition, it works well, 
> while for NOT PREFERRED to PREFERRED transition, there is a problem.
> What if I add some description of the meaning of control word changing 
> at the end of s3, so as to make it clear?
>
> >
> > If I now understand correctly, the situation is as follows:
> > - in both cases when there is a control word preference transition, send
> > a Label Withdraw.
> > - in the NOT PREFERRED to PREFERRED case send Label Release also (order
> > not important), wait for a responses from peer, then send Label Request
> > and negotiate use of control word using Label Mapping C bit as for a new
> > PW (might result in either using or not using control word depending on
> > state in peer).
> > - in the PREFERRED to NOT PREFERRED case, just negotiate C bit to 0
> > using Label Mapping - label will be maintained. [Need to check that RFC
> > 4447 is expecting/will allow this sequence.]
> >
> > If I have this straight, I think that the PREFERRED to NOT PREFERRED
> > case needs some more words in s3 and an introduction in s2. (And it
> > would be easier to understand with this case in a separate sub-section -
> > sorry to harp on about this).
> [Lizhong] your above description is totally right. How about changing 
> the end of s3 as below:
> When Local PE changes the use of control word from PREFERRED to NOT 
> PREFERRED, the local PE would be able to negotiate the Control Word to 
> be not used by deleting the PW configuration with PREFERRED use of 
> control word,  and configuring the PW again with NOT PREFERRED use of 
> control word. All of these procedures have been defined in [RFC4447] 
> section 5.4.1.
>
> >
> > > > >
> > > > > >
> > > > > > Minor issues:
> > > > > > s3: Has there been any discussion on possible race conditions?
> > > > >  Changing
> > > > > > the configuration value during the message exchange strikes 
> me as
> > > > > > dangerous - it is probably sufficient to note that changes 
> should be
> > > > > > suppressed during the Label Mapping message exchange but I 
> am not
> > > > > > totally sure about this.
> > > > > [Lizhong] The message would be processed in sequence in 
> TCP-based LDP
> > > > > session. I do not see a problem here. But we do have a note in 
> section
> > > > > 3 for multi-segment PW for sequence processing.
> > > > There are several network round trips in the message exchanges.  The
> > > > protocol and the configuration mechanism in a PE are potentially
> > > > separate threads.  There is scope, depending on the 
> implementation, for
> > > > the user at the 'remote' PE to change the configuration during the
> > > > message exchange making for a potential race condition.
> > > [Lizhong] we discussed the race condition on the PWE3 maillist from
> > > Spike, and for multi-segment PW, we add a note to ensure the sequence
> > > processing for implementation.
> > I look forward to the revised text.
> [Lizhong] How about add the following in s3: for the local PE, before 
> processing new configuration changing, the above message exchange 
> process should be finished.
>
> > >
> > >
> > > > >
> > > > > >
> > > > > > s3, bullet '-i':  I completely misparsed this section on first
> > > > > reading
> > > > > > and I am still not absolutely sure what message sequence is 
> being
> > > > > > specified.  Working back from later sections I *think* that the
> > > > > > intention is:
> > > > > > IF Mapping sent THEN { send Withdraw; send Release;}
> > > > > > Wait to receive Release
> > > > > > The implication at present is that a Mapping might not have been
> > > > > sent
> > > > > > and then only a Release is needed: is this a possibility? Please
> > > > > > clarify.
> > > > > > The picture in Appendix A suffers from the same problem.
> > > > > [Lizhong] Adrian raise the same comment, and I change it as 
> below:
> > > > >        -i.  PE MUST send a Label Release message to remote PE. 
> If a
> > > > > PE
> > > > >             has previously sent a Label Mapping message to a 
> remote
> > > > > PE,
> > > > >             it MUST also send a Label Withdraw message to the 
> remote
> > > > > PE,
> > > > >             and wait until it receives a Label Release message 
> from
> > > > > the
> > > > >            remote PE.
> > > > What does it send first if both must be sent?  The text in the 
> rest of
> > > > the document implies withdraw then release.  This new text sort of
> > > > implies release then withdraw but isn't really clear.
> > > [Lizhong] both should be sent, and does not require the sending
> > > sequence. The two messages does not have dependence.
> > In that case, it is important to say so.
> [Lizhong] I will add a sentence in point "i" to say so. How about below:
> Note: above Label Release message and Label Withdraw message sending 
> does not require specific sequence.
>
> > >
> > > > >
> > > > > >
> > > > > > s3, discussion of multi-segment PWs: The statement that S-PE's
> > > > > SHOULD
> > > > > > assume an initial passive role seems to have several problems:
> > > > > > - Does this mean that changing the configuration of an S-PE 
> would
> > > > > not
> > > > > > provoke the new mechanisms?
> > > > > > - The passive role situation is only specified for some sorts of
> > > > > linked
> > > > > > FECs in RFC 6073 - what about other cases?
> > > > > > - What are the consequences for ignoring the SHOULD in this 
> case? (I
> > > > > > have to say I am unsure that RFC 6073 deals with this problem
> > > > > either.)
> > > > > [Lizhong] we follow RFC6073, and passive role is only applied 
> for the
> > > > > PW FEC, other cases are out of scope.
> > > > Why? This needs an explanation. Also this doesn't cover the 
> point about
> > > > whether reconfig of an S-PE is allowed and how this squares with the
> > > > passive role.
> > > > > SHOULD means highly recommended. We do not meet any problem when
> > > > > implementing RFC6073. Do you suggest to change this to MUST?
> > > > Whenever a specification includes a 'SHOULD' the question arises 
> of what
> > > > alternatives there might be and what is the reason for 
> preferring the
> > > > suggested solution.  In the original setup, it is fairly clear 
> that life
> > > > is easier letting setup progress from  one end to the other 
> (although
> > > > this is not spelt out - I would have argued for this had  I 
> reviewed the
> > > > doc).  For the configuration change this is less obvious. 
>  Regarding the
> > > > point about reconfig of the  S-PE, it is going to make life more
> > > > complicated if the S-PE has to tell the T-PE to be active so it 
> can be
> > > > passive.  I would therefore argue that probably the notion of 
> passivity
> > > > is irrelevant to the transition use case.  Whether it should be 
> SHOULD
> > > > or MUST is therefore moot.
> > > [Lizhong] how about the following? Because we just refer to
> > RFC6073, and does not add anything new.
> > > An initial passive role is defined in [RFC6073] for S-PE.
> > I can't see that this really helps.
> > There are still two points at issue here:
> > - Why are the cases other than the one in RFC 4447 that refers to a
> > passive S-PE out of scope?  There aren't any statements to this effect
> > in the document.
> [Lizhong] the passive role is not for any specific cases. The passive 
> role is for the processing of message (e.g, label mapping, label 
> request). I will explicitly say that in the section.
>
> > - It is difficult for a S-PE that has its control word configuration
> > change to act passively.  If it is really passive than nothing will
> > happen until the label is withdrawn.  Otherwise it can't be descibed as
> > passive for this action.  The text in the current draft actually
> > describes what is specified in RFC 6073 when talking 'passive' rather
> > than explaining what happens when the control word configuration
> > changes.
> [Lizhong] the control word configuration changing talking about in 
> this draft only happens on T-PE, not S-PE. The S-PE is a passive role 
> for the message processing. I will make this clear in the draft.
>
> > >
> > > > > [Lizhong] has been revised in v-04.
> > > > Not as far as I can see.
> > > [Lizhong] write "pseudowire" directly in the text, not PW.
> > There are lots of instances of PW still left in v04. Expand acronym =>
> > define what it means on first usage i.e pseudowire (PW).  Same for the
> > various other acronyms that aren't defined in the text.
> [Lizhong] accept
> > >
> > > > > >
> > > > > > s2: Expand acronym PE.
> > > > > [Lizhong] accept
> > > > >
> > > > > > s2, 2nd sentence: s/configurable/configured/
> > > > > [Lizhong] configurable is right.
> > > > Leave that one to the RFc Editor.
> > > > >
> > > > > > s2, 3rd and 4th sentences: I *think* this text is trying to 
> say:
> > > > > >   The intention of the control word negotiation is that the 
> control
> > > > > word
> > > > > > will be used when both endpoints are configured with control 
> word
> > > > > usage
> > > > > > PREFERRED.  However if one endpoint is initially configured with
> > > > > control
> > > > > > word usage NOT PREFERRED but later changes to PREFERRED, a PW
> > > > > between
> > > > > > the endpoints will not transition to usage of the control 
> word as
> > > > > > explained below.
> > > > > [Lizhong] no, the case is that operator deploys PW with 
> control word
> > > > > used in the first phase. In the second phase, they want to upgrade
> > > > > their PW service to use control word. Two different deployment
> > > > > timeframes.
> > > > That is what my sentence says.
> > > [Lizhong] ok.
> > >
> >
> > > > > > s3: It would be much clearer if s3 was divided into 3 
> sub-sections
> > > > > > (possibly reordered):
> > > > > > - PREFERRED to NOT PREFERRED transition
> > > > > > - NOT PREFERRED to PREFERRED transition
> > > > > > - Multi-segment case (which should refer to both previous cases)
> > > > > > The pointer to the diagram in Appendix A could usefully 
> occur in the
> > > > > > introduction to s3.  If this was adopted s3.1 could either be a
> > > > > fourth
> > > > > > sub-section or a sub-sub-section of the PREFERRED to NOT 
> PREFERRED
> > > > > > section.
> > > > > [Lizhong] PREFERRED to NOT PREFERRED does not introduce any new.
> > > > > Multi-segment case is fully inherited from single-segment case. It
> > > > > would be redundancy to have sub-sections here.
> > > > I disagree strongly.  The multi-segment case affects the other 
> RFC and
> > > > needs to be made to stand out so that implementors can see where the
> > > > changes occur.  The PREFERRED to NOT PREFERRED case also ought to be
> > > > separated whether or not I am right about this case.
> > > [Lizhong] how about only divide multi-segment? The case of 
> PREFERRED to
> > > NOT PREFERRED case is only for reference, and the text is not many.
> > That is so, but it is a change of subject and the fact that it will then
> > be in the table of contents makes it easier for implementors to find the
> > relevant text.  I wouldn't call it 'redundant'.
> >
> > > > > > s3, last para/Appendix A:  The diagram doesn't cover the 
> PREFERRED
> > > > > to
> > > > > > NOT PREFERRED transition.
> > > > > [Lizhong] no, there is a "no" branch under "NOT Preferred to
> > > > > Preferred" to cover "PREFERRED to NOT PREFERRED". Anyway, the 
> diagram
> > > > > discription should be "NOT Preferred to Preferred" which is 
> wrong in
> > > > > v-04.
> > Need to check it reflects the Label Withdraw message needed in the
> > PREFERRED to NOT PREFERRED case.
> [Lizhong] ok, I could add Label Withdraw there.
> >
> >
> >


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--------------080708080409040104010706
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Please can you continue this
      conversation with the PWE3 <br>
      WG in the cc list so that it has the correct level of expert<br>
      oversight.<br>
      <br>
      Thanks<br>
      <br>
      Stewart<br>
      <br>
      On 21/06/2012 15:43, Lizhong Jin wrote:<br>
    </div>
    <blockquote
cite="mid:OF6E7B2A91.233F1F7A-ON48257A24.004B6705-48257A24.005100EB@zte.com.cn"
      type="cite">
      <br>
      <font face="sans-serif" size="2">Hi Elwyn,</font>
      <br>
      <font face="sans-serif" size="2">Please see inline below.</font>
      <br>
      <br>
      <font face="sans-serif" size="2">Thanks</font>
      <br>
      <font face="sans-serif" size="2">Lizhong</font>
      <br>
      <br>
      <br>
      <font face="sans-serif" size="2">Elwyn Davies
        <a class="moz-txt-link-rfc2396E" href="mailto:elwynd@folly.org.uk">&lt;elwynd@folly.org.uk&gt;</a>
        wrote 2012/06/21 20:38:27:<br>
        <br>
        &gt; Hi, Lizhong.<br>
        &gt; <br>
        &gt; I have removed the bits that we are agreed on to shorten
        the mail
        a bit.<br>
        &gt; <br>
        &gt; I don't think we have converged just yet.<br>
        &gt; <br>
        &gt; Regards,<br>
        &gt; Elwyn<br>
        &gt; <br>
        &gt; On Wed, 2012-06-20 at 01:17 +0800, Lizhong Jin wrote:<br>
        &gt; &gt; <br>
        &gt; &gt; Hi Elwyn, <br>
        &gt; &gt; Thank you for the prompt reply. See inline below. <br>
        &gt; &gt; <br>
        &gt; &gt; Lizhong <br>
        &gt; &gt; &nbsp; <br>
        &gt; &gt; <br>
        &gt; &gt; Elwyn Davies <a class="moz-txt-link-rfc2396E" href="mailto:elwynd@folly.org.uk">&lt;elwynd@folly.org.uk&gt;</a> wrote
        2012/06/19 23:16:08:<br>
        &gt; &gt; &gt; &gt; &gt; Document:
        draft-ietf-pwe3-cbit-negotiation-04.txt<br>
        &gt; &gt; &gt; &gt; &gt; Reviewer: Elwyn Davies<br>
        &gt; &gt; &gt; &gt; &gt; Review Date: 19 June 2012<br>
        &gt; &gt; &gt; &gt; &gt; IETF LC End Date: 15 June 2012<br>
        &gt; &gt; &gt; &gt; &gt; IESG Telechat date: 21 June 2012<br>
        &gt; &gt; &gt; &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; Summary: <br>
        &gt; &gt; &gt; &gt; &gt; Not ready. The proposal for the NOT
        PREFERRED
        to PREFERRED<br>
        &gt; &gt; &gt; &gt; transition<br>
        &gt; &gt; &gt; &gt; &gt; case does not appear to be compatible
        with the
        existing RFC 4447<br>
        &gt; &gt; &gt; &gt; &gt; standard in the way stated and there
        are a number
        of other minor<br>
        &gt; &gt; &gt; &gt; issues.<br>
        &gt; &gt; &gt; &gt; &gt; The draft is also in need of an editing
        pass by
        an author whose<br>
        &gt; &gt; &gt; &gt; mother<br>
        &gt; &gt; &gt; &gt; &gt; tongue is English as there are parts
        where the
        syntax is misleading<br>
        &gt; &gt; &gt; &gt; &gt; Major issues: <br>
        &gt; &gt; &gt; &gt; &gt; s3: The discussion of the NOT PREFERRED
        to PREFERRED
        transition case<br>
        &gt; &gt; &gt; &gt; &gt; (buried at the end of s3 - causing me
        to ask 'what
        about this case?'<br>
        &gt; &gt; &gt; &gt; &gt; during reading of s2 and most of s3)
        &nbsp;implies
        that some existing RFC<br>
        &gt; &gt; &gt; &gt; &gt; 4447 procedure applies. Clearly, if the
        PW is
        not using the control<br>
        &gt; &gt; &gt; &gt; word<br>
        &gt; &gt; &gt; &gt; &gt; then there is nothing to do. &nbsp;On the
        other
        hand, inspection of s6.2<br>
        &gt; &gt; &gt; &gt; of<br>
        &gt; &gt; &gt; &gt; &gt; RFC4447 indicates that once the two PEs
        have agreed
        on c = 1, 'setup<br>
        &gt; &gt; &gt; &gt; is<br>
        &gt; &gt; &gt; &gt; &gt; complete' and Label Mapping messages
        would therefore
        be<br>
        &gt; &gt; &gt; &gt; &gt; 'unexpected' (see item '-i' in second
        set of bullets
        in s6.2 of RFC<br>
        &gt; &gt; &gt; &gt; &gt; 4447). So, what procedure is to be
        used? And what
        implications does<br>
        &gt; &gt; &gt; &gt; this<br>
        &gt; &gt; &gt; &gt; &gt; have for backwards compatibility?
        &nbsp;Wouldn't
        it be generally simpler<br>
        &gt; &gt; &gt; &gt; to<br>
        &gt; &gt; &gt; &gt; &gt; apply the PREFERRED to NOT PREFERRED
        mechanism
        to all case? <br>
        &gt; &gt; &gt; &gt; [Lizhong] this draft is to solve the case to
        change
        a PW from c=0 to<br>
        &gt; &gt; &gt; &gt; c=1, that means one PE should change its use
        of control
        word from NOT<br>
        &gt; &gt; &gt; &gt; PREFERRED to PREFERRED. RFC4447 is already
        there and
        deployed, and the<br>
        &gt; &gt; &gt; &gt; PE will not always send its locally
        configured preferrence
        according<br>
        &gt; &gt; &gt; &gt; RFC4447, see PE1 behavior in section 2 step
        1&amp;2.
        That's why we could<br>
        &gt; &gt; &gt; &gt; not simply apply the mechanism at the end of
        section
        3. Hope it is<br>
        &gt; &gt; &gt; &gt; clear. <br>
        &gt; &gt; &gt; There are two issues here:<br>
        &gt; &gt; &gt; - Clarity: RFC 4447 does not have any discussion
        of what
        might happen if<br>
        &gt; &gt; &gt; the configuration value changes. &nbsp;The draft
        focusses
        on on transition<br>
        &gt; &gt; &gt; direction but does not mention the other except
        for one
        paragaph right<br>
        &gt; &gt; &gt; at the end of s3. &nbsp;It is therefore reasonable
        that
        somebody looking at<br>
        &gt; &gt; &gt; this draft would wonder 'what about the other
        transition
        direction?'.<br>
        &gt; &gt; &gt; Whether or not anything needs to be done it would
        save people
        wondering<br>
        &gt; &gt; &gt; if you put in a sentence in the introduction to
        explain
        that the other<br>
        &gt; &gt; &gt; direction is not (or is) a problem. <br>
        &gt; &gt; [Lizhong] accept. Add following: <br>
        &gt; &gt; When PE changes the preference for the use of control
        word from<br>
        &gt; &gt; PREFERRED to NOT PREFERRED, it should follow
        [RFC4447], and there
        is<br>
        &gt; &gt; no problem. <br>
        &gt; <br>
        &gt; See below...<br>
        &gt; &gt; <br>
        &gt; &gt; &gt; - Technical: The paragraph in s3 implies that the
        PREFERRED
        to NOT<br>
        &gt; &gt; &gt; PREFERRED direction will result in some part of
        the RFC
        4447 protocol<br>
        &gt; &gt; &gt; being (re-)invoked. &nbsp;What part is not made very
        clear.
        &nbsp;As far as I can<br>
        &gt; &gt; &gt; see sending more messages other than Label
        Release or Label
        Withdraw for<br>
        &gt; &gt; &gt; this PW is not part of the RFC 4447 protocol and
        hence will
        cause an<br>
        &gt; &gt; &gt; error. &nbsp;Alternatively if it isn't reinvoked, the
        PW
        will continue to use<br>
        &gt; &gt; &gt; control words. &nbsp;Please explain what is going on
        here.
        &nbsp;The fact that RFC<br>
        &gt; &gt; &gt; 4447 has been deployed doesn't explain what is
        going on.
        <br>
        &gt; &gt; [Lizhong] now I understand you concern. The last
        sentance of
        s3 is not<br>
        &gt; &gt; clear. How about the following: <br>
        &gt; &gt; In that case, local PE will always send Label Withdraw
        message
        if<br>
        &gt; &gt; already sending Label Mapping message, and then send
        new Label
        Mapping<br>
        &gt; &gt; message with C-bit value following the procedures
        defined in<br>
        &gt; &gt; [RFC4447]. <br>
        &gt; <br>
        &gt; I think we have reached the heart of the issue here: &nbsp;RFC
        4447
        does not<br>
        &gt; mention changing the control word configuration. &nbsp;The
        combination
        of the<br>
        &gt; existing text in the draft and what you have just weittrn
        above<br>
        &gt; indicates that *in both transition directions* the PE
        changing<br>
        &gt; configuration notifies its peer by sending a Label
        Withdraw. It is
        not<br>
        &gt; immediately obvious to me that you could deduce this from
        RFC 4447
        - if<br>
        &gt; it is then there needs to be a pointer to the relevant
        section in
        RFC<br>
        &gt; 4447 to enlighten the ignorant like me. &nbsp;Otherwise the
        PREFERRED
        to NOT<br>
        &gt; PREFERRED transition is *not* just 'follow the RFC 4447
        procedures'.</font>
      <br>
      <font face="sans-serif" size="2">[Lizhong] as an engineer, I
        interpret
        the configuration changing as deleting and configuring again.
        Control word
        configuration changing means deleting the old control word, and
        then configuring
        the new control word, that means deleting PW configuration, and
        configuring
        new PW configuration again. RFC4447 section 5.4.1 describe the
        procedure
        of PW deletion and configuration. When you apply the above
        procedure to
        PREFERRED to NOT PREFERRED transition, it works well, while for
        NOT PREFERRED
        to PREFERRED transition, there is a problem.</font>
      <br>
      <font face="sans-serif" size="2">What if I add some description of
        the
        meaning of control word changing at the end of s3, so as to make
        it clear?</font>
      <br>
      <font face="sans-serif" size="2"><br>
        &gt; <br>
        &gt; If I now understand correctly, the situation is as follows:<br>
        &gt; - in both cases when there is a control word preference
        transition,
        send<br>
        &gt; a Label Withdraw.<br>
        &gt; - in the NOT PREFERRED to PREFERRED case send Label Release
        also (order<br>
        &gt; not important), wait for a responses from peer, then send
        Label Request<br>
        &gt; and negotiate use of control word using Label Mapping C bit
        as for
        a new<br>
        &gt; PW (might result in either using or not using control word
        depending
        on<br>
        &gt; state in peer).<br>
        &gt; - in the PREFERRED to NOT PREFERRED case, just negotiate C
        bit to
        0<br>
        &gt; using Label Mapping - label will be maintained. [Need to
        check that
        RFC<br>
        &gt; 4447 is expecting/will allow this sequence.]<br>
        &gt; <br>
        &gt; If I have this straight, I think that the PREFERRED to NOT
        PREFERRED<br>
        &gt; case needs some more words in s3 and an introduction in s2.
        (And it<br>
        &gt; would be easier to understand with this case in a separate
        sub-section
        -<br>
        &gt; sorry to harp on about this). &nbsp; </font>
      <br>
      <font face="sans-serif" size="2">[Lizhong] your above description
        is
        totally right. How about changing the end of s3 as below:</font>
      <br>
      <font face="sans-serif" size="2">When Local PE changes the use of
        control
        word from PREFERRED to NOT PREFERRED, the local PE would be able
        to negotiate
        the Control Word to be not used by deleting the PW configuration
        with PREFERRED
        use of control word, &nbsp;and configuring the PW again with NOT
        PREFERRED
        use of control word. All of these procedures have been defined
        in [RFC4447]
        section 5.4.1.</font>
      <br>
      <font face="sans-serif" size="2"><br>
        &gt; <br>
        &gt; &gt; &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; Minor issues: <br>
        &gt; &gt; &gt; &gt; &gt; s3: Has there been any discussion on
        possible
        race conditions?<br>
        &gt; &gt; &gt; &gt; &nbsp;Changing<br>
        &gt; &gt; &gt; &gt; &gt; the configuration value during the
        message exchange
        strikes me as<br>
        &gt; &gt; &gt; &gt; &gt; dangerous - it is probably sufficient
        to note
        that changes should be<br>
        &gt; &gt; &gt; &gt; &gt; suppressed during the Label Mapping
        message exchange
        but I am not<br>
        &gt; &gt; &gt; &gt; &gt; totally sure about this. <br>
        &gt; &gt; &gt; &gt; [Lizhong] The message would be processed in
        sequence
        in TCP-based LDP<br>
        &gt; &gt; &gt; &gt; session. I do not see a problem here. But we
        do have
        a note in section<br>
        &gt; &gt; &gt; &gt; 3 for multi-segment PW for sequence
        processing. <br>
        &gt; &gt; &gt; There are several network round trips in the
        message exchanges.
        &nbsp;The<br>
        &gt; &gt; &gt; protocol and the configuration mechanism in a PE
        are potentially<br>
        &gt; &gt; &gt; separate threads. &nbsp;There is scope, depending on
        the
        implementation, for<br>
        &gt; &gt; &gt; the user at the 'remote' PE to change the
        configuration
        during the<br>
        &gt; &gt; &gt; message exchange making for a potential race
        condition.
        <br>
        &gt; &gt; [Lizhong] we discussed the race condition on the PWE3
        maillist
        from<br>
        &gt; &gt; Spike, and for multi-segment PW, we add a note to
        ensure the
        sequence<br>
        &gt; &gt; processing for implementation.<br>
        &gt; I look forward to the revised text.</font>
      <br>
      <font face="sans-serif" size="2">[Lizhong] How about add the
        following
        in s3: for the local PE, before processing new configuration
        changing,
        the above message exchange process should be finished.</font>
      <br>
      <font face="sans-serif" size="2"><br>
        &gt; &gt; &nbsp;<br>
        &gt; &gt; <br>
        &gt; &gt; &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; s3, bullet '-i': &nbsp;I completely
        misparsed
        this section on first<br>
        &gt; &gt; &gt; &gt; reading<br>
        &gt; &gt; &gt; &gt; &gt; and I am still not absolutely sure what
        message
        sequence is being<br>
        &gt; &gt; &gt; &gt; &gt; specified. &nbsp;Working back from later
        sections
        I *think* that the<br>
        &gt; &gt; &gt; &gt; &gt; intention is:<br>
        &gt; &gt; &gt; &gt; &gt; IF Mapping sent THEN { send Withdraw;
        send Release;}<br>
        &gt; &gt; &gt; &gt; &gt; Wait to receive Release<br>
        &gt; &gt; &gt; &gt; &gt; The implication at present is that a
        Mapping might
        not have been<br>
        &gt; &gt; &gt; &gt; sent<br>
        &gt; &gt; &gt; &gt; &gt; and then only a Release is needed: is
        this a possibility?
        Please<br>
        &gt; &gt; &gt; &gt; &gt; clarify.<br>
        &gt; &gt; &gt; &gt; &gt; The picture in Appendix A suffers from
        the same
        problem. <br>
        &gt; &gt; &gt; &gt; [Lizhong] Adrian raise the same comment, and
        I change
        it as below: <br>
        &gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;-i. &nbsp;PE MUST send a
        Label Release message to remote PE. If a<br>
        &gt; &gt; &gt; &gt; PE <br>
        &gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; has previously
        sent a Label Mapping message to a remote<br>
        &gt; &gt; &gt; &gt; PE, <br>
        &gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; it MUST also
        send a Label Withdraw message to the remote<br>
        &gt; &gt; &gt; &gt; PE, <br>
        &gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and wait
        until it receives a Label Release message from<br>
        &gt; &gt; &gt; &gt; the<br>
        &gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;remote PE.
        <br>
        &gt; &gt; &gt; What does it send first if both must be sent?
        &nbsp;The
        text in the rest of<br>
        &gt; &gt; &gt; the document implies withdraw then release. &nbsp;This
        new
        text sort of<br>
        &gt; &gt; &gt; implies release then withdraw but isn't really
        clear. <br>
        &gt; &gt; [Lizhong] both should be sent, and does not require
        the sending<br>
        &gt; &gt; sequence. The two messages does not have dependence. <br>
        &gt; In that case, it is important to say so.</font>
      <br>
      <font face="sans-serif" size="2">[Lizhong] I will add a sentence
        in point
        "i" to say so. How about below:</font>
      <br>
      <font face="sans-serif" size="2">Note: above Label Release message
        and
        Label Withdraw message sending does not require specific
        sequence.</font>
      <br>
      <font face="sans-serif" size="2"><br>
        &gt; &gt; <br>
        &gt; &gt; &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; s3, discussion of multi-segment PWs:
        The statement
        that S-PE's<br>
        &gt; &gt; &gt; &gt; SHOULD<br>
        &gt; &gt; &gt; &gt; &gt; assume an initial passive role seems to
        have several
        problems:<br>
        &gt; &gt; &gt; &gt; &gt; - Does this mean that changing the
        configuration
        of an S-PE would<br>
        &gt; &gt; &gt; &gt; not<br>
        &gt; &gt; &gt; &gt; &gt; provoke the new mechanisms?<br>
        &gt; &gt; &gt; &gt; &gt; - The passive role situation is only
        specified
        for some sorts of<br>
        &gt; &gt; &gt; &gt; linked<br>
        &gt; &gt; &gt; &gt; &gt; FECs in RFC 6073 - what about other
        cases?<br>
        &gt; &gt; &gt; &gt; &gt; - What are the consequences for
        ignoring the SHOULD
        in this case? (I<br>
        &gt; &gt; &gt; &gt; &gt; have to say I am unsure that RFC 6073
        deals with
        this problem<br>
        &gt; &gt; &gt; &gt; either.) <br>
        &gt; &gt; &gt; &gt; [Lizhong] we follow RFC6073, and passive
        role is only
        applied for the<br>
        &gt; &gt; &gt; &gt; PW FEC, other cases are out of scope. <br>
        &gt; &gt; &gt; Why? This needs an explanation. Also this doesn't
        cover
        the point about<br>
        &gt; &gt; &gt; whether reconfig of an S-PE is allowed and how
        this squares
        with the<br>
        &gt; &gt; &gt; passive role.<br>
        &gt; &gt; &gt; &gt; SHOULD means highly recommended. We do not
        meet any
        problem when<br>
        &gt; &gt; &gt; &gt; implementing RFC6073. Do you suggest to
        change this
        to MUST? <br>
        &gt; &gt; &gt; Whenever a specification includes a 'SHOULD' the
        question
        arises of what<br>
        &gt; &gt; &gt; alternatives there might be and what is the
        reason for preferring
        the<br>
        &gt; &gt; &gt; suggested solution. &nbsp;In the original setup, it is
        fairly
        clear that life<br>
        &gt; &gt; &gt; is easier letting setup progress from &nbsp;one end to
        the
        other (although<br>
        &gt; &gt; &gt; this is not spelt out - I would have argued for
        this had
        &nbsp;I reviewed the<br>
        &gt; &gt; &gt; doc). &nbsp;For the configuration change this is less
        obvious.
        &nbsp;Regarding the<br>
        &gt; &gt; &gt; point about reconfig of the &nbsp;S-PE, it is going to
        make
        life more<br>
        &gt; &gt; &gt; complicated if the S-PE has to tell the T-PE to
        be active
        so it can be<br>
        &gt; &gt; &gt; passive. &nbsp;I would therefore argue that probably
        the
        notion of passivity<br>
        &gt; &gt; &gt; is irrelevant to the transition use case.
        &nbsp;Whether
        it should be SHOULD<br>
        &gt; &gt; &gt; or MUST is therefore moot. <br>
        &gt; &gt; [Lizhong] how about the following? Because we just
        refer to <br>
        &gt; RFC6073, and does not add anything new. <br>
        &gt; &gt; An initial passive role is defined in [RFC6073] for
        S-PE.<br>
        &gt; I can't see that this really helps.<br>
        &gt; There are still two points at issue here:<br>
        &gt; - Why are the cases other than the one in RFC 4447 that
        refers to
        a<br>
        &gt; passive S-PE out of scope? &nbsp;There aren't any statements to
        this
        effect<br>
        &gt; in the document.</font>
      <br>
      <font face="sans-serif" size="2">[Lizhong] the passive role is not
        for
        any specific cases. The passive role is for the processing of
        message (e.g,
        label mapping, label request). I will explicitly say that in the
        section.</font>
      <br>
      <font face="sans-serif" size="2"><br>
        &gt; - It is difficult for a S-PE that has its control word
        configuration<br>
        &gt; change to act passively. &nbsp;If it is really passive than
        nothing
        will<br>
        &gt; happen until the label is withdrawn. &nbsp;Otherwise it can't be
        descibed
        as<br>
        &gt; passive for this action. &nbsp;The text in the current draft
        actually<br>
        &gt; describes what is specified in RFC 6073 when talking
        'passive' rather<br>
        &gt; than explaining what happens when the control word
        configuration<br>
        &gt; changes.</font>
      <br>
      <font face="sans-serif" size="2">[Lizhong] the control word
        configuration
        changing talking about in this draft only happens on T-PE, not
        S-PE. The
        S-PE is a passive role for the message processing. I will make
        this clear
        in the draft.</font>
      <br>
      <font face="sans-serif" size="2"><br>
        &gt; &gt; &nbsp;<br>
        &gt; &gt; &gt; &gt; [Lizhong] has been revised in v-04.<br>
        &gt; &gt; &gt; Not as far as I can see. <br>
        &gt; &gt; [Lizhong] write "pseudowire" directly in the text,
        not PW. <br>
        &gt; There are lots of instances of PW still left in v04. Expand
        acronym
        =&gt;<br>
        &gt; define what it means on first usage i.e pseudowire (PW).
        &nbsp;Same
        for the<br>
        &gt; various other acronyms that aren't defined in the text.</font>
      <br>
      <font face="sans-serif" size="2">[Lizhong] accept<br>
        &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; s2: Expand acronym PE. <br>
        &gt; &gt; &gt; &gt; [Lizhong] accept <br>
        &gt; &gt; &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; s2, 2nd sentence:
        s/configurable/configured/ <br>
        &gt; &gt; &gt; &gt; [Lizhong] configurable is right. <br>
        &gt; &gt; &gt; Leave that one to the RFc Editor.<br>
        &gt; &gt; &gt; &gt; <br>
        &gt; &gt; &gt; &gt; &gt; s2, 3rd and 4th sentences: I *think*
        this text
        is trying to say: <br>
        &gt; &gt; &gt; &gt; &gt; &nbsp; The intention of the control word
        negotiation
        is that the control<br>
        &gt; &gt; &gt; &gt; word<br>
        &gt; &gt; &gt; &gt; &gt; will be used when both endpoints are
        configured
        with control word<br>
        &gt; &gt; &gt; &gt; usage<br>
        &gt; &gt; &gt; &gt; &gt; PREFERRED. &nbsp;However if one endpoint is
        initially
        configured with<br>
        &gt; &gt; &gt; &gt; control<br>
        &gt; &gt; &gt; &gt; &gt; word usage NOT PREFERRED but later
        changes to
        PREFERRED, a PW<br>
        &gt; &gt; &gt; &gt; between<br>
        &gt; &gt; &gt; &gt; &gt; the endpoints will not transition to
        usage of
        the control word as<br>
        &gt; &gt; &gt; &gt; &gt; explained below. <br>
        &gt; &gt; &gt; &gt; [Lizhong] no, the case is that operator
        deploys PW
        with control word<br>
        &gt; &gt; &gt; &gt; used in the first phase. In the second
        phase, they
        want to upgrade<br>
        &gt; &gt; &gt; &gt; their PW service to use control word. Two
        different
        deployment<br>
        &gt; &gt; &gt; &gt; timeframes.<br>
        &gt; &gt; &gt; That is what my sentence says. <br>
        &gt; &gt; [Lizhong] ok. <br>
        &gt; &gt; <br>
        &gt; <br>
        &gt; &gt; &gt; &gt; &gt; s3: It would be much clearer if s3 was
        divided
        into 3 sub-sections<br>
        &gt; &gt; &gt; &gt; &gt; (possibly reordered):<br>
        &gt; &gt; &gt; &gt; &gt; - PREFERRED to NOT PREFERRED transition<br>
        &gt; &gt; &gt; &gt; &gt; - NOT PREFERRED to PREFERRED transition<br>
        &gt; &gt; &gt; &gt; &gt; - Multi-segment case (which should
        refer to both
        previous cases)<br>
        &gt; &gt; &gt; &gt; &gt; The pointer to the diagram in Appendix
        A could
        usefully occur in the<br>
        &gt; &gt; &gt; &gt; &gt; introduction to s3. &nbsp;If this was
        adopted
        s3.1 could either be a<br>
        &gt; &gt; &gt; &gt; fourth<br>
        &gt; &gt; &gt; &gt; &gt; sub-section or a sub-sub-section of the
        PREFERRED
        to NOT PREFERRED<br>
        &gt; &gt; &gt; &gt; &gt; section. <br>
        &gt; &gt; &gt; &gt; [Lizhong] PREFERRED to NOT PREFERRED does
        not introduce
        any new.<br>
        &gt; &gt; &gt; &gt; Multi-segment case is fully inherited from
        single-segment
        case. It<br>
        &gt; &gt; &gt; &gt; would be redundancy to have sub-sections
        here. <br>
        &gt; &gt; &gt; I disagree strongly. &nbsp;The multi-segment case
        affects
        the other RFC and<br>
        &gt; &gt; &gt; needs to be made to stand out so that
        implementors can see
        where the<br>
        &gt; &gt; &gt; changes occur. &nbsp;The PREFERRED to NOT PREFERRED
        case
        also ought to be<br>
        &gt; &gt; &gt; separated whether or not I am right about this
        case. <br>
        &gt; &gt; [Lizhong] how about only divide multi-segment? The
        case of PREFERRED
        to <br>
        &gt; &gt; NOT PREFERRED case is only for reference, and the text
        is not
        many.<br>
        &gt; That is so, but it is a change of subject and the fact that
        it will
        then<br>
        &gt; be in the table of contents makes it easier for
        implementors to find
        the<br>
        &gt; relevant text. &nbsp;I wouldn't call it 'redundant'.<br>
        &gt; <br>
        &gt; &gt; &gt; &gt; &gt; s3, last para/Appendix A: &nbsp;The diagram
        doesn't
        cover the PREFERRED<br>
        &gt; &gt; &gt; &gt; to<br>
        &gt; &gt; &gt; &gt; &gt; NOT PREFERRED transition. <br>
        &gt; &gt; &gt; &gt; [Lizhong] no, there is a "no" branch under
        "NOT Preferred to<br>
        &gt; &gt; &gt; &gt; Preferred" to cover "PREFERRED to NOT
        PREFERRED".
        Anyway, the diagram<br>
        &gt; &gt; &gt; &gt; discription should be "NOT Preferred to
        Preferred"
        which is wrong in<br>
        &gt; &gt; &gt; &gt; v-04. <br>
        &gt; Need to check it reflects the Label Withdraw message needed
        in the<br>
        &gt; PREFERRED to NOT PREFERRED case. </font>
      <br>
      <font face="sans-serif" size="2">[Lizhong] ok, I could add Label
        Withdraw
        there.<br>
        &gt; <br>
        &gt; <br>
        &gt; <br>
      </font>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------080708080409040104010706--

From Alexander.Vainshtein@ecitele.com  Thu Jun 21 08:09:30 2012
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D82F521F870A; Thu, 21 Jun 2012 08:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level: 
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4,  UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6yOfTSQFO0yR; Thu, 21 Jun 2012 08:09:28 -0700 (PDT)
Received: from mail1.bemta4.messagelabs.com (mail1.bemta4.messagelabs.com [85.158.143.242]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC0E21F86F7; Thu, 21 Jun 2012 08:09:27 -0700 (PDT)
Received: from [85.158.143.35:23581] by server-3.bemta-4.messagelabs.com id C5/4E-05808-42933EF4; Thu, 21 Jun 2012 15:09:24 +0000
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-10.tower-21.messagelabs.com!1340291351!10296788!2
X-Originating-IP: [168.87.1.157]
X-StarScan-Version: 6.5.10; banners=-,-,-
Received: (qmail 12085 invoked from network); 21 Jun 2012 15:09:15 -0000
Received: from unknown (HELO fridlpvsb003.ecitele.com) (168.87.1.157) by server-10.tower-21.messagelabs.com with SMTP; 21 Jun 2012 15:09:15 -0000
X-AuditID: a8571403-b7f1c6d000001c72-16-4fe3390dc59f
Received: from FRIDWPPCH002.ecitele.com (fridwppch002.ecitele.com [10.1.16.53]) by fridlpvsb003.ecitele.com (Symantec Messaging Gateway) with SMTP id 28.EC.07282.D0933EF4; Thu, 21 Jun 2012 17:09:01 +0200 (CEST)
Received: from FRIDWPPMB001.ecitele.com ([169.254.3.23]) by FRIDWPPCH002.ecitele.com ([10.1.16.53]) with mapi id 14.01.0339.001; Thu, 21 Jun 2012 17:09:14 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, Elwyn Davies <elwynd@folly.org.uk>
Thread-Topic: [PWE3] Gen-art last call review of draft-ietf-pwe3-cbit-negotiation-04
Thread-Index: AQHNT7WxkCViPPMHlEyr3en6hcq5kJcE16qQ
Date: Thu, 21 Jun 2012 15:09:13 +0000
Message-ID: <F9336571731ADE42A5397FC831CEAA02095011@FRIDWPPMB001.ecitele.com>
References: <OFAAEAB3D5.D300977C-ON48257A22.00581007-48257A22.005F0A02@zte.com.cn> <1340282307.31554.36408.camel@mightyatom.folly.org.uk> <4FE327F7.4000008@cisco.com>
In-Reply-To: <4FE327F7.4000008@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.4.42.92]
Content-Type: text/plain; charset="us-ascii"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA2WTfWwLYRzHPb1re52dnG700XlpLiFhNp15OYkuCyH1lor3ILjdPdqL9tr0 brOJP4ogJpiXP7RZumGZeemWNcSCCMsQZSZhLN5tCPOyZCPIknHXYybur+/z+35+z/f33D1H YOYyo5UQRBkFRdZLG1LwFDDImjVkRofLHjpvZKpbTgLm5tUGI9Pa2YMz10v7ALM71owz+7vP 4czdN+Ug3+g80luvd369tRt3VlX90Dm/3O8xOM9e+Y4v1q8OgZmsKPplVkY2Hkmcg14cFIpY roS2CbyDzqFtAS/LIR8SZQfNBgJI5Om8FNt/z0wFE0QbEjk/L4huBz1vqSuLYabOyMqh85Z5 BMmGsnys4LX5kCSxbmRTKuqpRH5DLeaJH63XBWp2guIrZaV4CHzzlAITAakpMH5ih1HTw+G9 53WGUpBCmKkHAL668On3ogrAulgkSRkoB4yfeaYYBJFOLYWHX81RGYwK6+Ce8m2YyqRRy+GT H/VJPp1aAaOJQ3pNT4Y3Dr41qBqnxsLYjn3JOkktgt0994xa2GkAj4drk4aJGg+bq6O4qoEy 3rfEWZ2qMcoCH7+u0GljU7Dqcgum6WHwfUefXtOj4fZTD4waPxFWXuo2aDoTVh/7gGnBQ+Gt 8Gtc40fAazVteBmwRAZERAa0Rwa0Rwa0VwJcGXpjUOC9gSKpwG7PzUacICMvyub8vjhQblTN ynSsAXw5kN0IKALQqeS7SR0us54tkkp8jWAEoaOHkR+nKKUhBX6+xMNKnvXBQi+SGgEkMDqd TLS3u8wkz5ZsQUH/H4tR3uJBzDqY86tfWV6fa7f/s6AtZN2SPJeZcitXbxNCART80zqSIGhI FjJK4tAgcqPijYJX/mvrCJOanKok16gMKQVYnyS4NT8BMonaj01tgLi893obMOOiX0RWC7lL RSkV9RSK/bt1Aoty4jRSVN1U5UL279OpROiUCNOgZITyg/Rb1hDISLvri52eczS6dsGmqHFU hnystTj38Bqmq/v81osTtk/jWzNnRR/lE5W9DbMW/PzspJ721Zu7ws/Bqr3jMty1K5vH/Cxr 2VZ9Z+ELT3uBdV32/HCi4tncxHDTw6adPU8rYvmrNocfr+C40KSuJhnPmDt9dtf7lyfZz529 gba0UPw2jUseNmcCFpTYXwQzjkQjBAAA
X-Mailman-Approved-At: Thu, 21 Jun 2012 08:12:08 -0700
Cc: "draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org" <draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, Lizhong Jin <lizhong.jin@zte.com.cn>, pwe3 <pwe3@ietf.org>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>
Subject: Re: [Gen-art] [PWE3] Gen-art last call review of	draft-ietf-pwe3-cbit-negotiation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 15:09:30 -0000

Elwyn, Stewart and all,

I do not see any technical issues with the proposed solution for PREFERRED -=
-> NOT PREFERRED configuration change in draft-ietf-pwe3-cbit-negotiation.
To the best of my understanding, it does not really require any additions to=
 the procedures defined in RFC 4447 and would work like following:

1. I assume that originally the two PEs have agreed to use the CW. (If they=
 didn't because the remote PE did not want to support it, there is nothing t=
o re-negotiate).
2. Local PE (where the configuration of the PW endpoint has changed):
	- Sends a Label Withdraw message for its original PW label mapping (where C=
-bit has been set)
	- Waits for the Label Release acknowledging this Label Withdraw message as=
 mandated by 5036
	- Sends a Label Mapping message with the C-bit cleared.
3. Remote PE, upon receiving the new Label Mapping with the C-bit cleared do=
es what RFC 4447 says, namely:
	- Withdraws its original Label Mapping with C-bit 
	- Waits for Label Release acknowledging this withdrawal
	- Sends a new Label Mapping message with C-bit cleared to the Local PW.
4. At this moment re-negotiation is complete.

This said, adding an explicit description to the text could be useful. But I=
MHO this is an editorial issue, not a technical one.

My 2c,
     Sasha


> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf
> Of Stewart Bryant
> Sent: Thursday, June 21, 2012 4:56 PM
> To: Elwyn Davies
> Cc: draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org; General Area Revi=
ew
> Team; Lizhong Jin; pwe3; pwe3-chairs@tools.ietf.org
> Subject: Re: [PWE3] Gen-art last call review of draft-ietf-pwe3-cbit-
> negotiation-04
> 
> Bringing this to the attention of the PWE3 WG
> since that need to know that this discussion is happening
> and will have a view as to what is already well
> known in terms of RFC4447 behavior and what
> needs clarification via this draft.
> 
> Stewart
> 
> On 21/06/2012 13:38, Elwyn Davies wrote:
> > Hi, Lizhong.
> >
> > I have removed the bits that we are agreed on to shorten the mail a bit.
> >
> > I don't think we have converged just yet.
> >
> > Regards,
> > Elwyn
> >
> > On Wed, 2012-06-20 at 01:17 +0800, Lizhong Jin wrote:
> >> Hi Elwyn,
> >> Thank you for the prompt reply. See inline below.
> >>
> >> Lizhong
> >>
> >>
> >> Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/19 23:16:08:
> >>>>> Document: draft-ietf-pwe3-cbit-negotiation-04.txt
> >>>>> Reviewer: Elwyn Davies
> >>>>> Review Date: 19 June 2012
> >>>>> IETF LC End Date: 15 June 2012
> >>>>> IESG Telechat date: 21 June 2012
> >>>>>
> >>>>> Summary:
> >>>>> Not ready. The proposal for the NOT PREFERRED to PREFERRED
> >>>> transition
> >>>>> case does not appear to be compatible with the existing RFC 4447
> >>>>> standard in the way stated and there are a number of other minor
> >>>> issues.
> >>>>> The draft is also in need of an editing pass by an author whose
> >>>> mother
> >>>>> tongue is English as there are parts where the syntax is misleading
> >>>>> Major issues:
> >>>>> s3: The discussion of the NOT PREFERRED to PREFERRED transition
> case
> >>>>> (buried at the end of s3 - causing me to ask 'what about this case?'
> >>>>> during reading of s2 and most of s3)  implies that some existing RFC
> >>>>> 4447 procedure applies. Clearly, if the PW is not using the control
> >>>> word
> >>>>> then there is nothing to do.  On the other hand, inspection of s6.2
> >>>> of
> >>>>> RFC4447 indicates that once the two PEs have agreed on c =3D 1, 'set=
up
> >>>> is
> >>>>> complete' and Label Mapping messages would therefore be
> >>>>> 'unexpected' (see item '-i' in second set of bullets in s6.2 of RFC
> >>>>> 4447). So, what procedure is to be used? And what implications does
> >>>> this
> >>>>> have for backwards compatibility?  Wouldn't it be generally simpler
> >>>> to
> >>>>> apply the PREFERRED to NOT PREFERRED mechanism to all case?
> >>>> [Lizhong] this draft is to solve the case to change a PW from c=3D0 t=
o
> >>>> c=3D1, that means one PE should change its use of control word from
> NOT
> >>>> PREFERRED to PREFERRED. RFC4447 is already there and deployed, and
> the
> >>>> PE will not always send its locally configured preferrence according
> >>>> RFC4447, see PE1 behavior in section 2 step 1&2. That's why we could
> >>>> not simply apply the mechanism at the end of section 3. Hope it is
> >>>> clear.
> >>> There are two issues here:
> >>> - Clarity: RFC 4447 does not have any discussion of what might happen=
 if
> >>> the configuration value changes.  The draft focusses on on transition
> >>> direction but does not mention the other except for one paragaph right
> >>> at the end of s3.  It is therefore reasonable that somebody looking at
> >>> this draft would wonder 'what about the other transition direction?'.
> >>> Whether or not anything needs to be done it would save people
> wondering
> >>> if you put in a sentence in the introduction to explain that the other
> >>> direction is not (or is) a problem.
> >> [Lizhong] accept. Add following:
> >> When PE changes the preference for the use of control word from
> >> PREFERRED to NOT PREFERRED, it should follow [RFC4447], and there is
> >> no problem.
> > See below...
> >>> - Technical: The paragraph in s3 implies that the PREFERRED to NOT
> >>> PREFERRED direction will result in some part of the RFC 4447 protocol
> >>> being (re-)invoked.  What part is not made very clear.  As far as I ca=
n
> >>> see sending more messages other than Label Release or Label Withdraw
> for
> >>> this PW is not part of the RFC 4447 protocol and hence will cause an
> >>> error.  Alternatively if it isn't reinvoked, the PW will continue to u=
se
> >>> control words.  Please explain what is going on here.  The fact that R=
FC
> >>> 4447 has been deployed doesn't explain what is going on.
> >> [Lizhong] now I understand you concern. The last sentance of s3 is not
> >> clear. How about the following:
> >> In that case, local PE will always send Label Withdraw message if
> >> already sending Label Mapping message, and then send new Label
> Mapping
> >> message with C-bit value following the procedures defined in
> >> [RFC4447].
> > I think we have reached the heart of the issue here:  RFC 4447 does not
> > mention changing the control word configuration.  The combination of the
> > existing text in the draft and what you have just weittrn above
> > indicates that *in both transition directions* the PE changing
> > configuration notifies its peer by sending a Label Withdraw. It is not
> > immediately obvious to me that you could deduce this from RFC 4447 - if
> > it is then there needs to be a pointer to the relevant section in RFC
> > 4447 to enlighten the ignorant like me.  Otherwise the PREFERRED to NOT
> > PREFERRED transition is *not* just 'follow the RFC 4447 procedures'.
> >
> > If I now understand correctly, the situation is as follows:
> > - in both cases when there is a control word preference transition, send
> > a Label Withdraw.
> > - in the NOT PREFERRED to PREFERRED case send Label Release also (order
> > not important), wait for a responses from peer, then send Label Request
> > and negotiate use of control word using Label Mapping C bit as for a new
> > PW (might result in either using or not using control word depending on
> > state in peer).
> > - in the PREFERRED to NOT PREFERRED case, just negotiate C bit to 0
> > using Label Mapping - label will be maintained. [Need to check that RFC
> > 4447 is expecting/will allow this sequence.]
> >
> > If I have this straight, I think that the PREFERRED to NOT PREFERRED
> > case needs some more words in s3 and an introduction in s2. (And it
> > would be easier to understand with this case in a separate sub-section -
> > sorry to harp on about this).
> >
> >>>>> Minor issues:
> >>>>> s3: Has there been any discussion on possible race conditions?
> >>>>   Changing
> >>>>> the configuration value during the message exchange strikes me as
> >>>>> dangerous - it is probably sufficient to note that changes should be
> >>>>> suppressed during the Label Mapping message exchange but I am not
> >>>>> totally sure about this.
> >>>> [Lizhong] The message would be processed in sequence in TCP-based
> LDP
> >>>> session. I do not see a problem here. But we do have a note in sectio=
n
> >>>> 3 for multi-segment PW for sequence processing.
> >>> There are several network round trips in the message exchanges.  The
> >>> protocol and the configuration mechanism in a PE are potentially
> >>> separate threads.  There is scope, depending on the implementation, fo=
r
> >>> the user at the 'remote' PE to change the configuration during the
> >>> message exchange making for a potential race condition.
> >> [Lizhong] we discussed the race condition on the PWE3 maillist from
> >> Spike, and for multi-segment PW, we add a note to ensure the sequence
> >> processing for implementation.
> > I look forward to the revised text.
> >>
> >>
> >>>>> s3, bullet '-i':  I completely misparsed this section on first
> >>>> reading
> >>>>> and I am still not absolutely sure what message sequence is being
> >>>>> specified.  Working back from later sections I *think* that the
> >>>>> intention is:
> >>>>> IF Mapping sent THEN { send Withdraw; send Release;}
> >>>>> Wait to receive Release
> >>>>> The implication at present is that a Mapping might not have been
> >>>> sent
> >>>>> and then only a Release is needed: is this a possibility? Please
> >>>>> clarify.
> >>>>> The picture in Appendix A suffers from the same problem.
> >>>> [Lizhong] Adrian raise the same comment, and I change it as below:
> >>>>         -i.  PE MUST send a Label Release message to remote PE. If a
> >>>> PE
> >>>>              has previously sent a Label Mapping message to a remote
> >>>> PE,
> >>>>              it MUST also send a Label Withdraw message to the remote
> >>>> PE,
> >>>>              and wait until it receives a Label Release message from
> >>>> the
> >>>>             remote PE.
> >>> What does it send first if both must be sent?  The text in the rest of
> >>> the document implies withdraw then release.  This new text sort of
> >>> implies release then withdraw but isn't really clear.
> >> [Lizhong] both should be sent, and does not require the sending
> >> sequence. The two messages does not have dependence.
> > In that case, it is important to say so.
> >>>>> s3, discussion of multi-segment PWs: The statement that S-PE's
> >>>> SHOULD
> >>>>> assume an initial passive role seems to have several problems:
> >>>>> - Does this mean that changing the configuration of an S-PE would
> >>>> not
> >>>>> provoke the new mechanisms?
> >>>>> - The passive role situation is only specified for some sorts of
> >>>> linked
> >>>>> FECs in RFC 6073 - what about other cases?
> >>>>> - What are the consequences for ignoring the SHOULD in this case? (I
> >>>>> have to say I am unsure that RFC 6073 deals with this problem
> >>>> either.)
> >>>> [Lizhong] we follow RFC6073, and passive role is only applied for the
> >>>> PW FEC, other cases are out of scope.
> >>> Why? This needs an explanation. Also this doesn't cover the point abou=
t
> >>> whether reconfig of an S-PE is allowed and how this squares with the
> >>> passive role.
> >>>> SHOULD means highly recommended. We do not meet any problem
> when
> >>>> implementing RFC6073. Do you suggest to change this to MUST?
> >>> Whenever a specification includes a 'SHOULD' the question arises of
> what
> >>> alternatives there might be and what is the reason for preferring the
> >>> suggested solution.  In the original setup, it is fairly clear that li=
fe
> >>> is easier letting setup progress from  one end to the other (although
> >>> this is not spelt out - I would have argued for this had  I reviewed t=
he
> >>> doc).  For the configuration change this is less obvious.  Regarding t=
he
> >>> point about reconfig of the  S-PE, it is going to make life more
> >>> complicated if the S-PE has to tell the T-PE to be active so it can be
> >>> passive.  I would therefore argue that probably the notion of passivit=
y
> >>> is irrelevant to the transition use case.  Whether it should be SHOULD
> >>> or MUST is therefore moot.
> >> [Lizhong] how about the following? Because we just refer to RFC6073,
> and does not add anything new.
> >> An initial passive role is defined in [RFC6073] for S-PE.
> > I can't see that this really helps.
> > There are still two points at issue here:
> > - Why are the cases other than the one in RFC 4447 that refers to a
> > passive S-PE out of scope?  There aren't any statements to this effect
> > in the document.
> > - It is difficult for a S-PE that has its control word configuration
> > change to act passively.  If it is really passive than nothing will
> > happen until the label is withdrawn.  Otherwise it can't be descibed as
> > passive for this action.  The text in the current draft actually
> > describes what is specified in RFC 6073 when talking 'passive' rather
> > than explaining what happens when the control word configuration
> > changes.
> >>
> >>>> [Lizhong] has been revised in v-04.
> >>> Not as far as I can see.
> >> [Lizhong] write "pseudowire" directly in the text, not PW.
> > There are lots of instances of PW still left in v04. Expand acronym =3D>
> > define what it means on first usage i.e pseudowire (PW).  Same for the
> > various other acronyms that aren't defined in the text.
> >>>>> s2: Expand acronym PE.
> >>>> [Lizhong] accept
> >>>>
> >>>>> s2, 2nd sentence: s/configurable/configured/
> >>>> [Lizhong] configurable is right.
> >>> Leave that one to the RFc Editor.
> >>>>> s2, 3rd and 4th sentences: I *think* this text is trying to say:
> >>>>>    The intention of the control word negotiation is that the control
> >>>> word
> >>>>> will be used when both endpoints are configured with control word
> >>>> usage
> >>>>> PREFERRED.  However if one endpoint is initially configured with
> >>>> control
> >>>>> word usage NOT PREFERRED but later changes to PREFERRED, a PW
> >>>> between
> >>>>> the endpoints will not transition to usage of the control word as
> >>>>> explained below.
> >>>> [Lizhong] no, the case is that operator deploys PW with control word
> >>>> used in the first phase. In the second phase, they want to upgrade
> >>>> their PW service to use control word. Two different deployment
> >>>> timeframes.
> >>> That is what my sentence says.
> >> [Lizhong] ok.
> >>
> >>>>> s3: It would be much clearer if s3 was divided into 3 sub-sections
> >>>>> (possibly reordered):
> >>>>> - PREFERRED to NOT PREFERRED transition
> >>>>> - NOT PREFERRED to PREFERRED transition
> >>>>> - Multi-segment case (which should refer to both previous cases)
> >>>>> The pointer to the diagram in Appendix A could usefully occur in the
> >>>>> introduction to s3.  If this was adopted s3.1 could either be a
> >>>> fourth
> >>>>> sub-section or a sub-sub-section of the PREFERRED to NOT
> PREFERRED
> >>>>> section.
> >>>> [Lizhong] PREFERRED to NOT PREFERRED does not introduce any new.
> >>>> Multi-segment case is fully inherited from single-segment case. It
> >>>> would be redundancy to have sub-sections here.
> >>> I disagree strongly.  The multi-segment case affects the other RFC and
> >>> needs to be made to stand out so that implementors can see where the
> >>> changes occur.  The PREFERRED to NOT PREFERRED case also ought to
> be
> >>> separated whether or not I am right about this case.
> >> [Lizhong] how about only divide multi-segment? The case of PREFERRED
> to
> >> NOT PREFERRED case is only for reference, and the text is not many.
> > That is so, but it is a change of subject and the fact that it will then
> > be in the table of contents makes it easier for implementors to find the
> > relevant text.  I wouldn't call it 'redundant'.
> >
> >>>>> s3, last para/Appendix A:  The diagram doesn't cover the PREFERRED
> >>>> to
> >>>>> NOT PREFERRED transition.
> >>>> [Lizhong] no, there is a "no" branch under "NOT Preferred to
> >>>> Preferred" to cover "PREFERRED to NOT PREFERRED". Anyway, the
> diagram
> >>>> discription should be "NOT Preferred to Preferred" which is wrong in
> >>>> v-04.
> > Need to check it reflects the Label Withdraw message needed in the
> > PREFERRED to NOT PREFERRED case.
> >
> >
> >
> 
> 
> --
> For corporate legal information go to:
> 
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3

This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


From lizhong.jin@zte.com.cn  Thu Jun 21 08:32:09 2012
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399D721F86B8; Thu, 21 Jun 2012 08:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.838
X-Spam-Level: 
X-Spam-Status: No, score=-101.838 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oeTx3X-NJRIs; Thu, 21 Jun 2012 08:32:06 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 6B16221F855E; Thu, 21 Jun 2012 08:32:01 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 514963275863407; Thu, 21 Jun 2012 23:30:24 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 52926.7619564388; Thu, 21 Jun 2012 23:31:57 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q5LFVsbh087199; Thu, 21 Jun 2012 23:31:54 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <OF6E7B2A91.233F1F7A-ON48257A24.004B6705-48257A24.005100EB@LocalDomain>
To: pwe3 <pwe3@ietf.org>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFCD93A615.A1A44624-ON48257A24.00551B46-48257A24.005551CA@zte.com.cn>
From: Lizhong Jin<lizhong.jin@zte.com.cn>
Date: Thu, 21 Jun 2012 23:31:02 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-06-21 23:31:56, Serialize complete at 2012-06-21 23:31:56
Content-Type: multipart/alternative; boundary="=_alternative 005551CA48257A24_="
X-MAIL: mse01.zte.com.cn q5LFVsbh087199
Cc: draft-ietf-pwe3-cbit-negotiation.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Elwyn Davies <elwynd@folly.org.uk>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-pwe3-cbit-negotiation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 15:32:09 -0000

This is a multipart message in MIME format.
--=_alternative 005551CA48257A24_=
Content-Type: text/plain; charset="US-ASCII"

This email is to send the review discussion to PWE3 list as the request 
from AD.

Thanks
Lizhong
 

Lizhong Jin wrote 2012/06/21 22:43:54:

> Hi Elwyn,
> Please see inline below.
> 
> Thanks
> Lizhong
> 
> Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/21 20:38:27:
> 
> > Hi, Lizhong.
> > 
> > I have removed the bits that we are agreed on to shorten the mail a 
bit.
> > 
> > I don't think we have converged just yet.
> > 
> > Regards,
> > Elwyn
> > 
> > On Wed, 2012-06-20 at 01:17 +0800, Lizhong Jin wrote:
> > > 
> > > Hi Elwyn, 
> > > Thank you for the prompt reply. See inline below. 
> > > 
> > > Lizhong 
> > > 
> > > 
> > > Elwyn Davies <elwynd@folly.org.uk> wrote 2012/06/19 23:16:08:
> > > > > > Document: draft-ietf-pwe3-cbit-negotiation-04.txt
> > > > > > Reviewer: Elwyn Davies
> > > > > > Review Date: 19 June 2012
> > > > > > IETF LC End Date: 15 June 2012
> > > > > > IESG Telechat date: 21 June 2012
> > > > > > 
> > > > > > Summary: 
> > > > > > Not ready. The proposal for the NOT PREFERRED to PREFERRED
> > > > > transition
> > > > > > case does not appear to be compatible with the existing RFC 
4447
> > > > > > standard in the way stated and there are a number of other 
minor
> > > > > issues.
> > > > > > The draft is also in need of an editing pass by an author 
whose
> > > > > mother
> > > > > > tongue is English as there are parts where the syntax is 
misleading
> > > > > > Major issues: 
> > > > > > s3: The discussion of the NOT PREFERRED to PREFERRED 
transition case
> > > > > > (buried at the end of s3 - causing me to ask 'what about this 
case?'
> > > > > > during reading of s2 and most of s3)  implies that some 
existing RFC
> > > > > > 4447 procedure applies. Clearly, if the PW is not using the 
control
> > > > > word
> > > > > > then there is nothing to do.  On the other hand, inspection of 
s6.2
> > > > > of
> > > > > > RFC4447 indicates that once the two PEs have agreed on c =1, 
'setup
> > > > > is
> > > > > > complete' and Label Mapping messages would therefore be
> > > > > > 'unexpected' (see item '-i' in second set of bullets in s6.2 
of RFC
> > > > > > 4447). So, what procedure is to be used? And what implications 
does
> > > > > this
> > > > > > have for backwards compatibility?  Wouldn't it be generally 
simpler
> > > > > to
> > > > > > apply the PREFERRED to NOT PREFERRED mechanism to all case? 
> > > > > [Lizhong] this draft is to solve the case to change a PW from 
c=0 to
> > > > > c=1, that means one PE should change its use of control word 
from NOT
> > > > > PREFERRED to PREFERRED. RFC4447 is already there and deployed, 
and the
> > > > > PE will not always send its locally configured preferrence 
according
> > > > > RFC4447, see PE1 behavior in section 2 step 1&2. That's why we 
could
> > > > > not simply apply the mechanism at the end of section 3. Hope it 
is
> > > > > clear. 
> > > > There are two issues here:
> > > > - Clarity: RFC 4447 does not have any discussion of what 
mighthappen if
> > > > the configuration value changes.  The draft focusses on on 
transition
> > > > direction but does not mention the other except for one paragaph 
right
> > > > at the end of s3.  It is therefore reasonable that somebody 
looking at
> > > > this draft would wonder 'what about the other transition 
direction?'.
> > > > Whether or not anything needs to be done it would save people 
wondering
> > > > if you put in a sentence in the introduction to explain that the 
other
> > > > direction is not (or is) a problem. 
> > > [Lizhong] accept. Add following: 
> > > When PE changes the preference for the use of control word from
> > > PREFERRED to NOT PREFERRED, it should follow [RFC4447], and there is
> > > no problem. 
> > 
> > See below...
> > > 
> > > > - Technical: The paragraph in s3 implies that the PREFERRED to NOT
> > > > PREFERRED direction will result in some part of the RFC 4447 
protocol
> > > > being (re-)invoked.  What part is not made very clear.  As far as 
I can
> > > > see sending more messages other than Label Release or Label 
Withdraw for
> > > > this PW is not part of the RFC 4447 protocol and hence will cause 
an
> > > > error.  Alternatively if it isn't reinvoked, the PW will continue 
to use
> > > > control words.  Please explain what is going on here.  The fact 
that RFC
> > > > 4447 has been deployed doesn't explain what is going on. 
> > > [Lizhong] now I understand you concern. The last sentance of s3 is 
not
> > > clear. How about the following: 
> > > In that case, local PE will always send Label Withdraw message if
> > > already sending Label Mapping message, and then send new Label 
Mapping
> > > message with C-bit value following the procedures defined in
> > > [RFC4447]. 
> > 
> > I think we have reached the heart of the issue here:  RFC 4447 does 
not
> > mention changing the control word configuration.  The combination of 
the
> > existing text in the draft and what you have just weittrn above
> > indicates that *in both transition directions* the PE changing
> > configuration notifies its peer by sending a Label Withdraw. It is not
> > immediately obvious to me that you could deduce this from RFC 4447 - 
if
> > it is then there needs to be a pointer to the relevant section in RFC
> > 4447 to enlighten the ignorant like me.  Otherwise the PREFERRED to 
NOT
> > PREFERRED transition is *not* just 'follow the RFC 4447 procedures'.
> [Lizhong] as an engineer, I interpret the configuration changing as 
> deleting and configuring again. Control word configuration changing 
> means deleting the old control word, and then configuring the new 
> control word, that means deleting PW configuration, and configuring 
> new PW configuration again. RFC4447 section 5.4.1 describe the 
> procedure of PW deletion and configuration. When you apply the above
> procedure to PREFERRED to NOT PREFERRED transition, it works well, 
> while for NOT PREFERRED to PREFERRED transition, there is a problem.
> What if I add some description of the meaning of control word 
> changing at the end of s3, so as to make it clear?
> 
> > 
> > If I now understand correctly, the situation is as follows:
> > - in both cases when there is a control word preference transition, 
send
> > a Label Withdraw.
> > - in the NOT PREFERRED to PREFERRED case send Label Release also 
(order
> > not important), wait for a responses from peer, then send Label 
Request
> > and negotiate use of control word using Label Mapping C bit as for a 
new
> > PW (might result in either using or not using control word depending 
on
> > state in peer).
> > - in the PREFERRED to NOT PREFERRED case, just negotiate C bit to 0
> > using Label Mapping - label will be maintained. [Need to check that 
RFC
> > 4447 is expecting/will allow this sequence.]
> > 
> > If I have this straight, I think that the PREFERRED to NOT PREFERRED
> > case needs some more words in s3 and an introduction in s2. (And it
> > would be easier to understand with this case in a separate sub-section 
-
> > sorry to harp on about this). 
> [Lizhong] your above description is totally right. How about 
> changing the end of s3 as below:
> When Local PE changes the use of control word from PREFERRED to NOT 
> PREFERRED, the local PE would be able to negotiate the Control Word 
> to be not used by deleting the PW configuration with PREFERRED use 
> of control word,  and configuring the PW again with NOT PREFERRED 
> use of control word. All of these procedures have been defined in 
> [RFC4447] section 5.4.1.
> 
> > 
> > > > > 
> > > > > > 
> > > > > > Minor issues: 
> > > > > > s3: Has there been any discussion on possible race conditions?
> > > > >  Changing
> > > > > > the configuration value during the message exchange strikes me 
as
> > > > > > dangerous - it is probably sufficient to note that 
changesshould be
> > > > > > suppressed during the Label Mapping message exchange but I am 
not
> > > > > > totally sure about this. 
> > > > > [Lizhong] The message would be processed in sequence in 
TCP-based LDP
> > > > > session. I do not see a problem here. But we do have a note in 
section
> > > > > 3 for multi-segment PW for sequence processing. 
> > > > There are several network round trips in the message exchanges. 
The
> > > > protocol and the configuration mechanism in a PE are potentially
> > > > separate threads.  There is scope, depending on the 
implementation, for
> > > > the user at the 'remote' PE to change the configuration during the
> > > > message exchange making for a potential race condition. 
> > > [Lizhong] we discussed the race condition on the PWE3 maillist from
> > > Spike, and for multi-segment PW, we add a note to ensure the 
sequence
> > > processing for implementation.
> > I look forward to the revised text.
> [Lizhong] How about add the following in s3: for the local PE, 
> before processing new configuration changing, the above message 
> exchange process should be finished.
> 
> > > 
> > > 
> > > > > 
> > > > > > 
> > > > > > s3, bullet '-i':  I completely misparsed this section on first
> > > > > reading
> > > > > > and I am still not absolutely sure what message sequence is 
being
> > > > > > specified.  Working back from later sections I *think* that 
the
> > > > > > intention is:
> > > > > > IF Mapping sent THEN { send Withdraw; send Release;}
> > > > > > Wait to receive Release
> > > > > > The implication at present is that a Mapping might not have 
been
> > > > > sent
> > > > > > and then only a Release is needed: is this a possibility? 
Please
> > > > > > clarify.
> > > > > > The picture in Appendix A suffers from the same problem. 
> > > > > [Lizhong] Adrian raise the same comment, and I change it as 
below: 
> > > > >        -i.  PE MUST send a Label Release message to remote PE. 
If a
> > > > > PE 
> > > > >             has previously sent a Label Mapping message to a 
remote
> > > > > PE, 
> > > > >             it MUST also send a Label Withdraw message to the 
remote
> > > > > PE, 
> > > > >             and wait until it receives a Label Release message 
from
> > > > > the
> > > > >            remote PE. 
> > > > What does it send first if both must be sent?  The text in the 
rest of
> > > > the document implies withdraw then release.  This new text sort of
> > > > implies release then withdraw but isn't really clear. 
> > > [Lizhong] both should be sent, and does not require the sending
> > > sequence. The two messages does not have dependence. 
> > In that case, it is important to say so.
> [Lizhong] I will add a sentence in point "i" to say so. How about below:
> Note: above Label Release message and Label Withdraw message sending
> does not require specific sequence.
> 
> > > 
> > > > > 
> > > > > > 
> > > > > > s3, discussion of multi-segment PWs: The statement that S-PE's
> > > > > SHOULD
> > > > > > assume an initial passive role seems to have several problems:
> > > > > > - Does this mean that changing the configuration of an S-PE 
would
> > > > > not
> > > > > > provoke the new mechanisms?
> > > > > > - The passive role situation is only specified for some sorts 
of
> > > > > linked
> > > > > > FECs in RFC 6073 - what about other cases?
> > > > > > - What are the consequences for ignoring the SHOULD in this 
case? (I
> > > > > > have to say I am unsure that RFC 6073 deals with this problem
> > > > > either.) 
> > > > > [Lizhong] we follow RFC6073, and passive role is only applied 
for the
> > > > > PW FEC, other cases are out of scope. 
> > > > Why? This needs an explanation. Also this doesn't cover the point 
about
> > > > whether reconfig of an S-PE is allowed and how this squares with 
the
> > > > passive role.
> > > > > SHOULD means highly recommended. We do not meet any problem when
> > > > > implementing RFC6073. Do you suggest to change this to MUST? 
> > > > Whenever a specification includes a 'SHOULD' the question arises 
of what
> > > > alternatives there might be and what is the reason for preferring 
the
> > > > suggested solution.  In the original setup, it is fairly clearthat 
life
> > > > is easier letting setup progress from  one end to the other 
(although
> > > > this is not spelt out - I would have argued for this had  I 
reviewed the
> > > > doc).  For the configuration change this is less obvious. 
Regarding the
> > > > point about reconfig of the  S-PE, it is going to make life more
> > > > complicated if the S-PE has to tell the T-PE to be active so it 
can be
> > > > passive.  I would therefore argue that probably the notion of 
passivity
> > > > is irrelevant to the transition use case.  Whether it should be 
SHOULD
> > > > or MUST is therefore moot. 
> > > [Lizhong] how about the following? Because we just refer to 
> > RFC6073, and does not add anything new. 
> > > An initial passive role is defined in [RFC6073] for S-PE.
> > I can't see that this really helps.
> > There are still two points at issue here:
> > - Why are the cases other than the one in RFC 4447 that refers to a
> > passive S-PE out of scope?  There aren't any statements to this effect
> > in the document.
> [Lizhong] the passive role is not for any specific cases. The 
> passive role is for the processing of message (e.g, label mapping, 
> label request). I will explicitly say that in the section.
> 
> > - It is difficult for a S-PE that has its control word configuration
> > change to act passively.  If it is really passive than nothing will
> > happen until the label is withdrawn.  Otherwise it can't be descibed 
as
> > passive for this action.  The text in the current draft actually
> > describes what is specified in RFC 6073 when talking 'passive' rather
> > than explaining what happens when the control word configuration
> > changes.
> [Lizhong] the control word configuration changing talking about in 
> this draft only happens on T-PE, not S-PE. The S-PE is a passive 
> role for the message processing. I will make this clear in the draft.
> 
> > > 
> > > > > [Lizhong] has been revised in v-04.
> > > > Not as far as I can see. 
> > > [Lizhong] write "pseudowire" directly in the text, not PW. 
> > There are lots of instances of PW still left in v04. Expand acronym =>
> > define what it means on first usage i.e pseudowire (PW).  Same for the
> > various other acronyms that aren't defined in the text.
> [Lizhong] accept
> > > 
> > > > > > 
> > > > > > s2: Expand acronym PE. 
> > > > > [Lizhong] accept 
> > > > > 
> > > > > > s2, 2nd sentence: s/configurable/configured/ 
> > > > > [Lizhong] configurable is right. 
> > > > Leave that one to the RFc Editor.
> > > > > 
> > > > > > s2, 3rd and 4th sentences: I *think* this text is trying to 
say: 
> > > > > >   The intention of the control word negotiation is that the 
control
> > > > > word
> > > > > > will be used when both endpoints are configured with control 
word
> > > > > usage
> > > > > > PREFERRED.  However if one endpoint is initially configured 
with
> > > > > control
> > > > > > word usage NOT PREFERRED but later changes to PREFERRED, a PW
> > > > > between
> > > > > > the endpoints will not transition to usage of the control word 
as
> > > > > > explained below. 
> > > > > [Lizhong] no, the case is that operator deploys PW with control 
word
> > > > > used in the first phase. In the second phase, they want to 
upgrade
> > > > > their PW service to use control word. Two different deployment
> > > > > timeframes.
> > > > That is what my sentence says. 
> > > [Lizhong] ok. 
> > > 
> > 
> > > > > > s3: It would be much clearer if s3 was divided into 3 
sub-sections
> > > > > > (possibly reordered):
> > > > > > - PREFERRED to NOT PREFERRED transition
> > > > > > - NOT PREFERRED to PREFERRED transition
> > > > > > - Multi-segment case (which should refer to both previous 
cases)
> > > > > > The pointer to the diagram in Appendix A could usefully occur 
in the
> > > > > > introduction to s3.  If this was adopted s3.1 could either be 
a
> > > > > fourth
> > > > > > sub-section or a sub-sub-section of the PREFERRED to NOT 
PREFERRED
> > > > > > section. 
> > > > > [Lizhong] PREFERRED to NOT PREFERRED does not introduce any new.
> > > > > Multi-segment case is fully inherited from single-segment case. 
It
> > > > > would be redundancy to have sub-sections here. 
> > > > I disagree strongly.  The multi-segment case affects the other RFC 
and
> > > > needs to be made to stand out so that implementors can see where 
the
> > > > changes occur.  The PREFERRED to NOT PREFERRED case also ought to 
be
> > > > separated whether or not I am right about this case. 
> > > [Lizhong] how about only divide multi-segment? The case of PREFERRED 
to 
> > > NOT PREFERRED case is only for reference, and the text is not many.
> > That is so, but it is a change of subject and the fact that it will 
then
> > be in the table of contents makes it easier for implementors to find 
the
> > relevant text.  I wouldn't call it 'redundant'.
> > 
> > > > > > s3, last para/Appendix A:  The diagram doesn't cover the 
PREFERRED
> > > > > to
> > > > > > NOT PREFERRED transition. 
> > > > > [Lizhong] no, there is a "no" branch under "NOT Preferred to
> > > > > Preferred" to cover "PREFERRED to NOT PREFERRED". Anyway, the 
diagram
> > > > > discription should be "NOT Preferred to Preferred" which is 
wrong in
> > > > > v-04. 
> > Need to check it reflects the Label Withdraw message needed in the
> > PREFERRED to NOT PREFERRED case. 
> [Lizhong] ok, I could add Label Withdraw there.
> > 
> > 
> > 

--=_alternative 005551CA48257A24_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">This email is to send the review discussion
to PWE3 list as the request from AD.</font>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br><font size=2><tt>Lizhong Jin wrote 2012/06/21 22:43:54:<br>
<br>
&gt; Hi Elwyn,</tt></font>
<br><font size=2><tt>&gt; Please see inline below.</tt></font>
<br><font size=2><tt>&gt; <br>
&gt; Thanks</tt></font>
<br><font size=2><tt>&gt; Lizhong</tt></font>
<br><font size=2><tt>&gt; <br>
&gt; Elwyn Davies &lt;elwynd@folly.org.uk&gt; wrote 2012/06/21 20:38:27:<br>
&gt; <br>
&gt; &gt; Hi, Lizhong.<br>
&gt; &gt; <br>
&gt; &gt; I have removed the bits that we are agreed on to shorten the
mail a bit.<br>
&gt; &gt; <br>
&gt; &gt; I don't think we have converged just yet.<br>
&gt; &gt; <br>
&gt; &gt; Regards,<br>
&gt; &gt; Elwyn<br>
&gt; &gt; <br>
&gt; &gt; On Wed, 2012-06-20 at 01:17 +0800, Lizhong Jin wrote:<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Hi Elwyn, <br>
&gt; &gt; &gt; Thank you for the prompt reply. See inline below. <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Lizhong <br>
&gt; &gt; &gt; &nbsp; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Elwyn Davies &lt;elwynd@folly.org.uk&gt; wrote 2012/06/19
23:16:08:<br>
&gt; &gt; &gt; &gt; &gt; &gt; Document: draft-ietf-pwe3-cbit-negotiation-04.txt<br>
&gt; &gt; &gt; &gt; &gt; &gt; Reviewer: Elwyn Davies<br>
&gt; &gt; &gt; &gt; &gt; &gt; Review Date: 19 June 2012<br>
&gt; &gt; &gt; &gt; &gt; &gt; IETF LC End Date: 15 June 2012<br>
&gt; &gt; &gt; &gt; &gt; &gt; IESG Telechat date: 21 June 2012<br>
&gt; &gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; Summary: <br>
&gt; &gt; &gt; &gt; &gt; &gt; Not ready. The proposal for the NOT PREFERRED
to PREFERRED<br>
&gt; &gt; &gt; &gt; &gt; transition<br>
&gt; &gt; &gt; &gt; &gt; &gt; case does not appear to be compatible with
the existing RFC 4447<br>
&gt; &gt; &gt; &gt; &gt; &gt; standard in the way stated and there are
a number of other minor<br>
&gt; &gt; &gt; &gt; &gt; issues.<br>
&gt; &gt; &gt; &gt; &gt; &gt; The draft is also in need of an editing pass
by an author whose<br>
&gt; &gt; &gt; &gt; &gt; mother<br>
&gt; &gt; &gt; &gt; &gt; &gt; tongue is English as there are parts where
the syntax is misleading<br>
&gt; &gt; &gt; &gt; &gt; &gt; Major issues: <br>
&gt; &gt; &gt; &gt; &gt; &gt; s3: The discussion of the NOT PREFERRED to
PREFERRED transition case<br>
&gt; &gt; &gt; &gt; &gt; &gt; (buried at the end of s3 - causing me to
ask 'what about this case?'<br>
&gt; &gt; &gt; &gt; &gt; &gt; during reading of s2 and most of s3) &nbsp;implies
that some existing RFC<br>
&gt; &gt; &gt; &gt; &gt; &gt; 4447 procedure applies. Clearly, if the PW
is not using the control<br>
&gt; &gt; &gt; &gt; &gt; word<br>
&gt; &gt; &gt; &gt; &gt; &gt; then there is nothing to do. &nbsp;On the
other hand, inspection of s6.2<br>
&gt; &gt; &gt; &gt; &gt; of<br>
&gt; &gt; &gt; &gt; &gt; &gt; RFC4447 indicates that once the two PEs have
agreed on c =1, 'setup<br>
&gt; &gt; &gt; &gt; &gt; is<br>
&gt; &gt; &gt; &gt; &gt; &gt; complete' and Label Mapping messages would
therefore be<br>
&gt; &gt; &gt; &gt; &gt; &gt; 'unexpected' (see item '-i' in second set
of bullets in s6.2 of RFC<br>
&gt; &gt; &gt; &gt; &gt; &gt; 4447). So, what procedure is to be used?
And what implications does<br>
&gt; &gt; &gt; &gt; &gt; this<br>
&gt; &gt; &gt; &gt; &gt; &gt; have for backwards compatibility? &nbsp;Wouldn't
it be generally simpler<br>
&gt; &gt; &gt; &gt; &gt; to<br>
&gt; &gt; &gt; &gt; &gt; &gt; apply the PREFERRED to NOT PREFERRED mechanism
to all case? <br>
&gt; &gt; &gt; &gt; &gt; [Lizhong] this draft is to solve the case to change
a PW from c=0 to<br>
&gt; &gt; &gt; &gt; &gt; c=1, that means one PE should change its use of
control word from NOT<br>
&gt; &gt; &gt; &gt; &gt; PREFERRED to PREFERRED. RFC4447 is already there
and deployed, and the<br>
&gt; &gt; &gt; &gt; &gt; PE will not always send its locally configured
preferrence according<br>
&gt; &gt; &gt; &gt; &gt; RFC4447, see PE1 behavior in section 2 step 1&amp;2.
That's why we could<br>
&gt; &gt; &gt; &gt; &gt; not simply apply the mechanism at the end of section
3. Hope it is<br>
&gt; &gt; &gt; &gt; &gt; clear. <br>
&gt; &gt; &gt; &gt; There are two issues here:<br>
&gt; &gt; &gt; &gt; - Clarity: RFC 4447 does not have any discussion of
what mighthappen if<br>
&gt; &gt; &gt; &gt; the configuration value changes. &nbsp;The draft focusses
on on transition<br>
&gt; &gt; &gt; &gt; direction but does not mention the other except for
one paragaph right<br>
&gt; &gt; &gt; &gt; at the end of s3. &nbsp;It is therefore reasonable
that somebody looking at<br>
&gt; &gt; &gt; &gt; this draft would wonder 'what about the other transition
direction?'.<br>
&gt; &gt; &gt; &gt; Whether or not anything needs to be done it would save
people wondering<br>
&gt; &gt; &gt; &gt; if you put in a sentence in the introduction to explain
that the other<br>
&gt; &gt; &gt; &gt; direction is not (or is) a problem. <br>
&gt; &gt; &gt; [Lizhong] accept. Add following: <br>
&gt; &gt; &gt; When PE changes the preference for the use of control word
from<br>
&gt; &gt; &gt; PREFERRED to NOT PREFERRED, it should follow [RFC4447],
and there is<br>
&gt; &gt; &gt; no problem. <br>
&gt; &gt; <br>
&gt; &gt; See below...<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; - Technical: The paragraph in s3 implies that the PREFERRED
to NOT<br>
&gt; &gt; &gt; &gt; PREFERRED direction will result in some part of the
RFC 4447 protocol<br>
&gt; &gt; &gt; &gt; being (re-)invoked. &nbsp;What part is not made very
clear. &nbsp;As far as I can<br>
&gt; &gt; &gt; &gt; see sending more messages other than Label Release
or Label Withdraw for<br>
&gt; &gt; &gt; &gt; this PW is not part of the RFC 4447 protocol and hence
will cause an<br>
&gt; &gt; &gt; &gt; error. &nbsp;Alternatively if it isn't reinvoked, the
PW will continue to use<br>
&gt; &gt; &gt; &gt; control words. &nbsp;Please explain what is going on
here. &nbsp;The fact that RFC<br>
&gt; &gt; &gt; &gt; 4447 has been deployed doesn't explain what is going
on. <br>
&gt; &gt; &gt; [Lizhong] now I understand you concern. The last sentance
of s3 is not<br>
&gt; &gt; &gt; clear. How about the following: <br>
&gt; &gt; &gt; In that case, local PE will always send Label Withdraw message
if<br>
&gt; &gt; &gt; already sending Label Mapping message, and then send new
Label Mapping<br>
&gt; &gt; &gt; message with C-bit value following the procedures defined
in<br>
&gt; &gt; &gt; [RFC4447]. <br>
&gt; &gt; <br>
&gt; &gt; I think we have reached the heart of the issue here: &nbsp;RFC
4447 does not<br>
&gt; &gt; mention changing the control word configuration. &nbsp;The combination
of the<br>
&gt; &gt; existing text in the draft and what you have just weittrn above<br>
&gt; &gt; indicates that *in both transition directions* the PE changing<br>
&gt; &gt; configuration notifies its peer by sending a Label Withdraw.
It is not<br>
&gt; &gt; immediately obvious to me that you could deduce this from RFC
4447 - if<br>
&gt; &gt; it is then there needs to be a pointer to the relevant section
in RFC<br>
&gt; &gt; 4447 to enlighten the ignorant like me. &nbsp;Otherwise the PREFERRED
to NOT<br>
&gt; &gt; PREFERRED transition is *not* just 'follow the RFC 4447 procedures'.</tt></font>
<br><font size=2><tt>&gt; [Lizhong] as an engineer, I interpret the configuration
changing as <br>
&gt; deleting and configuring again. Control word configuration changing
<br>
&gt; means deleting the old control word, and then configuring the new
<br>
&gt; control word, that means deleting PW configuration, and configuring
<br>
&gt; new PW configuration again. RFC4447 section 5.4.1 describe the <br>
&gt; procedure of PW deletion and configuration. When you apply the above<br>
&gt; procedure to PREFERRED to NOT PREFERRED transition, it works well,
<br>
&gt; while for NOT PREFERRED to PREFERRED transition, there is a problem.</tt></font>
<br><font size=2><tt>&gt; What if I add some description of the meaning
of control word <br>
&gt; changing at the end of s3, so as to make it clear?</tt></font>
<br><font size=2><tt>&gt; <br>
&gt; &gt; <br>
&gt; &gt; If I now understand correctly, the situation is as follows:<br>
&gt; &gt; - in both cases when there is a control word preference transition,
send<br>
&gt; &gt; a Label Withdraw.<br>
&gt; &gt; - in the NOT PREFERRED to PREFERRED case send Label Release also
(order<br>
&gt; &gt; not important), wait for a responses from peer, then send Label
Request<br>
&gt; &gt; and negotiate use of control word using Label Mapping C bit as
for a new<br>
&gt; &gt; PW (might result in either using or not using control word depending
on<br>
&gt; &gt; state in peer).<br>
&gt; &gt; - in the PREFERRED to NOT PREFERRED case, just negotiate C bit
to 0<br>
&gt; &gt; using Label Mapping - label will be maintained. [Need to check
that RFC<br>
&gt; &gt; 4447 is expecting/will allow this sequence.]<br>
&gt; &gt; <br>
&gt; &gt; If I have this straight, I think that the PREFERRED to NOT PREFERRED<br>
&gt; &gt; case needs some more words in s3 and an introduction in s2. (And
it<br>
&gt; &gt; would be easier to understand with this case in a separate sub-section
-<br>
&gt; &gt; sorry to harp on about this). &nbsp; </tt></font>
<br><font size=2><tt>&gt; [Lizhong] your above description is totally right.
How about <br>
&gt; changing the end of s3 as below:</tt></font>
<br><font size=2><tt>&gt; When Local PE changes the use of control word
from PREFERRED to NOT <br>
&gt; PREFERRED, the local PE would be able to negotiate the Control Word
<br>
&gt; to be not used by deleting the PW configuration with PREFERRED use
<br>
&gt; of control word, &nbsp;and configuring the PW again with NOT PREFERRED
<br>
&gt; use of control word. All of these procedures have been defined in
<br>
&gt; [RFC4447] section 5.4.1.</tt></font>
<br><font size=2><tt>&gt; <br>
&gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; Minor issues: <br>
&gt; &gt; &gt; &gt; &gt; &gt; s3: Has there been any discussion on possible
race conditions?<br>
&gt; &gt; &gt; &gt; &gt; &nbsp;Changing<br>
&gt; &gt; &gt; &gt; &gt; &gt; the configuration value during the message
exchange strikes me as<br>
&gt; &gt; &gt; &gt; &gt; &gt; dangerous - it is probably sufficient to
note that changesshould be<br>
&gt; &gt; &gt; &gt; &gt; &gt; suppressed during the Label Mapping message
exchange but I am not<br>
&gt; &gt; &gt; &gt; &gt; &gt; totally sure about this. <br>
&gt; &gt; &gt; &gt; &gt; [Lizhong] The message would be processed in sequence
in TCP-based LDP<br>
&gt; &gt; &gt; &gt; &gt; session. I do not see a problem here. But we do
have a note in section<br>
&gt; &gt; &gt; &gt; &gt; 3 for multi-segment PW for sequence processing.
<br>
&gt; &gt; &gt; &gt; There are several network round trips in the message
exchanges. &nbsp;The<br>
&gt; &gt; &gt; &gt; protocol and the configuration mechanism in a PE are
potentially<br>
&gt; &gt; &gt; &gt; separate threads. &nbsp;There is scope, depending on
the implementation, for<br>
&gt; &gt; &gt; &gt; the user at the 'remote' PE to change the configuration
during the<br>
&gt; &gt; &gt; &gt; message exchange making for a potential race condition.
<br>
&gt; &gt; &gt; [Lizhong] we discussed the race condition on the PWE3 maillist
from<br>
&gt; &gt; &gt; Spike, and for multi-segment PW, we add a note to ensure
the sequence<br>
&gt; &gt; &gt; processing for implementation.<br>
&gt; &gt; I look forward to the revised text.</tt></font>
<br><font size=2><tt>&gt; [Lizhong] How about add the following in s3:
for the local PE, <br>
&gt; before processing new configuration changing, the above message <br>
&gt; exchange process should be finished.</tt></font>
<br><font size=2><tt>&gt; <br>
&gt; &gt; &gt; &nbsp;<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; s3, bullet '-i': &nbsp;I completely misparsed
this section on first<br>
&gt; &gt; &gt; &gt; &gt; reading<br>
&gt; &gt; &gt; &gt; &gt; &gt; and I am still not absolutely sure what message
sequence is being<br>
&gt; &gt; &gt; &gt; &gt; &gt; specified. &nbsp;Working back from later
sections I *think* that the<br>
&gt; &gt; &gt; &gt; &gt; &gt; intention is:<br>
&gt; &gt; &gt; &gt; &gt; &gt; IF Mapping sent THEN { send Withdraw; send
Release;}<br>
&gt; &gt; &gt; &gt; &gt; &gt; Wait to receive Release<br>
&gt; &gt; &gt; &gt; &gt; &gt; The implication at present is that a Mapping
might not have been<br>
&gt; &gt; &gt; &gt; &gt; sent<br>
&gt; &gt; &gt; &gt; &gt; &gt; and then only a Release is needed: is this
a possibility? Please<br>
&gt; &gt; &gt; &gt; &gt; &gt; clarify.<br>
&gt; &gt; &gt; &gt; &gt; &gt; The picture in Appendix A suffers from the
same problem. <br>
&gt; &gt; &gt; &gt; &gt; [Lizhong] Adrian raise the same comment, and I
change it as below: <br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;-i. &nbsp;PE MUST send
a Label Release message to remote PE. If a<br>
&gt; &gt; &gt; &gt; &gt; PE <br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; has
previously sent a Label Mapping message to a remote<br>
&gt; &gt; &gt; &gt; &gt; PE, <br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; it MUST
also send a Label Withdraw message to the remote<br>
&gt; &gt; &gt; &gt; &gt; PE, <br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and
wait until it receives a Label Release message from<br>
&gt; &gt; &gt; &gt; &gt; the<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;remote
PE. <br>
&gt; &gt; &gt; &gt; What does it send first if both must be sent? &nbsp;The
text in the rest of<br>
&gt; &gt; &gt; &gt; the document implies withdraw then release. &nbsp;This
new text sort of<br>
&gt; &gt; &gt; &gt; implies release then withdraw but isn't really clear.
<br>
&gt; &gt; &gt; [Lizhong] both should be sent, and does not require the
sending<br>
&gt; &gt; &gt; sequence. The two messages does not have dependence. <br>
&gt; &gt; In that case, it is important to say so.</tt></font>
<br><font size=2><tt>&gt; [Lizhong] I will add a sentence in point &quot;i&quot;
to say so. How about below:</tt></font>
<br><font size=2><tt>&gt; Note: above Label Release message and Label Withdraw
message sending<br>
&gt; does not require specific sequence.</tt></font>
<br><font size=2><tt>&gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; s3, discussion of multi-segment PWs: The
statement that S-PE's<br>
&gt; &gt; &gt; &gt; &gt; SHOULD<br>
&gt; &gt; &gt; &gt; &gt; &gt; assume an initial passive role seems to have
several problems:<br>
&gt; &gt; &gt; &gt; &gt; &gt; - Does this mean that changing the configuration
of an S-PE would<br>
&gt; &gt; &gt; &gt; &gt; not<br>
&gt; &gt; &gt; &gt; &gt; &gt; provoke the new mechanisms?<br>
&gt; &gt; &gt; &gt; &gt; &gt; - The passive role situation is only specified
for some sorts of<br>
&gt; &gt; &gt; &gt; &gt; linked<br>
&gt; &gt; &gt; &gt; &gt; &gt; FECs in RFC 6073 - what about other cases?<br>
&gt; &gt; &gt; &gt; &gt; &gt; - What are the consequences for ignoring
the SHOULD in this case? (I<br>
&gt; &gt; &gt; &gt; &gt; &gt; have to say I am unsure that RFC 6073 deals
with this problem<br>
&gt; &gt; &gt; &gt; &gt; either.) <br>
&gt; &gt; &gt; &gt; &gt; [Lizhong] we follow RFC6073, and passive role
is only applied for the<br>
&gt; &gt; &gt; &gt; &gt; PW FEC, other cases are out of scope. <br>
&gt; &gt; &gt; &gt; Why? This needs an explanation. Also this doesn't cover
the point about<br>
&gt; &gt; &gt; &gt; whether reconfig of an S-PE is allowed and how this
squares with the<br>
&gt; &gt; &gt; &gt; passive role.<br>
&gt; &gt; &gt; &gt; &gt; SHOULD means highly recommended. We do not meet
any problem when<br>
&gt; &gt; &gt; &gt; &gt; implementing RFC6073. Do you suggest to change
this to MUST? <br>
&gt; &gt; &gt; &gt; Whenever a specification includes a 'SHOULD' the question
arises of what<br>
&gt; &gt; &gt; &gt; alternatives there might be and what is the reason
for preferring the<br>
&gt; &gt; &gt; &gt; suggested solution. &nbsp;In the original setup, it
is fairly clearthat life<br>
&gt; &gt; &gt; &gt; is easier letting setup progress from &nbsp;one end
to the other (although<br>
&gt; &gt; &gt; &gt; this is not spelt out - I would have argued for this
had &nbsp;I reviewed the<br>
&gt; &gt; &gt; &gt; doc). &nbsp;For the configuration change this is less
obvious. &nbsp;Regarding the<br>
&gt; &gt; &gt; &gt; point about reconfig of the &nbsp;S-PE, it is going
to make life more<br>
&gt; &gt; &gt; &gt; complicated if the S-PE has to tell the T-PE to be
active so it can be<br>
&gt; &gt; &gt; &gt; passive. &nbsp;I would therefore argue that probably
the notion of passivity<br>
&gt; &gt; &gt; &gt; is irrelevant to the transition use case. &nbsp;Whether
it should be SHOULD<br>
&gt; &gt; &gt; &gt; or MUST is therefore moot. <br>
&gt; &gt; &gt; [Lizhong] how about the following? Because we just refer
to <br>
&gt; &gt; RFC6073, and does not add anything new. <br>
&gt; &gt; &gt; An initial passive role is defined in [RFC6073] for S-PE.<br>
&gt; &gt; I can't see that this really helps.<br>
&gt; &gt; There are still two points at issue here:<br>
&gt; &gt; - Why are the cases other than the one in RFC 4447 that refers
to a<br>
&gt; &gt; passive S-PE out of scope? &nbsp;There aren't any statements
to this effect<br>
&gt; &gt; in the document.</tt></font>
<br><font size=2><tt>&gt; [Lizhong] the passive role is not for any specific
cases. The <br>
&gt; passive role is for the processing of message (e.g, label mapping,
<br>
&gt; label request). I will explicitly say that in the section.</tt></font>
<br><font size=2><tt>&gt; <br>
&gt; &gt; - It is difficult for a S-PE that has its control word configuration<br>
&gt; &gt; change to act passively. &nbsp;If it is really passive than nothing
will<br>
&gt; &gt; happen until the label is withdrawn. &nbsp;Otherwise it can't
be descibed as<br>
&gt; &gt; passive for this action. &nbsp;The text in the current draft
actually<br>
&gt; &gt; describes what is specified in RFC 6073 when talking 'passive'
rather<br>
&gt; &gt; than explaining what happens when the control word configuration<br>
&gt; &gt; changes.</tt></font>
<br><font size=2><tt>&gt; [Lizhong] the control word configuration changing
talking about in <br>
&gt; this draft only happens on T-PE, not S-PE. The S-PE is a passive <br>
&gt; role for the message processing. I will make this clear in the draft.</tt></font>
<br><font size=2><tt>&gt; <br>
&gt; &gt; &gt; &nbsp;<br>
&gt; &gt; &gt; &gt; &gt; [Lizhong] has been revised in v-04.<br>
&gt; &gt; &gt; &gt; Not as far as I can see. <br>
&gt; &gt; &gt; [Lizhong] write &quot;pseudowire&quot; directly in the text,
not PW. <br>
&gt; &gt; There are lots of instances of PW still left in v04. Expand acronym
=&gt;<br>
&gt; &gt; define what it means on first usage i.e pseudowire (PW). &nbsp;Same
for the<br>
&gt; &gt; various other acronyms that aren't defined in the text.</tt></font>
<br><font size=2><tt>&gt; [Lizhong] accept<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; s2: Expand acronym PE. <br>
&gt; &gt; &gt; &gt; &gt; [Lizhong] accept <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; s2, 2nd sentence: s/configurable/configured/
<br>
&gt; &gt; &gt; &gt; &gt; [Lizhong] configurable is right. <br>
&gt; &gt; &gt; &gt; Leave that one to the RFc Editor.<br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; s2, 3rd and 4th sentences: I *think* this
text is trying to say: <br>
&gt; &gt; &gt; &gt; &gt; &gt; &nbsp; The intention of the control word
negotiation is that the control<br>
&gt; &gt; &gt; &gt; &gt; word<br>
&gt; &gt; &gt; &gt; &gt; &gt; will be used when both endpoints are configured
with control word<br>
&gt; &gt; &gt; &gt; &gt; usage<br>
&gt; &gt; &gt; &gt; &gt; &gt; PREFERRED. &nbsp;However if one endpoint
is initially configured with<br>
&gt; &gt; &gt; &gt; &gt; control<br>
&gt; &gt; &gt; &gt; &gt; &gt; word usage NOT PREFERRED but later changes
to PREFERRED, a PW<br>
&gt; &gt; &gt; &gt; &gt; between<br>
&gt; &gt; &gt; &gt; &gt; &gt; the endpoints will not transition to usage
of the control word as<br>
&gt; &gt; &gt; &gt; &gt; &gt; explained below. <br>
&gt; &gt; &gt; &gt; &gt; [Lizhong] no, the case is that operator deploys
PW with control word<br>
&gt; &gt; &gt; &gt; &gt; used in the first phase. In the second phase,
they want to upgrade<br>
&gt; &gt; &gt; &gt; &gt; their PW service to use control word. Two different
deployment<br>
&gt; &gt; &gt; &gt; &gt; timeframes.<br>
&gt; &gt; &gt; &gt; That is what my sentence says. <br>
&gt; &gt; &gt; [Lizhong] ok. <br>
&gt; &gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; s3: It would be much clearer if s3 was divided
into 3 sub-sections<br>
&gt; &gt; &gt; &gt; &gt; &gt; (possibly reordered):<br>
&gt; &gt; &gt; &gt; &gt; &gt; - PREFERRED to NOT PREFERRED transition<br>
&gt; &gt; &gt; &gt; &gt; &gt; - NOT PREFERRED to PREFERRED transition<br>
&gt; &gt; &gt; &gt; &gt; &gt; - Multi-segment case (which should refer
to both previous cases)<br>
&gt; &gt; &gt; &gt; &gt; &gt; The pointer to the diagram in Appendix A
could usefully occur in the<br>
&gt; &gt; &gt; &gt; &gt; &gt; introduction to s3. &nbsp;If this was adopted
s3.1 could either be a<br>
&gt; &gt; &gt; &gt; &gt; fourth<br>
&gt; &gt; &gt; &gt; &gt; &gt; sub-section or a sub-sub-section of the PREFERRED
to NOT PREFERRED<br>
&gt; &gt; &gt; &gt; &gt; &gt; section. <br>
&gt; &gt; &gt; &gt; &gt; [Lizhong] PREFERRED to NOT PREFERRED does not
introduce any new.<br>
&gt; &gt; &gt; &gt; &gt; Multi-segment case is fully inherited from single-segment
case. It<br>
&gt; &gt; &gt; &gt; &gt; would be redundancy to have sub-sections here.
<br>
&gt; &gt; &gt; &gt; I disagree strongly. &nbsp;The multi-segment case affects
the other RFC and<br>
&gt; &gt; &gt; &gt; needs to be made to stand out so that implementors
can see where the<br>
&gt; &gt; &gt; &gt; changes occur. &nbsp;The PREFERRED to NOT PREFERRED
case also ought to be<br>
&gt; &gt; &gt; &gt; separated whether or not I am right about this case.
<br>
&gt; &gt; &gt; [Lizhong] how about only divide multi-segment? The case
of PREFERRED to <br>
&gt; &gt; &gt; NOT PREFERRED case is only for reference, and the text is
not many.<br>
&gt; &gt; That is so, but it is a change of subject and the fact that it
will then<br>
&gt; &gt; be in the table of contents makes it easier for implementors
to find the<br>
&gt; &gt; relevant text. &nbsp;I wouldn't call it 'redundant'.<br>
&gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &gt; s3, last para/Appendix A: &nbsp;The diagram
doesn't cover the PREFERRED<br>
&gt; &gt; &gt; &gt; &gt; to<br>
&gt; &gt; &gt; &gt; &gt; &gt; NOT PREFERRED transition. <br>
&gt; &gt; &gt; &gt; &gt; [Lizhong] no, there is a &quot;no&quot; branch
under &quot;NOT Preferred to<br>
&gt; &gt; &gt; &gt; &gt; Preferred&quot; to cover &quot;PREFERRED to NOT
PREFERRED&quot;. Anyway, the diagram<br>
&gt; &gt; &gt; &gt; &gt; discription should be &quot;NOT Preferred to Preferred&quot;
which is wrong in<br>
&gt; &gt; &gt; &gt; &gt; v-04. <br>
&gt; &gt; Need to check it reflects the Label Withdraw message needed in
the<br>
&gt; &gt; PREFERRED to NOT PREFERRED case. </tt></font>
<br><font size=2><tt>&gt; [Lizhong] ok, I could add Label Withdraw there.<br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
</tt></font>
--=_alternative 005551CA48257A24_=--


From d3e3e3@gmail.com  Thu Jun 21 17:30:31 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 250B511E8091 for <gen-art@ietfa.amsl.com>; Thu, 21 Jun 2012 17:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.509
X-Spam-Level: 
X-Spam-Status: No, score=-103.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3yc9Cu9824Af for <gen-art@ietfa.amsl.com>; Thu, 21 Jun 2012 17:30:29 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7363A11E80A1 for <gen-art@ietf.org>; Thu, 21 Jun 2012 17:30:29 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so1235809ghb.31 for <gen-art@ietf.org>; Thu, 21 Jun 2012 17:30:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=jXbom7BtqOv7GxySMvrZ1zEuqUVIvY9kepje9EWh6Lw=; b=SLXm2QYiyCBMxZ551qYpsLxGqmDDsn3t5ZZnOrzN4J2FG+kR+ZAq5WulSEcLDS84ix 6dKhK7WUoiP+OoMoJ5gqNxTO9Q/ACJ3aJ//DjzPtx6OkHETzoh0JA7RhPJgK9ACFsSHP wsrGTgdw7U4QpRESPBTw29YvtwvEpoq2VqLCIwg9HhFFpZTzutFguP4QyrO/++00vz4N 8hIxpUysrr8FES9WfKv6k8Uu8WvTnv8gyRObsZ1p1ysaObDr4IGpm9pHwPrzvtwn/fGR uvAUTOPJT5W/xh5JekAhuqdUpV9V/a+izYNU61vE5RqiVMapwKNsQM1nwau00BUbO1Yt MnUA==
Received: by 10.50.34.200 with SMTP id b8mr158143igj.50.1340325028864; Thu, 21 Jun 2012 17:30:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.16.227 with HTTP; Thu, 21 Jun 2012 17:30:08 -0700 (PDT)
In-Reply-To: <25DC600D0CC1F2479C7053ADEB93004E699DB9D54C@EUSAACMS0703.eamcs.ericsson.se>
References: <25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7@EUSAACMS0703.eamcs.ericsson.se> <CAF4+nEH3XmK=b0nN8Pcozc_6LB2vxajJ6OM4t7VvZ1Q-Fx13hQ@mail.gmail.com> <CAF4+nEEr7Ys4rZt7Ja97ygzy3bQwQ7J6ap2QW90rfi36Xv=X-w@mail.gmail.com> <25DC600D0CC1F2479C7053ADEB93004E699DB9D54C@EUSAACMS0703.eamcs.ericsson.se>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 21 Jun 2012 20:30:08 -0400
Message-ID: <CAF4+nEH=k8BMB+FtJr2gpUXPYoQVcuVFOsak5M7qwwbrBnWzGg@mail.gmail.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-trill-clear-correct.all@tools.ietf.org" <draft-ietf-trill-clear-correct.all@tools.ietf.org>, Ayan Banerjee <ayabaner@gmail.com>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-trill-clear-correct-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 00:30:31 -0000

Hi Meral,

On Wed, Jun 20, 2012 at 4:32 PM, Meral Shirazipour
<meral.shirazipour@ericsson.com> wrote:
> Hi Donald,
> =A0 Thank you for considering the comments. Please see below.
>
> Best Regards,
> Meral
>
> ---
> Meral Shirazipour
> Ericsson
> Research
> www.ericsson.com
>
>
> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: June-20-12 15:24
> To: Meral Shirazipour
> Cc: draft-ietf-trill-clear-correct.all@tools.ietf.org; gen-art@ietf.org; =
Ayan Banerjee
> Subject: Fwd: Gen-ART Last Call review of draft-ietf-trill-clear-correct-=
03.txt
>
> Hi Meral,
>
> A real response this time...
>
> Thanks for your thorough review. See below:
>
> On Tue, Jun 19, 2012 at 11:51 AM, Meral Shirazipour <meral.shirazipour@er=
icsson.com> wrote:
>> I am the assigned Gen-ART reviewer for
>> draft-ietf-trill-clear-correct-03.txt. For background on Gen-ART,
>> please see the FAQ at <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ=
.html>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>>
>> Document: draft-ietf-trill-clear-correct-03
>> Reviewer: Meral Shirazipour
>> Review Date: June-18-2012
>> IETF LC End Date: June-20-2012
>> IESG Telechat date: June-21-2012
>>
>>
>> Summary:
>> The document is ready for publication as a standards track RFC,
>> however I have a few comments.
>
> Thanks.
>
>> Minor issues:
>>
>> TRILL-PORT-VER sub-TLV should be "PORT-TRILL-VER" sub-TLV.(there are a
>> few
>> occurrences)
>
> Yes, thanks for spotting that.
>
>> Nits/editorial comments:
>>
>> - Suggestion: [Page 6], line 2, spell out first occurrence LSP
>
> OK.
>
>> - Suggestion: [Page 6], line 5, "overload bit on" ----> "overload bit se=
t"
>
> OK.
>
>> - Clarification:[Page 6], Section 2.1, line 5, add a comma "," after
>> "traffic engineered frames"
>
> OK.
>
>> - Typo:[Page 6], last word, "contain" --missing s--> "contains"
>
> I believe the current wording is correct.
>
> [msh] sorry about that.
>
>> - Suggestion: [Page 7], Section 2.2, line 2, spell out first
>> occurrence of "Reverse Path Forwarding Check" and then use "RPFC" in
>> the rest of the document.
>
> It depends a little on the context but =A0agree that most can be changed =
to RPFC.
> [msh] ok
>
>> - Clarification:[Page 10], Section 2.4.2.3, line 5, sentence starting
>> with
>> "RB2 MUST advertise ...": we could omit the second occurrence of "it
>> might use" in that sentence.
>
> OK.
>
>> - Clarification:[Page 10], Section 2.4.2.3, 3rd line from last, "end
>> stations connected to RB": "a RB" or "RBs"?
>
> Should be "end stations connected to RB3".
>
> [msh] ok
>
>> - Typo: [Page 11], Section 3.1,"( j, k)" --remove extra space--> "(j, k)=
"
>
> OK.
>
>> - Suggestion: [Page 11], Section 3.2, "already in flight" ---->
>> "already in transmission"
>
> I think the current wording is better.
>
> [msh] ok
>
>> - Typo [Page 12]:"many multi-destination frame"--missing s--> "many
>> multi-destination frames"
>
> OK.
>
>> - Clarification:[Page 13], Point 4. , Sentence 2: suggested clarificatio=
n:
>>
>> "It does so by checking LSPs it receives and updating its link state
>> database for any of its nicknames held with higher priority by another
>> TRILL Switch that is IS-IS reachable."
>
> I have no problem dropping "in" so it says "...checking LSPs..."
> rather than "...checking in LSPs..." but I think the rest of the change y=
ou suggest makes it slightly wrong and so would prefer to keep the rest of =
the wording of that sentence.
>
> [msh] In this case I think keeping the "in" is actually better. I underst=
and the sentence but had to read it a few times.

OK.

>> - Typo [Page 14]:"unicast Channel message"--missing s-->"unicast
>> Channel messages"
>
> OK.
>
>> - Typo [Page 16]: Section 5.2,"Routeing" ----> "Routing"
>
> The spelling used in the ISO 10589:2002 standard's title and the naming o=
f this field therein includes the "e".
>
> [msh] ok
>
>> - Suggestion:[Page 16],last sentence, suggestion: "This safety margin
>> is called "Margin" below."
>
> OK.
>
>> - Typo [Page 18]:"a specified in [RFC6325]"--missing s-->"as specified
>> in [RFC6325]"
>
> OK.
>
>> - Suggestion: [Page 19], spell out first occurrence of EISS
>
> OK.
>
>> - Suggestion:[Page 21], Point 1, not clear what the new text becomes.
>> Suggestion: refer to last paragraph of section 3.1 instead of
>> paragraph before 3.2, and propose the new sentence.
>
> OK.
>
>> - Clarification:[Page 21], Point 2, it is not clear what the change is
>> to section 3.2 of RFC6327.
>
> OK.
>
>> - Clarification:[Page 21], Point 3, it would be clearer to say "bullet
>> A9 is added" (if this is an event like the rest of the bullets in
>> section 3.3 of
>> RFC6327)
>
> Guess this does need clarification as its not an event, its a "o ..." typ=
e bullet item "after the list of events". I'll clarify.
>
> [msh]ok
>
>> - Clarification:[Page 22], section 10.1,"disagreement over the
>> Designated VLAN or the like". Suggestion: replace the term "or the
>> like" with other examples or remove the term.
>
> How about replacing "... in the face of partitioned VLANs or disagreement=
 over the Designated VLAN or the like in a link." with "... in the face of =
decreased VLAN connectivity in a link such as partitioned VLANs, many VLANs=
 disabled on ports, or disagreement over the Designated VLAN."
>
> [msh] ok
>
>> -Typo: [Page 22], section 10.1, "each others frames"---->"each other's
>> frames"
>
> OK.
>
>> -Typo: [Page 24], "DRB SHOULD NOT appointed"---->"DRB SHOULD NOT
>> appoint", "an VLAN"---->"a VLAN", "RBridged"---->"RBridge"
>
> OK.
>
>> -Clarification:[Page 25], Section 11, Point 1, "The previously
>> reserved", reference to document.
>
> OK. The block of nicknames from 0xFFC0 through 0xFFFE is reserved by the =
TRILL base protocol document [RFC6325].
>
>> - Clarification: [page 19/page 27], Informative References, reference
>> [802], to verify which standard we want to refer to for Canonical Format=
 Indicator:
>>
>> If it is "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan
>> Area
>> Networks: Overview and Architecture", then the date should be 7
>> February 2001."
>
> All copies I have seen clearly say 8 March 2001 on the cover.
>
> [msh] ok, since the reference is only for a definition. I made a typo too=
, it is 7 Feb 2002 that I saw-maybe I looked at the wrong document: http://=
standards.ieee.org/about/get/802/802.html ? )

Well, I went back and double checked... And the actual cover date of
the copy I have, which was the one distributed to IEEE 802 members via
the annual CD of all 802 standards, says 8 March 2002, which is what
it actually says in the draft, not 2001 as I typed above. Anyway, I'm
going to leave it as is for now.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street,=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

>> However this specific document does not define CIF. You may want to
>> refer to 802.1Q-2005.
> [Should be CFI above.]
>
> [msh] ok
>
> While "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan Area N=
etworks: Overview and Architecture" does not define the acronym CFI, it doe=
s define "canonical format" and "noncanonical format".
> There is no IEEE Std 802.1Q-2005 any more, it having been replaced by IEE=
E Std 802.1Q-2011 which does not define the acronym CFI. Doing some searche=
s, although 802.1Q-2011 replaces the CFI bit in Customer VLAN tags with the=
 DEI bit, there are a few occurrences of "canonical" left in 802.1Q-2011, m=
ost to say that bridges conformant to 802.1Q-2011 will interoperate with br=
idges that believe in the CFI bit as long as those bridges don't actually h=
ave any Token Ring interfaces so they will always set the CF bit to zero. Q=
uoting from page 3 of
> 802.1Q-2011: "The meanings of the terms Canonical format and Noncanonical=
 format are discussed in IEEE Std 802.".
>
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> =A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
> =A0155 Beaver Street,=A0Milford, MA 01757 USA
> =A0d3e3e3@gmail.com
>
>> Thanks,
>> Meral
>>
>> ---
>> Meral Shirazipour
>> Ericsson
>> Research
>> www.ericsson.com

From meral.shirazipour@ericsson.com  Fri Jun 22 06:59:50 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460DA21F85AF for <gen-art@ietfa.amsl.com>; Fri, 22 Jun 2012 06:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2LvtudKXajXo for <gen-art@ietfa.amsl.com>; Fri, 22 Jun 2012 06:59:49 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 339EB21F85AE for <gen-art@ietf.org>; Fri, 22 Jun 2012 06:59:49 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q5MDxcMr007253; Fri, 22 Jun 2012 08:59:46 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.57]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Fri, 22 Jun 2012 09:59:34 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 22 Jun 2012 09:59:12 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-trill-clear-correct-03.txt
Thread-Index: Ac1QDjuhi0PdSLdtTICuuW5KCoiBnQAcMf6g
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E699DB9E0B4@EUSAACMS0703.eamcs.ericsson.se>
References: <25DC600D0CC1F2479C7053ADEB93004E699DAFB0A7@EUSAACMS0703.eamcs.ericsson.se> <CAF4+nEH3XmK=b0nN8Pcozc_6LB2vxajJ6OM4t7VvZ1Q-Fx13hQ@mail.gmail.com> <CAF4+nEEr7Ys4rZt7Ja97ygzy3bQwQ7J6ap2QW90rfi36Xv=X-w@mail.gmail.com> <25DC600D0CC1F2479C7053ADEB93004E699DB9D54C@EUSAACMS0703.eamcs.ericsson.se> <CAF4+nEH=k8BMB+FtJr2gpUXPYoQVcuVFOsak5M7qwwbrBnWzGg@mail.gmail.com>
In-Reply-To: <CAF4+nEH=k8BMB+FtJr2gpUXPYoQVcuVFOsak5M7qwwbrBnWzGg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-trill-clear-correct.all@tools.ietf.org" <draft-ietf-trill-clear-correct.all@tools.ietf.org>, Ayan Banerjee <ayabaner@gmail.com>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-trill-clear-correct-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 13:59:50 -0000

Hi Donald,
   Ok, thanks for considering the suggestions.

BR,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com



> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: June-21-12 20:30
> To: Meral Shirazipour
> Cc: draft-ietf-trill-clear-correct.all@tools.ietf.org; gen-art@ietf.org; =
Ayan
> Banerjee
> Subject: Re: Gen-ART Last Call review of draft-ietf-trill-clear-correct-0=
3.txt
>=20
> Hi Meral,
>=20
> On Wed, Jun 20, 2012 at 4:32 PM, Meral Shirazipour
> <meral.shirazipour@ericsson.com> wrote:
> > Hi Donald,
> > =A0 Thank you for considering the comments. Please see below.
> >
> > Best Regards,
> > Meral
> >
> > ---
> > Meral Shirazipour
> > Ericsson
> > Research
> > www.ericsson.com
> >
> >
> > -----Original Message-----
> > From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> > Sent: June-20-12 15:24
> > To: Meral Shirazipour
> > Cc: draft-ietf-trill-clear-correct.all@tools.ietf.org;
> > gen-art@ietf.org; Ayan Banerjee
> > Subject: Fwd: Gen-ART Last Call review of
> > draft-ietf-trill-clear-correct-03.txt
> >
> > Hi Meral,
> >
> > A real response this time...
> >
> > Thanks for your thorough review. See below:
> >
> > On Tue, Jun 19, 2012 at 11:51 AM, Meral Shirazipour
> <meral.shirazipour@ericsson.com> wrote:
> >> I am the assigned Gen-ART reviewer for
> >> draft-ietf-trill-clear-correct-03.txt. For background on Gen-ART,
> >> please see the FAQ at <http://www.alvestrand.no/ietf/gen/art/gen-art-
> FAQ.html>.
> >>
> >> Please resolve these comments along with any other Last Call comments
> >> you may receive.
> >>
> >>
> >> Document: draft-ietf-trill-clear-correct-03
> >> Reviewer: Meral Shirazipour
> >> Review Date: June-18-2012
> >> IETF LC End Date: June-20-2012
> >> IESG Telechat date: June-21-2012
> >>
> >>
> >> Summary:
> >> The document is ready for publication as a standards track RFC,
> >> however I have a few comments.
> >
> > Thanks.
> >
> >> Minor issues:
> >>
> >> TRILL-PORT-VER sub-TLV should be "PORT-TRILL-VER" sub-TLV.(there are
> >> a few
> >> occurrences)
> >
> > Yes, thanks for spotting that.
> >
> >> Nits/editorial comments:
> >>
> >> - Suggestion: [Page 6], line 2, spell out first occurrence LSP
> >
> > OK.
> >
> >> - Suggestion: [Page 6], line 5, "overload bit on" ----> "overload bit =
set"
> >
> > OK.
> >
> >> - Clarification:[Page 6], Section 2.1, line 5, add a comma "," after
> >> "traffic engineered frames"
> >
> > OK.
> >
> >> - Typo:[Page 6], last word, "contain" --missing s--> "contains"
> >
> > I believe the current wording is correct.
> >
> > [msh] sorry about that.
> >
> >> - Suggestion: [Page 7], Section 2.2, line 2, spell out first
> >> occurrence of "Reverse Path Forwarding Check" and then use "RPFC" in
> >> the rest of the document.
> >
> > It depends a little on the context but =A0agree that most can be change=
d to
> RPFC.
> > [msh] ok
> >
> >> - Clarification:[Page 10], Section 2.4.2.3, line 5, sentence starting
> >> with
> >> "RB2 MUST advertise ...": we could omit the second occurrence of "it
> >> might use" in that sentence.
> >
> > OK.
> >
> >> - Clarification:[Page 10], Section 2.4.2.3, 3rd line from last, "end
> >> stations connected to RB": "a RB" or "RBs"?
> >
> > Should be "end stations connected to RB3".
> >
> > [msh] ok
> >
> >> - Typo: [Page 11], Section 3.1,"( j, k)" --remove extra space--> "(j, =
k)"
> >
> > OK.
> >
> >> - Suggestion: [Page 11], Section 3.2, "already in flight" ---->
> >> "already in transmission"
> >
> > I think the current wording is better.
> >
> > [msh] ok
> >
> >> - Typo [Page 12]:"many multi-destination frame"--missing s--> "many
> >> multi-destination frames"
> >
> > OK.
> >
> >> - Clarification:[Page 13], Point 4. , Sentence 2: suggested clarificat=
ion:
> >>
> >> "It does so by checking LSPs it receives and updating its link state
> >> database for any of its nicknames held with higher priority by
> >> another TRILL Switch that is IS-IS reachable."
> >
> > I have no problem dropping "in" so it says "...checking LSPs..."
> > rather than "...checking in LSPs..." but I think the rest of the change=
 you
> suggest makes it slightly wrong and so would prefer to keep the rest of t=
he
> wording of that sentence.
> >
> > [msh] In this case I think keeping the "in" is actually better. I under=
stand the
> sentence but had to read it a few times.
>=20
> OK.
>=20
> >> - Typo [Page 14]:"unicast Channel message"--missing s-->"unicast
> >> Channel messages"
> >
> > OK.
> >
> >> - Typo [Page 16]: Section 5.2,"Routeing" ----> "Routing"
> >
> > The spelling used in the ISO 10589:2002 standard's title and the naming=
 of
> this field therein includes the "e".
> >
> > [msh] ok
> >
> >> - Suggestion:[Page 16],last sentence, suggestion: "This safety margin
> >> is called "Margin" below."
> >
> > OK.
> >
> >> - Typo [Page 18]:"a specified in [RFC6325]"--missing s-->"as
> >> specified in [RFC6325]"
> >
> > OK.
> >
> >> - Suggestion: [Page 19], spell out first occurrence of EISS
> >
> > OK.
> >
> >> - Suggestion:[Page 21], Point 1, not clear what the new text becomes.
> >> Suggestion: refer to last paragraph of section 3.1 instead of
> >> paragraph before 3.2, and propose the new sentence.
> >
> > OK.
> >
> >> - Clarification:[Page 21], Point 2, it is not clear what the change
> >> is to section 3.2 of RFC6327.
> >
> > OK.
> >
> >> - Clarification:[Page 21], Point 3, it would be clearer to say
> >> "bullet
> >> A9 is added" (if this is an event like the rest of the bullets in
> >> section 3.3 of
> >> RFC6327)
> >
> > Guess this does need clarification as its not an event, its a "o ..." t=
ype bullet
> item "after the list of events". I'll clarify.
> >
> > [msh]ok
> >
> >> - Clarification:[Page 22], section 10.1,"disagreement over the
> >> Designated VLAN or the like". Suggestion: replace the term "or the
> >> like" with other examples or remove the term.
> >
> > How about replacing "... in the face of partitioned VLANs or disagreeme=
nt
> over the Designated VLAN or the like in a link." with "... in the face of
> decreased VLAN connectivity in a link such as partitioned VLANs, many VLA=
Ns
> disabled on ports, or disagreement over the Designated VLAN."
> >
> > [msh] ok
> >
> >> -Typo: [Page 22], section 10.1, "each others frames"---->"each
> >> other's frames"
> >
> > OK.
> >
> >> -Typo: [Page 24], "DRB SHOULD NOT appointed"---->"DRB SHOULD NOT
> >> appoint", "an VLAN"---->"a VLAN", "RBridged"---->"RBridge"
> >
> > OK.
> >
> >> -Clarification:[Page 25], Section 11, Point 1, "The previously
> >> reserved", reference to document.
> >
> > OK. The block of nicknames from 0xFFC0 through 0xFFFE is reserved by th=
e
> TRILL base protocol document [RFC6325].
> >
> >> - Clarification: [page 19/page 27], Informative References, reference
> >> [802], to verify which standard we want to refer to for Canonical Form=
at
> Indicator:
> >>
> >> If it is "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan
> >> Area
> >> Networks: Overview and Architecture", then the date should be 7
> >> February 2001."
> >
> > All copies I have seen clearly say 8 March 2001 on the cover.
> >
> > [msh] ok, since the reference is only for a definition. I made a typo
> > too, it is 7 Feb 2002 that I saw-maybe I looked at the wrong document:
> > http://standards.ieee.org/about/get/802/802.html ? )
>=20
> Well, I went back and double checked... And the actual cover date of the =
copy I
> have, which was the one distributed to IEEE 802 members via the annual CD=
 of
> all 802 standards, says 8 March 2002, which is what it actually says in t=
he draft,
> not 2001 as I typed above. Anyway, I'm going to leave it as is for now.
>=20
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> =A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
> =A0155 Beaver Street,=A0Milford, MA 01757 USA
> =A0d3e3e3@gmail.com
>=20
> >> However this specific document does not define CIF. You may want to
> >> refer to 802.1Q-2005.
> > [Should be CFI above.]
> >
> > [msh] ok
> >
> > While "IEEE Std 802-2001: IEEE Standard for Local and Metropolitan Area
> Networks: Overview and Architecture" does not define the acronym CFI, it =
does
> define "canonical format" and "noncanonical format".
> > There is no IEEE Std 802.1Q-2005 any more, it having been replaced by
> > IEEE Std 802.1Q-2011 which does not define the acronym CFI. Doing some
> > searches, although 802.1Q-2011 replaces the CFI bit in Customer VLAN
> > tags with the DEI bit, there are a few occurrences of "canonical" left
> > in 802.1Q-2011, most to say that bridges conformant to 802.1Q-2011
> > will interoperate with bridges that believe in the CFI bit as long as
> > those bridges don't actually have any Token Ring interfaces so they
> > will always set the CF bit to zero. Quoting from page 3 of
> > 802.1Q-2011: "The meanings of the terms Canonical format and
> Noncanonical format are discussed in IEEE Std 802.".
> >
> > Thanks,
> > Donald
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
> > =A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
> > =A0155 Beaver Street,=A0Milford, MA 01757 USA
> > =A0d3e3e3@gmail.com
> >
> >> Thanks,
> >> Meral
> >>
> >> ---
> >> Meral Shirazipour
> >> Ericsson
> >> Research
> >> www.ericsson.com

From Tom.Haynes@netapp.com  Fri Jun 22 08:06:16 2012
Return-Path: <Tom.Haynes@netapp.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D81C821F86F7; Fri, 22 Jun 2012 08:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8fEOXcta-sQ4; Fri, 22 Jun 2012 08:06:16 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id DF36021F86E5; Fri, 22 Jun 2012 08:06:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,458,1336374000"; d="scan'208";a="657232717"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 22 Jun 2012 08:06:15 -0700
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q5MF6FDB015259; Fri, 22 Jun 2012 08:06:15 -0700 (PDT)
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.92]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0298.004; Fri, 22 Jun 2012 08:05:23 -0700
From: "Haynes, Tom" <Tom.Haynes@netapp.com>
To: "rbarnes@bbn.com" <rbarnes@bbn.com>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org" <draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [nfsv4] Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11 (fwd)
Thread-Index: AQHNUIiR3/6yfq+JwEWuYsxcwIlj9Q==
Date: Fri, 22 Jun 2012 15:06:14 +0000
Message-ID: <CC08E06F.1AFEC%tom.haynes@netapp.com>
In-Reply-To: <alpine.LFD.2.02.1206201253010.38625@jlentini-linux.nane.netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A3AB0AC6EF04794EB4191E199A92143B@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 22 Jun 2012 08:29:32 -0700
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [Gen-art] [nfsv4] Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11 (fwd)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:06:17 -0000

<comments inline>

On 6/20/12 11:53 AM, "James Lentini" <jlentini@netapp.com> wrote:

>
>Below is the Gen-ART review comments for the FedFS admin protocol.
>
>-james
>
>---------- Forwarded message ----------
>Date: Tue, 19 Jun 2012 11:31:42 -0400
>From: Richard L. Barnes <rbarnes@bbn.com>
>To: ietf@ietf.org, The IESG <iesg@ietf.org>,
>    draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org, gen-art@ietf.org
>Subject: Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11
>
>I am the assigned Gen-ART reviewer for this draft. For background on
>Gen-ART, please see the FAQ at
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>Please resolve these comments along with any other Last Call comments
>you may receive.
>
>Document: draft-ietf-nfsv4-federated-fs-admin-11
>Reviewer: Richard Barnes
>Review Date: Jun-19-2012
>IETF LC End Date: Not known
>IESG Telechat date: Jun-28-2012
>
>Summary: Almost ready, couple of issues
>
>MAJOR:=20
>
>4. / 7.
>This protocol allows for the provisioning of security information as part
>of the FedFsNsdbParams, in the form of a certificate to be used in
>verifying a TLS server certificate.  There are two notable issues with
>how the document does this now:
>1. Section 4 does not adequately specify how the certificate in the
>FedFsNsdbParams should be used in the verification process.  Is it to be
>used as a trust anchor, so that any subordinate certificate is considered
>valid?  Or perhaps it is to be matched against the end-entity
>certificate.  In either case, it seems like it would be sufficient to
>provision a certificate fingerprint (or even a public key fingerprint)
>instead of the whole certificate.
>2. In the security considerations, the document should discuss the
>implications of provisioning trust information in this way (depending on
>how it is used), and any requirements for security mechanisms to be used
>in these cases.
>


I'm going to have to work with the rest of the group to answer this one.


>
>MINOR:
>
>2.=20
>It's not clear what the difference is between utf8string_cs and
>utf8string_cis.  Should you mention at some point that these MUST be
>UTF-8, even though the XDR won't enforce that?  (Say, at the beginning of
>Section 4?)


Argh, we did away with utf8string_cs and utf8string_cis in 3530bis.


utf8string_cis should be utf8val_REQUIRED4
utf8string_cs should be ascii_REQUIRED4

In 3530bis, these are defined as:

typedef :opaque  :utf8string<>:UTF-8 encoding for strings.
typedef :utf8string:utf8_expected:String expected to be UTF-8 but no
validation
typedef :utf8string:utf8val_RECOMMENDED4:String SHOULD be sent UTF-8 and
SHOULD be validated
typedef :utf8string:utf8val_REQUIRED4:String MUST be sent UTF-8 and MUST
be validated
typedef :utf8string:ascii_REQUIRED4:String MUST be sent as ASCII and thus
is automatically UTF-8


I'll change the types and there is already some text pointing the reader
to Chapter 12 of 3530bis.


>
>3.
>It's not clear to me how FEDFS_ERR_PERM differs from FEDFS_ERR_ACCESS.  I
>don't see it called out for use anywhere in the procedure calls.  Perhaps
>this is a legacy of prior versions that should be deleted?


This is inherited from the base NFSv4.0 documentation and also NFSv3. It
is also the difference between EPERM and EACCES. (see
http://www.wlug.org.nz/EACCES)


13.1.6.1.  NFS4ERR_ACCESS (Error Code 13)

   Indicates permission denied.  The caller does not have the correct
   permission to perform the requested operation.  Contrast this with
   NFS4ERR_PERM (Section 13.1.6.2), which restricts itself to owner or
   privileged user permission failures.

13.1.6.2.  NFS4ERR_PERM (Error Code 1)

   Indicates requester is not the owner.  The operation was not allowed
   because the caller is neither a privileged user (root) nor the owner
   of the target of the operation.






>
>
>EDITORIAL:=20
>
>3.=20
>The definition of FEDFS_ERR_LOOP isn't actually related to looping.  It
>seems like this should either detect a loop (e.g., via a repeated name),
>or be renamed something like FEDFS_ERR_TOOMANYREFERS.


This has its roots in a Linux error code:

>> As I recall this error is supposed to be returned when fedfsd is passed
>>a pathname that contains too many symlinks.  The equivalent errno on
>>Linux is called ELOOP.

We are striving to maintain parity.





>
>4. "The port is the NSDB transport port for the LDAP interface"
>Suggest rewording to clarify that this is an LDAP/TCP port (I initially
>wondered if other transports could be used), e.g.:
>"The port value in the FedFsNsdbName indicates the LDAP port on the NSDB"


Thanks, we've been struggling with this issue, I'll take your suggested
change here.

>
>_______________________________________________
>nfsv4 mailing list
>nfsv4@ietf.org
>https://www.ietf.org/mailman/listinfo/nfsv4


From wassim.haddad@ericsson.com  Fri Jun 22 10:46:56 2012
Return-Path: <wassim.haddad@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2E5E21F852E for <gen-art@ietfa.amsl.com>; Fri, 22 Jun 2012 10:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ScSfmchX4Ux5 for <gen-art@ietfa.amsl.com>; Fri, 22 Jun 2012 10:46:56 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 595D221F8493 for <gen-art@ietf.org>; Fri, 22 Jun 2012 10:46:56 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q5MHkst3027171; Fri, 22 Jun 2012 12:46:55 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.57]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Fri, 22 Jun 2012 13:46:50 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
To: Ben Niven-Jenkins <ben@velocix.com>
Date: Fri, 22 Jun 2012 13:46:58 -0400
Thread-Topic: [Gen-art] Gen-ART review of draft-ietf-cdni-problem-statement-06
Thread-Index: Ac1QnwBwipD5G7tRTX29EqCExvjTWQ==
Message-ID: <88D96067-8106-4B80-8D13-E840571BC977@ericsson.com>
References: <CC0A6B90.37B56%ben@velocix.com>
In-Reply-To: <CC0A6B90.37B56%ben@velocix.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; micalg=sha1; boundary="Apple-Mail-EA81C845-904F-4F35-A79B-29A580BEDA63"; protocol="application/pkcs7-signature"
MIME-Version: 1.0
Cc: "draft-ietf-cdni-problem-statement.all@tools.ietf.org" <draft-ietf-cdni-problem-statement.all@tools.ietf.org>, Gen-art <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-cdni-problem-statement-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 17:46:57 -0000

--Apple-Mail-EA81C845-904F-4F35-A79B-29A580BEDA63
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks a lot!


Wassim H.

Sent from my iPhone

On Jun 22, 2012, at 10:37, "Ben Niven-Jenkins" <ben@velocix.com> wrote:

> Wassim,
> 
> Thanks for the review, please see below:
> 
> On 19/06/2012 19:44, "Wassim Haddad" <wassim.haddad@ericsson.com> wrote:
> 
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq.
>> 
>> Please resolve these comments along with any other comments you may
>> receive.
>> 
>> Document:  draft-ietf-cdni-problem-statement-06
>> Reviewer: Wassim Haddad
>> Review Date: 2012-06-19
>> IETF LC End Date: 2012-06-06
>> IESG Telechat date: 2012-06-21
>> 
>> Summary: This draft is ready for publication as informational standard
>> but one (helpful) addition is suggested.
>> 
>> Major issues: None
>> 
>> Minor issues: 
>> 
>> - Sectiom 1.1: suggest defining "Quality of Experience" (mentioned 4
>> times in the document)
> 
> In my working copy, I have added the following to the terminology section:
> 
>   Quality of Experience (QoE): As defined in Section 2.4 of [RFC6390]
> 
> (Thanks Benoit for the pointer)
> 
> Ben

--Apple-Mail-EA81C845-904F-4F35-A79B-29A580BEDA63
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIENDCCBDAw
ggMYoAMCAQICEQDYVPUywOyjtwh/x6nlhfS/MA0GCSqGSIb3DQEBBQUAMDkxETAPBgNVBAoMCEVy
aWNzc29uMSQwIgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDEwHhcNMDkxMDI5MTU1
ODU3WhcNMTIxMDI5MTU1ODU0WjBoMREwDwYDVQQKDAhFcmljc3NvbjEWMBQGA1UEAwwNV2Fzc2lt
IEhhZGRhZDEQMA4GA1UEBRMHZXdhc2hhZDEpMCcGCSqGSIb3DQEJARYad2Fzc2ltLmhhZGRhZEBl
cmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJnf3T/nroDokwgzv1ob54nr
EQ2qce7b8P0j9dhnGFPhfROZzOb8Uuo1MPaSpDLVObZgSisoJ5JU0euu6pVcofmLQPZzdWzooCBa
s3Y2tuRtkvFgcZoDKJoo7sorV6yyeRwA+QZpvyS1A7cpsqxjB7jevoXrIFhjs79safz+/Ou/AgMB
AAGjggGGMIIBgjCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0LnRlbGlh
LmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVzdC50ZWxp
YS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nzb24/Y2Vy
dGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAlBgNVHREEHjAcgRp3YXNzaW0uaGFk
ZGFkQGVyaWNzc29uLmNvbTBGBgNVHSAEPzA9MDsGBiqFcGsBATAxMC8GCCsGAQUFBwIBFiNodHRw
Oi8vd3d3LmVyaWNzc29uLmNvbS9sZWdhbC5zaHRtbDAdBgNVHQ4EFgQUiY5imSIHErhSp2V+9kdO
JARmWScwHwYDVR0jBBgwFoAUlifDuN6lX11EPjlS5UWxdl9jMJswDgYDVR0PAQH/BAQDAgWgMA0G
CSqGSIb3DQEBBQUAA4IBAQBIXqbs40JZUFTT/PWl6A0c3S85eU48TVXuwP2wkVhrBUz+45qAo0Yo
FV3gDreoDoFGRFlHS5UiID7OUUyY4JJ0BCoqTPU6DGFjruZVNWk6gaL0WiFgqp0ro4CtysRmV1r1
no3JAaVcvZ4Hf7kOx2SxvresNlGlcDqk7eEABucmHNeQdDLCr61Ssrv3/Z6nMlI1IVLydpvqwgB8
7a0tqeejE3+QpTF0mLZWp1YYKz8hYSMX7MyJug372fN3MgWl7KiV0TOPMSn+yJZemwGl3xVmoT7j
N/1/J6ApI5bLJrLNUT2UYjnBAyw3RIrzYoMuHJZu9L0f1gBPC8tLC0FsDEjAMYICFTCCAhECAQEw
TjA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBD
QTAxAhEA2FT1MsDso7cIf8ep5YX0vzAJBgUrDgMCGgUAoIIBHTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjA2MjIxNzQ2NThaMCMGCSqGSIb3DQEJBDEWBBT/ycs7
S2VCN1+o9F7f/jWyp2YlWjBdBgkrBgEEAYI3EAQxUDBOMDkxETAPBgNVBAoMCEVyaWNzc29uMSQw
IgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEQDYVPUywOyjtwh/x6nlhfS/MF8G
CyqGSIb3DQEJEAILMVCgTjA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhEA2FT1MsDso7cIf8ep5YX0vzANBgkqhkiG9w0BAQEFAASBgDL6
iifceZMAQMX8TQt7nsLZtMkQaSz0j6/4oFLIJvju6EPwPEh2RxCQdkWiJLQF+du+fgBdeud4CL30
st504HAfza3zyICU6r5GANJUlQJ4/zQRXnEnpCDi6aaOpcvf5E0WQbCAOmYqnxEEAT/t29haGhwZ
3+VJC1z+meNPfxeiAAAAAAAA
--Apple-Mail-EA81C845-904F-4F35-A79B-29A580BEDA63--

From ben@velocix.com  Fri Jun 22 10:37:40 2012
Return-Path: <ben@velocix.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D491421F870F for <gen-art@ietfa.amsl.com>; Fri, 22 Jun 2012 10:37:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8r84PJB-eIKP for <gen-art@ietfa.amsl.com>; Fri, 22 Jun 2012 10:37:40 -0700 (PDT)
Received: from owa.velocix.com (mail-out2.velocix.com [81.134.152.13]) by ietfa.amsl.com (Postfix) with ESMTP id 5871021F8604 for <gen-art@ietf.org>; Fri, 22 Jun 2012 10:37:26 -0700 (PDT)
Received: from exc02cam.corp.velocix.com (172.18.4.42) by exc01cam.corp.velocix.com (172.18.4.41) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 22 Jun 2012 18:37:20 +0100
Received: from EXB03CAM.corp.velocix.com ([169.254.4.73]) by exc02cam.corp.velocix.com ([172.18.4.77]) with mapi id 14.02.0247.003; Fri, 22 Jun 2012 18:37:25 +0100
From: Ben Niven-Jenkins <ben@velocix.com>
To: Wassim Haddad <wassim.haddad@ericsson.com>, Gen-art <gen-art@ietf.org>
Thread-Topic: [Gen-art] Gen-ART review of draft-ietf-cdni-problem-statement-06
Thread-Index: AQHNTkudDhmUrEs/LEOqjNmykUXSKpcGnrmA
Date: Fri, 22 Jun 2012 17:37:24 +0000
Message-ID: <CC0A6B90.37B56%ben@velocix.com>
In-Reply-To: <A4CC8CCA-8B2A-4E82-BF83-4B1A718329A5@ericsson.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [81.134.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CB2AC16CE377114890B77A5BF98CC56A@velocix.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 22 Jun 2012 11:15:27 -0700
Cc: "draft-ietf-cdni-problem-statement.all@tools.ietf.org" <draft-ietf-cdni-problem-statement.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-cdni-problem-statement-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 17:37:41 -0000

Wassim,

Thanks for the review, please see below:

On 19/06/2012 19:44, "Wassim Haddad" <wassim.haddad@ericsson.com> wrote:

>I am the assigned Gen-ART reviewer for this draft. For background on
>Gen-ART, please see the FAQ at
>http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq.
>
>Please resolve these comments along with any other comments you may
>receive.
>
>Document:  draft-ietf-cdni-problem-statement-06
>Reviewer: Wassim Haddad
>Review Date: 2012-06-19
>IETF LC End Date: 2012-06-06
>IESG Telechat date: 2012-06-21
>
>Summary: This draft is ready for publication as informational standard
>but one (helpful) addition is suggested.
>
>Major issues: None
>
>Minor issues:=20
>
>- Sectiom 1.1: suggest defining "Quality of Experience" (mentioned 4
>times in the document)

In my working copy, I have added the following to the terminology section:

   Quality of Experience (QoE): As defined in Section 2.4 of [RFC6390]

(Thanks Benoit for the pointer)

Ben




From mahoney@nostrum.com  Fri Jun 22 13:55:51 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 129CA11E80CB for <gen-art@ietfa.amsl.com>; Fri, 22 Jun 2012 13:55:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3R3PmAN8Bwzx for <gen-art@ietfa.amsl.com>; Fri, 22 Jun 2012 13:55:50 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8939811E807F for <gen-art@ietf.org>; Fri, 22 Jun 2012 13:55:50 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-51-177.dllstx.fios.verizon.net [173.71.51.177]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q5MKtnPw007325 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 22 Jun 2012 15:55:50 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FE4DBD5.5090102@nostrum.com>
Date: Fri, 22 Jun 2012 15:55:49 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.51.177 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-06-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 20:55:51 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Roni Even         2012-07-13    draft-hoffman-tao-as-web-page-02

Suresh Krishnan   2012-07-04    draft-ietf-cdni-use-cases-08

Vijay Gurbani     2012-07-06    draft-ietf-ospf-prefix-hiding-04


The assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

And I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From Francis.Dupont@fdupont.fr  Sun Jun 24 10:31:08 2012
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC4021F85D6 for <gen-art@ietfa.amsl.com>; Sun, 24 Jun 2012 10:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qDdpZF2my3Pt for <gen-art@ietfa.amsl.com>; Sun, 24 Jun 2012 10:31:07 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 7534221F85D4 for <gen-art@ietf.org>; Sun, 24 Jun 2012 10:31:07 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id q5OHV6if045766; Sun, 24 Jun 2012 19:31:06 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201206241731.q5OHV6if045766@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Sun, 24 Jun 2012 19:31:06 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-v6ops-ra-guard-implementation.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-v6ops-ra-guard-implementation-04.txt (full)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jun 2012 17:31:08 -0000

(this message was stuck by the problems of the art.tools.ietf.org box
but without too much trouble as the summary went through in time)

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-v6ops-ra-guard-implementation-04.txt
Reviewer: Francis Dupont
Review Date: 20120606
IETF LC End Date: 20120612
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - ToC Page 2: RA Guard -> RA-Guard

 - ToC page 2: Acknowledgements -> Acknowledgments

 - 1 page 3: a funny fact is DHCPv4 (which IMHO is not really over IP)
 is not sensible to this attack, at the opposite of DHCPv6...

 - 2 page 4, title: RA Guard -> RA-Guard

 - 3 page 9, point 6: in fact IPsec has its own issue with fragmentation...
  Nevertheless I agree with the proposed text.

 - 6 page 13: i.e. -> i.e., and e.g. -> e.g.,

 - 7 page 14: Acknowledgements -> Acknowledgments

 - B page 18: organisations -> organizations

Thanks

Francis.Dupont@fdupont.fr

From vkg@bell-labs.com  Mon Jun 25 06:49:13 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5447621F85FC for <gen-art@ietfa.amsl.com>; Mon, 25 Jun 2012 06:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rSV5M172WRD5 for <gen-art@ietfa.amsl.com>; Mon, 25 Jun 2012 06:49:09 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id D732821F85F2 for <gen-art@ietf.org>; Mon, 25 Jun 2012 06:49:08 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q5PDn0VY008599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 25 Jun 2012 08:49:05 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q5PDmxmx003612 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Jun 2012 08:48:59 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q5PDmv2F016040; Mon, 25 Jun 2012 08:48:59 -0500 (CDT)
Message-ID: <4FE86DA5.90006@bell-labs.com>
Date: Mon, 25 Jun 2012 08:54:45 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: draft-ietf-ospf-prefix-hiding@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: General Area Review Team <gen-art@ietf.org>, Stewart Bryant <stbryant@cisco.com>, acee.lindem@ericsson.com, akr@cisco.com
Subject: [Gen-art] Gen-ART review of draft-ietf-ospf-prefix-hiding-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jun 2012 13:49:13 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-ospf-prefix-hiding-04.
Reviewer: Vijay K. Gurbani
Review Date: Jun-25-2012
IETF LC End Date: July-6-2012
IESG Telechat date: Not known

Summary: This draft is ready as a Proposed Standard.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From mustapha.aissaoui@alcatel-lucent.com  Wed Jun 27 13:22:05 2012
Return-Path: <mustapha.aissaoui@alcatel-lucent.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 273B221F86A8 for <gen-art@ietfa.amsl.com>; Wed, 27 Jun 2012 13:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lCY1nSqFfVCr for <gen-art@ietfa.amsl.com>; Wed, 27 Jun 2012 13:22:04 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id EB89121F8665 for <gen-art@ietf.org>; Wed, 27 Jun 2012 13:22:03 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id q5RKLutW000436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 27 Jun 2012 15:21:56 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q5RKLuxB020745 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 27 Jun 2012 15:21:56 -0500
Received: from USNAVSXCHMBSC2.ndc.alcatel-lucent.com ([135.3.39.145]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Wed, 27 Jun 2012 15:21:56 -0500
From: "Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Date: Wed, 27 Jun 2012 15:21:55 -0500
Thread-Topic: Gen-ART review of draft-ietf-pwe3-redundancy-bit-07.txt
Thread-Index: Ac04tNVtXAkzBuQLRKy+X09n0lIVbwby0yMA
Message-ID: <5DF53972F7E9134782DCE51624466FE50BD74A84F3@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
References: <4FBC9029.1000305@ericsson.com>
In-Reply-To: <4FBC9029.1000305@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: "draft-ietf-pwe3-redundancy-bit.authors@tools.ietf.org" <draft-ietf-pwe3-redundancy-bit.authors@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, Andy Malis <amalis@gmail.com>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pwe3-redundancy-bit-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2012 20:22:05 -0000

Hi Miguel,
Thank you again for the second review of this draft. All your comments are =
accepted and will be included in the next version.

Regards,
Mustapha.=20

-----Original Message-----
From: Miguel A. Garcia [mailto:Miguel.A.Garcia@ericsson.com]=20
Sent: Wednesday, May 23, 2012 3:22 AM
To: draft-ietf-pwe3-redundancy-bit.authors@tools.ietf.org; Andy Malis; pwe3=
-chairs@tools.ietf.org; Stewart Bryant
Cc: General Area Review Team
Subject: Gen-ART review of draft-ietf-pwe3-redundancy-bit-07.txt

I have been selected as the General Area Review Team (Gen-ART) reviewer for=
 this draft. For background on Gen-ART, please see the FAQ at <http://wiki.=
tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other comments you may receive=
.

Document: draft-ietf-pwe3-redundancy-bit-07.txt
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com> Review Date: 23-May-=
2012 IESG Telechat date: 24-May-2012

Summary: The document is almost ready for publication as a standards track =
RFC, but has some minor issues that should be fixed.

I reviewed version -06 of this document. At that time I had a few comments.=
 Most of them have been successfully addressed. In this review I am address=
ing the leftovers and new issues.

Major issues: none

Minor issues:

- In my previous review, I highlighted that many lowercase 2119-reserved wo=
rds (like "must", "may", etc.) should actually be written in uppercase to b=
e really normative. Rather than analyzing each case on a one by one basis, =
the authors have systematically written in uppercase all 2119-reserved word=
s. The problem is that now some uppercase 2119-reserved words don't make se=
nse, and should be reverted to lowercase. Allow me some examples:

   * Sections 1 (Introduction) and 2 (Motivation and Scope). Since these ar=
e descriptive sections in nature, normative text should not be written here=
. If there is a need to write normative text, it should be written later in=
 any of the procedures sections.

   * Section 5.2, 1st paragraph, the "MUST" does not really have a normativ=
e intention as it is currently written:

    One endpoint node of the redundant set of PWs is designated the
    Master and is responsible for selecting which PW both endpoints MUST
    use to forward user traffic.

   * Section 15.2. I understand that this section describes scenarios or ex=
amples of architectures. Therefore, it does not make sense to write normati=
ve statements in here. If you need one, it should be written in any of the =
procedures sections. There is a "SHOULD" on the 4th paragraph of Section 15=
.2. The same applies to the last paragraph in Section 15.4 and last paragra=
ph in Section 15.6.


Nits/editorial comments:

- The abstract has added a new sentence at the end. Unfortunately there is =
a new reference "in RFC 5542 [9]". Abstracts shouldn't include references. =
Just write "... in RFC 5542".

- There is an extra dot at the end of the second paragraph in Section 6.1. =
The same happen in the last paragraph of Section 15.3. And yet the same in =
the third paragraph of Section 15.4, and the second paragraph in 15.6.

- Section 15.4, second paragraph, the term "Figure" is repeated.

- Section 15.5, the last paragraph starts with some strange indentation.

/Miguel
--
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain

From ron.even.tlv@gmail.com  Thu Jun 28 07:28:52 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0A1221F84F8; Thu, 28 Jun 2012 07:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oMgnGTDe4hAf; Thu, 28 Jun 2012 07:28:51 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 405A621F84F6; Thu, 28 Jun 2012 07:28:51 -0700 (PDT)
Received: by bkty8 with SMTP id y8so2230979bkt.31 for <multiple recipients>; Thu, 28 Jun 2012 07:28:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=DA5MEXEu0DpBbcPJiet+yV+uluj4H3or/q+v3N+rorg=; b=sW6OyIQgN3y5A/WX0P/rG6dFtVyIu42jUky6kloUlPky7J/aRN18zUWOL4JXlUeBg/ k7uditZEPF8vrHDR1yj0VNJ3pETDWCWdQfbUDGP8EcmYObipVvSBKKeuRaFsWeK+A3FF Srs492IVpAZqXkOMwrgoZ2UlMI2mJgy3Ixjf/zcXvdoPFP8OlgBTJrD0uxe9mkk5gfF4 2GIp2RkAIw+E28wYeVR0piqbMG/bkCWdRa7nYwszTe6g3p98Mfar0bVMPnj2SZvI9utz bTelcWz8KiqZ5X4pYhdBFg5CEmXPZMUklsYUwkKDvFiKmnCi2tGUPi9h7NCxn0zGpVC0 tg3g==
Received: by 10.204.132.80 with SMTP id a16mr1384739bkt.82.1340893730281; Thu, 28 Jun 2012 07:28:50 -0700 (PDT)
Received: from RoniE ([109.64.198.75]) by mx.google.com with ESMTPS id iq16sm59240722bkc.6.2012.06.28.07.28.48 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Jun 2012 07:28:49 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-hoffman-tao-as-web-page.all@tools.ietf.org>, <ietf@ietf.org>, <gen-art@ietf.org>
Date: Thu, 28 Jun 2012 17:28:29 +0200
Message-ID: <00b701cd5542$acb50780$061f1680$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B8_01CD5553.703EC1E0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1VQqs+3AMkTzdBSOCThHrnWYVdSA==
Content-Language: en-us
Subject: [Gen-art] GenART LC review of draft-hoffman-tao-as-web-page-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 14:28:53 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00B8_01CD5553.703EC1E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-hoffman-tao-as-web-page-02

Reviewer: Roni Even

Review Date:2012-6-28

IETF LC End Date: 2012-7-13

IESG Telechat date:

 

Summary: This draft is ready for publication as an Informational RFC.

 

Major issues:

 

Minor issues:

In the section 2 the second sentence is "The initial content for the Tao web
page will come from the last Internet-Draft that was meant to replace RFC
4677.". I was wondering if this information is important to this document
when published. If it is maybe rephrase it to "The initial content for the
Tao web page is based on the last Internet-Draft that was meant to replace
RFC 4677". 

I also suggest that maybe it will be good to have an informative reference
to it.

 

 

Nits/editorial comments:

 

1.       Section 1 second paragraph "led" instead of "lead" 

2.       Section 2 third paragraph "proposed" instead of "propsed"

 


------=_NextPart_000_00B8_01CD5553.703EC1E0
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-microsoft-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=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1239562432;
	mso-list-type:hybrid;
	mso-list-template-ids:1795562620 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
draft-hoffman-tao-as-web-page-02<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;6&#8211;28<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;7&#8211;13<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In the =
section 2 the second sentence is &#8220;The initial content for the Tao =
web page will come from the last Internet-Draft that was meant to =
replace RFC 4677.&#8221;. I was wondering if this information is =
important to this document when published. If it is maybe rephrase it to =
&#8220;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The =
initial content for the Tao web page is based on the last Internet-Draft =
that was meant to replace RFC 4677&#8221;. <o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I also =
suggest that maybe it will be good to have an informative reference to =
it.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section 1 =
second paragraph &#8220;led&#8221; instead of &#8220;lead&#8221; =
<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section 2 =
third paragraph &#8220;proposed&#8221; instead of =
&#8220;propsed&#8221;<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00B8_01CD5553.703EC1E0--


From david.black@emc.com  Thu Jun 28 13:51:44 2012
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCC5421F8526; Thu, 28 Jun 2012 13:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vg1LkAWUb-E4; Thu, 28 Jun 2012 13:51:42 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 47F6A21F8593; Thu, 28 Jun 2012 13:51:41 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5SKpcOB030462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jun 2012 16:51:39 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 28 Jun 2012 16:51:16 -0400
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5SKpEHi013407; Thu, 28 Jun 2012 16:51:14 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub26.corp.emc.com ([10.254.110.182]) with mapi; Thu, 28 Jun 2012 16:51:14 -0400
From: <david.black@emc.com>
To: <alan.b.johnston@gmail.com>, <mohsen.soroush@sylantro.com>, <vvenkatar@gmail.com>, <gen-art@ietf.org>
Date: Thu, 28 Jun 2012 16:51:13 -0400
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Index: Ac1Vb8Dn5IHpqMlJQDmiZm9plrtFJQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: shida@ntt-at.com, bliss@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-bliss-shared-appearances-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 20:51:45 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-bliss-shared-appearances-11
Reviewer: David L. Black
Review Date: June 28, 2012
IETF LC End Date: June 28, 2012
IESG Telechat date: (if known)

Summary:

This draft is on the right track but has open issues, described in the revi=
ew.

This draft describes support for shared appearances in support of multi-lin=
e
and shared-line telephone often found in businesses.  All of the open issue=
s
are minor.  The draft is well-written and reasonably clear for the most par=
t,
although significant SIP expertise is required to completely understand it.

Major issues:  None.

Minor issues:

4.1 - REQ-16:

   in this case, seizing the line is the same thing as dialing.

That seems wrong - I would have thought it was a "prerequisite" as
opposed to "the same thing" because seizing the line is immediately
followed by a dialing request.

5.3.

   A user may select an appearance number but then abandon placing a
   call (go back on hook).  In this case, the UA MUST free up the
   appearance number by removing the event state with a PUBLISH as
   described in [RFC3903].

What happens when that can't be done due to UA or network failure?

5.4.

   A 400 response is returned if the chosen appearance number is invalid,

Is that always a 400 (Bad Request) or is any 4xx response allowed?  If
it's always 400, add the words "Bad Request" after "400".

   If the Appearance Agent policy does not allow this, a 400 response
   is returned.

Same question.  In addition, is 403 Forbidden allowed here?

   If an INVITE is sent by a member of the group to the shared AOR (i.e.
   they call their own AOR), the Appearance Agent MUST assign two
   appearance numbers.  The first appearance number will be the one
   selected or assigned to the outgoing INVITE.  The second appearance
   number will be another one assigned by the Appearance Agent for the
   INVITE as it is forked back to the members of the group.

How does that interact with the single appearance UAs in 8.1.1 that won't
understand the second appearance number?  A warning that such a UA can't
pick up its call to its own AOR would suffice, either here or in 8.1.1.

9.1=20

   A UA that has no knowledge of appearances must will only have
   appearance numbers for outgoing calls if assigned by the Appearance
   Agent.  If the non-shared appearance UA does not support Join or
   Replaces, all dialogs could be marked "exclusive" to indicate that
   these options are not available.

Should that "could be marked" be changed to "SHOULD be marked" ?
Also, analogous questions for "could" in 9.2 and "can" in 9.3.

All three of these affect interoperability.

12. Security Considerations

In general, this section is weak on rationale - the second, third and
fourth paragraphs should all explain more about the purpose of and/or
rationale for their security requirements (e.g., what does the security
mechanism protect against and when/why might that protection be desired
and/or required?).

   NOTIFY or PUBLISH message bodies that provide the dialog state
   information and the dialog identifiers MAY be encrypted end-to-end
   using the standard mechanisms.

What are "the standard mechanisms"?  List them, and provide references,
please.

Please ensure that the section 6 XML and Section 7 ABNF are
syntax-checked with actual tools.

Nits/editorial comments:

p.10:

   The next section discusses the operations used to implement parts of
   the shared appearance feature.

"The following list describes the operations ..." would be better.

5.3.1.

   A UA wanting to place a call but not have an appearance number
   assigned publishes before sending the INVITE without an 'appearance'
   element but with the 'shared' event package parameter present.

I think I understand what was intended here, but this would be clearer
if "publishes" was replaced with language about sending a PUBLISH.
It's also not completely clear whether "without" applies to the
INVITE or the PUBLISH, so this sentence probably needs to be reworded.

5.4. - Expand B2BUA acronym on first use.

idnits 2.12.13 ran clean.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From mahoney@nostrum.com  Thu Jun 28 15:46:07 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FFBB11E80F3 for <gen-art@ietfa.amsl.com>; Thu, 28 Jun 2012 15:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uw9zYLSTiRgV for <gen-art@ietfa.amsl.com>; Thu, 28 Jun 2012 15:46:06 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id AD78D11E80D7 for <gen-art@ietf.org>; Thu, 28 Jun 2012 15:46:06 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-51-177.dllstx.fios.verizon.net [173.71.51.177]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q5SMk1iC091554 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 28 Jun 2012 17:46:06 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FECDEA9.7020506@nostrum.com>
Date: Thu, 28 Jun 2012 17:46:01 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.51.177 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-06-28
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 22:46:07 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Alexey Melnikov   2012-07-10    draft-ietf-behave-lsn-requirements-07

Ben Campbell      2012-07-11    draft-ietf-oauth-urn-sub-ns-05

Brian Carpenter   2012-07-11    draft-ietf-6lowpan-btle-08

Francis Dupont    2012-07-11    draft-ietf-dnsext-dnssec-algo-imp-status-03

Joel Halpern      2012-07-11    draft-ietf-dnsext-dnssec-registry-update-03

Meral Shirazipour 2012-07-11    draft-ietf-v6ops-6204bis-09

Miguel Garcia     2012-07-11    draft-ietf-oauth-v2-threatmodel-06

Peter McCann      2012-07-12    draft-ietf-appsawg-received-state-04 *

Wassim Haddad     2012-07-10    draft-ietf-abfab-gss-eap-08


* On the 2012-07-19 telechat


The assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

And I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> .

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mahoney@nostrum.com  Thu Jun 28 15:49:42 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D248711E80FD for <gen-art@ietfa.amsl.com>; Thu, 28 Jun 2012 15:49:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FGWbnezAtwUL for <gen-art@ietfa.amsl.com>; Thu, 28 Jun 2012 15:49:42 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id E850211E80D7 for <gen-art@ietf.org>; Thu, 28 Jun 2012 15:49:41 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-51-177.dllstx.fios.verizon.net [173.71.51.177]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q5SMnf1j091772 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 28 Jun 2012 17:49:41 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FECDF85.5010903@nostrum.com>
Date: Thu, 28 Jun 2012 17:49:41 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.51.177 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-07-05 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 22:49:43 -0000

Hi all,

The following reviewers have assignments:

Reviewer                 LC end      Draft

Kathleen Moriarty      TR2012-06-18 draft-ietf-6man-lineid-05 **

Meral Shirazipour      TR2012-06-20 draft-ietf-trill-clear-correct-04 *

Vijay Gurbani          TR2012-06-14 draft-ietf-xrblock-rtcp-xr-meas-identity-07 *

Wassim Haddad          TR2012-06-06 draft-ietf-cdni-problem-statement-08 *

Wassim Haddad          TR2012-06-14 draft-ietf-intarea-ipv4-id-update-05

* Earlier draft reviewed
** Already reviewed


The assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

And I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

For your convenience, the review boilerplate template is included below.

Note that reviews should ideally be posted to the gen-art mailing list
by COB on Tuesday:
http://wiki.tools.ietf.org/area/gen/trac/wiki/

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From jmh@joelhalpern.com  Thu Jun 28 16:41:14 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5FA011E80E3 for <gen-art@ietfa.amsl.com>; Thu, 28 Jun 2012 16:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.335
X-Spam-Level: 
X-Spam-Status: No, score=-102.335 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LblLY5edVgmv for <gen-art@ietfa.amsl.com>; Thu, 28 Jun 2012 16:41:14 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 683DE21F8602 for <gen-art@ietf.org>; Thu, 28 Jun 2012 16:41:14 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 3B5D5557F03 for <gen-art@ietf.org>; Thu, 28 Jun 2012 16:41:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 97F021211B3; Thu, 28 Jun 2012 16:41:12 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.105] (pool-71-161-52-145.clppva.btas.verizon.net [71.161.52.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 16E061211B2; Thu, 28 Jun 2012 16:41:11 -0700 (PDT)
Message-ID: <4FECEB94.1000309@joelhalpern.com>
Date: Thu, 28 Jun 2012 19:41:08 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4FECDEA9.7020506@nostrum.com>
In-Reply-To: <4FECDEA9.7020506@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]   Review: draft-ietf-dnsext-dnssec-registry-update-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 23:41:14 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> .

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-dnsext-dnssec-registry-update-03
     DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry Updates
Reviewer: Joel Halpern
Review Date: 28-June-2012
IETF LC End Date: 11-July-2012
IESG Telechat date: N/A

Summary: This document is ready for publication as a Proposed Standard

From alan.b.johnston@gmail.com  Thu Jun 28 18:05:29 2012
Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0575F11E80FA; Thu, 28 Jun 2012 18:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kKLshi9zm47k; Thu, 28 Jun 2012 18:05:28 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id B5D1911E80A2; Thu, 28 Jun 2012 18:05:27 -0700 (PDT)
Received: by yenq13 with SMTP id q13so2595199yen.31 for <multiple recipients>; Thu, 28 Jun 2012 18:05:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=UKpmvQQl3KGBpTU+DKE/cWv4M90OECLV/6XPcxRaL1c=; b=E38N3onfj44+nigxSdK83N5XPWeq7LzXqseQFUvQqRV3GkxRBRTJLJYP4iB464muEB in7FIuOHip+PfogC81slJRE9TY6nNmfiiu2du5W57RsET6aSVyzWqn2ZY1bvA7xcy3EV YzzRn4V3AQQ7MzXeea7/kjK4EY0rvRgGB74qZRcFPBk8XC3XbQyTOrMjBqE4xf+dHMIj 9iMrwBqYUwpMRINa/KyXw7SVynnFzGnsMxWdjQzOKu3C9ykjGkaF9+pH8/PHtSVZ7pd8 xOnD4U80B2ownVoT3l/JLkKMJ2Xh0opHhkrxG6jUPDFnDXey5Q0K5PXUb28HH8MUHpbV Ru3Q==
MIME-Version: 1.0
Received: by 10.42.130.68 with SMTP id u4mr1429708ics.17.1340931925588; Thu, 28 Jun 2012 18:05:25 -0700 (PDT)
Received: by 10.231.228.135 with HTTP; Thu, 28 Jun 2012 18:05:25 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com>
Date: Thu, 28 Jun 2012 20:05:25 -0500
Message-ID: <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: david.black@emc.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mohsen.soroush@sylantro.com, ietf@ietf.org, gen-art@ietf.org, bliss@ietf.org, vvenkatar@gmail.com, shida@ntt-at.com
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bliss-shared-appearances-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 01:05:29 -0000

David,

Thank you for your review of the document. =A0See below for how I
propose to resolve the issues you have raised.  Let me know if you
have any other issues or concerns.

- Alan -

On Thu, Jun 28, 2012 at 3:51 PM, <david.black@emc.com> wrote:
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-bliss-shared-appearances-11
> Reviewer: David L. Black
> Review Date: June 28, 2012
> IETF LC End Date: June 28, 2012
> IESG Telechat date: (if known)
>
> Summary:
>
> This draft is on the right track but has open issues, described in the re=
view.
>
> This draft describes support for shared appearances in support of multi-l=
ine
> and shared-line telephone often found in businesses. =A0All of the open i=
ssues
> are minor. =A0The draft is well-written and reasonably clear for the most=
 part,
> although significant SIP expertise is required to completely understand i=
t.
>
> Major issues: =A0None.
>
> Minor issues:
>
> 4.1 - REQ-16:
>
> =A0 in this case, seizing the line is the same thing as dialing.
>
> That seems wrong - I would have thought it was a "prerequisite" as
> opposed to "the same thing" because seizing the line is immediately
> followed by a dialing request.


This requirement is about sending one request that causes both actions
to occur. =A0In a PSTN ringdown circuit (a very specialized circuit,
used for "hotlines"), the two operations are the same thing. =A0Besides
this statement, is REQ-16 itself not clear? =A0Perhaps I should just
remove this statement if it adds confusion rather than clarity to the
requirement.

>
>
> 5.3.
>
> =A0 A user may select an appearance number but then abandon placing a
> =A0 call (go back on hook). =A0In this case, the UA MUST free up the
> =A0 appearance number by removing the event state with a PUBLISH as
> =A0 described in [RFC3903].
>
> What happens when that can't be done due to UA or network failure?


A little further down in this section says:

"=A0 This publication state is refreshed as described in [RFC3903] during
=A0 =A0the early dialog state or the Appearance Agent may reassign the
=A0 =A0appearance number."

So if the removal publish is lost, it will eventually timeout since it
is not refreshed.  This is standard PUBLISH behavior described in RFC
3903.

>
>
> 5.4.
>
> =A0 A 400 response is returned if the chosen appearance number is invalid=
,
>
> Is that always a 400 (Bad Request) or is any 4xx response allowed? =A0If
> it's always 400, add the words "Bad Request" after "400".

We chose 400 in particular, although any 4xx response would have the
same result.  "Bad Request" is the reason phrase, and the practice of
putting it in () is a convention commonly used in SIP documents.  The
actual reason phrase can be different, customized ("Invalid
Appearance") if desired, or in a different language.

So in this case we are specifying the 400 response.

>
> =A0 If the Appearance Agent policy does not allow this, a 400 response
> =A0 is returned.
>
> Same question. =A0In addition, is 403 Forbidden allowed here?

403 is usually used in SIP to indicate that the request has failed due
to an authorization policy, and the request can be retried with
different credentials.  That doesn't quite fit here.

>
> =A0 If an INVITE is sent by a member of the group to the shared AOR (i.e.
> =A0 they call their own AOR), the Appearance Agent MUST assign two
> =A0 appearance numbers. =A0The first appearance number will be the one
> =A0 selected or assigned to the outgoing INVITE. =A0The second appearance
> =A0 number will be another one assigned by the Appearance Agent for the
> =A0 INVITE as it is forked back to the members of the group.
>
> How does that interact with the single appearance UAs in 8.1.1 that won't
> understand the second appearance number? =A0A warning that such a UA can'=
t
> pick up its call to its own AOR would suffice, either here or in 8.1.1.

I will put text in 8.1.1 that makes this point clear.

>
> 9.1
>
> =A0 A UA that has no knowledge of appearances must will only have
> =A0 appearance numbers for outgoing calls if assigned by the Appearance
> =A0 Agent. =A0If the non-shared appearance UA does not support Join or
> =A0 Replaces, all dialogs could be marked "exclusive" to indicate that
> =A0 these options are not available.
>
> Should that "could be marked" be changed to "SHOULD be marked" ?
> Also, analogous questions for "could" in 9.2 and "can" in 9.3.
>
> All three of these affect interoperability.

I can change this to SHOULD.  Actually, it doesn't affect
interoperability, as "exclusive" is just a hint, for user experience
and interface purposes and to reduce failed requests.  If a Join or
Replace is inadvertently sent, the operation will fail, which is the
same result as not allowing it, although a worse user experience.

>
> 12. Security Considerations
>
> In general, this section is weak on rationale - the second, third and
> fourth paragraphs should all explain more about the purpose of and/or
> rationale for their security requirements (e.g., what does the security
> mechanism protect against and when/why might that protection be desired
> and/or required?).

Right, the mechanisms are to provide privacy and to prevent
hijacking/spoofing.  I can add text to make this clear.

>
> =A0 NOTIFY or PUBLISH message bodies that provide the dialog state
> =A0 information and the dialog identifiers MAY be encrypted end-to-end
> =A0 using the standard mechanisms.
>
> What are "the standard mechanisms"? =A0List them, and provide references,
> please.

That would be S/MIME as described in RFC 3261.  I can add this.

>
> Please ensure that the section 6 XML and Section 7 ABNF are
> syntax-checked with actual tools.

I will double check them.

>
> Nits/editorial comments:
>
> p.10:
>
> =A0 The next section discusses the operations used to implement parts of
> =A0 the shared appearance feature.
>
> "The following list describes the operations ..." would be better.
>
> 5.3.1.
>
> =A0 A UA wanting to place a call but not have an appearance number
> =A0 assigned publishes before sending the INVITE without an 'appearance'
> =A0 element but with the 'shared' event package parameter present.
>
> I think I understand what was intended here, but this would be clearer
> if "publishes" was replaced with language about sending a PUBLISH.
> It's also not completely clear whether "without" applies to the
> INVITE or the PUBLISH, so this sentence probably needs to be reworded.

OK, it is the PUBLISH that doesn't have the parameter - I'll make this clea=
r.

>
> 5.4. - Expand B2BUA acronym on first use.
>
> idnits 2.12.13 ran clean.
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>

From peter@akayla.com  Thu Jun 28 21:55:14 2012
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79FD911E8127 for <gen-art@ietfa.amsl.com>; Thu, 28 Jun 2012 21:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tnVg5cW3JHvU for <gen-art@ietfa.amsl.com>; Thu, 28 Jun 2012 21:55:13 -0700 (PDT)
Received: from p3plsmtpa01-03.prod.phx3.secureserver.net (p3plsmtpa01-03.prod.phx3.secureserver.net [72.167.82.83]) by ietfa.amsl.com (Postfix) with SMTP id EE65211E80F4 for <gen-art@ietf.org>; Thu, 28 Jun 2012 21:55:12 -0700 (PDT)
Received: (qmail 25222 invoked from network); 29 Jun 2012 04:55:12 -0000
Received: from unknown (173.8.184.78) by p3plsmtpa01-03.prod.phx3.secureserver.net (72.167.82.83) with ESMTP; 29 Jun 2012 04:55:08 -0000
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-ippm-twamp-value-added-octets.all@tools.ietf.org>
Date: Thu, 28 Jun 2012 21:55:10 -0700
Message-ID: <029601cd55b3$5d387360$17a95a20$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1Vst90fvRgMPNAQLeI1Kicrd8uCw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-ippm-twamp-value-added-octets-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 04:55:14 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-ippm-twamp-value-added-octets-03
Reviewer: Peter Yee
Review Date: 28-June-2012
IETF LC End Date: 28-June-2012
IESG Telechat date: Pending

Summary: This draft describes an extension to the TWAMP protocol for
handling
packet "trains" which are used to quantify network capacity metrics. 
The document is ready for publication as an informational RFC. 

Major Issues: None

Minor Issues: None

Nits/editorial comments:

Section 2, in the paragraph right after the two bullets: "measurements" ->
"measurement".

Section 3, 5th paragraph, 4th sentence ("The method to measuring the UDP
delivery rate may also
require the packet loss.") left me confused.  Did you mean something like
"The method for
measuring the UDP delivery rate may also require the rate of packet loss."?
Percentage?
Count?

Next paragraph, 2nd sentence: "rate" -> "rates".

Next paragraph, same change.

Section 4, 2nd paragraph, 2nd sentence: "require" -> "requires".

Section 5, 2nd paragraph, 1st sentence: "of first" -> "of the first".

Section 5, 3rd diagram, it's not utterly clear that the Reserved field
includes the two bits
from the last octet on the previous line.  (Yes, I do understand that it's
really hard to
indicate the connection in an ASCII diagram!)  The text implies that must be
the case,
but only owing to the size of the field.

Section 5.1, second to last paragraph, last sentence: "If I bit" -> "If the
I bit".

Section 5.2, 2nd bullet, 2nd sub-bullet, 2nd sentence: "the another" ->
"another".

Section 5.:, "to estimate or calculate" -> "to estimating or calculating"?

Section 5.3, second sentence: "to identify" -> "of identifying".

Section 6, 1st paragraph: "direction" -> "directions".

Section 6, 2nd paragraph, 2nd sentence: "the whole trains" -> "whole
trains".

Section 6, 2nd paragraph, last sentence: "of new field" -> "of a new field".



From david.black@emc.com  Fri Jun 29 06:44:21 2012
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C061721F86FD; Fri, 29 Jun 2012 06:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.398
X-Spam-Level: 
X-Spam-Status: No, score=-102.398 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qImnSoaOKl70; Fri, 29 Jun 2012 06:44:20 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id C57C321F86C2; Fri, 29 Jun 2012 06:44:19 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5TDi7fv003111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2012 09:44:16 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 29 Jun 2012 09:43:57 -0400
Received: from mxhub15.corp.emc.com (mxhub15.corp.emc.com [128.222.70.236]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5TDht9Y008133; Fri, 29 Jun 2012 09:43:56 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub15.corp.emc.com ([128.222.70.236]) with mapi; Fri, 29 Jun 2012 09:43:55 -0400
From: <david.black@emc.com>
To: <alan.b.johnston@gmail.com>
Date: Fri, 29 Jun 2012 09:43:54 -0400
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Index: Ac1Vk1H5siVBJynsTLy55SYGzR+w1QAZ0lZQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208D3A89C@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
In-Reply-To: <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mohsen.soroush@sylantro.com, ietf@ietf.org, gen-art@ietf.org, bliss@ietf.org, vvenkatar@gmail.com, shida@ntt-at.com
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bliss-shared-appearances-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 13:44:22 -0000

Alan,

Thank you for the quick response.  I have a few comments on the proposed
resolutions.  Absence of a comment implies that I agree with the proposed
resolution.

REQ-16 - I understand what's going on here (automatic ringdown), but the
language is just slightly off because there is actually a dialing request.
Here's all of REQ-16:

   REQ-16 The mechanism should support a way for a UA to seize a
   particular appearance number and also send the request at the same
   time.  This is needed when an automatic ringdown feature (a telephone
   configured to immediately dial a phone number when it goes off hook)
   is combined with shared appearances - in this case, seizing the line
   is the same thing as dialing.

The language problem is that the line seizing includes a dialing request,
so "is the same thing as" isn't quite correct when applied solely to
"seizing the line".  As you suggest, the simplest fix would be to just
remove "- in this case ... dialing", or it could be changed to:

	- in this case, seizing the line is part of dialing.

5.3 - Doing nothing is fine.  I'm not a SIP expert, so I assume that
the standard PUBLISH behavior (soft-state times out if not refreshed)
is well-known to anyone who is, and hence no change is needed.

5.4 - please add "(Bad Request)" after each of the two instances of "400".

9.1/2/3 - please change to using "SHOULD" in each of these sections
and explain that the "SHOULD" is motivated by user experience concerns.

Thanks,
--David

> -----Original Message-----
> From: Alan Johnston [mailto:alan.b.johnston@gmail.com]
> Sent: Thursday, June 28, 2012 9:05 PM
> To: Black, David
> Cc: mohsen.soroush@sylantro.com; vvenkatar@gmail.com; gen-art@ietf.org;
> shida@ntt-at.com; bliss@ietf.org; ietf@ietf.org; rjsparks@nostrum.com
> Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
>=20
> David,
>=20
> Thank you for your review of the document. =A0See below for how I
> propose to resolve the issues you have raised.  Let me know if you
> have any other issues or concerns.
>=20
> - Alan -
>=20
> On Thu, Jun 28, 2012 at 3:51 PM, <david.black@emc.com> wrote:
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-bliss-shared-appearances-11
> > Reviewer: David L. Black
> > Review Date: June 28, 2012
> > IETF LC End Date: June 28, 2012
> > IESG Telechat date: (if known)
> >
> > Summary:
> >
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > This draft describes support for shared appearances in support of multi=
-line
> > and shared-line telephone often found in businesses. =A0All of the open=
 issues
> > are minor. =A0The draft is well-written and reasonably clear for the mo=
st
> part,
> > although significant SIP expertise is required to completely understand=
 it.
> >
> > Major issues: =A0None.
> >
> > Minor issues:
> >
> > 4.1 - REQ-16:
> >
> > =A0 in this case, seizing the line is the same thing as dialing.
> >
> > That seems wrong - I would have thought it was a "prerequisite" as
> > opposed to "the same thing" because seizing the line is immediately
> > followed by a dialing request.
>=20
>=20
> This requirement is about sending one request that causes both actions
> to occur. =A0In a PSTN ringdown circuit (a very specialized circuit,
> used for "hotlines"), the two operations are the same thing. =A0Besides
> this statement, is REQ-16 itself not clear? =A0Perhaps I should just
> remove this statement if it adds confusion rather than clarity to the
> requirement.
>=20
> >
> >
> > 5.3.
> >
> > =A0 A user may select an appearance number but then abandon placing a
> > =A0 call (go back on hook). =A0In this case, the UA MUST free up the
> > =A0 appearance number by removing the event state with a PUBLISH as
> > =A0 described in [RFC3903].
> >
> > What happens when that can't be done due to UA or network failure?
>=20
>=20
> A little further down in this section says:
>=20
> "=A0 This publication state is refreshed as described in [RFC3903] during
> =A0 =A0the early dialog state or the Appearance Agent may reassign the
> =A0 =A0appearance number."
>=20
> So if the removal publish is lost, it will eventually timeout since it
> is not refreshed.  This is standard PUBLISH behavior described in RFC
> 3903.
>=20
> >
> >
> > 5.4.
> >
> > =A0 A 400 response is returned if the chosen appearance number is inval=
id,
> >
> > Is that always a 400 (Bad Request) or is any 4xx response allowed? =A0I=
f
> > it's always 400, add the words "Bad Request" after "400".
>=20
> We chose 400 in particular, although any 4xx response would have the
> same result.  "Bad Request" is the reason phrase, and the practice of
> putting it in () is a convention commonly used in SIP documents.  The
> actual reason phrase can be different, customized ("Invalid
> Appearance") if desired, or in a different language.
>=20
> So in this case we are specifying the 400 response.
>=20
> >
> > =A0 If the Appearance Agent policy does not allow this, a 400 response
> > =A0 is returned.
> >
> > Same question. =A0In addition, is 403 Forbidden allowed here?
>=20
> 403 is usually used in SIP to indicate that the request has failed due
> to an authorization policy, and the request can be retried with
> different credentials.  That doesn't quite fit here.
>=20
> >
> > =A0 If an INVITE is sent by a member of the group to the shared AOR (i.=
e.
> > =A0 they call their own AOR), the Appearance Agent MUST assign two
> > =A0 appearance numbers. =A0The first appearance number will be the one
> > =A0 selected or assigned to the outgoing INVITE. =A0The second appearan=
ce
> > =A0 number will be another one assigned by the Appearance Agent for the
> > =A0 INVITE as it is forked back to the members of the group.
> >
> > How does that interact with the single appearance UAs in 8.1.1 that won=
't
> > understand the second appearance number? =A0A warning that such a UA ca=
n't
> > pick up its call to its own AOR would suffice, either here or in 8.1.1.
>=20
> I will put text in 8.1.1 that makes this point clear.
>=20
> >
> > 9.1
> >
> > =A0 A UA that has no knowledge of appearances must will only have
> > =A0 appearance numbers for outgoing calls if assigned by the Appearance
> > =A0 Agent. =A0If the non-shared appearance UA does not support Join or
> > =A0 Replaces, all dialogs could be marked "exclusive" to indicate that
> > =A0 these options are not available.
> >
> > Should that "could be marked" be changed to "SHOULD be marked" ?
> > Also, analogous questions for "could" in 9.2 and "can" in 9.3.
> >
> > All three of these affect interoperability.
>=20
> I can change this to SHOULD.  Actually, it doesn't affect
> interoperability, as "exclusive" is just a hint, for user experience
> and interface purposes and to reduce failed requests.  If a Join or
> Replace is inadvertently sent, the operation will fail, which is the
> same result as not allowing it, although a worse user experience.
>=20
> >
> > 12. Security Considerations
> >
> > In general, this section is weak on rationale - the second, third and
> > fourth paragraphs should all explain more about the purpose of and/or
> > rationale for their security requirements (e.g., what does the security
> > mechanism protect against and when/why might that protection be desired
> > and/or required?).
>=20
> Right, the mechanisms are to provide privacy and to prevent
> hijacking/spoofing.  I can add text to make this clear.
>=20
> >
> > =A0 NOTIFY or PUBLISH message bodies that provide the dialog state
> > =A0 information and the dialog identifiers MAY be encrypted end-to-end
> > =A0 using the standard mechanisms.
> >
> > What are "the standard mechanisms"? =A0List them, and provide reference=
s,
> > please.
>=20
> That would be S/MIME as described in RFC 3261.  I can add this.
>=20
> >
> > Please ensure that the section 6 XML and Section 7 ABNF are
> > syntax-checked with actual tools.
>=20
> I will double check them.
>=20
> >
> > Nits/editorial comments:
> >
> > p.10:
> >
> > =A0 The next section discusses the operations used to implement parts o=
f
> > =A0 the shared appearance feature.
> >
> > "The following list describes the operations ..." would be better.
> >
> > 5.3.1.
> >
> > =A0 A UA wanting to place a call but not have an appearance number
> > =A0 assigned publishes before sending the INVITE without an 'appearance=
'
> > =A0 element but with the 'shared' event package parameter present.
> >
> > I think I understand what was intended here, but this would be clearer
> > if "publishes" was replaced with language about sending a PUBLISH.
> > It's also not completely clear whether "without" applies to the
> > INVITE or the PUBLISH, so this sentence probably needs to be reworded.
>=20
> OK, it is the PUBLISH that doesn't have the parameter - I'll make this cl=
ear.
>=20
> >
> > 5.4. - Expand B2BUA acronym on first use.
> >
> > idnits 2.12.13 ran clean.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >


From alan.b.johnston@gmail.com  Fri Jun 29 07:17:34 2012
Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2B321F86AA; Fri, 29 Jun 2012 07:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x0AvZ4aVtn+E; Fri, 29 Jun 2012 07:17:30 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7065A21F86FD; Fri, 29 Jun 2012 07:17:30 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so3073815ggn.31 for <multiple recipients>; Fri, 29 Jun 2012 07:17:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=dk6H41O8IvIbdLLnP6a+MzMcMIdN1t9ODZg1cOjbDKE=; b=wZDaqviHB5hTcIhpHo1c7UkLyVe1ocVISo/6LELVU5hnz8qzUBKfLpFeC9KuEgAO/n HPMbTfr4InlK0o/9v3kX7RUfPmzVzx4Lpx9YBP34tD7RkOXE9zRdFTgxo5NjT6c9tpBa Gd+TvmbZ/ZgEAUeSTMpHShrmu+HSWETScJFq+yrYIq9+hWqC3ibjgd6UiuZRZ5PPPci1 sR/M6c1DgGxlKWeyDcrz7mbJijNWcCB4+3g9PiOiL3wjY/bqU/WJK//qbRDB+iDXDPSE 1MmtuSZIVmVGrUemaSXg7gwS7qd2vUPBHh8iAnRJ3s4ZTyk/4dfIXQa38JseB0OwL0Ss 5MOQ==
MIME-Version: 1.0
Received: by 10.50.193.196 with SMTP id hq4mr1555160igc.57.1340979449458; Fri, 29 Jun 2012 07:17:29 -0700 (PDT)
Received: by 10.231.228.135 with HTTP; Fri, 29 Jun 2012 07:17:29 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208D3A89C@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com> <8D3D17ACE214DC429325B2B98F3AE71208D3A89C@MX15A.corp.emc.com>
Date: Fri, 29 Jun 2012 09:17:29 -0500
Message-ID: <CAKhHsXEeKYSaM92dhs=mYfyx8ncsCvxW-9A9KGdUbfY3r=EVMw@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: david.black@emc.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mohsen.soroush@sylantro.com, ietf@ietf.org, gen-art@ietf.org, bliss@ietf.org, vvenkatar@gmail.com, shida@ntt-at.com
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bliss-shared-appearances-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 14:17:35 -0000

David,

I will make those changes.  Thanks for the feedback.

- Alan -

On Fri, Jun 29, 2012 at 8:43 AM,  <david.black@emc.com> wrote:
> Alan,
>
> Thank you for the quick response. =A0I have a few comments on the propose=
d
> resolutions. =A0Absence of a comment implies that I agree with the propos=
ed
> resolution.
>
> REQ-16 - I understand what's going on here (automatic ringdown), but the
> language is just slightly off because there is actually a dialing request=
.
> Here's all of REQ-16:
>
> =A0 REQ-16 The mechanism should support a way for a UA to seize a
> =A0 particular appearance number and also send the request at the same
> =A0 time. =A0This is needed when an automatic ringdown feature (a telepho=
ne
> =A0 configured to immediately dial a phone number when it goes off hook)
> =A0 is combined with shared appearances - in this case, seizing the line
> =A0 is the same thing as dialing.
>
> The language problem is that the line seizing includes a dialing request,
> so "is the same thing as" isn't quite correct when applied solely to
> "seizing the line". =A0As you suggest, the simplest fix would be to just
> remove "- in this case ... dialing", or it could be changed to:
>
> =A0 =A0 =A0 =A0- in this case, seizing the line is part of dialing.
>
> 5.3 - Doing nothing is fine. =A0I'm not a SIP expert, so I assume that
> the standard PUBLISH behavior (soft-state times out if not refreshed)
> is well-known to anyone who is, and hence no change is needed.
>
> 5.4 - please add "(Bad Request)" after each of the two instances of "400"=
.
>
> 9.1/2/3 - please change to using "SHOULD" in each of these sections
> and explain that the "SHOULD" is motivated by user experience concerns.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: Alan Johnston [mailto:alan.b.johnston@gmail.com]
>> Sent: Thursday, June 28, 2012 9:05 PM
>> To: Black, David
>> Cc: mohsen.soroush@sylantro.com; vvenkatar@gmail.com; gen-art@ietf.org;
>> shida@ntt-at.com; bliss@ietf.org; ietf@ietf.org; rjsparks@nostrum.com
>> Subject: Re: Gen-ART review of draft-ietf-bliss-shared-appearances-11
>>
>> David,
>>
>> Thank you for your review of the document. =A0See below for how I
>> propose to resolve the issues you have raised. =A0Let me know if you
>> have any other issues or concerns.
>>
>> - Alan -
>>
>> On Thu, Jun 28, 2012 at 3:51 PM, <david.black@emc.com> wrote:
>> >
>> > I am the assigned Gen-ART reviewer for this draft. For background on
>> > Gen-ART, please see the FAQ at
>> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>> >
>> > Please resolve these comments along with any other Last Call comments
>> > you may receive.
>> >
>> > Document: draft-ietf-bliss-shared-appearances-11
>> > Reviewer: David L. Black
>> > Review Date: June 28, 2012
>> > IETF LC End Date: June 28, 2012
>> > IESG Telechat date: (if known)
>> >
>> > Summary:
>> >
>> > This draft is on the right track but has open issues, described in the
>> review.
>> >
>> > This draft describes support for shared appearances in support of mult=
i-line
>> > and shared-line telephone often found in businesses. =A0All of the ope=
n issues
>> > are minor. =A0The draft is well-written and reasonably clear for the m=
ost
>> part,
>> > although significant SIP expertise is required to completely understan=
d it.
>> >
>> > Major issues: =A0None.
>> >
>> > Minor issues:
>> >
>> > 4.1 - REQ-16:
>> >
>> > =A0 in this case, seizing the line is the same thing as dialing.
>> >
>> > That seems wrong - I would have thought it was a "prerequisite" as
>> > opposed to "the same thing" because seizing the line is immediately
>> > followed by a dialing request.
>>
>>
>> This requirement is about sending one request that causes both actions
>> to occur. =A0In a PSTN ringdown circuit (a very specialized circuit,
>> used for "hotlines"), the two operations are the same thing. =A0Besides
>> this statement, is REQ-16 itself not clear? =A0Perhaps I should just
>> remove this statement if it adds confusion rather than clarity to the
>> requirement.
>>
>> >
>> >
>> > 5.3.
>> >
>> > =A0 A user may select an appearance number but then abandon placing a
>> > =A0 call (go back on hook). =A0In this case, the UA MUST free up the
>> > =A0 appearance number by removing the event state with a PUBLISH as
>> > =A0 described in [RFC3903].
>> >
>> > What happens when that can't be done due to UA or network failure?
>>
>>
>> A little further down in this section says:
>>
>> "=A0 This publication state is refreshed as described in [RFC3903] durin=
g
>> =A0 =A0the early dialog state or the Appearance Agent may reassign the
>> =A0 =A0appearance number."
>>
>> So if the removal publish is lost, it will eventually timeout since it
>> is not refreshed. =A0This is standard PUBLISH behavior described in RFC
>> 3903.
>>
>> >
>> >
>> > 5.4.
>> >
>> > =A0 A 400 response is returned if the chosen appearance number is inva=
lid,
>> >
>> > Is that always a 400 (Bad Request) or is any 4xx response allowed? =A0=
If
>> > it's always 400, add the words "Bad Request" after "400".
>>
>> We chose 400 in particular, although any 4xx response would have the
>> same result. =A0"Bad Request" is the reason phrase, and the practice of
>> putting it in () is a convention commonly used in SIP documents. =A0The
>> actual reason phrase can be different, customized ("Invalid
>> Appearance") if desired, or in a different language.
>>
>> So in this case we are specifying the 400 response.
>>
>> >
>> > =A0 If the Appearance Agent policy does not allow this, a 400 response
>> > =A0 is returned.
>> >
>> > Same question. =A0In addition, is 403 Forbidden allowed here?
>>
>> 403 is usually used in SIP to indicate that the request has failed due
>> to an authorization policy, and the request can be retried with
>> different credentials. =A0That doesn't quite fit here.
>>
>> >
>> > =A0 If an INVITE is sent by a member of the group to the shared AOR (i=
.e.
>> > =A0 they call their own AOR), the Appearance Agent MUST assign two
>> > =A0 appearance numbers. =A0The first appearance number will be the one
>> > =A0 selected or assigned to the outgoing INVITE. =A0The second appeara=
nce
>> > =A0 number will be another one assigned by the Appearance Agent for th=
e
>> > =A0 INVITE as it is forked back to the members of the group.
>> >
>> > How does that interact with the single appearance UAs in 8.1.1 that wo=
n't
>> > understand the second appearance number? =A0A warning that such a UA c=
an't
>> > pick up its call to its own AOR would suffice, either here or in 8.1.1=
.
>>
>> I will put text in 8.1.1 that makes this point clear.
>>
>> >
>> > 9.1
>> >
>> > =A0 A UA that has no knowledge of appearances must will only have
>> > =A0 appearance numbers for outgoing calls if assigned by the Appearanc=
e
>> > =A0 Agent. =A0If the non-shared appearance UA does not support Join or
>> > =A0 Replaces, all dialogs could be marked "exclusive" to indicate that
>> > =A0 these options are not available.
>> >
>> > Should that "could be marked" be changed to "SHOULD be marked" ?
>> > Also, analogous questions for "could" in 9.2 and "can" in 9.3.
>> >
>> > All three of these affect interoperability.
>>
>> I can change this to SHOULD. =A0Actually, it doesn't affect
>> interoperability, as "exclusive" is just a hint, for user experience
>> and interface purposes and to reduce failed requests. =A0If a Join or
>> Replace is inadvertently sent, the operation will fail, which is the
>> same result as not allowing it, although a worse user experience.
>>
>> >
>> > 12. Security Considerations
>> >
>> > In general, this section is weak on rationale - the second, third and
>> > fourth paragraphs should all explain more about the purpose of and/or
>> > rationale for their security requirements (e.g., what does the securit=
y
>> > mechanism protect against and when/why might that protection be desire=
d
>> > and/or required?).
>>
>> Right, the mechanisms are to provide privacy and to prevent
>> hijacking/spoofing. =A0I can add text to make this clear.
>>
>> >
>> > =A0 NOTIFY or PUBLISH message bodies that provide the dialog state
>> > =A0 information and the dialog identifiers MAY be encrypted end-to-end
>> > =A0 using the standard mechanisms.
>> >
>> > What are "the standard mechanisms"? =A0List them, and provide referenc=
es,
>> > please.
>>
>> That would be S/MIME as described in RFC 3261. =A0I can add this.
>>
>> >
>> > Please ensure that the section 6 XML and Section 7 ABNF are
>> > syntax-checked with actual tools.
>>
>> I will double check them.
>>
>> >
>> > Nits/editorial comments:
>> >
>> > p.10:
>> >
>> > =A0 The next section discusses the operations used to implement parts =
of
>> > =A0 the shared appearance feature.
>> >
>> > "The following list describes the operations ..." would be better.
>> >
>> > 5.3.1.
>> >
>> > =A0 A UA wanting to place a call but not have an appearance number
>> > =A0 assigned publishes before sending the INVITE without an 'appearanc=
e'
>> > =A0 element but with the 'shared' event package parameter present.
>> >
>> > I think I understand what was intended here, but this would be clearer
>> > if "publishes" was replaced with language about sending a PUBLISH.
>> > It's also not completely clear whether "without" applies to the
>> > INVITE or the PUBLISH, so this sentence probably needs to be reworded.
>>
>> OK, it is the PUBLISH that doesn't have the parameter - I'll make this c=
lear.
>>
>> >
>> > 5.4. - Expand B2BUA acronym on first use.
>> >
>> > idnits 2.12.13 ran clean.
>> >
>> > Thanks,
>> > --David
>> > ----------------------------------------------------
>> > David L. Black, Distinguished Engineer
>> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
>> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 29=
3-7786
>> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
>> > ----------------------------------------------------
>> >
>

From david.black@emc.com  Fri Jun 29 12:23:43 2012
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2E6521F88A3; Fri, 29 Jun 2012 12:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n8KxSv8lk2DY; Fri, 29 Jun 2012 12:23:42 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6A42821F889A; Fri, 29 Jun 2012 12:23:42 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5TJNYLU021288 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2012 15:23:35 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 29 Jun 2012 15:23:17 -0400
Received: from mxhub34.corp.emc.com (mxhub34.corp.emc.com [10.254.93.82]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5TJNHdw022925; Fri, 29 Jun 2012 15:23:17 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub34.corp.emc.com ([::1]) with mapi; Fri, 29 Jun 2012 15:23:16 -0400
From: <david.black@emc.com>
To: <dworley@avaya.com>, <alan.b.johnston@gmail.com>
Date: Fri, 29 Jun 2012 15:23:15 -0400
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Index: Ac1WK/SS5AOXm0ZpSfqMaQa/q754dwAAIaQQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208D3A9A0@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mohsen.soroush@sylantro.com, ietf@ietf.org, gen-art@ietf.org, bliss@ietf.org, vvenkatar@gmail.com
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bliss-shared-appearances-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 19:23:44 -0000

VGhhdCB3b3JrcyBmb3IgbWUsIFRoYW5rcywgLS1EYXZpZA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+IEZyb206IFdvcmxleSwgRGFsZSBSIChEYWxlKSBbbWFpbHRvOmR3b3JsZXlA
YXZheWEuY29tXQ0KPiBTZW50OiBGcmlkYXksIEp1bmUgMjksIDIwMTIgMzoxOCBQTQ0KPiBUbzog
YWxhbi5iLmpvaG5zdG9uQGdtYWlsLmNvbQ0KPiBDYzogQmxhY2ssIERhdmlkOyBtb2hzZW4uc29y
b3VzaEBzeWxhbnRyby5jb207IGlldGZAaWV0Zi5vcmc7IGdlbi0NCj4gYXJ0QGlldGYub3JnOyBi
bGlzc0BpZXRmLm9yZzsgdnZlbmthdGFyQGdtYWlsLmNvbQ0KPiBTdWJqZWN0OiBSZTogR2VuLUFS
VCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1ibGlzcy1zaGFyZWQtYXBwZWFyYW5jZXMtMTENCj4gDQo+
IE9uIFRodSwgMjAxMi0wNi0yOCBhdCAyMDowNSAtMDUwMCwgQWxhbiBKb2huc3RvbiB3cm90ZToN
Cj4gPiA+DQo+ID4gPiA0LjEgLSBSRVEtMTY6DQo+ID4gPg0KPiA+ID4gICBpbiB0aGlzIGNhc2Us
IHNlaXppbmcgdGhlIGxpbmUgaXMgdGhlIHNhbWUgdGhpbmcgYXMgZGlhbGluZy4NCj4gPiA+DQo+
ID4gPiBUaGF0IHNlZW1zIHdyb25nIC0gSSB3b3VsZCBoYXZlIHRob3VnaHQgaXQgd2FzIGEgInBy
ZXJlcXVpc2l0ZSIgYXMNCj4gPiA+IG9wcG9zZWQgdG8gInRoZSBzYW1lIHRoaW5nIiBiZWNhdXNl
IHNlaXppbmcgdGhlIGxpbmUgaXMgaW1tZWRpYXRlbHkNCj4gPiA+IGZvbGxvd2VkIGJ5IGEgZGlh
bGluZyByZXF1ZXN0Lg0KPiA+DQo+ID4NCj4gPiBUaGlzIHJlcXVpcmVtZW50IGlzIGFib3V0IHNl
bmRpbmcgb25lIHJlcXVlc3QgdGhhdCBjYXVzZXMgYm90aCBhY3Rpb25zDQo+ID4gdG8gb2NjdXIu
ICBJbiBhIFBTVE4gcmluZ2Rvd24gY2lyY3VpdCAoYSB2ZXJ5IHNwZWNpYWxpemVkIGNpcmN1aXQs
DQo+ID4gdXNlZCBmb3IgImhvdGxpbmVzIiksIHRoZSB0d28gb3BlcmF0aW9ucyBhcmUgdGhlIHNh
bWUgdGhpbmcuICBCZXNpZGVzDQo+ID4gdGhpcyBzdGF0ZW1lbnQsIGlzIFJFUS0xNiBpdHNlbGYg
bm90IGNsZWFyPyAgUGVyaGFwcyBJIHNob3VsZCBqdXN0DQo+ID4gcmVtb3ZlIHRoaXMgc3RhdGVt
ZW50IGlmIGl0IGFkZHMgY29uZnVzaW9uIHJhdGhlciB0aGFuIGNsYXJpdHkgdG8gdGhlDQo+ID4g
cmVxdWlyZW1lbnQuDQo+IA0KPiBJTUhPLCBhIGdvb2QgZml4IGlzOg0KPiANCj4gICAgUkVRLTE2
IFRoZSBtZWNoYW5pc20gc2hvdWxkIHN1cHBvcnQgYSB3YXkgZm9yIGEgVUEgdG8gc2VpemUgYQ0K
PiAgICBwYXJ0aWN1bGFyIGFwcGVhcmFuY2UgbnVtYmVyIGFuZCBhbHNvIHNlbmQgdGhlIHJlcXVl
c3QgYXQgdGhlIHNhbWUNCj4gICAgdGltZS4gIFRoaXMgaXMgbmVlZGVkIHdoZW4gYW4gYXV0b21h
dGljIHJpbmdkb3duIGZlYXR1cmUgKGEgdGVsZXBob25lDQo+ICAgIGNvbmZpZ3VyZWQgdG8gaW1t
ZWRpYXRlbHkgZGlhbCBhIHBob25lIG51bWJlciB3aGVuIGl0IGdvZXMgb2ZmIGhvb2spDQo+ICAg
IGlzIGNvbWJpbmVkIHdpdGggc2hhcmVkIGFwcGVhcmFuY2VzIC0gaW4gdGhpcyBjYXNlLCBzZWl6
aW5nIHRoZSBsaW5lDQo+ICAgIGlzID4+PmludGVncmF0ZWQgd2l0aDw8PCBkaWFsaW5nLg0KPiAN
Cj4gRGFsZQ0KDQo=

From dworley@avaya.com  Fri Jun 29 12:18:33 2012
Return-Path: <dworley@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54B0C21F8865; Fri, 29 Jun 2012 12:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.952
X-Spam-Level: 
X-Spam-Status: No, score=-102.952 tagged_above=-999 required=5 tests=[AWL=0.647, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D2sT0e2dOwwG; Fri, 29 Jun 2012 12:18:32 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id D1EF821F87EC; Fri, 29 Jun 2012 12:18:31 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAIj+7U+HCzI1/2dsb2JhbABFhVqvXoEegQeCGAEBAQEDEhERRRACAQgNCwICJgICAjAVEAEBBA4NGodpnnqKHpMggSCPDzJgA5sriguCew
X-IronPort-AV: E=Sophos;i="4.77,499,1336363200"; d="scan'208";a="313255578"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 29 Jun 2012 15:15:55 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 29 Jun 2012 14:59:49 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 29 Jun 2012 15:18:28 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "alan.b.johnston@gmail.com" <alan.b.johnston@gmail.com>
Date: Fri, 29 Jun 2012 15:18:24 -0400
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Index: Ac1WK/SS5AOXm0ZpSfqMaQa/q754dw==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
In-Reply-To: <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 29 Jun 2012 13:18:37 -0700
Cc: "mohsen.soroush@sylantro.com" <mohsen.soroush@sylantro.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "bliss@ietf.org" <bliss@ietf.org>, "vvenkatar@gmail.com" <vvenkatar@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bliss-shared-appearances-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 19:18:33 -0000

T24gVGh1LCAyMDEyLTA2LTI4IGF0IDIwOjA1IC0wNTAwLCBBbGFuIEpvaG5zdG9uIHdyb3RlOgo+
ID4KPiA+IDQuMSAtIFJFUS0xNjoKPiA+Cj4gPiAgIGluIHRoaXMgY2FzZSwgc2VpemluZyB0aGUg
bGluZSBpcyB0aGUgc2FtZSB0aGluZyBhcyBkaWFsaW5nLgo+ID4KPiA+IFRoYXQgc2VlbXMgd3Jv
bmcgLSBJIHdvdWxkIGhhdmUgdGhvdWdodCBpdCB3YXMgYSAicHJlcmVxdWlzaXRlIiBhcwo+ID4g
b3Bwb3NlZCB0byAidGhlIHNhbWUgdGhpbmciIGJlY2F1c2Ugc2VpemluZyB0aGUgbGluZSBpcyBp
bW1lZGlhdGVseQo+ID4gZm9sbG93ZWQgYnkgYSBkaWFsaW5nIHJlcXVlc3QuCj4gCj4gCj4gVGhp
cyByZXF1aXJlbWVudCBpcyBhYm91dCBzZW5kaW5nIG9uZSByZXF1ZXN0IHRoYXQgY2F1c2VzIGJv
dGggYWN0aW9ucwo+IHRvIG9jY3VyLiAgSW4gYSBQU1ROIHJpbmdkb3duIGNpcmN1aXQgKGEgdmVy
eSBzcGVjaWFsaXplZCBjaXJjdWl0LAo+IHVzZWQgZm9yICJob3RsaW5lcyIpLCB0aGUgdHdvIG9w
ZXJhdGlvbnMgYXJlIHRoZSBzYW1lIHRoaW5nLiAgQmVzaWRlcwo+IHRoaXMgc3RhdGVtZW50LCBp
cyBSRVEtMTYgaXRzZWxmIG5vdCBjbGVhcj8gIFBlcmhhcHMgSSBzaG91bGQganVzdAo+IHJlbW92
ZSB0aGlzIHN0YXRlbWVudCBpZiBpdCBhZGRzIGNvbmZ1c2lvbiByYXRoZXIgdGhhbiBjbGFyaXR5
IHRvIHRoZQo+IHJlcXVpcmVtZW50LgoKSU1ITywgYSBnb29kIGZpeCBpczoKCiAgIFJFUS0xNiBU
aGUgbWVjaGFuaXNtIHNob3VsZCBzdXBwb3J0IGEgd2F5IGZvciBhIFVBIHRvIHNlaXplIGEKICAg
cGFydGljdWxhciBhcHBlYXJhbmNlIG51bWJlciBhbmQgYWxzbyBzZW5kIHRoZSByZXF1ZXN0IGF0
IHRoZSBzYW1lCiAgIHRpbWUuICBUaGlzIGlzIG5lZWRlZCB3aGVuIGFuIGF1dG9tYXRpYyByaW5n
ZG93biBmZWF0dXJlIChhIHRlbGVwaG9uZQogICBjb25maWd1cmVkIHRvIGltbWVkaWF0ZWx5IGRp
YWwgYSBwaG9uZSBudW1iZXIgd2hlbiBpdCBnb2VzIG9mZiBob29rKQogICBpcyBjb21iaW5lZCB3
aXRoIHNoYXJlZCBhcHBlYXJhbmNlcyAtIGluIHRoaXMgY2FzZSwgc2VpemluZyB0aGUgbGluZQog
ICBpcyA+Pj5pbnRlZ3JhdGVkIHdpdGg8PDwgZGlhbGluZy4KCkRhbGUKCg==

From alan.b.johnston@gmail.com  Fri Jun 29 17:43:05 2012
Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94E2721F849A; Fri, 29 Jun 2012 17:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.203
X-Spam-Level: 
X-Spam-Status: No, score=-102.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTu8so4Rqnni; Fri, 29 Jun 2012 17:43:05 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id E510E21F844B; Fri, 29 Jun 2012 17:43:04 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so4968301obb.31 for <multiple recipients>; Fri, 29 Jun 2012 17:43:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:x-mailer:from:subject:date:to; bh=eF5yYxdrm0swAjP9jGXQF5kDnPRhZ5N4RqNg9kmEaAg=; b=lmI3kN/oGVrNVHkFcngn92r1j6nz79rYUHZ9LmTrY6z+izKqaavsbSu4mkkSS9p7Lh UFbT681uPb65ttObCQhOgHSOPHhBicGul30lCpfNhOcwO2sv1mFA7el3R6KSD5SBBQeh 82KbdsDeR/2Sf+IO6c62aNkRpmKS5j/0BX/DsrQxL1yqFjFztzw7SP+e974xFg1EDaEC 3M7AAlmzkCLX+Z/P0zDMfmaBE7D1X1dw1Bk1Wb11ii2J5K9BWv2rXwhUjr9yLb7vfIsS 9yqKFUzTnlqxfbdsm3NoH3OLstuFflkXYa3sdoAiXuAsuLzaabi84CtDU0eYnx2wpE20 Vesw==
Received: by 10.60.21.198 with SMTP id x6mr2034683oee.24.1341016898396; Fri, 29 Jun 2012 17:41:38 -0700 (PDT)
Received: from [10.4.153.20] (mobile-166-147-069-169.mycingular.net. [166.147.69.169]) by mx.google.com with ESMTPS id n10sm4159930oeb.6.2012.06.29.17.41.36 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Jun 2012 17:41:37 -0700 (PDT)
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.com>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain; charset=us-ascii
Message-Id: <8CC36564-7A02-47AC-9BCA-4DE0C9BECADE@gmail.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (9B206)
From: Alan Johnston <alan.b.johnston@gmail.com>
Date: Fri, 29 Jun 2012 19:41:28 -0500
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Cc: "mohsen.soroush@sylantro.com" <mohsen.soroush@sylantro.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "bliss@ietf.org" <bliss@ietf.org>, "vvenkatar@gmail.com" <vvenkatar@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bliss-shared-appearances-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jun 2012 00:43:05 -0000

We will use this language. Thanks, Dale.=20

 - Alan -



On Jun 29, 2012, at 2:18 PM, "Worley, Dale R (Dale)" <dworley@avaya.com> wro=
te:

> On Thu, 2012-06-28 at 20:05 -0500, Alan Johnston wrote:
>>>=20
>>> 4.1 - REQ-16:
>>>=20
>>>  in this case, seizing the line is the same thing as dialing.
>>>=20
>>> That seems wrong - I would have thought it was a "prerequisite" as
>>> opposed to "the same thing" because seizing the line is immediately
>>> followed by a dialing request.
>>=20
>>=20
>> This requirement is about sending one request that causes both actions
>> to occur.  In a PSTN ringdown circuit (a very specialized circuit,
>> used for "hotlines"), the two operations are the same thing.  Besides
>> this statement, is REQ-16 itself not clear?  Perhaps I should just
>> remove this statement if it adds confusion rather than clarity to the
>> requirement.
>=20
> IMHO, a good fix is:
>=20
>   REQ-16 The mechanism should support a way for a UA to seize a
>   particular appearance number and also send the request at the same
>   time.  This is needed when an automatic ringdown feature (a telephone
>   configured to immediately dial a phone number when it goes off hook)
>   is combined with shared appearances - in this case, seizing the line
>   is >>>integrated with<<< dialing.
>=20
> Dale
>=20

From suresh.krishnan@ericsson.com  Fri Jun 29 18:05:44 2012
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F16421F85D0; Fri, 29 Jun 2012 18:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level: 
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3HGjY2GCrNz1; Fri, 29 Jun 2012 18:05:42 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 69DDB21F85CC; Fri, 29 Jun 2012 18:05:42 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q5U15ctE026675; Fri, 29 Jun 2012 20:05:39 -0500
Received: from [142.133.112.108] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.264.0; Fri, 29 Jun 2012 21:05:32 -0400
Message-ID: <4FEE50DC.5030802@ericsson.com>
Date: Fri, 29 Jun 2012 21:05:32 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: "kathleen.moriarty@emc.com" <kathleen.moriarty@emc.com>
References: <F5063677821E3B4F81ACFB7905573F2403949010@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F2403949010@MX15A.corp.emc.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-6man-lineid.all@tools.ietf.org" <draft-ietf-6man-lineid.all@tools.ietf.org>, "sven.ooghe@alcatel-lucent.com" <sven.ooghe@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, =?ISO-8859-1?Q?Bal=E1zs_Varga_A?= <balazs.a.varga@ericsson.com>, "iesg@ietf.org" <iesg@ietf.org>, "nordmark@cisco.com" <nordmark@cisco.com>
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-6man-lineid-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jun 2012 01:05:44 -0000

Hi Kathleen,
  Thanks for the review.

kathleen.moriarty@emc.com wrote:
> Nits/editorial comments:
>  
> Figure 1: Some of the acronyms used in the diagram are not expanded upon
> in the introduction section, RG for instance (it is in the terminology
> section, but is the only acronym not spelled out near figure 1).  It may
> also be confusing to see AN for Access Node next to Aggregation
> Network.  It may help to expand AN?  It is in the Introduction, so not a
> big deal.

Will clarify this in the next revision. Thanks for catching this.

Thanks
Suresh
