
From vkg@bell-labs.com  Fri Feb  1 10:35:28 2013
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 EFF9E21F8D92 for <gen-art@ietfa.amsl.com>; Fri,  1 Feb 2013 10:35:28 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XJEfdEryO8fK for <gen-art@ietfa.amsl.com>; Fri,  1 Feb 2013 10:35:28 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 1E51321F8D44 for <gen-art@ietf.org>; Fri,  1 Feb 2013 10:35:28 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r11IZLAJ015124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 1 Feb 2013 12:35:21 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r11IZK5H017063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 1 Feb 2013 12:35:21 -0600
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 r11IZKXW000102; Fri, 1 Feb 2013 12:35:20 -0600 (CST)
Message-ID: <510C0AE8.3060201@bell-labs.com>
Date: Fri, 01 Feb 2013 12:35:20 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: draft-ietf-rtgwg-ordered-fib@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.9
Cc: Stewart Bryant <stbryant@cisco.com>, Adrian Farrel <adrian@olddog.co.uk>, General Area Review Team <gen-art@ietf.org>, akatlas@gmail.com, aretana@cisco.com
Subject: [Gen-art] Gen-ART review of draft-ietf-rtgwg-ordered-fib-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: Fri, 01 Feb 2013 18:35:29 -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-rtgwg-ordered-fib-09
Reviewer: Vijay K. Gurbani
Review Date: Feb-01-2013
IETF LC End Date: Unknown
IESG Telechat date: Feb-07-2013

This document is ready as an Informational.

Major: 0
Minor: 0
Nits: 1

Nits: It is mentioned in Section 2 that, "The technology described in
this document has been subject to extensive simulation using real
network topologies and costs and pathological convergence behaviour."

If the simulations were published in an archival format conference
proceeding or if the results are publicly available elsewhere, it may
make sense to provide appropriate references.

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 vkg@bell-labs.com  Fri Feb  1 10:59:16 2013
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 1EBB721E8039 for <gen-art@ietfa.amsl.com>; Fri,  1 Feb 2013 10:59:16 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kAcy8bz6bVff for <gen-art@ietfa.amsl.com>; Fri,  1 Feb 2013 10:59:15 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 35BF911E8099 for <gen-art@ietf.org>; Fri,  1 Feb 2013 10:59:15 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r11IxAPN006108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 1 Feb 2013 12:59:10 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r11Ix9Xr012487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 1 Feb 2013 12:59:10 -0600
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 r11Ix9h9018806; Fri, 1 Feb 2013 12:59:09 -0600 (CST)
Message-ID: <510C107D.5040503@bell-labs.com>
Date: Fri, 01 Feb 2013 12:59:09 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: draft-ietf-tsvwg-sctp-udp-encaps@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.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: gorry@erg.abdn.ac.uk, General Area Review Team <gen-art@ietf.org>, "James M. Polk" <jmpolk@cisco.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [Gen-art] Gen-ART review of draft-ietf-tsvwg-sctp-udp-encaps-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: Fri, 01 Feb 2013 18:59:16 -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-tsvwg-sctp-udp-encaps-09
Reviewer: Vijay K. Gurbani
Review Date: Fev-01-2013
IETF LC End Date: Jan-22-2013
IESG Telechat date: Feb-07-2013

This document is ready as a Proposed Standard.

Major: 0
Minor: 0
Nits: 0

I reviewed -07 and have no further comments on -09.

- 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 stbryant@cisco.com  Fri Feb  1 11:22:41 2013
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 2976A21E8044 for <gen-art@ietfa.amsl.com>; Fri,  1 Feb 2013 11:22:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.522
X-Spam-Level: 
X-Spam-Status: No, score=-110.522 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cywz91DjsKtm for <gen-art@ietfa.amsl.com>; Fri,  1 Feb 2013 11:22:39 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id D0AEA21E8039 for <gen-art@ietf.org>; Fri,  1 Feb 2013 11:22:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1242; q=dns/txt; s=iport; t=1359746557; x=1360956157; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=nhIpJebn6G6tmfojLm70b0phAlpQ6iWSWV9eeb3F8hc=; b=ilxLJ2/UUcdYx5teWr+I7SzrzKde805S+F0QR+2HyY+ZqWf6/LGgc1HK 6vaK6lZGa0W89FdehqvUuWcprghSc7fdt1bisl91rMCXXl8CTK/kV8ppP 5XxCjud4nURal0bZgPsc0hWWTxP0eBFNBd2kP2A9e/pTPMkiWzatmwjnA I=;
X-IronPort-AV: E=Sophos;i="4.84,579,1355097600"; d="scan'208";a="80192133"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 01 Feb 2013 19:22:35 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r11JMZEX014306 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Feb 2013 19:22:35 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r11JMYJX015417; Fri, 1 Feb 2013 19:22:34 GMT
Message-ID: <510C15FA.3060103@cisco.com>
Date: Fri, 01 Feb 2013 19:22:34 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
References: <510C0AE8.3060201@bell-labs.com>
In-Reply-To: <510C0AE8.3060201@bell-labs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-rtgwg-ordered-fib@tools.ietf.org, Adrian Farrel <adrian@olddog.co.uk>, General Area Review Team <gen-art@ietf.org>, akatlas@gmail.com, aretana@cisco.com
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-rtgwg-ordered-fib-09
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: Fri, 01 Feb 2013 19:22:41 -0000

On 01/02/2013 18:35, Vijay K. Gurbani 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-rtgwg-ordered-fib-09
> Reviewer: Vijay K. Gurbani
> Review Date: Feb-01-2013
> IETF LC End Date: Unknown
> IESG Telechat date: Feb-07-2013
>
> This document is ready as an Informational.
>
> Major: 0
> Minor: 0
> Nits: 1
>
> Nits: It is mentioned in Section 2 that, "The technology described in
> this document has been subject to extensive simulation using real
> network topologies and costs and pathological convergence behaviour."
>
> If the simulations were published in an archival format conference
> proceeding or if the results are publicly available elsewhere, it may
> make sense to provide appropriate references. 
Some elements are scattered though the IETF meeting archives as this
was discussed in the RTGWG meetings.

However some aspects are too sensitive to publish as we looked
at the expected behaviour on operational networks complete with
costs.

- Stewart



From vkg@bell-labs.com  Fri Feb  1 11:29:43 2013
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 4C45421E8041 for <gen-art@ietfa.amsl.com>; Fri,  1 Feb 2013 11:29:43 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bfY6nFgx3GQ for <gen-art@ietfa.amsl.com>; Fri,  1 Feb 2013 11:29:42 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACCA11E8097 for <gen-art@ietf.org>; Fri,  1 Feb 2013 11:29:42 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r11JTa9Q017396 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 1 Feb 2013 13:29:37 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r11JTaXj022116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 1 Feb 2013 13:29:36 -0600
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 r11JTZ0c013190; Fri, 1 Feb 2013 13:29:35 -0600 (CST)
Message-ID: <510C179F.4080900@bell-labs.com>
Date: Fri, 01 Feb 2013 13:29:35 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: stbryant@cisco.com
References: <510C0AE8.3060201@bell-labs.com> <510C15FA.3060103@cisco.com>
In-Reply-To: <510C15FA.3060103@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: draft-ietf-rtgwg-ordered-fib@tools.ietf.org, Adrian Farrel <adrian@olddog.co.uk>, General Area Review Team <gen-art@ietf.org>, akatlas@gmail.com, aretana@cisco.com
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-rtgwg-ordered-fib-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: Fri, 01 Feb 2013 19:29:43 -0000

On 02/01/2013 01:22 PM, Stewart Bryant wrote:
> Some elements are scattered though the IETF meeting archives as this
> was discussed in the RTGWG meetings.
>
> However some aspects are too sensitive to publish as we looked
> at the expected behaviour on operational networks complete with
> costs.

Stewart: Sure, I can understand the need for sensitivity.

Would be nice to have a canonical topology stripped of any sensitive
network configuration, but I realize that this is not a necessity nor
a prerequisite for moving the draft ahead.  That is why I indicated
this as a nit.

However, the engineer in me likes to see papers with results
that can easily be duplicated by others working in the domain.

That said, please move ahead with the draft from my end.  I have
no further comments.

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 rbarnes@bbn.com  Sun Feb  3 11:12:37 2013
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 606AF21F84E2 for <gen-art@ietfa.amsl.com>; Sun,  3 Feb 2013 11:12:37 -0800 (PST)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWtQt25KM5ab for <gen-art@ietfa.amsl.com>; Sun,  3 Feb 2013 11:12:33 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 0B9F721F8472 for <gen-art@ietf.org>; Sun,  3 Feb 2013 11:12:32 -0800 (PST)
Received: from [128.89.253.237] (port=51498) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1U24zQ-00090N-4o for gen-art@ietf.org; Sun, 03 Feb 2013 14:12:32 -0500
From: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <5279E69A-0B41-4E65-BCBA-7F1B928AC697@bbn.com>
Date: Sun, 3 Feb 2013 14:12:32 -0500
To: gen-art@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [Gen-art] Gen-ART review of draft-ietf-ccamp-lmp-behavior-negotiation-10
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 Feb 2013 19:12:37 -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-ccamp-lmp-behavior-negotiation-06
Reviewer: Richard Barnes
Review Date: 2013-02-02
IETF LC End Date: 2012-01-21
IESG Telechat date: 2012-02-07

Summary:  Ready, with a couple of minor questions / clarifications.

Comment:

Overall, this document seems very clear and readable.  Thanks!  The one =
concern I have is over the use of "likely" in the discussion of backward =
compatibility; I would like to see more precise language there.

Section 2.1.  Would be helpful to either include the old formats and/or =
say explicitly what is changing.=20

Section 2.2. =20
"Nodes which support" -> "nodes that support" =20
"Ordering of CONFIG objects" -> "... With different C-type values"

Section 3.1.MBZ. Might help to clarify that this means that the number =
of bits MUST be a multiple of 32. (I got a little confused between bits =
and bytes here.)

Section 4. "Likely"
Is it possible for a 4204-compliant implementation to not do one of =
these?  If so then remove "likely".  If not, then why happens on the =
exceptional case?=

From rbarnes@bbn.com  Sun Feb  3 11:13:41 2013
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 C309721F84E2; Sun,  3 Feb 2013 11:13:41 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0Gom1g8l1WI; Sun,  3 Feb 2013 11:13:41 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4311121F8472; Sun,  3 Feb 2013 11:13:41 -0800 (PST)
Received: from [128.89.253.237] (port=51500) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1U250R-000MCE-OU; Sun, 03 Feb 2013 14:13:35 -0500
From: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sun, 3 Feb 2013 14:13:36 -0500
Message-Id: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com>
To: "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Cc: draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-ccamp-lmp-behavior-negotiation-10
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 Feb 2013 19:13:41 -0000

I have been selected as the General Area Review Team (Gen-ART) reviewer =
for this draft (for background on Gen-ART, please =
seehttp://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-ccamp-lmp-behavior-negotiation-10
Reviewer: Richard Barnes
Review Date: 2013-02-02
IETF LC End Date: 2012-01-21
IESG Telechat date: 2012-02-07

Summary:  Ready, with a couple of minor questions / clarifications.

Comment:

Overall, this document seems very clear and readable.  Thanks!  The one =
concern I have is over the use of "likely" in the discussion of backward =
compatibility; I would like to see more precise language there.

Section 2.1.  Would be helpful to either include the old formats and/or =
say explicitly what is changing.=20

Section 2.2. =20
"Nodes which support" -> "nodes that support" =20
"Ordering of CONFIG objects" -> "... With different C-type values"

Section 3.1.MBZ. Might help to clarify that this means that the number =
of bits MUST be a multiple of 32. (I got a little confused between bits =
and bytes here.)

Section 4. "Likely"
Is it possible for a 4204-compliant implementation to not do one of =
these?  If so then remove "likely".  If not, then why happens on the =
exceptional case?=

From david.black@emc.com  Sun Feb  3 12:55:42 2013
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 C724821F87D9; Sun,  3 Feb 2013 12:55:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=2.299, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bklcBUlUUe60; Sun,  3 Feb 2013 12:55:41 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1C25021F87D4; Sun,  3 Feb 2013 12:55:40 -0800 (PST)
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 r13KtUvx008094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 3 Feb 2013 15:55:32 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sun, 3 Feb 2013 15:55:10 -0500
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r13Kt8Ot005100; Sun, 3 Feb 2013 15:55:08 -0500
Received: from mx15a.corp.emc.com ([169.254.1.210]) by mxhub13.corp.emc.com ([128.222.70.234]) with mapi; Sun, 3 Feb 2013 15:55:08 -0500
From: "Black, David" <david.black@emc.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Content-Class: urn:content-classes:message
Date: Sun, 3 Feb 2013 15:55:07 -0500
Thread-Topic: Gen-ART review of draft-ietf-sidr-algorithm-agility-11
Thread-Index: AQHN9I+FMi1VHdNSWkquHGET+qZOd5hotufpgAABeIk=
Message-ID: <6BE9E091-6BD8-4D6C-941A-7A50128A0773@mimectl>
References: <8D3D17ACE214DC429325B2B98F3AE71287CBF04D@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71287E873CF@MX15A.corp.emc.com>, <EF4348D391D0334996EE9681630C83F022049044@xmb-rcd-x02.cisco.com>
In-Reply-To: <EF4348D391D0334996EE9681630C83F022049044@xmb-rcd-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-mimectl: Produced By Microsoft Exchange V8.3.105.0
Content-Type: multipart/alternative; boundary="_000_6BE9E0916BD84D6C941A7A50128A0773mimectl_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "Stewart Bryant \(stbryant\)" <stbryant@cisco.com>, "Roque Gagliano \(rogaglia\)" <rogaglia@cisco.com>, Stephen Kent <kent@bbn.com>, "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-sidr-algorithm-agility-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: Sun, 03 Feb 2013 20:55:42 -0000

--_000_6BE9E0916BD84D6C941A7A50128A0773mimectl_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

One (final, I hope) comment in response to the second last call on this dra=
ft.

I think publication as a BCP is definitely appropriate, as this draft is en=
tirely about a transition process.

Thanks,
--David

________________________________
From: Roque Gagliano (rogaglia) [rogaglia@cisco.com]
Sent: Thursday, January 17, 2013 3:49 AM
To: Black, David
Cc: Roque Gagliano (rogaglia); Stephen Kent; Sean Turner; gen-art@ietf.org;=
 sidr@ietf.org; Stewart Bryant (stbryant)
Subject: Re: Gen-ART review of draft-ietf-sidr-algorithm-agility-11

Thank YOU David for been such a great reviewer.

I will solve the Idnits in my working version waiting for other comments du=
ring IESG review.

Regards,
Roque



On Jan 17, 2013, at 6:38 AM, "Black, David" <david.black@emc.com> wrote:

> The -11 version of this draft resolves all of the concerns raised by the
> Gen-ART review of the -09 version.  I want to thank the authors for the
> timely and productive manner in which the review's concerns were addresse=
d.
>
> idnits 2.12.13 found a minor line length problem that can be left to the
> RFC Editor to correct.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: Black, David
>> Sent: Friday, December 28, 2012 3:26 PM
>> To: rogaglia@cisco.com; Stephen Kent; Sean Turner; gen-art@ietf.org
>> Cc: Black, David; sidr@ietf.org; Stewart Bryant
>> Subject: Gen-ART review of draft-ietf-sidr-algorithm-agility-09
>>
>> 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-sidr-algorithm-agility-09
>> Reviewer: David L. Black
>> Review Date: December 28, 2012
>> IETF LC End Date: December 14, 2012
>>
>> Summary:
>>
>> This draft is on the right track but has open issues, described in the r=
eview.
>>
>> I apologize for the tardy arrival of this review after the end of IETF L=
ast
>> Call for this draft - the last few months have been a rather busy time f=
or me.
>>
>> This draft specifies the algorithm transition process for RPKI, which
>> entails coordinated issuance of new certificates and other signed produc=
ts
>> across the collection of RPKI CAs in a fashion that ensures that at leas=
t
>> one set of signed products is usable at all times.
>>
>> The draft is generally well-written and clear, but has an unfortunate
>> nomenclature change problem that is the primary open issue[*].
>>
>> Major issues:
>>
>> [*] Section 4.7 changes the meaning of the algorithm suite names (A, B
>> and C) from prior sections.  This also affects Sections 6 and 7.
>> I have classified this as a major issue as I believe it introduces
>> severe lack of clarity (and potential ambiguity) into the following
>> two paragraphs in Section 7:
>>
>>   During Phase 1, a CA that revokes a certificate under Suite A SHOULD
>>   revoke the corresponding certificate under Suite B, if that
>>   certificate exists.  During Phase 4, a CA that revokes a certificate
>>   under Suite A SHOULD revoke the corresponding certificate under Suite
>>   C, if that certificate exists.
>>
>>   During Phase 1, a CA may revoke certificates under Suite B without
>>   revoking them under Suite A, since the Suite B products are for test
>>   purposes.  During Phase 4 a CA may revoke certificates issued under
>>   Suite C without revoking them under Suite A, since Suite C products
>>   are being deprecated.
>>
>> Despite the use of three letters (A, B and C), there are only two
>> algorithm suites involved, and different instances of Suite A refer to
>> different algorithm suites.  In each paragraph, the first instance of
>> "Suite A" refers to the same algorithm suite as "Suite C", and the
>> second instance of "Suite A" refers to the same algorithm suite
>> as "Suite B".
>>
>> It would be much better and clearer to not change the meaning of the
>> algorithm suite names until the EOL date. In addition, this change
>> should enable removal of the Suite C concept from this draft.  I
>> strongly recommend removing the Suite C concept, as the C-A-B
>> chronological order of suite introduction dates seems counter-intuitive.
>>
>> Minor issues:
>>
>> Starting in Section 4.3.1, there are a number of uses of "will be"
>> (future tense) in the milestone and phase descriptions.  All of
>> these uses of "will be" should be reviewed to determine whether
>> "MUST be" is appropriate, e.g., as appears to be the case for
>> this sentence in 4.3.1:
>>
>>   Additionally, the new algorithm transition timeline document will be
>>   published with the following information:
>>
>> When "MUST be" is not appropriate, present tense (i.e., "is") is
>> preferable.
>>
>> Nits/editorial:
>>
>> Abstract: The following two sentences don't quite line up:
>>
>>   The process
>>   is expected to be completed in a time scale of months or years.
>>   Consequently, no emergency transition is specified.
>>
>> Also, section 4.2 indicates that a multi-year transition timeframe
>> is expected, which suggests that "months" is not appropriate in
>> the abstract.  Suggested rephrasing:
>>
>>   The time available to complete the transition process
>>   is expected to be several years.
>>   Consequently, no emergency transition process is specified.
>>
>> Section 2. Introduction: The first sentence in the last paragraph
>> mentions a forthcoming BCP on transition timetable.  The rest of
>> that paragraph implies that the BCP is for a single transition, as
>> opposed to being a BCP for transitions in general.  It would be
>> helpful to clarify that at the start of the paragraph, e.g.,
>> by adding "For each algorithm transition," to the start of the
>> paragraph.
>>
>> Section 3 Definitions: Is there any concern about possible
>> confusion of the use of "Suite B" in this draft with NSA Suite B?
>> The draft is clear on what Suite B means for RPKI, but I suspect
>> that RPKI Suite B and NSA Suite B are unlikely to match, if ever.
>>
>> Describing Phase 0 as both the steady state of the RPKI and the first
>> phase of transition is confusing (e.g., in 4.3).  It would be clearer
>> if Phase 0 began with publication of the updated RPKI algorithm
>> document (Milestone 1) and that the activities that are unchanged
>> from steady state were described as not changing in phase 0.
>>
>> Starting near the end of section 4.3, the three characters
>> |-> are used in figures to represent an RPKI hierarchy relationship;
>> that relationship should be defined and/or explained before it is used.
>> For clarity, I'd suggest swapping the order of the two paragraphs
>> above that figure in 4.3 and making the following change at the end
>> of the paragraph that is moved down (addition of the word
>> "certificate" is the important change):
>>
>> OLD
>>   and shows the relationship between three CAs (X, Y, and Z) that form
>>   a chain.
>> NEW
>>   and shows the relationships among the three CAs (X, Y, and Z)
>>   that participate in a certificate chain.
>>
>> Subsequent uses of |-> seemed clear to me.
>>
>> Section 4.5 Phase 2 says that Suite B product SHOULD be stored at
>> independent publication points, but does not make it clear that this
>> recommendation applies beyond phase 2.  I suggest adding text to
>> make that clear - a reference to Section 9 (which is clear about
>> this) may be useful as part of that text.
>>
>> In Section 6, please expand the ROA acronym on first use and consider
>> whether it should be defined in Section 3.  I'm also assuming that the
>> ASN acronym is intended to refer to ASN.1 content; if not, that
>> acronym also needs attention.
>>
>> idnits 2.12.13 found a couple of minor nits:
>>
>>  ** There is 1 instance of too long lines in the document, the longest o=
ne
>>     being 23 characters in excess of 72.
>>
>>  =3D=3D The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keywo=
rd, but
>>     does not include the phrase in its RFC 2119 key words list.
>>
>> Thanks,
>> --David
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>



--_000_6BE9E0916BD84D6C941A7A50128A0773mimectl_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD>
<STYLE>.EmailQuote {
	BORDER-LEFT: #800000 2px solid; PADDING-LEFT: 4pt; MARGIN-LEFT: 1pt
}
</STYLE>

<STYLE title=3DowaParaStyle><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></STYLE>
</HEAD>
<BODY ocsi=3D"x">
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3D"Courier New">One (fin=
al, I hope) comment in response to the second last call on this draft.</FON=
T></DIV>
<DIV dir=3Dltr><FONT size=3D2 face=3D"courier new"></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2 face=3D"courier new">I think publication as a=
 BCP is definitely appropriate, as this draft is entirely about a transitio=
n process.</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2 face=3D"courier new"></FONT>&nbsp;</DIV>
<DIV>
<DIV><FONT size=3D2 face=3D"Courier New">Thanks,</FONT></DIV>
<DIV><FONT size=3D2 face=3D"courier new">--David</FONT></DIV>
<DIV><FONT face=3D"Courier New"><FONT size=3D2></FONT>&nbsp;</DIV></FONT></=
DIV>
<DIV style=3D"DIRECTION: ltr" id=3DdivRpF315341>
<HR tabIndex=3D-1>
<FONT color=3D#000000 size=3D2 face=3DTahoma><B>From:</B> Roque Gagliano (r=
ogaglia) [rogaglia@cisco.com]<BR><B>Sent:</B> Thursday, January 17, 2013 3:=
49 AM<BR><B>To:</B> Black, David<BR><B>Cc:</B> Roque Gagliano (rogaglia); S=
tephen Kent; Sean Turner; gen-art@ietf.org; sidr@ietf.org; Stewart Bryant (=
stbryant)<BR><B>Subject:</B> Re: Gen-ART review of draft-ietf-sidr-algorith=
m-agility-11<BR></FONT><BR></DIV>
<DIV></DIV><FONT size=3D2>
<DIV class=3DPlainText>Thank YOU David for been such a great reviewer.<BR><=
BR>I will solve the Idnits in my working version waiting for other comments=
 during IESG review.<BR><BR>Regards,<BR>Roque<BR><BR><BR><BR>On Jan 17, 201=
3, at 6:38 AM, "Black, David" &lt;david.black@emc.com&gt; wrote:<BR><BR>&gt=
; The -11 version of this draft resolves all of the concerns raised by the<=
BR>&gt; Gen-ART review of the -09 version.&nbsp; I want to thank the author=
s for the<BR>&gt; timely and productive manner in which the review's concer=
ns were addressed.<BR>&gt; <BR>&gt; idnits 2.12.13 found a minor line lengt=
h problem that can be left to the<BR>&gt; RFC Editor to correct.<BR>&gt; <B=
R>&gt; Thanks,<BR>&gt; --David<BR>&gt; <BR>&gt;&gt; -----Original Message--=
---<BR>&gt;&gt; From: Black, David<BR>&gt;&gt; Sent: Friday, December 28, 2=
012 3:26 PM<BR>&gt;&gt; To: rogaglia@cisco.com; Stephen Kent; Sean Turner; =
gen-art@ietf.org<BR>&gt;&gt; Cc: Black, David; sidr@ietf.org; Stewart Bryan=
t<BR>&gt;&gt; Subject: Gen-ART review of draft-ietf-sidr-algorithm-agility-=
09<BR>&gt;&gt; <BR>&gt;&gt; I am the assigned Gen-ART reviewer for this dra=
ft. For background on<BR>&gt;&gt; Gen-ART, please see the FAQ at<BR>&gt;&gt=
; &lt;<A href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" t=
arget=3D_blank>http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</A>&=
gt;.<BR>&gt;&gt; <BR>&gt;&gt; Please resolve these comments along with any =
other Last Call comments<BR>&gt;&gt; you may receive.<BR>&gt;&gt; <BR>&gt;&=
gt; Document: draft-ietf-sidr-algorithm-agility-09<BR>&gt;&gt; Reviewer: Da=
vid L. Black<BR>&gt;&gt; Review Date: December 28, 2012<BR>&gt;&gt; IETF LC=
 End Date: December 14, 2012<BR>&gt;&gt; <BR>&gt;&gt; Summary:<BR>&gt;&gt; =
<BR>&gt;&gt; This draft is on the right track but has open issues, describe=
d in the review.<BR>&gt;&gt; <BR>&gt;&gt; I apologize for the tardy arrival=
 of this review after the end of IETF Last<BR>&gt;&gt; Call for this draft =
- the last few months have been a rather busy time for me.<BR>&gt;&gt; <BR>=
&gt;&gt; This draft specifies the algorithm transition process for RPKI, wh=
ich<BR>&gt;&gt; entails coordinated issuance of new certificates and other =
signed products<BR>&gt;&gt; across the collection of RPKI CAs in a fashion =
that ensures that at least<BR>&gt;&gt; one set of signed products is usable=
 at all times.<BR>&gt;&gt; <BR>&gt;&gt; The draft is generally well-written=
 and clear, but has an unfortunate<BR>&gt;&gt; nomenclature change problem =
that is the primary open issue[*].<BR>&gt;&gt; <BR>&gt;&gt; Major issues:<B=
R>&gt;&gt; <BR>&gt;&gt; [*] Section 4.7 changes the meaning of the algorith=
m suite names (A, B<BR>&gt;&gt; and C) from prior sections.&nbsp; This also=
 affects Sections 6 and 7.<BR>&gt;&gt; I have classified this as a major is=
sue as I believe it introduces<BR>&gt;&gt; severe lack of clarity (and pote=
ntial ambiguity) into the following<BR>&gt;&gt; two paragraphs in Section 7=
:<BR>&gt;&gt; <BR>&gt;&gt;&nbsp;&nbsp; During Phase 1, a CA that revokes a =
certificate under Suite A SHOULD<BR>&gt;&gt;&nbsp;&nbsp; revoke the corresp=
onding certificate under Suite B, if that<BR>&gt;&gt;&nbsp;&nbsp; certifica=
te exists.&nbsp; During Phase 4, a CA that revokes a certificate<BR>&gt;&gt=
;&nbsp;&nbsp; under Suite A SHOULD revoke the corresponding certificate und=
er Suite<BR>&gt;&gt;&nbsp;&nbsp; C, if that certificate exists.<BR>&gt;&gt;=
 <BR>&gt;&gt;&nbsp;&nbsp; During Phase 1, a CA may revoke certificates unde=
r Suite B without<BR>&gt;&gt;&nbsp;&nbsp; revoking them under Suite A, sinc=
e the Suite B products are for test<BR>&gt;&gt;&nbsp;&nbsp; purposes.&nbsp;=
 During Phase 4 a CA may revoke certificates issued under<BR>&gt;&gt;&nbsp;=
&nbsp; Suite C without revoking them under Suite A, since Suite C products<=
BR>&gt;&gt;&nbsp;&nbsp; are being deprecated.<BR>&gt;&gt; <BR>&gt;&gt; Desp=
ite the use of three letters (A, B and C), there are only two<BR>&gt;&gt; a=
lgorithm suites involved, and different instances of Suite A refer to<BR>&g=
t;&gt; different algorithm suites.&nbsp; In each paragraph, the first insta=
nce of<BR>&gt;&gt; "Suite A" refers to the same algorithm suite as "Suite C=
", and the<BR>&gt;&gt; second instance of "Suite A" refers to the same algo=
rithm suite<BR>&gt;&gt; as "Suite B".<BR>&gt;&gt; <BR>&gt;&gt; It would be =
much better and clearer to not change the meaning of the<BR>&gt;&gt; algori=
thm suite names until the EOL date. In addition, this change<BR>&gt;&gt; sh=
ould enable removal of the Suite C concept from this draft.&nbsp; I<BR>&gt;=
&gt; strongly recommend removing the Suite C concept, as the C-A-B<BR>&gt;&=
gt; chronological order of suite introduction dates seems counter-intuitive=
.<BR>&gt;&gt; <BR>&gt;&gt; Minor issues:<BR>&gt;&gt; <BR>&gt;&gt; Starting =
in Section 4.3.1, there are a number of uses of "will be"<BR>&gt;&gt; (futu=
re tense) in the milestone and phase descriptions.&nbsp; All of<BR>&gt;&gt;=
 these uses of "will be" should be reviewed to determine whether<BR>&gt;&gt=
; "MUST be" is appropriate, e.g., as appears to be the case for<BR>&gt;&gt;=
 this sentence in 4.3.1:<BR>&gt;&gt; <BR>&gt;&gt;&nbsp;&nbsp; Additionally,=
 the new algorithm transition timeline document will be<BR>&gt;&gt;&nbsp;&n=
bsp; published with the following information:<BR>&gt;&gt; <BR>&gt;&gt; Whe=
n "MUST be" is not appropriate, present tense (i.e., "is") is<BR>&gt;&gt; p=
referable.<BR>&gt;&gt; <BR>&gt;&gt; Nits/editorial:<BR>&gt;&gt; <BR>&gt;&gt=
; Abstract: The following two sentences don't quite line up:<BR>&gt;&gt; <B=
R>&gt;&gt;&nbsp;&nbsp; The process<BR>&gt;&gt;&nbsp;&nbsp; is expected to b=
e completed in a time scale of months or years.<BR>&gt;&gt;&nbsp;&nbsp; Con=
sequently, no emergency transition is specified.<BR>&gt;&gt; <BR>&gt;&gt; A=
lso, section 4.2 indicates that a multi-year transition timeframe<BR>&gt;&g=
t; is expected, which suggests that "months" is not appropriate in<BR>&gt;&=
gt; the abstract.&nbsp; Suggested rephrasing:<BR>&gt;&gt; <BR>&gt;&gt;&nbsp=
;&nbsp; The time available to complete the transition process<BR>&gt;&gt;&n=
bsp;&nbsp; is expected to be several years.<BR>&gt;&gt;&nbsp;&nbsp; Consequ=
ently, no emergency transition process is specified.<BR>&gt;&gt; <BR>&gt;&g=
t; Section 2. Introduction: The first sentence in the last paragraph<BR>&gt=
;&gt; mentions a forthcoming BCP on transition timetable.&nbsp; The rest of=
<BR>&gt;&gt; that paragraph implies that the BCP is for a single transition=
, as<BR>&gt;&gt; opposed to being a BCP for transitions in general.&nbsp; I=
t would be<BR>&gt;&gt; helpful to clarify that at the start of the paragrap=
h, e.g.,<BR>&gt;&gt; by adding "For each algorithm transition," to the star=
t of the<BR>&gt;&gt; paragraph.<BR>&gt;&gt; <BR>&gt;&gt; Section 3 Definiti=
ons: Is there any concern about possible<BR>&gt;&gt; confusion of the use o=
f "Suite B" in this draft with NSA Suite B?<BR>&gt;&gt; The draft is clear =
on what Suite B means for RPKI, but I suspect<BR>&gt;&gt; that RPKI Suite B=
 and NSA Suite B are unlikely to match, if ever.<BR>&gt;&gt; <BR>&gt;&gt; D=
escribing Phase 0 as both the steady state of the RPKI and the first<BR>&gt=
;&gt; phase of transition is confusing (e.g., in 4.3).&nbsp; It would be cl=
earer<BR>&gt;&gt; if Phase 0 began with publication of the updated RPKI alg=
orithm<BR>&gt;&gt; document (Milestone 1) and that the activities that are =
unchanged<BR>&gt;&gt; from steady state were described as not changing in p=
hase 0.<BR>&gt;&gt; <BR>&gt;&gt; Starting near the end of section 4.3, the =
three characters<BR>&gt;&gt; |-&gt; are used in figures to represent an RPK=
I hierarchy relationship;<BR>&gt;&gt; that relationship should be defined a=
nd/or explained before it is used.<BR>&gt;&gt; For clarity, I'd suggest swa=
pping the order of the two paragraphs<BR>&gt;&gt; above that figure in 4.3 =
and making the following change at the end<BR>&gt;&gt; of the paragraph tha=
t is moved down (addition of the word<BR>&gt;&gt; "certificate" is the impo=
rtant change):<BR>&gt;&gt; <BR>&gt;&gt; OLD<BR>&gt;&gt;&nbsp;&nbsp; and sho=
ws the relationship between three CAs (X, Y, and Z) that form<BR>&gt;&gt;&n=
bsp;&nbsp; a chain.<BR>&gt;&gt; NEW<BR>&gt;&gt;&nbsp;&nbsp; and shows the r=
elationships among the three CAs (X, Y, and Z)<BR>&gt;&gt;&nbsp;&nbsp; that=
 participate in a certificate chain.<BR>&gt;&gt; <BR>&gt;&gt; Subsequent us=
es of |-&gt; seemed clear to me.<BR>&gt;&gt; <BR>&gt;&gt; Section 4.5 Phase=
 2 says that Suite B product SHOULD be stored at<BR>&gt;&gt; independent pu=
blication points, but does not make it clear that this<BR>&gt;&gt; recommen=
dation applies beyond phase 2.&nbsp; I suggest adding text to<BR>&gt;&gt; m=
ake that clear - a reference to Section 9 (which is clear about<BR>&gt;&gt;=
 this) may be useful as part of that text.<BR>&gt;&gt; <BR>&gt;&gt; In Sect=
ion 6, please expand the ROA acronym on first use and consider<BR>&gt;&gt; =
whether it should be defined in Section 3.&nbsp; I'm also assuming that the=
<BR>&gt;&gt; ASN acronym is intended to refer to ASN.1 content; if not, tha=
t<BR>&gt;&gt; acronym also needs attention.<BR>&gt;&gt; <BR>&gt;&gt; idnits=
 2.12.13 found a couple of minor nits:<BR>&gt;&gt; <BR>&gt;&gt;&nbsp; ** Th=
ere is 1 instance of too long lines in the document, the longest one<BR>&gt=
;&gt;&nbsp;&nbsp;&nbsp;&nbsp; being 23 characters in excess of 72.<BR>&gt;&=
gt; <BR>&gt;&gt;&nbsp; =3D=3D The document seems to use 'NOT RECOMMENDED' a=
s an RFC 2119 keyword, but<BR>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; does not inc=
lude the phrase in its RFC 2119 key words list.<BR>&gt;&gt; <BR>&gt;&gt; Th=
anks,<BR>&gt;&gt; --David<BR>&gt;&gt; -------------------------------------=
---------------<BR>&gt;&gt; David L. Black, Distinguished Engineer<BR>&gt;&=
gt; EMC Corporation, 176 South St., Hopkinton, MA&nbsp; 01748<BR>&gt;&gt; +=
1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; FAX: +1 (508) 293-7786<BR>&gt;&gt; david.black@emc.com&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile: +1 (978) 394-7754<BR>&gt;&gt; -=
---------------------------------------------------<BR>&gt; <BR><BR><BR></D=
IV></FONT></BODY></HTML>

--_000_6BE9E0916BD84D6C941A7A50128A0773mimectl_--

From miguel.a.garcia@ericsson.com  Mon Feb  4 00:24:50 2013
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 B6A5E21F87D9 for <gen-art@ietfa.amsl.com>; Mon,  4 Feb 2013 00:24:50 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wG2n5DONvNF3 for <gen-art@ietfa.amsl.com>; Mon,  4 Feb 2013 00:24:49 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id C537421F87D7 for <gen-art@ietf.org>; Mon,  4 Feb 2013 00:24:48 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-f0-510f704f2c42
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id C4.0E.10459.F407F015; Mon,  4 Feb 2013 09:24:47 +0100 (CET)
Received: from [159.107.24.210] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.279.1; Mon, 4 Feb 2013 09:24:46 +0100
Message-ID: <510F704D.4090109@ericsson.com>
Date: Mon, 4 Feb 2013 09:24:45 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: davids@iit.edu, "\"Vijay K. Gurbani\" " <vkg@bell-labs.com>,  sporetsky@allot.com, Al Morton <acmorton@att.com>,  bmwg-chairs@tools.ietf.org, Ronald Bonica <rbonica@juniper.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFLMWRmVeSWpSXmKPExsUyM+Jvra5/AX+gwflr4hZbj01ktJi6vI3N 4ua+BWwWV199ZrE48N3BonXaVSaLhjVyDuwe7899Y/Z42T+H0aPvsovHkiU/mTz2333C5HG9 6Sq7x5fLn9kC2KO4bFJSczLLUov07RK4Ml692s9S8E6wYuvqCewNjN18XYycHBICJhKf2l6x Q9hiEhfurWcDsYUETjJKTG4QhbBXM0p8meIFYvMKaEssfvmHsYuRg4NFQEViVzNYOZuAuUTr xo1gY0QFoiTeX21ihigXlDg58wlLFyMXh4jATkaJN7uPMIEkmAX0JY782Q1mCwvYSDy9PJsR Im4rcWHOdRYIW15i+9s5zBA3aEpMvrmUeQIj/ywkc2chaZmFpGUBI/MqRvbcxMyc9HLDTYzA 8D245bfuDsZT50QOMUpzsCiJ84a5XggQEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwBhjVn81 9kfxxRVuuz97fNG+Ziai+i6+vTfqvMoTS+6KDK5ld/nzTs/+HDk3SuivdnsnS9WJWW6rs+ZZ WSaYXdtZ4+ppyf3RupnNPvfu1uxE1qLTHPOWnT0W1C/uyuFrcu/4qnWtW3qupuRVaeZsWPmA /+pW+T+X7txm2cVr9+HLeWv9vTs58pRYijMSDbWYi4oTAV6uzSItAgAA
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-bmwg-sip-bench-meth-08
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 Feb 2013 08:24:50 -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-bmwg-sip-bench-meth-08
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 2013-04-02
IETF LC End Date: 2013-01-30

Summary: The document is on track for publication as an Informational 
RFC, but has some issues that should be addressed before publication.

Major issues: none

Minor issues:

- Please expand acronyms at first usage. In particular, I didn't find a 
description of what "IM" is. Are you referring to Instant Messaging?

- Continuing with the previous one, now on Section 6.13. If you refer to 
Instant Messaging, then it is not clear to to me if you are benchmarking 
the one-shot Instant Message produced by the SIP MESSAGE method or if you 
are benchmarking the session-based Instant Messaging created with SIP and 
instantiated with MSRP. Please clarify what you are benchmarking and 
please add a reference to an RFC that defines the IM that you are 
benchmarking.



Nits/editorial comments:

- General: to avoid confusion, the text should add reference to other 
protocols when they are mentioned in the text. This includes: RTP, SRTP, 
perhaps event TCP and UDP, although these two should be clear for everyone.

- Section 4.1 The text says:

    Test cases may be performed with any transport protocol supported by
    SIP.  This includes, but is not limited to, SIP TCP, SIP UDP, and
    TLS.

   My comment: SIP TCP and SIP UDP are not transport protocols. TCP and 
UDP are transport protocols.


- Section 4.4. The text says:

    The test cases specified in this document provide SIP performance
    independent of the protocol used for the media stream.  Any media
    protocol supported by SIP may be used.  This includes, but is not
    limited to, RTP, RTSP, and SRTP...


   My comment: As far as I know, RTSP, specified in RFC 2326. is NOT a 
media protocol, and SIP is not intended to establish RTSP sessions.



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


From housley@vigilsec.com  Mon Feb  4 11:01:46 2013
Return-Path: <housley@vigilsec.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 0E30221F8959 for <gen-art@ietfa.amsl.com>; Mon,  4 Feb 2013 11:01:46 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pS4BVG0dwwIn for <gen-art@ietfa.amsl.com>; Mon,  4 Feb 2013 11:01:45 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7508121F894D for <gen-art@ietf.org>; Mon,  4 Feb 2013 11:01:45 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id AF00F9A4011; Mon,  4 Feb 2013 14:01:57 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id PobOgIbodX3W; Mon,  4 Feb 2013 14:01:33 -0500 (EST)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id C58159A4008; Mon,  4 Feb 2013 14:01:56 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4FD37E36.9080203@isode.com>
Date: Mon, 4 Feb 2013 14:01:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D3D42C39-041A-4DB1-8730-A9A1143A2209@vigilsec.com>
References: <4FD37E36.9080203@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1085)
Cc: draft-ietf-geopriv-dhcp-lbyr-uri-option.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>
Subject: Re: [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: Mon, 04 Feb 2013 19:01:46 -0000

Alexey:

I have not seen a reply to this review.  Are your concerns resolved in =
the current version?

Russ

On Jun 9, 2012, at 12:47 PM, Alexey Melnikov 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>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> 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)
>=20
> Summary: This document is nearly ready for publication as a Proposed =
Standard.
>=20
> Major issues: None
>=20
> Minor issues:
>=20
> 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.
>=20
> In Section 2.3: LuriType =3D1 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).
>=20
> LuriType=3D2: in network byte order?
>=20
> In Section 3.2: "data:" URI needs an Informative reference (RFC 2397).
>=20
> In Section 3.3: all media types mentioned (two?) need Normative =
references.
>=20
>=20
> Nits/editorial comments:
>=20
> In Section 3, 2nd to the last para: s/deference/dereference ?
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From christer.holmberg@ericsson.com  Mon Feb  4 16:55:04 2013
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 DD18221F8B64 for <gen-art@ietfa.amsl.com>; Mon,  4 Feb 2013 16:55:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.224
X-Spam-Level: 
X-Spam-Status: No, score=-6.224 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iVhcnj7RP3fJ for <gen-art@ietfa.amsl.com>; Mon,  4 Feb 2013 16:55:04 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id A89F821F8B2E for <gen-art@ietf.org>; Mon,  4 Feb 2013 16:55:03 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-89-511058665702
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 23.F1.10459.66850115; Tue,  5 Feb 2013 01:55:02 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.195]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.02.0318.004; Tue, 5 Feb 2013 01:55:02 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-shafranovich-mime-sql-03
Thread-Index: Ac4DOuPMXiNkMSIJTBOr80jWpqiZTg==
Date: Tue, 5 Feb 2013 00:55:01 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B0D3B85@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM+JvrW5ahECgwabVqhZzFnpbXH31mcWB yWPJkp9MHl8uf2YLYIrisklJzcksSy3St0vgyrh5u4214CBbxYmJK5gaGO+zdDFyckgImEg8 PbSDEcIWk7hwbz1bFyMXh5DAIUaJzecOs0M4ixklvvedYu5i5OBgE7CQ6P6nDdIgIqApMXfF WyYQm1kgXeLe8QOsILYwUMnrC/vYIWpsJebOusYMYetJ7OueCVbPIqAi8ebJBTYQm1fAW+Jx RzdYPSPQEd9PrYGaKS5x68l8JojjBCSW7DnPDGGLSrx8/I8VwlaU+PhqHyNEvY7Egt2f2CBs bYllC18zQ8wXlDg58wnLBEaRWUjGzkLSMgtJyywkLQsYWVYxsucmZuaklxtuYgQG/MEtv3V3 MJ46J3KIUZqDRUmcN8z1QoCQQHpiSWp2ampBalF8UWlOavEhRiYOTqkGxoSSp4W9Ag/m5Qhm dPhYJT6yurZYZq/C9jXfGrfcidvztCG+2y/Byfjpmq05Jb+dU9f7pm83+XFF3tAnREmetydd m6ui1so83ezcCcN3Va9n5/YwLPMwn9gjyr2j497PjrkiKefUZVgmHJt/+up0TSvBn3n8HPVn lnSbaL3jefJi7UFBxlsTlFiKMxINtZiLihMBT8oxeUYCAAA=
Cc: "draft-shafranovich-mime-sql.all@tools.ietf.org" <draft-shafranovich-mime-sql.all@tools.ietf.org>
Subject: [Gen-art] Genart review of draft-shafranovich-mime-sql-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: Tue, 05 Feb 2013 00:55:05 -0000

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>

Document:                    draft-shafranovich-mime-sql-03.txt

Reviewer:                     Christer Holmberg

Review Date:                 5 Feb 2013

IETF LC End Date:        20 Feb 2013

IETF Telechat Date:       21 Feb 2013

Summary:  The draft is well written, with a couple of minor editorial comme=
nts (see below), and is ready for publication.
=20
Major Issues: None
=20
Minor Issues: None

Editorial nits: None

Q_ED_1: In section 2, I suggest to remove "which will be submitted to IANA =
after approval of this document.".

Q_ED_2: In section 3, I suggest to remove "After approval,".=20

Best regards,

Christer

=20
=20

From suresh.krishnan@ericsson.com  Mon Feb  4 21:08:43 2013
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 7437921F8915 for <gen-art@ietfa.amsl.com>; Mon,  4 Feb 2013 21:08:43 -0800 (PST)
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=1.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gO8v8z8iffmL for <gen-art@ietfa.amsl.com>; Mon,  4 Feb 2013 21:08:42 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id B00EC21F88E1 for <gen-art@ietf.org>; Mon,  4 Feb 2013 21:08:42 -0800 (PST)
X-AuditID: c6180641-b7f926d000000e79-a9-511093d9c755
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 79.2C.03705.9D390115; Tue,  5 Feb 2013 06:08:41 +0100 (CET)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC004.ericsson.se (147.117.188.84) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 5 Feb 2013 00:08:41 -0500
Received: from [164.48.125.54] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 5 Feb 2013 00:08:40 -0500
Message-ID: <51109339.2030502@ericsson.com>
Date: Tue, 5 Feb 2013 00:06:01 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: <draft-ietf-rtgwg-ipfrr-notvia-addresses.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJJMWRmVeSWpSXmKPExsUyuXRPiO7NyQKBBndv2ljs+dHEanH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvjYud+loI3PBVvf95ibWDcwNXFyMkhIWAi MWHxJnYIW0ziwr31bF2MXBxCAkcYJWbe2MYI4exmlNj7+S1UZgujxITVO1i7GDk4eAW0JZac rQPpZhFQkZg07TwziM0GNHXDzs9MILaoQJhE7+tzjCA2r4CgxMmZT1hAbBGBQolNjfPB6oUF giQ2L9jJCDJSQkBcYs0bDpAws4CexJSrLYwQtrzE9rdzwMqFBDQltq75zjqBUWAWkqmzkLTM QtKygJF5FSNHaXFqWW66keEmRmDwHZNgc9zBuOCT5SFGaQ4WJXHeUNcLAUIC6YklqdmpqQWp RfFFpTmpxYcYmTg4pRoYK7i2LF36/RtX64y/79Yc8RaQdi15+GBB9s/MIJ5cqRUsQouMmFq/ OccweZSsKfjik+Bi/3vvLZPdtgJrkrpv6ZkdXDPHw9490eDP+mc+SZ9uPekUWmYxo6X1kP8p MaFPvEwvL189cY0562rznVMNRsmOb169mrx8Xsp55vBbB3Ifnp8YqbfxuxJLcUaioRZzUXEi AOlE2DsMAgAA
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-rtgwg-ipfrr-notvia-addresses-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: Tue, 05 Feb 2013 05:08:43 -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-rtgwg-ipfrr-notvia-addresses-10.txt
Reviewer: Suresh Krishnan
Review Date: 2013/02/04
IESG Telechat date: 2013/02/07

Summary: This document is almost ready for publication as an
Informational RFC but I have some comments you may wish to address.

Minor
=====

* Section 5.4

It is not clear how the next-next-hop for a DR is calculated if the
router P uses ECMP to reach the DR (i.e. there are potentially multiple
next-next-hops). Can you please clarify?

* MTU considerations

There is no discussion of the MTU issues that come up due to
encapsulation and some form of requirement for the repair endpoint to
perform path MTU discovery. This is especially important for IPv6 endpoints.

* Security Considerations

- The first sentence talks about using this mechanism disguising
delivery of a packet without talking about further details. Are you
talking about one of the issues discussed in Section 2 of RFC6169? If
so, a pointer could be useful.

- What does the term private address mean in the context of this
section? Does it mean a RFC1918 or RFC4193 address (the properties
requested seem to imply these)? If so, it might be good to make this
explicit.

Editorial
=========

* Section 1

s/based on the concept tunnelling/based on the concept of tunnelling/

Thanks
Suresh


From huawei.danli@huawei.com  Mon Feb  4 19:05:45 2013
Return-Path: <huawei.danli@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 AF43C21F88EA; Mon,  4 Feb 2013 19:05:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.732
X-Spam-Level: *
X-Spam-Status: No, score=1.732 tagged_above=-999 required=5 tests=[AWL=-1.056,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339,  MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5gHeUWnxkkO; Mon,  4 Feb 2013 19:05:45 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id ACD2821F88E8; Mon,  4 Feb 2013 19:05:43 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APK98078; Tue, 05 Feb 2013 03:05:42 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Feb 2013 03:04:43 +0000
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Feb 2013 03:05:38 +0000
Received: from szxeml555-mbx.china.huawei.com ([169.254.1.229]) by szxeml403-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.007; Tue, 5 Feb 2013 11:05:35 +0800
From: "Lidan (Dan)" <huawei.danli@huawei.com>
To: Richard Barnes <rbarnes@bbn.com>, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-ccamp-lmp-behavior-negotiation-10
Thread-Index: AQHOAkKfFPU9gjEKO0O3gq+ZfCNfU5hqkSYw
Date: Tue, 5 Feb 2013 03:05:34 +0000
Message-ID: <92A1F6CF27D54D4DA5364E59D892A02A388518AA@szxeml555-mbx.china.huawei.com>
References: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com>
In-Reply-To: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.73.151]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 04 Feb 2013 23:54:19 -0800
Cc: "draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org" <draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] =?gb2312?b?tPC4tDogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0?= =?gb2312?b?Zi1jY2FtcC1sbXAtYmVoYXZpb3ItbmVnb3RpYXRpb24tMTA=?=
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 Feb 2013 03:05:45 -0000

SGkgUmljaGFyZCwNCg0KVGhhbmtzIGZvciB0aGUgcmV2aWV3IG9mIHRoaXMgZHJhZnQhDQoNCj4g
U2VjdGlvbiAyLjEuICBXb3VsZCBiZSBoZWxwZnVsIHRvIGVpdGhlciBpbmNsdWRlIHRoZSBvbGQg
Zm9ybWF0cyBhbmQvb3Igc2F5IGV4cGxpY2l0bHkgd2hhdCBpcyBjaGFuZ2luZy4NCkFkZGVkIHRo
ZSBvcmlnaW5hbCBmb3JtYXQgb2YgQ29uZmlnLCBDb25maWdBY2sgYW5kIENvbmZpZ05hY2sgbWVz
c2FnZXMgd2hpY2ggYXJlIGRlZmluZWQgaW4gUkZDNDIwNC4NCg0KPiBTZWN0aW9uIDIuMi4gIA0K
PiAiTm9kZXMgd2hpY2ggc3VwcG9ydCIgLT4gIm5vZGVzIHRoYXQgc3VwcG9ydCIgIA0KPiAiT3Jk
ZXJpbmcgb2YgQ09ORklHIG9iamVjdHMiIC0+ICIuLi4gV2l0aCBkaWZmZXJlbnQgQy10eXBlIHZh
bHVlcyINClVwZGF0ZWQgdGhlIHRleHQgYXMgc3VnZ2VzdGVkLg0KDQo+IFNlY3Rpb24gMy4xLk1C
Wi4gTWlnaHQgaGVscCB0byBjbGFyaWZ5IHRoYXQgdGhpcyBtZWFucyB0aGF0IHRoZSBudW1iZXIg
b2YgYml0cyBNVVNUIGJlIGEgbXVsdGlwbGUgb2YgMzIuIChJIGdvdCBhIGxpdHRsZSBjb25mdXNl
ZCBiZXR3ZWVuIGJpdHMgYW5kIGJ5dGVzIGhlcmUuKQ0KT0xEOg0KVGhlIHJlbWFpbmluZyBiaXRz
IGluIHRoZSBmbGFncyBmaWVsZCBNVVNUIGJlIHNldCB0byB6ZXJvICgwKS4gVGhlIG51bWJlciBv
ZiBiaXRzIHByZXNlbnQgaXMgYmFzZWQgb24gdGhlIExlbmd0aCBmaWVsZCBvZiB0aGUgTE1QIG9i
amVjdCBoZWFkZXIgYW5kIE1VU1QgaW5jbHVkZSBlbm91Z2ggYml0cyBzbyB0aGUgTGVuZ3RoIGZp
ZWxkIE1VU1QgYmUgYXQgbGVhc3QgOCwgYW5kIE1VU1QgYmUgYSBtdWx0aXBsZSBvZiA0Lg0KTkVX
Og0KVGhlIHJlbWFpbmluZyBiaXRzIGluIHRoZSBmbGFncyBmaWVsZCBNVVNUIGJlIHNldCB0byB6
ZXJvICgwKS4gVGhlIG51bWJlciBvZiBiaXRzIHByZXNlbnQgaXMgYmFzZWQgb24gdGhlIExlbmd0
aCBmaWVsZCBvZiB0aGUgTE1QIG9iamVjdCBoZWFkZXIgYW5kIE1VU1QgaW5jbHVkZSBlbm91Z2gg
Yml0cyBzbyB0aGUgTGVuZ3RoIGZpZWxkIE1VU1QgYmUgYXQgbGVhc3QgOCwgYW5kIHRoZSBudW1i
ZXIgb2YgYml0cyBNVVNUIGJlIGEgbXVsdGlwbGUgb2YgMzIuDQoNCj4gU2VjdGlvbiA0LiAiTGlr
ZWx5Ig0KPiBJcyBpdCBwb3NzaWJsZSBmb3IgYSA0MjA0LWNvbXBsaWFudCBpbXBsZW1lbnRhdGlv
biB0byBub3QgZG8gb25lIG9mIHRoZXNlPyAgSWYgc28gdGhlbiByZW1vdmUgImxpa2VseSIuICBJ
ZiBub3QsIHRoZW4gd2h5IGhhcHBlbnMgb24gdGhlIGV4Y2VwdGlvbmFsIGNhc2U/DQpUaGVyZSBp
cyBubyBvdGhlciBleGNlcHRpb24sIHNvIEkganVzdCByZW1vdmVkIHRoZSB3b3JkICJsaWtlbHki
Lg0KDQpJIHdpbGwgaG9sZCB0aGUgbmV3IHZlcnNpb24gdW50aWwgSSBnZXQgdGhlIGZ1cnRoZXIg
aW5zdHJ1Y3Rpb24gZnJvbSBteSBkb2N1bWVudCBzaGVwaGVyZCBvciBBRC4NCg0KQmVzdCByZWdh
cmRzLA0KDQpEYW4NCg0KDQotLS0tLdPKvP7Urbz+LS0tLS0NCreivP7IyzogUmljaGFyZCBCYXJu
ZXMgW21haWx0bzpyYmFybmVzQGJibi5jb21dIA0Kt6LLzcqxvOQ6IDIwMTPE6jLUwjTI1SAzOjE0
DQrK1bz+yMs6IGlldGZAaWV0Zi5vcmc7IFRoZSBJRVNHDQqzrcvNOiBkcmFmdC1pZXRmLWNjYW1w
LWxtcC1iZWhhdmlvci1uZWdvdGlhdGlvbkB0b29scy5pZXRmLm9yZzsgZ2VuLWFydEBpZXRmLm9y
Zw0K1vfM4jogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2FtcC1sbXAtYmVoYXZpb3It
bmVnb3RpYXRpb24tMTANCg0KSSBoYXZlIGJlZW4gc2VsZWN0ZWQgYXMgdGhlIEdlbmVyYWwgQXJl
YSBSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQgKGZvciBiYWNr
Z3JvdW5kIG9uIEdlbi1BUlQsIHBsZWFzZSBzZWVodHRwOi8vd3d3LmFsdmVzdHJhbmQubm8vaWV0
Zi9nZW4vYXJ0L2dlbi1hcnQtRkFRLmh0bWwpLg0KDQpQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9u
IGZyb20geW91ciBkb2N1bWVudCBzaGVwaGVyZCBvciBBRCBiZWZvcmUgcG9zdGluZyBhIG5ldyB2
ZXJzaW9uIG9mIHRoZSBkcmFmdC4NCg0KRG9jdW1lbnQ6IGRyYWZ0LWlldGYtY2NhbXAtbG1wLWJl
aGF2aW9yLW5lZ290aWF0aW9uLTEwDQpSZXZpZXdlcjogUmljaGFyZCBCYXJuZXMNClJldmlldyBE
YXRlOiAyMDEzLTAyLTAyDQpJRVRGIExDIEVuZCBEYXRlOiAyMDEyLTAxLTIxDQpJRVNHIFRlbGVj
aGF0IGRhdGU6IDIwMTItMDItMDcNCg0KU3VtbWFyeTogIFJlYWR5LCB3aXRoIGEgY291cGxlIG9m
IG1pbm9yIHF1ZXN0aW9ucyAvIGNsYXJpZmljYXRpb25zLg0KDQpDb21tZW50Og0KDQpPdmVyYWxs
LCB0aGlzIGRvY3VtZW50IHNlZW1zIHZlcnkgY2xlYXIgYW5kIHJlYWRhYmxlLiAgVGhhbmtzISAg
VGhlIG9uZSBjb25jZXJuIEkgaGF2ZSBpcyBvdmVyIHRoZSB1c2Ugb2YgImxpa2VseSIgaW4gdGhl
IGRpc2N1c3Npb24gb2YgYmFja3dhcmQgY29tcGF0aWJpbGl0eTsgSSB3b3VsZCBsaWtlIHRvIHNl
ZSBtb3JlIHByZWNpc2UgbGFuZ3VhZ2UgdGhlcmUuDQoNClNlY3Rpb24gMi4xLiAgV291bGQgYmUg
aGVscGZ1bCB0byBlaXRoZXIgaW5jbHVkZSB0aGUgb2xkIGZvcm1hdHMgYW5kL29yIHNheSBleHBs
aWNpdGx5IHdoYXQgaXMgY2hhbmdpbmcuIA0KDQpTZWN0aW9uIDIuMi4gIA0KIk5vZGVzIHdoaWNo
IHN1cHBvcnQiIC0+ICJub2RlcyB0aGF0IHN1cHBvcnQiICANCiJPcmRlcmluZyBvZiBDT05GSUcg
b2JqZWN0cyIgLT4gIi4uLiBXaXRoIGRpZmZlcmVudCBDLXR5cGUgdmFsdWVzIg0KDQpTZWN0aW9u
IDMuMS5NQlouIE1pZ2h0IGhlbHAgdG8gY2xhcmlmeSB0aGF0IHRoaXMgbWVhbnMgdGhhdCB0aGUg
bnVtYmVyIG9mIGJpdHMgTVVTVCBiZSBhIG11bHRpcGxlIG9mIDMyLiAoSSBnb3QgYSBsaXR0bGUg
Y29uZnVzZWQgYmV0d2VlbiBiaXRzIGFuZCBieXRlcyBoZXJlLikNCg0KU2VjdGlvbiA0LiAiTGlr
ZWx5Ig0KSXMgaXQgcG9zc2libGUgZm9yIGEgNDIwNC1jb21wbGlhbnQgaW1wbGVtZW50YXRpb24g
dG8gbm90IGRvIG9uZSBvZiB0aGVzZT8gIElmIHNvIHRoZW4gcmVtb3ZlICJsaWtlbHkiLiAgSWYg
bm90LCB0aGVuIHdoeSBoYXBwZW5zIG9uIHRoZSBleGNlcHRpb25hbCBjYXNlPw0K

From lberger@labn.net  Tue Feb  5 06:24:44 2013
Return-Path: <lberger@labn.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 3627021F88E8 for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 06:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.177
X-Spam-Level: 
X-Spam-Status: No, score=-98.177 tagged_above=-999 required=5 tests=[AWL=-2.873, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, SARE_SUB_ENC_GB2312=1.345, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ah6QHUuO4C-4 for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 06:24:43 -0800 (PST)
Received: from oproxy1-pub.bluehost.com (oproxy1-pub.bluehost.com [66.147.249.253]) by ietfa.amsl.com (Postfix) with SMTP id BA04821F88E5 for <gen-art@ietf.org>; Tue,  5 Feb 2013 06:24:43 -0800 (PST)
Received: (qmail 15246 invoked by uid 0); 5 Feb 2013 14:24:21 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy1.bluehost.com with SMTP; 5 Feb 2013 14:24:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=j2CE59lLdBV/ivgjzSltcmQgrZSSSXTMAxBRAcaaHnY=;  b=Ej9LlQlZoOa9MctnozsH7pPcQTFr0DLd+1p7bmolnwZArX7UCaKaGDseKPc/ANW7mkttu2LVn/4BmH69hoWxGkWG83FGvNvr3cs5w+9fW8LPuoHQwuOqJ97SHGktyy0T;
Received: from box313.bluehost.com ([69.89.31.113]:43566 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1U2jRd-0003uC-83; Tue, 05 Feb 2013 07:24:21 -0700
Message-ID: <51111613.7070300@labn.net>
Date: Tue, 05 Feb 2013 09:24:19 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Lidan (Dan)" <huawei.danli@huawei.com>, Richard Barnes <rbarnes@bbn.com>
References: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com> <92A1F6CF27D54D4DA5364E59D892A02A388518AA@szxeml555-mbx.china.huawei.com>
In-Reply-To: <92A1F6CF27D54D4DA5364E59D892A02A388518AA@szxeml555-mbx.china.huawei.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: "draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org" <draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] =?gb2312?b?tPC4tDogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0?= =?gb2312?b?Zi1jY2FtcC1sbXAtYmVoYXZpb3ItbmVnb3RpYXRpb24tMTA=?=
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 Feb 2013 14:24:44 -0000

Dan/Richard,
	

On 2/4/2013 10:05 PM, Lidan (Dan) wrote:
> Hi Richard,
> 
> Thanks for the review of this draft!
> 
>> Section 2.1.  Would be helpful to either include the old formats
>> and/or say explicitly what is changing.

> Added the original format of Config, ConfigAck and ConfigNack
> messages which are defined in RFC4204.
> 

I personally think it's a mistake to repeat definitions in non-bis RFCs.
 I think this increases the possibility of mistakes and confusion (e.g.,
when the text isn't copied properly or when the original document is
replaced).

My original thought was to propose text to follow Richard's suggestion
of explicitly saying what has changed, but I see such text is there at
the start of section 2:

   LMP Config, ConfigNack and ConfigAck messages are modified by this
   document to allow for the inclusion of multiple CONFIG objects. The
   Config and ConfigNack messages were only defined to carry one CONFIG
   object in [RFC4204]. The ConfigAck message, which was defined
   without carrying any CONFIG objects in [RFC4204], is modified to
   enable explicit identification of negotiated configuration
   parameters. The inclusion of CONFIG objects in ConfigAck messages is
   triggered by the use of the BehaviorConfig object (defined below) in
   a received Config message.

Richard,

Is this text sufficient?  Alternatively, this text can be moved to
immediately proceed the BNF.

Much thanks
Lou
(document co-author)

From lberger@labn.net  Tue Feb  5 06:53:58 2013
Return-Path: <lberger@labn.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 EF19921F88B4 for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 06:53:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.492
X-Spam-Level: 
X-Spam-Status: No, score=-101.492 tagged_above=-999 required=5 tests=[AWL=0.773, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKtH6rn+chHp for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 06:53:57 -0800 (PST)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id 369EF21F88B5 for <gen-art@ietf.org>; Tue,  5 Feb 2013 06:53:57 -0800 (PST)
Received: (qmail 20318 invoked by uid 0); 5 Feb 2013 14:53:31 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 5 Feb 2013 14:53:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=Zp/lg88axpdkqgMzJIPHgbhQmWfOAxKzzPMhW9VJ3l0=;  b=f+dvtRQio8Dzg27E2nABalxNQJdlAXTN24yXWc5Rj7+f69KplZG7BbSuI/iAX3nSk8+jCMMg4xZ68vSGtpmf2QLNOYzyJpFXgtzifjaoRuuKPbjKxTvJnMzi51mIuP0J;
Received: from box313.bluehost.com ([69.89.31.113]:48237 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1U2jtq-0003zi-Q2; Tue, 05 Feb 2013 07:53:31 -0700
Message-ID: <51111CE8.2060204@labn.net>
Date: Tue, 05 Feb 2013 09:53:28 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Richard Barnes <rbarnes@bbn.com>
References: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com>
In-Reply-To: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ccamp-lmp-behavior-negotiation-10
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 Feb 2013 14:53:58 -0000

Richard,
	Thank you for the review.  I have one additional question/response on
your comments:

On 2/3/2013 2:13 PM, Richard Barnes wrote:
> I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, please seehttp://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-ccamp-lmp-behavior-negotiation-10
> Reviewer: Richard Barnes
> Review Date: 2013-02-02
> IETF LC End Date: 2012-01-21
> IESG Telechat date: 2012-02-07
> 
> Summary:  Ready, with a couple of minor questions / clarifications.
> 
> Comment:
> 
> Overall, this document seems very clear and readable.  Thanks!  The one concern I have is over the use of "likely" in the discussion of backward compatibility; I would like to see more precise language there.
> 
> Section 2.1.  Would be helpful to either include the old formats and/or say explicitly what is changing. 
> 
> Section 2.2.  
> "Nodes which support" -> "nodes that support"  
> "Ordering of CONFIG objects" -> "... With different C-type values"
> 
> Section 3.1.MBZ. Might help to clarify that this means that the
> number of bits MUST be a multiple of 32. (I got a little confused
> between bits and bytes here.)
> 

I think you're right.  The current text can easily result in confision
between the size of the MBZ field and the setting of the length field
define in RFC4204.  It's probably best to just remove the reference to
the length field. How about this:

OLD
The number of bits present is based on the Length field of the LMP
object header and MUST include enough bits so the Length field MUST be
at least 8, and MUST be a multiple of 4.

NEW
This field MUST be sized to ensure 32 bit alignment of the object.

Lou
(co-author)

> Section 4. "Likely"
> Is it possible for a 4204-compliant implementation to not do one of these?  If so then remove "likely".  If not, then why happens on the exceptional case?
> 
> 
> 

From rlb@ipv.sx  Tue Feb  5 07:08:59 2013
Return-Path: <rlb@ipv.sx>
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 C43B021F8919 for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 07:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z-zHJ2BT72YC for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 07:08:59 -0800 (PST)
Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176]) by ietfa.amsl.com (Postfix) with ESMTP id 81CBD21F88FB for <gen-art@ietf.org>; Tue,  5 Feb 2013 07:08:52 -0800 (PST)
Received: by mail-lb0-f176.google.com with SMTP id s4so305145lbc.35 for <gen-art@ietf.org>; Tue, 05 Feb 2013 07:08:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=A0UaT9ZPmbRhi/3wCO7S4Z5Du3GC46guabChV+BxHZc=; b=aRmfM52UCEA0oKR7hxdVJIv4ZPzHZuAGsoMTrIs9WDOP9qAtLnjFbg1bST7w+MNq8A EGhi929nXgxqxuH3hZoBroBK+I1x8SwfrQsZx8xRT/zo4BV/Arx+942Iy4NpNqyB9O1z gqfqvauvuCbMF9pa1jnG5UjFrDYFgis5odz340c7NJVw9SvblGMxacTM/5HxzgqxfaUG HpHi/8NEzUZRv444/rmkNGRLrrOj2lZ6JNoX2ekBs5/tScAxumYMlbghL1OhaPnswiTw ECOvFWmm6ABZrbbR1o15ruTpbxFzUrr+lB7N4iowRcENJ+J4s0DBg6Y5XIAW1TTua5XK h7HA==
MIME-Version: 1.0
X-Received: by 10.152.127.202 with SMTP id ni10mr23324677lab.6.1360076930915;  Tue, 05 Feb 2013 07:08:50 -0800 (PST)
Received: by 10.112.142.170 with HTTP; Tue, 5 Feb 2013 07:08:50 -0800 (PST)
X-Originating-IP: [155.212.214.60]
In-Reply-To: <51111613.7070300@labn.net>
References: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com> <92A1F6CF27D54D4DA5364E59D892A02A388518AA@szxeml555-mbx.china.huawei.com> <51111613.7070300@labn.net>
Date: Tue, 5 Feb 2013 10:08:50 -0500
Message-ID: <CAL02cgTosa9Y1R4UOyPXZAwOZ_X7KRrDEdJ3p98uGD3XHKaYsw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=f46d042c6aeb559dba04d4fb9641
X-Gm-Message-State: ALoCoQmQaGIKCovLBV6LvvzxLKV+0QmujQUgLzuJ2DLuKisdgvKeorDGxjaa9HJ7oEMGMvBGFCLP
X-Mailman-Approved-At: Tue, 05 Feb 2013 07:21:05 -0800
Cc: "draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org" <draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "Lidan \(Dan\)" <huawei.danli@huawei.com>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] =?utf-8?b?562U5aSNOiBHZW4tQVJUIHJldmlldyBvZiBkcmFmdC1p?= =?utf-8?q?etf-ccamp-lmp-behavior-negotiation-10?=
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 Feb 2013 15:09:00 -0000

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

Hey Lou,

That text looks fine to me!

--Richard


On Tue, Feb 5, 2013 at 9:24 AM, Lou Berger <lberger@labn.net> wrote:

> Dan/Richard,
>
>
> On 2/4/2013 10:05 PM, Lidan (Dan) wrote:
> > Hi Richard,
> >
> > Thanks for the review of this draft!
> >
> >> Section 2.1.  Would be helpful to either include the old formats
> >> and/or say explicitly what is changing.
>
> > Added the original format of Config, ConfigAck and ConfigNack
> > messages which are defined in RFC4204.
> >
>
> I personally think it's a mistake to repeat definitions in non-bis RFCs.
>  I think this increases the possibility of mistakes and confusion (e.g.,
> when the text isn't copied properly or when the original document is
> replaced).
>
> My original thought was to propose text to follow Richard's suggestion
> of explicitly saying what has changed, but I see such text is there at
> the start of section 2:
>
>    LMP Config, ConfigNack and ConfigAck messages are modified by this
>    document to allow for the inclusion of multiple CONFIG objects. The
>    Config and ConfigNack messages were only defined to carry one CONFIG
>    object in [RFC4204]. The ConfigAck message, which was defined
>    without carrying any CONFIG objects in [RFC4204], is modified to
>    enable explicit identification of negotiated configuration
>    parameters. The inclusion of CONFIG objects in ConfigAck messages is
>    triggered by the use of the BehaviorConfig object (defined below) in
>    a received Config message.
>
> Richard,
>
> Is this text sufficient?  Alternatively, this text can be moved to
> immediately proceed the BNF.
>
> Much thanks
> Lou
> (document co-author)
>

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

<div dir=3D"ltr">Hey Lou,<div><br></div><div>That text looks fine to me!</d=
iv><div><br></div><div style>--Richard</div></div><div class=3D"gmail_extra=
"><br><br><div class=3D"gmail_quote">On Tue, Feb 5, 2013 at 9:24 AM, Lou Be=
rger <span dir=3D"ltr">&lt;<a href=3D"mailto:lberger@labn.net" target=3D"_b=
lank">lberger@labn.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Dan/Richard,<br>
<div class=3D"im"><br>
<br>
On 2/4/2013 10:05 PM, Lidan (Dan) wrote:<br>
&gt; Hi Richard,<br>
&gt;<br>
&gt; Thanks for the review of this draft!<br>
&gt;<br>
&gt;&gt; Section 2.1. =A0Would be helpful to either include the old formats=
<br>
&gt;&gt; and/or say explicitly what is changing.<br>
<br>
&gt; Added the original format of Config, ConfigAck and ConfigNack<br>
&gt; messages which are defined in RFC4204.<br>
&gt;<br>
<br>
</div>I personally think it&#39;s a mistake to repeat definitions in non-bi=
s RFCs.<br>
=A0I think this increases the possibility of mistakes and confusion (e.g.,<=
br>
when the text isn&#39;t copied properly or when the original document is<br=
>
replaced).<br>
<br>
My original thought was to propose text to follow Richard&#39;s suggestion<=
br>
of explicitly saying what has changed, but I see such text is there at<br>
the start of section 2:<br>
<br>
=A0 =A0LMP Config, ConfigNack and ConfigAck messages are modified by this<b=
r>
=A0 =A0document to allow for the inclusion of multiple CONFIG objects. The<=
br>
=A0 =A0Config and ConfigNack messages were only defined to carry one CONFIG=
<br>
=A0 =A0object in [RFC4204]. The ConfigAck message, which was defined<br>
=A0 =A0without carrying any CONFIG objects in [RFC4204], is modified to<br>
=A0 =A0enable explicit identification of negotiated configuration<br>
=A0 =A0parameters. The inclusion of CONFIG objects in ConfigAck messages is=
<br>
=A0 =A0triggered by the use of the BehaviorConfig object (defined below) in=
<br>
=A0 =A0a received Config message.<br>
<br>
Richard,<br>
<br>
Is this text sufficient? =A0Alternatively, this text can be moved to<br>
immediately proceed the BNF.<br>
<br>
Much thanks<br>
Lou<br>
(document co-author)<br>
</blockquote></div><br></div>

--f46d042c6aeb559dba04d4fb9641--

From david.black@emc.com  Tue Feb  5 11:34:41 2013
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 E484E21F8651; Tue,  5 Feb 2013 11:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PLfQ4VOTfmAb; Tue,  5 Feb 2013 11:34:41 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 7868C21F85DB; Tue,  5 Feb 2013 11:34:39 -0800 (PST)
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 r15JYbrA032541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Feb 2013 14:34:37 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 5 Feb 2013 14:34:23 -0500
Received: from mxhub27.corp.emc.com (mxhub27.corp.emc.com [10.254.110.183]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r15JYNou021000; Tue, 5 Feb 2013 14:34:23 -0500
Received: from mx15a.corp.emc.com ([169.254.1.210]) by mxhub27.corp.emc.com ([10.254.110.183]) with mapi; Tue, 5 Feb 2013 14:34:23 -0500
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "nabil.n.bitar@verizon.com" <nabil.n.bitar@verizon.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Tue, 5 Feb 2013 14:34:22 -0500
Thread-Topic: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-07
Thread-Index: Ac1/QFqQF9gPSsZLRYeNSY3JGwq32iElzE2w
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7128800E87E@MX15A.corp.emc.com>
References: <7EB1738E-2545-4A33-B5C0-548630347568@mimectl>
In-Reply-To: <7EB1738E-2545-4A33-B5C0-548630347568@mimectl>
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_8D3D17ACE214DC429325B2B98F3AE7128800E87EMX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-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: Tue, 05 Feb 2013 19:34:42 -0000

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

The -07 version of this draft addresses all of the nits noted in the Gen-AR=
T
review of the -06 version.

This draft is ready for publication as a Proposed Standard RFC.

Thanks,
--David

From: Black, David
Sent: Monday, August 20, 2012 9:58 PM
To: dinmohan@hotmail.com; nabil.n.bitar@verizon.com; sajassi@cisco.com; gen=
-art@ietf.org
Cc: Black, David; pwe3@ietf.org; ietf@ietf.org
Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

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/GenArtfaq>.

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

Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
Reviewer: David L. Black
Review Date: August 20, 2012
IETF LC End Date: August 20, 2012

Summary:
This draft is basically ready for publication, but has nits that
should be fixed before publication.



This draft covers defect behavior for Ethernet pseudowires,

including defect state mapping and PE defect reporting behavior.

The draft is generally in good shape.  I found a few minor nits.



1) The draft uses a lot of acronyms - while each acronym appears to

be expanded on first use, an additional section near the start of the

draft listing all of them would be helpful.



2) There's a typo in the first paragraph of section 2:



     covers the following Ethernet OAM (Opertaions, Administration and



Opertaions -> Operations.



3) The following normative reference is incomplete - please add additional

information that will enable a reader to locate the referenced document:



     [MEF16] "Ethernet Local Management Interface", MEF16, January 2006.



4) idnits 2.12.13 did not like the pagination:



  =3D=3D The page length should not exceed 58 lines per page, but there was=
 22
     longer pages, the longest (page 1) being 61 lines

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black@emc.com<mailto:david.black@emc.com>        Mobile: +1 (978) 394=
-7754
----------------------------------------------------

--_000_8D3D17ACE214DC429325B2B98F3AE7128800E87EMX15Acorpemccom_
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: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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>The -07 version of t=
his draft addresses all of the nits noted in the Gen-ART<o:p></o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courie=
r New";color:black'>review of the -06 version.<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";col=
or:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>This draft is ready =
for publication as a Proposed Standard RFC.<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'><o:p>&nbsp;</o:p></span></p><div><div><p class=3DMsoNormal><span s=
tyle=3D'font-size:10.0pt;font-family:"Courier New";color:black'>Thanks,<br>=
--David</span><span style=3D'font-size:11.0pt;font-family:"Courier New";col=
or:black'><o:p></o:p></span></p></div></div><p class=3DMsoNormal><span styl=
e=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o=
:p></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;paddin=
g:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4D=
F 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Black, David <b=
r><b>Sent:</b> Monday, August 20, 2012 9:58 PM<br><b>To:</b> dinmohan@hotma=
il.com; nabil.n.bitar@verizon.com; sajassi@cisco.com; gen-art@ietf.org<br><=
b>Cc:</b> Black, David; pwe3@ietf.org; ietf@ietf.org<br><b>Subject:</b> Gen=
-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06<o:p></o:p></span></p></d=
iv></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNorma=
l><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>I =
am the assigned Gen-ART reviewer for this draft. For background on Gen-ART,=
 please<br>see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/ge=
n/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/ge=
n/trac/wiki/GenArtfaq</a>&gt;.<br><br>Please resolve these comments along w=
ith any other Last Call comments you may receive.<br><br>Document: </span><=
span lang=3DEN style=3D'font-size:10.0pt;font-family:"Courier New";color:bl=
ack'>draft-ietf-pwe3-mpls-eth-oam-iwk-06</span><o:p></o:p></p></div><div><p=
 class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New=
";color:black'>Reviewer: David L. Black<br>Review Date: August 20, 2012<br>=
IETF LC End Date: August 20, 2012<br><br>Summary:<br>This draft is basicall=
y ready for publication, but has nits that<br>should be fixed before public=
ation.</span><o:p></o:p></p></div><p>&nbsp;<o:p></o:p></p><p><span style=3D=
'font-size:10.0pt;font-family:"Courier New";color:black'>This draft covers =
defect behavior for Ethernet pseudowires,</span><o:p></o:p></p><p><span sty=
le=3D'font-size:10.0pt;font-family:"Courier New";color:black'>including def=
ect state mapping and PE defect reporting behavior.</span><o:p></o:p></p><p=
><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>The=
 draft is generally in good shape.&nbsp; I found a few minor nits.</span><o=
:p></o:p></p><p>&nbsp;<o:p></o:p></p><p><span style=3D'font-size:10.0pt;fon=
t-family:"Courier New"'>1) The draft uses a lot of acronyms - while each ac=
ronym appears to</span><o:p></o:p></p><p><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New"'>be expanded on first use, an additional section ne=
ar the start of the</span><o:p></o:p></p><p><span style=3D'font-size:10.0pt=
;font-family:"Courier New"'>draft listing all of them would be helpful.</sp=
an><o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p><span style=3D'font-size:10.0p=
t;font-family:"Courier New"'>2) There's&nbsp;a typo in the first paragraph =
of section 2:</span><o:p></o:p></p><p>&nbsp;<o:p></o:p></p><div><p><span la=
ng=3DEN style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&n=
bsp;&nbsp;&nbsp; &nbsp;covers the following Ethernet OAM (Opertaions, Admin=
istration and </span><span lang=3DEN style=3D'font-size:10.0pt;color:black'=
><o:p></o:p></span></p><p><span lang=3DEN style=3D'font-size:10.0pt;color:b=
lack'>&nbsp;<o:p></o:p></span></p><p><span lang=3DEN style=3D'font-size:10.=
0pt;font-family:"Courier New";color:black'>Opertaions&nbsp;-&gt; Operations=
.</span><span lang=3DEN style=3D'font-size:10.0pt;color:black'><o:p></o:p><=
/span></p><p><span lang=3DEN style=3D'font-size:10.0pt;color:black'>&nbsp;<=
o:p></o:p></span></p><p><span lang=3DEN style=3D'font-size:10.0pt;font-fami=
ly:"Courier New";color:black'>3) The following normative reference is incom=
plete - please add additional</span><span lang=3DEN style=3D'font-size:10.0=
pt;color:black'><o:p></o:p></span></p><p><span lang=3DEN style=3D'font-size=
:10.0pt;font-family:"Courier New";color:black'>information that will enable=
 a reader to locate the referenced document:</span><span lang=3DEN style=3D=
'font-size:10.0pt;color:black'><o:p></o:p></span></p><p><span lang=3DEN sty=
le=3D'font-size:10.0pt;color:black'>&nbsp;<o:p></o:p></span></p><p><span la=
ng=3DEN style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&n=
bsp;&nbsp;&nbsp; &nbsp;[MEF16] &quot;Ethernet Local Management Interface&qu=
ot;, MEF16, January 2006.<o:p></o:p></span></p><p><span lang=3DEN style=3D'=
font-size:10.0pt;font-family:"Courier New";color:black'>&nbsp;<o:p></o:p></=
span></p><p><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>4)&nbsp;idnits 2.12.13 did not like the pagination:<o:p><=
/o:p></span></p><p><span lang=3DEN style=3D'font-size:10.0pt;font-family:"C=
ourier New";color:black'>&nbsp;<o:p></o:p></span></p><p><span lang=3DEN sty=
le=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&nbsp; =3D=3D=
 The page length should not exceed 58 lines per page, but there was 22<br>&=
nbsp;&nbsp;&nbsp;&nbsp; longer pages, the longest (page 1) being 61 lines</=
span><span style=3D'color:black'><o:p></o:p></span></p></div><div><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Thanks,</span><o:p></o=
:p></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font=
-family:"Courier New"'>--David</span><o:p></o:p></p></div><div><p class=3DM=
soNormal><span style=3D'font-size:10.0pt;font-family:"Courier New"'>-------=
---------------------------------------------<br>David L. Black, Distinguis=
hed Engineer<br>EMC Corporation, 176 South St., Hopkinton, MA&nbsp; 01748<b=
r>+1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; FAX: +1 (508) 293-7786<br><a href=3D"mailto:david.black@em=
c.com" target=3D"_blank">david.black@emc.com</a>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Mobile: +1 (978) 394-7754<br>------------------------------=
----------------------</span><span style=3D'font-family:"Courier New"'><o:p=
></o:p></span></p></div></div></div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE7128800E87EMX15Acorpemccom_--

From martin.thomson@gmail.com  Tue Feb  5 12:48:57 2013
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 8E28321F853E for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 12:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.712
X-Spam-Level: 
X-Spam-Status: No, score=-4.712 tagged_above=-999 required=5 tests=[AWL=-1.112, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFCWj9ro0il5 for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 12:48:57 -0800 (PST)
Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) by ietfa.amsl.com (Postfix) with ESMTP id B822121F853D for <gen-art@ietf.org>; Tue,  5 Feb 2013 12:48:56 -0800 (PST)
Received: by mail-wg0-f49.google.com with SMTP id 15so522539wgd.16 for <gen-art@ietf.org>; Tue, 05 Feb 2013 12:48:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=ByumizHLCOzyauH84mZjceExVCd7y0glCzwivQftTdw=; b=Z/h6Mmmf8Wt/mA2zghUZuTFRlBT0iuIvK2tq+Dk6tCR2EIerQCXErBHGUX1WLJjJJ8 qALW+FvOjJ5A3xWfjx4fFqFNf5AYVvXaB3pSXYIcW/6iJs3aZjxjrcOsytBkctjuIyJx K9J+36GGzxQDU66D1yo5Z9yeyxGYdgSZ0hekVj19qQxY8Me6CGAt+NIncav76/9yVxBC 8/Mqz0PxUb+KchB83Ddh5hrfblcDetmiZpW4DrGRhfS3dew6XcMnoJ3jgc9RSDpd0eBD RwyRo8UoyudXWZZRXuMvsbfcVhiduTV0bdun46icLyUsZ1z9A2Icc5/9LFCABgsOV9QT an+A==
MIME-Version: 1.0
X-Received: by 10.180.104.196 with SMTP id gg4mr793678wib.16.1360097335955; Tue, 05 Feb 2013 12:48:55 -0800 (PST)
Received: by 10.194.5.135 with HTTP; Tue, 5 Feb 2013 12:48:55 -0800 (PST)
In-Reply-To: <CABkgnnUG0UV0sLsknPtx3Y0g=_KHhpQhw-Ot7LX-G-efZRrSKw@mail.gmail.com>
References: <CABkgnnUG0UV0sLsknPtx3Y0g=_KHhpQhw-Ot7LX-G-efZRrSKw@mail.gmail.com>
Date: Tue, 5 Feb 2013 15:48:55 -0500
Message-ID: <CABkgnnV=pJtekt1izFDEtJZDywc1hRecV6z8LY4Hc5T8zr1X0Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Subject: [Gen-art] Fwd: Gen-ART review of draft-ietf-avtcore-srtp-encrypted-header-ext-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, 05 Feb 2013 20:48:57 -0000

FYI, I can't believe that I did this again.

Sorry Russ.

---------- Forwarded message ----------
From: Martin Thomson <martin.thomson@gmail.com>
Date: 17 January 2013 13:49
Subject: Gen-ART review of draft-ietf-avtcore-srtp-encrypted-header-ext-04
To: draft-ietf-avtcore-srtp-encrypted-header-ext.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>.

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

Document: draft-ietf-avtcore-srtp-encrypted-header-ext-04
Reviewer: Martin Thomson
Review Date: 2013-01-17
IETF LC End Date: 2013-01-17
IESG Telechat date: (if known)

Summary:  This document is clear, well-written and ready for
publication as proposed standard.

Minor issues:  I wonder if it is necessary to establish a registry for
the labels used in SRTP key derivation (k_e, k_s, k_he, k_hs, etc...).
 As unlikely as it seems, a collision in this space would be bad.

Nits/editorial comments:
S5: s/alternate/alternative/

From martin.thomson@gmail.com  Tue Feb  5 13:17:54 2013
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 201FE21F8667 for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 13:17:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.124
X-Spam-Level: 
X-Spam-Status: No, score=-5.124 tagged_above=-999 required=5 tests=[AWL=-1.525, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0aAV7YpwgKq for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 13:17:53 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id F2C3221F8682 for <gen-art@ietf.org>; Tue,  5 Feb 2013 13:17:52 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id o1so832944wic.5 for <gen-art@ietf.org>; Tue, 05 Feb 2013 13:17:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=AgWz+jD98hf5AarYO2fNy+Dz5LYC1kdFWZQ4vaiDawE=; b=Llnws55IjuCB9yrsnvRLfxh1kN7RieruHVSMH0fhWuPxQnXyyvuUuUHt6qdVRzlMP9 VePskRxI1/rEszfmxsPnVf7lzSivv2euWwe7H2zqRY0EPA4hycv9IcdQCdyZfirw7sxp 5O/SMEbmtIfeLvqbMSQjEDkrHA5Bo7gm17ZMG5w9J+DtTz15a7GmA9H4dR+Jg6nzWLQn ae1nHXopTq+O8mujOPFfFb4EElNYsgCNeaPQpoDbepjjGx1Q5khZlQcCN8AlPQEwsMMC kSR/Je3rbLi92PFL6bsD5LAM8IZ7qsUjqdv9SK/bWKz02Y0UTenADy2yVmwCTGMbFJP3 0MlA==
MIME-Version: 1.0
X-Received: by 10.180.101.98 with SMTP id ff2mr1162105wib.0.1360099072076; Tue, 05 Feb 2013 13:17:52 -0800 (PST)
Received: by 10.194.5.135 with HTTP; Tue, 5 Feb 2013 13:17:52 -0800 (PST)
In-Reply-To: <CABkgnnUG0UV0sLsknPtx3Y0g=_KHhpQhw-Ot7LX-G-efZRrSKw@mail.gmail.com>
References: <CABkgnnUG0UV0sLsknPtx3Y0g=_KHhpQhw-Ot7LX-G-efZRrSKw@mail.gmail.com>
Date: Tue, 5 Feb 2013 16:17:52 -0500
Message-ID: <CABkgnnWAcw8++zkKhWjDpFLWJXBb08cc16Acnt-rN6NAsS_qZQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-ietf-avtcore-srtp-encrypted-header-ext.all@tools.ietf.org,  "gen-art@ietf.org" <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-srtp-encrypted-header-ext-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, 05 Feb 2013 21:17:54 -0000

I've reviewed the latest (-06) and it is equally ready.  (That is,
I've seen no changes as a result of this review.)

On 17 January 2013 13:49, Martin Thomson <martin.thomson@gmail.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-avtcore-srtp-encrypted-header-ext-04
> Reviewer: Martin Thomson
> Review Date: 2013-01-17
> IETF LC End Date: 2013-01-17
> IESG Telechat date: (if known)
>
> Summary:  This document is clear, well-written and ready for
> publication as proposed standard.
>
> Minor issues:  I wonder if it is necessary to establish a registry for
> the labels used in SRTP key derivation (k_e, k_s, k_he, k_hs, etc...).
>  As unlikely as it seems, a collision in this space would be bad.
>
> Nits/editorial comments:
> S5: s/alternate/alternative/

From mccap@petoni.org  Tue Feb  5 18:03:54 2013
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 8637021F8A14 for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 18:03:54 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qhird2jmdd2Y for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 18:03:53 -0800 (PST)
Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by ietfa.amsl.com (Postfix) with ESMTP id 9396621F89A4 for <gen-art@ietf.org>; Tue,  5 Feb 2013 18:03:53 -0800 (PST)
Received: by mail-wg0-f43.google.com with SMTP id e12so699744wge.22 for <gen-art@ietf.org>; Tue, 05 Feb 2013 18:03:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type; bh=LYbYXc4QQcvbts3WH0dK04B9d25O0aRNrLCIrUF4854=; b=CV2lWmqDJzva5HDuRtX+fGP427bBT0CCARwI448cTN9ut4FQMwdSlpeyyAZlWOwX5J Mo4WatyPuUaW875ECTiwNHsAV/a2MS9y65BoJK8WIXjbN9OGEBF577jiVedGcCQk6y1O 7vdWZd3upMO6ylyEcrXfmlYlG3r2J3QgEEysw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type:x-gm-message-state; bh=LYbYXc4QQcvbts3WH0dK04B9d25O0aRNrLCIrUF4854=; b=NwadJZaxoywJfkHjcejTB8kIoi+6id0GmTO+2iyCoLaXfm9Xp+vWUpa39yhq+6D/FG URX58mx1ueg/FuPzZGXyG4k7oLmqnDIzMeqFWdQNr314MpwqbF+M21ksaal4HjnpErqh ckpG4zDvxOaPn3QawegYXAsZT7TRxBmKsT0uRz8UXzVv/qgWanzJiF9bcqG0YhYaJK8J JIOzzSTQHFk6ZoeCQuXxKfmpaOMeEYCR7NQdceTngSIZer6FnDDTqj0lwFXe3JKgFtaW pIZ1uhPDfFb20akAZO3m1hr0ZShcfx932tcQeORS26p1PieeD09pxqgfTLst46Jo34fa cguQ==
MIME-Version: 1.0
X-Received: by 10.180.82.41 with SMTP id f9mr1847678wiy.25.1360116230003; Tue, 05 Feb 2013 18:03:50 -0800 (PST)
Received: by 10.194.60.111 with HTTP; Tue, 5 Feb 2013 18:03:49 -0800 (PST)
X-Originating-IP: [68.45.157.93]
Date: Tue, 5 Feb 2013 21:03:49 -0500
Message-ID: <CACvMsLF9uzoahbTyb8pAA1ctDao2x5hYp-LQVBKUTWDpEGW_Tg@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-roll-p2p-measurement.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlFM8rll9tmXgQ0yd+gNAfb3HEOOSMjIenR7bdGjVqkJl2IKSAMR25Srw7f44biz2sCOyKB
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-roll-p2p-measurement-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: Wed, 06 Feb 2013 02:03:54 -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-roll-p2p-measurement-09
Reviewer:    Pete McCann
Review Date:  2012-02-05
IETF LC End Date:
IESG Telechat date: 2012-02-07

Summary:  Ready with nits

Major issues: None

Minor issues:

Section 5:
   An Intermediate Point MUST discard the packet with no further
   processing if the received MO is not a Measurement Request (i.e., T =
   0).
It wasn't clear to me at first why the Intermediate Points are not supposed
to see the Measurement Replies.  I gather this is because the RPL control
message used to send the reply uses a global or unique-local address
instead of a link-local address.  It may be worthwhile calling this
out explicitly
in Section 2 when you describe the two new RPL Control Messages.

Really, the Replies do pass through Intermediate Points but they are not
processed because they are not addressed to the Intermediate Point.  Right?


Nits/editorial comments:

Section 1:
   situations, where
SHOULD BE:
   situations where

Section 5.3:
   and the route accumulation in on
SHOULD BE:
  and the route accumulation is on

From lufang@cisco.com  Tue Feb  5 21:51:48 2013
Return-Path: <lufang@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 8EFA721F889D for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 21:51:48 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sn59Lw23XtHN for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 21:51:47 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1E621F86C4 for <gen-art@ietf.org>; Tue,  5 Feb 2013 21:51:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5567; q=dns/txt; s=iport; t=1360129907; x=1361339507; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=jZ//rpdzsrUuQGnjI6YJrLTkgYYOm7AsacZYr7GMAnY=; b=T9cKJNzNTXBX7eJrT7Cjt8WfXpzweN8yt7uMKlEja0Z5HaXCH5Cd4V6C RvixmzINDBdQeNeM7SywpkTYLIIfOndBA/yYWcnlF89tov1QXK2gE1jHh Q3rufRGHYffqvIiEXsgslnOG3WXV0yDsWePRbMjwDux+NmgKwf02M+XZW g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EALXuEVGtJV2Y/2dsb2JhbAA8Cb9rFnOCHwEBAQQ6PwwGAQgRAwECCxRCHQgBAQQBDQUIAYd2Aw8MuyOMFoEEg2BhA5IuOoRWjzWCfoIk
X-IronPort-AV: E=Sophos;i="4.84,613,1355097600"; d="scan'208";a="173847179"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP; 06 Feb 2013 05:51:46 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r165pkL6001500 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Feb 2013 05:51:46 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.232]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Tue, 5 Feb 2013 23:51:45 -0600
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Review of draft-ietf-mpls-tp-security-framework-07
Thread-Index: Ac3/mwU7IdpVSjk6TAG/2FHsTA3yZwEm2eIA
Date: Wed, 6 Feb 2013 05:51:44 +0000
Message-ID: <0DB8F45437AB844CBB5102F807A0AD93102793F9@xmb-rcd-x03.cisco.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA07B76B@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [10.21.144.9]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <590B806DB4FDD0409D3D97AA6D2B83C0@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "nabil.bitar@verizon.com" <nabil.bitar@verizon.com>, "ms-daikoku@kddi.com" <ms-daikoku@kddi.com>, "lei.wang@limenetworks.no" <lei.wang@limenetworks.no>, "ben@niven-jenkins.co.uk" <ben@niven-jenkins.co.uk>, "raymond.zhang@alcatel-lucent.com" <raymond.zhang@alcatel-lucent.com>, "scott.mansfield@ericsson.com" <scott.mansfield@ericsson.com>, "rfg@acm.org" <rfg@acm.org>, "henry.yu@twtelecom.com" <henry.yu@twtelecom.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-mpls-tp-security-framework-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: Wed, 06 Feb 2013 05:51:48 -0000

Hi Dan,

Thank you very much for your review and detailed comments, really
appreciate your discussion and helpful suggestions.

I updated the document, addressed all your comments. It is reflected in
the 08 version just posted.
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-security-framework-0
8.txt


We acknowledged your help in the document.

Please see in-line.

-----Original Message-----
From: <Romascanu>, "Dan   (Dan)" <dromasca@avaya.com>
Date: Thursday, January 31, 2013 2:09 AM
To: "gen-art@ietf.org" <gen-art@ietf.org>
Cc: Luyuan Fang <lufang@cisco.com>, "ben@niven-jenkins.co.uk"
<ben@niven-jenkins.co.uk>, "scott.mansfield@ericsson.com"
<scott.mansfield@ericsson.com>, "rfg@acm.org" <rfg@acm.org>,
"raymond.zhang@alcatel-lucent.com" <raymond.zhang@alcatel-lucent.com>,
Nabil Bitar <nabil.bitar@verizon.com>, "ms-daikoku@kddi.com"
<ms-daikoku@kddi.com>, "henry.yu@twtelecom.com" <henry.yu@twtelecom.com>,
"lei.wang@limenetworks.no" <lei.wang@limenetworks.no>,
"adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: Gen-ART Review of draft-ietf-mpls-tp-security-framework-07

>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-mpls-tp-security-framework-07
>Reviewer: Dan Romascanu
>Review Date: 1/31/13
>IETF LC End Date: 2/6/13
>IESG Telechat date: (if known)
>
>Summary: Ready with Issues
>
>This is a short, well-written and useful document that supplements RFC
>5920 with information on reference models, security threats and defense
>techniques specific to MPLS-TP. There is one major issue which I believe
>should be fixed and is not too difficult to fix if the authors agree.
>
>Major issues:
>
>One of the major features of extending MPLS in MPLS-TP is rightly
>identified in the words of the Abstract as the 'strong emphasis on static
>provisioning supported by network management systems'. However Sections 3
>and 4 miss to describe accurately the threats introduced by provisioning
>tools and the defensive techniques that need to be put in place in order
>to address these threats.
>
>Section 3 speaks about 'attacks to NMS' but this is quite vague (what
>kind of attacks?) and incomplete, as it is not only the NMS that can be
>attacked but also the communication between the NMS and the routers that
>are being provisioned, as well as the access of the users to the
>provisioning tools. Threats like disclosure of information, masquerade
>(as NMS) or access of unauthorized users to the provisioning information
>and controls need to be clearly articulated here.

[luyuan] Good points. In Section 3, the following text is added (after the
paragraph talks "attacks to NMS"):


Attacks to NMS may come from external attackers, or insiders. Outside
attacks are initiated outside of the trusted zone by unauthorized user of
the MPLS-TP network management systems. Insider attack is initiated from
inside of the trusted zone by an entity with authorized access to the
management systems, but performs unapproved harmful functions to the
MPLS-TP networks. These attacks may be directly targeted to the NMS, or
via the compromised communication channels between the NMS and the network
devices that are being provisioned, or through the access of the users to
the provisioning tools. The security threat may include disclosure of
information, generating false OAM messages, taking down MPLS-TP LSPs,
connecting to the wrong MPLS-TP tunnel end points, and DoS attacks to the
MPLS-TP networks.


>=20
>
>In Section 4 the corresponding defensive techniques need to be listed, or
>at least make clear that techniques like entity authentication for
>identity verification, encryption for confidentiality, message integrity
>and replay detection to ensure the validity of message streams, as well
>as users access control and events logging need to apply also for NMS
>applications and provisioning traffic.

>=20
[luyuan] Agreed. The following paragraph is added at the end of the
section 4, pretty much based on your suggestions.

It is important to point out the following security defense techniques
which are particularly critical for NMS due to the strong emphasis on
static provisioning supported by NMS in MPLS-TP deployment. These
techniques include: Entity authentication for identity verification,
encryption for confidentiality, message integrity and replay detection to
ensure the validity of message streams, as well as users access control
and events logging which must be applied for NMS and provisioning
applications.
>
>Minor issues:=20
>
>Nits/editorial comments:
>
>1. Several acronyms are not expanded at first occurrence: PE/T-PE, GAL

[luyuan] Fixed. We initially had terminology section, it was taken out
during the last call discussion. I added the section back with a new list
of terms that are relevant to this document.
>
>2. Inconsistent abbreviation: T-PE in the text, TPE in figures 2-5

[luyuan] Fixed.
>
>3. The first sentence in Section 3 seems broken grammatically:
>
>> This section discuss various network security threats which are to
>   MPLS-TP and may endanger MPLS-TP networks.

[luyuan] Fixed.
New text: This section discusses various network security threats that are
unique to MPLS-TP and may endanger MPLS-TP networks.
>
>
Thanks,
Luyuan


From huawei.danli@huawei.com  Tue Feb  5 16:52:26 2013
Return-Path: <huawei.danli@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 8522221F85D2; Tue,  5 Feb 2013 16:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.092
X-Spam-Level: *
X-Spam-Status: No, score=1.092 tagged_above=-999 required=5 tests=[AWL=-1.358,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6pVzy2ghkhyP; Tue,  5 Feb 2013 16:52:25 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5650A21F8596; Tue,  5 Feb 2013 16:52:23 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOE80256; Wed, 06 Feb 2013 00:52:21 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 6 Feb 2013 00:51:22 +0000
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 6 Feb 2013 00:52:20 +0000
Received: from szxeml555-mbx.china.huawei.com ([169.254.1.229]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.007; Wed, 6 Feb 2013 08:52:15 +0800
From: "Lidan (Dan)" <huawei.danli@huawei.com>
To: Richard Barnes <rlb@ipv.sx>, Lou Berger <lberger@labn.net>
Thread-Topic: =?gb2312?B?tPC4tDogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2FtcC1sbXAt?= =?gb2312?Q?behavior-negotiation-10?=
Thread-Index: AQHOAkKfFPU9gjEKO0O3gq+ZfCNfU5hqkSYwgAA9MICAAAxwAIABKJCg
Date: Wed, 6 Feb 2013 00:52:14 +0000
Message-ID: <92A1F6CF27D54D4DA5364E59D892A02A38851F2B@szxeml555-mbx.china.huawei.com>
References: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com> <92A1F6CF27D54D4DA5364E59D892A02A388518AA@szxeml555-mbx.china.huawei.com> <51111613.7070300@labn.net> <CAL02cgTosa9Y1R4UOyPXZAwOZ_X7KRrDEdJ3p98uGD3XHKaYsw@mail.gmail.com>
In-Reply-To: <CAL02cgTosa9Y1R4UOyPXZAwOZ_X7KRrDEdJ3p98uGD3XHKaYsw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.73.151]
Content-Type: multipart/alternative; boundary="_000_92A1F6CF27D54D4DA5364E59D892A02A38851F2Bszxeml555mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Wed, 06 Feb 2013 00:02:19 -0800
Cc: The IESG <iesg@ietf.org>, Richard Barnes <rbarnes@bbn.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org" <draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org>
Subject: [Gen-art] =?gb2312?b?tPC4tDogtPC4tDogR2VuLUFSVCByZXZpZXcgb2YgZHJh?= =?gb2312?b?ZnQtaWV0Zi1jY2FtcC1sbXAtYmVoYXZpb3ItbmVnb3RpYXRpb24tMTA=?=
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 Feb 2013 00:52:26 -0000

--_000_92A1F6CF27D54D4DA5364E59D892A02A38851F2Bszxeml555mbxchi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

T2ssIHRoZSBvbGQgZm9ybWF0cyBvZiBDb25maWcvQ29uZmlnQWNrL0NvbmZpZ05hY2sgYXJlIG5v
dCBuZWNlc3NhcnkgdG8gYmUgcmVwZWF0ZWQgaW4gdGhpcyBkcmFmdC4gSSB3aWxsIGNsZWFuIHRo
ZSB0ZXh0Lg0KDQpUaGFua3MsDQoNCkRhbg0KDQoNCreivP7IyzogUmljaGFyZCBCYXJuZXMgW21h
aWx0bzpybGJAaXB2LnN4XQ0Kt6LLzcqxvOQ6IDIwMTPE6jLUwjXI1SAyMzowOQ0KytW8/sjLOiBM
b3UgQmVyZ2VyDQqzrcvNOiBMaWRhbiAoRGFuKTsgUmljaGFyZCBCYXJuZXM7IGRyYWZ0LWlldGYt
Y2NhbXAtbG1wLWJlaGF2aW9yLW5lZ290aWF0aW9uQHRvb2xzLmlldGYub3JnOyBnZW4tYXJ0QGll
dGYub3JnOyBpZXRmQGlldGYub3JnOyBUaGUgSUVTRw0K1vfM4jogUmU6ILTwuLQ6IEdlbi1BUlQg
cmV2aWV3IG9mIGRyYWZ0LWlldGYtY2NhbXAtbG1wLWJlaGF2aW9yLW5lZ290aWF0aW9uLTEwDQoN
CkhleSBMb3UsDQoNClRoYXQgdGV4dCBsb29rcyBmaW5lIHRvIG1lIQ0KDQotLVJpY2hhcmQNCg0K
T24gVHVlLCBGZWIgNSwgMjAxMyBhdCA5OjI0IEFNLCBMb3UgQmVyZ2VyIDxsYmVyZ2VyQGxhYm4u
bmV0PG1haWx0bzpsYmVyZ2VyQGxhYm4ubmV0Pj4gd3JvdGU6DQpEYW4vUmljaGFyZCwNCg0KDQpP
biAyLzQvMjAxMyAxMDowNSBQTSwgTGlkYW4gKERhbikgd3JvdGU6DQo+IEhpIFJpY2hhcmQsDQo+
DQo+IFRoYW5rcyBmb3IgdGhlIHJldmlldyBvZiB0aGlzIGRyYWZ0IQ0KPg0KPj4gU2VjdGlvbiAy
LjEuICBXb3VsZCBiZSBoZWxwZnVsIHRvIGVpdGhlciBpbmNsdWRlIHRoZSBvbGQgZm9ybWF0cw0K
Pj4gYW5kL29yIHNheSBleHBsaWNpdGx5IHdoYXQgaXMgY2hhbmdpbmcuDQoNCj4gQWRkZWQgdGhl
IG9yaWdpbmFsIGZvcm1hdCBvZiBDb25maWcsIENvbmZpZ0FjayBhbmQgQ29uZmlnTmFjaw0KPiBt
ZXNzYWdlcyB3aGljaCBhcmUgZGVmaW5lZCBpbiBSRkM0MjA0Lg0KPg0KSSBwZXJzb25hbGx5IHRo
aW5rIGl0J3MgYSBtaXN0YWtlIHRvIHJlcGVhdCBkZWZpbml0aW9ucyBpbiBub24tYmlzIFJGQ3Mu
DQogSSB0aGluayB0aGlzIGluY3JlYXNlcyB0aGUgcG9zc2liaWxpdHkgb2YgbWlzdGFrZXMgYW5k
IGNvbmZ1c2lvbiAoZS5nLiwNCndoZW4gdGhlIHRleHQgaXNuJ3QgY29waWVkIHByb3Blcmx5IG9y
IHdoZW4gdGhlIG9yaWdpbmFsIGRvY3VtZW50IGlzDQpyZXBsYWNlZCkuDQoNCk15IG9yaWdpbmFs
IHRob3VnaHQgd2FzIHRvIHByb3Bvc2UgdGV4dCB0byBmb2xsb3cgUmljaGFyZCdzIHN1Z2dlc3Rp
b24NCm9mIGV4cGxpY2l0bHkgc2F5aW5nIHdoYXQgaGFzIGNoYW5nZWQsIGJ1dCBJIHNlZSBzdWNo
IHRleHQgaXMgdGhlcmUgYXQNCnRoZSBzdGFydCBvZiBzZWN0aW9uIDI6DQoNCiAgIExNUCBDb25m
aWcsIENvbmZpZ05hY2sgYW5kIENvbmZpZ0FjayBtZXNzYWdlcyBhcmUgbW9kaWZpZWQgYnkgdGhp
cw0KICAgZG9jdW1lbnQgdG8gYWxsb3cgZm9yIHRoZSBpbmNsdXNpb24gb2YgbXVsdGlwbGUgQ09O
RklHIG9iamVjdHMuIFRoZQ0KICAgQ29uZmlnIGFuZCBDb25maWdOYWNrIG1lc3NhZ2VzIHdlcmUg
b25seSBkZWZpbmVkIHRvIGNhcnJ5IG9uZSBDT05GSUcNCiAgIG9iamVjdCBpbiBbUkZDNDIwNF0u
IFRoZSBDb25maWdBY2sgbWVzc2FnZSwgd2hpY2ggd2FzIGRlZmluZWQNCiAgIHdpdGhvdXQgY2Fy
cnlpbmcgYW55IENPTkZJRyBvYmplY3RzIGluIFtSRkM0MjA0XSwgaXMgbW9kaWZpZWQgdG8NCiAg
IGVuYWJsZSBleHBsaWNpdCBpZGVudGlmaWNhdGlvbiBvZiBuZWdvdGlhdGVkIGNvbmZpZ3VyYXRp
b24NCiAgIHBhcmFtZXRlcnMuIFRoZSBpbmNsdXNpb24gb2YgQ09ORklHIG9iamVjdHMgaW4gQ29u
ZmlnQWNrIG1lc3NhZ2VzIGlzDQogICB0cmlnZ2VyZWQgYnkgdGhlIHVzZSBvZiB0aGUgQmVoYXZp
b3JDb25maWcgb2JqZWN0IChkZWZpbmVkIGJlbG93KSBpbg0KICAgYSByZWNlaXZlZCBDb25maWcg
bWVzc2FnZS4NCg0KUmljaGFyZCwNCg0KSXMgdGhpcyB0ZXh0IHN1ZmZpY2llbnQ/ICBBbHRlcm5h
dGl2ZWx5LCB0aGlzIHRleHQgY2FuIGJlIG1vdmVkIHRvDQppbW1lZGlhdGVseSBwcm9jZWVkIHRo
ZSBCTkYuDQoNCk11Y2ggdGhhbmtzDQpMb3UNCihkb2N1bWVudCBjby1hdXRob3IpDQoNCg==

--_000_92A1F6CF27D54D4DA5364E59D892A02A38851F2Bszxeml555mbxchi_
Content-Type: text/html; charset="gb2312"
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=CB=CE=CC=E5;}
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-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.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=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ok, the ol=
d formats of Config/ConfigAck/ConfigNack are not necessary to be repeated i=
n this draft. I will clean the text.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dan<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">=B7=A2=BC=FE=C8=
=CB<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D"fo=
nt-size:10.0pt"> Richard Barnes [mailto:rlb@ipv.sx]
<br>
</span><b><span style=3D"font-size:10.0pt">=B7=A2=CB=CD=CA=B1=BC=E4<span la=
ng=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D"font-size:10.=
0pt"> 2013</span><span style=3D"font-size:10.0pt">=C4=EA<span lang=3D"EN-US=
">2</span>=D4=C2<span lang=3D"EN-US">5</span>=C8=D5<span lang=3D"EN-US"> 23=
:09<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> Lou Berger<br>
</span><b>=B3=AD=CB=CD<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Lidan (Dan); Richard Barnes; draft-ietf-ccamp-lmp-behavior-negotiation@to=
ols.ietf.org; gen-art@ietf.org; ietf@ietf.org; The IESG<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Re: </span>=B4=F0=B8=B4<span lang=3D"EN-US">: Gen-ART review of draft-iet=
f-ccamp-lmp-behavior-negotiation-10<o:p></o:p></span></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hey Lou,<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">That text looks fine to me!<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">--Richard<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Tue, Feb 5, 2013 at 9:24 AM,=
 Lou Berger &lt;<a href=3D"mailto:lberger@labn.net" target=3D"_blank">lberg=
er@labn.net</a>&gt; wrote:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Dan/Richard,<o:p></o:p></span><=
/p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<br>
<br>
On 2/4/2013 10:05 PM, Lidan (Dan) wrote:<br>
&gt; Hi Richard,<br>
&gt;<br>
&gt; Thanks for the review of this draft!<br>
&gt;<br>
&gt;&gt; Section 2.1. &nbsp;Would be helpful to either include the old form=
ats<br>
&gt;&gt; and/or say explicitly what is changing.<br>
<br>
&gt; Added the original format of Config, ConfigAck and ConfigNack<br>
&gt; messages which are defined in RFC4204.<br>
&gt;<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I personally think it's a mista=
ke to repeat definitions in non-bis RFCs.<br>
&nbsp;I think this increases the possibility of mistakes and confusion (e.g=
.,<br>
when the text isn't copied properly or when the original document is<br>
replaced).<br>
<br>
My original thought was to propose text to follow Richard's suggestion<br>
of explicitly saying what has changed, but I see such text is there at<br>
the start of section 2:<br>
<br>
&nbsp; &nbsp;LMP Config, ConfigNack and ConfigAck messages are modified by =
this<br>
&nbsp; &nbsp;document to allow for the inclusion of multiple CONFIG objects=
. The<br>
&nbsp; &nbsp;Config and ConfigNack messages were only defined to carry one =
CONFIG<br>
&nbsp; &nbsp;object in [RFC4204]. The ConfigAck message, which was defined<=
br>
&nbsp; &nbsp;without carrying any CONFIG objects in [RFC4204], is modified =
to<br>
&nbsp; &nbsp;enable explicit identification of negotiated configuration<br>
&nbsp; &nbsp;parameters. The inclusion of CONFIG objects in ConfigAck messa=
ges is<br>
&nbsp; &nbsp;triggered by the use of the BehaviorConfig object (defined bel=
ow) in<br>
&nbsp; &nbsp;a received Config message.<br>
<br>
Richard,<br>
<br>
Is this text sufficient? &nbsp;Alternatively, this text can be moved to<br>
immediately proceed the BNF.<br>
<br>
Much thanks<br>
Lou<br>
(document co-author)<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_92A1F6CF27D54D4DA5364E59D892A02A38851F2Bszxeml555mbxchi_--

From prvs=742667baf=mukul@uwm.edu  Tue Feb  5 19:33:01 2013
Return-Path: <prvs=742667baf=mukul@uwm.edu>
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 AE1C621F8645 for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 19:33:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJQvPXMoa6wV for <gen-art@ietfa.amsl.com>; Tue,  5 Feb 2013 19:33:00 -0800 (PST)
Received: from ip4mta.uwm.edu (ip4mta.uwm.edu [129.89.7.194]) by ietfa.amsl.com (Postfix) with ESMTP id C6CC221F8622 for <gen-art@ietf.org>; Tue,  5 Feb 2013 19:32:59 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0EADzNEVF/AAAB/2dsb2JhbABFhki5NoMZI1YbFAYCDRkCWQaIJAyoPIJAhweJCoEjjyWBEwOIZo07gR2PNYMdggU
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta03.pantherlink.uwm.edu (Postfix) with ESMTP id 0AB3B1216AE; Tue,  5 Feb 2013 21:32:59 -0600 (CST)
X-Virus-Scanned: amavisd-new at 
Received: from mta03.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta03.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2l8yYMeTrKvN; Tue,  5 Feb 2013 21:32:58 -0600 (CST)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta03.pantherlink.uwm.edu (Postfix) with ESMTP id B072C1216A6; Tue,  5 Feb 2013 21:32:58 -0600 (CST)
Date: Tue, 5 Feb 2013 21:32:58 -0600 (CST)
From: Mukul Goyal <mukul@uwm.edu>
To: Pete McCann <mccap@petoni.org>
Message-ID: <164701377.226448.1360121578639.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <CACvMsLF9uzoahbTyb8pAA1ctDao2x5hYp-LQVBKUTWDpEGW_Tg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [99.20.249.193]
X-Mailer: Zimbra 6.0.15_GA_2995 (ZimbraWebClient - SAF3 (Win)/6.0.15_GA_2995)
X-Authenticated-User: mukul@uwm.edu
X-Mailman-Approved-At: Wed, 06 Feb 2013 00:02:19 -0800
Cc: gen-art@ietf.org, draft-ietf-roll-p2p-measurement all <draft-ietf-roll-p2p-measurement.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-roll-p2p-measurement-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: Wed, 06 Feb 2013 03:33:01 -0000

Hi Pete

Please see my response inline.

[PM]

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-roll-p2p-measurement-09
Reviewer:    Pete McCann
Review Date:  2012-02-05
IETF LC End Date:
IESG Telechat date: 2012-02-07

Summary:  Ready with nits

Major issues: None

Minor issues:

Section 5:
   An Intermediate Point MUST discard the packet with no further
   processing if the received MO is not a Measurement Request (i.e., T =
   0).
It wasn't clear to me at first why the Intermediate Points are not supposed
to see the Measurement Replies.  I gather this is because the RPL control
message used to send the reply uses a global or unique-local address
instead of a link-local address.  It may be worthwhile calling this
out explicitly
in Section 2 when you describe the two new RPL Control Messages.

Really, the Replies do pass through Intermediate Points but they are not
processed because they are not addressed to the Intermediate Point.  Right?

[MG]
So there are two different questions really:

Q1: Why the Intermediate Points are not supposed to see the Measurement Replies?
Ans to Q1:
The Measurement Reply is _unicast_ to the Start Point. So, the routers on the Measurement Reply's path treat it just as another data packet. The RPL code running on these routers never sees the Measurement Reply. So, if the RPL code on a router does see a Measurement Reply and this router is not listed as the Start Point inside the message, the router MUST discard the received message.

Q2: Would the Measurement Reply pass through the Intermediate Points (at any layer)?
Ans to Q2:
Let's first be clear about what an Intermediate Point is. The Intermediate Points are the routers on the route being measured excluding the Start Point and the End Point. Now, Section 6.1 clearly identifies the situations where the Measurement Reply _may_ travel back to the Start Point using the reverse of the measured route. So, it is possible that the Measurement Reply travels along the reverse of the measured path and, in this case, the Measurement Reply does pass through all the Intermediate Points. However, the End Point may decide to send the Measurement Reply along a different route (different than the measured route). In that case, the Measurement Reply may not pass through the Intermediate Points.

Hopefully this clarifies things. If you still think that the text needs to change, please let me know.

[PM]
Nits/editorial comments:

Section 1:
   situations, where
SHOULD BE:
   situations where

Section 5.3:
   and the route accumulation in on
SHOULD BE:
  and the route accumulation is on

[MG]
Thanks. I will make these changes in the final document.

Thanks
Mukul

From ron.even.tlv@gmail.com  Wed Feb  6 00:24:25 2013
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 4858A21F8519; Wed,  6 Feb 2013 00:24:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=1.090,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8s1lYFxDA0AQ; Wed,  6 Feb 2013 00:24:24 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id EA87321F84BB; Wed,  6 Feb 2013 00:24:23 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id f13so503194eaa.3 for <multiple recipients>; Wed, 06 Feb 2013 00:24:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=WqNAAcEuHiWtFOLLA5Xr1SspU1xX4g5+u2Tudj3B5Xs=; b=lavP4YRMzaC359LZrl2EdB163JpXd+AkhS4ZJECY4ECTYFGkk1SsJ3C4O9SQRim46M Cmw/GEW4buDgZ22if5FvPIUZqJBh/EsMzCi7hl5NFBnEuB4pyvgfxvQplo4tE+PDm2Zd nO448JMbTw+EF/2Oca54FAgvipJEF99VjrC6aBvOcj6R2L7t/qLtKxSHeeWmqHhKFLPJ vKUxVEjYFiGdSk0sMhRouO7TC3Hcr0Gd+o2kgEgZD2hQeaodm1atIk/EGGsTNRAC0nZu Y4UWOnK4Ax1o47bVbJLF5MdoeFYAKkJPe76b/mtu24LDkZMEG7c9CIxJlt1PTuaoHjp/ FTFw==
X-Received: by 10.14.225.133 with SMTP id z5mr95973865eep.15.1360139063117; Wed, 06 Feb 2013 00:24:23 -0800 (PST)
Received: from RoniE (bzq-79-181-179-229.red.bezeqint.net. [79.181.179.229]) by mx.google.com with ESMTPS id q42sm26226087eem.14.2013.02.06.00.24.20 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 06 Feb 2013 00:24:22 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-harkins-brainpool-ike-groups.all@tools.ietf.org>
Date: Wed, 6 Feb 2013 10:21:30 +0200
Message-ID: <04d701ce0442$f9a81d20$ecf85760$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04D8_01CE0453.BD318960"
X-Mailer: Microsoft Outlook 14.0
thread-index: Ac4EQvd90NNKeCsHSXq8kAsBI8lTsg==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-harkins-brainpool-ike-groups-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: Wed, 06 Feb 2013 08:24:25 -0000

This is a multipart message in MIME format.

------=_NextPart_000_04D8_01CE0453.BD318960
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-harkins-brainpool-ike-groups-04

Reviewer: Roni Even

Review Date:2013-2-13

IETF LC End Date: 2013-2-28

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

 


------=_NextPart_000_04D8_01CE0453.BD318960
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;}
--></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><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><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"'>Document: =
</span><span style=3D'font-family:"Courier =
New","serif"'>draft-harkins-brainpool-ike-groups-04</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"'>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:2013&#8211;2&#8211;13<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: 2013-2&#8211;28<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</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"'>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"'><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=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_04D8_01CE0453.BD318960--


From dromasca@avaya.com  Wed Feb  6 03:57:59 2013
Return-Path: <dromasca@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 B724621F84DC for <gen-art@ietfa.amsl.com>; Wed,  6 Feb 2013 03:57:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.388
X-Spam-Level: 
X-Spam-Status: No, score=-103.388 tagged_above=-999 required=5 tests=[AWL=0.211, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g5vLjMvMati9 for <gen-art@ietfa.amsl.com>; Wed,  6 Feb 2013 03:57:58 -0800 (PST)
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 33E2621F84C0 for <gen-art@ietf.org>; Wed,  6 Feb 2013 03:57:57 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAP0QA1HGmAcF/2dsb2JhbAA8CYJru2cWc4IeAQEBAQIBEig/DAQCAQgNBAMBAQELFAkHMhQJCAEBBAENBQgBGYdbAwkGAQuhWJx0jA1+g1NhA5IgOoRPhHGKO4J3giQ
X-IronPort-AV: E=Sophos;i="4.84,541,1355115600"; d="scan'208";a="342717464"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 06 Feb 2013 06:58:54 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 Feb 2013 06:56:46 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Wed, 6 Feb 2013 06:58:14 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Luyuan Fang (lufang)" <lufang@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Review of draft-ietf-mpls-tp-security-framework-07
Thread-Index: Ac3/mwU7IdpVSjk6TAG/2FHsTA3yZwEm2eIAAAqrFpA=
Date: Wed, 6 Feb 2013 11:58:12 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA08300A@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA07B76B@AZ-FFEXMB04.global.avaya.com> <0DB8F45437AB844CBB5102F807A0AD93102793F9@xmb-rcd-x03.cisco.com>
In-Reply-To: <0DB8F45437AB844CBB5102F807A0AD93102793F9@xmb-rcd-x03.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "nabil.bitar@verizon.com" <nabil.bitar@verizon.com>, "ms-daikoku@kddi.com" <ms-daikoku@kddi.com>, "lei.wang@limenetworks.no" <lei.wang@limenetworks.no>, "ben@niven-jenkins.co.uk" <ben@niven-jenkins.co.uk>, "raymond.zhang@alcatel-lucent.com" <raymond.zhang@alcatel-lucent.com>, "scott.mansfield@ericsson.com" <scott.mansfield@ericsson.com>, "rfg@acm.org" <rfg@acm.org>, "henry.yu@twtelecom.com" <henry.yu@twtelecom.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-mpls-tp-security-framework-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: Wed, 06 Feb 2013 11:57:59 -0000

Thank you for addressing my comments.=20

>From my perspective the document is now ready.=20

Regards,=20

Dan




> -----Original Message-----
> From: Luyuan Fang (lufang) [mailto:lufang@cisco.com]
> Sent: Wednesday, February 06, 2013 7:52 AM
> To: Romascanu, Dan (Dan); gen-art@ietf.org
> Cc: ben@niven-jenkins.co.uk; scott.mansfield@ericsson.com; rfg@acm.org;
> raymond.zhang@alcatel-lucent.com; nabil.bitar@verizon.com; ms-
> daikoku@kddi.com; henry.yu@twtelecom.com; lei.wang@limenetworks.no;
> adrian@olddog.co.uk
> Subject: Re: Gen-ART Review of draft-ietf-mpls-tp-security-framework-07
>=20
> Hi Dan,
>=20
> Thank you very much for your review and detailed comments, really
> appreciate your discussion and helpful suggestions.
>=20
> I updated the document, addressed all your comments. It is reflected in
> the 08 version just posted.
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-security-
> framework-0
> 8.txt
>=20
>=20
> We acknowledged your help in the document.
>=20
> Please see in-line.
>=20
> -----Original Message-----
> From: <Romascanu>, "Dan   (Dan)" <dromasca@avaya.com>
> Date: Thursday, January 31, 2013 2:09 AM
> To: "gen-art@ietf.org" <gen-art@ietf.org>
> Cc: Luyuan Fang <lufang@cisco.com>, "ben@niven-jenkins.co.uk"
> <ben@niven-jenkins.co.uk>, "scott.mansfield@ericsson.com"
> <scott.mansfield@ericsson.com>, "rfg@acm.org" <rfg@acm.org>,
> "raymond.zhang@alcatel-lucent.com" <raymond.zhang@alcatel-lucent.com>,
> Nabil Bitar <nabil.bitar@verizon.com>, "ms-daikoku@kddi.com"
> <ms-daikoku@kddi.com>, "henry.yu@twtelecom.com"
> <henry.yu@twtelecom.com>, "lei.wang@limenetworks.no"
> <lei.wang@limenetworks.no>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
> Subject: Gen-ART Review of draft-ietf-mpls-tp-security-framework-07
>=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>.
> >
> >Please resolve these comments along with any other Last Call comments
> >you may receive.
> >
> >Document: draft-ietf-mpls-tp-security-framework-07
> >Reviewer: Dan Romascanu
> >Review Date: 1/31/13
> >IETF LC End Date: 2/6/13
> >IESG Telechat date: (if known)
> >
> >Summary: Ready with Issues
> >
> >This is a short, well-written and useful document that supplements RFC
> >5920 with information on reference models, security threats and defense
> >techniques specific to MPLS-TP. There is one major issue which I
> >believe should be fixed and is not too difficult to fix if the authors
> agree.
> >
> >Major issues:
> >
> >One of the major features of extending MPLS in MPLS-TP is rightly
> >identified in the words of the Abstract as the 'strong emphasis on
> >static provisioning supported by network management systems'. However
> >Sections 3 and 4 miss to describe accurately the threats introduced by
> >provisioning tools and the defensive techniques that need to be put in
> >place in order to address these threats.
> >
> >Section 3 speaks about 'attacks to NMS' but this is quite vague (what
> >kind of attacks?) and incomplete, as it is not only the NMS that can be
> >attacked but also the communication between the NMS and the routers
> >that are being provisioned, as well as the access of the users to the
> >provisioning tools. Threats like disclosure of information, masquerade
> >(as NMS) or access of unauthorized users to the provisioning
> >information and controls need to be clearly articulated here.
>=20
> [luyuan] Good points. In Section 3, the following text is added (after
> the paragraph talks "attacks to NMS"):
>=20
>=20
> Attacks to NMS may come from external attackers, or insiders. Outside
> attacks are initiated outside of the trusted zone by unauthorized user
> of the MPLS-TP network management systems. Insider attack is initiated
> from inside of the trusted zone by an entity with authorized access to
> the management systems, but performs unapproved harmful functions to the
> MPLS-TP networks. These attacks may be directly targeted to the NMS, or
> via the compromised communication channels between the NMS and the
> network devices that are being provisioned, or through the access of the
> users to the provisioning tools. The security threat may include
> disclosure of information, generating false OAM messages, taking down
> MPLS-TP LSPs, connecting to the wrong MPLS-TP tunnel end points, and DoS
> attacks to the MPLS-TP networks.
>=20
>=20
> >
> >
> >In Section 4 the corresponding defensive techniques need to be listed,
> >or at least make clear that techniques like entity authentication for
> >identity verification, encryption for confidentiality, message
> >integrity and replay detection to ensure the validity of message
> >streams, as well as users access control and events logging need to
> >apply also for NMS applications and provisioning traffic.
>=20
> >
> [luyuan] Agreed. The following paragraph is added at the end of the
> section 4, pretty much based on your suggestions.
>=20
> It is important to point out the following security defense techniques
> which are particularly critical for NMS due to the strong emphasis on
> static provisioning supported by NMS in MPLS-TP deployment. These
> techniques include: Entity authentication for identity verification,
> encryption for confidentiality, message integrity and replay detection
> to ensure the validity of message streams, as well as users access
> control and events logging which must be applied for NMS and
> provisioning applications.
> >
> >Minor issues:
> >
> >Nits/editorial comments:
> >
> >1. Several acronyms are not expanded at first occurrence: PE/T-PE, GAL
>=20
> [luyuan] Fixed. We initially had terminology section, it was taken out
> during the last call discussion. I added the section back with a new
> list of terms that are relevant to this document.
> >
> >2. Inconsistent abbreviation: T-PE in the text, TPE in figures 2-5
>=20
> [luyuan] Fixed.
> >
> >3. The first sentence in Section 3 seems broken grammatically:
> >
> >> This section discuss various network security threats which are to
> >   MPLS-TP and may endanger MPLS-TP networks.
>=20
> [luyuan] Fixed.
> New text: This section discusses various network security threats that
> are unique to MPLS-TP and may endanger MPLS-TP networks.
> >
> >
> Thanks,
> Luyuan


From lufang@cisco.com  Wed Feb  6 06:43:37 2013
Return-Path: <lufang@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 0C35F21F8715 for <gen-art@ietfa.amsl.com>; Wed,  6 Feb 2013 06:43:37 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nQ+It9uGXCar for <gen-art@ietfa.amsl.com>; Wed,  6 Feb 2013 06:43:35 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 935D721F8472 for <gen-art@ietf.org>; Wed,  6 Feb 2013 06:43:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7410; q=dns/txt; s=iport; t=1360161815; x=1361371415; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=G1PDuqOlDRYSIVyziAsW5N8RKlO7nfctQo0Q8Igl9Uk=; b=Xr5YqV9i6qhlxLd6qy7/uphEfepO7tpNbNHc/pAribFSR3Hr2PpY8bBW Lzlnzs+g4z6PEoDmR8lE1nkRc7oti6joTaB7etDI8HQZkRC0ePjc5gbDk q0BvxGNJsLsaXy0y8I/01cnFaWhR5jAro0VuFOG61hYkjokodQbCXm2G7 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAFprElGtJV2d/2dsb2JhbAA8CcBEFnOCHwEBAQQ6PwwGAQgRAwEBAQsUCTkUCQgBAQQBDQUIAYd2Aw8MvByMFoEEg2BhA5IuOoRWjzWCfoIk
X-IronPort-AV: E=Sophos;i="4.84,615,1355097600"; d="scan'208";a="174057860"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 06 Feb 2013 14:43:35 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r16EhYNB029031 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Feb 2013 14:43:34 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.232]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Wed, 6 Feb 2013 08:43:34 -0600
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Review of draft-ietf-mpls-tp-security-framework-07
Thread-Index: Ac3/mwU7IdpVSjk6TAG/2FHsTA3yZwEm2eIAAAqrFpAAB+e6gA==
Date: Wed, 6 Feb 2013 14:43:33 +0000
Message-ID: <0DB8F45437AB844CBB5102F807A0AD9310279877@xmb-rcd-x03.cisco.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA08300A@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [10.21.112.101]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DEBC9DE2030CF34CABD42C0A84D391E9@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "nabil.bitar@verizon.com" <nabil.bitar@verizon.com>, "ms-daikoku@kddi.com" <ms-daikoku@kddi.com>, "lei.wang@limenetworks.no" <lei.wang@limenetworks.no>, "ben@niven-jenkins.co.uk" <ben@niven-jenkins.co.uk>, "raymond.zhang@alcatel-lucent.com" <raymond.zhang@alcatel-lucent.com>, "scott.mansfield@ericsson.com" <scott.mansfield@ericsson.com>, "rfg@acm.org" <rfg@acm.org>, "henry.yu@twtelecom.com" <henry.yu@twtelecom.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-mpls-tp-security-framework-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: Wed, 06 Feb 2013 14:43:37 -0000

Dan,

Thank you again!
Luyuan

-----Original Message-----
From: <Romascanu>, "Dan   (Dan)" <dromasca@avaya.com>
Date: Wednesday, February 6, 2013 3:58 AM
To: Luyuan Fang <lufang@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "ben@niven-jenkins.co.uk" <ben@niven-jenkins.co.uk>,
"scott.mansfield@ericsson.com" <scott.mansfield@ericsson.com>,
"rfg@acm.org" <rfg@acm.org>, "raymond.zhang@alcatel-lucent.com"
<raymond.zhang@alcatel-lucent.com>, Nabil Bitar <nabil.bitar@verizon.com>,
"ms-daikoku@kddi.com" <ms-daikoku@kddi.com>, "henry.yu@twtelecom.com"
<henry.yu@twtelecom.com>, "lei.wang@limenetworks.no"
<lei.wang@limenetworks.no>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: RE: Gen-ART Review of draft-ietf-mpls-tp-security-framework-07

>Thank you for addressing my comments.
>
>From my perspective the document is now ready.
>
>Regards,=20
>
>Dan
>
>
>
>
>> -----Original Message-----
>> From: Luyuan Fang (lufang) [mailto:lufang@cisco.com]
>> Sent: Wednesday, February 06, 2013 7:52 AM
>> To: Romascanu, Dan (Dan); gen-art@ietf.org
>> Cc: ben@niven-jenkins.co.uk; scott.mansfield@ericsson.com; rfg@acm.org;
>> raymond.zhang@alcatel-lucent.com; nabil.bitar@verizon.com; ms-
>> daikoku@kddi.com; henry.yu@twtelecom.com; lei.wang@limenetworks.no;
>> adrian@olddog.co.uk
>> Subject: Re: Gen-ART Review of draft-ietf-mpls-tp-security-framework-07
>>=20
>> Hi Dan,
>>=20
>> Thank you very much for your review and detailed comments, really
>> appreciate your discussion and helpful suggestions.
>>=20
>> I updated the document, addressed all your comments. It is reflected in
>> the 08 version just posted.
>> http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-security-
>> framework-0
>> 8.txt
>>=20
>>=20
>> We acknowledged your help in the document.
>>=20
>> Please see in-line.
>>=20
>> -----Original Message-----
>> From: <Romascanu>, "Dan   (Dan)" <dromasca@avaya.com>
>> Date: Thursday, January 31, 2013 2:09 AM
>> To: "gen-art@ietf.org" <gen-art@ietf.org>
>> Cc: Luyuan Fang <lufang@cisco.com>, "ben@niven-jenkins.co.uk"
>> <ben@niven-jenkins.co.uk>, "scott.mansfield@ericsson.com"
>> <scott.mansfield@ericsson.com>, "rfg@acm.org" <rfg@acm.org>,
>> "raymond.zhang@alcatel-lucent.com" <raymond.zhang@alcatel-lucent.com>,
>> Nabil Bitar <nabil.bitar@verizon.com>, "ms-daikoku@kddi.com"
>> <ms-daikoku@kddi.com>, "henry.yu@twtelecom.com"
>> <henry.yu@twtelecom.com>, "lei.wang@limenetworks.no"
>> <lei.wang@limenetworks.no>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
>> Subject: Gen-ART Review of draft-ietf-mpls-tp-security-framework-07
>>=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>.
>> >
>> >Please resolve these comments along with any other Last Call comments
>> >you may receive.
>> >
>> >Document: draft-ietf-mpls-tp-security-framework-07
>> >Reviewer: Dan Romascanu
>> >Review Date: 1/31/13
>> >IETF LC End Date: 2/6/13
>> >IESG Telechat date: (if known)
>> >
>> >Summary: Ready with Issues
>> >
>> >This is a short, well-written and useful document that supplements RFC
>> >5920 with information on reference models, security threats and defense
>> >techniques specific to MPLS-TP. There is one major issue which I
>> >believe should be fixed and is not too difficult to fix if the authors
>> agree.
>> >
>> >Major issues:
>> >
>> >One of the major features of extending MPLS in MPLS-TP is rightly
>> >identified in the words of the Abstract as the 'strong emphasis on
>> >static provisioning supported by network management systems'. However
>> >Sections 3 and 4 miss to describe accurately the threats introduced by
>> >provisioning tools and the defensive techniques that need to be put in
>> >place in order to address these threats.
>> >
>> >Section 3 speaks about 'attacks to NMS' but this is quite vague (what
>> >kind of attacks?) and incomplete, as it is not only the NMS that can be
>> >attacked but also the communication between the NMS and the routers
>> >that are being provisioned, as well as the access of the users to the
>> >provisioning tools. Threats like disclosure of information, masquerade
>> >(as NMS) or access of unauthorized users to the provisioning
>> >information and controls need to be clearly articulated here.
>>=20
>> [luyuan] Good points. In Section 3, the following text is added (after
>> the paragraph talks "attacks to NMS"):
>>=20
>>=20
>> Attacks to NMS may come from external attackers, or insiders. Outside
>> attacks are initiated outside of the trusted zone by unauthorized user
>> of the MPLS-TP network management systems. Insider attack is initiated
>> from inside of the trusted zone by an entity with authorized access to
>> the management systems, but performs unapproved harmful functions to the
>> MPLS-TP networks. These attacks may be directly targeted to the NMS, or
>> via the compromised communication channels between the NMS and the
>> network devices that are being provisioned, or through the access of the
>> users to the provisioning tools. The security threat may include
>> disclosure of information, generating false OAM messages, taking down
>> MPLS-TP LSPs, connecting to the wrong MPLS-TP tunnel end points, and DoS
>> attacks to the MPLS-TP networks.
>>=20
>>=20
>> >
>> >
>> >In Section 4 the corresponding defensive techniques need to be listed,
>> >or at least make clear that techniques like entity authentication for
>> >identity verification, encryption for confidentiality, message
>> >integrity and replay detection to ensure the validity of message
>> >streams, as well as users access control and events logging need to
>> >apply also for NMS applications and provisioning traffic.
>>=20
>> >
>> [luyuan] Agreed. The following paragraph is added at the end of the
>> section 4, pretty much based on your suggestions.
>>=20
>> It is important to point out the following security defense techniques
>> which are particularly critical for NMS due to the strong emphasis on
>> static provisioning supported by NMS in MPLS-TP deployment. These
>> techniques include: Entity authentication for identity verification,
>> encryption for confidentiality, message integrity and replay detection
>> to ensure the validity of message streams, as well as users access
>> control and events logging which must be applied for NMS and
>> provisioning applications.
>> >
>> >Minor issues:
>> >
>> >Nits/editorial comments:
>> >
>> >1. Several acronyms are not expanded at first occurrence: PE/T-PE, GAL
>>=20
>> [luyuan] Fixed. We initially had terminology section, it was taken out
>> during the last call discussion. I added the section back with a new
>> list of terms that are relevant to this document.
>> >
>> >2. Inconsistent abbreviation: T-PE in the text, TPE in figures 2-5
>>=20
>> [luyuan] Fixed.
>> >
>> >3. The first sentence in Section 3 seems broken grammatically:
>> >
>> >> This section discuss various network security threats which are to
>> >   MPLS-TP and may endanger MPLS-TP networks.
>>=20
>> [luyuan] Fixed.
>> New text: This section discusses various network security threats that
>> are unique to MPLS-TP and may endanger MPLS-TP networks.
>> >
>> >
>> Thanks,
>> Luyuan
>


From housley@vigilsec.com  Wed Feb  6 11:39:00 2013
Return-Path: <housley@vigilsec.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 D084B21F8A52 for <gen-art@ietfa.amsl.com>; Wed,  6 Feb 2013 11:39:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bjGD5M1XGMTh for <gen-art@ietfa.amsl.com>; Wed,  6 Feb 2013 11:39:00 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 535A621F8A42 for <gen-art@ietf.org>; Wed,  6 Feb 2013 11:39:00 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id F2FCC9A4013; Wed,  6 Feb 2013 14:39:07 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 6vZZw99n+dmS; Wed,  6 Feb 2013 14:38:50 -0500 (EST)
Received: from v150.vpn.iad.rg.net (v150.vpn.iad.rg.net [198.180.150.150]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3F2849A4020; Wed,  6 Feb 2013 14:39:05 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <D3D42C39-041A-4DB1-8730-A9A1143A2209@vigilsec.com>
Date: Wed, 6 Feb 2013 14:38:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4A11B85-801D-41DB-A804-49A916BD1AD5@vigilsec.com>
References: <4FD37E36.9080203@isode.com> <D3D42C39-041A-4DB1-8730-A9A1143A2209@vigilsec.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1085)
Cc: draft-ietf-geopriv-dhcp-lbyr-uri-option.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>
Subject: Re: [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: Wed, 06 Feb 2013 19:39:00 -0000

Alexey:

The telechat is less that 24 hours away.  I hope you are online and can =
reply soon.

Russ


On Feb 4, 2013, at 2:01 PM, Russ Housley wrote:

> Alexey:
>=20
> I have not seen a reply to this review.  Are your concerns resolved in =
the current version?
>=20
> Russ
>=20
> On Jun 9, 2012, at 12:47 PM, Alexey Melnikov 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 resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> 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)
>>=20
>> Summary: This document is nearly ready for publication as a Proposed =
Standard.
>>=20
>> Major issues: None
>>=20
>> Minor issues:
>>=20
>> 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.
>>=20
>> In Section 2.3: LuriType =3D1 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).
>>=20
>> LuriType=3D2: in network byte order?
>>=20
>> In Section 3.2: "data:" URI needs an Informative reference (RFC =
2397).
>>=20
>> In Section 3.3: all media types mentioned (two?) need Normative =
references.
>>=20
>>=20
>> Nits/editorial comments:
>>=20
>> In Section 3, 2nd to the last para: s/deference/dereference ?
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From alexey.melnikov@isode.com  Thu Feb  7 02:38:03 2013
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 D4DA121F855C for <gen-art@ietfa.amsl.com>; Thu,  7 Feb 2013 02:38:03 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C7i96VuP6O1t for <gen-art@ietfa.amsl.com>; Thu,  7 Feb 2013 02:38:03 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 3F8F921F855A for <gen-art@ietf.org>; Thu,  7 Feb 2013 02:38:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1360233482; d=isode.com; s=selector; i=@isode.com; bh=dz58X4X8U8WiKQM+g3LDcgdV0fjG+w+KuZJDwpk2s90=; 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=ldoXxDmtWM3sdQIGZNMKDSqzI1QyaCysONtvzWJ9xmJyyT73eLp0pQfbXfBDmYvLS0ExlW pNYp7J2d4h8YnsxoTWNTmm07SX2lfPgk+X04ksAxAExlp7vXG7GgOzcelsXhI9uC6tCWbe n19l9T4rM3RZFAqbFi4k1unQupHNS1c=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <UROECAAYIXrd@statler.isode.com>; Thu, 7 Feb 2013 10:38:02 +0000
Message-ID: <51138447.8070604@isode.com>
Date: Thu, 07 Feb 2013 10:39:03 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: Russ Housley <housley@vigilsec.com>
References: <4FD37E36.9080203@isode.com> <D3D42C39-041A-4DB1-8730-A9A1143A2209@vigilsec.com>
In-Reply-To: <D3D42C39-041A-4DB1-8730-A9A1143A2209@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-geopriv-dhcp-lbyr-uri-option.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>
Subject: Re: [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: Thu, 07 Feb 2013 10:38:03 -0000

On 04/02/2013 19:01, Russ Housley wrote:
> Alexey:
>
> I have not seen a reply to this review.  Are your concerns resolved in the current version?
Sorry, missed that earlier: half of them were resolved. I post an 
updated review.


From alexey.melnikov@isode.com  Thu Feb  7 02:52:39 2013
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 0FB5821F845A; Thu,  7 Feb 2013 02:52:39 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nMhtxyjEpeDL; Thu,  7 Feb 2013 02:52:38 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 4B1A121F8481; Thu,  7 Feb 2013 02:52:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1360234357; d=isode.com; s=selector; i=@isode.com; bh=lg0Q7q0fl1aNgYd8MuTy8fRoKj/hj+M4YOasuWD7akk=; 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=nrPOENrSCaszl854faCoPofbjRsGkHBRxgnECShvug/IjiHnmPL3MZMycVWL3Vx8+5fQ5H qHuxj0Snk2RRIuOpjBKj2HtAoEv+6NZXrNQsl6BTwgBr+ICsW2RZf2sQyPcHfoKFqDvj+j lX9RNSmvJ4nqbEKpcUECI6ZcchPWOrM=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <UROHdAAYIWkE@statler.isode.com>; Thu, 7 Feb 2013 10:52:37 +0000
Message-ID: <511387B3.7040807@isode.com>
Date: Thu, 07 Feb 2013 10:53:39 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
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, iesg@ietf.org
Subject: [Gen-art] Gen-ART (telechat) review of draft-ietf-geopriv-dhcp-lbyr-uri-option-18
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 Feb 2013 10:52:39 -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-18
Reviewer: Alexey Melnikov
Review Date: 2013-02-07
IETF LC End Date: 2013-02-07
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 3.2: "data:" URI needs an Informative reference (RFC 2397).

In the same section I see:

    o Section 3.3 IANA registers acceptable location URI schemes (or
      types) for use by this specification. Clients MUST reject URI
      schemes not currently registered in IANA.

The last sentence looks wrong. Firstly, you already restrict the list of 
acceptable URIs to the list specified in Section 3.3. Secondly, what 
does this requirement mean exactly? Is the client required to fetch the 
list of registered URIs from iana.org (I hope not)? I suggest just 
deleting the last sentence.

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


From Michael.Baer@sparta.com  Thu Feb  7 13:44:04 2013
Return-Path: <Michael.Baer@sparta.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 D3AA321F86F5 for <gen-art@ietfa.amsl.com>; Thu,  7 Feb 2013 13:44:04 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2D3rAwJq2wD for <gen-art@ietfa.amsl.com>; Thu,  7 Feb 2013 13:44:01 -0800 (PST)
Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by ietfa.amsl.com (Postfix) with ESMTP id C573721F86CC for <gen-art@ietf.org>; Thu,  7 Feb 2013 13:44:01 -0800 (PST)
Received: from Beta5.sparta.com (beta5.sparta.com [157.185.63.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id r17Lhr27023170; Thu, 7 Feb 2013 15:43:53 -0600
Received: from tanis.huntsville.ads.sparta.com ([157.185.63.118]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id r17LhmXZ005304; Thu, 7 Feb 2013 15:43:53 -0600
Received: from localhost (157.185.61.22) by tanis.huntsville.ads.sparta.com (157.185.63.118) with Microsoft SMTP Server (TLS) id 14.2.247.3; Thu, 7 Feb 2013 15:43:46 -0600
From: Michael Baer <michael.baer@sparta.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: SPARTA NSS
References: <50FAD3A6.9020704@gmail.com>
X-Face: 
Date: Thu, 7 Feb 2013 13:43:44 -0800
In-Reply-To: <50FAD3A6.9020704@gmail.com> (Brian E. Carpenter's message of "Sat, 19 Jan 2013 17:11:02 +0000")
Message-ID: <87obfvkdf3.fsf@rebma.mikesoffice.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Mailman-Approved-At: Thu, 07 Feb 2013 14:04:38 -0800
Cc: draft-ietf-sidr-rpki-rtr-protocol-mib.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-sidr-rpki-rtr-protocol-mib-04.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 Feb 2013 22:03:29 -0000

Hi Brian,

We submitted an update draft earlier I have changes in the update
related to your comments inline below.

>>>>> On Sat, 19 Jan 2013 17:11:02 +0000, Brian E Carpenter <brian.e.carpenter@gmail.com> said:

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

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

    BC> Document: draft-ietf-sidr-rpki-rtr-protocol-mib-04.txt Reviewer:
    BC> Brian Carpenter Review Date: 2013-01-19 IETF LC End Date:
    BC> 2013-01-14 IESG Telechat date: 2013-01-24

    BC> Summary: In good shape, two open issues pending from LC
    BC> review.  --------

    BC> Comment: --------

    BC> I see a note in the tracker that the MIB Doctor review "still
    BC> needs to happen".  However, one of the authors is a MIB doctor.

    BC> Major issue: ------------

    BC> In draft-ietf-sidr-rpki-rtr-26 the list of caches is stated to
    BC> include

    BC>   Name: The IP Address or fully qualified domain name of the
    BC> cache.

    BC> I find no way to represent the FQDN option in the MIB module. We
    BC> state explicitly in the 6renum documents that it should be
    BC> possible to configure network elements using names in preference
    BC> to addresses, so I think this is a problem. Of course, at run
    BC> time, the FQDN will have been resolved into an address, but why
    BC> isn't there also an FQDN object in the MIB module?  I had a
    BC> reply on this topic from one of the authors, but there has been
    BC> no updated draft:
    BC> http://www.ietf.org/mail-archive/web/gen-art/current/msg08031.html

We changed the InetAddressType objects in the draft.  They are no longer
limited by this MIB as to what they can support.  The compliance
statement was also changed to required support for ipv4, ipv6 and dns
types for the InetAddressType objects, i.e. a FQDN can be represented
now.

    BC> Minor issue: ------------

    BC> In draft-ietf-sidr-rpki-rtr-26 the preference is defined as

    BC>  Preference: An unsigned integer denoting the router's
    BC> preference to connect to that cache, the lower the value the
    BC> more preferred.

    BC> That doesn't specify a range. The MIB specifies the range as
    BC> 0..255:

    BC>    rpkiRtrCacheServerPreference OBJECT-TYPE SYNTAX Unsigned32
    BC> (0..255)

    BC> Is this an oversight in draft-ietf-sidr-rpki-rtr? If not, it
    BC> seems necessary to state what should be in the MIB object if
    BC> preference>255.

This object was changed to not have the 255 limit (just the inherit max
value for its Unsigned32 type now).

    BC> "Two Notification have been defined..."
    BC> s/Notification/Notifications/

Missed this fix in the update.

Thanks,
Mike

-- 
Michael Baer
Senior Research Scientist
SPARTA National Security Sector
michael.baer@sparta.com
C:530.902.3131

From jmpolk@cisco.com  Thu Feb  7 14:41:04 2013
Return-Path: <jmpolk@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 7F78D1F0D08; Thu,  7 Feb 2013 14:41:04 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKXRpWm2xpsy; Thu,  7 Feb 2013 14:41:03 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 963DB1F0CFF; Thu,  7 Feb 2013 14:40:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1558; q=dns/txt; s=iport; t=1360276864; x=1361486464; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=l+dIDAOkF8liDaqZohU9xUgOINpuanzggJ0Sa5hV39A=; b=c4gZD8LczIvnnsWSz5PaGysq5YzKlwzv9As8RH1bcB5uiD2g6+6Qhx2M GPeuoI/9KXJnxKzUqDAOF75rUVxyCX4WasgqdFkVkRopN7sd5/SmngUfZ /5Z7EmC/Ka3TX2NPMujU44fpM5N/wulk9xL82aQJ1szNpmz7IMaMXjVi9 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EANwsFFGtJV2c/2dsb2JhbABFwHEWc4IfAQEBBDgCPxAHBBQECRUQDwo+BgGIIwzAHpFcA4hmjliPNYMf
X-IronPort-AV: E=Sophos;i="4.84,625,1355097600"; d="scan'208";a="174673001"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 07 Feb 2013 22:40:55 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) (authenticated bits=0) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r17Mesim014145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Feb 2013 22:40:54 GMT
Message-Id: <201302072240.r17Mesim014145@rcdn-core-5.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 07 Feb 2013 16:40:52 -0600
To: Alexey Melnikov <alexey.melnikov@isode.com>, <draft-ietf-geopriv-dhcp-lbyr-uri-option.all@tools.ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <511387B3.7040807@isode.com>
References: <511387B3.7040807@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: gen-art@ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART (telechat) review of draft-ietf-geopriv-dhcp-lbyr-uri-option-18
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 Feb 2013 22:41:04 -0000

At 04:53 AM 2/7/2013, Alexey Melnikov 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-geopriv-dhcp-lbyr-uri-option-18
>Reviewer: Alexey Melnikov
>Review Date: 2013-02-07
>IETF LC End Date: 2013-02-07
>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.

which RFC would you like me to reference?


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

done


>In the same section I see:
>
>    o Section 3.3 IANA registers acceptable location URI schemes (or
>      types) for use by this specification. Clients MUST reject URI
>      schemes not currently registered in IANA.
>
>The last sentence looks wrong. Firstly, you already restrict the 
>list of acceptable URIs to the list specified in Section 3.3. 
>Secondly, what does this requirement mean exactly? Is the client 
>required to fetch the list of registered URIs from iana.org (I hope 
>not)? I suggest just deleting the last sentence.

removed


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

done

James




From barryleiba@gmail.com  Thu Feb  7 15:00:39 2013
Return-Path: <barryleiba@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 F2C7811E80A2; Thu,  7 Feb 2013 15:00:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tj4THcoaonda; Thu,  7 Feb 2013 15:00:38 -0800 (PST)
Received: from mail-la0-x235.google.com (la-in-x0235.1e100.net [IPv6:2a00:1450:4010:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 26B9E11E809C; Thu,  7 Feb 2013 15:00:37 -0800 (PST)
Received: by mail-la0-f53.google.com with SMTP id fr10so3149659lab.40 for <multiple recipients>; Thu, 07 Feb 2013 15:00:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=VfjOOE5eP5dZ9sJ/jzrm/fkPkkACJ+ixcPI8yaNtBIE=; b=Pelg/ms0RD9Sw3oFNChEHU0plXIxcuCvSae4K5RViBAHMi8mFy0jcT2c8K3564D6u6 XbAZU/MqOeDPWXIB8at+mVd55/vQMbH9pDK4Iv9kEbsEuq/ELe72mNYBbQyLLPVieu2T vI15bD6DUD+/iOM0BC3Us8MdH3NarBW2nTvahuLrwF1gaPC1mHQBefe1MGdZhykAdNeo zXDx7KVXaq0bTMayEX68UdCKZkBKEx+8QNxH7AE1DAOaiSGe4iiggxdAmCkVOEkFCjYp NOgph/GIcht8j63PmHMImhzEbgp0rWwCHifWI8zuf6sdTs7sWPkE4MvaSC2t8n/s9GZi 67uw==
MIME-Version: 1.0
X-Received: by 10.112.47.168 with SMTP id e8mr1462446lbn.46.1360278036917; Thu, 07 Feb 2013 15:00:36 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.112.47.168 with HTTP; Thu, 7 Feb 2013 15:00:36 -0800 (PST)
In-Reply-To: <201302072240.r17Mesim014145@rcdn-core-5.cisco.com>
References: <511387B3.7040807@isode.com> <201302072240.r17Mesim014145@rcdn-core-5.cisco.com>
Date: Thu, 7 Feb 2013 18:00:36 -0500
X-Google-Sender-Auth: D9LGHXktR_uTdwk1cgglHeZG75s
Message-ID: <CALaySJKdaCRTu7GMPcUZ+K2ofNHPOmj38c=BznNqWTxe6SQwKw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: James Polk <jmpolk@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-ietf-geopriv-dhcp-lbyr-uri-option.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART (telechat) review of draft-ietf-geopriv-dhcp-lbyr-uri-option-18
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 Feb 2013 23:00:39 -0000

>> 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.
>
> which RFC would you like me to reference?

RFC 3986 is the canonical reference for URIs.

Barry

From jmpolk@cisco.com  Thu Feb  7 15:20:47 2013
Return-Path: <jmpolk@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 46E4721F8599; Thu,  7 Feb 2013 15:20:47 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uVKGagDijubM; Thu,  7 Feb 2013 15:20:46 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 4E67321F8620; Thu,  7 Feb 2013 15:20:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1734; q=dns/txt; s=iport; t=1360279246; x=1361488846; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=5wV+UJApImVxiG60Hx4c+30fmP7XIiJOSlebNfZu93Y=; b=gqFfcxHq5bJxygYbDejZiX23LBSwqXr4fjeVIOs5rUTP6Zf7wAM+V8A+ aAQb/cKy1g0mSaCVfxoZmIDt/rZ9g7KLb7aMwhKZlNz5LDUfcH3Qpe6Kp oOxwJ6RoipqIH/LoTlDWnBjPH9o6ZyPaqHyQ2MZRfVXDFyMw0tyvuFxPm k=;
X-IronPort-AV: E=Sophos;i="4.84,625,1355097600"; d="scan'208";a="174724944"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-4.cisco.com with ESMTP; 07 Feb 2013 23:20:46 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) (authenticated bits=0) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r17NKjto012539 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Feb 2013 23:20:45 GMT
Message-Id: <201302072320.r17NKjto012539@rcdn-core2-6.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 07 Feb 2013 17:20:43 -0600
To: Alexey Melnikov <alexey.melnikov@isode.com>, <draft-ietf-geopriv-dhcp-lbyr-uri-option.all@tools.ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <201302072240.r17Mesim014145@rcdn-core-5.cisco.com>
References: <511387B3.7040807@isode.com> <201302072240.r17Mesim014145@rcdn-core-5.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: gen-art@ietf.org, James Polk <jmpolk@cisco.com>, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART (telechat) review of draft-ietf-geopriv-dhcp-lbyr-uri-option-18
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 Feb 2013 23:20:47 -0000

At 04:40 PM 2/7/2013, James Polk wrote:
>At 04:53 AM 2/7/2013, Alexey Melnikov 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-geopriv-dhcp-lbyr-uri-option-18
>>Reviewer: Alexey Melnikov
>>Review Date: 2013-02-07
>>IETF LC End Date: 2013-02-07
>>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.
>
>which RFC would you like me to reference?

Thanks to Barry (pointing me towards RFC 3986), this one is now done.



>>In Section 3.2: "data:" URI needs an Informative reference (RFC 2397).
>
>done
>
>
>>In the same section I see:
>>
>>    o Section 3.3 IANA registers acceptable location URI schemes (or
>>      types) for use by this specification. Clients MUST reject URI
>>      schemes not currently registered in IANA.
>>
>>The last sentence looks wrong. Firstly, you already restrict the 
>>list of acceptable URIs to the list specified in Section 3.3. 
>>Secondly, what does this requirement mean exactly? Is the client 
>>required to fetch the list of registered URIs from iana.org (I hope 
>>not)? I suggest just deleting the last sentence.
>
>removed
>
>
>>In Section 3.3: all media types mentioned (two?) need Normative references.
>
>done
>
>James
>
>


From mahoney@nostrum.com  Thu Feb  7 16:38:50 2013
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 A344921F89CB for <gen-art@ietfa.amsl.com>; Thu,  7 Feb 2013 16:38:50 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zUjZGUyZEOc4 for <gen-art@ietfa.amsl.com>; Thu,  7 Feb 2013 16:38:50 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id EE98221F89D5 for <gen-art@ietf.org>; Thu,  7 Feb 2013 16:38:49 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r180cnhD019011 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 7 Feb 2013 18:38:49 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <51144918.8050602@nostrum.com>
Date: Thu, 07 Feb 2013 18:38:48 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
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 (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-02-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 Feb 2013 00:38:50 -0000

Hi all,

The following reviewers have assignments:


Reviewer          LC end       Draft
---------------------------------------------------------------------
Alexey Melnikov   2013-02-18   draft-ietf-mpls-tp-ethernet-addressing-05

Ben Campbell      2013-02-18   draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04

Brian Carpenter   2013-03-06   draft-arkko-iesg-crossarea-02

Christer Holmberg 2013-02-20   draft-templin-intarea-seal-51

Dan Romascanu     2013-02-24   draft-cardenas-dff-09

Mary Barnes       2013-02-19   draft-ietf-p2psip-base-24 *

Roni Even         2013-02-19   draft-ietf-ancp-pon-04 *

Wassim Haddad     2013-02-15   draft-ietf-paws-problem-stmt-usecases-rqmts-12

* 2nd Last Call


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

And 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


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  Thu Feb  7 23:59:01 2013
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 5440821F8972 for <gen-art@ietfa.amsl.com>; Thu,  7 Feb 2013 23:59:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.545
X-Spam-Level: 
X-Spam-Status: No, score=-99.545 tagged_above=-999 required=5 tests=[AWL=-0.624, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hw1Yc5jGFH3v for <gen-art@ietfa.amsl.com>; Thu,  7 Feb 2013 23:59:00 -0800 (PST)
Received: from mail-we0-x235.google.com (we-in-x0235.1e100.net [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 5E3A321F8964 for <gen-art@ietf.org>; Thu,  7 Feb 2013 23:59:00 -0800 (PST)
Received: by mail-we0-f181.google.com with SMTP id t44so2752464wey.12 for <gen-art@ietf.org>; Thu, 07 Feb 2013 23:58:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XCOjyDpwGmeG9pxbmUXa8mAQ4vo6/LocdjDH8NcoUfs=; b=fYizOtKDyr1aFJTs+FTO5K46/4SPIqFC8ciI/PO5UtERXePqiNcTSOtxx/VuPRbfk5 CSCVKobWCgZ7o6AyhgKnZr25kcBYtCSPgQV92MZLEAdLfUFW4ixeO2zQiUtoTbjg7xAt fK0a1FN69DTZIqvOGO9Mdw4f7MADDeTMvvdqhkyxLDBRKKfOuvolNHh0vXpO/KU3g84A 4Aj0YQv7oNrSyRstMZ8bYBBCwdMRfPhDgyjbBzPCCzO73afMmlqgPc4d2fgGPscGh2RG d56BWlDhuKnOyhtlvv86KeLE0mqYF4PWLlbvgIROoRfKBlhv/fUTSqXaMiVlzlBQqx7c lCHQ==
X-Received: by 10.194.92.65 with SMTP id ck1mr7677251wjb.54.1360310339490; Thu, 07 Feb 2013 23:58:59 -0800 (PST)
Received: from [192.168.1.65] (host-2-101-188-26.as13285.net. [2.101.188.26]) by mx.google.com with ESMTPS id e6sm13816127wiz.1.2013.02.07.23.58.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 07 Feb 2013 23:58:58 -0800 (PST)
Message-ID: <5114B04A.7050006@gmail.com>
Date: Fri, 08 Feb 2013 07:59:06 +0000
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: Michael Baer <michael.baer@sparta.com>
References: <50FAD3A6.9020704@gmail.com> <87obfvkdf3.fsf@rebma.mikesoffice.com>
In-Reply-To: <87obfvkdf3.fsf@rebma.mikesoffice.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-sidr-rpki-rtr-protocol-mib.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-sidr-rpki-rtr-protocol-mib-04.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, 08 Feb 2013 07:59:01 -0000

Hi Michael, yes thanks, that fixes my issues.

I guess the authors of RFC 4001 knew what they were doing when they wrote:

         To support future extensions, the InetAddressType textual
         convention SHOULD NOT be sub-typed in object type definitions.
         It MAY be sub-typed in compliance statements in order to
         require only a subset of these address types for a compliant
         implementation.

Regards
   Brian Carpenter

On 07/02/2013 21:43, Michael Baer wrote:
> Hi Brian,
> 
> We submitted an update draft earlier I have changes in the update
> related to your comments inline below.
> 
>>>>>> On Sat, 19 Jan 2013 17:11:02 +0000, Brian E Carpenter <brian.e.carpenter@gmail.com> said:
> 
>     BC> I have been selected as the General Area Review Team (Gen-ART)
>     BC> reviewer for this draft (for background on Gen-ART, please see
>     BC> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
> 
>     BC> Please wait for direction from your document shepherd or AD
>     BC> before posting a new version of the draft.
> 
>     BC> Document: draft-ietf-sidr-rpki-rtr-protocol-mib-04.txt Reviewer:
>     BC> Brian Carpenter Review Date: 2013-01-19 IETF LC End Date:
>     BC> 2013-01-14 IESG Telechat date: 2013-01-24
> 
>     BC> Summary: In good shape, two open issues pending from LC
>     BC> review.  --------
> 
>     BC> Comment: --------
> 
>     BC> I see a note in the tracker that the MIB Doctor review "still
>     BC> needs to happen".  However, one of the authors is a MIB doctor.
> 
>     BC> Major issue: ------------
> 
>     BC> In draft-ietf-sidr-rpki-rtr-26 the list of caches is stated to
>     BC> include
> 
>     BC>   Name: The IP Address or fully qualified domain name of the
>     BC> cache.
> 
>     BC> I find no way to represent the FQDN option in the MIB module. We
>     BC> state explicitly in the 6renum documents that it should be
>     BC> possible to configure network elements using names in preference
>     BC> to addresses, so I think this is a problem. Of course, at run
>     BC> time, the FQDN will have been resolved into an address, but why
>     BC> isn't there also an FQDN object in the MIB module?  I had a
>     BC> reply on this topic from one of the authors, but there has been
>     BC> no updated draft:
>     BC> http://www.ietf.org/mail-archive/web/gen-art/current/msg08031.html
> 
> We changed the InetAddressType objects in the draft.  They are no longer
> limited by this MIB as to what they can support.  The compliance
> statement was also changed to required support for ipv4, ipv6 and dns
> types for the InetAddressType objects, i.e. a FQDN can be represented
> now.
> 
>     BC> Minor issue: ------------
> 
>     BC> In draft-ietf-sidr-rpki-rtr-26 the preference is defined as
> 
>     BC>  Preference: An unsigned integer denoting the router's
>     BC> preference to connect to that cache, the lower the value the
>     BC> more preferred.
> 
>     BC> That doesn't specify a range. The MIB specifies the range as
>     BC> 0..255:
> 
>     BC>    rpkiRtrCacheServerPreference OBJECT-TYPE SYNTAX Unsigned32
>     BC> (0..255)
> 
>     BC> Is this an oversight in draft-ietf-sidr-rpki-rtr? If not, it
>     BC> seems necessary to state what should be in the MIB object if
>     BC> preference>255.
> 
> This object was changed to not have the 255 limit (just the inherit max
> value for its Unsigned32 type now).
> 
>     BC> "Two Notification have been defined..."
>     BC> s/Notification/Notifications/
> 
> Missed this fix in the update.
> 
> Thanks,
> Mike
> 

From brian.e.carpenter@gmail.com  Sat Feb  9 06:53:45 2013
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 17F6521F8734 for <gen-art@ietfa.amsl.com>; Sat,  9 Feb 2013 06:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.739
X-Spam-Level: 
X-Spam-Status: No, score=-99.739 tagged_above=-999 required=5 tests=[AWL=-0.818, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8AiTS3cyj0eF for <gen-art@ietfa.amsl.com>; Sat,  9 Feb 2013 06:53:44 -0800 (PST)
Received: from mail-we0-x22e.google.com (we-in-x022e.1e100.net [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id DA83121F86CE for <gen-art@ietf.org>; Sat,  9 Feb 2013 06:53:43 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id r6so3759443wey.33 for <gen-art@ietf.org>; Sat, 09 Feb 2013 06:53:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type; bh=yy3d0FgqC8L1ntMezkm3oPDD7ZAv/BZYnVvOCe4xC50=; b=eYH1Qh+Ypf1FUa/i3BECH44oP9MrWSRA99tZ5kS3tHknOCK7aT9h6fMcvh5iiVldMo dEx9jlPQx0UgHYpUIQEedAuHpABwoui5ORQRQXG4VYUJyJdN++hHKMiyHIBbdGTMPzkS G2Y88SfsloflzxAdnC73mP+MkyBuGop48GgYxG6k/Yyb7tcISqopWzutIeGNV3AswZzD aQi82haId67J9iOhAyvAK75U2DlnGGKCh7N52JdVS2EzNJHEu14h4NgC/n9cEnH48kTX 70NKG9F6xVlMHMmI1tT16ET0pYndPN13EetjufZEeIGjcii014DXT/Rm0D5Kvn814ULA geFA==
X-Received: by 10.194.178.33 with SMTP id cv1mr15224885wjc.46.1360421616548; Sat, 09 Feb 2013 06:53:36 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-25.as13285.net. [2.102.219.25]) by mx.google.com with ESMTPS id cu7sm19850463wib.8.2013.02.09.06.53.34 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 09 Feb 2013 06:53:35 -0800 (PST)
Message-ID: <511662FE.7000103@gmail.com>
Date: Sat, 09 Feb 2013 14:53:50 +0000
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-arkko-iesg-crossarea.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------080509020102050707090407"
Subject: [Gen-art] Gen-ART LC review of draft-arkko-iesg-crossarea-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: Sat, 09 Feb 2013 14:53:45 -0000

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

Please see attached review.

     Brian



--------------080509020102050707090407
Content-Type: text/plain;
 name="draft-arkko-iesg-crossarea-03-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-arkko-iesg-crossarea-03-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBM
YXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IGRyYWZ0
LWFya2tvLWllc2ctY3Jvc3NhcmVhLTAzLnR4dA0KUmV2aWV3ZXI6IEJyaWFuIENhcnBlbnRl
cg0KUmV2aWV3IERhdGU6IDIwMTMtMDItMDkNCklFVEYgTEMgRW5kIERhdGU6IDIwMTMtMDMt
MDYNCklFU0cgVGVsZWNoYXQgZGF0ZTogMjAxMy0NCg0KU3VtbWFyeTogIE9uIHRoZSByaWdo
dCBsaW5lcw0KLS0tLS0tLS0NCg0KTWFqb3IgSXNzdWVzOiAgDQotLS0tLS0tLS0tLS0tDQoN
Cj4gQXJlYSBTaG9wcGluZw0KDQpJJ20gbm90IGVudGlyZWx5IGhhcHB5IHdpdGggdGhpcyBk
aXNjdXNzaW9uLiBGcm9tIHRoZSBwb2ludCBvZiB2aWV3IG9mIHRoZQ0KcGVyc29uIHRyeWlu
ZyB0byBpbnRyb2R1Y2luZyBhIG5ldyB0b3BpYyB0aGF0IGRvZXMgaW5kZWVkIGNyb3NzIGFy
ZWFzLCBpdCBpcw0KKmluZXZpdGFibGUqIHRvIGNvbW1pdCB0aGUgc2luIG9mIGFyZWEgc2hv
cHBpbmcuIDxzaG91dD5UaGlzIGlzIG5vdCBhIGZhdWx0IG9mDQp0aGUgc2hvcHBlcjsgaXQn
cyB0aGUgZmF1bHQgb2YgdGhlIElFVEYgZm9yIGhhdmluZyBhcmVhcyBpbiB0aGUgZmlyc3Qg
cGxhY2UuPC9zaG91dD4NCg0KSSBhZ3JlZSB0aGF0IGl0J3MgdGhlIElFU0cncywgYW5kIGFs
c28gdGhlIElBQidzLCBqb2IgdG8gcmVzb2x2ZSB0aGlzIHdoZW4NCml0IGFyaXNlcy4gQnV0
IHRoZSBjdXJyZW50IHRleHQgbWFrZXMgaXQgc291bmQgYXMgaWYgdGhlIHByb3RhZ29uaXN0
IGlzIHRvDQpibGFtZSBmb3IgYnJpbmdpbmcgYSBjcm9zcy1hcmVhIHByb2JsZW0gdG8gdGhl
IElFVEYuDQoNClRoZXJlIGFsc28gc2VlbXMgdG8gYmUgYSBtaXNzaW5nIHRvcGljLCBoZXJl
IGFuZCBpbiB0aGUgcmVjb21tZW5kYXRpb25zOg0KdGhlIGltcG9ydGFuY2Ugb2YgdGhlIEJP
RiAoYW5kIGJhciBCT0YpIHByb2Nlc3MsIGFuZCB0b3BpYyByZXZpZXcgYnkgdGhlDQpJQUIs
IGluIGlkZW50aWZ5aW5nIGNyb3NzLWFyZWEgdG9waWNzIGFuZCBjaGFydGVyaW5nIHRoZW0g
Y2FyZWZ1bGx5LiBUaGUNCndvcnN0IHRoaW5nIHRoYXQgY2FuIGhhcHBlbiBpcyB0byBCT0Yg
YW5kIGNoYXJ0ZXIgYSB0b3BpYyB3aXRoaW4gb25lIGFyZWEsDQpidXQgZGlzY292ZXIgbGF0
ZXIgdGhhdCBpdCBpcyBpbiBmYWN0IGEgY3Jvc3MtYXJlYSB0b3BpYy4gVGhlcmUgYXJlDQpy
ZWxldmFudCBSRkNzOiA1NDM0LCA2NzcxLg0KDQpNaW5vciBJc3N1ZXM6ICANCi0tLS0tLS0t
LS0tLS0NCg0KPiAyLiAgRXhhbXBsZXMgb2YgQ3Jvc3MtQXJlYSBXb3JrDQo+DQo+ICAgTWFu
eSBJRVRGIGVmZm9ydHMgY3Jvc3MgYXJlYSBib3VuZGFyaWVzLiAgU29tZSByZWNlbnQgZXhh
bXBsZXMgb2YNCj4gICBzdWNoIHdvcmsgaW5jbHVkZToNCj4NCj4gICBvICBUaGUgZGV2ZWxv
cG1lbnQgb2YgYSByb3V0aW5nLXByb3RvY29sIGJhc2VkIGJyaWRnaW5nIG1vZGVsLiAgVGhp
cw0KPiAgICAgIHdvcmsgaGFzIGJlZW4gZ29pbmcgb24gaW4gdGhlIFRSSUxMIFdHIG9uIHRo
ZSBJbnRlcm5ldCBBcmVhIGFuZCBpbg0KPiAgICAgIHBhcmFsbGVsIGluIHRoZSBJU0lTIFdH
IG9uIHRoZSBSb3V0aW5nIEFyZWEuDQoNCkEgdmVyeSBpbXBvcnRhbnQgYXNwZWN0IG9mIHRo
aXMgZXhhbXBsZSBpcyB0aGF0IGl0ICphbHNvKiBvdmVybGFwcyB3aXRoIElFRUUgd29yay4N
ClRoYXQgc2NlbmFyaW8gc2hvdWxkIHN1cmVseSBiZSBtZW50aW9uZWQsIGF0IGxlYXN0IGJ5
IGEgY3Jvc3MtcmVmZXJlbmNlIHRvIHRoZQ0KdmFyaW91cyBSRkNzIG9uIGxpYWlzb25zOiA0
MDUyLCA0MDUzLCA0NjkxLg0KDQo+ICAgbyAgVGhlIFJFTlVNIFdHIG9uIHRoZSBPcGVyYXRp
b25zIGFuZCBNYW5hZ2VtZW50IEFyZWEgaXMgYWRkcmVzc2luZw0KPiAgICAgIHJlbnVtYmVy
aW5nIGlzc3VlcywgYnV0IHdpbGwgaGF2ZSB0byB3b3JrIHdpdGggb3RoZXIgYXJlYXMgaWYN
Cj4gICAgICBjaGFuZ2VzIG9yIGV4dGVuc2lvbnMgdG8gc3BlY2lmaWMgcHJvdG9jb2xzIGFy
ZSByZXF1aXJlZC4NCg0KVGhlIFdHIG5hbWUgaXMgNlJFTlVNLiBJbiBmYWN0IGl0cyBjaGFy
dGVyIGlzIGV4cGxpY2l0IHRoYXQgcHJvdG9jb2wgd29yaw0Kd2lsbCAqbm90KiBiZSBkb25l
IGluIHRoZSBXRy4gKFRoZSBzYW1lIGlzIHRydWUgb2YgVjZPUFMuKSANCg0KPiAzLiAgUmF0
aW9uYWxlIGZvciBDcm9zcy1BcmVhIFdvcmsNCi4uLg0KPiAgIFRoZQ0KPiAgIGFjdHVhbCBz
b2x1dGlvbiB3b3JrIGlzIHRoZW4gdGFrZW4gdXAgYnkgdGhlIHJlbGV2YW50IHRlY2huaWNh
bA0KPiAgIGNvbW11bml0eSB0aGF0IHdvcmtzIG9uIHRoZSBwcm90b2NvbCB0aGF0IG5lZWRz
IHRvIGJlIGV4dGVuZGVkLg0KDQpJdCB3b3VsZCBiZSB1c2VmdWwgdG8gcmVmZXIgdG8gdGhl
IFJGQ3MgYWJvdXQgZXh0ZW5zaW9uczogNDc3NSwgNjcwOS4NCg0KTml0cw0KLS0tLQ0KDQpU
aGVyZSBhcmUgbnVtZXJvdXMgZXJyb3JzIGluIHRoZSBjaG9pY2Ugb2YgcHJlcG9zaXRpb25z
LCBlLmcuICJUaGUgTFdJRyBXRyBvbiB0aGUgDQpJbnRlcm5ldCBBcmVhIiwgdGhhdCBuZWVk
IHRvIGJlIGZpeGVkIGR1cmluZyBlZGl0aW5nLg==
--------------080509020102050707090407--

From jari.arkko@piuha.net  Sun Feb 10 03:00:12 2013
Return-Path: <jari.arkko@piuha.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 3820B21F8570 for <gen-art@ietfa.amsl.com>; Sun, 10 Feb 2013 03:00:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FRdf0n5ynLVZ for <gen-art@ietfa.amsl.com>; Sun, 10 Feb 2013 03:00:11 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 386B621F856D for <gen-art@ietf.org>; Sun, 10 Feb 2013 03:00:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 863012CC43; Sun, 10 Feb 2013 13:00:10 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w9QAMMOmlGFd; Sun, 10 Feb 2013 13:00:09 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id DC8A62CC3B; Sun, 10 Feb 2013 13:00:08 +0200 (EET)
Message-ID: <51177DB7.8090507@piuha.net>
Date: Sun, 10 Feb 2013 04:00:07 -0700
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <511662FE.7000103@gmail.com>
In-Reply-To: <511662FE.7000103@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, draft-arkko-iesg-crossarea.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-arkko-iesg-crossarea-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: Sun, 10 Feb 2013 11:00:12 -0000

Brian,

Thanks again for your review.

> Major Issues:
> -------------
>
> > Area Shopping
>
> I'm not entirely happy with this discussion. From the point of view of the
> person trying to introducing a new topic that does indeed cross areas, it is
> *inevitable* to commit the sin of area shopping. <shout>This is not a fault of
> the shopper; it's the fault of the IETF for having areas in the first place.</shout>
>
> I agree that it's the IESG's, and also the IAB's, job to resolve this when
> it arises. But the current text makes it sound as if the protagonist is to
> blame for bringing a cross-area problem to the IETF.

I already replied on a separate thread about this. Agreed.

>
> There also seems to be a missing topic, here and in the recommendations:
> the importance of the BOF (and bar BOF) process, and topic review by the
> IAB, in identifying cross-area topics and chartering them carefully. The
> worst thing that can happen is to BOF and charter a topic within one area,
> but discover later that it is in fact a cross-area topic. There are
> relevant RFCs: 5434, 6771.

A good point. Thanks.

>
> Minor Issues:
> -------------
>
> > 2.  Examples of Cross-Area Work
> >
> >   Many IETF efforts cross area boundaries.  Some recent examples of
> >   such work include:
> >
> >   o  The development of a routing-protocol based bridging model.  This
> >      work has been going on in the TRILL WG on the Internet Area and in
> >      parallel in the ISIS WG on the Routing Area.
>
> A very important aspect of this example is that it *also* overlaps with IEEE work.
> That scenario should surely be mentioned, at least by a cross-reference to the
> various RFCs on liaisons: 4052, 4053, 4691.

Yes.

>
> >   o  The RENUM WG on the Operations and Management Area is addressing
> >      renumbering issues, but will have to work with other areas if
> >      changes or extensions to specific protocols are required.
>
> The WG name is 6RENUM. In fact its charter is explicit that protocol work
> will *not* be done in the WG. (The same is true of V6OPS.)

Right. Will fix.

>
> > 3.  Rationale for Cross-Area Work
> ...
> >   The
> >   actual solution work is then taken up by the relevant technical
> >   community that works on the protocol that needs to be extended.
>
> It would be useful to refer to the RFCs about extensions: 4775, 6709.

OK

>
> Nits
> ----
>
> There are numerous errors in the choice of prepositions, e.g. "The LWIG WG on the
> Internet Area", that need to be fixed during editing.

OK

Jari


From miguel.a.garcia@ericsson.com  Sun Feb 10 22:21:10 2013
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 1827921F8793 for <gen-art@ietfa.amsl.com>; Sun, 10 Feb 2013 22:21:10 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P4cEw9FsoxFO for <gen-art@ietfa.amsl.com>; Sun, 10 Feb 2013 22:21:09 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1279021F877B for <gen-art@ietf.org>; Sun, 10 Feb 2013 22:21:08 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-a8-51188dd2d6b3
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 9E.D1.10459.2DD88115; Mon, 11 Feb 2013 07:21:07 +0100 (CET)
Received: from [159.107.24.134] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.279.1; Mon, 11 Feb 2013 07:21:06 +0100
Message-ID: <51188DCE.6080306@ericsson.com>
Date: Mon, 11 Feb 2013 07:21:02 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: draft-ietf-mpls-tp-use-cases-and-design.authors@tools.ietf.org,  Loa Andersson <loa@pi.nu>, Adrian Farrel <adrian@olddog.co.uk>, mpls-chairs@tools.ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjluLIzCtJLcpLzFFi42KZGfG3Rvdyr0SgwbazPBY/em4wW1zfv53Z 4uqrzywW/+bOYbb4fmkJiwOrx5IlP5k8Vmxeyegxa3obm8eXy5/ZAliiuGxSUnMyy1KL9O0S uDLeTutnLZjGWzHv8CrWBsZzXF2MnBwSAiYSFzsfMkHYYhIX7q1n62Lk4hASOMko0b2tlQnC WcMocXbNdRaQKl4BbYlt/fvZQWwWAVWJ67t/gMXZBMwlWjduBIuLCkRJvL/axAxRLyhxcuYT FpBBIgKLGSVWHmsGK2IW0Jc48mc30AYODmEBV4mjM/IhwrYSF+ZA7GIWkJfY/nYO2BwhAU2J yTeXMk9g5J+FZOwsJC2zkLQsYGRexciem5iZk15uuIkRGJYHt/zW3cF46pzIIUZpDhYlcd4w 1wsBQgLpiSWp2ampBalF8UWlOanFhxiZODilGhhLJGY4Lp75n5Vhs0Zs3yKuvU/rFK+e25f3 Z7rDvivF0oKsCy5O+b/i2w0Fz4mLziwWYRMzs7i16cHpmkuHRC7vCEiw+DvfaJLn+zmLV+6p v3ezf25h4IPa993VE/2P7n+z46zl2/1Lq9b8TUh/vueZXIXNkuLbvRc+CtdyNCRNsK/IFjk9 M9H/jhJLcUaioRZzUXEiAEQKzCkZAgAA
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-use-cases-and-design-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, 11 Feb 2013 06:21:10 -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-mpls-tp-use-cases-and-design-06
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 2013-02-10
IETF LC End Date: 2013-02-11
IESG Telechat date:

Summary: The document is almost ready for publication as Informational 
RFC, but has some NITS that should be addressed.

Major issues: none

Minor issues: none

Nits/editorial comments:

- The RFC Editor rules require to expand each acronym at a first usage. I 
noticed that the draft uses Section 2 as a container of all the acronyms, 
but most of these acronyms have already been used in Section 1. So, I am 
not sure if the current text is acceptable to the RFC Editor. Perhaps the 
authors should send them a question. One potential idea to explore is 
leaving the first paragraph of Section 1 in there, and move the rest of 
the Section to a new Section 3, whose potential title is "Background". 
This will solve that problem.

- It appears that Section is alphabetically ordered, but the term "NMS" 
is misplaced.

- Section 3.3.2, first paragraph. The text refers to "PSW/SGW or ASNGW)". 
Section 2 expands "PSW" as Packet Data Network Gateway. I suspect the 
acronym is wrong, because the Packet Data Network Gateway is commonly 
abbreviated as PDN GW or P-GW. I have never seen PSW to refer to a PDN GW 
or P-GW.

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


From vkg@bell-labs.com  Mon Feb 11 07:34:54 2013
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 B6F1021F87D4 for <gen-art@ietfa.amsl.com>; Mon, 11 Feb 2013 07:34:54 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AMCiRUAL84FP for <gen-art@ietfa.amsl.com>; Mon, 11 Feb 2013 07:34:53 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id AF56821F876E for <gen-art@ietf.org>; Mon, 11 Feb 2013 07:34:48 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r1BFYkvh008941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 11 Feb 2013 09:34:46 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1BFYjkE010309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 11 Feb 2013 09:34:46 -0600
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 r1BFYfI1021627; Mon, 11 Feb 2013 09:34:42 -0600 (CST)
Message-ID: <5119101F.4030606@bell-labs.com>
Date: Mon, 11 Feb 2013 09:37:03 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: draft-ietf-simple-simple@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.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: General Area Review Team <gen-art@ietf.org>, hisham.khartabil@gmail.com
Subject: [Gen-art] Gen-ART review of draft-ietf-simple-simple-08
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 Feb 2013 15:34:54 -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-simple-simple-08
Reviewer: Vijay K. Gurbani
Review Date: Feb-11-2013
IETF LC End Date: Feb-14-2013
IESG Telechat date: Not known

This document is ready as an Informational.  Some comments for
changes follow.

Major: 0
Minor: 2
Nits: 1

Minor:
- S2.1, discussion of rfc3265: RFC3265 is now made obsolete by rfc6665,
  I believe an update is appropriate here as well as other places where
  a reference to rfc3265 is made.

  Additionally, a reference to rfc3856 will be appropriate when
  we first talk about presence as a SUBS/NOT event package i.e.,
  s/Presence is defined as an event package/Presence is defined as
  an event package [RFC3865]/

- S3.2, discussion of rfc3862: Does CPIM stand for "Common Presence and
   Instant Messaging" or does it stand for "Common Profile for Instant
   Messaging", as expanded in rfc3862 itself?

Nits:

- Abstract, perhaps better for a standard document to use more
   formal language and:
   s/It breaks them up into categories/It categorizes the specifications/

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 aretana@cisco.com  Mon Feb 11 13:15:30 2013
Return-Path: <aretana@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 9932F21F8AB7; Mon, 11 Feb 2013 13:15:30 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1iDyPgWm39te; Mon, 11 Feb 2013 13:15:29 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id A6E1821F890D; Mon, 11 Feb 2013 13:15:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3284; q=dns/txt; s=iport; t=1360617329; x=1361826929; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=a1Py4EaY96o5jDaOhxGfxf5qljf8W6c68Lh+5kgri/A=; b=EUfOfspUVTCiDuuxU9y7dE+16MWVqu357V3SyPhz9C799xq4/q3H8tv6 52vpQlDP9uX+/ZcmjcENJBC9eJpxq73VSI6DpRwcxTUq13bO3pLOjW/l+ EhtKG2zh/KaO8zAcTsTFHgIfwgkmqyvCQ5HO77SRqKa6cR+rbk7KTkCdE I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAMNdGVGtJXG//2dsb2JhbAA6CsEkFnOCIQEEOj8SAQgUDhRCJQIEAQ0FCIgKDMAdjUeDZWEDkmqEV482gwaCJA
X-IronPort-AV: E=Sophos;i="4.84,644,1355097600"; d="scan'208";a="172902479"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-9.cisco.com with ESMTP; 11 Feb 2013 21:15:29 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r1BLFTAX017510 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 11 Feb 2013 21:15:29 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.213]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0328.009; Mon, 11 Feb 2013 15:15:28 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Ben Campbell <ben@nostrum.com>, Acee Lindem <acee.lindem@ericsson.com>, "Abhay Roy (akr)" <akr@cisco.com>
Thread-Topic: Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
Thread-Index: AQHN9DdZ9OjrkRsEWE2bqOnRv2sH7Zh1YiiA
Date: Mon, 11 Feb 2013 21:15:28 +0000
Message-ID: <BBD66FD99311804F80324E8139B3C94ED42270@xmb-aln-x15.cisco.com>
In-Reply-To: <CD0EC318-1015-41ED-8E0B-045D6EB258F9@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.221.163]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F109AA3999EA91469817701ACBF6E83E@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 11 Feb 2013 13:16:48 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org" <draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, "ospf-chairs@tools.ietf.org" <ospf-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
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 Feb 2013 21:15:30 -0000

On 1/16/13 5:17 PM, "Ben Campbell" <ben@nostrum.com> wrote:

Ben:

Hi!

Sorry for the delay, my filters put this in a different place..  I'm
explicitly adding the OSPF chairs.  Comments below.


>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-ospfv3-iid-registry-update-00
>Reviewer: Ben Campbell
>Review Date: 2013-01-16
>IETF LC End Date: 2013-01-24
>
>Summary: This draft is not ready for publication as a proposed standard.
>There is a significant IANA registration issue described in the review
>body.
>
>Major issues:
>
>This draft carves out a significant part of a registry with an assignment
>policy of "standards action" for "private use". It offers very little
>motivation for the change. In my opinion, this sort of change should come
>with a clear justification.
>
>Specifically, the draft modifies the OSPFv3 Address Family Instance ID
>registry to carve out half of the unassigned space for "private use". The
>justification for this is a single sentence saying that some networks
>need to use IIDs to identify specific applications. I think that needs
>significant elaboration in order to motivate the change in a way that the
>reader can evaluate.
>
>My understanding from the OFPS list is that this is in support of
>draft-ietf-ospf-ipv4-embedded-ipv6-routing, which is an informational
>draft. I have to wonder why the draft under review was not simply the
>IANA considerations for that draft.
>
>I suggest one of two paths forward:
>
>1) If this change is in support of that draft in particular, then this
>draft should say that, and include a _normative_ reference. I recognize
>the normative downref would complicate things--but I think that
>complication is reasonable under the circumstances.
>
>2) If this change is to support a general need that goes beyond
>draft-ietf-ospf-ipv4-embedded-ipv6-routing, then this draft should
>describe that need in enough detail for people to think about it, perhaps
>with an informative reference to
>draft-ietf-ospf-ipv4-embedded-ipv6-routing as an _example_.

In short (from the shepherd write-up): "The new range is for applications
that do not justify a standards track OSPFv3 Instance ID allocation. An
example would be "Routing for IPv4-embedded IPv6 Packets"".

During pre-publication review, the WG chairs asked us to not include
explicit references to draft-ietf-ospf-ipv4-embedded-ipv6-routing as that
is just an example and not the only potential user/driver.  I don't have a
problem adding an example, but I want to get agreement/comments/guidance
from the chairs before adding the text.  Acee/Abhay??


>
>
>Minor issues:
>
>-- section 3:
>
>I don't think it's appropriate to use normative language for IANA
>requests. Especially not "MUST". (I think the strongest thing we can do
>here is a polite request :-)  )   I suggest recasting that to descriptive
>language, and removing section 2 and the RFC 2119 reference.

Yes, we already removed that in the -01 version.

Thanks!!

Alvaro.


From rbarnes@bbn.com  Mon Feb 11 15:46:39 2013
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 0A24721F8856; Mon, 11 Feb 2013 15:46:39 -0800 (PST)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pSHPuzEX6z31; Mon, 11 Feb 2013 15:46:38 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 5204521F8812; Mon, 11 Feb 2013 15:46:38 -0800 (PST)
Received: from [128.89.254.29] (port=58806) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1U5352-000HGK-U2; Mon, 11 Feb 2013 18:46:36 -0500
From: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 11 Feb 2013 18:45:48 -0500
Message-Id: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com>
To: "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-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, 11 Feb 2013 23:46:39 -0000

I have been selected as the General Area Review Team (Gen-ART) reviewer =
for this draft (for background on Gen-ART, =
pleaseseehttp://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-mpls-tp-ethernet-addressing-05
Reviewer: Richard Barnes
Review Date: 2013-02-11
IETF LC End Date: 2013-02-18
IESG Telechat date: TBD

Summary:  Ready, with a couple of minor questions / clarifications.

Comment:

The document is mostly very clearly written.  (Thanks!)  It would have =
helped me understand if it could have been clarified up front that the =
mechanism in this document is intended for "pure Ethernet" MPLS-TP =
(without assumptions about layer 3+).  The current introduction says as =
much, but in a negative way, in terms of ARP or ND not being available.

I have some minor unease about the distinction that this document makes =
between point-to-point and multipoint links.  The document correctly =
notes that a point-to-point link might become multipoint without either =
end being aware.  I would have thought this would argue for using GAP in =
all cases, but instead the document carries on with addressing the =
point-to-point case separately.=

From meral.shirazipour@ericsson.com  Mon Feb 11 19:47:46 2013
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 BD71321F854E for <gen-art@ietfa.amsl.com>; Mon, 11 Feb 2013 19:47:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.932
X-Spam-Level: 
X-Spam-Status: No, score=-2.932 tagged_above=-999 required=5 tests=[AWL=-0.334, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kBEDNNwBWo1k for <gen-art@ietfa.amsl.com>; Mon, 11 Feb 2013 19:47:45 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id C723921F853D for <gen-art@ietf.org>; Mon, 11 Feb 2013 19:47:45 -0800 (PST)
X-AuditID: c618062d-b7fcb6d000007ada-7e-5119bb60150c
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 71.0A.31450.06BB9115; Tue, 12 Feb 2013 04:47:45 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0318.004; Mon, 11 Feb 2013 22:47:44 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-forces-lfb-lib.all@tools.ietf.org" <draft-ietf-forces-lfb-lib.all@tools.ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-forces-lfb-lib-10
Thread-Index: Ac4I03Cc+d11DYPzQfGQWLF9umoJ+Q==
Date: Tue, 12 Feb 2013 03:47:43 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A07CA6F@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A07CA6Feusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsUyuXRPrG7ibslAg7cr+S229B9ltLj66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJVx5/4p9oIjKhX7L79lbmC8rNDFyMkhIWAi cfvXZyYIW0ziwr31bF2MXBxCAkcYJT7+288O4SxnlJjd8oEVpIpNwEJi++/nYLaIQLLEpE0X GEFsZgFNiU1Nz9lAbGEBR4lZ03qYIGrcJBb0tTJD2HoSOw4vBLNZBFQlLt/YxQJi8wp4S8yb tRcszgh0xfdTa5ggZopL3HoyH+o6AYkle84zQ9iiEi8f/2OFsJUlvs95xAJRny/R0fgOaqag xMmZT1gmMArPQjJqFpKyWUjKIOI6Egt2f2KDsLUlli18zQxjnznwmAlZfAEj+ypGjtLi1LLc dCODTYzAODkmwaa7g3HPS8tDjNIcLErivEGuFwKEBNITS1KzU1MLUovii0pzUosPMTJxcEo1 MG5xtZ0/Y3aRiHqpAs+XVc8UfVp/ZGk9Fjc+zqEm/+voQ/V6UWPFpQJM4df4dRhF4tIdFTXX l3zm/M56M1eGiWnHrucGzi5u8WHs3eYPNa8ud9BpiV/NmNTJ8o7/X3VElebzpClux+Q3iUiZ 39Vt6Za/fGwK22Lf0hu64f+WihtsjXrsoF6txFKckWioxVxUnAgAeQqZjGECAAA=
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-forces-lfb-lib-10
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 Feb 2013 03:47:46 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A07CA6Feusaamb107ericsso_
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-AR=
T, please see the FAQ at http://wiki.tools.ietf.org/area/gen/trac/wiki/GenA=
rtfaq  .

Please resolve any Last Call comments you may have received.

Document: draft-ietf-forces-lfb-lib-10
Reviewer: Meral Shirazipour
Review Date: 2013-02-11
IETF LC End Date: 2013-02-11
IESG Telechat date: NA

Summary:
This draft is ready to be published as Proposed Standard.

Major issues:
none

Minor issues:
none

Nits/editorial comments:
none



Best Regards,
Meral

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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<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=3D"EN-CA" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> &nbsp;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve any Last Call comments you may have r=
eceived.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CA">Document: draft-ietf-forces-lfb=
-lib-10<o:p></o:p></span></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-02-11<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-02-11<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is ready to be published as Proposed Stan=
dard.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues:<o:p></o:p></p>
<p class=3D"MsoNormal">none<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal">none<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">none<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A07CA6Feusaamb107ericsso_--

From ron.even.tlv@gmail.com  Mon Feb 11 22:49:10 2013
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 DBBEB21F8C2C; Mon, 11 Feb 2013 22:49:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.821
X-Spam-Level: 
X-Spam-Status: No, score=-2.821 tagged_above=-999 required=5 tests=[AWL=0.777,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P5kG57EVULoe; Mon, 11 Feb 2013 22:49:10 -0800 (PST)
Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by ietfa.amsl.com (Postfix) with ESMTP id 526C821F8C12; Mon, 11 Feb 2013 22:49:09 -0800 (PST)
Received: by mail-ee0-f54.google.com with SMTP id c41so3563353eek.27 for <multiple recipients>; Mon, 11 Feb 2013 22:49:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=XBthy7qHCa6rhqGH+C+0GyMPmEeCpAk5C/dTz+Jn4gE=; b=cH2WXBXwabozYGONA7Akt+GuBz7+KIb8o0J2w+i7SGohv0E+7mzv6RbbwBDQTwVaae hCMbq/S0BIleoL6+jvZ7PljLKGD/X0KgAvPRHEdpCQBCa3sTni45S/UryE+RtCz6K9s4 qQG9q6oHKZa/yJmqaJEs4xG7zPKGrxl5wWgGsvuon6aMhXaxwplSu5BuL8vSwgZe2PPv +SX5MvYrQxVwhmCTbro2TnRUhgZ855xMch7N1/LwvZtm3AOIW3fBfGBvRyHF+VY0DHyW bHLsUCTzYlAxqUdOiOhMb7hxepTNUBTxV8u/Kum5ObtM26tQ0FtPVpsk2Ep9WCmPo2ft 6lFg==
X-Received: by 10.14.174.73 with SMTP id w49mr59825819eel.17.1360651748422; Mon, 11 Feb 2013 22:49:08 -0800 (PST)
Received: from RoniE (bzq-79-181-179-229.red.bezeqint.net. [79.181.179.229]) by mx.google.com with ESMTPS id m46sm2040420eeo.16.2013.02.11.22.49.05 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 11 Feb 2013 22:49:07 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-ancp-pon.all@tools.ietf.org>
Date: Tue, 12 Feb 2013 08:46:16 +0200
Message-ID: <06da01ce08ec$a9fc9590$fdf5c0b0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_06DB_01CE08FD.6D8601D0"
X-Mailer: Microsoft Outlook 14.0
thread-index: Ac4I7KgEW1ueTd0DSHaPAhSPsbanHA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-ancp-pon-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, 12 Feb 2013 06:49:11 -0000

This is a multipart message in MIME format.

------=_NextPart_000_06DB_01CE08FD.6D8601D0
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-ancp-pon-04

Reviewer: Roni Even

Review Date:2013-2-12

IETF LC End Date: 2013-2-19

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	OMCI is expanded very late in the document and not on the first
usage.

 


------=_NextPart_000_06DB_01CE08FD.6D8601D0
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;}
@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:296448786;
	mso-list-type:hybrid;
	mso-list-template-ids:1423221754 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><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><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"'>Document: =
</span><span style=3D'font-family:"Courier =
New","serif"'>draft-ietf-ancp-pon-04<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:2013&#8211;2&#8211;12<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: 2013-2&#8211;19<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</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"'>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"'><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=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>OMCI is =
expanded very late in the document and not on the first =
usage.<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_06DB_01CE08FD.6D8601D0--


From alexey.melnikov@isode.com  Tue Feb 12 05:19:02 2013
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 6344521F8E5A; Tue, 12 Feb 2013 05:19:02 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e9GGfsT6+5-i; Tue, 12 Feb 2013 05:19:01 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 359C621F8D84; Tue, 12 Feb 2013 05:19:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1360675140; d=isode.com; s=selector; i=@isode.com; bh=YBalNRwN/PrMbSeYmLftlzdLmwsw/lv7dVKJKN6a1jg=; 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=B+Zt2r8pzyaNkat9O7FC19V05Wyk8TjOHGbRs9eDmo8AhYJ2tWyzLWi02bwxUod3qlr/Bt SpS3ir1ATYa7OZdkp1jfcXJKLOJBqZ5k8utsJkyRGd36WgT7D/EFuahYC2tYZk02fLd/EL pKBb+H+48rWr1khQfIsbTHiCY4z7UYE=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <URpBPgAYIUfy@statler.isode.com>; Tue, 12 Feb 2013 13:18:56 +0000
Message-ID: <511A4188.6030101@isode.com>
Date: Tue, 12 Feb 2013 13:20:08 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: draft-ietf-mmusic-sdp-cs.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 LC review of draft-ietf-mmusic-sdp-cs-17
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 Feb 2013 13:19:02 -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-mmusic-sdp-cs-17
Reviewer: Alexey Melnikov
Review Date: 2013-02-12
IETF LC End Date: 2013-02-01
IESG Telechat date: N/A


Summary: This draft is ready for publication as a Standard Track RFC 
(with some nits/minor issues):

Major issues:

Minor issues:

5.2.2.  Media Descriptions

    When "RTP/AVP" is used in the <proto> field, the <fmt> subfield
    contains the RTP payload type numbers.  We use the <fmt> subfield to
    indicate the list of available codecs over the circuit-switched
    bearer, by re-using the conventions and payload type numbers defined
    for RTP/AVP.  The RTP audio and video media types, which, when
    applied to PSTN circuit-switched bearers, represent merely an audio
    or video codec.  The endpoint SHOULD only use those payload type
    whose corresponding codecs is available for PSTN media streams.

Why is this a SHOULD? What are possible reasons for violating it?


5.6.1.  Generating the Initial Offer

    The <fmt> subfield carries the payload type number(s) the endpoint is
    wishing to use.  Payload type numbers in this case refer to the
    codecs that the endpoint wishes to use on the PSTN media stream. For
    example, if the endpoint wishes to use the GSM codec, it would add
    payload type number 3 in the list of codecs.  The list of payload
    types SHOULD only contain those codecs the endpoint is able to use on
    the PSTN bearer.

Again, a SHOULD similar to the one above. Can you please explain the 
reasoning for it?


    If the Offerer is only able to become the passive party in the
    circuit-switched bearer setup, it MUST add the "callerid", "uuie"
    and/or "dtmf" subfields,

This text is a bit awkward as you specify this field as extensible. So I 
think you need to add a choice for extensions here.

Similar text in section 5.6.2

    but MUST NOT specify values for those
    subfields.

5.6.2.  Generating the Answer

    If the Answerer becomes the active party, it MUST add any of the
    "callerid", "uuie" or "dtmf" subfield values.

8.3.  Registration of new "addrtype" values


    Note to IANA: The current "addrtype" sub-registry structure does not
    capture the fact that a given addrtype is defined in the context of a
    particular "nettype".  The sub-registry structure should be to
    correct that as part of this registration.

Did you mean "should be corrected as part ..."


Nits/editorial comments:

5.3.3.  Considerations on correlations

    Passive endpoints should expect an incoming CS call for setting up
    the audio bearer.  Passive endpoints MAY suppress the incoming CS
    alert during a certain time periods.  Additional restrictions can be
    applied, such as the passive endpoint not alerting incoming calls
    originated from the number that was observed uduring the offer/answer

Typo: during

    negotiation.


5.7.  Formal Syntax

    The following is the formal Augmented Backus-Naur Form (ABNF)
    [RFC5234] syntax that supports the extensions defined in this
    specification.  The syntax is built above the SDP [RFC4566] and the
    tel URI [RFC3966] grammars.  Implementations according to this
    specification MUST be compliant with this syntax.

    Figure 2 shows the formal syntax of the extensions defined in this
    memo.

            ; extension to the connection field originally specified
            ; in RFC 4566

            connection-field   =  [%x63 "=" nettype SP addrtype SP
            connection-address CRLF]
            ;nettype and addrtype are defined in RFC 4566

            connection-address /=  global-number-digits / "-"
            ; global-number-digits specified in RFC 3966

This is good, but you don't specify where CRLF, HEXDIG are defined. I 
can guess, but it would be better if a reader doesn't have to guess.

            ;subrules for correlation attribute
            attribute          /= cs-correlation-attr
            ; attribute defined in RFC 4566
            cs-correlation-attr = "cs-correlation:" corr-mechanisms
            corr-mechanisms    = corr-mech *(SP corr-mech)
            corr-mech          = caller-id-mech / uuie-mech /
                                 dtmf-mech / ext-mech
            caller-id-mech     = "callerid" [":" caller-id-value]
            caller-id-value    = "+" 1*15DIGIT
            uuie-mech          = "uuie" [":" uuie-value]
            uuie-value         = 1*65(HEXDIG HEXDIG)
                                 ;This represents up to 130 HEXDIG
                                 ; (65 octets)
                                 ;HEXDIG defined in RFC5234
                                 ;HEXDIG defined as 0-9, A-F
            dtmf-mech          = "dtmf" [":" dtmf-value]
            dtmf-value         = 1*32(DIGIT / %x41-44 / %x23 / %x2A )
            ;0-9, A-D, '#' and '*'
            ext-mech           = ext-mech-name [":" ext-mech-value]
            ext-mech-name      = token
            ext-mech-value     = token
            ; token is specified in RFC4566


From nabil.n.bitar@verizon.com  Tue Feb 12 07:25:10 2013
Return-Path: <nabil.n.bitar@verizon.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 144B021F8EEC; Tue, 12 Feb 2013 07:25:10 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ijZMG9l1EoQP; Tue, 12 Feb 2013 07:25:09 -0800 (PST)
Received: from fldsmtpe01.verizon.com (fldsmtpe01.verizon.com [140.108.26.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2021921F8EE3; Tue, 12 Feb 2013 07:25:09 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by fldsmtpe01.verizon.com with ESMTP; 12 Feb 2013 14:53:14 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
X-IronPort-AV: E=Sophos;i="4.84,650,1355097600";  d="scan'208,217";a="413212070"
Received: from fldp1lumxc7hb03.verizon.com (HELO FLDP1LUMXC7HB03.us.one.verizon.com) ([166.68.75.86]) by fldsmtpi03.verizon.com with ESMTP; 12 Feb 2013 14:52:12 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([169.254.3.33]) by FLDP1LUMXC7HB03.us.one.verizon.com ([166.68.75.86]) with mapi; Tue, 12 Feb 2013 09:52:12 -0500
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-ancp-pon.all@tools.ietf.org" <draft-ietf-ancp-pon.all@tools.ietf.org>
Date: Tue, 12 Feb 2013 09:52:07 -0500
Thread-Topic: Gen-ART LC review of draft-ietf-ancp-pon-04
Thread-Index: Ac4JMIncWadkfIo5Qp609P3ZKd123A==
Message-ID: <CD3FC0F0.76E96%nabil.n.bitar@verizon.com>
In-Reply-To: <06da01ce08ec$a9fc9590$fdf5c0b0$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CD3FC0F076E96nabilnbitarverizoncom_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-ancp-pon-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, 12 Feb 2013 15:25:10 -0000

--_000_CD3FC0F076E96nabilnbitarverizoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Roni,
Thanks. Will do the edit you pointed out.

Thanks,
Nbail

From: Roni Even <ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>>
Date: Tuesday, February 12, 2013 1:46 AM
To: "draft-ietf-ancp-pon.all@tools.ietf.org<mailto:draft-ietf-ancp-pon.all@=
tools.ietf.org>" <draft-ietf-ancp-pon.all@tools.ietf.org<mailto:draft-ietf-=
ancp-pon.all@tools.ietf.org>>
Cc: "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.o=
rg>>, "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:=
gen-art@ietf.org>>
Subject: Gen-ART LC review of draft-ietf-ancp-pon-04
Resent-To: <droms@bucknell.edu<mailto:droms@bucknell.edu>>, <matthew.bocci@=
alcatel-lucent.com<mailto:matthew.bocci@alcatel-lucent.com>>, "<, nabil.n.b=
itar@verizon.com<mailto:nabil.n.bitar@verizon.com>>", <sanjay.wadhwa@alcate=
l-lucent.com<mailto:sanjay.wadhwa@alcatel-lucent.com>>, <wdec@cisco.com<mai=
lto:wdec@cisco.com>>

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-ancp-pon-04

Reviewer: Roni Even

Review Date:2013=962=9612

IETF LC End Date: 2013-2=9619

IESG Telechat date:



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





Major issues:



Minor issues:




Nits/editorial comments:

 1.  OMCI is expanded very late in the document and not on the first usage.


--_000_CD3FC0F076E96nabilnbitarverizoncom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=
 -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14p=
x; font-family: Calibri, sans-serif; "><div>Hi Roni,</div><div>Thanks. Will=
 do the edit you pointed out.</div><div><br></div><div>Thanks,</div><div>Nb=
ail</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div style=3D"fon=
t-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTT=
OM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEF=
T: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: me=
dium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From: </span>=
 Roni Even &lt;<a href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail=
.com</a>&gt;<br><span style=3D"font-weight:bold">Date: </span> Tuesday, Feb=
ruary 12, 2013 1:46 AM<br><span style=3D"font-weight:bold">To: </span> &quo=
t;<a href=3D"mailto:draft-ietf-ancp-pon.all@tools.ietf.org">draft-ietf-ancp=
-pon.all@tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:draft-ietf-ancp-pon=
.all@tools.ietf.org">draft-ietf-ancp-pon.all@tools.ietf.org</a>&gt;<br><spa=
n style=3D"font-weight:bold">Cc: </span> &quot;<a href=3D"mailto:ietf@ietf.=
org">ietf@ietf.org</a>&quot; &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf=
.org</a>&gt;, &quot;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a=
>&quot; &lt;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;<br=
><span style=3D"font-weight:bold">Subject: </span> Gen-ART LC review of dra=
ft-ietf-ancp-pon-04<br><span style=3D"font-weight:bold">Resent-To: </span> =
&lt;<a href=3D"mailto:droms@bucknell.edu">droms@bucknell.edu</a>&gt;, &lt;<=
a href=3D"mailto:matthew.bocci@alcatel-lucent.com">matthew.bocci@alcatel-lu=
cent.com</a>&gt;, &quot;&lt;, <a href=3D"mailto:nabil.n.bitar@verizon.com">=
nabil.n.bitar@verizon.com</a>&gt;&quot;, &lt;<a href=3D"mailto:sanjay.wadhw=
a@alcatel-lucent.com">sanjay.wadhwa@alcatel-lucent.com</a>&gt;, &lt;<a href=
=3D"mailto:wdec@cisco.com">wdec@cisco.com</a>&gt;<br></div><div><br></div><=
div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micros=
oft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xm=
lns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http://=
www.w3.org/TR/REC-html40"><meta name=3D"Generator" content=3D"Microsoft Wor=
d 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;}
@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:296448786;
	mso-list-type:hybrid;
	mso-list-template-ids:1423221754 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-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]--><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoNormal"><a name=3D"O=
LE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART reviewer for =
this draft. For background on Gen-ART, please see the FAQ at &lt;</a><a hre=
f=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_bl=
ank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p><=
/o:p></p><p class=3D"MsoNormal">Please resolve these comments along with an=
y other Last Call comments you may receive.<o:p></o:p></p><p class=3D"MsoPl=
ainText"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">Document:
</span><span style=3D"font-family: 'Courier New', serif; ">draft-ietf-ancp-=
pon-04<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-s=
ize: 11pt; font-family: Calibri, sans-serif; ">Reviewer: Roni Even<o:p></o:=
p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font=
-family: Calibri, sans-serif; ">Review Date:2013=962=9612<o:p></o:p></span>=
</p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; ">IETF LC End Date: 2013-2=9619<o:p></o:p></span></p><=
p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calib=
ri, sans-serif; ">IESG Telechat date:
<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 1=
1pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p cla=
ss=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calibri, s=
ans-serif; ">Summary: This draft is ready for publication as an Information=
al RFC</span><span style=3D"font-size: 11pt; font-family: Calibri, sans-ser=
if; ">.<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-=
size: 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p=
><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Cal=
ibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><=
span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Major is=
sues:<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-si=
ze: 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><=
p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calib=
ri, sans-serif; ">Minor issues:<o:p></o:p></span></p><p class=3D"MsoPlainTe=
xt"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; "><o:=
p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size=
: 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p =
class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p><ol style=3D"mar=
gin-top:0in" start=3D"1" type=3D"1"><li class=3D"MsoNormal" style=3D"mso-li=
st:l0 level1 lfo1">OMCI is expanded very late in the document and not on th=
e first usage.<o:p></o:p></li></ol><p class=3D"MsoNormal"><o:p>&nbsp;</o:p>=
</p></div></div></div></span></body></html>

--_000_CD3FC0F076E96nabilnbitarverizoncom_--

From Francis.Dupont@fdupont.fr  Wed Feb 13 06:06:50 2013
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 3CF7621F86C4 for <gen-art@ietfa.amsl.com>; Wed, 13 Feb 2013 06:06:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, 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 vy-oIXXf08yn for <gen-art@ietfa.amsl.com>; Wed, 13 Feb 2013 06:06:49 -0800 (PST)
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 C74E521F86BB for <gen-art@ietf.org>; Wed, 13 Feb 2013 06:06:46 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r1DE6jUb091635; Wed, 13 Feb 2013 15:06:45 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201302131406.r1DE6jUb091635@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Juergen Quittek <Quittek@neclab.eu>
In-reply-to: Your message of Tue, 29 Jan 2013 16:40:43 GMT. <CD2DB657.6B129%quittek@neclab.eu> 
Date: Wed, 13 Feb 2013 15:06:45 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: "draft-ietf-eman-requirements.all@tools.ietf.org" <draft-ietf-eman-requirements.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-eman-requirements-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: Wed, 13 Feb 2013 14:06:50 -0000

 In your previous mail you wrote:

>  > - ToC page 3 and 11 page 23: Acknowledgements -? Acknowledgments
>  
>  Well, both is possible.  I changed it as suggested.

=> it is a standard US vs UK English...

>  > - 1 page 4 and others: why Power State and not power state? I believe it
>  >  comes from a document where you imported the term from?
>  
>  The capitalized term is defined in the terminology section.  Is this OK?

=> it is OK (and a point for the RFC Editor): I just wanted to understand.

Thanks

Francis.Dupont@fdupont.fr

From Quittek@neclab.eu  Wed Feb 13 06:50:06 2013
Return-Path: <Quittek@neclab.eu>
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 F008321F8778 for <gen-art@ietfa.amsl.com>; Wed, 13 Feb 2013 06:50:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.586
X-Spam-Level: 
X-Spam-Status: No, score=-103.586 tagged_above=-999 required=5 tests=[AWL=0.013, 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 yEIRCHPfOwZP for <gen-art@ietfa.amsl.com>; Wed, 13 Feb 2013 06:50:00 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id B8AC621F871D for <gen-art@ietf.org>; Wed, 13 Feb 2013 06:50:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 2CADA1031D0; Wed, 13 Feb 2013 15:50:00 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oiYlL--V4I0W; Wed, 13 Feb 2013 15:50:00 +0100 (CET)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 0E687103183; Wed, 13 Feb 2013 15:49:45 +0100 (CET)
Received: from PALLENE.office.hd ([169.254.1.80]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Wed, 13 Feb 2013 15:48:27 +0100
From: Juergen Quittek <Quittek@neclab.eu>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Thread-Topic: review of draft-ietf-eman-requirements-10.txt 
Thread-Index: AQHOCfOPQu0yb5pTS0Gj9a+0PUS3cJh33rAA
Date: Wed, 13 Feb 2013 14:48:26 +0000
Message-ID: <CD41665E.6B191%quittek@neclab.eu>
In-Reply-To: <201302131406.r1DE6jUb091635@givry.fdupont.fr>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
x-originating-ip: [10.1.2.219]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18F1FBADF7EBE442A25E2DB763F70126@office.hd>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-eman-requirements.all@tools.ietf.org" <draft-ietf-eman-requirements.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-eman-requirements-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: Wed, 13 Feb 2013 14:50:07 -0000

Hi Francis,.

Thanks for your confirmantion.
    Juergen

On 13.02.13 15:06, "Francis Dupont" <Francis.Dupont@fdupont.fr> wrote:

> In your previous mail you wrote:
>
>>  > - ToC page 3 and 11 page 23: Acknowledgements -? Acknowledgments
>> =20
>>  Well, both is possible.  I changed it as suggested.
>
>=3D> it is a standard US vs UK English...
>
>>  > - 1 page 4 and others: why Power State and not power state? I
>>believe it
>>  >  comes from a document where you imported the term from?
>> =20
>>  The capitalized term is defined in the terminology section.  Is this
>>OK?
>
>=3D> it is OK (and a point for the RFC Editor): I just wanted to understan=
d.
>
>Thanks
>
>Francis.Dupont@fdupont.fr


From vincent.roca@inria.fr  Wed Feb 13 09:07:49 2013
Return-Path: <vincent.roca@inria.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 F0E2A21F89EF; Wed, 13 Feb 2013 09:07:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.806
X-Spam-Level: 
X-Spam-Status: No, score=-109.806 tagged_above=-999 required=5 tests=[AWL=-0.442, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zu1Zl40bPZjW; Wed, 13 Feb 2013 09:07:48 -0800 (PST)
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by ietfa.amsl.com (Postfix) with ESMTP id 217B621F8A6F; Wed, 13 Feb 2013 09:07:43 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,658,1355094000"; d="scan'208,217";a="2109953"
Received: from unknown (HELO [10.2.29.151]) ([78.250.189.3]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/AES128-SHA; 13 Feb 2013 17:55:43 +0100
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-1-215950537
From: Vincent Roca <vincent.roca@inria.fr>
In-Reply-To: <032b01cdf34f$7714f300$653ed900$@gmail.com>
Date: Wed, 13 Feb 2013 18:07:19 +0100
Message-Id: <DBDA5F3C-6911-4266-8F0E-637A404BE7A9@inria.fr>
References: <032b01cdf34f$7714f300$653ed900$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: gen-art@ietf.org, Vincent Roca <vincent.roca@inria.fr>, ietf@ietf.org, draft-ietf-rmt-fcast.all@tools.ietf.org
Subject: Re: [Gen-art] GenART LC review of draft-ietf-rmt-fcast-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: Wed, 13 Feb 2013 17:07:49 -0000

--Apple-Mail-1-215950537
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Dear Roni,

Thanks a lot for your comments. Here are my answers.


> Document: draft-ietf-rmt-fcast-07
> Reviewer: Roni Even
> Review Date:2013=961=9615
> IETF LC End Date: 2013-1=9622
> IESG Telechat date:
> =20
> Summary: This draft is almost ready for publication as Standard track =
RFC.
> =20
> =20
> Major issues:
> =20
> Minor issues:
> =20
> 1.       I had some problem when reading the document about what is =
mandatory to support. The distinction between what is  required to be  =
supported and used is mentioned in section 5. Also section 3.3 discusses =
what compliant implementation is, but section 5 provides the full =
information. I think that it will be better to move section 5 before or =
at the beginning of section 3 or as part of  3.3.  no need to have the =
information twice.

I agree. The new 3.3 section now explains the concepts, and the =
"mandatory to implement" things are moved to
the "Requirements for Compliant Implementations" section.


This "compliant implementations" section is moved at the end of section =
3 as suggested by Joseph Yee.
The new ToC is therefore:

   2.  FCAST Data Formats
   3.  FCAST Principles
   4.  Requirements for Compliant Implementations


> 2.       In section 3.3 =93The support of GZIP encoding, or any other =
solution, remains optional.=94 I think that support is mandatory.

You're right and there is also some confusion here between the GZIP use =
in MDEnc, and the GZIP use in
Content-Encoding. It makes no sense to say GZIP is mandatory in MDEnc, =
and optional in Content-Encoding.
This is now clarified in the "compliant implementations" section.


NEW item in "compliant implementations" section:

   | Content-Encoding       | MUST be supported.  All FCAST            |
   |                        | implementations MUST support GZIP        |
   |                        | encoding [RFC1952]                       |


Additionally, I've moved text from Section 2.2 about Content-Length and
Content-Encoding (that includes lengthy discussion on GZIP usage)
to Section 3.3. There's now a single place to explain concepts with all
the details.


OLD item in 2.2:

   o  Content-Encoding: it specifies the optional encoding of the object
      list, performed by FCAST.  For instance:
           Content-Encoding: gzip
      indicates that the Object List field has been encoded with GZIP
      [RFC1952].  If there is no Content-Encoding entry, the receiver
      MUST assume that the Object List field is plain text (default).
      The support of GZIP encoding, in addition to the plain text form,
      is REQUIRED.  The Content-Encoding entry MAY be used to indicate
      other encoding types to support non-standard FCAST implementation
      or future extended specifications.


NEW item in 2.2:

   o  Content-Encoding: it specifies the optional encoding of the object
      list, performed by FCAST.


OLD item in 3.3:
   o  Content-Encoding: a string that contains the optional encoding of
      the object performed by FCAST.  If there is no Content-Encoding
      entry, the receiver MUST assume that the object is not encoded
      (default).  The support of GZIP encoding, or any other solution,
      remains optional.


NEW item in 3.3:

   o  Content-Encoding: a string that contains the optional encoding of
      the object performed by FCAST.  For instance:
           Content-Encoding: gzip
      indicates that the Object List field has been encoded with GZIP
      [RFC1952].  If there is no Content-Encoding entry, the receiver
      MUST assume that FCAST did not perform any encoding to the object
      (default).


While doing that I realized that the Fcast-CID-Complete and Fcast-CID-ID
were not mentioned at all in the "compliant implementations" section. =
This
is now corrected as follows:

NEW item in "compliant implementations" section:

   CID-specific Meta-data items (Section 2.2):

       +-----------------------+-------------------+
       | Feature               | Status            |
       +-----------------------+-------------------+
       | Fcast-CID-Complete    | MUST be supported |
       | Fcast-CID-ID          | MUST be supported |
       +-----------------------+-------------------+


>  Nits/editorial comments:


The following 4 comments have been resolved.

> In section 5.1 at the end of first table =93in-bound=94 should be =
=93in-band=94
> In section 6 in the paragraph after the bullet points =93possibly =
possibly=94
> In section 7 =93This specification requires IANA to create two new =
registries=94 I think there are three new registries.
> In section 7.1 second paragraph =93registry registry=94

Thanks a lot for your comments.
Cheers,

   Vincent


--Apple-Mail-1-215950537
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><base href=3D"x-msg://491/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div>Dear Roni,</div><div><br></div>Thanks a lot =
for your comments.&nbsp;Here are my =
answers.<div><div><br></div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">Document:<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-family: 'Courier New'; =
">draft-ietf-rmt-fcast-07</span><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">Reviewer: Roni Even<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; ">Review =
Date:2013=961=9615<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">IETF LC End Date: =
2013-1=9622<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">IESG Telechat =
date:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">Summary: This draft is almost ready for publication as Standard track =
RFC</span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">Major =
issues:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">Minor issues:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0.5in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; "><span>1.<span style=3D"font: normal normal normal =
7pt/normal 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
dir=3D"LTR"></span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">I had some problem when reading the document about what is =
mandatory to support. The distinction between what is &nbsp;required to =
be &nbsp;supported and used is mentioned in section 5. Also section 3.3 =
discusses what compliant implementation is, but section 5 provides the =
full information. I think that it will be better to move section 5 =
before or at the beginning of section 3 or as part of &nbsp;3.3. =
&nbsp;no need to have the information =
twice.</span></div></div></div></span></blockquote><div><br></div><div>I =
agree. The new 3.3 section now explains the concepts, and the "mandatory =
to implement" things are moved to</div><div>the "Requirements for =
Compliant Implementations" =
section.</div><div><br></div><div><div><br></div></div><div>This&nbsp;"com=
pliant implementations" section&nbsp;is moved&nbsp;at the end of section =
3 as suggested by&nbsp;Joseph Yee.</div><div>The new ToC is =
therefore:</div><div><br></div><div>&nbsp; &nbsp;2. &nbsp;FCAST Data =
Formats</div><div>&nbsp; &nbsp;3. &nbsp;FCAST Principles<br>&nbsp; =
&nbsp;4. &nbsp;Requirements for Compliant =
Implementations<br><br></div><br><blockquote type=3D"cite"><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; text-indent: -0.25in; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; "><span>2.<span style=3D"font: =
normal normal normal 7pt/normal 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
dir=3D"LTR"></span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">In section 3.3 =93</span><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">The support of GZIP encoding, or any =
other solution, remains optional.=94 I think that support is =
mandatory.</span></div></div></div></blockquote><div><br></div><div>You're=
 right and there is also some confusion here between the GZIP use =
in&nbsp;MDEnc, and the GZIP use in</div><div>Content-Encoding.&nbsp;It =
makes no sense to say GZIP is mandatory in MDEnc, and optional in =
Content-Encoding.</div><div>This is now clarified =
in&nbsp;the&nbsp;"compliant implementations" =
section.</div><div><div><br></div><div><br></div><div>NEW item =
in&nbsp;"compliant implementations" =
section:</div><div><div><div><br></div></div><div><div><font =
class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp;| =
Content-Encoding &nbsp; &nbsp; &nbsp; | MUST be supported. &nbsp;All =
FCAST &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</font></div><div><font =
class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp;| &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;| implementations MUST support GZIP &nbsp; &nbsp; &nbsp; =
&nbsp;|</font></div><div><font class=3D"Apple-style-span" face=3D"'Courier=
 New'">&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| encoding [RFC1952] &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
|</font></div><div><br></div></div></div></div><div><br></div><div>Additio=
nally, I've moved text from Section 2.2 about Content-Length =
and</div><div>Content-Encoding (that includes lengthy discussion on GZIP =
usage)</div><div>to Section 3.3. There's now a single place to explain =
concepts with all</div><div>the =
details.</div><div><br></div><div><br></div><div>OLD item in =
2.2:</div><div><br></div><div><div>&nbsp; &nbsp;o =
&nbsp;Content-Encoding: it specifies the optional encoding of the =
object</div><div>&nbsp; &nbsp; &nbsp; list, performed by FCAST. =
&nbsp;For instance:</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Content-Encoding: gzip</div><div>&nbsp; &nbsp; &nbsp; indicates =
that the Object List field has been encoded with GZIP</div><div>&nbsp; =
&nbsp; &nbsp; [RFC1952]. &nbsp;If there is no Content-Encoding entry, =
the receiver</div><div>&nbsp; &nbsp; &nbsp; MUST assume that the Object =
List field is plain text (default).</div><div>&nbsp; &nbsp; &nbsp; The =
support of GZIP encoding, in addition to the plain text =
form,</div><div>&nbsp; &nbsp; &nbsp; is REQUIRED. &nbsp;The =
Content-Encoding entry MAY be used to indicate</div><div>&nbsp; &nbsp; =
&nbsp; other encoding types to support non-standard FCAST =
implementation</div><div>&nbsp; &nbsp; &nbsp; or future extended =
specifications.</div><div><br></div><div><br></div></div><div>NEW item =
in 2.2:</div><div><br></div><div><div>&nbsp; &nbsp;o =
&nbsp;Content-Encoding: it specifies the optional encoding of the =
object</div><div>&nbsp; &nbsp; &nbsp; list, performed by =
FCAST.</div><div><br></div></div><div><br></div><div>OLD item in =
3.3:</div><div><div>&nbsp; &nbsp;o &nbsp;Content-Encoding: a string that =
contains the optional encoding of</div><div>&nbsp; &nbsp; &nbsp; the =
object performed by FCAST. &nbsp;If there is no =
Content-Encoding</div><div>&nbsp; &nbsp; &nbsp; entry, the receiver MUST =
assume that the object is not encoded</div><div>&nbsp; &nbsp; &nbsp; =
(default). &nbsp;The support of GZIP encoding, or any other =
solution,</div><div>&nbsp; &nbsp; &nbsp; remains =
optional.</div><div><br></div></div><div><br></div><div>NEW item in =
3.3:</div><div><div><br></div><div><div><div>&nbsp; &nbsp;o =
&nbsp;Content-Encoding: a string that contains the optional encoding =
of</div><div>&nbsp; &nbsp; &nbsp; the object performed by FCAST. =
&nbsp;For instance:</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Content-Encoding: gzip</div><div>&nbsp; &nbsp; &nbsp; indicates =
that the Object List field has been encoded with GZIP</div><div>&nbsp; =
&nbsp; &nbsp; [RFC1952]. &nbsp;If there is no Content-Encoding entry, =
the receiver</div><div>&nbsp; &nbsp; &nbsp; MUST assume that FCAST did =
not perform any encoding to the object</div><div>&nbsp; &nbsp; &nbsp; =
(default).</div></div></div></div><div><br></div><div><br></div><div>While=
 doing that I realized that the&nbsp;Fcast-CID-Complete =
and&nbsp;Fcast-CID-ID</div><div>were not mentioned at all in the =
"compliant implementations"&nbsp;section. This</div><div>is now =
corrected as follows:</div><div><br></div><div>NEW item =
in&nbsp;"compliant implementations" =
section:</div><div><br></div><div><div>&nbsp; &nbsp;CID-specific =
Meta-data items (Section 2.2):</div><div><br></div><div><font =
class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp; &nbsp; =
&nbsp;+-----------------------+-------------------+</font></div><div><font=
 class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp; &nbsp; =
&nbsp;| Feature &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Status &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</font></div><div><font =
class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp; &nbsp; =
&nbsp;+-----------------------+-------------------+</font></div><div><font=
 class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp; &nbsp; =
&nbsp;| Fcast-CID-Complete &nbsp; &nbsp;| MUST be supported =
|</font></div><div><font class=3D"Apple-style-span" face=3D"'Courier =
New'">&nbsp; &nbsp; &nbsp; &nbsp;| Fcast-CID-ID &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;| MUST be supported |</font></div><div><font =
class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp; &nbsp; =
&nbsp;+-----------------------+-------------------+</font></div><div><br><=
/div></div><br><blockquote type=3D"cite"><div lang=3D"EN-US" link=3D"blue"=
 vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></span><span =
class=3D"Apple-style-span" style=3D"font-family: Calibri, sans-serif; =
font-size: 15px; line-height: 17px; ">Nits/editorial =
comments:</span></div></div></div></blockquote><div><br></div><div><br></d=
iv><div>The following 4 comments have been =
resolved.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" =
link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><p class=3D"MsoNormal" style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 10pt; margin-left: 0in; line-height: =
17px; font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p></o:p></p><ol start=3D"1" type=3D"1" style=3D"margin-bottom: 0in; =
margin-top: 0in; "><li class=3D"MsoNormal" style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 10pt; margin-left: 0in; line-height: =
17px; font-size: 11pt; font-family: Calibri, sans-serif; ">In section =
5.1 at the end of first table =93in-bound=94 should be =
=93in-band=94<o:p></o:p></li><li class=3D"MsoNormal" style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 10pt; margin-left: 0in; =
line-height: 17px; font-size: 11pt; font-family: Calibri, sans-serif; =
">In section 6 in the paragraph after the bullet points =93possibly =
possibly=94<o:p></o:p></li><li class=3D"MsoNormal" style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 10pt; margin-left: 0in; =
line-height: 17px; font-size: 11pt; font-family: Calibri, sans-serif; =
">In section 7 =93This specification requires IANA to create two new =
registries=94 I think there are three new registries.<o:p></o:p></li><li =
class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 10pt; margin-left: 0in; line-height: 17px; font-size: =
11pt; font-family: Calibri, sans-serif; ">In section 7.1 second =
paragraph =93registry =
registry=94</li></ol></div></div></blockquote><div><br></div>Thanks a =
lot for your comments.</div><div>Cheers,</div><div><br></div><div>&nbsp; =
&nbsp;Vincent</div><div><br></div></div></body></html>=

--Apple-Mail-1-215950537--

From mahoney@nostrum.com  Thu Feb 14 15:34:10 2013
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 496F421F8960 for <gen-art@ietfa.amsl.com>; Thu, 14 Feb 2013 15:34:10 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KGHVXiCJNVWi for <gen-art@ietfa.amsl.com>; Thu, 14 Feb 2013 15:34:09 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 29C8421F86DD for <gen-art@ietf.org>; Thu, 14 Feb 2013 15:34:09 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r1ENY80W016762 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 14 Feb 2013 17:34:08 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <511D7470.20400@nostrum.com>
Date: Thu, 14 Feb 2013 17:34:08 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
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 (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-02-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 Feb 2013 23:34:10 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Ben Campbell       2013-02-28   draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04 *
  
Elwyn Davies       2013-02-22   draft-ietf-idr-as-private-reservation-03

Francis Dupont     2013-02-25   draft-ietf-dhc-secure-dhcpv6-07 **

Joel Halpern       2013-02-26   draft-ietf-tcpm-proportional-rate-reduction-04 **

Kathleen Moriarty  2013-02-27   draft-ietf-geopriv-flow-identity-01

Martin Thomson     2013-02-27   draft-ietf-mpls-gach-adv-06
  

* Last Call extended due to IPR disclosure 1710
** On the 2/28 telechat


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

And 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


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 Feb 14 15:34:19 2013
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 AC5BB21F8962 for <gen-art@ietfa.amsl.com>; Thu, 14 Feb 2013 15:34:19 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qpvoVMkTD6gK for <gen-art@ietfa.amsl.com>; Thu, 14 Feb 2013 15:34:19 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 105D121F8960 for <gen-art@ietf.org>; Thu, 14 Feb 2013 15:34:18 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r1ENYIoK016788 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 14 Feb 2013 17:34:18 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <511D747A.3000808@nostrum.com>
Date: Thu, 14 Feb 2013 17:34:18 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
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 (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2013-02-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 Feb 2013 23:34:19 -0000

Hi all,

The following reviewers have assignments:

Reviewer             LC end      Draft

Alexey Melnikov      2013-01-24  draft-ietf-idr-deprecate-dpa-etal-00 **

Brian Carpenter      2013-02-05  draft-ietf-behave-nat64-discovery-heuristic-13 **
Brian Carpenter      2013-01-25  draft-ietf-eman-rfc4133bis-06 *

Christer Holmberg    2013-02-20  draft-shafranovich-mime-sql-04 *
Christer Holmberg    2013-02-20  draft-templin-intarea-seal-51

David Black          2012-08-20  draft-ietf-pwe3-mpls-eth-oam-iwk-07 **

Dan Romascanu        2013-02-06  draft-ietf-mpls-tp-security-framework-08 *

Joel Halpern         2013-02-11  draft-leiba-urnbis-ietf-namespace-02 *

Mary Barnes          2013-02-19  draft-ietf-p2psip-base-24 *

Meral Shirazipour    2013-01-25  draft-ietf-radext-radius-extensions-11 *
Meral Shirazipour    2013-01-29  draft-ietf-6man-nd-extension-headers-03 **

Peter McCann         2013-02-18  draft-templin-ironbis-12

Roni Even            2013-02-19  draft-ietf-ancp-pon-04 **
Roni Even            2013-02-14  draft-gp-obsolete-icmp-types-iana-01 **

Vijay Gurbani        2013-02-14  draft-ietf-simple-simple-08 **

Wassim Haddad        2013-02-01  draft-ietf-xrblock-rtcp-xr-summary-stat-08
Wassim Haddad        2013-02-15  draft-ietf-paws-problem-stmt-usecases-rqmts-12

* Earlier draft reviewed
** Already reviewed


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

And 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

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 Feb 14 15:55:14 2013
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 7D51B21F8967 for <gen-art@ietfa.amsl.com>; Thu, 14 Feb 2013 15:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.262
X-Spam-Level: 
X-Spam-Status: No, score=-102.262 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDL6n48UUlwn for <gen-art@ietfa.amsl.com>; Thu, 14 Feb 2013 15:55:14 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1FEB321F8953 for <gen-art@ietf.org>; Thu, 14 Feb 2013 15:55:14 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id DD5F0A6B74 for <gen-art@ietf.org>; Thu, 14 Feb 2013 15:55:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id C10B62C128A; Thu, 14 Feb 2013 15:55:12 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-135-91.clppva.east.verizon.net [70.106.135.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id E0D592C1289; Thu, 14 Feb 2013 15:55:11 -0800 (PST)
Message-ID: <511D7957.2030609@joelhalpern.com>
Date: Thu, 14 Feb 2013 18:55:03 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <50F88571.90201@nostrum.com>
In-Reply-To: <50F88571.90201@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, gen-art@ietf.org, Barry Leiba <barryleiba@computer.org>
Subject: [Gen-art]   review: draft-leiba-urnbis-ietf-namespace-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, 14 Feb 2013 23: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-leiba-urnbis-ietf-namespace-02
     Registration of Second-Level URI Namespaces Under "ietf"
Reviewer: Joel M. Halpern
Review Date: 14-Feb-2013
IETF LC End Date: 11-Feb-2013
IESG Telechat date: 21-Feb-2013

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

Major issues: None.

Minor issues: None
     Thank you for fixing the minor inconsistency noted in the previous 
review.

Nits/editorial comments: None.

https://www.ietf.org/mailman/listinfo/gen-art


From jmh@joelhalpern.com  Thu Feb 14 16:26:24 2013
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 D58E921F8619 for <gen-art@ietfa.amsl.com>; Thu, 14 Feb 2013 16:26:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.262
X-Spam-Level: 
X-Spam-Status: No, score=-102.262 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Woh0Qklu3xxP for <gen-art@ietfa.amsl.com>; Thu, 14 Feb 2013 16:26:24 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 7809F21F85D0 for <gen-art@ietf.org>; Thu, 14 Feb 2013 16:26:24 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 56F16A3B34 for <gen-art@ietf.org>; Thu, 14 Feb 2013 16:26:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 21F571C07F0; Thu, 14 Feb 2013 16:26:24 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-135-91.clppva.east.verizon.net [70.106.135.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 2BFD31C0179; Thu, 14 Feb 2013 16:26:23 -0800 (PST)
Message-ID: <511D80A6.7090705@joelhalpern.com>
Date: Thu, 14 Feb 2013 19:26:14 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
References: <511D7470.20400@nostrum.com>
In-Reply-To: <511D7470.20400@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Wesley Eddy <wes@mti-systems.com>, pasi.sarolahti@iki.fi, draft-ietf-tcpm-proportional-rate-reduction@tools.ietf.org
Subject: [Gen-art] Review: draft-ietf-tcpm-proportional-rate-reduction-04.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, 15 Feb 2013 00:26: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-tcpm-proportional-rate-reduction-04.txt
     Proportional Rate Reduction for TCP
Reviewer: Joel M. Halpern
Review Date: 14-Feb-2013
IETF LC End Date: 26-Feb-2013
IESG Telechat date: 28-Feb-2013

Summary: This document is ready for publication as an Experimental RFC

Major issues:

Minor issues:

Nits/editorial comments:
     Much of the information in the Abstract could be left out.  It 
suffices for it to be present in the Introduction, as it is.

From brian.e.carpenter@gmail.com  Fri Feb 15 00:57:32 2013
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 1222E21F87D9 for <gen-art@ietfa.amsl.com>; Fri, 15 Feb 2013 00:57:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.835
X-Spam-Level: 
X-Spam-Status: No, score=-100.835 tagged_above=-999 required=5 tests=[AWL=0.856, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12XsspcHFSbI for <gen-art@ietfa.amsl.com>; Fri, 15 Feb 2013 00:57:31 -0800 (PST)
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by ietfa.amsl.com (Postfix) with ESMTP id CC4A821F8A0C for <gen-art@ietf.org>; Fri, 15 Feb 2013 00:57:30 -0800 (PST)
Received: by mail-wi0-f173.google.com with SMTP id hq4so846874wib.12 for <gen-art@ietf.org>; Fri, 15 Feb 2013 00:57:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type; bh=jP56dbH9hbXpgebCohU6lM5eFbltd8nHGJQk6ioVHi4=; b=LmaOA+nMnpTZy1OxVeKEXzWCfU7raOydsgt9R1EubacNK7tSe0m08enNCA9izeHnwX RZwn3kDVof+9mF7h5ZZd4lsVRKnlvNB0WnqGe0cPOXPoX7zwwVBBXX1K42g7QIK38iCl SylpCMNcPxeRxgc/Ph+d2Oj0C/rfmoet7MQ733V6X/6wk2Y8JQkExXB1dce71Lgx7xWp 2rFa2gW0WKOJiNlcPoEs7nUMp7iYTtFQ/cqqNDjfBjPORTk05khWtVnM8DlVfKiVWQCR b/a4Fbyyn9edgADWICeyBUWrvOGRjeKt8sxPFcp/RMgS8qETv6C7hxe/SCGOgNhsfueK epyA==
X-Received: by 10.180.79.201 with SMTP id l9mr2544064wix.20.1360918650016; Fri, 15 Feb 2013 00:57:30 -0800 (PST)
Received: from [192.168.1.65] (host-2-101-188-220.as13285.net. [2.101.188.220]) by mx.google.com with ESMTPS id bs6sm3939390wib.4.2013.02.15.00.57.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Feb 2013 00:57:29 -0800 (PST)
Message-ID: <511DF887.3090706@gmail.com>
Date: Fri, 15 Feb 2013 08:57:43 +0000
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-eman-rfc4133bis.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------010408090103020600030807"
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-eman-rfc4133bis-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: Fri, 15 Feb 2013 08:57:32 -0000

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

Please see attached review.

     Brian






--------------010408090103020600030807
Content-Type: text/plain;
 name="draft-ietf-eman-rfc4133bis-06-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-eman-rfc4133bis-06-carpenter.txt"

SSBoYXZlIGJlZW4gc2VsZWN0ZWQgYXMgdGhlIEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAo
R2VuLUFSVCkNCnJldmlld2VyIGZvciB0aGlzIGRyYWZ0IChmb3IgYmFja2dyb3VuZCBvbiBH
ZW4tQVJULCBwbGVhc2Ugc2VlDQpodHRwOi8vd3d3LmFsdmVzdHJhbmQubm8vaWV0Zi9nZW4v
YXJ0L2dlbi1hcnQtRkFRLmh0bWwpLg0KDQpQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZy
b20geW91ciBkb2N1bWVudCBzaGVwaGVyZA0Kb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcg
dmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLWVtYW4tcmZj
NDEzM2Jpcy0wNi50eHQNClJldmlld2VyOiBCcmlhbiBDYXJwZW50ZXINClJldmlldyBEYXRl
OiAyMDEzLTAyLTE1DQpJRVRGIExDIEVuZCBEYXRlOiAyMDEzLTAxLTI1DQpJRVNHIFRlbGVj
aGF0IGRhdGU6IDIwMTMtMDItMjENCg0KU3VtbWFyeTogIFJlYWR5DQotLS0tLS0tLQ0KDQpD
b21tZW50OiAgDQotLS0tLS0tLQ0KDQpNeSBMYXN0IENhbGwgY29tbWVudHMgd2VyZSBoYW5k
bGVkLCB0aGFua3MuIFRoZXJlIGFyZSBudW1lcm91cyBjaGFuZ2VzIHRvIHRoZSBNSUINCm1v
ZHVsZSBzaW5jZSBMYXN0IENhbGwsIGJ1dCB0byBteSBpZ25vcmFudCBleWUgdGhleSBzZWVt
IE9LLg==
--------------010408090103020600030807--

From brian.e.carpenter@gmail.com  Fri Feb 15 01:07:22 2013
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 40EEA21F89A3 for <gen-art@ietfa.amsl.com>; Fri, 15 Feb 2013 01:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.88
X-Spam-Level: 
X-Spam-Status: No, score=-100.88 tagged_above=-999 required=5 tests=[AWL=0.811, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-060GrpjALG for <gen-art@ietfa.amsl.com>; Fri, 15 Feb 2013 01:07:21 -0800 (PST)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by ietfa.amsl.com (Postfix) with ESMTP id 910EC21F8996 for <gen-art@ietf.org>; Fri, 15 Feb 2013 01:07:14 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id fg15so2535273wgb.25 for <gen-art@ietf.org>; Fri, 15 Feb 2013 01:07:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type; bh=YzsD1rs4rDr54bAUdzfVjdbhGKs6TZZdpxIVGo+Bua8=; b=L6VO3nQMQ9X6j3CtSpITz3xGdxQ4x4uq00okCuPSyc+FrMj5K5Vq1OKJ8/E6Ql+8xF +zgS9Uby4mXSAcLyNL2kDk10LBz+3DR0cbicE4CMoUWulqtvPqfrsrE+gWgQ8qt6Cdy2 10Pt9Jg7vikeKv+KDtnV7M9jbBsZL9axSsX5Y5JWRECxwok9/mkPkKrlFyPJAHFi6uSG tgkL250HxF7kHzREtpGmUnxrji+8dHyyKD8El7h7bf+6jRoC4U4XwZoCVb3h+W5BxavA Cvcf2WPxlXjTx+3ScmyoldtEcA0k4LUNDEQSoS5YjzMauHOaxq6Pls2GF9KFqU+7Z5Wj hVgg==
X-Received: by 10.180.85.103 with SMTP id g7mr2614225wiz.29.1360919233740; Fri, 15 Feb 2013 01:07:13 -0800 (PST)
Received: from [192.168.1.65] (host-2-101-188-220.as13285.net. [2.101.188.220]) by mx.google.com with ESMTPS id o8sm3558772wix.7.2013.02.15.01.07.12 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Feb 2013 01:07:13 -0800 (PST)
Message-ID: <511DFACE.20903@gmail.com>
Date: Fri, 15 Feb 2013 09:07:26 +0000
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-behave-nat64-discovery-heuristic.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------010607010203090308090304"
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-behave-nat64-discovery-heuristic-13.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, 15 Feb 2013 09:07:22 -0000

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

Please see attached review.

     Brian

--------------010607010203090308090304
Content-Type: text/plain;
 name="draft-ietf-behave-nat64-discovery-heuristic-13-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename*0="draft-ietf-behave-nat64-discovery-heuristic-13-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBM
YXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IGRyYWZ0
LWlldGYtYmVoYXZlLW5hdDY0LWRpc2NvdmVyeS1oZXVyaXN0aWMtMTMudHh0DQpSZXZpZXdl
cjogQnJpYW4gQ2FycGVudGVyDQpSZXZpZXcgRGF0ZTogMjAxMy0wMi0xNQ0KSUVURiBMQyBF
bmQgRGF0ZTogMjAxMy0wMi0wNQ0KSUVTRyBUZWxlY2hhdCBkYXRlOiAyMDEzLTAyLTIxDQoN
ClN1bW1hcnk6ICBBbG1vc3QgcmVhZHkgKGJ1dCBkZWZpbml0ZWx5IE5PVCByZWFkeSkNCi0t
LS0tLS0tDQoNCkNvbW1lbnQ6DQotLS0tLS0tLQ0KDQpUaGlzIGlzIGlkZW50aWNhbCB0byBt
eSBMYXN0IENhbGwgcmV2aWV3IGFzIEkgaGF2ZSBzZWVuIG5vIHJlc3BvbnNlIGZyb20gdGhl
IGF1dGhvcnMuDQpJJ3ZlIGNsYXNzaWZpZWQgdGhlIGlzc3VlcyBhcyBtaW5vciwgYnV0IEkg
dGhpbmsgdGhleSBuZWVkIHRvIGJlIGZpeGVkLiBJQU5BIGhhcyBzZXJpb3VzDQpjb21tZW50
cyB0b28uDQoNCkZpcnN0bHkgbGV0IG1lIG5vdGUgdGhhdCBJIGtlcHQgb3V0IG9mIHRoZSBk
aXNjdXNzaW9uIG9mIHRoaXMgZHJhZnQgaW4gQkVIQVZFLCBhbHRob3VnaA0KSSdtIGNvbXBs
ZXRlbHkgZmFtaWxpYXIgd2l0aCBOQVQ2NCBhbmQgRE5TNjQuDQoNCkl0IGlzIGluZGVlZCBh
IGhldXJpc3RpYy4gQXMgZmFyIGFzIEkgY2FuIHRlbGwgaXQncyB0aGUgYmVzdCB0aGF0IGNh
biBiZSBkb25lIGFuZCBpdA0Kd2FzIHZlcnkgdGhvcm91Z2hseSBiYXNoZWQgYXJvdW5kIGlu
IHRoZSBXRy4gSSBqdXN0IGRvbid0IGZpbmQgaXQgY29udmluY2luZw0KYXMgc3RhbmRhcmRz
IHRyYWNrIG1hdGVyaWFsOyBpdCB3YWxrcywgdGFsa3MgYW5kIHF1YWNrcyBsaWtlIGFuIEV4
cGVyaW1lbnRhbCBSRkMuDQpUaGlzIGlzIHBlcnNvbmFsIG9waW5pb24gYW5kIHRoZSBjb3Vu
dGVyLWFyZ3VtZW50IGlzIGF0DQpodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93
ZWIvYmVoYXZlL2N1cnJlbnQvbXNnMTA1MTcuaHRtbA0KDQpNaW5vciBJc3N1ZXM6ICANCi0t
LS0tLS0tLS0tLS0NCg0KVGhpcyBkb2N1bWVudCBkZWZpbml0ZWx5IGNhbm5vdCBiZSB1bmRl
cnN0b29kIGJ5IGFueW9uZSB3aG8gaGFzIG5vdCBmaXJzdA0KdW5kZXJzdG9vZCB0aGUgTkFU
NjQgYW5kIEROUzY0IGRvY3VtZW50cy4gSXQgbWlnaHQgYmUgdXNlZnVsIHRvIHN0YXRlDQp0
aGlzIGV4cGxpY2l0bHkgaW4gdGhlIGZpcnN0IHBhcmFncmFwaC4gDQoNCiIgIEEgZGF5IHdp
bGwgY29tZSB3aGVuIHRoaXMgdG9vbCBpcyBubyBsb25nZXIgbmVlZGVkLiAgQXQgdGhhdCBw
b2ludA0KICAgdGhlIGJlc3Qgc3VpdGVkIHRlY2huaXF1ZXMgZm9yIGltcGxlbWVudGluZyBh
biBleGl0IHN0cmF0ZWd5IHdpbGwgYmUNCiAgIGRvY3VtZW50ZWQuIg0KDQpUaGUgc2Vjb25k
IHNlbnRlbmNlIHJlYWxseSBzYXlzIG5vdGhpbmcuIFdoeSBpcyBhbnkgc3RyYXRlZ3kgb3Ro
ZXIgdGhhbg0KYW4gIm9mZiIgc3dpdGNoIHJlcXVpcmVkPyBJZiB0aGVyZSBhcmUgbm8gbW9y
ZSBJUHY0LW9ubHkgc2VydmljZXMsIHRoZXJlDQp3aWxsIGJlIChvYnNlcnZhYmx5KSBubyB0
cmFmZmljIGluIHRoZSBOQVQ2NCBib3guDQoNCjguICBJQU5BIENvbnNpZGVyYXRpb25zDQoN
CiAgICJUaGUgd2VsbC1rbm93biBkb21haW4gbmFtZSBjb3VsZCBiZSwgZm9yIGV4YW1wbGUs
ICJpcHY0b25seS5hcnBhIi4gIg0KDQpJZiBpdCdzIGFuIGV4YW1wbGUsIHlvdSBjYW4ndCBy
ZWZlciB0byBpdCB1bmNvbmRpdGlvbmFsbHkgZWFybGllciBpbiB0aGUgZG9jdW1lbnQuDQpJ
IHdvdWxkIG1ha2UgYW4gZXhwbGljaXQgcmVxdWVzdCB0byBJQU5BIGZvciB0aGlzIGV4YWN0
IG5hbWUuIE90aGVyd2lzZSwgeW91J2QgbmVlZA0KdG8gcmVwbGFjZSBhbGwgb2NjdXJyZW5j
ZXMgb2YgaXB2NG9ubHkuYXJwYSBieSBGUUROLVRCRCBhbmQgaGF2ZSB0aGUgUkZDIEVkaXRv
cg0KZml4IGl0IHVwLg0KDQpUaGUgc2FtZSB0aGluZyBhcHBsaWVzIHRvIDE5Mi4wLjAuMTcw
IGFuZCAxOTIuMC4wLjE3MS4gRWl0aGVyIHRoZXkgbmVlZCB0byBiZQ0KVEJEMSBhbmQgVEJE
MiBpbiB0aGUgdGV4dCwgb3IgeW91IG5lZWQgYW4gZXhwbGljaXQgcmVxdWVzdCB0byBJQU5B
Lg0KDQpXaG8gcG9wdWxhdGVzIHRoZSBETlMgd2l0aCB0aGUgUlJzIGZvciBpcHY0b25seS5h
cnBhPyBUaGF0IHJlc3BvbnNpYmlsaXR5IG5lZWRzDQp0byBiZSBkZWZpbmVkLg==
--------------010607010203090308090304--

From elwynd@dial.pipex.com  Fri Feb 15 01:15:34 2013
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 CB1B321F8953 for <gen-art@ietfa.amsl.com>; Fri, 15 Feb 2013 01:15:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uT4GUkj6A+WI for <gen-art@ietfa.amsl.com>; Fri, 15 Feb 2013 01:15:33 -0800 (PST)
Received: from mk-outboundfilter-6.mail.uk.tiscali.com (mk-outboundfilter-6.mail.uk.tiscali.com [212.74.114.14]) by ietfa.amsl.com (Postfix) with ESMTP id 1344421F885C for <gen-art@ietf.org>; Fri, 15 Feb 2013 01:15:32 -0800 (PST)
X-Trace: 545999524/mk-outboundfilter-6.mail.uk.tiscali.com/PIPEX/$OFF_NET_AUTH_ACCEPTED/None/192.165.126.77/None/elwynd@dial.pipex.com
X-SBRS: None
X-RemoteIP: 192.165.126.77
X-IP-MAIL-FROM: elwynd@dial.pipex.com
X-SMTP-AUTH: elwynd@dial.pipex.com
X-MUA: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAKb7HVHApX5N/2dsb2JhbAANN8B7g1FAAS8NFhgDAgECAUsNAQcBAYgaqWKTLZIDA5YngR2EQY1+
X-IronPort-AV: E=Sophos;i="4.84,672,1355097600"; d="scan'208";a="545999524"
X-IP-Direction: OUT
Received: from aptilo1-sesb.ericsson.net (HELO [10.156.69.237]) ([192.165.126.77]) by smtp.pipex.tiscali.co.uk with ESMTP; 15 Feb 2013 09:15:26 +0000
Message-ID: <511DFCAD.6020509@dial.pipex.com>
Date: Fri, 15 Feb 2013 10:15:25 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org
Subject: [Gen-art] Gen-art last call review of draft-ietf-idr-as-private-reservation-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, 15 Feb 2013 09:15: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 Last Call comments
you may receive.

Document: draft-ietf-idr-as-private-reservation-03.txt
Reviewer: Elwyn Davies
Review Date: 15 February 2013
IETF LC End Date: 22 February 2013
IESG Telechat date: (if known) -

Summary: Ready for the IESG.

Nits/editorial comments:  The draft is not actually definitive about 
range of values to be allocated - the range in s10 is just a 
'suggestion'.  Who is actually making the decision about the range?

Aside: I noted that the highest possible 32 bit number (4294967295 = 
0xFFFFFFFF) is excluded from the proposed range.  This is marked as 
reserved in the IANA table but AFAICS this reserved item does not have a 
specification associated with the reservation.  This document would be 
an opportunity to explicitly mention that the topmost value is reserved 
(for future expansion? :-) )



From martin.thomson@gmail.com  Fri Feb 15 11:33:06 2013
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 19FC821F8675 for <gen-art@ietfa.amsl.com>; Fri, 15 Feb 2013 11:33:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.864
X-Spam-Level: 
X-Spam-Status: No, score=-4.864 tagged_above=-999 required=5 tests=[AWL=-1.265, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vddm5bnyApSl for <gen-art@ietfa.amsl.com>; Fri, 15 Feb 2013 11:33:04 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id D3B1221F8673 for <gen-art@ietf.org>; Fri, 15 Feb 2013 11:33:03 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id o1so1590010wic.5 for <gen-art@ietf.org>; Fri, 15 Feb 2013 11:33:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=VdroZKzO9ljIyGgBTQlUjEL7ddAHzSENZaZ4Nxqswh8=; b=PMIqz1F9HOsJVIjvVKeazIWretiAIS3DdtJtyd91HISi9STqA9HAs6ujnKzDPhtiw9 AkD4hrXcGe+cAqID5Wkr5OIEPnYPG3OZe8REIHlcqqMvLpr3vhD0wzB4VTMHCca3ZTGG 3WvggfMKsfgeObZA+BALKXCQrfZSaymrwFy3EzDKOc/qo166yH1qXU1u5nHFYa7FyLzQ 5BDakRnqlZGSl1HbSKQY6v5+uQbOBfCLrXaxJjo1IhdvUwFzKYsjBjwjTnXI9a7g6iPR Lngb8qRAhQpQ9bnq2QjbZ+OhX+oIbDDIHurQcVjXRlS5IqZcIxsNJNyv9gjnIwaoQijd hEhw==
MIME-Version: 1.0
X-Received: by 10.180.8.130 with SMTP id r2mr6314543wia.28.1360956783032; Fri, 15 Feb 2013 11:33:03 -0800 (PST)
Received: by 10.194.5.135 with HTTP; Fri, 15 Feb 2013 11:33:02 -0800 (PST)
Date: Fri, 15 Feb 2013 11:33:02 -0800
Message-ID: <CABkgnnW-53MVHZaW4QweqBjrPGCrP=fCNQ+LJdaG__ePh2tn1A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-gach-adv.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [Gen-art] Gen-ART review of draft-ietf-mpls-gach-adv-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, 15 Feb 2013 19:33:06 -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-mpls-gach-adv-06
Reviewer: Martin Thomson
Review Date: 2013-02-15
IETF LC End Date: 2013-02-27
IESG Telechat date: (if known)

Summary: The document is almost ready for publication as proposed
standard.  There is a major issue that should be easy to resolve.

Major issues:

Section 6.3 duplicates the description of HMAC provided in RFC 2104.
That is likely to cause a bug.

If you reference RFC 2104, then the only requirement is a clear
specification for what message is input to the HMAC.  Currently, this
is buried.  It is unclear if the input includes the G-ACh header
defined in RFC 5586 (it doesn't need to, but this needs to be made
explicit).

Filling the authentication part with 0x878FE1F3 seems unnecessary busy
work, but it's harmless as long as the hash function produces a
multiple of 32 bits of output.

Minor issues:

To avoid forward compatibility issues, reserved fields should come
with guidance that says: "Implementations of this protocol version
MUST set reserved fields to all zero bits when sending and ignore any
value when receiving messages."

In Section 4.4, how does the duration interact with the lifetime?
What happens when the duration is longer than lifetime such that the
TLV is expunged before the duration is up?

Section 5.2 states:
   [...] If one
   of the received TLV objects has the same Type as a previously
   received TLV then the data from the new object SHALL replace the data
   associated with that Type unless the X specification dictates a
   different behavior.

This leads to different retention characteristics depending on some
arbitrary application-specific requirements.  It also complicates
implementations.  Is there a strong motivation for the "unless the X
specification dictates a different behavior" part of this statement?

If this behaviour is desirable, a note regarding what happens to the
composed TLV when some of the values that contribute to it might
expire might be necessary.

Regarding the last paragraph of Section 6.3:
          This also means that the use of hash functions with larger
          output sizes will increase the size of the GAP message as
          transmitted on the wire.

If you want to prevent hash truncation, then use 'MUST'.  Personally,
I see no reason to do so.  It's a good way to get smaller messages,
with a corresponding reduction in the strength of the assurance
provided.

Nits:

Section 3 could use some subheadings to aid navigation (and referencing).

Section 3 describes the size of fields only through ASCII-art.  It's a
fairly simple thing to add a bit count to the description of each
field.  That includes the reserved fields, which have no descriptions.

I like the text in the editors note on page 8.  Why is it not the
actual text already?

Sections 4.2 and 4.3 could probably use a note that notes that
retention of these TLVs doesn't make any sense.  These could be sent
with zero lifetime, except that if these are sent along with the
Source Address TLV, that's not possible... unless you send multiple
application data blocks for the same application.  Is that possible?

From jdrosen@jdrosen.net  Sat Feb 16 04:21:34 2013
Return-Path: <jdrosen@jdrosen.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 2C67121F8700 for <gen-art@ietfa.amsl.com>; Sat, 16 Feb 2013 04:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.976
X-Spam-Level: 
X-Spam-Status: No, score=-101.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzhRnUGPMXko for <gen-art@ietfa.amsl.com>; Sat, 16 Feb 2013 04:21:33 -0800 (PST)
Received: from ecbiz71.inmotionhosting.com (ecbiz71.inmotionhosting.com [70.39.232.100]) by ietfa.amsl.com (Postfix) with ESMTP id E48CE21F84F4 for <gen-art@ietf.org>; Sat, 16 Feb 2013 04:21:32 -0800 (PST)
Received: from mail-wi0-f177.google.com ([209.85.212.177]:51220) by ecbiz71.inmotionhosting.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80) (envelope-from <jdrosen@jdrosen.net>) id 1U6gln-0003af-L2 for gen-art@ietf.org; Sat, 16 Feb 2013 07:21:31 -0500
Received: by mail-wi0-f177.google.com with SMTP id hm14so2059052wib.10 for <gen-art@ietf.org>; Sat, 16 Feb 2013 04:21:31 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.76.7 with SMTP id g7mr9427322wjw.50.1361017291357; Sat, 16 Feb 2013 04:21:31 -0800 (PST)
Received: by 10.194.165.230 with HTTP; Sat, 16 Feb 2013 04:21:31 -0800 (PST)
In-Reply-To: <5119101F.4030606@bell-labs.com>
References: <5119101F.4030606@bell-labs.com>
Date: Sat, 16 Feb 2013 07:21:31 -0500
Message-ID: <CA+23+fGBuQJpjeRFTFBQrHcyt3CABX5mzCdQhU8AA_qvgB6-TA@mail.gmail.com>
From: Jonathan Rosenberg <jdrosen@jdrosen.net>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: multipart/alternative; boundary=047d7beba2022f3e2404d5d688cf
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz71.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jdrosen.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Mailman-Approved-At: Sat, 16 Feb 2013 05:30:24 -0800
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-simple-simple@tools.ietf.org, "Hisham \(Hash\) Khartabil" <hisham.khartabil@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-simple-simple-08
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 Feb 2013 12:21:34 -0000

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

Hi Vijay,

Thanks for the comments. Responses below:




On Mon, Feb 11, 2013 at 10:37 AM, Vijay K. Gurbani <vkg@bell-labs.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<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-simple-simple-08
> Reviewer: Vijay K. Gurbani
> Review Date: Feb-11-2013
> IETF LC End Date: Feb-14-2013
> IESG Telechat date: Not known
>
> This document is ready as an Informational.  Some comments for
> changes follow.
>
> Major: 0
> Minor: 2
> Nits: 1
>
> Minor:
> - S2.1, discussion of rfc3265: RFC3265 is now made obsolete by rfc6665,
>  I believe an update is appropriate here as well as other places where
>  a reference to rfc3265 is made.
>

Fixed.


>
>  Additionally, a reference to rfc3856 will be appropriate when
>  we first talk about presence as a SUBS/NOT event package i.e.,
>  s/Presence is defined as an event package/Presence is defined as
>  an event package [RFC3865]/
>

Fixed.


>
> - S3.2, discussion of rfc3862: Does CPIM stand for "Common Presence and
>   Instant Messaging" or does it stand for "Common Profile for Instant
>   Messaging", as expanded in rfc3862 itself?
>

Actually, the title of RFC3862 is in fact "Common Presence and Instant
Messaging", even though the message format it defines is common profile for
instant messaging. As such, I have kept this since the acronym refers to
the title of the spec.


>
> Nits:
>
> - Abstract, perhaps better for a standard document to use more
>   formal language and:
>   s/It breaks them up into categories/It categorizes the specifications/
>

Fixed.


>
> 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<vijay.gurbani@alcatel-lucent.com>
> Web:   http://ect.bell-labs.com/who/**vkg/<http://ect.bell-labs.com/who/vkg/>
>


Thanks,
Jonathan R.

-- 
Jonathan Rosenberg, Ph.D.
jdrosen@jdrosen.net
http://www.jdrosen.net

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

<div dir=3D"ltr">Hi Vijay,<div><br></div><div>Thanks for the comments. Resp=
onses below:</div><div><br></div><div><br></div><div class=3D"gmail_extra">=
<br><br><div class=3D"gmail_quote">On Mon, Feb 11, 2013 at 10:37 AM, Vijay =
K. Gurbani <span dir=3D"ltr">&lt;<a href=3D"mailto:vkg@bell-labs.com" targe=
t=3D"_blank">vkg@bell-labs.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I am the assigned 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" tar=
get=3D"_blank">http://wiki.tools.ietf.org/<u></u>area/gen/trac/wiki/GenArtf=
aq</a>&gt;.<br>
<br>
Please resolve these comments along with any other Last Call comments<br>
you may receive.<br>
<br>
Document: draft-ietf-simple-simple-08<br>
Reviewer: Vijay K. Gurbani<br>
Review Date: Feb-11-2013<br>
IETF LC End Date: Feb-14-2013<br>
IESG Telechat date: Not known<br>
<br>
This document is ready as an Informational. =A0Some comments for<br>
changes follow.<br>
<br>
Major: 0<br>
Minor: 2<br>
Nits: 1<br>
<br>
Minor:<br>
- S2.1, discussion of rfc3265: RFC3265 is now made obsolete by rfc6665,<br>
=A0I believe an update is appropriate here as well as other places where<br=
>
=A0a reference to rfc3265 is made.<br></blockquote><div><br></div><div styl=
e>Fixed.</div><div style>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
=A0Additionally, a reference to rfc3856 will be appropriate when<br>
=A0we first talk about presence as a SUBS/NOT event package i.e.,<br>
=A0s/Presence is defined as an event package/Presence is defined as<br>
=A0an event package [RFC3865]/<br></blockquote><div><br></div><div style>Fi=
xed.</div><div style>=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- S3.2, discussion of rfc3862: Does CPIM stand for &quot;Common Presence an=
d<br>
=A0 Instant Messaging&quot; or does it stand for &quot;Common Profile for I=
nstant<br>
=A0 Messaging&quot;, as expanded in rfc3862 itself?<br></blockquote><div><b=
r></div><div style>Actually, the title of RFC3862 is in fact &quot;Common P=
resence and Instant Messaging&quot;, even though the message format it defi=
nes is common profile for instant messaging. As such, I have kept this sinc=
e the acronym refers to the title of the spec.</div>
<div style>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Nits:<br>
<br>
- Abstract, perhaps better for a standard document to use more<br>
=A0 formal language and:<br>
=A0 s/It breaks them up into categories/It categorizes the specifications/<=
br></blockquote><div><br></div><div style>Fixed.</div><div style>=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">

<br>
Thanks,<br>
<br>
- vijay<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- <br>
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent<br>
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)<br>
Email: vkg@{<a href=3D"http://bell-labs.com" target=3D"_blank">bell-labs.co=
m</a>,<a href=3D"http://acm.org" target=3D"_blank">acm.org</a>} / <a href=
=3D"mailto:vijay.gurbani@alcatel-lucent.com" target=3D"_blank">vijay.gurban=
i@alcatel-lucent.<u></u>com</a><br>

Web: =A0 <a href=3D"http://ect.bell-labs.com/who/vkg/" target=3D"_blank">ht=
tp://ect.bell-labs.com/who/<u></u>vkg/</a><br>
</font></span></blockquote></div><br><br clear=3D"all"><div style>Thanks,</=
div><div style>Jonathan R.</div><div style><br></div>-- <br><div dir=3D"ltr=
">Jonathan Rosenberg, Ph.D.<br><a href=3D"mailto:jdrosen@jdrosen.net" targe=
t=3D"_blank">jdrosen@jdrosen.net</a><br>
<a href=3D"http://www.jdrosen.net" target=3D"_blank">http://www.jdrosen.net=
</a></div>
</div></div>

--047d7beba2022f3e2404d5d688cf--

From vkg@bell-labs.com  Sun Feb 17 10:07:23 2013
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 CA4ED21F854A for <gen-art@ietfa.amsl.com>; Sun, 17 Feb 2013 10:07:22 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Dx3YNTwFw7A for <gen-art@ietfa.amsl.com>; Sun, 17 Feb 2013 10:07:17 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 949BC21F8B02 for <gen-art@ietf.org>; Sun, 17 Feb 2013 10:07:17 -0800 (PST)
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 r1HI7EpF008117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 17 Feb 2013 12:07:15 -0600 (CST)
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 r1HI7EuD026917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 17 Feb 2013 12:07:14 -0600
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.19.72]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1HI7AkF008666; Sun, 17 Feb 2013 12:07:10 -0600 (CST)
Message-ID: <51211CE0.9030408@bell-labs.com>
Date: Sun, 17 Feb 2013 12:09:36 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@jdrosen.net>
References: <5119101F.4030606@bell-labs.com> <CA+23+fGBuQJpjeRFTFBQrHcyt3CABX5mzCdQhU8AA_qvgB6-TA@mail.gmail.com>
In-Reply-To: <CA+23+fGBuQJpjeRFTFBQrHcyt3CABX5mzCdQhU8AA_qvgB6-TA@mail.gmail.com>
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>, draft-ietf-simple-simple@tools.ietf.org, "Hisham \(Hash\) Khartabil" <hisham.khartabil@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-simple-simple-08
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 Feb 2013 18:07:23 -0000

On 02/16/2013 06:21 AM, Jonathan Rosenberg wrote:
>     - S3.2, discussion of rfc3862: Does CPIM stand for "Common Presence and
>        Instant Messaging" or does it stand for "Common Profile for Instant
>        Messaging", as expanded in rfc3862 itself?
>
>
> Actually, the title of RFC3862 is in fact "Common Presence and Instant
> Messaging", even though the message format it defines is common profile
> for instant messaging. As such, I have kept this since the acronym
> refers to the title of the spec.

Jonathan: Sure, no worries.

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 Francis.Dupont@fdupont.fr  Mon Feb 18 06:54:07 2013
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 19CAF21F89D5 for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 06:53:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.932
X-Spam-Level: 
X-Spam-Status: No, score=-2.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G57W0ggpQx7G for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 06:53:51 -0800 (PST)
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 C779B21F890E for <gen-art@ietf.org>; Mon, 18 Feb 2013 06:53:50 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r1IErhWQ036131; Mon, 18 Feb 2013 15:53:43 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201302181453.r1IErhWQ036131@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 18 Feb 2013 15:53:43 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: draft-laurie-pki-sunlight.all@tools.ietf.org
Subject: [Gen-art] review of draft-laurie-pki-sunlight-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: Mon, 18 Feb 2013 14:54:08 -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-laurie-pki-sunlight-07.txt
Reviewer: Francis Dupont
Review Date: 20130208
IETF LC End Date: 20130226
IESG Telechat date: unknown

Summary: Almost Ready

Major issues: None

Minor issues:
 - section 2 is not enough accurate, for instance:
  * the critical [k1:k2] notation is introduced after its first use, IMHO
   it is the primary one, i.e., [n] is a short hand for [0:n]
  * the largest power of two must be strictly smaller, not just smaller.
   Without this critical detail recursion rules don't work for n = 2^m
 Unfortunately there is no wikipedia or equivalent web page where to refer to
 so the document is the place where all gory details have to be...

 - the Maximum Merge Delay (MMD) is an important parameter but I can't find
  where is the way users get its value, nor any recommendation for it.

Nits/editorial comments:
 - 1 page 4: CA is not a well known abbrev so please introduce it
  (cf http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt)

 - 1 page 4: it is a general mechanism but what are its constraints at
  the exception of the intended usage. For instance is the mechanism
  applicable to any end entity public key certificate? or larger??

 - 1 page 5: misbehaviours -> misbehaviors
  (and 3.3 page 16, and others too)

 - 1 page 5: e.g. -> e.g.,

 - 2.1.1 page 6: i.e. -> i.e.,

 - 2.1.1 page 7 and 2.1.2 page 8: the wording "the length (k2 - k1) list"
  is IMHO a bit uncommon even I can understand it.

 - 2.1.4 page 10: using a key of at least 2048 bits. ->
  using a public key of at least 2048 bits. (or a modulus as it is for RSA?)

 - 3 pages 13, 14, etc: what is the language used for ASN.1? It is not
  ASN.1 itself, nor C?

 - 3.1 page 12: accomodate -> accommodate

 - 3.1 page 13: parenthesis around 65535 are not necessary (i.e, they
  are insipid and stupid :-)

 - 3.1 page 13: submmited -> submitted

 - 3.2 page 14: opaque TBSCertificate<1..2^16-1> add final ';'

 - 4.6 page 22: honour -> honor

 - 4.6 page 22: convering -> covering? 

BTW if the document creates new OID perhaps they should be put in an annex?

Regards

Francis.Dupont@fdupont.fr

PS: I noted there are still some LC comments in the ML.

From Jon.Mitchell@microsoft.com  Mon Feb 18 07:27:46 2013
Return-Path: <Jon.Mitchell@microsoft.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 9544021F87D7 for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 07:27:46 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3b+89ADzPRtA for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 07:27:45 -0800 (PST)
Received: from na01-by1-obe.outbound.o365filtering.com (na01-by1-obe.ptr.o365filtering.com [64.4.22.87]) by ietfa.amsl.com (Postfix) with ESMTP id 64F7321F8A14 for <gen-art@ietf.org>; Mon, 18 Feb 2013 07:27:26 -0800 (PST)
Received: from CH1SR01CA101.namsdf01.sdf.exchangelabs.com (10.255.157.18) by CH1SR01MB612.namsdf01.sdf.exchangelabs.com (10.255.157.40) with Microsoft SMTP Server (TLS) id 15.0.620.19; Mon, 18 Feb 2013 15:27:18 +0000
Received: from SN2FFOFD003.ffo.gbl (157.55.158.26) by CH1SR01CA101.outlook.office365.com (10.255.157.18) with Microsoft SMTP Server (TLS) id 15.0.620.19 via Frontend Transport; Mon, 18 Feb 2013 15:27:18 +0000
Received: from hybrid.exchange.microsoft.com (131.107.1.27) by SN2FFOFD003.mail.o365filtering.com (10.111.201.40) with Microsoft SMTP Server (TLS) id 15.0.620.12 via Frontend Transport; Mon, 18 Feb 2013 15:27:17 +0000
Received: from DFM-TK5MBX15-02.exchange.corp.microsoft.com (157.54.110.9) by DF-G14-02.exchange.corp.microsoft.com (157.54.87.56) with Microsoft SMTP Server (TLS) id 14.3.123.1; Mon, 18 Feb 2013 07:26:55 -0800
Received: from DFM-DB3MBX15-07.exchange.corp.microsoft.com (10.166.18.225) by DFM-TK5MBX15-02.exchange.corp.microsoft.com (157.54.110.9) with Microsoft SMTP Server (TLS) id 15.0.620.14; Mon, 18 Feb 2013 07:26:53 -0800
Received: from DFM-DB3MBX15-08.exchange.corp.microsoft.com (10.166.18.226) by DFM-DB3MBX15-07.exchange.corp.microsoft.com (10.166.18.225) with Microsoft SMTP Server (TLS) id 15.0.620.14; Mon, 18 Feb 2013 07:26:32 -0800
Received: from DFM-DB3MBX15-08.exchange.corp.microsoft.com ([169.254.12.208]) by DFM-DB3MBX15-08.exchange.corp.microsoft.com ([169.254.12.90]) with mapi id 15.00.0620.012; Mon, 18 Feb 2013 07:26:21 -0800
From: "Jon Mitchell (GNS)" <Jon.Mitchell@microsoft.com>
To: Elwyn Davies <elwynd@dial.pipex.com>, General Area Review Team <gen-art@ietf.org>
Thread-Topic: Gen-art last call review of draft-ietf-idr-as-private-reservation-03
Thread-Index: AQHOC10lIVUr21ivuU+LWoBnRrohjph/sC6Q
Date: Mon, 18 Feb 2013 15:26:21 +0000
Message-ID: <f1195a2f3468441d85edaf0b8b843bba@DFM-DB3MBX15-08.exchange.corp.microsoft.com>
References: <511DFCAD.6020509@dial.pipex.com>
In-Reply-To: <511DFCAD.6020509@dial.pipex.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.1.27; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(13464002)(377454001)(876001)(53806001)(51856001)(54356001)(80022001)(49866001)(66066001)(65816001)(4396001)(59766001)(20776003)(56776001)(47776003)(5343655001)(46406002)(63696002)(54316002)(79102001)(56816002)(76482001)(77982001)(44976002)(23726001)(74662001)(46102001)(31966008)(16406001)(33646001)(50466001)(74502001)(47446002)(47736001)(50986001)(47976001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CH1SR01MB612; H:hybrid.exchange.microsoft.com; RD:mail7.exchange.microsoft.com; MX:1; A:1; LANG:en; 
X-Forefront-PRVS: 0761DE1EDD
X-OriginatorOrg: DuplicateDomain-7923a859-03c9-4312-a77c-440aa45aaf52.microsoft.com
X-Mailman-Approved-At: Mon, 18 Feb 2013 07:29:14 -0800
Cc: "draft-ietf-idr-as-private-reservation.all@tools.ietf.org" <draft-ietf-idr-as-private-reservation.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-idr-as-private-reservation-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: Mon, 18 Feb 2013 15:27:46 -0000

Elwyn -

Thanks for your review.  The suggestion is being made to IANA who owns the =
assignment and was discussed at length in the working group with rough cons=
ensus.  IANA will replace the suggested values into TBDX values below that =
text if IESG approves.  This text will not be in the RFC, it's to be strick=
en from the final document by RFC Editor (I was attempting to write this te=
xt in alignment with Section 5.1 of RFC 5226) .

On the final ASN in the range, this is in accordance with like reservation =
of the existing 2 byte Private ASN reservations, where the final ASN in tha=
t space is not utilized either (except for well-known community values).  A=
lso, a case was made that code implementations tend to have issues with fin=
al number usage if using incorrect variable types for storage.  That said, =
the small discussion on and off list about this resolved that if we wanted =
to formalize the reservation of the last ASN of both the 2 byte space 65535=
 and the 4 byte space 4294967295, probably a separate draft should be const=
ructed detailing the logic behind these as they have nothing to do with Pri=
vate ASN's per se and have already been marked as Reserved by IANA as you n=
oted.  I'm open to IESG direction if we want to take a different approach o=
n this...

Cheers,

Jon

-----Original Message-----
From: Elwyn Davies [mailto:elwynd@dial.pipex.com]=20
Sent: Friday, February 15, 2013 4:15 AM
To: General Area Review Team
Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org
Subject: Gen-art last call review of draft-ietf-idr-as-private-reservation-=
03

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/GenArtfaq>.

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

Document: draft-ietf-idr-as-private-reservation-03.txt
Reviewer: Elwyn Davies
Review Date: 15 February 2013
IETF LC End Date: 22 February 2013
IESG Telechat date: (if known) -

Summary: Ready for the IESG.

Nits/editorial comments:  The draft is not actually definitive about range =
of values to be allocated - the range in s10 is just a 'suggestion'.  Who i=
s actually making the decision about the range?

Aside: I noted that the highest possible 32 bit number (4294967295 =3D
0xFFFFFFFF) is excluded from the proposed range.  This is marked as reserve=
d in the IANA table but AFAICS this reserved item does not have a specifica=
tion associated with the reservation.  This document would be an opportunit=
y to explicitly mention that the topmost value is reserved (for future expa=
nsion? :-) )



From elwynd@dial.pipex.com  Mon Feb 18 17:12:47 2013
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 381FA21E808E for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 17:12:47 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Lk2c+kP6Vu7 for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 17:12:46 -0800 (PST)
Received: from auth.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 B4B0421E8063 for <gen-art@ietf.org>; Mon, 18 Feb 2013 17:12:37 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1U7bl1-0000YH-80; Tue, 19 Feb 2013 01:12:35 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: "Jon Mitchell (GNS)" <Jon.Mitchell@microsoft.com>
In-Reply-To: <f1195a2f3468441d85edaf0b8b843bba@DFM-DB3MBX15-08.exchange.corp.microsoft.com>
References: <511DFCAD.6020509@dial.pipex.com> <f1195a2f3468441d85edaf0b8b843bba@DFM-DB3MBX15-08.exchange.corp.microsoft.com>
Content-Type: text/plain
Date: Tue, 19 Feb 2013 01:12:05 +0000
Message-Id: <1361236326.4494.891.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: "draft-ietf-idr-as-private-reservation.all@tools.ietf.org" <draft-ietf-idr-as-private-reservation.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-idr-as-private-reservation-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: Tue, 19 Feb 2013 01:12:47 -0000

On Mon, 2013-02-18 at 15:26 +0000, Jon Mitchell (GNS) wrote:
> Elwyn -
> 
> Thanks for your review. 
:-)

>  The suggestion is being made to IANA who owns the assignment and was
> discussed at length in the working group with rough consensus.  
As specified in the registry, allocations in this registry are either by
IETF Concensus (i.e. a suitable RFC such as this draft is intended to
be) or request from a RIR. Thus it isn't a matter of suggesting to IANA
but telling them what the IETF want done - so this draft should be
definitive - and what you said about WG concensus constitutes the values
to be used unless somebody else in the IETF manages to alter the
concensus which seems unlikely.
  
> IANA will replace the suggested values into TBDX values below that
> text if IESG approves.  This text will not be in the RFC, it's to be
> stricken from the final document by RFC Editor (I was attempting to
> write this text in alignment with Section 5.1 of RFC 5226) .
Yes, that's fine and as expected.
> 
> On the final ASN in the range, this is in accordance with like
> reservation of the existing 2 byte Private ASN reservations, where the
> final ASN in that space is not utilized either (except for well-known
> community values).  Also, a case was made that code implementations
> tend to have issues with final number usage if using incorrect
> variable types for storage.  That said, the small discussion on and
> off list about this resolved that if we wanted to formalize the
> reservation of the last ASN of both the 2 byte space 65535 and the 4
> byte space 4294967295, probably a separate draft should be constructed
> detailing the logic behind these as they have nothing to do with
> Private ASN's per se and have already been marked as Reserved by IANA
> as you noted.  I'm open to IESG direction if we want to take a
> different approach on this...
Publishing a separate draft seems a bit overkill but clearly that's not
my decision. ;-)

Regards,
Elwyn
> 
> Cheers,
> 
> Jon
> 
> -----Original Message-----
> From: Elwyn Davies [mailto:elwynd@dial.pipex.com] 
> Sent: Friday, February 15, 2013 4:15 AM
> To: General Area Review Team
> Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org
> Subject: Gen-art last call review of draft-ietf-idr-as-private-reservation-03
> 
> 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-as-private-reservation-03.txt
> Reviewer: Elwyn Davies
> Review Date: 15 February 2013
> IETF LC End Date: 22 February 2013
> IESG Telechat date: (if known) -
> 
> Summary: Ready for the IESG.
> 
> Nits/editorial comments:  The draft is not actually definitive about range of values to be allocated - the range in s10 is just a 'suggestion'.  Who is actually making the decision about the range?
> 
> Aside: I noted that the highest possible 32 bit number (4294967295 =
> 0xFFFFFFFF) is excluded from the proposed range.  This is marked as reserved in the IANA table but AFAICS this reserved item does not have a specification associated with the reservation.  This document would be an opportunity to explicitly mention that the topmost value is reserved (for future expansion? :-) )
> 
> 


From meral.shirazipour@ericsson.com  Mon Feb 18 20:54:39 2013
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 8DCB921E803A for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 20:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level: 
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OWIgP36rL7yo for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 20:54:38 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5325C21E804B for <gen-art@ietf.org>; Mon, 18 Feb 2013 20:54:38 -0800 (PST)
X-AuditID: c618062d-b7fcb6d000007ada-0e-5123058dae6b
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id B6.90.31450.D8503215; Tue, 19 Feb 2013 05:54:37 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0318.004; Mon, 18 Feb 2013 23:54:36 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-radext-radius-extensions.all@tools.ietf.org" <draft-ietf-radext-radius-extensions.all@tools.ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-radext-radius-extensions-12
Thread-Index: Ac4OXP4tP5Ju86bvRMW2I8CUvcL0ww==
Date: Tue, 19 Feb 2013 04:54:35 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A08CCC7@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A08CCC7eusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsUyuXRPrG4vq3KgQXeDgcXJLw3sFldffWZx YPJYsuQnk8eXy5/ZApiiuGxSUnMyy1KL9O0SuDIOPZrMWPBFveLQmrfsDYynlLsYOTkkBEwk Vt//zA5hi0lcuLeerYuRi0NI4AijRN+LflYIZzmjxJsdvWBVbAIWEtt/P2cFsUUEyiVOzDwP ZjMLaEpsanoO1M3BISwQKLGvuwCiJEzi3r3ZjBC2nsSlk9/BylkEVCWeXDzJAmLzCnhL/Hl5 kQ3EZgQ64vupNUwQI8Ulbj2ZzwRxnIDEkj3nmSFsUYmXj/+xQtjKEkue7GeBqM+X2Pi6kxVi pqDEyZlPWCYwCs9CMmoWkrJZSMog4joSC3Z/YoOwtSWWLXzNDGOfOfCYCVl8ASP7KkaO0uLU stx0I4NNjMAoOSbBpruDcc9Ly0OM0hwsSuK8Qa4XAoQE0hNLUrNTUwtSi+KLSnNSiw8xMnFw SjUwqh29qynsMFHQatoUk7DHX2adyzPg+vpJt3Vzw4sHzi3eOn+ynAqnsz5ke8p31yLouXng PsEfR7ftf3nYM3hlz9kVt2bwli1f+viR8WUjE27Fs3Uq8iH3JNi4T/hMX/goKTHuYMeT2Rp2 hoVm7Z2nWSLj70/gMCyzPP70dcQ+xuoLZ8qtxURZlViKMxINtZiLihMBlHyuQGACAAA=
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-radext-radius-extensions-12
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 Feb 2013 04:54:39 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A08CCC7eusaamb107ericsso_
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-AR=
T, please see the FAQ at < http://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq> .

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

Document: draft-ietf-radext-radius-extensions-12
Reviewer: Meral Shirazipour
Review Date: 2013-02-18
IETF LC End Date: 2013-01-25
IESG Telechat date: 2013-02-21

Summary: This draft is ready for publication as Proposed Standard (with som=
e editorial comments).


Nits/editorial comments:
-[Page 15], 3rd paragraph, "withing"--typo-->"within"
-[Page 27], Figure at the bottom is cut.
-[Page 32], Figure at the bottom is cut.
-[Page 37], Section 5.2, "implementors"-typo?-->"implementers"


Best Regards,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<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=3D"EN-CA" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt; .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please wait for direction from your document shepher=
d or AD before posting a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-radext-radius-extensions-12<o:p=
></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-02-18<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-01-25<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2013-02-21<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready for publication as Prop=
osed Standard (with some editorial comments).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 15], 3rd paragraph, &quot;withing&quot;--typo=
--&gt;&quot;within&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 27], Figure at the bottom is cut.<o:p></o:p><=
/p>
<p class=3D"MsoNormal">-[Page 32], Figure at the bottom is cut.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span lang=3D"FR-CA">-[Page 37], Section 5.2, &quot;=
implementors&quot;&#8212;typo?--&gt;&quot;</span>implementers<span lang=3D"=
FR-CA">&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CA"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CA"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A08CCC7eusaamb107ericsso_--

From meral.shirazipour@ericsson.com  Mon Feb 18 21:01:20 2013
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 CE9BC21F8DAE for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 21:01:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level: 
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MjCyA+iPpkqd for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 21:01:20 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id DEC0021F8DB0 for <gen-art@ietf.org>; Mon, 18 Feb 2013 21:01:18 -0800 (PST)
X-AuditID: c6180641-b7f926d000000e79-af-5123071dd08a
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id A0.0E.03705.D1703215; Tue, 19 Feb 2013 06:01:18 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 00:01:17 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "raft-ietf-6man-nd-extension-headers.all@tools.ietf.org" <raft-ietf-6man-nd-extension-headers.all@tools.ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-6man-nd-extension-headers-03
Thread-Index: Ac4OXhvGgklfwbwYR72ZOB6cLkv7SA==
Date: Tue, 19 Feb 2013 05:01:16 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A08CCF9@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A08CCF9eusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsUyuXRPrK4cu3KgwZxbohZXX31mseht/crq wOSxZMlPJo8vlz+zBTBFcdmkpOZklqUW6dslcGWs2XCYseCHUsWse7OZGhjnyHcxcnJICJhI fF1+lRXCFpO4cG89WxcjF4eQwBFGicb/X9khnOWMEh3HprODVLEJWEhs//0crENEoFyi/eMe JhCbWUBTYlPTczYQW1ggSOLupeuMEDXhEjsXzWaHsPUkrq7rAatnEVCVuH34OjOIzSvgLfH/ 3UWwmYxAV3w/tQZqprjErSfzmSCuE5BYsuc8M4QtKvHy8T+oq5UlljzZzwJRny/RfOcUO8RM QYmTM5+wTGAUnoVk1CwkZbOQlEHEdSQW7P7EBmFrSyxb+JoZxj5z4DETsvgCRvZVjBylxall uelGhpsYgXFyTILNcQfjgk+WhxilOViUxHlDXS8ECAmkJ5akZqemFqQWxReV5qQWH2Jk4uCU amDUCFZ4tenw5Oa74o9vbvWUzr3Fu3jJ9MOWRg+bs3Oyijp+RH8+a/O3Z3LS54IuI8amKd4V Ml+Pf7q/bvuEIrfpbzanXCi2nnTw2g4JzQcX3MPadwelR7/JSFo357WSe3rkEseqrUvSbWes XmaQ8/1QTteBE6mlboc/NU1dqno1XuOexox7An9DlFiKMxINtZiLihMB6vPN1WECAAA=
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-6man-nd-extension-headers-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: Tue, 19 Feb 2013 05:01:20 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A08CCF9eusaamb107ericsso_
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-AR=
T, please see the FAQ at < http://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq>.

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

Document: draft-ietf-6man-nd-extension-headers-03
Reviewer: Meral Shirazipour
Review Date: 2013-02-19
IETF LC End Date: 2013-01-29
IESG Telechat date: 2013-02-21

Summary: This draft is ready for publication as Proposed Standard.


Nits/editorial comments:
Please refer to http://www.ietf.org/mail-archive/web/gen-art/current/msg081=
38.html

Best Regards,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<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=3D"EN-CA" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please wait for direction from your document shepher=
d or AD before posting a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-6man-nd-extension-headers-03<o:=
p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-02-19<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-01-29<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2013-02-21<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready for publication as Prop=
osed Standard.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">Please refer to http://www.ietf.org/mail-archive/web=
/gen-art/current/msg08138.html<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A08CCF9eusaamb107ericsso_--

From meral.shirazipour@ericsson.com  Mon Feb 18 21:03:15 2013
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 578C921F8DC3 for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 21:03:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.765
X-Spam-Level: 
X-Spam-Status: No, score=-2.765 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yxLPzRQuXCE1 for <gen-art@ietfa.amsl.com>; Mon, 18 Feb 2013 21:03:14 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id DC8F021F8DB9 for <gen-art@ietf.org>; Mon, 18 Feb 2013 21:03:13 -0800 (PST)
X-AuditID: c618062d-b7fcb6d000007ada-6b-51230791c8fe
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id AD.A0.31450.19703215; Tue, 19 Feb 2013 06:03:13 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 00:03:12 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-6man-nd-extension-headers.all@tools.ietf.org" <draft-ietf-6man-nd-extension-headers.all@tools.ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-6man-nd-extension-headers-03
Thread-Index: Ac4OXmniJdYTuQuoRV6naNLovHceYg==
Date: Tue, 19 Feb 2013 05:03:11 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A08CD2B@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A08CD2Beusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsUyuXSPt+5EduVAg8OL1C3OH+lgtbj66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJXx/MM3toLLqhWd+2ezNTDeUOxi5OSQEDCR +Pm3mQnCFpO4cG89WxcjF4eQwBFGiWsf+1kgnOWMErff/2UEqWITsJDY/vs5K4gtIlApsWL2 WjYQm1lAU2JT03MwW1ggSOLupeuMEDXhEjsXzWaHsPUktp5bChZnEVCV2L/6EzOIzSvgLfF1 3iywGkagK76fWsMEMVNc4taT+VDXCUgs2XOeGcIWlXj5+B8rhK0sseTJfhaI+nyJp8vfMkLM FJQ4OfMJywRG4VlIRs1CUjYLSRlEXEdiwe5PbBC2tsSyha+ZYewzBx4zIYsvYGRfxchRWpxa lptuZLCJERgnxyTYdHcw7nlpeYhRmoNFSZw3yPVCgJBAemJJanZqakFqUXxRaU5q8SFGJg5O qQbG5dPZks6dPpMto9njyNLF1ZW4sV3125ykDdldp8R8th3avIbvWL7+/ym7f0uxzjjylE0r q0J29dz0qVMK1iz/OTXCVblL06v6/J/ImUn1rOtTpzdPrdx+JebcDt7ZBv8EH3xUmpK+jcOg 4yh7+xEevyW+Eg+Ng8R4/dN97bboRBT1clmEmUkosRRnJBpqMRcVJwIAziFx7WECAAA=
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-6man-nd-extension-headers-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: Tue, 19 Feb 2013 05:03:15 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A08CD2Beusaamb107ericsso_
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-AR=
T, please see the FAQ at < http://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq>.

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

Document: draft-ietf-6man-nd-extension-headers-03
Reviewer: Meral Shirazipour
Review Date: 2013-02-19
IETF LC End Date: 2013-01-29
IESG Telechat date: 2013-02-21

Summary: This draft is ready for publication as Proposed Standard.


Nits/editorial comments:
Please refer to http://www.ietf.org/mail-archive/web/gen-art/current/msg081=
38.html

Best Regards,
Meral

---
Meral Shirazipour
Ericsson
Research
www.ericsson.com<http://www.ericsson.com>


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{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: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=3D"EN-CA" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please wait for direction from your document shepher=
d or AD before posting a new version of the draft.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-6man-nd-extension-headers-03<o:=
p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-02-19<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-01-29<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2013-02-21<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready for publication as Prop=
osed Standard.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">Please refer to <a href=3D"http://www.ietf.org/mail-=
archive/web/gen-art/current/msg08138.html">
http://www.ietf.org/mail-archive/web/gen-art/current/msg08138.html</a><o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://www.ericsson.com">www.ericsson.com=
</a><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A08CD2Beusaamb107ericsso_--

From christer.holmberg@ericsson.com  Tue Feb 19 01:34:47 2013
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 8ED4D21F8B0B for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 01:34:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.292
X-Spam-Level: 
X-Spam-Status: No, score=-6.292 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U+ZNIXAlDhLr for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 01:34:47 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8938621F8B2B for <gen-art@ietf.org>; Tue, 19 Feb 2013 01:34:46 -0800 (PST)
X-AuditID: c1b4fb30-b7f0d6d000007e61-b4-51234735e780
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id F7.D8.32353.53743215; Tue, 19 Feb 2013 10:34:45 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.82]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 10:34:45 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-shafranovich-mime-sql-03
Thread-Index: Ac4DOuPMXiNkMSIJTBOr80jWpqiZTgLSVUtA
Date: Tue, 19 Feb 2013 09:34:43 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B0F788D@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B0D3B85@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B0D3B85@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+Jvja6pu3KgwZJryhZzFnpbXH31mcWB yWPJkp9MHl8uf2YLYIrisklJzcksSy3St0vgyrh5KLJgInfF0i0BDYx3OboYOTkkBEwkPv/a zARhi0lcuLeerYuRi0NI4BCjxOF5vewQzmJGiZ55cxm7GDk42AQsJLr/aYM0iAhoSsxd8Ras mVkgXeLe8QOsILawgI3ErTUT2CBqbCXmzrrGDGEbSRzZeB+snkVAVaJ5xn4WEJtXwFuiu+kr WL0QkH1r4W8wm1PAR+Jg1xVGEJsR6Ljvp9ZA7RKXuPVkPtTRAhJL9pxnhrBFJV4+/scKYStK XJ2+HKpeR2LB7k9sELa2xLKFr5kh9gpKnJz5hGUCo9gsJGNnIWmZhaRlFpKWBYwsqxjZcxMz c9LLzTcxAqPj4JbfBjsYN90XO8QozcGiJM4b7nohQEggPbEkNTs1tSC1KL6oNCe1+BAjEwen VANjdNtegw9s/bqfp6nJ8zaXcc26d6C1x1xHsaQ9TGxFb4Efi7Nm+ZIjs759tn/U0752b8qx adyTdtpGrtoSyPGM9+WTunArYWnpHXvWMoZUNGil2CjX34vl7b3856N74n3NpWbmPzZxbP+n nrF48TEHw+1nvpVItial5q//lXB14vb7b3riT1gosRRnJBpqMRcVJwIAI53kSVwCAAA=
Cc: "draft-shafranovich-mime-sql.all@tools.ietf.org" <draft-shafranovich-mime-sql.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-shafranovich-mime-sql-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: Tue, 19 Feb 2013 09:34:47 -0000

Hi,

I have reviewed the -04 version. My comments on -03 have been addressed, an=
d the document is ready for publication.

Regards,

Christer

-----Original Message-----
From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On Behalf =
Of Christer Holmberg
Sent: 5. helmikuuta 2013 2:55
To: gen-art@ietf.org
Cc: draft-shafranovich-mime-sql.all@tools.ietf.org
Subject: [Gen-art] Genart review of draft-shafranovich-mime-sql-03

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>

Document:                    draft-shafranovich-mime-sql-03.txt

Reviewer:                     Christer Holmberg

Review Date:                 5 Feb 2013

IETF LC End Date:        20 Feb 2013

IETF Telechat Date:       21 Feb 2013

Summary:  The draft is well written, with a couple of minor editorial comme=
nts (see below), and is ready for publication.
=20
Major Issues: None
=20
Minor Issues: None

Editorial nits: None

Q_ED_1: In section 2, I suggest to remove "which will be submitted to IANA =
after approval of this document.".

Q_ED_2: In section 3, I suggest to remove "After approval,".=20

Best regards,

Christer

=20
=20
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art

From christer.holmberg@ericsson.com  Tue Feb 19 02:09:49 2013
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 9914321F8930 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 02:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.29
X-Spam-Level: 
X-Spam-Status: No, score=-6.29 tagged_above=-999 required=5 tests=[AWL=-0.042,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bWNy3V9AH9dE for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 02:09:48 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id BEABD21F88EA for <gen-art@ietf.org>; Tue, 19 Feb 2013 02:09:47 -0800 (PST)
X-AuditID: c1b4fb25-b7f366d000004d10-99-51234f6a4528
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 1E.88.19728.A6F43215; Tue, 19 Feb 2013 11:09:46 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.82]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 11:09:46 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-templin-intarea-seal-51.txt
Thread-Index: Ac4OiTSa1jkabDjkRUqWja4TC497FQ==
Date: Tue, 19 Feb 2013 10:09:45 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B0F78E8@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B0F78E8ESESSMB209ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDLMWRmVeSWpSXmKPExsUyM+JvjW6Wv3KgwfNOPYsH62awWVx99ZnF gcljyZKfTB5fLn9mC2CK4rJJSc3JLEst0rdL4MrYtrqFraDdouLM91XsDYzrDboYOTkkBEwk tlw+wQhhi0lcuLeerYuRi0NI4BCjxJofT5khnMWMEpsWXgPKcHCwCVhIdP/TBmkQEdCUmLvi LROIzSyQKvFi+i1WEFtYwFri07I7zBA1DhJfLk5mgbD1JBavgqhhEVCV2LqwBczmFfCW2Dbt FRuIzQh0xPdTa6BmikvcejKfCeI4AYkle84zQ9iiEi8f/2OFsBUlrk5fDlWfL/H65TEmiJmC EidnPmGZwCg8C8moWUjKZiEpg4jrSCzY/YkNwtaWWLbwNTOMfebAYyZk8QWM7KsY2XMTM3PS y402MQJj5OCW36o7GO+cEznEKM3BoiTOG+56IUBIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD 47yTt86f7dT3KOM/w8xwMl6vK+Dhl1uMvRfOOopOSd/kmZv/I21hrGJ2S8O7/nSZCa5Pj3/b karLycqcWiFXMGNykfGOSSdNns9Sk9j2oSe+uGgDd9bCKO97JsW1i7aWWUx43XXcZs2aJ4kL X2dsvcgXHhxn7x1xX9Pkie6D+7w9i2QXLr87TYmlOCPRUIu5qDgRANOvqgtfAgAA
Cc: "draft-templin-intarea-seal-all@tools.ietf.org" <draft-templin-intarea-seal-all@tools.ietf.org>
Subject: [Gen-art] Genart review of draft-templin-intarea-seal-51.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 Feb 2013 10:09:49 -0000

--_000_7594FB04B1934943A5C02806D1A2204B0F78E8ESESSMB209ericsso_
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-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>



Document:                    draft-templin-intarea-seal-51.txt



Reviewer:                     Christer Holmberg



Review Date:                 19 Feb 2013



IETF LC End Date:        20 Feb 2013



IETF Telechat Date:       21 Feb 2013



Summary:  The draft is well written, but with some editorial comments that =
I suggest to be addressed before publication.

Major Issues: None

Minor Issues: None



Editorial nits: See below



Q_ED_1: Most of the text in the Abstract section does not belong there. The=
 section should talk about what the document does, and not define what a su=
bnetwork is etc. Only the last sentence talks about what the draft is about=
.



Q_ED_2: In the Introduction section, I would suggest to add a reference for=
 IP encapsulating/tunneling. RFC 2003 is referenced later in the document, =
but I think it would be good to have something also in the Introduction.



Q_ED_3: In section 1.2, do you need to define 'subnetwork' here? Isn't it b=
etter to have the definition in one single place - the Terminology section?



Q_ED_4: In section 12, there seems to be a dot too much :)



Best regards,



Christer




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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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";}
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";}
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;}
@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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">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://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq</a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-templin-intarea-seal-51.txt<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Reviewer:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Christer Holmberg<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Review Date:&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;19 Feb 2013<o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; 20 Feb 2013<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IETF Telechat Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; 21 Feb 2013<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary:&nbsp; The draft is well written, but wit=
h some editorial comments that I suggest to be addressed before publication=
.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p></o:p></p>
<p class=3D"MsoPlainText">Major Issues: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p></o:p></p>
<p class=3D"MsoPlainText">Minor Issues: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Editorial nits: See below<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q_ED_1: Most of the text in the Abstract section =
does not belong there. The section should talk about what the document does=
, and not define what a subnetwork is etc. Only the last sentence talks abo=
ut what the draft is about.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q_ED_2: In the Introduction section, I would sugg=
est to add a reference for IP encapsulating/tunneling. RFC 2003 is referenc=
ed later in the document, but I think it would be good to have something al=
so in the Introduction.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q_ED_3: In section 1.2, do you need to define &#8=
216;subnetwork&#8217; here? Isn&#8217;t it better to have the definition in=
 one single place &#8211; the Terminology section?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q_ED_4: In section 12, there seems to be a dot to=
o much <span style=3D"font-family:Wingdings">
J</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Best regards,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Christer<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B0F78E8ESESSMB209ericsso_--

From christer.holmberg@ericsson.com  Tue Feb 19 02:12:14 2013
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 8279421F88EA for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 02:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.288
X-Spam-Level: 
X-Spam-Status: No, score=-6.288 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t-QshNUw77TA for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 02:12:13 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 77B5721F8904 for <gen-art@ietf.org>; Tue, 19 Feb 2013 02:12:11 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-55-51234ffa4a12
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 2A.2F.10459.AFF43215; Tue, 19 Feb 2013 11:12:10 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.82]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 11:11:11 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-templin-intarea-seal-51.txt
Thread-Index: Ac4OiTSa1jkabDjkRUqWja4TC497FQAAB/tA
Date: Tue, 19 Feb 2013 10:11:11 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B0F890C@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B0F78E8@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B0F78E8@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B0F890CESESSMB209ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyM+Jvje4vf+VAg9unVC22/b7EaHH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvj0YdexoKNzhXfJ91kbWDca9XFyMkhIWAi cfzdOjYIW0ziwr31QDYXh5DAIUaJxpMfmUESQgKLGSWalzB2MXJwsAlYSHT/0wYJiwhoSsxd 8ZYJxGYWSJVofnCDBcQWFrCXePL1ISNEjYPEl4uTWSBsI4k5v7eA2SwCqhKb/l8AG88r4C1x tXE3G8Qqb4kbr8+DzeQU8JE4sPQNWA0j0G3fT62B2iUucevJfCaImwUkluw5zwxhi0q8fPyP FcJWlLg6fTlUfb7ElwNrWSB2CUqcnPmEZQKj6Cwko2YhKZuFpAwiriOxYPcnNghbW2LZwtfM MPaZA4+ZkMUXMLKvYmTPTczMSS833MQIjKiDW37r7mA8dU7kEKM0B4uSOG+Y64UAIYH0xJLU 7NTUgtSi+KLSnNTiQ4xMHJxSDYx5uy/+2v7a84NM/dd3KSqNas9/3Ytuzms8v9hDh/HpxHmW 9/aqXNu28jX7FwudH7MK12/ZvPhOwLR7jkYLDm0IqtLKyb0kGRbotOLO3WmpF5buWVoQGfcl 9tYtobX/JYpe3J4QP8Npfu7u621uvS5r5v/6GHVFN6qiTe+hq6Qa+0Kpm1cSMpqWK7EUZyQa ajEXFScCANYbuKd2AgAA
Cc: "draft-templin-intarea-seal.all@tools.ietf.org" <draft-templin-intarea-seal.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-templin-intarea-seal-51.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 Feb 2013 10:12:14 -0000

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

E-mail address corrected.

From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On Behalf =
Of Christer Holmberg
Sent: 19. helmikuuta 2013 12:10
To: gen-art@ietf.org
Cc: draft-templin-intarea-seal-all@tools.ietf.org
Subject: [Gen-art] Genart review of draft-templin-intarea-seal-51.txt


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>



Document:                    draft-templin-intarea-seal-51.txt



Reviewer:                     Christer Holmberg



Review Date:                 19 Feb 2013



IETF LC End Date:        20 Feb 2013



IETF Telechat Date:       21 Feb 2013



Summary:  The draft is well written, but with some editorial comments that =
I suggest to be addressed before publication.



Major Issues: None



Minor Issues: None



Editorial nits: See below



Q_ED_1: Most of the text in the Abstract section does not belong there. The=
 section should talk about what the document does, and not define what a su=
bnetwork is etc. Only the last sentence talks about what the draft is about=
.



Q_ED_2: In the Introduction section, I would suggest to add a reference for=
 IP encapsulating/tunneling. RFC 2003 is referenced later in the document, =
but I think it would be good to have something also in the Introduction.



Q_ED_3: In section 1.2, do you need to define 'subnetwork' here? Isn't it b=
etter to have the definition in one single place - the Terminology section?



Q_ED_4: In section 12, there seems to be a dot too much :)



Best regards,



Christer






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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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: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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
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: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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">E-mail address correct=
ed.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> gen-art-=
bounces@ietf.org [mailto:gen-art-bounces@ietf.org]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> 19. helmikuuta 2013 12:10<br>
<b>To:</b> gen-art@ietf.org<br>
<b>Cc:</b> draft-templin-intarea-seal-all@tools.ietf.org<br>
<b>Subject:</b> [Gen-art] Genart review of draft-templin-intarea-seal-51.tx=
t<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">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://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq</a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-templin-intarea-seal-51.txt<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Reviewer:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Christer Holmberg<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Review Date:&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;19 Feb 2013<o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; 20 Feb 2013<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IETF Telechat Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; 21 Feb 2013<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary:&nbsp; The draft is well written, but wit=
h some editorial comments that I suggest to be addressed before publication=
.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major Issues: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor Issues: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Editorial nits: See below<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q_ED_1: Most of the text in the Abstract section =
does not belong there. The section should talk about what the document does=
, and not define what a subnetwork is etc. Only the last sentence talks abo=
ut what the draft is about.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q_ED_2: In the Introduction section, I would sugg=
est to add a reference for IP encapsulating/tunneling. RFC 2003 is referenc=
ed later in the document, but I think it would be good to have something al=
so in the Introduction.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q_ED_3: In section 1.2, do you need to define &#8=
216;subnetwork&#8217; here? Isn&#8217;t it better to have the definition in=
 one single place &#8211; the Terminology section?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q_ED_4: In section 12, there seems to be a dot to=
o much <span style=3D"font-family:Wingdings">
J</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Best regards,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Christer<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B0F890CESESSMB209ericsso_--

From yakov@shaftek.org  Tue Feb 19 04:18:48 2013
Return-Path: <yakov@shaftek.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 D982F21F8BB6 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 04:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level: 
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SOmSFkbwPo4D for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 04:18:48 -0800 (PST)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2DCB421F8BA1 for <gen-art@ietf.org>; Tue, 19 Feb 2013 04:18:48 -0800 (PST)
Received: by mail-ie0-f169.google.com with SMTP id 13so8454688iea.28 for <gen-art@ietf.org>; Tue, 19 Feb 2013 04:18:47 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=3Ns+jlJLwBr9ezSjU2Vnr/v/9gbFSkf119CXbfjgG3o=; b=c2xW2Qt8jZPQwajwhGchoGDSXLGp2MskvAuSUpydZIkS2Jw9tH9/OfDf9ZdP2qsL3K R1jic6CXlBh8YezIXIsYxKGbVhDEPAGWxqbPNk6FD4/QPtkl4WE2ulUDaXtBgsKJcZpo GIoysnBSgpORP5Ou0ONOho4Lzn9/bP6icqiro/HFYN97GZRiwKlgu2vc/Ub1H9EH2GLI jA77UHwofuYlMLbE2+2UF5MTcMHsBmkiTRXvDCM+VEV0kPnLlhZyoyvJIatbxr+Cstcu dS7U3771Yr4PHpzZX1JUY3rdfMKk+qLyYaAh60/sq10Kg0JdkAgnv6L2d6kGzQ3cCnRa IVTA==
MIME-Version: 1.0
X-Received: by 10.50.184.132 with SMTP id eu4mr5794580igc.19.1361276327637; Tue, 19 Feb 2013 04:18:47 -0800 (PST)
Received: by 10.64.99.232 with HTTP; Tue, 19 Feb 2013 04:18:47 -0800 (PST)
X-Originating-IP: [98.140.248.199]
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B0F788D@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B0D3B85@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B0F788D@ESESSMB209.ericsson.se>
Date: Tue, 19 Feb 2013 07:18:47 -0500
Message-ID: <CAPQd5oTvgLC+T=a8C8z3ewFKz9suODJ1KgFfuCjcFGTFG_LOKA@mail.gmail.com>
From: Yakov Shafranovich <yakov@shaftek.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=14dae9340ebdf331aa04d612d78e
X-Gm-Message-State: ALoCoQl3F3SwLuz3fQPIJsMWkiCuLvubv9ILO2UosXZbqXPoMEEF9p25XA/9FUy7A5m7CHPGNYTH
X-Mailman-Approved-At: Tue, 19 Feb 2013 05:07:35 -0800
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-shafranovich-mime-sql.all@tools.ietf.org" <draft-shafranovich-mime-sql.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-shafranovich-mime-sql-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: Tue, 19 Feb 2013 12:18:49 -0000

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

Thanks

On Tuesday, February 19, 2013, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:
> Hi,
>
> I have reviewed the -04 version. My comments on -03 have been addressed,
and the document is ready for publication.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On
Behalf Of Christer Holmberg
> Sent: 5. helmikuuta 2013 2:55
> To: gen-art@ietf.org
> Cc: draft-shafranovich-mime-sql.all@tools.ietf.org
> Subject: [Gen-art] Genart review of draft-shafranovich-mime-sql-03
>
> 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-shafranovich-mime-sql-03.txt
>
> Reviewer:                     Christer Holmberg
>
> Review Date:                 5 Feb 2013
>
> IETF LC End Date:        20 Feb 2013
>
> IETF Telechat Date:       21 Feb 2013
>
> Summary:  The draft is well written, with a couple of minor editorial
comments (see below), and is ready for publication.
>
> Major Issues: None
>
> Minor Issues: None
>
> Editorial nits: None
>
> Q_ED_1: In section 2, I suggest to remove "which will be submitted to
IANA after approval of this document.".
>
> Q_ED_2: In section 3, I suggest to remove "After approval,".
>
> Best regards,
>
> Christer
>
>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
>

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

Thanks<br><br>On Tuesday, February 19, 2013, Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com</=
a>&gt; wrote:<br>&gt; Hi,<br>&gt;<br>&gt; I have reviewed the -04 version. =
My comments on -03 have been addressed, and the document is ready for publi=
cation.<br>
&gt;<br>&gt; Regards,<br>&gt;<br>&gt; Christer<br>&gt;<br>&gt; -----Origina=
l Message-----<br>&gt; From: <a href=3D"mailto:gen-art-bounces@ietf.org">ge=
n-art-bounces@ietf.org</a> [mailto:<a href=3D"mailto:gen-art-bounces@ietf.o=
rg">gen-art-bounces@ietf.org</a>] On Behalf Of Christer Holmberg<br>
&gt; Sent: 5. helmikuuta 2013 2:55<br>&gt; To: <a href=3D"mailto:gen-art@ie=
tf.org">gen-art@ietf.org</a><br>&gt; Cc: <a href=3D"mailto:draft-shafranovi=
ch-mime-sql.all@tools.ietf.org">draft-shafranovich-mime-sql.all@tools.ietf.=
org</a><br>
&gt; Subject: [Gen-art] Genart review of draft-shafranovich-mime-sql-03<br>=
&gt;<br>&gt; I am the assigned Gen-ART reviewer for this draft. For backgro=
und on Gen-ART, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf=
.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac=
/wiki/GenArtfaq</a>&gt;<br>
&gt;<br>&gt; Document: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0draft-shafran=
ovich-mime-sql-03.txt<br>&gt;<br>&gt; Reviewer: =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 Christer Holmberg<br>&gt;<br>&gt; Review Date: =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 5 Feb 2013<br>&gt;<br>&gt; IETF LC End Date: =A0 =A0 =A0 =
=A020 Feb 2013<br>
&gt;<br>&gt; IETF Telechat Date: =A0 =A0 =A0 21 Feb 2013<br>&gt;<br>&gt; Su=
mmary: =A0The draft is well written, with a couple of minor editorial comme=
nts (see below), and is ready for publication.<br>&gt;<br>&gt; Major Issues=
: None<br>
&gt;<br>&gt; Minor Issues: None<br>&gt;<br>&gt; Editorial nits: None<br>&gt=
;<br>&gt; Q_ED_1: In section 2, I suggest to remove &quot;which will be sub=
mitted to IANA after approval of this document.&quot;.<br>&gt;<br>&gt; Q_ED=
_2: In section 3, I suggest to remove &quot;After approval,&quot;.<br>
&gt;<br>&gt; Best regards,<br>&gt;<br>&gt; Christer<br>&gt;<br>&gt;<br>&gt;=
<br>&gt; _______________________________________________<br>&gt; Gen-art ma=
iling list<br>&gt; <a href=3D"mailto:Gen-art@ietf.org">Gen-art@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/gen-art">https://www.=
ietf.org/mailman/listinfo/gen-art</a><br>&gt;

--14dae9340ebdf331aa04d612d78e--

From dromasca@avaya.com  Tue Feb 19 06:18:33 2013
Return-Path: <dromasca@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 577C921F8D9C for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 06:18:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.43
X-Spam-Level: 
X-Spam-Status: No, score=-103.43 tagged_above=-999 required=5 tests=[AWL=0.169, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WMgC3jiEWTXv for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 06:18:31 -0800 (PST)
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 55A4C21F8D02 for <gen-art@ietf.org>; Tue, 19 Feb 2013 06:18:31 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAP0QA1GHCzI1/2dsb2JhbABFgmu7ZxZzgiABAQMSKD8SARUHDhRCJgEEDg0ah20BC6FYjGqQCo0Vg0lhA5cphHGKO4J3giQ
X-IronPort-AV: E=Sophos;i="4.84,541,1355115600"; d="scan'208";a="344243690"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 19 Feb 2013 09:20:54 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 19 Feb 2013 09:17:34 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Tue, 19 Feb 2013 09:18:52 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review for draft-cardenas-dff-09
Thread-Index: Ac4OrAr/1G/r/YAuSwWVKubLcvcOqA==
Date: Tue, 19 Feb 2013 14:18:52 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA08ED95@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "scespedes@icesi.edu.co" <scespedes@icesi.edu.co>, "m.dow@freescale.com" <m.dow@freescale.com>, "alvaro.cardenas-mora@us.fujitsu.com" <alvaro.cardenas-mora@us.fujitsu.com>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>, "smartnetpro-iwao_std@ml.css.fujitsu.com" <smartnetpro-iwao_std@ml.css.fujitsu.com>, "ulrich.herberg@us.fujitsu.com" <ulrich.herberg@us.fujitsu.com>
Subject: [Gen-art] Gen-ART review for draft-cardenas-dff-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, 19 Feb 2013 14:18:34 -0000

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/GenArtfaq>.

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

Document: draft-cardenas-dff-09
Reviewer: Dan Romascanu
Review Date: 2/19/2013
IETF LC End Date: 2/24/2013
IESG Telechat date: 2/28/2013

Summary: I have several questions and comments related to this document. So=
me of them may be the result of my lack of familiarity with this technology=
, some other may require clarifications or modifications in the document. U=
ntil the issues and questions noted below are addressed I cannot assess if =
this document is ready.=20

Major issues:

1. Section 1 includes a note that 'this specification is intended for exper=
imentation'. When such statements are made I believe the authors should inc=
lude also some information about what kind of information they expect to re=
ceive from the experiments, where (in what types and sizes of networks) the=
 experiments should be conducted, what are the criteria to consider the exp=
eriments successful.

2. In "mesh-under" mode both EUI-64 link layer addresses and 16-bit short a=
ddresses can be used. First question - can these be mixed in the same DFF d=
omain? Second - the 16-bit short addresses are unique only within the same =
PAN. This means that a DFF domain cannot spin over more than one PAN. Am I =
correct or do I miss something? These should be articulated in the Applicab=
ility statement.=20

3. Are the protocol parameters defined in Section 8 configurable? Do they n=
eed to be kept in non-volatile memory to survive a power failure event? - t=
here is no mention about this in the document.=20

4. Same question for the list of bidirectional neighbors - should they be s=
tored in non-volatile memory, or are they completely rebuilt at (re)-boot? =
=20

5. Same question for the information sets used by DFF described in Section =
6 - should they be stored in non-volatile memory, or are they completely re=
built at (re)-boot?=20

6. In section 9.2 - what happened if when adding a new Processed Tuple base=
d on a new incoming packet the routing discovers that the P_seq_number is a=
lready in used for another entry in the list. This can happen, as the seque=
nce numbers are unique per routers, and current packets may originate from =
different routers? Is this not a problem? Why?=20

7. Section 14 - header formats - don't we need a version field? If not, why=
?=20

8. Security Considerations section 16.3.2 - should not Sequence Number Tamp=
ering be added to the Packet Header Modifications attacks?=20

Minor issues:

1. The applicability statement says that the protocol ' Assumes that the un=
derlying link layer provides means to detect if a Packet has been successfu=
lly delivered to the Next Hop or not', ' Is designed for networks with litt=
le traffic in terms of numbers of Packets per second', and 'Is used for uni=
cast transmissions only'. These are limitations important enough to be ment=
ioned in the Abstract and Introduction section.=20

2. Section 15 - am I right that DFF domains running in "route-over" MoP and=
 "mesh-under" MoP never mix, so if they happen to be overlaying or adjoinin=
g one near the other they should be considered as distinct domains? If this=
 is correct, I suggest to be explicit about this.=20


Nits/editorial comments:

1. In Sections 2.1 and 2.2 the delimitors between the terms and their expla=
nations are inconsistent (colons for some, dashes for other)



From aland@deployingradius.com  Tue Feb 19 06:46:24 2013
Return-Path: <aland@deployingradius.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 95B3021F8832 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 06:46:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ckuyeNydyxq for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 06:46:24 -0800 (PST)
Received: from power.freeradius.org (power.freeradius.org [88.190.25.44]) by ietfa.amsl.com (Postfix) with ESMTP id 12E3921F8798 for <gen-art@ietf.org>; Tue, 19 Feb 2013 06:46:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id D72B62241133; Tue, 19 Feb 2013 15:45:40 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wDMl8nKDShH; Tue, 19 Feb 2013 15:45:40 +0100 (CET)
Received: from Thor-2.local (bas1-ottawa11-1177737285.dsl.bell.ca [70.50.216.69]) by power.freeradius.org (Postfix) with ESMTPSA id 45FA12240780; Tue, 19 Feb 2013 15:45:40 +0100 (CET)
Message-ID: <51239013.5060401@deployingradius.com>
Date: Tue, 19 Feb 2013 09:45:39 -0500
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A08CCC7@eusaamb107.ericsson.se>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A08CCC7@eusaamb107.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-radext-radius-extensions.all@tools.ietf.org" <draft-ietf-radext-radius-extensions.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Call review of draft-ietf-radext-radius-extensions-12
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 Feb 2013 14:46:24 -0000

Meral Shirazipour wrote:
> Summary: This draft is ready for publication as Proposed Standard (with
> some editorial comments).

  Thanks.  I'll fix the changes in the next revision of the document.

  Alan DeKok.

From meral.shirazipour@ericsson.com  Tue Feb 19 06:46:34 2013
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 3555621F8947 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 06:46:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.741
X-Spam-Level: 
X-Spam-Status: No, score=-2.741 tagged_above=-999 required=5 tests=[AWL=-0.142, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vKI5avwIP3PN for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 06:46:33 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7392821F8904 for <gen-art@ietf.org>; Tue, 19 Feb 2013 06:46:33 -0800 (PST)
X-AuditID: c618062d-b7fcb6d000007ada-20-51239048d06b
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id FE.3B.31450.84093215; Tue, 19 Feb 2013 15:46:32 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 09:46:32 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Alan DeKok <aland@deployingradius.com>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-radext-radius-extensions-12
Thread-Index: Ac4OXP4tP5Ju86bvRMW2I8CUvcL0wwAfLNiAAAp1SBA=
Importance: low
X-Priority: 5
Date: Tue, 19 Feb 2013 14:46:31 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A08E19F@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A08CCC7@eusaamb107.ericsson.se> <51239013.5060401@deployingradius.com>
In-Reply-To: <51239013.5060401@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyuXRPoK7nBOVAg4N8Fk2fm9gtTn5pYLe4 +uoziwOzR8vRFhaPJUt+Mnl8ufyZLYA5issmJTUnsyy1SN8ugSujd0snW8FBlopzDStYGhjv MXcxcnJICJhIbLy9mh3CFpO4cG89WxcjF4eQwBFGibsvVrNAOMsZJZbd2Q9WxSZgIbH993NW EFtEQEtiwfpFYEXMAgsYJU4+v8IGkhAWCJU4s+QbI0RRmMS9e7OhbCuJ+/dvsoDYnAL8Ei/u nGWDWM0r0bukDWgoBweLgKrEzOtSIGFeAW+J1tfnwMqFBEoklp44xATRaizR0rUFzGYEuvr7 qTVgNrOAuMStJ/OZIEYKSCzZcx7qS1GJl4//sULYyhLf5zxigajXkViw+xMbhK0tsWzha2aI vYISJ2c+YZnAKDELydhZSFpmIWmZhaRlASPLKkaO0uLUstx0I4NNjMBIOybBpruDcc9Ly0OM 0hwsSuK8Qa4XAoQE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwOpqcYWgVXSB9Zr7d5nOsF0zF DHq1vVgn7THbukyzYMPm9jN26cEHds4/KXZ4qWMLZ9LhTc+mCp/XuMbDG7xXqPSe/3Tfq2/t lWQ3TCl0Nqmfp3hu4eNHnsW6txNOLalw1LNZLJ5oGHUwWa1CO+5z7L1QflH3JP+rBXM+PIiX uq3Twz4zWd1ciaU4I9FQi7moOBEAkfr+WYICAAA=
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-radext-radius-extensions.all@tools.ietf.org" <draft-ietf-radext-radius-extensions.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Call review of draft-ietf-radext-radius-extensions-12
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 Feb 2013 14:46:34 -0000

Hi,
  Thanks you.

Best Regards,
Meral

-----Original Message-----
From: Alan DeKok [mailto:aland@deployingradius.com]=20
Sent: February-19-13 9:46 AM
To: Meral Shirazipour
Cc: draft-ietf-radext-radius-extensions.all@tools.ietf.org; gen-art@ietf.or=
g
Subject: Re: Gen-ART Telechat Call review of draft-ietf-radext-radius-exten=
sions-12

Meral Shirazipour wrote:
> Summary: This draft is ready for publication as Proposed Standard=20
> (with some editorial comments).

  Thanks.  I'll fix the changes in the next revision of the document.

  Alan DeKok.

From fltemplin@yahoo.com  Tue Feb 19 10:47:12 2013
Return-Path: <fltemplin@yahoo.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 59B7A1F0C4E for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 10:47:12 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V+zf0+t+Llwd for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 10:47:11 -0800 (PST)
Received: from nm19.bullet.mail.bf1.yahoo.com (nm19.bullet.mail.bf1.yahoo.com [98.139.212.178]) by ietfa.amsl.com (Postfix) with SMTP id 700B621F8E65 for <gen-art@ietf.org>; Tue, 19 Feb 2013 10:47:11 -0800 (PST)
Received: from [98.139.212.150] by nm19.bullet.mail.bf1.yahoo.com with NNFMP; 19 Feb 2013 18:47:10 -0000
Received: from [98.139.212.205] by tm7.bullet.mail.bf1.yahoo.com with NNFMP; 19 Feb 2013 18:47:10 -0000
Received: from [127.0.0.1] by omp1014.mail.bf1.yahoo.com with NNFMP; 19 Feb 2013 18:47:10 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 774888.49607.bm@omp1014.mail.bf1.yahoo.com
Received: (qmail 94662 invoked by uid 60001); 19 Feb 2013 18:47:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1361299630; bh=+39kjYh8emxnqqtcrgNQ1aEt0XrGzpioKwa/hUnoSRg=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=c2i+Myr9dQZxiF1XWpuXlGp1eceNUf/Xzp3qpj3rFNwR98wTuc6YNAklRR6U9GUWsLNw2bThaR1lmdD8snJFwAjQg7MDb0z69mk+pz13gZD4pvwYrr9r22t/ZQ3jCK11JSchjngbPTksq+5G7mW45kzBCSa24xDX45xvBFhqvWU=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=y5wudMTkzsuARnmraWTln8E80sW+LatHloBvRs9AA+Hf5Npg6j2lNw9KKVGOBrzbCaP4+SEICIXiJojbe4zpoVBlJnxzDEQu3CBZCwxpjQ0R5847fjZFjcEPa56itRbMFnp0ftIrYo9lxwlbNgSlzBy4LPDplKm9qh8AvtXRnhc=;
X-YMail-OSG: KT4TxQ0VM1kZAlgwaVOFuzTfp2mhXqFefhvD2ywdBFGpg8h fDKy71qirJbQu7U6DuJV4M08ef6g2QjwWZ4lZQJ5XQ0XkBusjeNIcs4vlQ2g 6UAsNCDpcoir4snvDdNmuDwaA7QSzibUZFtyymCp3JrqnHHwYDKauR4zOo5F 4aC9xPODmEWyLuZU1o8brq6IRXmOfzsZjxrXSJ9Aqa2CIrMCvdF6.HPTXtX5 oQqX77DYJBCPOGehP9UzZb.F9Ttg_WbhNlN8irilz_YgdWfUKISZIftU.Xox HyLVxZSX9wDxtM3GPbhqeibHCA8eTk7Z6Vuucy2w.NsG61RBnv380OyT8c4f 1DDzrelJ19hGDULN1kB.NxaBmmW2P.JSnnzNUywlggoIvwMjfoZNE7qzGSRw dxhitrjIBGjhTnXUkuXeXmueMjFg7zJc4ftOG6tqAXhvHRdoo_L0aYlBQTxt 2YXuHCq8yfEHsV0_Bbq5nzoeHkjkdpMtRH67NVKqjZ.9kBMsF2RbCnw.M2D6 Nz4tYP25kXbbUjA--
Received: from [130.76.32.40] by web161906.mail.bf1.yahoo.com via HTTP; Tue, 19 Feb 2013 10:47:10 PST
X-Rocket-MIMEInfo: 001.001, SGVsbG8gQ2hyaXN0ZXIsCgpUaGFuayB5b3UgZm9yIHlvdXIgcmV2aWV3IGlucHV0LCBhbmQgcGxlYXNlIHNlZSBiZWxvdyBmb3IgcmVzcG9uc2VzOgoKUmVnYXJkcyAtIEZyZWQKZmx0ZW1wbGluQGFjbS5vcmcKCgo.X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBGcm9tOiBDaHJpc3RlciBIb2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPgo.VG86ICJnZW4tYXJ0QGlldGYub3JnIiA8Z2VuLWFydEBpZXRmLm9yZz4gCj5DYzogImRyYWZ0LXRlbXBsaW4taW50YXJlYS1zZWEBMAEBAQE-
X-RocketYMMF: fltemplin
X-Mailer: YahooMailWebService/0.8.134.513
References: <7594FB04B1934943A5C02806D1A2204B0F78E8@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B0F890C@ESESSMB209.ericsson.se>
Message-ID: <1361299630.93115.YahooMailNeo@web161906.mail.bf1.yahoo.com>
Date: Tue, 19 Feb 2013 10:47:10 -0800 (PST)
From: "Fred L. Templin" <fltemplin@acm.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B0F890C@ESESSMB209.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: "draft-templin-intarea-seal.all@tools.ietf.org" <draft-templin-intarea-seal.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-templin-intarea-seal-51.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Fred L. Templin" <fltemplin@acm.org>
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 Feb 2013 18:47:12 -0000

Hello Christer,=0A=0AThank you for your review input, and please see below =
for responses:=0A=0ARegards - Fred=0Afltemplin@acm.org=0A=0A=0A>___________=
_____________________=0A> From: Christer Holmberg <christer.holmberg@ericss=
on.com>=0A>To: "gen-art@ietf.org" <gen-art@ietf.org> =0A>Cc: "draft-templin=
-intarea-seal.all@tools.ietf.org" <draft-templin-intarea-seal.all@tools.iet=
f.org> =0A>Sent: Tuesday, February 19, 2013 2:11 AM=0A>Subject: RE: Genart =
review of draft-templin-intarea-seal-51.txt=0A> =0A>=0A> =0A>E-mail address=
 corrected.=0A>=C2=A0=0A>From:gen-art-bounces@ietf.org [mailto:gen-art-boun=
ces@ietf.org] On Behalf Of Christer Holmberg=0A>Sent: 19. helmikuuta 2013 1=
2:10=0A>To: gen-art@ietf.org=0A>Cc: draft-templin-intarea-seal-all@tools.ie=
tf.org=0A>Subject: [Gen-art] Genart review of draft-templin-intarea-seal-51=
.txt=0A>=C2=A0=0A>I am the assigned Gen-ART reviewer for this draft. For ba=
ckground on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area=
/gen/trac/wiki/GenArtfaq>=0A>=C2=A0=0A>Document:=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 draft-templin-intarea-seal-51.txt=0A>=C2=A0=0A>Reviewer:=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Christer Holmberg=0A>=C2=A0=0A>Revi=
ew Date:=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A019 Feb 2013=0A>=C2=A0=0A>IETF LC End Date:=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 20 Feb 2013=0A>=C2=A0=0A>IETF Telec=
hat Date:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 21 Feb 2013=0A>=C2=A0=0A>Summ=
ary:=C2=A0 The draft is well written, but with some editorial comments that=
 I suggest to be addressed before publication.=0A>=C2=A0=0A>Major Issues: N=
one=0A>=C2=A0=0A>Minor Issues: None=0A>=C2=A0=0A>Editorial nits: See below=
=0A>=C2=A0=0A>Q_ED_1: Most of the text in the Abstract section does not bel=
ong there. The section should talk about what the document does, and not de=
fine what a subnetwork is etc. Only the last sentence talks about what the =
draft is about.=0A=0AHere is a proposed rewrite of the abstract:=0A=0A=C2=
=A0 "The Subnetwork Encapsulation and Adaptation Layer (SEAL) operates over=
 virtual topologies configured over connected IP=0A=C2=A0=C2=A0 network rou=
ting regions bounded by encapsulating border nodes. These virtual topologie=
s are manifested by tunnels that=0A=C2=A0=C2=A0 may span multiple IP and/or=
 sub-IP layer forwarding hops, where they may incur packet duplication, pac=
ket reordering, source=0A=C2=A0=C2=A0 address spoofing and traversal of lin=
ks with diverse Maximum Transmission Units (MTUs). SEAL uniquely addresses =
these=0A=C2=A0=C2=A0 issues through the encapsulation and messaging mechani=
sms specified in this document."=0A=0A=0A>Q_ED_2: In the Introduction secti=
on, I would suggest to add a reference for IP encapsulating/tunneling. RFC =
2003 is referenced later in the document, but I think it would be good to h=
ave something also in the Introduction.=0A=0ACitations for IP encapsulating=
/tunneling can be added as follows=0A=0A=C2=A0 "The use of IP encapsulation=
 (also known as "tunneling") has long been considered as the means for=0A=
=C2=A0=C2=A0=C2=A0 creating such virtual topologies (e.g., see [RFC2003][RF=
C2473])."=0A=0A>Q_ED_3: In section 1.2, do you need to define =E2=80=98subn=
etwork=E2=80=99 here? Isn=E2=80=99t it better to have the definition in one=
 single place =E2=80=93 the Terminology section?=0A=0AProposed resolution i=
s to rewrite the first sentence of this section as follows:=0A=0A=0A=C2=A0=
=C2=A0 "This document concerns subnetworks manifested through a virtual top=
ology configured over a connected=0A=C2=A0=C2=A0=C2=A0=C2=A0 network routin=
g region and bounded by encapsulating border nodes."=0A=0A>Q_ED_4: In secti=
on 12, there seems to be a dot too much J=0A=0AI don't understand this - co=
uld you clarify?=0A=0A>Best regards,=0A>=C2=A0=0A>Christer=0A>=C2=A0=0A>=C2=
=A0=0A>=C2=A0=0A>=0A>

From christer.holmberg@ericsson.com  Tue Feb 19 11:21:36 2013
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 2CBFE21F8E72 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 11:21:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.285
X-Spam-Level: 
X-Spam-Status: No, score=-6.285 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cHezjbXn76r5 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 11:21:35 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 116B821F8E30 for <gen-art@ietf.org>; Tue, 19 Feb 2013 11:21:33 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-c8-5123d0bc3a7f
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 9F.4D.10459.CB0D3215; Tue, 19 Feb 2013 20:21:33 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.82]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 20:21:32 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Fred L. Templin" <fltemplin@acm.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-templin-intarea-seal-51.txt
Thread-Index: Ac4OiTSa1jkabDjkRUqWja4TC497FQAAB/tAAA/z7wAAAxhu6Q==
Date: Tue, 19 Feb 2013 19:21:31 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B0FAE0F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B0F78E8@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B0F890C@ESESSMB209.ericsson.se>, <1361299630.93115.YahooMailNeo@web161906.mail.bf1.yahoo.com>
In-Reply-To: <1361299630.93115.YahooMailNeo@web161906.mail.bf1.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsUyM+Jvje7eC8qBBtctLLb9vsRo0b/lD6PF 1VefWRyYPS5f8fZYsuQnk8eXy5/ZApijuGxSUnMyy1KL9O0SuDKWNAcXvJGuWLjgFUsDY7tY FyMHh4SAicSFfTFdjJxAppjEhXvr2boYuTiEBA4xSvx6uQLKWcwoceB2DyNIA5uAhUT3P22Q BhGBIIm/xz4xg9jMAqkSzQ9usIDYwgL2Ek++PmSEqHGQ+HJxMguE7SSx8/k/dhCbRUBVouHO AzCbV8Bb4u3JpywQu04xStxbdhhsKKeAp8TMe81gzYxA130/tYYJYpm4xK0n85kgrhaQWLLn PDOELSrx8vE/VojHFCWW98tBlBtIvD83H+pObYllC18zQ+wVlDg58wnLBEaxWUimzkLSMgtJ yywkLQsYWVYxsucmZuaklxtuYgTGy8Etv3V3MJ46J3KIUZqDRUmcN8z1QoCQQHpiSWp2ampB alF8UWlOavEhRiYOTqkGxrz9yfKGfOXSa3ryS2Udnf72McxvPPGhzJODeZ5ahP4K5teRkXO8 5xT2PtOuuFx2zTpk5fYmTctPky/xpCzg5alnWqAdPcfLZm6bbNGjD0FPtD+6c0i3z8/8yJc+ gcl2itMPl1dZ0+35tCrPbpML7PkneuJ1gEBLyOIlwW5Pbx6xyjIr3mSsxFKckWioxVxUnAgA jEI8DGUCAAA=
Cc: "draft-templin-intarea-seal.all@tools.ietf.org" <draft-templin-intarea-seal.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-templin-intarea-seal-51.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 Feb 2013 19:21:36 -0000

Hi Fred,

Comments inline.

>>From:gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On Behalf=
 Of Christer Holmberg
>>Sent: 19. helmikuuta 2013 12:10
>>To: gen-art@ietf.org
>>Cc: draft-templin-intarea-seal-all@tools.ietf.org
>>Subject: [Gen-art] Genart review of draft-templin-intarea-seal-51.txt
>>=A0
>>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/G=
enArtfaq>
>>=A0
>>Document:                    draft-templin-intarea-seal-51.txt
>>=A0
>>Reviewer:                     Christer Holmberg
>>=A0
>>Review Date:                 19 Feb 2013
>>=A0
>>IETF LC End Date:        20 Feb 2013
>>=A0
>>IETF Telechat Date:       21 Feb 2013
>>=A0
>>Summary:  The draft is well written, but with some editorial comments tha=
t I suggest to be addressed before publication.
>>=A0
>>Major Issues: None
>>=A0
>>Minor Issues: None
>>=A0
>>Editorial nits: See below
>>=A0
>>Q_ED_1: Most of the text in the Abstract section does not belong there. T=
he section should talk about what the document does, and not define what a =
subnetwork is etc. Only the last sentence talks about what the draft is abo=
ut.
>
>Here is a proposed rewrite of the abstract:
>
>  "The Subnetwork Encapsulation and Adaptation Layer (SEAL) operates over =
virtual topologies configured over connected IP
>   network routing regions bounded by encapsulating border nodes. These vi=
rtual topologies are manifested by tunnels that
>   may span multiple IP and/or sub-IP layer forwarding hops, where they ma=
y incur packet duplication, packet reordering, source
>   address spoofing and traversal of links with diverse Maximum Transmissi=
on Units (MTUs). SEAL uniquely addresses these
>   issues through the encapsulation and messaging mechanisms specified in =
this document."

It looks good, but I would start with a "This document specifies a Subnetwo=
rk Encapsulation and Adaptation Layer (SEAL). SEAL operates over virtual...=
."


>>Q_ED_2: In the Introduction section, I would suggest to add a reference f=
or IP encapsulating/tunneling. RFC 2003 is referenced later in the document=
, but I think it would be good to have something also in the Introduction.
>
>Citations for IP encapsulating/tunneling can be added as follows
>
>  "The use of IP encapsulation (also known as "tunneling") has long been c=
onsidered as the means for
>    creating such virtual topologies (e.g., see [RFC2003][RFC2473])."

Looks good.

>>Q_ED_3: In section 1.2, do you need to define =91subnetwork=92 here? Isn=
=92t it better to have the definition in one single place =96 the Terminolo=
gy section?
>
>Proposed resolution is to rewrite the first sentence of this section as fo=
llows:
>
>  "This document concerns subnetworks manifested through a virtual topolog=
y configured over a connected
>     network routing region and bounded by encapsulating border nodes."

Looks good.

>>Q_ED_4: In section 12, there seems to be a dot too much J
>
>I don't understand this - could you clarify?

At least in my browser, section 12 looks like:

-----

   The IANA is requested to allocate a User Port number for "SEAL" in
   the 'port-numbers' registry for the TCP and UDP protocols.

   The IANA is further requested to allocate an IP protocol number for
   "SEAL" in the "protocol-numbers" registry.

   .

-----

Note the lonely dot at the end, below the second paragraph :)

Regards,

Christer


From fltemplin@yahoo.com  Tue Feb 19 11:35:44 2013
Return-Path: <fltemplin@yahoo.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 D269821E80BB for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 11:35:44 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WfOB+7UfmQF5 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 11:35:44 -0800 (PST)
Received: from nm31-vm0.bullet.mail.bf1.yahoo.com (nm31-vm0.bullet.mail.bf1.yahoo.com [72.30.239.8]) by ietfa.amsl.com (Postfix) with ESMTP id B4A8221E80B9 for <gen-art@ietf.org>; Tue, 19 Feb 2013 11:35:43 -0800 (PST)
Received: from [98.139.212.153] by nm31.bullet.mail.bf1.yahoo.com with NNFMP; 19 Feb 2013 19:35:43 -0000
Received: from [98.139.212.212] by tm10.bullet.mail.bf1.yahoo.com with NNFMP; 19 Feb 2013 19:35:43 -0000
Received: from [127.0.0.1] by omp1021.mail.bf1.yahoo.com with NNFMP; 19 Feb 2013 19:35:43 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 59980.84417.bm@omp1021.mail.bf1.yahoo.com
Received: (qmail 3862 invoked by uid 60001); 19 Feb 2013 19:35:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1361302542; bh=uo/VhyvbejFceHbt70qN6rEHHYh1cT9XyTz+UJBG1ws=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=3TtMixekYRCzIjGAmW/A/i7d23BTAPrKPuq8iib0Af2TyCimnz/rWb3s0zaY2keQ/ouyUMl7oEFoLZDc6lbVX8HDS5FBb7f3zRofc9DQgrG3OouvUg+EzDZOpOD+QcWAnOqWjyvVIcluJrOvwuza5nhQj1si/o22hxChbL/YP2g=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=HzXZTFCM2adD+Z8yTbjZXHyopBA3Acp3UR8Ux/WIQl6DD3xcvuQey3pSwuJjbPwSGnf9kpQOkk3swWUaiiztbotC9cJ/HwkYtk9POeZ/jXsvX+WSXUezDqM8FiXl5ss70tQbJOxAk2ZHEz7u0JgwWkmK8T8YrtmAgC4DWW8phvk=;
X-YMail-OSG: pwv5mXsVM1l61VhR1PoDgSKaViZ9mTeAY1kGGHyJS2DQDLX 4ITVVCroGJZlu0uYoz6fT5neV6cJUrQ5eDf8pwCon5KX4kP.xn0KHHUMzdAb fwjGNzffo2cq1IyxxflvvJfZW7m0.vjKMLqJ5oL0AAv6kX4omaoR11bndSNi _3IC2e8_0JWYemYQjuNWshX.z9JANFMhkHZfVjTNmOzip9RovCMFBF9TeYI7 q664JIkaNmGO4Sm2WQ6qnAdEh6kCjH5TgIXtZbApWIv57kEHv3igFejYIy2j ycqeHcbUVh0ItBH76apFN0_6hTHLeWojwMsJz4Kd5k4CzTLTu..cJclGku39 5tZUnFMDzCSAoq9LFuvGuB.UBYY4LBCy2UUwm4rpZ_guMqrUTwx_X1oL7Bav yKQa14UR3mpCcvcXYG7nVwvhMtbgleD.RhW52goX2JHvMgyG.M4uj8MdhhGU V1hmHvSIdR0va7ISmG5fhayxQYeQ479TEkRxiJisfJ.iLt91HdMmEzz8fmon _o7DTJm8_w6HiuQ--
Received: from [130.76.32.40] by web161905.mail.bf1.yahoo.com via HTTP; Tue, 19 Feb 2013 11:35:42 PST
X-Rocket-MIMEInfo: 001.001, SGVsbG8gQ2hyaXN0ZXIsCgpUaGFua3MgYWdhaW4gZm9yIHRoaXMgZm9sbG93LXVwLCBhbmQgc2VlIGJlbG93OgoKRnJlZApmbHRlbXBsaW5AYWNtLm9yZwoKCgoKLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQo.IEZyb206IENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20.Cj4gVG86IEZyZWQgTC4gVGVtcGxpbiA8Zmx0ZW1wbGluQGFjbS5vcmc.OyAiZ2VuLWFydEBpZXRmLm9yZyIgPGdlbi1hcnRAaWV0Zi5vcmc.Cj4gQ2M6ICJkcmFmdC10ZW1wbGluLWludGFyZWEBMAEBAQE-
X-RocketYMMF: fltemplin
X-Mailer: YahooMailWebService/0.8.134.513
References: <7594FB04B1934943A5C02806D1A2204B0F78E8@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B0F890C@ESESSMB209.ericsson.se>, <1361299630.93115.YahooMailNeo@web161906.mail.bf1.yahoo.com> <7594FB04B1934943A5C02806D1A2204B0FAE0F@ESESSMB209.ericsson.se>
Message-ID: <1361302542.391.YahooMailNeo@web161905.mail.bf1.yahoo.com>
Date: Tue, 19 Feb 2013 11:35:42 -0800 (PST)
From: "Fred L. Templin" <fltemplin@acm.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B0FAE0F@ESESSMB209.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: "draft-templin-intarea-seal.all@tools.ietf.org" <draft-templin-intarea-seal.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-templin-intarea-seal-51.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Fred L. Templin" <fltemplin@acm.org>
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 Feb 2013 19:35:45 -0000

Hello Christer,=0A=0AThanks again for this follow-up, and see below:=0A=0AF=
red=0Afltemplin@acm.org=0A=0A=0A=0A=0A----- Original Message -----=0A> From=
: Christer Holmberg <christer.holmberg@ericsson.com>=0A> To: Fred L. Templi=
n <fltemplin@acm.org>; "gen-art@ietf.org" <gen-art@ietf.org>=0A> Cc: "draft=
-templin-intarea-seal.all@tools.ietf.org" <draft-templin-intarea-seal.all@t=
ools.ietf.org>=0A> Sent: Tuesday, February 19, 2013 11:21 AM=0A> Subject: R=
E: Genart review of draft-templin-intarea-seal-51.txt=0A> =0A> =0A> Hi Fred=
,=0A> =0A> Comments inline.=0A> =0A>>> From:gen-art-bounces@ietf.org [mailt=
o:gen-art-bounces@ietf.org] On =0A> Behalf Of Christer Holmberg=0A>>> Sent:=
 19. helmikuuta 2013 12:10=0A>>> To: gen-art@ietf.org=0A>>> Cc: draft-templ=
in-intarea-seal-all@tools.ietf.org=0A>>> Subject: [Gen-art] Genart review o=
f draft-templin-intarea-seal-51.txt=0A>>> =C2=A0=0A>>> I am the assigned Ge=
n-ART reviewer for this draft. For background on =0A> Gen-ART, please see t=
he FAQ at =0A> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>=0A=
>>> =C2=A0=0A>>> Document:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 draft-templin-intarea-seal-51.txt=0A>>> =C2=A0=0A>>> R=
eviewer:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0  Christer Holmberg=0A>>> =C2=A0=0A>>> Review Date:=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0  19 Feb 2013=0A>>> =C2=A0=0A>>> IETF LC =
End Date:=C2=A0 =C2=A0 =C2=A0 =C2=A0 20 Feb 2013=0A>>> =C2=A0=0A>>> IETF Te=
lechat Date:=C2=A0 =C2=A0 =C2=A0  21 Feb 2013=0A>>> =C2=A0=0A>>> Summary:=
=C2=A0 The draft is well written, but with some editorial comments =0A> tha=
t I suggest to be addressed before publication.=0A>>> =C2=A0=0A>>> Major Is=
sues: None=0A>>> =C2=A0=0A>>> Minor Issues: None=0A>>> =C2=A0=0A>>> Editori=
al nits: See below=0A>>> =C2=A0=0A>>> Q_ED_1: Most of the text in the Abstr=
act section does not belong there. =0A> The section should talk about what =
the document does, and not define what a =0A> subnetwork is etc. Only the l=
ast sentence talks about what the draft is about.=0A>> =0A>> Here is a prop=
osed rewrite of the abstract:=0A>> =0A>> =C2=A0 "The Subnetwork Encapsulati=
on and Adaptation Layer (SEAL) operates =0A> over virtual topologies config=
ured over connected IP=0A>> =C2=A0  network routing regions bounded by enca=
psulating border nodes. These =0A> virtual topologies are manifested by tun=
nels that=0A>> =C2=A0  may span multiple IP and/or sub-IP layer forwarding =
hops, where they may =0A> incur packet duplication, packet reordering, sour=
ce=0A>> =C2=A0  address spoofing and traversal of links with diverse Maximu=
m Transmission =0A> Units (MTUs). SEAL uniquely addresses these=0A>> =C2=A0=
  issues through the encapsulation and messaging mechanisms specified in =
=0A> this document."=0A> =0A> It looks good, but I would start with a "This=
 document specifies a =0A> Subnetwork Encapsulation and Adaptation Layer (S=
EAL). SEAL operates over =0A> virtual...."=0A=0AYes, your suggestion looks =
better. It will appear this way in the next document=0Aversion.=0A=0A>>> Q_=
ED_2: In the Introduction section, I would suggest to add a reference =0A> =
for IP encapsulating/tunneling. RFC 2003 is referenced later in the documen=
t, =0A> but I think it would be good to have something also in the Introduc=
tion.=0A>> =0A>> Citations for IP encapsulating/tunneling can be added as f=
ollows=0A>> =0A>> =C2=A0 "The use of IP encapsulation (also known as "tunne=
ling") =0A> has long been considered as the means for=0A>> =C2=A0 =C2=A0 cr=
eating such virtual topologies (e.g., see [RFC2003][RFC2473])."=0A> =0A> Lo=
oks good.=0A=0AOK.=0A=0A>>> Q_ED_3: In section 1.2, do you need to define =
=E2=80=98subnetwork=E2=80=99 here? Isn=E2=80=99t =0A> it better to have the=
 definition in one single place =E2=80=93 the Terminology section?=0A>> =0A=
>> Proposed resolution is to rewrite the first sentence of this section as =
=0A> follows:=0A>> =0A>> =C2=A0 "This document concerns subnetworks manifes=
ted through a virtual =0A> topology configured over a connected=0A>> =C2=A0=
 =C2=A0  network routing region and bounded by encapsulating border nodes."=
=0A> =0A> Looks good.=0A=0AOK.=0A=C2=A0=0A>>> Q_ED_4: In section 12, there =
seems to be a dot too much J=0A>> =0A>> I don't understand this - could you=
 clarify?=0A> =0A> At least in my browser, section 12 looks like:=0A> =0A> =
-----=0A> =0A> =C2=A0  The IANA is requested to allocate a User Port number=
 for "SEAL" in=0A> =C2=A0  the 'port-numbers' registry for the TCP and UDP =
protocols.=0A> =0A> =C2=A0  The IANA is further requested to allocate an IP=
 protocol number for=0A> =C2=A0  "SEAL" in the "protocol-numbers" registry.=
=0A> =0A> =C2=A0  .=0A> =0A> -----=0A> =0A> Note the lonely dot at the end,=
 below the second paragraph :)=0A=0AAh, I see it now. This will also be fix=
ed. Thank you.=0A=0AFred=0Afltemplin@acm.org=0A=0A> =0A> Regards,=0A> =0A> =
Christer=0A> 

From Jon.Mitchell@microsoft.com  Tue Feb 19 12:27:14 2013
Return-Path: <Jon.Mitchell@microsoft.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 3D33721F8B07 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 12:27:14 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aRbVmHo9eRZW for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 12:27:13 -0800 (PST)
Received: from na01-sn2-obe.outbound.o365filtering.com (na01-sn2-obe.ptr.o365filtering.com [157.55.158.29]) by ietfa.amsl.com (Postfix) with ESMTP id 2FFA921F8B06 for <gen-art@ietf.org>; Tue, 19 Feb 2013 12:27:13 -0800 (PST)
Received: from BLUSR01CA103.namsdf01.sdf.exchangelabs.com (10.255.124.148) by BLUSR01MB603.namsdf01.sdf.exchangelabs.com (10.255.124.168) with Microsoft SMTP Server (TLS) id 15.0.620.19; Tue, 19 Feb 2013 20:27:10 +0000
Received: from BY1FFOFD001.ffo.gbl (64.4.22.90) by BLUSR01CA103.outlook.office365.com (10.255.124.148) with Microsoft SMTP Server (TLS) id 15.0.620.19 via Frontend Transport; Tue, 19 Feb 2013 20:27:09 +0000
Received: from hybrid.exchange.microsoft.com (131.107.1.27) by BY1FFOFD001.mail.o365filtering.com (10.1.16.83) with Microsoft SMTP Server (TLS) id 15.0.620.12 via Frontend Transport; Tue, 19 Feb 2013 20:27:09 +0000
Received: from DFM-TK5MBX15-05.exchange.corp.microsoft.com (157.54.109.44) by DF-G14-02.exchange.corp.microsoft.com (157.54.87.56) with Microsoft SMTP Server (TLS) id 14.3.123.1; Tue, 19 Feb 2013 12:26:43 -0800
Received: from DFM-DB3MBX15-08.exchange.corp.microsoft.com (10.166.18.226) by DFM-TK5MBX15-05.exchange.corp.microsoft.com (157.54.109.44) with Microsoft SMTP Server (TLS) id 15.0.620.14; Tue, 19 Feb 2013 12:26:43 -0800
Received: from DFM-DB3MBX15-08.exchange.corp.microsoft.com (10.166.18.226) by DFM-DB3MBX15-08.exchange.corp.microsoft.com (10.166.18.226) with Microsoft SMTP Server (TLS) id 15.0.620.14; Tue, 19 Feb 2013 12:26:40 -0800
Received: from DFM-DB3MBX15-08.exchange.corp.microsoft.com ([169.254.12.208]) by DFM-DB3MBX15-08.exchange.corp.microsoft.com ([169.254.12.153]) with mapi id 15.00.0620.012; Tue, 19 Feb 2013 12:26:40 -0800
From: "Jon Mitchell (GNS)" <Jon.Mitchell@microsoft.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
Thread-Topic: Gen-art last call review of draft-ietf-idr-as-private-reservation-03
Thread-Index: AQHOC10lIVUr21ivuU+LWoBnRrohjph/sC6QgAE7doCAALefAA==
Date: Tue, 19 Feb 2013 20:26:40 +0000
Message-ID: <4f5ed402038544d0b1da25226424e60b@DFM-DB3MBX15-08.exchange.corp.microsoft.com>
References: <511DFCAD.6020509@dial.pipex.com> <f1195a2f3468441d85edaf0b8b843bba@DFM-DB3MBX15-08.exchange.corp.microsoft.com> <1361236326.4494.891.camel@mightyatom>
In-Reply-To: <1361236326.4494.891.camel@mightyatom>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.1.27; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(41574001)(24454001)(51704002)(13464002)(377424002)(377454001)(47976001)(46406002)(50986001)(56776001)(50466001)(49866001)(54316002)(56816002)(76482001)(66066001)(63696002)(47776003)(46102001)(80022001)(54356001)(20776003)(53806001)(65816001)(33646001)(59766001)(44976002)(4396001)(876001)(47736001)(23726001)(31966008)(77982001)(47446002)(74662001)(74502001)(79102001)(5343655001)(51856001)(16406001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BLUSR01MB603; H:hybrid.exchange.microsoft.com; RD:mail7.exchange.microsoft.com; MX:1; A:1; LANG:en; 
X-Forefront-PRVS: 0762FFD075
X-OriginatorOrg: DuplicateDomain-7923a859-03c9-4312-a77c-440aa45aaf52.microsoft.com
Cc: "draft-ietf-idr-as-private-reservation.all@tools.ietf.org" <draft-ietf-idr-as-private-reservation.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-idr-as-private-reservation-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: Tue, 19 Feb 2013 20:27:14 -0000

Elwyn -

Yes, I agree this is a reasonable change to remove all of the "suggestion" =
text in the IANA considerations area and will make sure it is in the next d=
raft if one is required, either way all of that text will be removed by IAN=
A, who has also just sent back their review of the actions required.

On your second comment, currently being published as an RFC is a draft rese=
rving as0 in a similar fashion, so I do think it's most appropriate as a se=
cond doc.. and I really have trouble tying these reservations to a RFC abou=
t Private ASN's.   If no doc is published, the good news is that IANA has a=
lready reserved the last number (with no justification).  Again, if IESG or=
 others feel strongly it should be in this draft, I will try to work out so=
me text to justify their reservations...

Thanks!

Jon

-----Original Message-----
From: Elwyn Davies [mailto:elwynd@dial.pipex.com]=20
Sent: Monday, February 18, 2013 8:12 PM
To: Jon Mitchell (GNS)
Cc: General Area Review Team; draft-ietf-idr-as-private-reservation.all@too=
ls.ietf.org
Subject: RE: Gen-art last call review of draft-ietf-idr-as-private-reservat=
ion-03

On Mon, 2013-02-18 at 15:26 +0000, Jon Mitchell (GNS) wrote:
> Elwyn -
>=20
> Thanks for your review.=20
:-)

>  The suggestion is being made to IANA who owns the assignment and was=20
> discussed at length in the working group with rough consensus.
As specified in the registry, allocations in this registry are either by IE=
TF Concensus (i.e. a suitable RFC such as this draft is intended to
be) or request from a RIR. Thus it isn't a matter of suggesting to IANA but=
 telling them what the IETF want done - so this draft should be definitive =
- and what you said about WG concensus constitutes the values to be used un=
less somebody else in the IETF manages to alter the concensus which seems u=
nlikely.
 =20
> IANA will replace the suggested values into TBDX values below that=20
> text if IESG approves.  This text will not be in the RFC, it's to be=20
> stricken from the final document by RFC Editor (I was attempting to=20
> write this text in alignment with Section 5.1 of RFC 5226) .
Yes, that's fine and as expected.
>=20
> On the final ASN in the range, this is in accordance with like=20
> reservation of the existing 2 byte Private ASN reservations, where the=20
> final ASN in that space is not utilized either (except for well-known=20
> community values).  Also, a case was made that code implementations=20
> tend to have issues with final number usage if using incorrect=20
> variable types for storage.  That said, the small discussion on and=20
> off list about this resolved that if we wanted to formalize the=20
> reservation of the last ASN of both the 2 byte space 65535 and the 4=20
> byte space 4294967295, probably a separate draft should be constructed=20
> detailing the logic behind these as they have nothing to do with=20
> Private ASN's per se and have already been marked as Reserved by IANA=20
> as you noted.  I'm open to IESG direction if we want to take a=20
> different approach on this...
Publishing a separate draft seems a bit overkill but clearly that's not my =
decision. ;-)

Regards,
Elwyn
>=20
> Cheers,
>=20
> Jon
>=20
> -----Original Message-----
> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
> Sent: Friday, February 15, 2013 4:15 AM
> To: General Area Review Team
> Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org
> Subject: Gen-art last call review of=20
> draft-ietf-idr-as-private-reservation-03
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on=20
> Gen-ART, please see the FAQ at
>=20
> <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-ietf-idr-as-private-reservation-03.txt
> Reviewer: Elwyn Davies
> Review Date: 15 February 2013
> IETF LC End Date: 22 February 2013
> IESG Telechat date: (if known) -
>=20
> Summary: Ready for the IESG.
>=20
> Nits/editorial comments:  The draft is not actually definitive about rang=
e of values to be allocated - the range in s10 is just a 'suggestion'.  Who=
 is actually making the decision about the range?
>=20
> Aside: I noted that the highest possible 32 bit number (4294967295 =3D
> 0xFFFFFFFF) is excluded from the proposed range.  This is marked as=20
> reserved in the IANA table but AFAICS this reserved item does not have=20
> a specification associated with the reservation.  This document would=20
> be an opportunity to explicitly mention that the topmost value is=20
> reserved (for future expansion? :-) )
>=20
>=20


From christer.holmberg@ericsson.com  Tue Feb 19 12:29:39 2013
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 A86AA21F8B6D for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 12:29:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.284
X-Spam-Level: 
X-Spam-Status: No, score=-6.284 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QfYhsxATlhlf for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 12:29:38 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5419821F8B69 for <gen-art@ietf.org>; Tue, 19 Feb 2013 12:29:38 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-bd-5123e0aeed88
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id B0.22.10459.EA0E3215; Tue, 19 Feb 2013 21:29:35 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.82]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 21:29:34 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Fred L. Templin" <fltemplin@acm.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-templin-intarea-seal-51.txt
Thread-Index: Ac4OiTSa1jkabDjkRUqWja4TC497FQAAB/tAAA/z7wAAAxhu6f//9MsAgAAfsOY=
Date: Tue, 19 Feb 2013 20:29:33 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B0FBED5@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B0F78E8@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B0F890C@ESESSMB209.ericsson.se>, <1361299630.93115.YahooMailNeo@web161906.mail.bf1.yahoo.com> <7594FB04B1934943A5C02806D1A2204B0FAE0F@ESESSMB209.ericsson.se>, <1361302542.391.YahooMailNeo@web161905.mail.bf1.yahoo.com>
In-Reply-To: <1361302542.391.YahooMailNeo@web161905.mail.bf1.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyM+Jvje76B8qBBs/auC22/b7EaNG/5Q+j xdVXn1kcmD0uX/H2WLLkJ5PHl8uf2QKYo7hsUlJzMstSi/TtErgytnW8YSmYp1pxcMMfpgbG A7JdjJwcEgImEvfXL2GDsMUkLtxbD2RzcQgJHGKUePL2FTuEs5hR4vftG4xdjBwcbAIWEt3/ tEEaRASCJP4e+8QMYjMLpEo0P7jBAmILC9hLPPn6kBGixkHiy8XJLBC2n8THA/vYQWwWAVWJ jpMtYDavgLfE702XWSB2HWeS2LluNliCU8Bd4tqLjWDXMQJd9/3UGiaIZeISt57MZ4K4WkBi yZ7zzBC2qMTLx/9YQe6UEFCUWN4vB1FuIPH+3HyoO7Ulli18zQyxV1Di5MwnLBMYxWYhmToL ScssJC2zkLQsYGRZxciem5iZk15uuIkRGDUHt/zW3cF46pzIIUZpDhYlcd4w1wsBQgLpiSWp 2ampBalF8UWlOanFhxiZODilGhjdzxZvqij12tIkvuKcXveltN2sh94eMT7Rfn2e1tyuH4yt RcuWn0rz9n3xwia8e/q3xbumfXpZ4abjkbjSpMYw75Wa9JZFvOV33gm5lQtnztlxXbC4c65a wBafCnVZzWn/P9aKNmunvmqY0aHQsfL7nbuPX0/WiH4i/oJVZvcS9/Vzi0JsLkYqsRRnJBpq MRcVJwIAx2UORGgCAAA=
Cc: "draft-templin-intarea-seal.all@tools.ietf.org" <draft-templin-intarea-seal.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-templin-intarea-seal-51.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 Feb 2013 20:29:39 -0000

Hi,

With the changes below, I think the document is ready for publication :)

Regards,

Christer

________________________________________
From: Fred L. Templin [fltemplin@acm.org]
Sent: Tuesday, 19 February 2013 9:35 PM
To: Christer Holmberg; gen-art@ietf.org
Cc: draft-templin-intarea-seal.all@tools.ietf.org
Subject: Re: Genart review of draft-templin-intarea-seal-51.txt

Hello Christer,

Thanks again for this follow-up, and see below:

Fred
fltemplin@acm.org




----- Original Message -----
> From: Christer Holmberg <christer.holmberg@ericsson.com>
> To: Fred L. Templin <fltemplin@acm.org>; "gen-art@ietf.org" <gen-art@ietf=
.org>
> Cc: "draft-templin-intarea-seal.all@tools.ietf.org" <draft-templin-intare=
a-seal.all@tools.ietf.org>
> Sent: Tuesday, February 19, 2013 11:21 AM
> Subject: RE: Genart review of draft-templin-intarea-seal-51.txt
>
>
> Hi Fred,
>
> Comments inline.
>
>>> From:gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On
> Behalf Of Christer Holmberg
>>> Sent: 19. helmikuuta 2013 12:10
>>> To: gen-art@ietf.org
>>> Cc: draft-templin-intarea-seal-all@tools.ietf.org
>>> Subject: [Gen-art] Genart review of draft-templin-intarea-seal-51.txt
>>>
>>> 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-templin-intarea-seal-51.txt
>>>
>>> Reviewer:                     Christer Holmberg
>>>
>>> Review Date:                 19 Feb 2013
>>>
>>> IETF LC End Date:        20 Feb 2013
>>>
>>> IETF Telechat Date:       21 Feb 2013
>>>
>>> Summary:  The draft is well written, but with some editorial comments
> that I suggest to be addressed before publication.
>>>
>>> Major Issues: None
>>>
>>> Minor Issues: None
>>>
>>> Editorial nits: See below
>>>
>>> Q_ED_1: Most of the text in the Abstract section does not belong there.
> The section should talk about what the document does, and not define what=
 a
> subnetwork is etc. Only the last sentence talks about what the draft is a=
bout.
>>
>> Here is a proposed rewrite of the abstract:
>>
>>   "The Subnetwork Encapsulation and Adaptation Layer (SEAL) operates
> over virtual topologies configured over connected IP
>>    network routing regions bounded by encapsulating border nodes. These
> virtual topologies are manifested by tunnels that
>>    may span multiple IP and/or sub-IP layer forwarding hops, where they =
may
> incur packet duplication, packet reordering, source
>>    address spoofing and traversal of links with diverse Maximum Transmis=
sion
> Units (MTUs). SEAL uniquely addresses these
>>    issues through the encapsulation and messaging mechanisms specified i=
n
> this document."
>
> It looks good, but I would start with a "This document specifies a
> Subnetwork Encapsulation and Adaptation Layer (SEAL). SEAL operates over
> virtual...."

Yes, your suggestion looks better. It will appear this way in the next docu=
ment
version.

>>> Q_ED_2: In the Introduction section, I would suggest to add a reference
> for IP encapsulating/tunneling. RFC 2003 is referenced later in the docum=
ent,
> but I think it would be good to have something also in the Introduction.
>>
>> Citations for IP encapsulating/tunneling can be added as follows
>>
>>   "The use of IP encapsulation (also known as "tunneling")
> has long been considered as the means for
>>     creating such virtual topologies (e.g., see [RFC2003][RFC2473])."
>
> Looks good.

OK.

>>> Q_ED_3: In section 1.2, do you need to define =91subnetwork=92 here? Is=
n=92t
> it better to have the definition in one single place =96 the Terminology =
section?
>>
>> Proposed resolution is to rewrite the first sentence of this section as
> follows:
>>
>>   "This document concerns subnetworks manifested through a virtual
> topology configured over a connected
>>      network routing region and bounded by encapsulating border nodes."
>
> Looks good.

OK.

>>> Q_ED_4: In section 12, there seems to be a dot too much J
>>
>> I don't understand this - could you clarify?
>
> At least in my browser, section 12 looks like:
>
> -----
>
>    The IANA is requested to allocate a User Port number for "SEAL" in
>    the 'port-numbers' registry for the TCP and UDP protocols.
>
>    The IANA is further requested to allocate an IP protocol number for
>    "SEAL" in the "protocol-numbers" registry.
>
>    .
>
> -----
>
> Note the lonely dot at the end, below the second paragraph :)

Ah, I see it now. This will also be fixed. Thank you.

Fred
fltemplin@acm.org

>
> Regards,
>
> Christer
>

From wassim.haddad@ericsson.com  Tue Feb 19 13:13:06 2013
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 ADD7421F8AC0 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 13:13:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.404
X-Spam-Level: 
X-Spam-Status: No, score=-101.404 tagged_above=-999 required=5 tests=[AWL=0.967, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PaE7XxYOCn0L for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 13:13:05 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7680F21F8ABA for <gen-art@ietf.org>; Tue, 19 Feb 2013 13:13:05 -0800 (PST)
X-AuditID: c618062d-b7fcb6d000007ada-29-5123eae00ae1
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 6F.35.31450.0EAE3215; Tue, 19 Feb 2013 22:13:04 +0100 (CET)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC002.ericsson.se (147.117.188.78) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 19 Feb 2013 16:13:04 -0500
Received: from eusjgala119.dyn.sj.us.am.ericsson.se (147.117.20.214) by eusaamw0712.eamcs.ericsson.se (147.117.20.182) with Microsoft SMTP Server id 8.3.279.1; Tue, 19 Feb 2013 16:13:03 -0500
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_36C0A492-9A34-48C3-BD58-B1B81103C083"
Date: Tue, 19 Feb 2013 13:13:06 -0800
Message-ID: <8BAD56D7-1D7D-487D-A221-CABF61DC75CD@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
MIME-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprALMWRmVeSWpSXmKPExsUyuXSPn+6DV8qBBu+v2Fg8nfaL1eLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfGt2uz2Aqu8lX0XTvO0sDYxNvFyMkhIWAi MX/PZSYIW0ziwr31bF2MXBxCAkcYJW5tnMEK4exhlJiyYQoThHOYUaL78WcWkBY2AQOJr8vP soLYzAJJEqc+HwUbJSwQIPH96Wowm0VAVeLnuj9sIDavgL1E/8I77F2MHED1RRLnF0WAhEUE NCXmrnjLBBLmFdCTWNXLDHGQrMSKqb1gU4QE1CWm3JrAMoGRfxaSZbMQOiDC2hLLFr6GsnUk Fuz+xAZhy0tsfzsHrubMgcdMCxjZVjFylBanluWmGxlsYgSG6jEJNt0djHteWh5ilOZgURLn DXK9ECAkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBkaffvi1ZiHeCpa+KuuSU5ckhC0599ZMv fMn0uK2G67GuRlE2y+FnhqU5Hak8GSZzLaZnym9Y51/78E9Msalz+gsmnkXSTD3py+I1wmt6 F/6RjqxTPC1w4MGa7zzTbndl3+W/d/bFqs//atQYHmo37vh3pj602LPTm1PJ/dzRZNGDHze8 NElRYinOSDTUYi4qTgQApUMPZiMCAAA=
Cc: draft-ietf-paws-problem-stmt-usecases-rqmts.all@tools.ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-paws-problem-stmt-usecases-rqmts
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 Feb 2013 21:13:06 -0000

--Apple-Mail=_36C0A492-9A34-48C3-BD58-B1B81103C083
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"

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

Document: draft-ietf-paws-problem-stmt-usecases-rqmts-13
Reviewer:  Wassim M. Haddad
Review Date: 19 Feb 2013
IETF LC End Date: 15 Feb 2013
IETF Telechat Date: 21 Feb 2013

Summary:  Well written. This draft is ready for publication as =
informational standard.


- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.







--Apple-Mail=_36C0A492-9A34-48C3-BD58-B1B81103C083
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset="us-ascii"

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART,&nbsp;<br>please see the FAQ at &lt;<a href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;<br><br>Document:&nbsp;draft-ietf-paws-problem-stmt-usecases-rqmts-13<br>Reviewer: &nbsp;Wassim M. Haddad<br>Review Date: 19 Feb 2013<br>IETF LC End Date: 15 Feb 2013<br>IETF Telechat Date: 21 Feb 2013<br><br>Summary: &nbsp;Well written.&nbsp;This draft is ready for publication as informational standard.</div><div><br><br>- Major Issues: None<br><br>- Minor Issues: None<br><br><br>Regards,<br><br>Wassim H.</div><div><br></div><div><br></div><br><div><br></div><div><div apple-content-edited="true"><br class="Apple-interchange-newline">
</div>
<br></div></body></html>
--Apple-Mail=_36C0A492-9A34-48C3-BD58-B1B81103C083--

From elwynd@dial.pipex.com  Tue Feb 19 13:28:34 2013
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 C251921F88D8 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 13:28:34 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7vlT2HrQ6es for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 13:28:32 -0800 (PST)
Received: from 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 6CA5D21F888A for <gen-art@ietf.org>; Tue, 19 Feb 2013 13:28:30 -0800 (PST)
Received: from mightyatom.folly.org.uk ([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 1U7ujb-00012i-AP; Tue, 19 Feb 2013 21:28:21 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: "Jon Mitchell (GNS)" <Jon.Mitchell@microsoft.com>
In-Reply-To: <4f5ed402038544d0b1da25226424e60b@DFM-DB3MBX15-08.exchange.corp.microsoft.com>
References: <511DFCAD.6020509@dial.pipex.com> <f1195a2f3468441d85edaf0b8b843bba@DFM-DB3MBX15-08.exchange.corp.microsoft.com> <1361236326.4494.891.camel@mightyatom> <4f5ed402038544d0b1da25226424e60b@DFM-DB3MBX15-08.exchange.corp.microsoft.com>
Content-Type: text/plain
Date: Tue, 19 Feb 2013 21:27:49 +0000
Message-Id: <1361309269.4494.986.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-idr-as-private-reservation.all@tools.ietf.org" <draft-ietf-idr-as-private-reservation.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-idr-as-private-reservation-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: Tue, 19 Feb 2013 21:28:35 -0000

Hi, Jon.

On Tue, 2013-02-19 at 20:26 +0000, Jon Mitchell (GNS) wrote:
> Elwyn -
> 
> Yes, I agree this is a reasonable change to remove all of the
> "suggestion" text in the IANA considerations area and will make sure
> it is in the next draft if one is required, either way all of that
> text will be removed by IANA, who has also just sent back their review
> of the actions required.
Seems like we are all agreed where things need to go here. Good!
> 
> On your second comment, currently being published as an RFC is a draft
> reserving as0 in a similar fashion, so I do think it's most
> appropriate as a second doc.. 
Yeh.. I know, I was also gen-art reviewer for that one. Probably too
late to squeeze it in there .. and it wouldn't have been much more
sensible there either.

> and I really have trouble tying these reservations to a RFC about
> Private ASN's.   If no doc is published, the good news is that IANA
> has already reserved the last number (with no justification).  Again,
> if IESG or others feel strongly it should be in this draft, I will try
> to work out some text to justify their reservations...
Oh, well it looks as if somebody ought to spend a merry evening cobbling
together a two section draft to reserve the top number for the sake of
completeness.

Regards,
Elwyn
> 
> Thanks!
> 
> Jon
> 
> -----Original Message-----
> From: Elwyn Davies [mailto:elwynd@dial.pipex.com] 
> Sent: Monday, February 18, 2013 8:12 PM
> To: Jon Mitchell (GNS)
> Cc: General Area Review Team; draft-ietf-idr-as-private-reservation.all@tools.ietf.org
> Subject: RE: Gen-art last call review of draft-ietf-idr-as-private-reservation-03
> 
> On Mon, 2013-02-18 at 15:26 +0000, Jon Mitchell (GNS) wrote:
> > Elwyn -
> > 
> > Thanks for your review. 
> :-)
> 
> >  The suggestion is being made to IANA who owns the assignment and was 
> > discussed at length in the working group with rough consensus.
> As specified in the registry, allocations in this registry are either by IETF Concensus (i.e. a suitable RFC such as this draft is intended to
> be) or request from a RIR. Thus it isn't a matter of suggesting to IANA but telling them what the IETF want done - so this draft should be definitive - and what you said about WG concensus constitutes the values to be used unless somebody else in the IETF manages to alter the concensus which seems unlikely.
>   
> > IANA will replace the suggested values into TBDX values below that 
> > text if IESG approves.  This text will not be in the RFC, it's to be 
> > stricken from the final document by RFC Editor (I was attempting to 
> > write this text in alignment with Section 5.1 of RFC 5226) .
> Yes, that's fine and as expected.
> > 
> > On the final ASN in the range, this is in accordance with like 
> > reservation of the existing 2 byte Private ASN reservations, where the 
> > final ASN in that space is not utilized either (except for well-known 
> > community values).  Also, a case was made that code implementations 
> > tend to have issues with final number usage if using incorrect 
> > variable types for storage.  That said, the small discussion on and 
> > off list about this resolved that if we wanted to formalize the 
> > reservation of the last ASN of both the 2 byte space 65535 and the 4 
> > byte space 4294967295, probably a separate draft should be constructed 
> > detailing the logic behind these as they have nothing to do with 
> > Private ASN's per se and have already been marked as Reserved by IANA 
> > as you noted.  I'm open to IESG direction if we want to take a 
> > different approach on this...
> Publishing a separate draft seems a bit overkill but clearly that's not my decision. ;-)
> 
> Regards,
> Elwyn
> > 
> > Cheers,
> > 
> > Jon
> > 
> > -----Original Message-----
> > From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
> > Sent: Friday, February 15, 2013 4:15 AM
> > To: General Area Review Team
> > Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org
> > Subject: Gen-art last call review of 
> > draft-ietf-idr-as-private-reservation-03
> > 
> > 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-as-private-reservation-03.txt
> > Reviewer: Elwyn Davies
> > Review Date: 15 February 2013
> > IETF LC End Date: 22 February 2013
> > IESG Telechat date: (if known) -
> > 
> > Summary: Ready for the IESG.
> > 
> > Nits/editorial comments:  The draft is not actually definitive about range of values to be allocated - the range in s10 is just a 'suggestion'.  Who is actually making the decision about the range?
> > 
> > Aside: I noted that the highest possible 32 bit number (4294967295 =
> > 0xFFFFFFFF) is excluded from the proposed range.  This is marked as 
> > reserved in the IANA table but AFAICS this reserved item does not have 
> > a specification associated with the reservation.  This document would 
> > be an opportunity to explicitly mention that the topmost value is 
> > reserved (for future expansion? :-) )
> > 
> > 
> 


From wassim.haddad@ericsson.com  Tue Feb 19 14:54:11 2013
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 8741621F88EA for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 14:54:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.001
X-Spam-Level: 
X-Spam-Status: No, score=-102.001 tagged_above=-999 required=5 tests=[AWL=0.597, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8xU5aHi6D2sS for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 14:54:01 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 555CB21F88DB for <gen-art@ietf.org>; Tue, 19 Feb 2013 14:54:01 -0800 (PST)
X-AuditID: c6180641-b7f926d000000e79-de-512402887c02
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E8.D8.03705.88204215; Tue, 19 Feb 2013 23:54:00 +0100 (CET)
Received: from eusaamw0707.eamcs.ericsson.se (147.117.20.32) by EUSAAHC007.ericsson.se (147.117.188.93) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 19 Feb 2013 17:53:57 -0500
Received: from eusjgala119.dyn.sj.us.am.ericsson.se (147.117.20.214) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.3.279.1; Tue, 19 Feb 2013 17:53:57 -0500
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_702EE7A0-891C-4A20-9E90-51A15BA4D621"
Date: Tue, 19 Feb 2013 14:53:59 -0800
Message-ID: <BB2659D2-2AEB-4986-8A0E-CF5ABE778E1C@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
MIME-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprILMWRmVeSWpSXmKPExsUyuXRPrG4Hk0qgwdfbshb7r39itLj66jOL A5PHkiU/mTy2bF7MHMAUxWWTkpqTWZZapG+XwJWxbv0PloIW/oq/v14wNzDO5O1i5OSQEDCR mHXhBTuELSZx4d56ti5GLg4hgSOMEqeW34ZydjNKvD6+ngXCOcQosavlDgtIC5uAgcTX5WdZ QWxmgSSJriW72EBsYQEfiXc3lzKD2CwCqhJzWo6BxXkF7CUu/Wtlh6gvkLh/rQusRkRAU2Lu irdMXYwcQDV6Eqt6mSEukpVYMbWXCcQWElCXmHJrAssERv5ZSLbNQuiACGtLLFv4GsrWkViw +xMbpri2xJkDj5kWMLKtYuQoLU4ty003MtzECAzWYxJsjjsYF3yyPMQozcGiJM4b6nohQEgg PbEkNTs1tSC1KL6oNCe1+BAjEwenVAMjk1eHqv0kxZKkI5L79oedmnmvtOu+9O+KFe8PTt63 wX6b/DV3L3VBq6gFWQ8PMum+8hLqO8NSsnW1+d/nKYGrcoSuXZwcVn9lzbyLV/d3ijbXNIYF Br5/EOA4wTp9XdmTBSmHdoVr2a6N/cYoMmeJcOozfR8WzqlzVs5Pjqjv2BjX/GbjP2s2JZbi jERDLeai4kQAWbpc/yQCAAA=
Cc: draft-ietf-xrblock-rtcp-xr-summary-stat.all@tools.ietf.orgdi
Subject: [Gen-art] Gen-ART Review of draft-ietf-xrblock-rtcp-xr-summary-stat
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 Feb 2013 22:54:13 -0000

--Apple-Mail=_702EE7A0-891C-4A20-9E90-51A15BA4D621
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"

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

Document: draft-ietf-xrblock-rtcp-xr-summary-stat-08
Reviewer:  Wassim Haddad
Review Date: 19 Feb 2013
IETF LC End Date: 01 Feb 2013
IETF Telechat Date: 21 Feb 2013

Summary:  This draft is ready for publication as proposed standard.

- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.


--Apple-Mail=_702EE7A0-891C-4A20-9E90-51A15BA4D621
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="us-ascii"

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><pre =
style=3D"word-wrap: break-word; white-space: pre-wrap; "><div =
style=3D"font-family: Helvetica; white-space: normal; ">I am the =
assigned Gen-ART reviewer for this draft. For background on =
Gen-ART,&nbsp;<br>please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;<br><br>Document:&nb=
sp;draft-ietf-xrblock-rtcp-xr-summary-stat-08<br>Reviewer: &nbsp;Wassim =
Haddad<br>Review Date: 19 Feb 2013<br>IETF LC End Date: 01 Feb =
2013<br>IETF Telechat Date: 21 Feb 2013<br><br>Summary: &nbsp;This draft =
is ready for publication as proposed standard.</div><div =
style=3D"font-family: Helvetica; white-space: normal; "><br>- Major =
Issues: None<br><br>- Minor Issues: =
None<br><br><br>Regards,<br><br>Wassim =
H.</div><div><br></div></pre></body></html>=

--Apple-Mail=_702EE7A0-891C-4A20-9E90-51A15BA4D621--

From wassim.haddad@ericsson.com  Tue Feb 19 14:58:07 2013
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 BF7DF21E8037 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 14:58:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.2
X-Spam-Level: 
X-Spam-Status: No, score=-102.2 tagged_above=-999 required=5 tests=[AWL=0.398,  BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FzxS5wvujJGY for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 14:58:07 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 9007321E80A7 for <gen-art@ietf.org>; Tue, 19 Feb 2013 14:57:51 -0800 (PST)
X-AuditID: c6180641-b7f926d000000e79-bd-5124036e72a6
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 1C.09.03705.E6304215; Tue, 19 Feb 2013 23:57:51 +0100 (CET)
Received: from eusaamw0706.eamcs.ericsson.se (147.117.20.31) by EUSAAHC007.ericsson.se (147.117.188.93) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 19 Feb 2013 17:57:50 -0500
Received: from eusjgala119.dyn.sj.us.am.ericsson.se (147.117.20.214) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.3.279.1; Tue, 19 Feb 2013 17:57:50 -0500
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DD42D6FF-345E-44EA-B91A-EDF5E550EF02"
Date: Tue, 19 Feb 2013 14:57:52 -0800
Message-ID: <BB028913-19A7-49A8-B1CA-B02F216E093A@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
MIME-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprALMWRmVeSWpSXmKPExsUyuXRPrG4+s0qgQX8Pq8XdSa+YLa6++szi wOSxZMlPJo8vlz+zBTBFcdmkpOZklqUW6dslcGV0nH7MWNAkVrFvyw6mBsa1wl2MnBwSAiYS 23+8Y4awxSQu3FvP1sXIxSEkcIRRYvPMpawgCSGB3YwSew75QCQOMUpMu97PBJJgEzCQ+Lr8 LFgRs0CSRNOSNWBxYQEfiXc3l4JNZRFQlWhavIodxOYVsJdYt7GdGaI+T+Jk2zmwehEBTYm5 K94C2RxANXoSq3qhDpKVWDG1lwniBnWJKbcmsExg5J+FZNsshA6IsLbEsoWvoWwdiQW7P7Fh imtLnDnwmGkBI9sqRo7S4tSy3HQjw02MwFA9JsHmuINxwSfLQ4zSHCxK4ryhrhcChATSE0tS s1NTC1KL4otKc1KLDzEycXBKNTDaeKxZurqv+eB24SqOC2v2ZB5k9GsITJHOs+9SYrywN/+M 6KWtBrOKWN78Ebier65Wop936M4XW70Dfzhrnky9X37ojtNSreWcKnJCoYXfHFMZjsyOPnpN cfvqkg+xrz6+Wtan/dXlzw1L49bZE76Gx4oy8wrMmVDFs+pk3VKuLZxGa+vV5u1WYinOSDTU Yi4qTgQA50dvPiMCAAA=
Cc: draft-ietf-xrblock-rtcp-xr-summary-stat.all@tools.ietf.org
Subject: [Gen-art] Gen-ART Review of draft-ietf-xrblock-rtcp-xr-summary-stat
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 Feb 2013 22:58:07 -0000

--Apple-Mail=_DD42D6FF-345E-44EA-B91A-EDF5E550EF02
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"

Sorry for the typo! Re-sending!


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

Document: draft-ietf-xrblock-rtcp-xr-summary-stat-08
Reviewer:  Wassim Haddad
Review Date: 19 Feb 2013
IETF LC End Date: 01 Feb 2013
IETF Telechat Date: 21 Feb 2013

Summary:  This draft is ready for publication as proposed standard.

- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.





--Apple-Mail=_DD42D6FF-345E-44EA-B91A-EDF5E550EF02
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="us-ascii"

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><pre =
style=3D"word-wrap: break-word; white-space: pre-wrap; "><div =
style=3D"font-family: Helvetica; white-space: normal; ">Sorry for the =
typo! Re-sending!</div><div style=3D"font-family: Helvetica; =
white-space: normal; "><br></div><div style=3D"font-family: Helvetica; =
white-space: normal; "><br></div><div style=3D"font-family: Helvetica; =
white-space: normal; ">I am the assigned Gen-ART reviewer for this =
draft. For background on Gen-ART,&nbsp;<br>please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;<br><br>Document:&nb=
sp;draft-ietf-xrblock-rtcp-xr-summary-stat-08<br>Reviewer: &nbsp;Wassim =
Haddad<br>Review Date: 19 Feb 2013<br>IETF LC End Date: 01 Feb =
2013<br>IETF Telechat Date: 21 Feb 2013<br><br>Summary: &nbsp;This draft =
is ready for publication as proposed standard.</div><div =
style=3D"font-family: Helvetica; white-space: normal; "><br>- Major =
Issues: None<br><br>- Minor Issues: =
None<br><br><br>Regards,<br><br>Wassim H.</div></pre><div><br></div><div =
apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
medium; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div></div><br class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_DD42D6FF-345E-44EA-B91A-EDF5E550EF02--

From mary.ietf.barnes@gmail.com  Tue Feb 19 16:06:36 2013
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 9B16D21F87A5 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 16:06:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.582
X-Spam-Level: 
X-Spam-Status: No, score=-103.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hNLFDTiprv8v for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 16:06:35 -0800 (PST)
Received: from mail-qa0-f53.google.com (mail-qa0-f53.google.com [209.85.216.53]) by ietfa.amsl.com (Postfix) with ESMTP id 4A33321F8750 for <gen-art@ietf.org>; Tue, 19 Feb 2013 16:06:35 -0800 (PST)
Received: by mail-qa0-f53.google.com with SMTP id z4so2147865qan.5 for <gen-art@ietf.org>; Tue, 19 Feb 2013 16:06:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=ngRjyPl+NoLi2uqCEmEgHz7ZssHudCulXMHjWL8r0Ls=; b=Khh7ACnQ6bedg5V/rHkq7VXJWMWj2aZRhE/SMr3CmBDpXnDrCaPHiO8mniyQXUVOeE DTkI54mExVFAeqh2RVqjq/FWM8KLZgjsr2UtPB0bSD0Dyong9Ez7kaP0SXaa7JGhXPIH bzcJLsnyTcDI2eabn+7nIGREj5GnrZiEVZv66ngTevrrdcGS+O9vvJSsyBGll5a/LdHQ 5YoZpRxpCBor61WTsMewMnS/0gaDCYsM889SR3U7kKqnObdV/7i0nu3m7wNKSZKc/hJ7 ouHOgUucJ1nL9PIHikifJkgNbXw0hwx0L7N3Yq60ATRcSUf/LqPD1rAPjBkNFDwP/n1e lVLA==
MIME-Version: 1.0
X-Received: by 10.224.174.80 with SMTP id s16mr6535540qaz.85.1361318794717; Tue, 19 Feb 2013 16:06:34 -0800 (PST)
Received: by 10.49.131.199 with HTTP; Tue, 19 Feb 2013 16:06:34 -0800 (PST)
Date: Tue, 19 Feb 2013 18:06:34 -0600
Message-ID: <CAHBDyN6-J6SgnNqA1ZTcnFsLGzaeD2wGD5W58rte3A-vn2SQiA@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-p2psip-base.all@tools.ietf.org,  Marc Petit-Huguenin <marc@petit-huguenin.org>, Dean Willis <dean.willis@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART LC Review: draft-ietf-p2psip-base-24
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 Feb 2013 00:06:36 -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>.


Document: draft-ietf-p2psip-base-24
Reviewer:  Mary Barnes
Review Date: 19 February 2013
Previous Review Date (-23): 14 December 2012
Original Review Date (-17): 6 August 2011
IETF LC End Date: 22 July 2011
IETF 2nd LC End Date: 19 February 2013

Summary: Almost Ready.  This version is in significantly better shape
than the previous versions.

Comments:
=========
I reviewed against my review of the -23 up through section 6.  I
reviewed beyond section 6 of this version (section 5 of -17, section 6
of -23) against my comments on the -17, since I had not re-reviewed
those against the -23.


General:
--------

I still *strongly* recommend that you ensure Henning has reviewed this
document *before* it gets into the RFC editor's queue.  The last RFC I
had published with Henning as a co-author had much more extensive
changes suggested during AUTH 48 than I found acceptable. If all the
co-authors have not reviewed and approved the draft before it goes
into the RFC editor's queue, then the document should not go into the
RFC editor's queue. He has fairly strict (and quite accurate) views on
grammar and structure but it really isn't good to have so many changes
go in at AUTH48 as there is a risk of introducing true technical bugs
or changing something that was carefully crafted to achieve WG
consensus:
http://www.cs.columbia.edu/~hgs/etc/writing-bugs.html
Note, that there some are cases of incorrect grammar that I have not
identified because I think the RFC editor can fix, however, Henning
may have different views on this.


Major:
------
- [-17, section 10.5] Section 11.5, 3rd para:  text uses the phrase
"it can note the Node-ID in the response and use this Node-ID to start
sending requests".  It's not clear whether the use of the Node-ID is a
MAY or a MUST.    [Note: Marc's response to this was that it's an open
issue, but this should be clarified prior to publication].

Minor:
------
- idnits identifies 5 errors (downrefs).  I will note that in the
PROTO write-up it was noted that those should likely be moved to
Informative.

- [-17] Section 1.2.1, 2nd paragraph: I don't understand the example
as to why a single application requires multiple usages - i.e, why
voicemail?  Isn't the intent to say that an application might need to
use both SIP and XMPP - i.e., you wouldn't define a "usage" for an
application, would you?
[While Cullen responded to this comment with an explanation, there was
no change to clarify the text and Marc's response didn't help clarify
my concern]

- Section 3.3, 2nd paragraph after the capability bullet list, next to
last sentence.  There is at least an article missing from this
sentence and it reads rather awkwardly. Perhaps changing to something
like:
OLD:
   If there is a failure on
   the reverse path caused by topology change since the request was
   sent, this will be handled by the end-to-end retransmission of the
   response as described in Section 6.2.1.
NEW:
   Note that a failure on
   the reverse path caused by a topology change after the request was
   sent, will be handled by the end-to-end retransmission of the
   response as described in Section 6.2.1.

- [-17] Section 3.3, last paragraph.  Add a reference to 5.4.2.4
after "RouteQuery method"

- Section 3.4, last paragraph, 3rd sentence: "that the specified by
the algorithm" should be something like "than specified by the
algorithm".

- [-23] Section 6.6:  All my previous concerns were addressed, except,
the Note to implementors paragraph still seems out of context - it
should be deleted or this section should be restructured so it is in
context.

- [-17, section 11] Section 12, Second paragraph, 3rd sentence
says that "It gets routed to the admitting peer (AP), yet the flow
shows that the message first gets routed to the PP and then onto AP.
It would be helpful if that were clarified.   [Note: Marc's response
indicated that he thought this was fixed in the -23, however, the diff
shows no changes to that specific text between the -17 and the -24 ]


Nits:
-----

- Section 1.2.5, 2nd para, last sentence: this sentence is a bit tough
to interpret on a first read.  I would suggest rewording something
like the following:
OLD:
  This layer is to the Message Transport Layer as link-
   level congestion control and retransmission in modern wireless
   networks is to Internet transport protocols.
NEW:
   The relation of this layer to the Message Transport Layer
   "is similar to"|"can be likened to" the relation of the link-
   level congestion control and retransmission in modern wireless
   networks to Internet transport protocols.

- Section 3.4, last paragraph, 4th sentence: "in accord" -> "in accordance"

- Section 10.1, 2nd paragraph, 5th sentence: "can be thought of a
doubly-linked list" -> "can be thought of as a doubly-linked list"

- Section 15, last paragraph: "help resolve" -> "helped resolve"

From marc@petit-huguenin.org  Tue Feb 19 16:16:43 2013
Return-Path: <marc@petit-huguenin.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 1777C21F886B for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 16:16:43 -0800 (PST)
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, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wrBHuAr3+0eJ for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 16:16:39 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id D234E21F8830 for <gen-art@ietf.org>; Tue, 19 Feb 2013 16:16:38 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:b500:ef19:52a7:2e46] (unknown [IPv6:2601:9:4b80:32:b500:ef19:52a7:2e46]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id B5C9B201F3; Wed, 20 Feb 2013 00:16:36 +0000 (UTC)
Message-ID: <512415E5.1060702@petit-huguenin.org>
Date: Tue, 19 Feb 2013 16:16:37 -0800
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
References: <CAHBDyN6-J6SgnNqA1ZTcnFsLGzaeD2wGD5W58rte3A-vn2SQiA@mail.gmail.com>
In-Reply-To: <CAHBDyN6-J6SgnNqA1ZTcnFsLGzaeD2wGD5W58rte3A-vn2SQiA@mail.gmail.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 19 Feb 2013 17:50:27 -0800
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-p2psip-base.all@tools.ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Gen-art] Gen-ART LC Review: draft-ietf-p2psip-base-24
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 Feb 2013 00:16:43 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Thanks Mary.  I start working on this immediately.

On 02/19/2013 04:06 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-p2psip-base-24 Reviewer:  Mary Barnes Review Date: 19
> February 2013 Previous Review Date (-23): 14 December 2012 Original Review
> Date (-17): 6 August 2011 IETF LC End Date: 22 July 2011 IETF 2nd LC End
> Date: 19 February 2013
> 
> Summary: Almost Ready.  This version is in significantly better shape than
> the previous versions.
> 
> Comments: ========= I reviewed against my review of the -23 up through
> section 6.  I reviewed beyond section 6 of this version (section 5 of -17,
> section 6 of -23) against my comments on the -17, since I had not
> re-reviewed those against the -23.
> 
> 
> General: --------
> 
> I still *strongly* recommend that you ensure Henning has reviewed this 
> document *before* it gets into the RFC editor's queue.  The last RFC I had
> published with Henning as a co-author had much more extensive changes
> suggested during AUTH 48 than I found acceptable. If all the co-authors
> have not reviewed and approved the draft before it goes into the RFC
> editor's queue, then the document should not go into the RFC editor's
> queue. He has fairly strict (and quite accurate) views on grammar and
> structure but it really isn't good to have so many changes go in at AUTH48
> as there is a risk of introducing true technical bugs or changing something
> that was carefully crafted to achieve WG consensus: 
> http://www.cs.columbia.edu/~hgs/etc/writing-bugs.html Note, that there some
> are cases of incorrect grammar that I have not identified because I think
> the RFC editor can fix, however, Henning may have different views on this.
> 
> 
> Major: ------ - [-17, section 10.5] Section 11.5, 3rd para:  text uses the
> phrase "it can note the Node-ID in the response and use this Node-ID to
> start sending requests".  It's not clear whether the use of the Node-ID is
> a MAY or a MUST.    [Note: Marc's response to this was that it's an open 
> issue, but this should be clarified prior to publication].
> 
> Minor: ------ - idnits identifies 5 errors (downrefs).  I will note that in
> the PROTO write-up it was noted that those should likely be moved to 
> Informative.
> 
> - [-17] Section 1.2.1, 2nd paragraph: I don't understand the example as to
> why a single application requires multiple usages - i.e, why voicemail?
> Isn't the intent to say that an application might need to use both SIP and
> XMPP - i.e., you wouldn't define a "usage" for an application, would you? 
> [While Cullen responded to this comment with an explanation, there was no
> change to clarify the text and Marc's response didn't help clarify my
> concern]
> 
> - Section 3.3, 2nd paragraph after the capability bullet list, next to last
> sentence.  There is at least an article missing from this sentence and it
> reads rather awkwardly. Perhaps changing to something like: OLD: If there
> is a failure on the reverse path caused by topology change since the
> request was sent, this will be handled by the end-to-end retransmission of
> the response as described in Section 6.2.1. NEW: Note that a failure on the
> reverse path caused by a topology change after the request was sent, will
> be handled by the end-to-end retransmission of the response as described in
> Section 6.2.1.
> 
> - [-17] Section 3.3, last paragraph.  Add a reference to 5.4.2.4 after
> "RouteQuery method"
> 
> - Section 3.4, last paragraph, 3rd sentence: "that the specified by the
> algorithm" should be something like "than specified by the algorithm".
> 
> - [-23] Section 6.6:  All my previous concerns were addressed, except, the
> Note to implementors paragraph still seems out of context - it should be
> deleted or this section should be restructured so it is in context.
> 
> - [-17, section 11] Section 12, Second paragraph, 3rd sentence says that
> "It gets routed to the admitting peer (AP), yet the flow shows that the
> message first gets routed to the PP and then onto AP. It would be helpful
> if that were clarified.   [Note: Marc's response indicated that he thought
> this was fixed in the -23, however, the diff shows no changes to that
> specific text between the -17 and the -24 ]
> 
> 
> Nits: -----
> 
> - Section 1.2.5, 2nd para, last sentence: this sentence is a bit tough to
> interpret on a first read.  I would suggest rewording something like the
> following: OLD: This layer is to the Message Transport Layer as link- level
> congestion control and retransmission in modern wireless networks is to
> Internet transport protocols. NEW: The relation of this layer to the
> Message Transport Layer "is similar to"|"can be likened to" the relation of
> the link- level congestion control and retransmission in modern wireless 
> networks to Internet transport protocols.
> 
> - Section 3.4, last paragraph, 4th sentence: "in accord" -> "in
> accordance"
> 
> - Section 10.1, 2nd paragraph, 5th sentence: "can be thought of a 
> doubly-linked list" -> "can be thought of as a doubly-linked list"
> 
> - Section 15, last paragraph: "help resolve" -> "helped resolve"
> 


- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRJBXhAAoJECnERZXWan7EArsP/1Jwo7XD8sRHgFFNyw6hCLZB
c7ovMWrpJgM+EENmFq9pkTIQLLE/E3BAGzCsXZ3xoSPkemhUmxWFkGheuWQowzeP
ShoE8OcB6C/RIgqpkNuZfCnmvhBv5he1nsDj8RJ3e7YDkjpBixLK+x0EFncJVaWs
PF77UIEOaddq4R5WYtfovxOeRYS8z00JQfM8JBOHdSHKkNr1IvlJMVKgmtO3gQHH
1JS+O44pljkXrB8okLoEhDPjYaDMM08PE2HIbOyu6aaFPgBe7E1cNeniyoG0w0Sf
hMkpJiAxLoLuEWMfkpWrHXNGK76EDDnCbGK5Xpi9EpsPHHCjVgZxB6AfuunRB+we
RA2PPqTV1Fa9ZkSSO+wbm3n2dUALp1bOq4LGgL3vjsWg+ePiTIynHaemHFTgOEMU
xnQdA3At/Du+GkRqatuKn7dTegNw+tvXS2WAytscHvJ2X4pj8yOl6c/NNtDeEduN
jfB8RclXB5srMALfmHFr6I8CsfGRpuRTES1DkaNaiWJRhqI7G8QYhJitpJwwneKd
PQI2pnNYBpY+4sVjl6xJb9ynBlmaDOTdnfhmWj2QeRxnqZQxGTdnoBOHolfKYIV6
R8BjiEoJKPSLwuxpWBxDvIJUoxMPNkndSAbkpqawsMQvIptmlG5R4vL92ljTthhH
OTgyQ3TUjCf9D/4FO5AQ
=UxzS
-----END PGP SIGNATURE-----

From mccap@petoni.org  Tue Feb 19 20:05:19 2013
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 45B5021F8855 for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 20:05:19 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZCy3JYnAIcnu for <gen-art@ietfa.amsl.com>; Tue, 19 Feb 2013 20:05:18 -0800 (PST)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by ietfa.amsl.com (Postfix) with ESMTP id A364C21F8806 for <gen-art@ietf.org>; Tue, 19 Feb 2013 20:05:18 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id hz1so3791713pad.24 for <gen-art@ietf.org>; Tue, 19 Feb 2013 20:05:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type; bh=9LF69DmMm/BvanEjuzLTdEcCFfQOiYOAP86+a0DvQnw=; b=GUklsVdWxptIiHuoEngCuYhDOTcQfRt9CKm+nO0+leW7f8yuoo9t5FY4Q8Nb8rqdGZ QsT/6PgKt2D5s/W8CRO9oX+mbJxjJ/Ql4giClYO1hPN7EujKDNm0EPnfeq/D8xgniK/y F1o5zt3k6sYxvRkYMU+fCscmJ4QejSiqf59wc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type:x-gm-message-state; bh=9LF69DmMm/BvanEjuzLTdEcCFfQOiYOAP86+a0DvQnw=; b=TK3og2APQjlrvZgr+mKYT+UnQdFtj0SP7X1yVjU06Mqr980Ci1PKxqz/CuQ54geGh7 QIAMgnBUsHetPHP8Adxwb+DDiPpyx2eZbt2/vX/YZoMxbbksGxJklNTgY/jCoxEpOCWn MSWFpkvgQiiT2uevdTKI55O0YcsZySl8lLRWmcbu7oKT2ajm9j8yIV9nIcn5NCsHtkLX SAJmkYBQBUMAjrxVABg4HQXV9Rrcq2vxhxX+UIEmYA92WQC79daqRQdnsRQE3WqrT6I+ AI+CegkYpCXwB9X1gk7SkdeHhbjMi1ST9y7mBByLqQPSXWZpxoy9j8alV/pOOuSk2P9P ADqw==
MIME-Version: 1.0
X-Received: by 10.66.222.35 with SMTP id qj3mr51426913pac.69.1361333118244; Tue, 19 Feb 2013 20:05:18 -0800 (PST)
Received: by 10.68.17.164 with HTTP; Tue, 19 Feb 2013 20:05:18 -0800 (PST)
X-Originating-IP: [68.45.157.93]
Date: Tue, 19 Feb 2013 23:05:18 -0500
Message-ID: <CACvMsLHd16wn4w0UyT0deg5M+kx4orszX3uGqiU98KfYW0sboA@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-templin-ironbis.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnJUp5UQxQ9QLRO9NQ7BRB4e5H0vmc1+Sy0M+gJHuNE6WM0tXo2Z1kBSrFsVzJrj+OvBSJJ
Subject: [Gen-art] Gen-ART Telechat Review of draft-templin-ironbis-12
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 Feb 2013 04:05: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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:  draft-templin-ironbis-12
Reviewer:  Peter McCann
Review Date: 2013-02-19
IETF LC End Date: 2013-02-18
IESG Telechat date: 2013-02-21

Summary:  Ready

Major issues:  none

Minor issues:  none

Nits/editorial comments:

The draft is well-written and the ideas are clearly explained. I think
it represents an important contribution to the route scaling/mobility
management/multihoming problem space.

From br@brianrosen.net  Wed Feb 20 06:20:46 2013
Return-Path: <br@brianrosen.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 7A03E21F87B1 for <gen-art@ietfa.amsl.com>; Wed, 20 Feb 2013 06:20:46 -0800 (PST)
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=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FauEB95eLCnX for <gen-art@ietfa.amsl.com>; Wed, 20 Feb 2013 06:20:45 -0800 (PST)
Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com [209.85.220.178]) by ietfa.amsl.com (Postfix) with ESMTP id 1A60E21F8780 for <gen-art@ietf.org>; Wed, 20 Feb 2013 06:20:45 -0800 (PST)
Received: by mail-vc0-f178.google.com with SMTP id m8so5076781vcd.9 for <gen-art@ietf.org>; Wed, 20 Feb 2013 06:20:44 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=UCULI51f612l+WiWCb1QipNFmNbhRh/Su9RNgeGLlG0=; b=TngZfDjsDym66zhOACO8OoSGTe8i4wJISMuESGLbOdSs2kMOFMReNWmz+D76aLOUZM LirHMne6bBiW8Ug0+DYqOZR+q9et5+URrVyOiZyZmjagqyv+9PbFKDXUjKzhmBYNQbo2 3yyQU4KAyj55toQmCV/B18eom8svlPbKO000rlPNs3Q5WUgrX+QnYm2jX0sogJ7QlMJb obqZlElrQQe+7pMqQaMxIFP2IMb+jLT57miI2Lch30iiJqJT7IHMxnD098AIQiSfDkZt 9w66G+apdtAaFjjCuo+1aIdpZDKvJIyMxMZqMi3xpd6eODguwPyUeZ/cRGyLZJVUhFAa CntA==
X-Received: by 10.59.9.201 with SMTP id du9mr26801666ved.38.1361370044442; Wed, 20 Feb 2013 06:20:44 -0800 (PST)
Received: from [192.168.133.32] (neustargw.va.neustar.com. [209.173.53.233]) by mx.google.com with ESMTPS id yu12sm91091521vec.6.2013.02.20.06.20.42 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 Feb 2013 06:20:43 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <512415E5.1060702@petit-huguenin.org>
Date: Wed, 20 Feb 2013 09:20:40 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D82BACC-F763-4A4F-9E3C-61AACB3FB440@brianrosen.net>
References: <CAHBDyN6-J6SgnNqA1ZTcnFsLGzaeD2wGD5W58rte3A-vn2SQiA@mail.gmail.com> <512415E5.1060702@petit-huguenin.org>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQl7S0SWeLcPqeZ2lTifrvdiQnMhvOUSUPCyDN/SK2zKhOFdFIy0sVN5etA4fIGTKz2nf+8b
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-p2psip-base.all@tools.ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Gen-art] Gen-ART LC Review: draft-ietf-p2psip-base-24
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 Feb 2013 14:20:46 -0000

I will contact Henning

Brian

On Feb 19, 2013, at 7:16 PM, Marc Petit-Huguenin =
<marc@petit-huguenin.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>=20
> Thanks Mary.  I start working on this immediately.
>=20
> On 02/19/2013 04:06 PM, Mary Barnes wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on=20=

>> Gen-ART, please see the FAQ at=20
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>>=20
>> Document: draft-ietf-p2psip-base-24 Reviewer:  Mary Barnes Review =
Date: 19
>> February 2013 Previous Review Date (-23): 14 December 2012 Original =
Review
>> Date (-17): 6 August 2011 IETF LC End Date: 22 July 2011 IETF 2nd LC =
End
>> Date: 19 February 2013
>>=20
>> Summary: Almost Ready.  This version is in significantly better shape =
than
>> the previous versions.
>>=20
>> Comments: =3D=3D=3D=3D=3D=3D=3D=3D=3D I reviewed against my review of =
the -23 up through
>> section 6.  I reviewed beyond section 6 of this version (section 5 of =
-17,
>> section 6 of -23) against my comments on the -17, since I had not
>> re-reviewed those against the -23.
>>=20
>>=20
>> General: --------
>>=20
>> I still *strongly* recommend that you ensure Henning has reviewed =
this=20
>> document *before* it gets into the RFC editor's queue.  The last RFC =
I had
>> published with Henning as a co-author had much more extensive changes
>> suggested during AUTH 48 than I found acceptable. If all the =
co-authors
>> have not reviewed and approved the draft before it goes into the RFC
>> editor's queue, then the document should not go into the RFC editor's
>> queue. He has fairly strict (and quite accurate) views on grammar and
>> structure but it really isn't good to have so many changes go in at =
AUTH48
>> as there is a risk of introducing true technical bugs or changing =
something
>> that was carefully crafted to achieve WG consensus:=20
>> http://www.cs.columbia.edu/~hgs/etc/writing-bugs.html Note, that =
there some
>> are cases of incorrect grammar that I have not identified because I =
think
>> the RFC editor can fix, however, Henning may have different views on =
this.
>>=20
>>=20
>> Major: ------ - [-17, section 10.5] Section 11.5, 3rd para:  text =
uses the
>> phrase "it can note the Node-ID in the response and use this Node-ID =
to
>> start sending requests".  It's not clear whether the use of the =
Node-ID is
>> a MAY or a MUST.    [Note: Marc's response to this was that it's an =
open=20
>> issue, but this should be clarified prior to publication].
>>=20
>> Minor: ------ - idnits identifies 5 errors (downrefs).  I will note =
that in
>> the PROTO write-up it was noted that those should likely be moved to=20=

>> Informative.
>>=20
>> - [-17] Section 1.2.1, 2nd paragraph: I don't understand the example =
as to
>> why a single application requires multiple usages - i.e, why =
voicemail?
>> Isn't the intent to say that an application might need to use both =
SIP and
>> XMPP - i.e., you wouldn't define a "usage" for an application, would =
you?=20
>> [While Cullen responded to this comment with an explanation, there =
was no
>> change to clarify the text and Marc's response didn't help clarify my
>> concern]
>>=20
>> - Section 3.3, 2nd paragraph after the capability bullet list, next =
to last
>> sentence.  There is at least an article missing from this sentence =
and it
>> reads rather awkwardly. Perhaps changing to something like: OLD: If =
there
>> is a failure on the reverse path caused by topology change since the
>> request was sent, this will be handled by the end-to-end =
retransmission of
>> the response as described in Section 6.2.1. NEW: Note that a failure =
on the
>> reverse path caused by a topology change after the request was sent, =
will
>> be handled by the end-to-end retransmission of the response as =
described in
>> Section 6.2.1.
>>=20
>> - [-17] Section 3.3, last paragraph.  Add a reference to 5.4.2.4 =
after
>> "RouteQuery method"
>>=20
>> - Section 3.4, last paragraph, 3rd sentence: "that the specified by =
the
>> algorithm" should be something like "than specified by the =
algorithm".
>>=20
>> - [-23] Section 6.6:  All my previous concerns were addressed, =
except, the
>> Note to implementors paragraph still seems out of context - it should =
be
>> deleted or this section should be restructured so it is in context.
>>=20
>> - [-17, section 11] Section 12, Second paragraph, 3rd sentence says =
that
>> "It gets routed to the admitting peer (AP), yet the flow shows that =
the
>> message first gets routed to the PP and then onto AP. It would be =
helpful
>> if that were clarified.   [Note: Marc's response indicated that he =
thought
>> this was fixed in the -23, however, the diff shows no changes to that
>> specific text between the -17 and the -24 ]
>>=20
>>=20
>> Nits: -----
>>=20
>> - Section 1.2.5, 2nd para, last sentence: this sentence is a bit =
tough to
>> interpret on a first read.  I would suggest rewording something like =
the
>> following: OLD: This layer is to the Message Transport Layer as link- =
level
>> congestion control and retransmission in modern wireless networks is =
to
>> Internet transport protocols. NEW: The relation of this layer to the
>> Message Transport Layer "is similar to"|"can be likened to" the =
relation of
>> the link- level congestion control and retransmission in modern =
wireless=20
>> networks to Internet transport protocols.
>>=20
>> - Section 3.4, last paragraph, 4th sentence: "in accord" -> "in
>> accordance"
>>=20
>> - Section 10.1, 2nd paragraph, 5th sentence: "can be thought of a=20
>> doubly-linked list" -> "can be thought of as a doubly-linked list"
>>=20
>> - Section 15, last paragraph: "help resolve" -> "helped resolve"
>>=20
>=20
>=20
> - --=20
> Marc Petit-Huguenin
> Email: marc@petit-huguenin.org
> Blog: http://blog.marc.petit-huguenin.org
> Profile: http://www.linkedin.com/in/petithug
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>=20
> iQIcBAEBCAAGBQJRJBXhAAoJECnERZXWan7EArsP/1Jwo7XD8sRHgFFNyw6hCLZB
> c7ovMWrpJgM+EENmFq9pkTIQLLE/E3BAGzCsXZ3xoSPkemhUmxWFkGheuWQowzeP
> ShoE8OcB6C/RIgqpkNuZfCnmvhBv5he1nsDj8RJ3e7YDkjpBixLK+x0EFncJVaWs
> PF77UIEOaddq4R5WYtfovxOeRYS8z00JQfM8JBOHdSHKkNr1IvlJMVKgmtO3gQHH
> 1JS+O44pljkXrB8okLoEhDPjYaDMM08PE2HIbOyu6aaFPgBe7E1cNeniyoG0w0Sf
> hMkpJiAxLoLuEWMfkpWrHXNGK76EDDnCbGK5Xpi9EpsPHHCjVgZxB6AfuunRB+we
> RA2PPqTV1Fa9ZkSSO+wbm3n2dUALp1bOq4LGgL3vjsWg+ePiTIynHaemHFTgOEMU
> xnQdA3At/Du+GkRqatuKn7dTegNw+tvXS2WAytscHvJ2X4pj8yOl6c/NNtDeEduN
> jfB8RclXB5srMALfmHFr6I8CsfGRpuRTES1DkaNaiWJRhqI7G8QYhJitpJwwneKd
> PQI2pnNYBpY+4sVjl6xJb9ynBlmaDOTdnfhmWj2QeRxnqZQxGTdnoBOHolfKYIV6
> R8BjiEoJKPSLwuxpWBxDvIJUoxMPNkndSAbkpqawsMQvIptmlG5R4vL92ljTthhH
> OTgyQ3TUjCf9D/4FO5AQ
> =3DUxzS
> -----END PGP SIGNATURE-----


From marc@petit-huguenin.org  Wed Feb 20 07:14:12 2013
Return-Path: <marc@petit-huguenin.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 8327E21F87FB for <gen-art@ietfa.amsl.com>; Wed, 20 Feb 2013 07:14:12 -0800 (PST)
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, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5BhmBV3wBuKo for <gen-art@ietfa.amsl.com>; Wed, 20 Feb 2013 07:14:11 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 106E721F87FF for <gen-art@ietf.org>; Wed, 20 Feb 2013 07:14:11 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:e444:31b2:26dd:bd] (unknown [IPv6:2601:9:4b80:32:e444:31b2:26dd:bd]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id EF53A201F3; Wed, 20 Feb 2013 15:14:08 +0000 (UTC)
Message-ID: <5124E842.1070201@petit-huguenin.org>
Date: Wed, 20 Feb 2013 07:14:10 -0800
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Brian Rosen <br@brianrosen.net>
References: <CAHBDyN6-J6SgnNqA1ZTcnFsLGzaeD2wGD5W58rte3A-vn2SQiA@mail.gmail.com> <512415E5.1060702@petit-huguenin.org> <1D82BACC-F763-4A4F-9E3C-61AACB3FB440@brianrosen.net>
In-Reply-To: <1D82BACC-F763-4A4F-9E3C-61AACB3FB440@brianrosen.net>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-p2psip-base.all@tools.ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Gen-art] Gen-ART LC Review: draft-ietf-p2psip-base-24
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 Feb 2013 15:14:12 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/20/2013 06:20 AM, Brian Rosen wrote:
> I will contact Henning

I was in the process yesterday evening of doing a review according to the link
Mary send when Roland's review arrived, which basically killed any chance of
doing that.  So either Henning send me today a list of things to fix, or I'll
do the review later, but that probably be after the IESG telechat.

> 
> Brian
> 
> On Feb 19, 2013, at 7:16 PM, Marc Petit-Huguenin <marc@petit-huguenin.org>
> wrote:
> 
> Thanks Mary.  I start working on this immediately.
> 
> On 02/19/2013 04:06 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-p2psip-base-24 Reviewer:  Mary Barnes Review
>>>> Date: 19 February 2013 Previous Review Date (-23): 14 December 2012
>>>> Original Review Date (-17): 6 August 2011 IETF LC End Date: 22 July
>>>> 2011 IETF 2nd LC End Date: 19 February 2013
>>>> 
>>>> Summary: Almost Ready.  This version is in significantly better shape
>>>> than the previous versions.
>>>> 
>>>> Comments: ========= I reviewed against my review of the -23 up
>>>> through section 6.  I reviewed beyond section 6 of this version
>>>> (section 5 of -17, section 6 of -23) against my comments on the -17,
>>>> since I had not re-reviewed those against the -23.
>>>> 
>>>> 
>>>> General: --------
>>>> 
>>>> I still *strongly* recommend that you ensure Henning has reviewed
>>>> this document *before* it gets into the RFC editor's queue.  The last
>>>> RFC I had published with Henning as a co-author had much more
>>>> extensive changes suggested during AUTH 48 than I found acceptable.
>>>> If all the co-authors have not reviewed and approved the draft before
>>>> it goes into the RFC editor's queue, then the document should not go
>>>> into the RFC editor's queue. He has fairly strict (and quite
>>>> accurate) views on grammar and structure but it really isn't good to
>>>> have so many changes go in at AUTH48 as there is a risk of
>>>> introducing true technical bugs or changing something that was
>>>> carefully crafted to achieve WG consensus: 
>>>> http://www.cs.columbia.edu/~hgs/etc/writing-bugs.html Note, that
>>>> there some are cases of incorrect grammar that I have not identified
>>>> because I think the RFC editor can fix, however, Henning may have
>>>> different views on this.
>>>> 
>>>> 
>>>> Major: ------ - [-17, section 10.5] Section 11.5, 3rd para:  text
>>>> uses the phrase "it can note the Node-ID in the response and use this
>>>> Node-ID to start sending requests".  It's not clear whether the use
>>>> of the Node-ID is a MAY or a MUST.    [Note: Marc's response to this
>>>> was that it's an open issue, but this should be clarified prior to
>>>> publication].
>>>> 
>>>> Minor: ------ - idnits identifies 5 errors (downrefs).  I will note
>>>> that in the PROTO write-up it was noted that those should likely be
>>>> moved to Informative.
>>>> 
>>>> - [-17] Section 1.2.1, 2nd paragraph: I don't understand the example
>>>> as to why a single application requires multiple usages - i.e, why
>>>> voicemail? Isn't the intent to say that an application might need to
>>>> use both SIP and XMPP - i.e., you wouldn't define a "usage" for an
>>>> application, would you? [While Cullen responded to this comment with
>>>> an explanation, there was no change to clarify the text and Marc's
>>>> response didn't help clarify my concern]
>>>> 
>>>> - Section 3.3, 2nd paragraph after the capability bullet list, next
>>>> to last sentence.  There is at least an article missing from this
>>>> sentence and it reads rather awkwardly. Perhaps changing to something
>>>> like: OLD: If there is a failure on the reverse path caused by
>>>> topology change since the request was sent, this will be handled by
>>>> the end-to-end retransmission of the response as described in Section
>>>> 6.2.1. NEW: Note that a failure on the reverse path caused by a
>>>> topology change after the request was sent, will be handled by the
>>>> end-to-end retransmission of the response as described in Section
>>>> 6.2.1.
>>>> 
>>>> - [-17] Section 3.3, last paragraph.  Add a reference to 5.4.2.4
>>>> after "RouteQuery method"
>>>> 
>>>> - Section 3.4, last paragraph, 3rd sentence: "that the specified by
>>>> the algorithm" should be something like "than specified by the
>>>> algorithm".
>>>> 
>>>> - [-23] Section 6.6:  All my previous concerns were addressed,
>>>> except, the Note to implementors paragraph still seems out of context
>>>> - it should be deleted or this section should be restructured so it
>>>> is in context.
>>>> 
>>>> - [-17, section 11] Section 12, Second paragraph, 3rd sentence says
>>>> that "It gets routed to the admitting peer (AP), yet the flow shows
>>>> that the message first gets routed to the PP and then onto AP. It
>>>> would be helpful if that were clarified.   [Note: Marc's response
>>>> indicated that he thought this was fixed in the -23, however, the
>>>> diff shows no changes to that specific text between the -17 and the
>>>> -24 ]
>>>> 
>>>> 
>>>> Nits: -----
>>>> 
>>>> - Section 1.2.5, 2nd para, last sentence: this sentence is a bit
>>>> tough to interpret on a first read.  I would suggest rewording
>>>> something like the following: OLD: This layer is to the Message
>>>> Transport Layer as link- level congestion control and retransmission
>>>> in modern wireless networks is to Internet transport protocols. NEW:
>>>> The relation of this layer to the Message Transport Layer "is similar
>>>> to"|"can be likened to" the relation of the link- level congestion
>>>> control and retransmission in modern wireless networks to Internet
>>>> transport protocols.
>>>> 
>>>> - Section 3.4, last paragraph, 4th sentence: "in accord" -> "in 
>>>> accordance"
>>>> 
>>>> - Section 10.1, 2nd paragraph, 5th sentence: "can be thought of a 
>>>> doubly-linked list" -> "can be thought of as a doubly-linked list"
>>>> 
>>>> - Section 15, last paragraph: "help resolve" -> "helped resolve"
>>>> 
> 
> 
> 

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRJOg2AAoJECnERZXWan7EgygQAKZOFUs981xC3DO/0kNdqqxT
JEdTbNsEmfPurt5HP4GyX1Xz1nXirbrItl4Cb5ss0r2CuBuCQHKZhT82yukNgaUE
yVjVQSSuH+myWPTi+qxjpzrFIZRvYOZUQQrleMNeivVnCNEeIgxWcOq3UJVMrAEB
4dStv3fwA4a3yaRQT9EfPML23UUtnmXDNklwDx4Ih5AgDz8xQilxcl4IpSZwPXcm
K4AUOmQJOL64KiWQCXEhXS6fen51azOlRgYRuUNoaz5K2GMSvhPFDLfmVdnjX4Vu
QVK7PJgPjIi3bgSArQe99LbwuUpJWZOsihnFvjvP689FNdxOZ/7cu2lp9bmJmifR
bJNmj/LDk+q4phlpYYkcPqSYLrAg1tbEbV3M6mJqCti3APF8ODXSfydsijdD1Lvx
8HRdUasaWfakQ3Jh3qADXJVfdRW7xM6CsrGusq/surgW/B3AlPAcwNkmsr4iZEAm
ILTjHFkqWPmQDNs6UkPqVFnzH8LTAPsKmb7GHKJEKkVQfBe1BZ7MHFODkzFtp9wn
drCg1cr+LUuiskPKhJqF7Jplb+kU+9wq1XlcNy3koSrljHF4TvDqrBOSIJnxqCyT
cAU4iAL0rqw7BGtEutRHzJ8Tl4qgSebZeYO3RjCqAr3oACjtzUr8JFF2GEayWV/f
5nI2ugEK/+xxevxbyH0c
=dbqe
-----END PGP SIGNATURE-----

From gonzalo.camarillo@ericsson.com  Wed Feb 20 07:46:54 2013
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 6D63621F888F for <gen-art@ietfa.amsl.com>; Wed, 20 Feb 2013 07:46:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.089
X-Spam-Level: 
X-Spam-Status: No, score=-106.089 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_RMML_Stock9=0.13, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id unYx05fBcgfj for <gen-art@ietfa.amsl.com>; Wed, 20 Feb 2013 07:46:53 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9413D21F883C for <gen-art@ietf.org>; Wed, 20 Feb 2013 07:46:52 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-2e-5124efeb9c3d
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 22.6C.10459.BEFE4215; Wed, 20 Feb 2013 16:46:51 +0100 (CET)
Received: from [131.160.126.44] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.279.1; Wed, 20 Feb 2013 16:46:51 +0100
Message-ID: <5124EFEA.1040302@ericsson.com>
Date: Wed, 20 Feb 2013 17:46:50 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
References: <CAHBDyN6-J6SgnNqA1ZTcnFsLGzaeD2wGD5W58rte3A-vn2SQiA@mail.gmail.com> <512415E5.1060702@petit-huguenin.org> <1D82BACC-F763-4A4F-9E3C-61AACB3FB440@brianrosen.net> <5124E842.1070201@petit-huguenin.org>
In-Reply-To: <5124E842.1070201@petit-huguenin.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsUyM+Jvje7r9yqBBg/2a1k8vT+NzWLXFS2L jv+/WCyuvvrMYvHqxU12i7XHbzJafN6/n9mB3eP+t7/sHjtn3WX3WLLkJ5PH8dPXWT0uLvnG 6PHl8mc2j1V3vrAGsEdx2aSk5mSWpRbp2yVwZWzv+8Zc0GdZsXDNCqYGxt16XYycHBICJhKn Xj1hg7DFJC7cWw9kc3EICZxklPh98iQzhLOGUeLhn1ZmkCpeAW2JvScmgtksAqoSR3c+BOtm E7CQ2HLrPguILSoQJfH+ahNUvaDEyZlPwOIiAoYS5xddBxvKLPCLUeLRjmeMIAlhAUuJp4du Qa2+xCjx5tFOsASngJHE5UMrGCHuk5RYNK0TbBKzgKZE6/bf7BC2vMT2t3PAtgkBXbf8WQvL BEahWUiWz0LSMgtJywJG5lWM7LmJmTnp5YabGIExcXDLb90djKfOiRxilOZgURLnDXO9ECAk kJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBsTT91H/x5YlqE2cuC3vUdzH+0Rtjn9ofX13LJj6x +/Nf095rUuwmiXWcuQpxIeuU9S1+P2PkOvDG0rR8OavG3NsrbZMfbl7b4h4Ude1H6dN3mq7f 5v/zF2T/I33lx2elYt82dwWTy40Tji+e9rVpPcufJg/Hk7eWyPfs9g/RKq/pf2ulIxHVosRS nJFoqMVcVJwIAOcY8K5XAgAA
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, Brian Rosen <br@brianrosen.net>, draft-ietf-p2psip-base.all@tools.ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Gen-art] Gen-ART LC Review: draft-ietf-p2psip-base-24
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 Feb 2013 15:46:54 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

there is no way Henning is going to review this document in the next
24 hours. So, do whatever you need to do and I will talk with Henning
later.

Thanks,

Gonzalo

On 20/02/2013 5:14 PM, Marc Petit-Huguenin wrote:
> On 02/20/2013 06:20 AM, Brian Rosen wrote:
>> I will contact Henning
> 
> I was in the process yesterday evening of doing a review according
> to the link Mary send when Roland's review arrived, which basically
> killed any chance of doing that.  So either Henning send me today a
> list of things to fix, or I'll do the review later, but that
> probably be after the IESG telechat.
> 
> 
>> Brian
> 
>> On Feb 19, 2013, at 7:16 PM, Marc Petit-Huguenin
>> <marc@petit-huguenin.org> wrote:
> 
>> Thanks Mary.  I start working on this immediately.
> 
>> On 02/19/2013 04:06 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-p2psip-base-24 Reviewer:  Mary Barnes
>>>>> Review Date: 19 February 2013 Previous Review Date (-23):
>>>>> 14 December 2012 Original Review Date (-17): 6 August 2011
>>>>> IETF LC End Date: 22 July 2011 IETF 2nd LC End Date: 19
>>>>> February 2013
>>>>> 
>>>>> Summary: Almost Ready.  This version is in significantly
>>>>> better shape than the previous versions.
>>>>> 
>>>>> Comments: ========= I reviewed against my review of the -23
>>>>> up through section 6.  I reviewed beyond section 6 of this
>>>>> version (section 5 of -17, section 6 of -23) against my
>>>>> comments on the -17, since I had not re-reviewed those
>>>>> against the -23.
>>>>> 
>>>>> 
>>>>> General: --------
>>>>> 
>>>>> I still *strongly* recommend that you ensure Henning has
>>>>> reviewed this document *before* it gets into the RFC
>>>>> editor's queue.  The last RFC I had published with Henning
>>>>> as a co-author had much more extensive changes suggested
>>>>> during AUTH 48 than I found acceptable. If all the
>>>>> co-authors have not reviewed and approved the draft before 
>>>>> it goes into the RFC editor's queue, then the document
>>>>> should not go into the RFC editor's queue. He has fairly
>>>>> strict (and quite accurate) views on grammar and structure
>>>>> but it really isn't good to have so many changes go in at
>>>>> AUTH48 as there is a risk of introducing true technical
>>>>> bugs or changing something that was carefully crafted to
>>>>> achieve WG consensus: 
>>>>> http://www.cs.columbia.edu/~hgs/etc/writing-bugs.html Note,
>>>>> that there some are cases of incorrect grammar that I have
>>>>> not identified because I think the RFC editor can fix,
>>>>> however, Henning may have different views on this.
>>>>> 
>>>>> 
>>>>> Major: ------ - [-17, section 10.5] Section 11.5, 3rd para:
>>>>> text uses the phrase "it can note the Node-ID in the
>>>>> response and use this Node-ID to start sending requests".
>>>>> It's not clear whether the use of the Node-ID is a MAY or a
>>>>> MUST.    [Note: Marc's response to this was that it's an
>>>>> open issue, but this should be clarified prior to 
>>>>> publication].
>>>>> 
>>>>> Minor: ------ - idnits identifies 5 errors (downrefs).  I
>>>>> will note that in the PROTO write-up it was noted that
>>>>> those should likely be moved to Informative.
>>>>> 
>>>>> - [-17] Section 1.2.1, 2nd paragraph: I don't understand
>>>>> the example as to why a single application requires
>>>>> multiple usages - i.e, why voicemail? Isn't the intent to
>>>>> say that an application might need to use both SIP and XMPP
>>>>> - i.e., you wouldn't define a "usage" for an application,
>>>>> would you? [While Cullen responded to this comment with an
>>>>> explanation, there was no change to clarify the text and
>>>>> Marc's response didn't help clarify my concern]
>>>>> 
>>>>> - Section 3.3, 2nd paragraph after the capability bullet
>>>>> list, next to last sentence.  There is at least an article
>>>>> missing from this sentence and it reads rather awkwardly.
>>>>> Perhaps changing to something like: OLD: If there is a
>>>>> failure on the reverse path caused by topology change since
>>>>> the request was sent, this will be handled by the
>>>>> end-to-end retransmission of the response as described in
>>>>> Section 6.2.1. NEW: Note that a failure on the reverse path
>>>>> caused by a topology change after the request was sent,
>>>>> will be handled by the end-to-end retransmission of the
>>>>> response as described in Section 6.2.1.
>>>>> 
>>>>> - [-17] Section 3.3, last paragraph.  Add a reference to
>>>>> 5.4.2.4 after "RouteQuery method"
>>>>> 
>>>>> - Section 3.4, last paragraph, 3rd sentence: "that the
>>>>> specified by the algorithm" should be something like "than
>>>>> specified by the algorithm".
>>>>> 
>>>>> - [-23] Section 6.6:  All my previous concerns were
>>>>> addressed, except, the Note to implementors paragraph still
>>>>> seems out of context - it should be deleted or this section
>>>>> should be restructured so it is in context.
>>>>> 
>>>>> - [-17, section 11] Section 12, Second paragraph, 3rd
>>>>> sentence says that "It gets routed to the admitting peer
>>>>> (AP), yet the flow shows that the message first gets routed
>>>>> to the PP and then onto AP. It would be helpful if that
>>>>> were clarified.   [Note: Marc's response indicated that he
>>>>> thought this was fixed in the -23, however, the diff shows
>>>>> no changes to that specific text between the -17 and the 
>>>>> -24 ]
>>>>> 
>>>>> 
>>>>> Nits: -----
>>>>> 
>>>>> - Section 1.2.5, 2nd para, last sentence: this sentence is
>>>>> a bit tough to interpret on a first read.  I would suggest
>>>>> rewording something like the following: OLD: This layer is
>>>>> to the Message Transport Layer as link- level congestion
>>>>> control and retransmission in modern wireless networks is
>>>>> to Internet transport protocols. NEW: The relation of this
>>>>> layer to the Message Transport Layer "is similar to"|"can
>>>>> be likened to" the relation of the link- level congestion 
>>>>> control and retransmission in modern wireless networks to
>>>>> Internet transport protocols.
>>>>> 
>>>>> - Section 3.4, last paragraph, 4th sentence: "in accord" ->
>>>>> "in accordance"
>>>>> 
>>>>> - Section 10.1, 2nd paragraph, 5th sentence: "can be
>>>>> thought of a doubly-linked list" -> "can be thought of as a
>>>>> doubly-linked list"
>>>>> 
>>>>> - Section 15, last paragraph: "help resolve" -> "helped
>>>>> resolve"
>>>>> 
> 
> 
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (MingW32)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJRJO/pAAoJENEzUJhwP4c2+5IIAMGKYdj0TF71N03TyOe406EJ
A0WZKPEQwFHIJcly0weIHTorjjd48ukC369W1/VokffSuV4tFdRgYGFVZMiGRSE5
Jl6f9DCZJclCp26c5hSgb54IpiIIaps8Yk3Jy3J+wW81l+l3jUClM4pJNJyh6oxi
jNNjJX67ATsqsN3D0Il7/6a0K90d0zUHL9tqIbHFIz5ls7UISQem4jsL2SJPJr6B
8I1R/TSXgf00huLx8EhEV44hPhMkSc7DNtEutY1a7jQ2D6Q+55mXABveY05GmI4y
1eq2u8WZzoBvA1mWOcvpa4ICwYr4pYG8bCD0EiHqSyXEE7icirjH8OyUDx3uza0=
=9jzo
-----END PGP SIGNATURE-----

From mary.ietf.barnes@gmail.com  Thu Feb 21 04:49:57 2013
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 0107021F8C55 for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 04:49:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.517
X-Spam-Level: 
X-Spam-Status: No, score=-103.517 tagged_above=-999 required=5 tests=[AWL=-0.048, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_RMML_Stock9=0.13, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cul8SSzbVcRy for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 04:49:55 -0800 (PST)
Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by ietfa.amsl.com (Postfix) with ESMTP id 8954821F8BE0 for <gen-art@ietf.org>; Thu, 21 Feb 2013 04:49:55 -0800 (PST)
Received: by mail-qa0-f47.google.com with SMTP id j8so2968613qah.20 for <gen-art@ietf.org>; Thu, 21 Feb 2013 04:49:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Guwe4zHPcKt9NZDikBiaoZlX4GLRiGUcSNHHmIF0SjY=; b=jTGkxBVH0524j51ipFePW10yTMh6Mt5lMFBx67BPJjLyWe42nKOyVgvpSyEntKR735 HnM51QkfazFsmRuS7TyLoDZF3qp4XqvZ8MIDlqUkkuzSDrfFWkB6P1rowhoUFJMtSdqO H27X0LxbZbJH620wjOd9M040JYz5cMJxctQxSDuAaNCa7bzEJ7Ko0lfOWdYshZMNkCeW f/Co0MyRykvICtsW3KHcYTdVvP+/77rTNK3u41OkBtvfK3/5JZUU+Dxoej4JYf/fSa0I QNk+ToB5jjpGaVhjAVpBAtkspQRI86pDjJvfDE2ZDBbCi0GG0Qzi4A0LwOijqnI78zfH SYOA==
MIME-Version: 1.0
X-Received: by 10.224.216.65 with SMTP id hh1mr10818552qab.43.1361450991431; Thu, 21 Feb 2013 04:49:51 -0800 (PST)
Received: by 10.49.131.199 with HTTP; Thu, 21 Feb 2013 04:49:51 -0800 (PST)
In-Reply-To: <5124EFEA.1040302@ericsson.com>
References: <CAHBDyN6-J6SgnNqA1ZTcnFsLGzaeD2wGD5W58rte3A-vn2SQiA@mail.gmail.com> <512415E5.1060702@petit-huguenin.org> <1D82BACC-F763-4A4F-9E3C-61AACB3FB440@brianrosen.net> <5124E842.1070201@petit-huguenin.org> <5124EFEA.1040302@ericsson.com>
Date: Thu, 21 Feb 2013 06:49:51 -0600
Message-ID: <CAHBDyN5hOh48XJrvoEnu_eQU4AE_QxxomxbVti8m=ycT2A3ryg@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Marc Petit-Huguenin <marc@petit-huguenin.org>, Brian Rosen <br@brianrosen.net>, draft-ietf-p2psip-base.all@tools.ietf.org, Dean Willis <dean.willis@softarmor.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review: draft-ietf-p2psip-base-24
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 Feb 2013 12:49:57 -0000

Certainly - but it's a pay now or a pay later unless you can convince
Henning that he doesn't need to do his usual careful review of a
document with his name.  This suggestion is based on my experience
with the XCON protocol document. The level of complexity and density
of this specification is significantly higher than the XCON document.
It will be a huge challenge for the RFC editor - I think even Alice
would find it so.  Having to deal with a potential large number of
edits at that stage has the potential to break or changes things that
were so carefully fixed.

Regards,
Mary.

On Wed, Feb 20, 2013 at 9:46 AM, Gonzalo Camarillo
<Gonzalo.Camarillo@ericsson.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> there is no way Henning is going to review this document in the next
> 24 hours. So, do whatever you need to do and I will talk with Henning
> later.
>
> Thanks,
>
> Gonzalo
>
> On 20/02/2013 5:14 PM, Marc Petit-Huguenin wrote:
>> On 02/20/2013 06:20 AM, Brian Rosen wrote:
>>> I will contact Henning
>>
>> I was in the process yesterday evening of doing a review according
>> to the link Mary send when Roland's review arrived, which basically
>> killed any chance of doing that.  So either Henning send me today a
>> list of things to fix, or I'll do the review later, but that
>> probably be after the IESG telechat.
>>
>>
>>> Brian
>>
>>> On Feb 19, 2013, at 7:16 PM, Marc Petit-Huguenin
>>> <marc@petit-huguenin.org> wrote:
>>
>>> Thanks Mary.  I start working on this immediately.
>>
>>> On 02/19/2013 04:06 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-p2psip-base-24 Reviewer:  Mary Barnes
>>>>>> Review Date: 19 February 2013 Previous Review Date (-23):
>>>>>> 14 December 2012 Original Review Date (-17): 6 August 2011
>>>>>> IETF LC End Date: 22 July 2011 IETF 2nd LC End Date: 19
>>>>>> February 2013
>>>>>>
>>>>>> Summary: Almost Ready.  This version is in significantly
>>>>>> better shape than the previous versions.
>>>>>>
>>>>>> Comments: ========= I reviewed against my review of the -23
>>>>>> up through section 6.  I reviewed beyond section 6 of this
>>>>>> version (section 5 of -17, section 6 of -23) against my
>>>>>> comments on the -17, since I had not re-reviewed those
>>>>>> against the -23.
>>>>>>
>>>>>>
>>>>>> General: --------
>>>>>>
>>>>>> I still *strongly* recommend that you ensure Henning has
>>>>>> reviewed this document *before* it gets into the RFC
>>>>>> editor's queue.  The last RFC I had published with Henning
>>>>>> as a co-author had much more extensive changes suggested
>>>>>> during AUTH 48 than I found acceptable. If all the
>>>>>> co-authors have not reviewed and approved the draft before
>>>>>> it goes into the RFC editor's queue, then the document
>>>>>> should not go into the RFC editor's queue. He has fairly
>>>>>> strict (and quite accurate) views on grammar and structure
>>>>>> but it really isn't good to have so many changes go in at
>>>>>> AUTH48 as there is a risk of introducing true technical
>>>>>> bugs or changing something that was carefully crafted to
>>>>>> achieve WG consensus:
>>>>>> http://www.cs.columbia.edu/~hgs/etc/writing-bugs.html Note,
>>>>>> that there some are cases of incorrect grammar that I have
>>>>>> not identified because I think the RFC editor can fix,
>>>>>> however, Henning may have different views on this.
>>>>>>
>>>>>>
>>>>>> Major: ------ - [-17, section 10.5] Section 11.5, 3rd para:
>>>>>> text uses the phrase "it can note the Node-ID in the
>>>>>> response and use this Node-ID to start sending requests".
>>>>>> It's not clear whether the use of the Node-ID is a MAY or a
>>>>>> MUST.    [Note: Marc's response to this was that it's an
>>>>>> open issue, but this should be clarified prior to
>>>>>> publication].
>>>>>>
>>>>>> Minor: ------ - idnits identifies 5 errors (downrefs).  I
>>>>>> will note that in the PROTO write-up it was noted that
>>>>>> those should likely be moved to Informative.
>>>>>>
>>>>>> - [-17] Section 1.2.1, 2nd paragraph: I don't understand
>>>>>> the example as to why a single application requires
>>>>>> multiple usages - i.e, why voicemail? Isn't the intent to
>>>>>> say that an application might need to use both SIP and XMPP
>>>>>> - i.e., you wouldn't define a "usage" for an application,
>>>>>> would you? [While Cullen responded to this comment with an
>>>>>> explanation, there was no change to clarify the text and
>>>>>> Marc's response didn't help clarify my concern]
>>>>>>
>>>>>> - Section 3.3, 2nd paragraph after the capability bullet
>>>>>> list, next to last sentence.  There is at least an article
>>>>>> missing from this sentence and it reads rather awkwardly.
>>>>>> Perhaps changing to something like: OLD: If there is a
>>>>>> failure on the reverse path caused by topology change since
>>>>>> the request was sent, this will be handled by the
>>>>>> end-to-end retransmission of the response as described in
>>>>>> Section 6.2.1. NEW: Note that a failure on the reverse path
>>>>>> caused by a topology change after the request was sent,
>>>>>> will be handled by the end-to-end retransmission of the
>>>>>> response as described in Section 6.2.1.
>>>>>>
>>>>>> - [-17] Section 3.3, last paragraph.  Add a reference to
>>>>>> 5.4.2.4 after "RouteQuery method"
>>>>>>
>>>>>> - Section 3.4, last paragraph, 3rd sentence: "that the
>>>>>> specified by the algorithm" should be something like "than
>>>>>> specified by the algorithm".
>>>>>>
>>>>>> - [-23] Section 6.6:  All my previous concerns were
>>>>>> addressed, except, the Note to implementors paragraph still
>>>>>> seems out of context - it should be deleted or this section
>>>>>> should be restructured so it is in context.
>>>>>>
>>>>>> - [-17, section 11] Section 12, Second paragraph, 3rd
>>>>>> sentence says that "It gets routed to the admitting peer
>>>>>> (AP), yet the flow shows that the message first gets routed
>>>>>> to the PP and then onto AP. It would be helpful if that
>>>>>> were clarified.   [Note: Marc's response indicated that he
>>>>>> thought this was fixed in the -23, however, the diff shows
>>>>>> no changes to that specific text between the -17 and the
>>>>>> -24 ]
>>>>>>
>>>>>>
>>>>>> Nits: -----
>>>>>>
>>>>>> - Section 1.2.5, 2nd para, last sentence: this sentence is
>>>>>> a bit tough to interpret on a first read.  I would suggest
>>>>>> rewording something like the following: OLD: This layer is
>>>>>> to the Message Transport Layer as link- level congestion
>>>>>> control and retransmission in modern wireless networks is
>>>>>> to Internet transport protocols. NEW: The relation of this
>>>>>> layer to the Message Transport Layer "is similar to"|"can
>>>>>> be likened to" the relation of the link- level congestion
>>>>>> control and retransmission in modern wireless networks to
>>>>>> Internet transport protocols.
>>>>>>
>>>>>> - Section 3.4, last paragraph, 4th sentence: "in accord" ->
>>>>>> "in accordance"
>>>>>>
>>>>>> - Section 10.1, 2nd paragraph, 5th sentence: "can be
>>>>>> thought of a doubly-linked list" -> "can be thought of as a
>>>>>> doubly-linked list"
>>>>>>
>>>>>> - Section 15, last paragraph: "help resolve" -> "helped
>>>>>> resolve"
>>>>>>
>>
>>
>>
>>
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (MingW32)
> Comment: Using GnuPG with undefined - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJRJO/pAAoJENEzUJhwP4c2+5IIAMGKYdj0TF71N03TyOe406EJ
> A0WZKPEQwFHIJcly0weIHTorjjd48ukC369W1/VokffSuV4tFdRgYGFVZMiGRSE5
> Jl6f9DCZJclCp26c5hSgb54IpiIIaps8Yk3Jy3J+wW81l+l3jUClM4pJNJyh6oxi
> jNNjJX67ATsqsN3D0Il7/6a0K90d0zUHL9tqIbHFIz5ls7UISQem4jsL2SJPJr6B
> 8I1R/TSXgf00huLx8EhEV44hPhMkSc7DNtEutY1a7jQ2D6Q+55mXABveY05GmI4y
> 1eq2u8WZzoBvA1mWOcvpa4ICwYr4pYG8bCD0EiHqSyXEE7icirjH8OyUDx3uza0=
> =9jzo
> -----END PGP SIGNATURE-----

From gonzalo.camarillo@ericsson.com  Thu Feb 21 04:56:23 2013
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 7DC4E21F8DC9 for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 04:56:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.155
X-Spam-Level: 
X-Spam-Status: No, score=-106.155 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VlEZAu5a5YcU for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 04:56:22 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id DDBF821F87A6 for <gen-art@ietf.org>; Thu, 21 Feb 2013 04:56:21 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-13-512619746482
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 6A.F2.10459.47916215; Thu, 21 Feb 2013 13:56:20 +0100 (CET)
Received: from [131.160.126.44] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.279.1; Thu, 21 Feb 2013 13:56:20 +0100
Message-ID: <51261973.6000106@ericsson.com>
Date: Thu, 21 Feb 2013 14:56:19 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
References: <CAHBDyN6-J6SgnNqA1ZTcnFsLGzaeD2wGD5W58rte3A-vn2SQiA@mail.gmail.com> <512415E5.1060702@petit-huguenin.org> <1D82BACC-F763-4A4F-9E3C-61AACB3FB440@brianrosen.net> <5124E842.1070201@petit-huguenin.org> <5124EFEA.1040302@ericsson.com> <CAHBDyN5hOh48XJrvoEnu_eQU4AE_QxxomxbVti8m=ycT2A3ryg@mail.gmail.com>
In-Reply-To: <CAHBDyN5hOh48XJrvoEnu_eQU4AE_QxxomxbVti8m=ycT2A3ryg@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPLMWRmVeSWpSXmKPExsUyM+JvjW6ppFqgwV1mi6f3p7FZ7LqiZdHx /xeLxdVXn1ksXr24yW6x9vhNRovP+/czO7B73P/2l91j56y77B5Llvxk8jh++jqrx8Ul3xg9 vlz+zOax6s4X1gD2KC6blNSczLLUIn27BK6Mw50/WQuu2Ve8vmfQwPjKuIuRg0NCwERi6g3W LkZOIFNM4sK99WxdjFwcQgInGSW+npvPCOGsYZRY9HM2G0gVr4C2xN9Dc8BsFgFVid1rfoJ1 swlYSGy5dZ8FZKioQJTElX2WEOWCEidnPmEBsUUEdCS+fX4LtoBZ4D+jxOmLW5hAEsIClhJP D92C2rydSWLC3WOsIIM4BQIlbiyogbhOUmLRtE6wQcwCehJTrrYwQtjyEtvfzmEGsYWAblv+ rIVlAqPQLCS7ZyFpmYWkZQEj8ypG9tzEzJz0csNNjMBIOLjlt+4OxlPnRA4xSnOwKInzhrle CBASSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAaM3B2DIh50phSEFz5q69fhsUTy7a0lv7ryX4 yo2eUJ+yjdPeiF9v37J55xku5sfr1Jw5LOV+7tqyc2aCJ1/N+dKY6bt5d+wV4RJQ0crvXHba XuHZqXOl626ziakodsquPXfE5Xe9fNBXIen0a6a/tmwImTz9vufxdS5ikrff+EzdcldfZaP4 FCWW4oxEQy3mouJEAERfPyNSAgAA
Cc: Marc Petit-Huguenin <marc@petit-huguenin.org>, Brian Rosen <br@brianrosen.net>, draft-ietf-p2psip-base.all@tools.ietf.org, Dean Willis <dean.willis@softarmor.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review: draft-ietf-p2psip-base-24
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 Feb 2013 12:56:23 -0000

Hi Mary,

yes, as you know, I know Henning very well. I will talk with him about
this. A potential outcome is that we get this document in the Approved
Point Raised state and then we get him to review it. In any case, thanks
for the advice!

Cheers,

Gonzalo

On 21/02/2013 2:49 PM, Mary Barnes wrote:
> Certainly - but it's a pay now or a pay later unless you can convince
> Henning that he doesn't need to do his usual careful review of a
> document with his name.  This suggestion is based on my experience
> with the XCON protocol document. The level of complexity and density
> of this specification is significantly higher than the XCON document.
> It will be a huge challenge for the RFC editor - I think even Alice
> would find it so.  Having to deal with a potential large number of
> edits at that stage has the potential to break or changes things that
> were so carefully fixed.
> 
> Regards,
> Mary.
> 
> On Wed, Feb 20, 2013 at 9:46 AM, Gonzalo Camarillo
> <Gonzalo.Camarillo@ericsson.com> wrote:
> Hi,
> 
> there is no way Henning is going to review this document in the next
> 24 hours. So, do whatever you need to do and I will talk with Henning
> later.
> 
> Thanks,
> 
> Gonzalo
> 
> On 20/02/2013 5:14 PM, Marc Petit-Huguenin wrote:
>>>> On 02/20/2013 06:20 AM, Brian Rosen wrote:
>>>>> I will contact Henning
>>>>
>>>> I was in the process yesterday evening of doing a review according
>>>> to the link Mary send when Roland's review arrived, which basically
>>>> killed any chance of doing that.  So either Henning send me today a
>>>> list of things to fix, or I'll do the review later, but that
>>>> probably be after the IESG telechat.
>>>>
>>>>
>>>>> Brian
>>>>
>>>>> On Feb 19, 2013, at 7:16 PM, Marc Petit-Huguenin
>>>>> <marc@petit-huguenin.org> wrote:
>>>>
>>>>> Thanks Mary.  I start working on this immediately.
>>>>
>>>>> On 02/19/2013 04:06 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-p2psip-base-24 Reviewer:  Mary Barnes
>>>>>>>> Review Date: 19 February 2013 Previous Review Date (-23):
>>>>>>>> 14 December 2012 Original Review Date (-17): 6 August 2011
>>>>>>>> IETF LC End Date: 22 July 2011 IETF 2nd LC End Date: 19
>>>>>>>> February 2013
>>>>>>>>
>>>>>>>> Summary: Almost Ready.  This version is in significantly
>>>>>>>> better shape than the previous versions.
>>>>>>>>
>>>>>>>> Comments: ========= I reviewed against my review of the -23
>>>>>>>> up through section 6.  I reviewed beyond section 6 of this
>>>>>>>> version (section 5 of -17, section 6 of -23) against my
>>>>>>>> comments on the -17, since I had not re-reviewed those
>>>>>>>> against the -23.
>>>>>>>>
>>>>>>>>
>>>>>>>> General: --------
>>>>>>>>
>>>>>>>> I still *strongly* recommend that you ensure Henning has
>>>>>>>> reviewed this document *before* it gets into the RFC
>>>>>>>> editor's queue.  The last RFC I had published with Henning
>>>>>>>> as a co-author had much more extensive changes suggested
>>>>>>>> during AUTH 48 than I found acceptable. If all the
>>>>>>>> co-authors have not reviewed and approved the draft before
>>>>>>>> it goes into the RFC editor's queue, then the document
>>>>>>>> should not go into the RFC editor's queue. He has fairly
>>>>>>>> strict (and quite accurate) views on grammar and structure
>>>>>>>> but it really isn't good to have so many changes go in at
>>>>>>>> AUTH48 as there is a risk of introducing true technical
>>>>>>>> bugs or changing something that was carefully crafted to
>>>>>>>> achieve WG consensus:
>>>>>>>> http://www.cs.columbia.edu/~hgs/etc/writing-bugs.html Note,
>>>>>>>> that there some are cases of incorrect grammar that I have
>>>>>>>> not identified because I think the RFC editor can fix,
>>>>>>>> however, Henning may have different views on this.
>>>>>>>>
>>>>>>>>
>>>>>>>> Major: ------ - [-17, section 10.5] Section 11.5, 3rd para:
>>>>>>>> text uses the phrase "it can note the Node-ID in the
>>>>>>>> response and use this Node-ID to start sending requests".
>>>>>>>> It's not clear whether the use of the Node-ID is a MAY or a
>>>>>>>> MUST.    [Note: Marc's response to this was that it's an
>>>>>>>> open issue, but this should be clarified prior to
>>>>>>>> publication].
>>>>>>>>
>>>>>>>> Minor: ------ - idnits identifies 5 errors (downrefs).  I
>>>>>>>> will note that in the PROTO write-up it was noted that
>>>>>>>> those should likely be moved to Informative.
>>>>>>>>
>>>>>>>> - [-17] Section 1.2.1, 2nd paragraph: I don't understand
>>>>>>>> the example as to why a single application requires
>>>>>>>> multiple usages - i.e, why voicemail? Isn't the intent to
>>>>>>>> say that an application might need to use both SIP and XMPP
>>>>>>>> - i.e., you wouldn't define a "usage" for an application,
>>>>>>>> would you? [While Cullen responded to this comment with an
>>>>>>>> explanation, there was no change to clarify the text and
>>>>>>>> Marc's response didn't help clarify my concern]
>>>>>>>>
>>>>>>>> - Section 3.3, 2nd paragraph after the capability bullet
>>>>>>>> list, next to last sentence.  There is at least an article
>>>>>>>> missing from this sentence and it reads rather awkwardly.
>>>>>>>> Perhaps changing to something like: OLD: If there is a
>>>>>>>> failure on the reverse path caused by topology change since
>>>>>>>> the request was sent, this will be handled by the
>>>>>>>> end-to-end retransmission of the response as described in
>>>>>>>> Section 6.2.1. NEW: Note that a failure on the reverse path
>>>>>>>> caused by a topology change after the request was sent,
>>>>>>>> will be handled by the end-to-end retransmission of the
>>>>>>>> response as described in Section 6.2.1.
>>>>>>>>
>>>>>>>> - [-17] Section 3.3, last paragraph.  Add a reference to
>>>>>>>> 5.4.2.4 after "RouteQuery method"
>>>>>>>>
>>>>>>>> - Section 3.4, last paragraph, 3rd sentence: "that the
>>>>>>>> specified by the algorithm" should be something like "than
>>>>>>>> specified by the algorithm".
>>>>>>>>
>>>>>>>> - [-23] Section 6.6:  All my previous concerns were
>>>>>>>> addressed, except, the Note to implementors paragraph still
>>>>>>>> seems out of context - it should be deleted or this section
>>>>>>>> should be restructured so it is in context.
>>>>>>>>
>>>>>>>> - [-17, section 11] Section 12, Second paragraph, 3rd
>>>>>>>> sentence says that "It gets routed to the admitting peer
>>>>>>>> (AP), yet the flow shows that the message first gets routed
>>>>>>>> to the PP and then onto AP. It would be helpful if that
>>>>>>>> were clarified.   [Note: Marc's response indicated that he
>>>>>>>> thought this was fixed in the -23, however, the diff shows
>>>>>>>> no changes to that specific text between the -17 and the
>>>>>>>> -24 ]
>>>>>>>>
>>>>>>>>
>>>>>>>> Nits: -----
>>>>>>>>
>>>>>>>> - Section 1.2.5, 2nd para, last sentence: this sentence is
>>>>>>>> a bit tough to interpret on a first read.  I would suggest
>>>>>>>> rewording something like the following: OLD: This layer is
>>>>>>>> to the Message Transport Layer as link- level congestion
>>>>>>>> control and retransmission in modern wireless networks is
>>>>>>>> to Internet transport protocols. NEW: The relation of this
>>>>>>>> layer to the Message Transport Layer "is similar to"|"can
>>>>>>>> be likened to" the relation of the link- level congestion
>>>>>>>> control and retransmission in modern wireless networks to
>>>>>>>> Internet transport protocols.
>>>>>>>>
>>>>>>>> - Section 3.4, last paragraph, 4th sentence: "in accord" ->
>>>>>>>> "in accordance"
>>>>>>>>
>>>>>>>> - Section 10.1, 2nd paragraph, 5th sentence: "can be
>>>>>>>> thought of a doubly-linked list" -> "can be thought of as a
>>>>>>>> doubly-linked list"
>>>>>>>>
>>>>>>>> - Section 15, last paragraph: "help resolve" -> "helped
>>>>>>>> resolve"
>>>>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
> 


From shares@ndzh.com  Thu Feb 21 07:29:25 2013
Return-Path: <shares@ndzh.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 0705921F8E6D for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 07:29:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.006
X-Spam-Level: *
X-Spam-Status: No, score=1.006 tagged_above=-999 required=5 tests=[AWL=0.501,  BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sT8WyT6P+5ZC for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 07:29:24 -0800 (PST)
Received: from hickoryhill-consulting.com (unknown [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 8680521F8E9D for <gen-art@ietf.org>; Thu, 21 Feb 2013 07:29:23 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=64.112.195.202; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Jon Mitchell \(GNS\)'" <Jon.Mitchell@microsoft.com>, "'Elwyn Davies'" <elwynd@dial.pipex.com>, "'General Area Review Team'" <gen-art@ietf.org>
References: <511DFCAD.6020509@dial.pipex.com> <f1195a2f3468441d85edaf0b8b843bba@DFM-DB3MBX15-08.exchange.corp.microsoft.com>
In-Reply-To: <f1195a2f3468441d85edaf0b8b843bba@DFM-DB3MBX15-08.exchange.corp.microsoft.com>
Date: Thu, 21 Feb 2013 10:29:07 -0500
Message-ID: <00d001ce1048$30d63f00$9282bd00$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJn+X55OJNmPAsTdqI4/oT78g4/vQHs9lBBl0EyqAA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-idr-as-private-reservation-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, 21 Feb 2013 15:29:25 -0000

Jon and Elwyn:

I would like to make a correction here. The WG as a body of experts
suggested to the author via the Author to IANA.  Perhaps as a body of
experts, this WG is sufficient to begin this range.  Second, the suggestion
from the chairs is that IANA might want to allocate a portion of this total
range for initial usage. 

Finally, the Private Address space in the IPV4 space and this IPv6 range are
logically connected, but the numbers are not connected.

Please let me know if this challenges any of your review. 

Sue Hares
(Shepherd and co-chair) 

-----Original Message-----
From: Jon Mitchell (GNS) [mailto:Jon.Mitchell@microsoft.com] 
Sent: Monday, February 18, 2013 10:26 AM
To: Elwyn Davies; General Area Review Team
Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org
Subject: RE: Gen-art last call review of
draft-ietf-idr-as-private-reservation-03


Elwyn -

Thanks for your review.  The suggestion is being made to IANA who owns the
assignment and was discussed at length in the working group with rough
consensus.  IANA will replace the suggested values into TBDX values below
that text if IESG approves.  This text will not be in the RFC, it's to be
stricken from the final document by RFC Editor (I was attempting to write
this text in alignment with Section 5.1 of RFC 5226) .

On the final ASN in the range, this is in accordance with like reservation
of the existing 2 byte Private ASN reservations, where the final ASN in that
space is not utilized either (except for well-known community values).
Also, a case was made that code implementations tend to have issues with
final number usage if using incorrect variable types for storage.  That
said, the small discussion on and off list about this resolved that if we
wanted to formalize the reservation of the last ASN of both the 2 byte space
65535 and the 4 byte space 4294967295, probably a separate draft should be
constructed detailing the logic behind these as they have nothing to do with
Private ASN's per se and have already been marked as Reserved by IANA as you
noted.  I'm open to IESG direction if we want to take a different approach
on this...

Cheers,

Jon

-----Original Message-----
From: Elwyn Davies [mailto:elwynd@dial.pipex.com] 
Sent: Friday, February 15, 2013 4:15 AM
To: General Area Review Team
Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org
Subject: Gen-art last call review of
draft-ietf-idr-as-private-reservation-03

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-as-private-reservation-03.txt
Reviewer: Elwyn Davies
Review Date: 15 February 2013
IETF LC End Date: 22 February 2013
IESG Telechat date: (if known) -

Summary: Ready for the IESG.

Nits/editorial comments:  The draft is not actually definitive about range
of values to be allocated - the range in s10 is just a 'suggestion'.  Who is
actually making the decision about the range?

Aside: I noted that the highest possible 32 bit number (4294967295 =
0xFFFFFFFF) is excluded from the proposed range.  This is marked as reserved
in the IANA table but AFAICS this reserved item does not have a
specification associated with the reservation.  This document would be an
opportunity to explicitly mention that the topmost value is reserved (for
future expansion? :-) )




From shares@ndzh.com  Thu Feb 21 07:37:30 2013
Return-Path: <shares@ndzh.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 7AC8E21F8EAD for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 07:37:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.975
X-Spam-Level: 
X-Spam-Status: No, score=0.975 tagged_above=-999 required=5 tests=[AWL=0.470,  BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lgfR6BNIzxRF for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 07:37:29 -0800 (PST)
Received: from hickoryhill-consulting.com (unknown [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 2078221F8E8C for <gen-art@ietf.org>; Thu, 21 Feb 2013 07:37:24 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=64.112.195.202; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Elwyn Davies'" <elwynd@dial.pipex.com>, "'Jon Mitchell \(GNS\)'" <Jon.Mitchell@microsoft.com>
References: <511DFCAD.6020509@dial.pipex.com>	 <f1195a2f3468441d85edaf0b8b843bba@DFM-DB3MBX15-08.exchange.corp.microsoft.com> <1361236326.4494.891.camel@mightyatom>
In-Reply-To: <1361236326.4494.891.camel@mightyatom>
Date: Thu, 21 Feb 2013 10:37:19 -0500
Message-ID: <00e201ce1049$55cd2d90$016788b0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJn+X55OJNmPAsTdqI4/oT78g4/vQHs9lBBAjjRiW6XL3CYoA==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-idr-as-private-reservation-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, 21 Feb 2013 15:37:30 -0000

Elwyn and Jon:

This is an IETF consensus about the draft range.  As such, it should be put
in the draft as Jon indicated.  As a shepherd and a co-chair, my comment to
the IANA team is that perhaps they should consider handling out a portion of
the whole space. 

Once it is out, no one ever says "less" but someone always says "more".   I
will try to respond to the IANA or have a conversation about this draft with
them if possible.  I will note this in my status to Stewart Bryant (AD)
today. 

Sue 

-----Original Message-----
From: Elwyn Davies [mailto:elwynd@dial.pipex.com] 
Sent: Monday, February 18, 2013 8:12 PM
To: Jon Mitchell (GNS)
Cc: General Area Review Team;
draft-ietf-idr-as-private-reservation.all@tools.ietf.org
Subject: RE: Gen-art last call review of
draft-ietf-idr-as-private-reservation-03

On Mon, 2013-02-18 at 15:26 +0000, Jon Mitchell (GNS) wrote:
> Elwyn -
> 
> Thanks for your review. 
:-)

>  The suggestion is being made to IANA who owns the assignment and was 
> discussed at length in the working group with rough consensus.
As specified in the registry, allocations in this registry are either by
IETF Concensus (i.e. a suitable RFC such as this draft is intended to
be) or request from a RIR. Thus it isn't a matter of suggesting to IANA but
telling them what the IETF want done - so this draft should be definitive -
and what you said about WG concensus constitutes the values to be used
unless somebody else in the IETF manages to alter the concensus which seems
unlikely.
  
> IANA will replace the suggested values into TBDX values below that 
> text if IESG approves.  This text will not be in the RFC, it's to be 
> stricken from the final document by RFC Editor (I was attempting to 
> write this text in alignment with Section 5.1 of RFC 5226) .
Yes, that's fine and as expected.
> 
> On the final ASN in the range, this is in accordance with like 
> reservation of the existing 2 byte Private ASN reservations, where the 
> final ASN in that space is not utilized either (except for well-known 
> community values).  Also, a case was made that code implementations 
> tend to have issues with final number usage if using incorrect 
> variable types for storage.  That said, the small discussion on and 
> off list about this resolved that if we wanted to formalize the 
> reservation of the last ASN of both the 2 byte space 65535 and the 4 
> byte space 4294967295, probably a separate draft should be constructed 
> detailing the logic behind these as they have nothing to do with 
> Private ASN's per se and have already been marked as Reserved by IANA 
> as you noted.  I'm open to IESG direction if we want to take a 
> different approach on this...
Publishing a separate draft seems a bit overkill but clearly that's not my
decision. ;-)

Regards,
Elwyn
> 
> Cheers,
> 
> Jon
> 
> -----Original Message-----
> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
> Sent: Friday, February 15, 2013 4:15 AM
> To: General Area Review Team
> Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org
> Subject: Gen-art last call review of 
> draft-ietf-idr-as-private-reservation-03
> 
> 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-as-private-reservation-03.txt
> Reviewer: Elwyn Davies
> Review Date: 15 February 2013
> IETF LC End Date: 22 February 2013
> IESG Telechat date: (if known) -
> 
> Summary: Ready for the IESG.
> 
> Nits/editorial comments:  The draft is not actually definitive about range
of values to be allocated - the range in s10 is just a 'suggestion'.  Who is
actually making the decision about the range?
> 
> Aside: I noted that the highest possible 32 bit number (4294967295 =
> 0xFFFFFFFF) is excluded from the proposed range.  This is marked as 
> reserved in the IANA table but AFAICS this reserved item does not have 
> a specification associated with the reservation.  This document would 
> be an opportunity to explicitly mention that the topmost value is 
> reserved (for future expansion? :-) )
> 
> 



From shares@ndzh.com  Thu Feb 21 07:43:51 2013
Return-Path: <shares@ndzh.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 36F1E21F8E69 for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 07:43:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.947
X-Spam-Level: 
X-Spam-Status: No, score=0.947 tagged_above=-999 required=5 tests=[AWL=0.442,  BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bwk5yWbKxVa for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 07:43:50 -0800 (PST)
Received: from hickoryhill-consulting.com (unknown [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 4D44B21F8703 for <gen-art@ietf.org>; Thu, 21 Feb 2013 07:43:50 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=64.112.195.202; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Jon Mitchell \(GNS\)'" <Jon.Mitchell@microsoft.com>, "'Elwyn Davies'" <elwynd@dial.pipex.com>
References: <511DFCAD.6020509@dial.pipex.com>	 <f1195a2f3468441d85edaf0b8b843bba@DFM-DB3MBX15-08.exchange.corp.microsoft.com> <1361236326.4494.891.camel@mightyatom> <4f5ed402038544d0b1da25226424e60b@DFM-DB3MBX15-08.exchange.corp.microsoft.com>
In-Reply-To: <4f5ed402038544d0b1da25226424e60b@DFM-DB3MBX15-08.exchange.corp.microsoft.com>
Date: Thu, 21 Feb 2013 10:43:33 -0500
Message-ID: <00e401ce104a$3512ec60$9f38c520$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJn+X55OJNmPAsTdqI4/oT78g4/vQHs9lBBAjjRiW4Cb1V6p5cb9tBA
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-idr-as-private-reservation-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, 21 Feb 2013 15:43:51 -0000

Jon and Elwyn:

These drafts are working toward a larger goal - the eventual update of the
RFC 4271 with current practices.   Getting consensus on these items except
in very small pieces have been extremely difficult. 

Eventually, these will be all rolled up into larger documents that refer to
these smaller documents. 

The reason behind this is tactical. The smaller drafts allow people to stop
doing bad things to BGP immediately.  We have new implementation coming due
to the explosion in the Data center market.  Therefore, vague pieces in
RFC4271 must be plugged now. 

It seems that I really should get around to writing up the process on the
IDR web page and an internet draft. 

Thanks for your hard work, 

Sue 

-----Original Message-----
From: Jon Mitchell (GNS) [mailto:Jon.Mitchell@microsoft.com] 
Sent: Tuesday, February 19, 2013 3:27 PM
To: Elwyn Davies
Cc: General Area Review Team;
draft-ietf-idr-as-private-reservation.all@tools.ietf.org
Subject: RE: Gen-art last call review of
draft-ietf-idr-as-private-reservation-03


Elwyn -

Yes, I agree this is a reasonable change to remove all of the "suggestion"
text in the IANA considerations area and will make sure it is in the next
draft if one is required, either way all of that text will be removed by
IANA, who has also just sent back their review of the actions required.

On your second comment, currently being published as an RFC is a draft
reserving as0 in a similar fashion, so I do think it's most appropriate as a
second doc.. and I really have trouble tying these reservations to a RFC
about Private ASN's.   If no doc is published, the good news is that IANA
has already reserved the last number (with no justification).  Again, if
IESG or others feel strongly it should be in this draft, I will try to work
out some text to justify their reservations...

Thanks!

Jon

-----Original Message-----
From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
Sent: Monday, February 18, 2013 8:12 PM
To: Jon Mitchell (GNS)
Cc: General Area Review Team;
draft-ietf-idr-as-private-reservation.all@tools.ietf.org
Subject: RE: Gen-art last call review of
draft-ietf-idr-as-private-reservation-03

On Mon, 2013-02-18 at 15:26 +0000, Jon Mitchell (GNS) wrote:
> Elwyn -
> 
> Thanks for your review. 
:-)

>  The suggestion is being made to IANA who owns the assignment and was 
> discussed at length in the working group with rough consensus.
As specified in the registry, allocations in this registry are either by
IETF Concensus (i.e. a suitable RFC such as this draft is intended to
be) or request from a RIR. Thus it isn't a matter of suggesting to IANA but
telling them what the IETF want done - so this draft should be definitive -
and what you said about WG concensus constitutes the values to be used
unless somebody else in the IETF manages to alter the concensus which seems
unlikely.
  
> IANA will replace the suggested values into TBDX values below that 
> text if IESG approves.  This text will not be in the RFC, it's to be 
> stricken from the final document by RFC Editor (I was attempting to 
> write this text in alignment with Section 5.1 of RFC 5226) .
Yes, that's fine and as expected.
> 
> On the final ASN in the range, this is in accordance with like 
> reservation of the existing 2 byte Private ASN reservations, where the 
> final ASN in that space is not utilized either (except for well-known 
> community values).  Also, a case was made that code implementations 
> tend to have issues with final number usage if using incorrect 
> variable types for storage.  That said, the small discussion on and 
> off list about this resolved that if we wanted to formalize the 
> reservation of the last ASN of both the 2 byte space 65535 and the 4 
> byte space 4294967295, probably a separate draft should be constructed 
> detailing the logic behind these as they have nothing to do with 
> Private ASN's per se and have already been marked as Reserved by IANA 
> as you noted.  I'm open to IESG direction if we want to take a 
> different approach on this...
Publishing a separate draft seems a bit overkill but clearly that's not my
decision. ;-)

Regards,
Elwyn
> 
> Cheers,
> 
> Jon
> 
> -----Original Message-----
> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
> Sent: Friday, February 15, 2013 4:15 AM
> To: General Area Review Team
> Cc: draft-ietf-idr-as-private-reservation.all@tools.ietf.org
> Subject: Gen-art last call review of
> draft-ietf-idr-as-private-reservation-03
> 
> 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-as-private-reservation-03.txt
> Reviewer: Elwyn Davies
> Review Date: 15 February 2013
> IETF LC End Date: 22 February 2013
> IESG Telechat date: (if known) -
> 
> Summary: Ready for the IESG.
> 
> Nits/editorial comments:  The draft is not actually definitive about range
of values to be allocated - the range in s10 is just a 'suggestion'.  Who is
actually making the decision about the range?
> 
> Aside: I noted that the highest possible 32 bit number (4294967295 =
> 0xFFFFFFFF) is excluded from the proposed range.  This is marked as 
> reserved in the IANA table but AFAICS this reserved item does not have 
> a specification associated with the reservation.  This document would 
> be an opportunity to explicitly mention that the topmost value is 
> reserved (for future expansion? :-) )
> 
> 



From dean.willis@softarmor.com  Thu Feb 21 08:58:02 2013
Return-Path: <dean.willis@softarmor.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 0236621F8EAA for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 08:58:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.403, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nTXLKEsvWsst for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 08:58:00 -0800 (PST)
Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by ietfa.amsl.com (Postfix) with ESMTP id 89C8321F8EAF for <gen-art@ietf.org>; Thu, 21 Feb 2013 08:58:00 -0800 (PST)
Received: by mail-vc0-f169.google.com with SMTP id n10so5885532vcn.14 for <gen-art@ietf.org>; Thu, 21 Feb 2013 08:57:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=h54SOFZgTHb93eoZw56s32BUqoU6XfXBnbVCBTPvPWw=; b=fS3AP8Gt5gHaO0PXkeYi45QJfMs7XYA7wv7qDbIvU1tuGnmkeBUmlBUe3ipx/FfiyX MX17TaR1UX4byjKJ3lE7LT7yOEuCvYMgqZdn9mNB/k5ImlYaBdlh49S0WojWx+Zw6w35 ZsvR3ajZpqPVxzfVGhOeyYDlR4XYd9U1RWzok=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=h54SOFZgTHb93eoZw56s32BUqoU6XfXBnbVCBTPvPWw=; b=maktPmmXI+y7lQb4U31QBZ0zxmJi+i8xcVFhO6+KwiyyW4I9ACLS7bZIG19pbGxiVp Hng7pLch19lKXyzQbxwrGYw8nggudh8u28VNJ2I6JvqO9vpnVbDGkw5OdxIR4RXtpqi+ lJIz6KUXsWW1503GZdyBW/8jZnHvoOY5NlL9dOFnWvcupO/W0puM8D6nFL2fInJuX9dv wR6qPyp4LUxuCEuNU0W2+sNWVWHpzdYOBQntqKyftz+2eEwLNo1WdJt3g/8e8ThuKrWb 0e9/5ZUlRjcugmPr81EqfUimeUG4OoKFzWI8eRTIclZVW5xWfezNNQ3PYawKRBVNp2EO juuA==
MIME-Version: 1.0
X-Received: by 10.58.28.169 with SMTP id c9mr32634715veh.5.1361465871508; Thu, 21 Feb 2013 08:57:51 -0800 (PST)
Received: by 10.58.46.17 with HTTP; Thu, 21 Feb 2013 08:57:51 -0800 (PST)
In-Reply-To: <51261973.6000106@ericsson.com>
References: <CAHBDyN6-J6SgnNqA1ZTcnFsLGzaeD2wGD5W58rte3A-vn2SQiA@mail.gmail.com> <512415E5.1060702@petit-huguenin.org> <1D82BACC-F763-4A4F-9E3C-61AACB3FB440@brianrosen.net> <5124E842.1070201@petit-huguenin.org> <5124EFEA.1040302@ericsson.com> <CAHBDyN5hOh48XJrvoEnu_eQU4AE_QxxomxbVti8m=ycT2A3ryg@mail.gmail.com> <51261973.6000106@ericsson.com>
Date: Thu, 21 Feb 2013 10:57:51 -0600
Message-ID: <CAOHm=4uHFKF+v__5_K4iJVmD_Zr9zGKMOom0vEwpA1jrgdyX=A@mail.gmail.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnWupzGTtKUq9aImSy8lcsEh6ItTu/nWrlTY6jlJ0Ny00n6khpy0FUWUNXh1KWwcGc2qIG6
Cc: Marc Petit-Huguenin <marc@petit-huguenin.org>, draft-ietf-p2psip-base.all@tools.ietf.org, Brian Rosen <br@brianrosen.net>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review: draft-ietf-p2psip-base-24
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 Feb 2013 16:58:02 -0000

Mary's very right about the need to get Henning's further review
processed ahead of the RFC-Ed work, and I like Gonzalo's suggestion
for dealing with it.

On Thu, Feb 21, 2013 at 6:56 AM, Gonzalo Camarillo
<Gonzalo.Camarillo@ericsson.com> wrote:
> Hi Mary,
>
> yes, as you know, I know Henning very well. I will talk with him about
> this. A potential outcome is that we get this document in the Approved
> Point Raised state and then we get him to review it. In any case, thanks
> for the advice!
>
> Cheers,
>
> Gonzalo
>
> On 21/02/2013 2:49 PM, Mary Barnes wrote:
>> Certainly - but it's a pay now or a pay later unless you can convince
>> Henning that he doesn't need to do his usual careful review of a
>> document with his name.  This suggestion is based on my experience
>> with the XCON protocol document. The level of complexity and density
>> of this specification is significantly higher than the XCON document.
>> It will be a huge challenge for the RFC editor - I think even Alice
>> would find it so.  Having to deal with a potential large number of
>> edits at that stage has the potential to break or changes things that
>> were so carefully fixed.
>>
>> Regards,
>> Mary.
>>
>> On Wed, Feb 20, 2013 at 9:46 AM, Gonzalo Camarillo
>> <Gonzalo.Camarillo@ericsson.com> wrote:
>> Hi,
>>
>> there is no way Henning is going to review this document in the next
>> 24 hours. So, do whatever you need to do and I will talk with Henning
>> later.
>>
>> Thanks,
>>
>> Gonzalo
>>
>> On 20/02/2013 5:14 PM, Marc Petit-Huguenin wrote:
>>>>> On 02/20/2013 06:20 AM, Brian Rosen wrote:
>>>>>> I will contact Henning
>>>>>
>>>>> I was in the process yesterday evening of doing a review according
>>>>> to the link Mary send when Roland's review arrived, which basically
>>>>> killed any chance of doing that.  So either Henning send me today a
>>>>> list of things to fix, or I'll do the review later, but that
>>>>> probably be after the IESG telechat.
>>>>>
>>>>>
>>>>>> Brian
>>>>>
>>>>>> On Feb 19, 2013, at 7:16 PM, Marc Petit-Huguenin
>>>>>> <marc@petit-huguenin.org> wrote:
>>>>>
>>>>>> Thanks Mary.  I start working on this immediately.
>>>>>
>>>>>> On 02/19/2013 04:06 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-p2psip-base-24 Reviewer:  Mary Barnes
>>>>>>>>> Review Date: 19 February 2013 Previous Review Date (-23):
>>>>>>>>> 14 December 2012 Original Review Date (-17): 6 August 2011
>>>>>>>>> IETF LC End Date: 22 July 2011 IETF 2nd LC End Date: 19
>>>>>>>>> February 2013
>>>>>>>>>
>>>>>>>>> Summary: Almost Ready.  This version is in significantly
>>>>>>>>> better shape than the previous versions.
>>>>>>>>>
>>>>>>>>> Comments: ========= I reviewed against my review of the -23
>>>>>>>>> up through section 6.  I reviewed beyond section 6 of this
>>>>>>>>> version (section 5 of -17, section 6 of -23) against my
>>>>>>>>> comments on the -17, since I had not re-reviewed those
>>>>>>>>> against the -23.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> General: --------
>>>>>>>>>
>>>>>>>>> I still *strongly* recommend that you ensure Henning has
>>>>>>>>> reviewed this document *before* it gets into the RFC
>>>>>>>>> editor's queue.  The last RFC I had published with Henning
>>>>>>>>> as a co-author had much more extensive changes suggested
>>>>>>>>> during AUTH 48 than I found acceptable. If all the
>>>>>>>>> co-authors have not reviewed and approved the draft before
>>>>>>>>> it goes into the RFC editor's queue, then the document
>>>>>>>>> should not go into the RFC editor's queue. He has fairly
>>>>>>>>> strict (and quite accurate) views on grammar and structure
>>>>>>>>> but it really isn't good to have so many changes go in at
>>>>>>>>> AUTH48 as there is a risk of introducing true technical
>>>>>>>>> bugs or changing something that was carefully crafted to
>>>>>>>>> achieve WG consensus:
>>>>>>>>> http://www.cs.columbia.edu/~hgs/etc/writing-bugs.html Note,
>>>>>>>>> that there some are cases of incorrect grammar that I have
>>>>>>>>> not identified because I think the RFC editor can fix,
>>>>>>>>> however, Henning may have different views on this.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Major: ------ - [-17, section 10.5] Section 11.5, 3rd para:
>>>>>>>>> text uses the phrase "it can note the Node-ID in the
>>>>>>>>> response and use this Node-ID to start sending requests".
>>>>>>>>> It's not clear whether the use of the Node-ID is a MAY or a
>>>>>>>>> MUST.    [Note: Marc's response to this was that it's an
>>>>>>>>> open issue, but this should be clarified prior to
>>>>>>>>> publication].
>>>>>>>>>
>>>>>>>>> Minor: ------ - idnits identifies 5 errors (downrefs).  I
>>>>>>>>> will note that in the PROTO write-up it was noted that
>>>>>>>>> those should likely be moved to Informative.
>>>>>>>>>
>>>>>>>>> - [-17] Section 1.2.1, 2nd paragraph: I don't understand
>>>>>>>>> the example as to why a single application requires
>>>>>>>>> multiple usages - i.e, why voicemail? Isn't the intent to
>>>>>>>>> say that an application might need to use both SIP and XMPP
>>>>>>>>> - i.e., you wouldn't define a "usage" for an application,
>>>>>>>>> would you? [While Cullen responded to this comment with an
>>>>>>>>> explanation, there was no change to clarify the text and
>>>>>>>>> Marc's response didn't help clarify my concern]
>>>>>>>>>
>>>>>>>>> - Section 3.3, 2nd paragraph after the capability bullet
>>>>>>>>> list, next to last sentence.  There is at least an article
>>>>>>>>> missing from this sentence and it reads rather awkwardly.
>>>>>>>>> Perhaps changing to something like: OLD: If there is a
>>>>>>>>> failure on the reverse path caused by topology change since
>>>>>>>>> the request was sent, this will be handled by the
>>>>>>>>> end-to-end retransmission of the response as described in
>>>>>>>>> Section 6.2.1. NEW: Note that a failure on the reverse path
>>>>>>>>> caused by a topology change after the request was sent,
>>>>>>>>> will be handled by the end-to-end retransmission of the
>>>>>>>>> response as described in Section 6.2.1.
>>>>>>>>>
>>>>>>>>> - [-17] Section 3.3, last paragraph.  Add a reference to
>>>>>>>>> 5.4.2.4 after "RouteQuery method"
>>>>>>>>>
>>>>>>>>> - Section 3.4, last paragraph, 3rd sentence: "that the
>>>>>>>>> specified by the algorithm" should be something like "than
>>>>>>>>> specified by the algorithm".
>>>>>>>>>
>>>>>>>>> - [-23] Section 6.6:  All my previous concerns were
>>>>>>>>> addressed, except, the Note to implementors paragraph still
>>>>>>>>> seems out of context - it should be deleted or this section
>>>>>>>>> should be restructured so it is in context.
>>>>>>>>>
>>>>>>>>> - [-17, section 11] Section 12, Second paragraph, 3rd
>>>>>>>>> sentence says that "It gets routed to the admitting peer
>>>>>>>>> (AP), yet the flow shows that the message first gets routed
>>>>>>>>> to the PP and then onto AP. It would be helpful if that
>>>>>>>>> were clarified.   [Note: Marc's response indicated that he
>>>>>>>>> thought this was fixed in the -23, however, the diff shows
>>>>>>>>> no changes to that specific text between the -17 and the
>>>>>>>>> -24 ]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Nits: -----
>>>>>>>>>
>>>>>>>>> - Section 1.2.5, 2nd para, last sentence: this sentence is
>>>>>>>>> a bit tough to interpret on a first read.  I would suggest
>>>>>>>>> rewording something like the following: OLD: This layer is
>>>>>>>>> to the Message Transport Layer as link- level congestion
>>>>>>>>> control and retransmission in modern wireless networks is
>>>>>>>>> to Internet transport protocols. NEW: The relation of this
>>>>>>>>> layer to the Message Transport Layer "is similar to"|"can
>>>>>>>>> be likened to" the relation of the link- level congestion
>>>>>>>>> control and retransmission in modern wireless networks to
>>>>>>>>> Internet transport protocols.
>>>>>>>>>
>>>>>>>>> - Section 3.4, last paragraph, 4th sentence: "in accord" ->
>>>>>>>>> "in accordance"
>>>>>>>>>
>>>>>>>>> - Section 10.1, 2nd paragraph, 5th sentence: "can be
>>>>>>>>> thought of a doubly-linked list" -> "can be thought of as a
>>>>>>>>> doubly-linked list"
>>>>>>>>>
>>>>>>>>> - Section 15, last paragraph: "help resolve" -> "helped
>>>>>>>>> resolve"
>>>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>
>

From fluffy@cisco.com  Thu Feb 21 12:36:05 2013
Return-Path: <fluffy@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 017C721F8EC6 for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 12:36:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.58
X-Spam-Level: 
X-Spam-Status: No, score=-110.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RGDnkFjUfccG for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 12:36:04 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 72CDB21F8EE6 for <gen-art@ietf.org>; Thu, 21 Feb 2013 12:36:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=142; q=dns/txt; s=iport; t=1361478964; x=1362688564; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=1QfuJc6kqIXDFWok5jQyxOfktnUJOywdvXcl4k594Uk=; b=P86smwyEsmO4qp2LW/sEheHySeYLTWat9Ia/IafwyaooK7sSSMcyUB95 l+Dm5a8ohnuH9l+LxQpnRKFn8BdAyQR/9QaKucXxh7jbt4dsJ/xpCkWKH /R+vouotyl7yw3vxBctB8KJ2cw+9L7F05heXpwnAx39WXHZ3GHdn2HS4h 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: At4FAGaEJlGtJV2Z/2dsb2JhbABFhge7BYEFFnOCHwEBAQMBeQULAgEIIiQyJQIEDgUIiAQGvymOXTEHgl9hA4gznmGDB4In
X-IronPort-AV: E=Sophos;i="4.84,711,1355097600"; d="scan'208";a="179827771"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP; 21 Feb 2013 20:36:04 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r1LKa4I3014818 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Feb 2013 20:36:04 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.155]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Thu, 21 Feb 2013 14:36:03 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Dean Willis <dean.willis@softarmor.com>
Thread-Topic: Gen-ART LC Review: draft-ietf-p2psip-base-24
Thread-Index: AQHOEHMRcV6Tn4kkl0ePgmuGSjMk0w==
Date: Thu, 21 Feb 2013 20:36:03 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1133F6D0E@xmb-aln-x02.cisco.com>
References: <CAHBDyN6-J6SgnNqA1ZTcnFsLGzaeD2wGD5W58rte3A-vn2SQiA@mail.gmail.com> <512415E5.1060702@petit-huguenin.org> <1D82BACC-F763-4A4F-9E3C-61AACB3FB440@brianrosen.net> <5124E842.1070201@petit-huguenin.org> <5124EFEA.1040302@ericsson.com> <CAHBDyN5hOh48XJrvoEnu_eQU4AE_QxxomxbVti8m=ycT2A3ryg@mail.gmail.com> <51261973.6000106@ericsson.com> <CAOHm=4uHFKF+v__5_K4iJVmD_Zr9zGKMOom0vEwpA1jrgdyX=A@mail.gmail.com>
In-Reply-To: <CAOHm=4uHFKF+v__5_K4iJVmD_Zr9zGKMOom0vEwpA1jrgdyX=A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <09E072F4D8C39F4AAE1E98189EFF0F4D@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Marc Petit-Huguenin <marc@petit-huguenin.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "<draft-ietf-p2psip-base.all@tools.ietf.org>" <draft-ietf-p2psip-base.all@tools.ietf.org>, Brian Rosen <br@brianrosen.net>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review: draft-ietf-p2psip-base-24
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 Feb 2013 20:36:05 -0000

On Feb 21, 2013, at 9:57 AM, Dean Willis <dean.willis@softarmor.com> wrote:

> I like Gonzalo's suggestion
> for dealing with it.

+1


From mahoney@nostrum.com  Thu Feb 21 14:58:39 2013
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 B5A1C21E803D for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 14:58:39 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wirlj5f7egVp for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 14:58:39 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3586621E8039 for <gen-art@ietf.org>; Thu, 21 Feb 2013 14:58:38 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r1LMwbCv044656 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 21 Feb 2013 16:58:38 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <5126A69D.5060302@nostrum.com>
Date: Thu, 21 Feb 2013 16:58:37 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
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 (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-02-21
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 Feb 2013 22:58:39 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Alexey Melnikov   2013-03-07   draft-ietf-idr-deprecate-dpa-etal-00 **
  
Martin Thomson    2013-03-19   draft-schaad-pkix-rfc2875-bis-07 *

Meral Shirazipour 2013-03-06   draft-ietf-appsawg-acct-uri-03

Peter McCann      2013-03-07   draft-ietf-tsvwg-byte-pkt-congest-09


* 2nd LC due to downrefs
** 2nd LC due to change from Informational to Proposed Standard



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

And 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


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 Feb 21 15:04:21 2013
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 0BA4B21E803D for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 15:04:21 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0i1iKcTHrnO0 for <gen-art@ietfa.amsl.com>; Thu, 21 Feb 2013 15:04:20 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7222721E8039 for <gen-art@ietf.org>; Thu, 21 Feb 2013 15:04:20 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r1LN4I5Q045355 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 21 Feb 2013 17:04:19 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <5126A7F2.1050506@nostrum.com>
Date: Thu, 21 Feb 2013 17:04:18 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
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 (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2013-02-28 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, 21 Feb 2013 23:04:21 -0000

Hi all,

The following reviewers have assignments:

Reviewer             LC end      Draft
------------------------------------------------------------------------------------
Ben Campbell         2013-02-28  draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04

Dan Romascanu        2013-02-24  draft-cardenas-dff-09 **

Francis Dupont       2013-02-25  draft-ietf-dhc-secure-dhcpv6-07

Joel Halpern         2013-02-26  draft-ietf-tcpm-proportional-rate-reduction-04 **

Kathleen Moriarty    2013-02-27  draft-ietf-geopriv-flow-identity-01

Mary Barnes          2013-01-16  draft-ietf-6man-ipv6-atomic-fragments-03

Roni Even            2013-02-28  draft-harkins-brainpool-ike-groups-04 **

Suresh Krishnan      2013-02-28  draft-eastlake-additional-xmlsec-uris-09


* Earlier draft reviewed
** Already reviewed



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

And 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

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 benl@google.com  Fri Feb 22 03:17:53 2013
Return-Path: <benl@google.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 0374C21F8E8B for <gen-art@ietfa.amsl.com>; Fri, 22 Feb 2013 03:17:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d5gR5bwOFCX2 for <gen-art@ietfa.amsl.com>; Fri, 22 Feb 2013 03:17:52 -0800 (PST)
Received: from mail-ie0-x22d.google.com (ie-in-x022d.1e100.net [IPv6:2607:f8b0:4001:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 55C9D21F8E7B for <gen-art@ietf.org>; Fri, 22 Feb 2013 03:17:52 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id 9so548507iec.4 for <gen-art@ietf.org>; Fri, 22 Feb 2013 03:17:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Qgv6TfJpTMh9my6i2QMqH4OHHwEJ+lVMb3mcxKFL++Y=; b=mD2U7O2G/44fv4ZaZjXWcPUd2tSdtmeL84IeJMvhV4HPgYtumP+loy4RAgD6EZBt6o QxTiEgTuJ/O95RA9XB7IA52jFZaY777RgQHrwEGbj6lr7YBqt++ybEqhtzpTZTERSIrR SxVqkxtoDXEqO8E2ompILR5cAU3SPL0tDPBvSe/yE/lTSDBlC4OLj8INsVXulMq+a23p p2ZGPGfItQn6DPvxtnbCQgTd3ahpLE3ydM1rSzDhpRtfnZ371C7Ee3uqlysehrFYg3Pl V2X/cSwAgIfVL2hPcvsL4ewmmboO/PTmRNHoWSOwPe3Lj5rWYz1SrrcoQ/vxmVXvPFvp vooA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=Qgv6TfJpTMh9my6i2QMqH4OHHwEJ+lVMb3mcxKFL++Y=; b=K9TgRZtDd7BJMO413FARSWN2HyJYPwjO2Pkri/6c63dlf3v2QAtQ/FjBxz4Z9AqqO6 M9dLoxygawwpVrskAOs2Xcnkc0bBKIakbPj/Kh8LGVYpFUC3v1PpJF5sHWPKsGUr/7OA 9zBfOFnTpFWpHbZegOiimjSwJT5k/oHhKIjM/krJDP9a/4uhtI0NFSVcMcP8ombjBOnh M1rA/Udn6bbZcNn+mtuJZUM2XrCyeTYYfpPqkcBNjjaLZs8kgxwQxLUNoAGd1LgfLTNo WzC9kNuwZt2mIyA85+K6fHerWMg3NAZIlbUpzNtOUCAMNSKonkFH5/AgGHIek7zcF5x+ zBmQ==
MIME-Version: 1.0
X-Received: by 10.50.153.198 with SMTP id vi6mr14912231igb.112.1361531871938;  Fri, 22 Feb 2013 03:17:51 -0800 (PST)
Received: by 10.64.140.71 with HTTP; Fri, 22 Feb 2013 03:17:51 -0800 (PST)
In-Reply-To: <201302181453.r1IErhWQ036131@givry.fdupont.fr>
References: <201302181453.r1IErhWQ036131@givry.fdupont.fr>
Date: Fri, 22 Feb 2013 11:17:51 +0000
Message-ID: <CABrd9SQP2qegcL=R6rrRZj5UQHjMk8TjfTiHWWmGcamnO_ojfg@mail.gmail.com>
From: Ben Laurie <benl@google.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>,  "therightkey@ietf.org" <therightkey@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQn8tDJgljubH9iL/648U8ztjH/uTvjymPsgbXFrg19tAuDRvVGSUSW3WTgye0coAQ66mvPWSraFDIy7q6+jwxUaZPiDmLaQ/CCecKx3JgL27DIPkKCJ2u9lCp0uwJiUhXzI0viNCsqU2vL1R33sptgwZCyFQs5xDnohNowEYgzfDkbgkcy9PRoxdjzXL6i+jbq3QHkT
X-Mailman-Approved-At: Fri, 22 Feb 2013 05:08:25 -0800
Cc: gen-art@ietf.org, draft-laurie-pki-sunlight.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-laurie-pki-sunlight-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: Fri, 22 Feb 2013 11:17:53 -0000

On 18 February 2013 14:53, Francis Dupont <Francis.Dupont@fdupont.fr> 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-laurie-pki-sunlight-07.txt
> Reviewer: Francis Dupont
> Review Date: 20130208
> IETF LC End Date: 20130226
> IESG Telechat date: unknown
>
> Summary: Almost Ready
>
> Major issues: None
>
> Minor issues:
>  - section 2 is not enough accurate, for instance:
>   * the critical [k1:k2] notation is introduced after its first use, IMHO
>    it is the primary one, i.e., [n] is a short hand for [0:n]

Notation is rather tricky here, but I don't think that saying D[n] is
shorthand for D[0:n] adds clarity. This is because D[k:n] becomes
D[n-k] on recursion. Saying D[k:n] is the same as D[0:n-k] is just
confusing (and, indeed, wrong).

>   * the largest power of two must be strictly smaller, not just smaller.

There is no difference between "strictly smaller" and "smaller" (in
contrast to "decreasing" and "strictly decreasing").

>    Without this critical detail recursion rules don't work for n = 2^m
>  Unfortunately there is no wikipedia or equivalent web page where to refer to
>  so the document is the place where all gory details have to be...
>
>  - the Maximum Merge Delay (MMD) is an important parameter but I can't find
>   where is the way users get its value, nor any recommendation for it.

We anticipate that this will be published in some kind of human readable policy.

> Nits/editorial comments:
>  - 1 page 4: CA is not a well known abbrev so please introduce it
>   (cf http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt)

Fixed.

>  - 1 page 4: it is a general mechanism but what are its constraints at
>   the exception of the intended usage. For instance is the mechanism
>   applicable to any end entity public key certificate? or larger??

I don't know what this comment refers to.

>  - 1 page 5: misbehaviours -> misbehaviors
>   (and 3.3 page 16, and others too)

I am not American.

>  - 1 page 5: e.g. -> e.g.,

Fixed.

>  - 2.1.1 page 6: i.e. -> i.e.,

Fixed.

>  - 2.1.1 page 7 and 2.1.2 page 8: the wording "the length (k2 - k1) list"
>   is IMHO a bit uncommon even I can understand it.

It's maths.

>  - 2.1.4 page 10: using a key of at least 2048 bits. ->
>   using a public key of at least 2048 bits. (or a modulus as it is for RSA?)

The public and private keys are the same length in RSA (and the length
is the length of the modulus).

>  - 3 pages 13, 14, etc: what is the language used for ASN.1? It is not
>   ASN.1 itself, nor C?

The format of certificates is defined elsewhere. The name ASN.1Cert
(which is what I assume you refer to) is taken from RFC 5246.

>  - 3.1 page 12: accomodate -> accommodate

Fixed.

>  - 3.1 page 13: parenthesis around 65535 are not necessary (i.e, they
>   are insipid and stupid :-)

I love you, too.

In fact, they are required, see section 4.5 of RFC 5246.

>  - 3.1 page 13: submmited -> submitted

Fixed.

>  - 3.2 page 14: opaque TBSCertificate<1..2^16-1> add final ';'

Fixed.

>  - 4.6 page 22: honour -> honor

No.

>  - 4.6 page 22: convering -> covering?

Fixed.

> BTW if the document creates new OID perhaps they should be put in an annex?

I am not aware of a requirement to do so.

Thanks for your comments!

> Regards
>
> Francis.Dupont@fdupont.fr
>
> PS: I noted there are still some LC comments in the ML.

I am not aware of any I have missed.

From kathleen.moriarty@emc.com  Sat Feb 23 06:35:56 2013
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 B89E121F8F27; Sat, 23 Feb 2013 06:35:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.155
X-Spam-Level: 
X-Spam-Status: No, score=-2.155 tagged_above=-999 required=5 tests=[AWL=0.443,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ujBqt6KRRu2G; Sat, 23 Feb 2013 06:35:55 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 28B2F21F867D; Sat, 23 Feb 2013 06:35:54 -0800 (PST)
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 r1NEZrv3025588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 23 Feb 2013 09:35:53 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sat, 23 Feb 2013 09:35:40 -0500
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r1NEZdmr004817; Sat, 23 Feb 2013 09:35:40 -0500
Received: from mx15a.corp.emc.com ([169.254.1.74]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Sat, 23 Feb 2013 09:35:39 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-geopriv-flow-identity.all@ietf.org" <draft-ietf-geopriv-flow-identity.all@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Date: Sat, 23 Feb 2013 09:35:38 -0500
Thread-Topic: Gen-ART review of draft-ietf-geopriv-flow-identity-01
Thread-Index: Ac4R0wwskUgHKWqnT2Kg1TiPlfdWIw==
Message-ID: <F5063677821E3B4F81ACFB7905573F24D625C2EC@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_F5063677821E3B4F81ACFB7905573F24D625C2ECMX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ray.bellis@nominet.org.uk" <ray.bellis@nominet.org.uk>
Subject: [Gen-art] Gen-ART review of draft-ietf-geopriv-flow-identity-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: Sat, 23 Feb 2013 14:35:56 -0000

--_000_F5063677821E3B4F81ACFB7905573F24D625C2ECMX15Acorpemccom_
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-geopriv-flow-identity-01
Reviewer: Kathleen Moriarty
Review Date: February 23, 2013
IETF LC End Date: Thursday
IESG Telechat date: (if known)

Summary:  The draft is ready for publication, it is well written and the XM=
L schema in section 4 validates properly.


Abstract:
   RFC 6155 specifies an extension for the HTTP-Enabled Location
   Delivery (HELD) Protocol allowing the use of an IP address and port
   number to request a Device location based on an individual packet
   flow.

   However, certain kinds of NAT require that identifiers for both ends
   of the packet flow must be specified in order to unambiguously
   satisfy the location request.

   This document specifies an XML Schema and URN Sub-Namespace for a
   Flow Identity Extension for HELD to support this requirement.

   This document updates RFC 6155 by deprecating the port number
   elements specified therein.

Major issues:

Minor issues:

Nits/editorial comments:



--_000_F5063677821E3B4F81ACFB7905573F24D625C2ECMX15Acorpemccom_
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-geopriv-flow-identity-01</div>
<div>Reviewer: Kathleen Moriarty</div>
<div>Review Date: February 23, 2013</div>
<div>IETF LC End Date: Thursday</div>
<div>IESG Telechat date: (if known)</div>
<div>&nbsp;</div>
<div>Summary:&nbsp; The draft is ready for publication, it is well written =
and the XML schema in section 4 validates properly.</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div><font face=3D"Courier New, monospace" size=3D"2">Abstract:</font></div=
>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; RFC 6155=
 specifies an extension for the HTTP-Enabled Location</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; Delivery=
 (HELD) Protocol allowing the use of an IP address and port</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; number t=
o request a Device location based on an individual packet</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; flow.</f=
ont></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; However,=
 certain kinds of NAT require that identifiers for both ends</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; of the p=
acket flow must be specified in order to unambiguously</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; satisfy =
the location request.</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; This doc=
ument specifies an XML Schema and URN Sub-Namespace for a</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; Flow Ide=
ntity Extension for HELD to support this requirement.</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; This doc=
ument updates RFC 6155 by deprecating the port number</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;&nbsp; elements=
 specified therein.</font></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">&nbsp;</font></div>
</font>
</body>
</html>

--_000_F5063677821E3B4F81ACFB7905573F24D625C2ECMX15Acorpemccom_--

From mary.ietf.barnes@gmail.com  Sat Feb 23 09:43:44 2013
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 B3F6121F8E50 for <gen-art@ietfa.amsl.com>; Sat, 23 Feb 2013 09:43:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.573
X-Spam-Level: 
X-Spam-Status: No, score=-103.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h9l2GiLwQrQg for <gen-art@ietfa.amsl.com>; Sat, 23 Feb 2013 09:43:44 -0800 (PST)
Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by ietfa.amsl.com (Postfix) with ESMTP id 38C3721F8E4F for <gen-art@ietf.org>; Sat, 23 Feb 2013 09:43:44 -0800 (PST)
Received: by mail-qc0-f182.google.com with SMTP id k19so733563qcs.27 for <gen-art@ietf.org>; Sat, 23 Feb 2013 09:43:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=UR9KUsWFzh4kISolJam2i8nnEgjXR2Jdka0a8aY9Gig=; b=OxHj/adMoFRcy+h9IOknvUJB+F9tjt7J5vAsUBtlQb4G+qDtGzezYdqtFWkkOKUp1Z xTc877ZlVD7ti2RWRQNs3xdqdxVtpby18fWpNc+hGmQip6KTN2GGoKDoNzdfZCb/ZStq EgpJDylwNst0BZuW8wnoZc2/4+HFzdDwwTztB/bETecwELgU/R4IhbwnCtXyuErWaEbe x1RJWJf36uvc29HnSBwVRED08xELBqHAew5JsODg5o0KIEw4wGVqUCMsC2CNKOEzVTPO TJs8jQW5UxkBK4oHSRTX2WtfTX0kY3B0yHfwSaUpkNUrgC0EiBu5THckQLMXsc2VS0O1 s4bQ==
MIME-Version: 1.0
X-Received: by 10.49.72.136 with SMTP id d8mr3706690qev.62.1361641423669; Sat, 23 Feb 2013 09:43:43 -0800 (PST)
Received: by 10.49.131.199 with HTTP; Sat, 23 Feb 2013 09:43:43 -0800 (PST)
In-Reply-To: <CAHBDyN6dcHoghqic1s0Mtk-o7gv0b8TndVZeRnsErFw_Aj15yg@mail.gmail.com>
References: <CAHBDyN6dcHoghqic1s0Mtk-o7gv0b8TndVZeRnsErFw_Aj15yg@mail.gmail.com>
Date: Sat, 23 Feb 2013 11:43:43 -0600
Message-ID: <CAHBDyN6HC0oXDfMp1pYgKEwXpYezYB89AJD19v9GLqBqT6ZtAg@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] Fwd: Gen-ART Review: draft-ietf-6man-ipv6-atomic-fragments-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: Sat, 23 Feb 2013 17:43:44 -0000

Oops, I just looked and I forget to send this to gen-art.

Mary.

---------- Forwarded message ----------
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Thu, Jan 24, 2013 at 11:09 AM
Subject: Gen-ART Review: draft-ietf-6man-ipv6-atomic-fragments-03
To: draft-ietf-6man-ipv6-atomic-fragments.all@tools.ietf.org


Sorry for the delay.

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-6man-ipv6-atomic-fragments-03
Reviewer:  Mary Barnes
Review Date:  24 Jan 2013
IETF LC End Date: 16 Jan 2013

Summary:  Ready.

From jmh@joelhalpern.com  Sat Feb 23 14:24:34 2013
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 D789C21F8DDC; Sat, 23 Feb 2013 14:24:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.263
X-Spam-Level: 
X-Spam-Status: No, score=-102.263 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ml5HELr8htXB; Sat, 23 Feb 2013 14:24:34 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id F2F8921F8D96; Sat, 23 Feb 2013 14:24:33 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id C1EB8A68DC; Sat, 23 Feb 2013 14:24:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 99EC81C090F; Sat, 23 Feb 2013 14:24:30 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-135-91.clppva.east.verizon.net [70.106.135.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id E532A1C0539; Sat, 23 Feb 2013 14:24:27 -0800 (PST)
Message-ID: <5129418E.5060502@joelhalpern.com>
Date: Sat, 23 Feb 2013 17:24:14 -0500
From: Joel Halpern <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: david.black@emc.com
References: <7C4DFCE962635144B8FAE8CA11D0BF1E055F69357F@MX14A.corp.emc.com> <4DCD4DEA.2050902@joelhalpern.com> <7C4DFCE962635144B8FAE8CA11D0BF1E055F6937FA@MX14A.corp.emc.com> <4DD142AE.5030409@joelhalpern.com> <7C4DFCE962635144B8FAE8CA11D0BF1E055F693A04@MX14A.corp.emc.com> <4DD15A40.2010209@joelhalpern.com>
In-Reply-To: <4DD15A40.2010209@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: savi@ietf.org, gen-art@ietf.org, christian.vogt@ericsson.com, jeanmichel.combes@gmail.com, joel.halpern@ericsson.com
Subject: Re: [Gen-art] [savi] Gen-ART review of draft-ietf-savi-threat-scope-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, 23 Feb 2013 22:24:35 -0000

Antiquity lives on.  This draft is back from the dead.
Somehow, it made it to the IESG review without my finishing addressing 
your comments.  My apologies for that.   I am trying to finish this off.

You will see Monday afternoon a new draft in the repository, with a 
section 4.1.2 on LACP, and a new paragraph in 5.2.3 to note the issues 
around (virtual) host relocation.

I hope that these properly address your old but very well-taken comments.

(I can send it to you if you want itsooner.)

Thank you,
Joel M. Halpern

On 5/16/2011 1:09 PM, Joel M. Halpern wrote:
> I can plan to make these changes at the end of the last call.
> Joel
>
> On 5/16/2011 12:56 PM, david.black@emc.com wrote:
>> Joel,
>>
>> I think the LACP discussion could be added to 4.1.1.
>>
>> I also think that there's a general theme that needs to be covered
>> across all of 4.1.1 - 4.1.4: When there are multiple traffic egress
>> points from a domain (4.1.1 - 4.1.4 cover four different types of
>> domains), the SAVI checks on all the egresses should be coordinated
>> and consistent in order to avoid surprises when the traffic switches
>> to a different egress point.
>>
>> Thanks,
>> --David
>>
>>> -----Original Message-----
>>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
>>> Sent: Monday, May 16, 2011 11:29 AM
>>> To: Black, David
>>> Cc: dmcpherson@verisign.com; fred@cisco.com;
>>> joel.halpern@ericsson.com; gen-art@ietf.org;
>>> savi@ietf.org; christian.vogt@ericsson.com; jeanmichel.combes@gmail.com
>>> Subject: Re: [savi] Gen-ART review of draft-ietf-savi-threat-scope-05
>>>
>>> Looking at the draft more carefully (when I am more awake, sorry), I
>>> think what you are asking is that more text be put in section 4.1, maybe
>>> a subsection?  That additional text would talk about placement on a
>>> switch that is not directly attached to the client, but is not as far
>>> upstream as the first hop router?  That text would include mention of
>>> the effect of spanning tree variation and LACP path changes.
>>>
>>> Sorry I was dense,
>>> Joel
>>>
>>> On 5/15/2011 9:45 PM, david.black@emc.com wrote:
>>>> Joel,
>>>>
>>>> If LACP is running active-passive across links to two different
>>>> switches, there may be no physical
>>> network node common to the currently active and currently passive
>>> paths for some traffic.  If SAVI
>>> is set up poorly, a switch to the currently passive link could remove
>>> validation checks or black-
>>> hole traffic that was flowing on the previously active link. For
>>> example, binding an IP address to a
>>> single port or ports on a single switch is insufficient in such an
>>> environment (address validation
>>> binding needs to span switches).
>>>>
>>>> The material in 5.2.4 on Multi-LAN Hosts looks like a starting point
>>>> - wrt SAVI, active-passive
>>> link aggregation across multiple switches can be a way to get into
>>> that sort of trouble on a single
>>> LAN (!).  Beyond that, I think the notion that SAVI checks should be
>>> consistent across alternate
>>> paths for the same traffic is applicable at other scopes, e.g., all
>>> egresses from a multi-homed
>>> network to the ISP networks involved.
>>>>
>>>> Thanks,
>>>> --David
>>>>
>>>>> -----Original Message-----
>>>>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
>>>>> Sent: Friday, May 13, 2011 11:28 AM
>>>>> To: Black, David
>>>>> Cc: dmcpherson@verisign.com; fred@cisco.com;
>>>>> joel.halpern@ericsson.com; gen-art@ietf.org;
>>>>> savi@ietf.org; christian.vogt@ericsson.com;
>>>>> jeanmichel.combes@gmail.com
>>>>> Subject: Re: [savi] Gen-ART review of draft-ietf-savi-threat-scope-05
>>>>>
>>>>> Thank you David.
>>>>> I think I understand the second part of your comment (about
>>>>> multi-instance hosts), and will have to look at the document more
>>>>> to see
>>>>> how to address that.
>>>>>
>>>>> I am not sure I understand what the question is regarding the LACP /
>>>>> link group issue.  Is this really different from the issues that arise
>>>>> whenever the SAVI functionality is not on the leaf switch?  Where
>>>>> in the
>>>>> document do you think it would help to discuss this?
>>>>>
>>>>> Thank you,
>>>>> Joel
>>>>>
>>>>> On 5/13/2011 1:03 AM, 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-savi-threat-scope-05
>>>>>> Reviewer: David L. Black
>>>>>> Review Date: 12 May 2011
>>>>>> IETF LC End Date: 18 May 2011
>>>>>>
>>>>>> Summary: This draft is on the right track, but has open issues,
>>>>>> described in the review.
>>>>>>
>>>>>> This draft discusses the threats and deployment environment for IP
>>>>>> source
>>>>>> address validation with particular attention to finer-grain
>>>>>> validation that
>>>>>> could be used within a network to validate IP addresses closer to
>>>>>> the sources
>>>>>> of network traffic than ingress to an ISP's network.
>>>>>>
>>>>>> Major issues:
>>>>>>
>>>>>> There is no discussion of link teaming or aggregation (e.g., via
>>>>>> LACP); this
>>>>>> may affect source address validation functionality by requiring
>>>>>> the same
>>>>>> validation checks on all aggregated ports.  An important case to
>>>>>> discuss
>>>>>> is where the aggregated host links are connected to ports on
>>>>>> different switches
>>>>>> (e.g., in an active/passive configuration).
>>>>>>
>>>>>> The discussion of multi-instance hosts in section 5.2.3 is incomplete
>>>>>> in several important aspects:
>>>>>>
>>>>>> (1) Some of the software switch implementations are single
>>>>>> instance switches
>>>>>> whose implementation is distributed across multiple physical
>>>>>> servers.  This
>>>>>> results in concerns similar to the link aggregation discussion above.
>>>>>>
>>>>>> (2) Live migration of virtual machines among physical servers causes
>>>>>> relocation of MAC addresses across switch ports.  A so-called
>>>>>> "gratuitous ARP"
>>>>>> is often used to inform the network of the MAC address move;
>>>>>> port-based
>>>>>> source address validation information needs to move in response to
>>>>>> such ARPs.
>>>>>>
>>>>>> (3) MAC address relocation is also used as a failure recovery
>>>>>> technique; the
>>>>>> surviving hardware element (e.g., host in a cluster) takes over
>>>>>> the MAC
>>>>>> addresses of the failed hardware; like the previous case, a
>>>>>> "gratuitous ARP"
>>>>>> is a common means of informing the network that the MAC address
>>>>>> has moved,
>>>>>> and source address validation information needs to move in
>>>>>> response to it.
>>>>>>
>>>>>> Minor issues:
>>>>>>
>>>>>> There doesn't seem to be much discussion of dynamic network
>>>>>> reconfiguration,
>>>>>> which may change traffic egress points.  VRRP may be a useful
>>>>>> example to
>>>>>> discuss beyond the typical routing protocol updates to forwarding
>>>>>> tables.
>>>>>>
>>>>>> Nits/editorial comments:
>>>>>>
>>>>>> idnits 2.12.11 ran clean.
>>>>>>
>>>>>> Thanks,
>>>>>> --David
>>>>>> ----------------------------------------------------
>>>>>> David L. Black, Distinguished Engineer
>>>>>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>>>>>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>>>>>> david.black@emc.com        Mobile: +1 (978) 394-7754
>>>>>> ----------------------------------------------------
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> savi mailing list
>>>>>> savi@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/savi
>>>>>>
>>>>
>>>>
>>
>>


From suresh.krishnan@ericsson.com  Sat Feb 23 21:01:06 2013
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 39BAE21F8AC1 for <gen-art@ietfa.amsl.com>; Sat, 23 Feb 2013 21:01:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.288
X-Spam-Level: 
X-Spam-Status: No, score=-102.288 tagged_above=-999 required=5 tests=[AWL=0.311, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7tdD4RYdo26q for <gen-art@ietfa.amsl.com>; Sat, 23 Feb 2013 21:01:05 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 4F43D21F8ABC for <gen-art@ietf.org>; Sat, 23 Feb 2013 21:01:05 -0800 (PST)
X-AuditID: c6180641-b7f926d000000e79-20-51299e90c43e
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E9.AE.03705.09E99215; Sun, 24 Feb 2013 06:01:04 +0100 (CET)
Received: from eusaamw0706.eamcs.ericsson.se (147.117.20.31) by EUSAAHC002.ericsson.se (147.117.188.78) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sun, 24 Feb 2013 00:01:03 -0500
Received: from [164.48.125.56] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.31) with Microsoft SMTP Server (TLS) id 8.3.279.1; Sun, 24 Feb 2013 00:01:03 -0500
Message-ID: <51299DE4.7010502@ericsson.com>
Date: Sat, 23 Feb 2013 23:58:12 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: <draft-eastlake-additional-xmlsec-uris.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBJMWRmVeSWpSXmKPExsUyuXSPn+6EeZqBBjN2qlu8n3aZ1eLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfG9osn2QsW81Y8WmHRwHiLq4uRk0NCwERi 84v9bBC2mMSFe+uBbC4OIYEjjBI3Np1jhHB2M0p8Wr2ZCcLZwigxt+EEK0gLr4C2xKL1X4AS HBwsAqoS+w+ogYTZgKZu2PmZCcQWFQiT6H0NMgikXFDi5MwnLCC2iEC+xK7d18DGCAu4S6z8 2c8KMkZCQFxizRsOkDCzgJ7ElKstjBC2vMT2t3OYQWwhAU2JrWu+s05gFJiFZOosJC2zkLQs YGRexchRWpxalptuZLiJERh6xyTYHHcwLvhkeYhRmoNFSZw31PVCgJBAemJJanZqakFqUXxR aU5q8SFGJg5OqQZG7U99wksqtuxtkH7Au7P1YOHGA4WqJ/z37tgQ+PiTy63Q6be6rlz5bCEp c+G00lL5uWE969WuNoQsYgu6NFf5/xnuIEa9cKkHLCLL3y9YGNuqt/ScCuctqwOcem+Puf7b 1887d8czmQN395xctOln5Mx5ghwL9igU2rqkn3vI2ruwdOeqJ8usa5RYijMSDbWYi4oTAbWE BOkLAgAA
Subject: [Gen-art] Gen-ART review of draft-eastlake-additional-xmlsec-uris-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, 24 Feb 2013 05:01:06 -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-eastlake-additional-xmlsec-uris-09.txt
Reviewer: Suresh Krishnan
Review Date: 2013/02/23
IESG Telechat date: 2013/02/28
IETF Last call end date: 2013/02/28

Summary: This document is almost ready for publication as a Proposed
Standard but I have some comments you may wish to address.

Minor
=====

* Section 2.1.1.

The following text is a bit misleading as it looks like this document is
taking a stance on the use of MD5.

"Use of MD5 is NOT RECOMMENDED [RFC6151]."

Suggest rewording to something like

"Please note that the use of MD5 is no longer recommended for digital
signatures [RFC6151]."

* Section 2.3.1.

Same comment as for Section 2.1.1.

* Security Considerations

Again, this paragraph looks like it is making recommendations that
duplicate the recommendations from RFC6151. Is this paragraph really
necessary?

"Due to computer speed and cryptographic advances, the use of MD5 as a
DigestMethod or in the RSA-MD5 SignatureMethod is NOT RECOMMENDED.
The cryptographic advances concerned do not affect the security of
HMAC-MD5; however, there is little reason not to go for one of the
SHA series of algorithms."

Downrefs
========

There are 9 downrefs that have not been called out. 5 of them are listed
in the downref registry. The other 4 downrefs are listed below

RFC2315
RFC4050
RFC4269
RFC6234

Thanks
Suresh


From Francis.Dupont@fdupont.fr  Sun Feb 24 09:38:22 2013
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 8E5AD21F9080 for <gen-art@ietfa.amsl.com>; Sun, 24 Feb 2013 09:38:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iqZ88lzhJfep for <gen-art@ietfa.amsl.com>; Sun, 24 Feb 2013 09:38:21 -0800 (PST)
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 7EA7321F907D for <gen-art@ietf.org>; Sun, 24 Feb 2013 09:38:21 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r1OHcIgu073206; Sun, 24 Feb 2013 18:38:19 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201302241738.r1OHcIgu073206@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Sun, 24 Feb 2013 18:38:18 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-dhc-secure-dhcpv6.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-dhc-secure-dhcpv6-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: Sun, 24 Feb 2013 17:38:22 -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-dhc-secure-dhcpv6-07.txt
Reviewer: Francis Dupont
Review Date: 20130220
IETF LC End Date: 20130225
IESG Telechat date: 20130228

Summary: Not Ready

Major issues: the proposal fails to provide the expected security,
 in particular it does nothing real against replay and the basic
 function (anti-spoofing) relies on pre-configuration.

Minor issues: some but major issues should imply enough changes to make
 them more candicates for comments

Nits/editorial comments: (including technical comments)
 - first the I-D format is not followed (printed the 17 pages with
  4 pages per sheet gives 9 sheets...)

 - Abstract page 2: IMHO the Abstract should be first (i.e., just
  after the title and before the Status of this Memo)

 - I know well SeND so when I compare to it I can see a lot of issues.

  To summarize SeND uses 4 devices: nonces, timestamps, CGAs and a PKI.
  Nonces and timestamps are for anti-replay (IMHO nonces have a crypto
  function too as they introduce unpredictable random in messages,
  but I don't know if it is an important point or not). CGAs are for
  authentication and message integrity. The PKI (known today as the
  RPKI) is for authorization, i.e., the prefix is checked to be really
  assigned to the entity running the router.

  When I compare to the secure DHCPv6 proposal I can get only the CGA
  part. There are timestamps but one way and without any text explaining
  how to apply them (i.e., the proposal is incomplete about this point:
  anti-replay).

  The authorization problem is not addressed until the end of the document
  where pre-configuration is introduced. BTW the current DHCPv6 security
  is mainly rejected because it requires pre-configuration (of course
  it has many other problems but this operational one is as far as I
  know the most blocking one).

 - 1 page 3: I'd like to see anti-replay and authorization issues at
  least mentioned here.

 - 3 a page 3: ownership doesn't protect against fake, it protects
  against impersonation, i.e., with CGAs a fake server can launch an
  attack but nobody can impersonate the legimate server. So either
  the description of the attack is wrong or the protection mechanism
  is not the right one.

 - 3 b page 4: i.e. -> i.e.,

 - 3 c page 4 (comment): in fact the reason IPsec is rarely used to protect
  relay/server communication is not because IPsec is hard but because
  usually this communication is inside the ISP internal infrastructure
  so is not subject to easy attacks. With other words the vulnerable
  part is the client/agent communication over a very unprotected LAN,
  a wireless LAN for instance, where of course IPsec is not applicable.

 - 4 page 4: abovementioned -> above mentioned or above-mentioned?

 - 4 page 5: replay protection is mentioned, there is a timestamp field
  in the signature option but nothing about how to use it...

 - 4.2 page 5: IMHO the text about collision could be removed: it is
  well known collisions are not a problem in this case. And algo
  agility is something one wants a priori, so it doesn't need a bad
  argument to support it.
  BTW if you can't find a general IETF document explaining why algo
  agility is good we can ask the security directorate to make a formal
  statement. In anycase you should get something to reference...

 - 5.2 page 8: in the signature please put the tag value in its own line
  (so implementors can more easily cut and paste it).

 - 5.2 page 9: I am not sure the wording of the padding is very correct...

 - 5.4 page 10: section 5.1 and 5.2 -> sections

 - 6.2 page 12: where is the text about timestamps? With the current
  processing rules a relay attack is trivial (so either you remove
  anti-replay from the threats the proposal deals with, or you complete
  the proposal).

 - 6.2 page 12: someone suggested for DNSSEC to avoid silly large RSA
  exponents too. (comment (as you wrote prudent practice...))

 - 7 pages 14 and 15: I have nothing against this security considerations but
  unfortunately as they are well written they kill most of the interests
  in the proposal:
    - anti-spoofing provided by pre-configuration (i.e., you can also
     pre-configured shared secrets for authentication/integrity)
    - no downgrade protection when compatibility is kept.
    - another text about collisions (please keep this one and remove the
     section 4.2 one)

 - 9 page 17: IMHO Dorms -> Droms ...

Regards 

Francis.Dupont@fdupont.fr

From d3e3e3@gmail.com  Sun Feb 24 18:05:00 2013
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 B3A5621F9152 for <gen-art@ietfa.amsl.com>; Sun, 24 Feb 2013 18:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.482
X-Spam-Level: 
X-Spam-Status: No, score=-103.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n7G2dANwjEZT for <gen-art@ietfa.amsl.com>; Sun, 24 Feb 2013 18:04:58 -0800 (PST)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id 000F421F8EB2 for <gen-art@ietf.org>; Sun, 24 Feb 2013 18:04:57 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id i10so2433527oag.14 for <gen-art@ietf.org>; Sun, 24 Feb 2013 18:04:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=C8hwEvmZuoaUkL4ySUMM2uQdsUgWSG0uyQv4y8gWUyY=; b=wJa87JObruF2hK5xhojwgpLEI6CAga+z83TFpVl9QA9hFd6scPZ1XTzgGqi2He7SgM 085W4HLoAAIA6VUJx67gbIyUPk69NQWjIWAf0P0Pe9e/0VzWCmxraowlLdt7W0AMDHTu XYfcigrV+nnjUnLfKJFLz7dQoKd9VyoWvhCV8l6SxZo+sN18ZMoValrgpxW1XA97jh2P R2SCocET4E/dg9BJjQwQlzdgS3y3pYrvej93H0xVBr+fOw7QJo0/Remjrk9u36Qf51k/ MR7RgmnIfy3TGlR7bDpjImy7Sc9lMneg8mjQGf9+PgBYEk/mD2lSdKAqKJ2b8YfkDd8X bGJQ==
X-Received: by 10.182.40.71 with SMTP id v7mr5937797obk.85.1361757896756; Sun, 24 Feb 2013 18:04:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Sun, 24 Feb 2013 18:04:36 -0800 (PST)
In-Reply-To: <51299DE4.7010502@ericsson.com>
References: <51299DE4.7010502@ericsson.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 24 Feb 2013 21:04:36 -0500
Message-ID: <CAF4+nEE+vqKuee1pQ_c6hvhuynKMsy--paWVUmi0Gf4Vq0PPVQ@mail.gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: General Area Review Team <gen-art@ietf.org>, draft-eastlake-additional-xmlsec-uris.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-eastlake-additional-xmlsec-uris-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, 25 Feb 2013 02:05:00 -0000

Hi Suresh,

Thanks for the review.

On Sat, Feb 23, 2013 at 11:58 PM, Suresh Krishnan
<suresh.krishnan@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
> 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-eastlake-additional-xmlsec-uris-09.txt
> Reviewer: Suresh Krishnan
> Review Date: 2013/02/23
> IESG Telechat date: 2013/02/28
> IETF Last call end date: 2013/02/28
>
> Summary: This document is almost ready for publication as a Proposed
> Standard but I have some comments you may wish to address.
>
> Minor
> =====
>
> * Section 2.1.1.
>
> The following text is a bit misleading as it looks like this document is
> taking a stance on the use of MD5.
>
> "Use of MD5 is NOT RECOMMENDED [RFC6151]."
>
> Suggest rewording to something like
>
> "Please note that the use of MD5 is no longer recommended for digital
> signatures [RFC6151]."

OK.

> * Section 2.3.1.
>
> Same comment as for Section 2.1.1.

OK.

> * Security Considerations
>
> Again, this paragraph looks like it is making recommendations that
> duplicate the recommendations from RFC6151. Is this paragraph really
> necessary?
>
> "Due to computer speed and cryptographic advances, the use of MD5 as a
> DigestMethod or in the RSA-MD5 SignatureMethod is NOT RECOMMENDED.
> The cryptographic advances concerned do not affect the security of
> HMAC-MD5; however, there is little reason not to go for one of the
> SHA series of algorithms."

The inclusion of something about the inadvisability of MD5 was
suggested to me by an AD. I'm perfectly happy to re-word things so
that it does not "take a stance" but merely provides informative
pointers as a convenience to the reader.

> Downrefs
> ========
>
> There are 9 downrefs that have not been called out. 5 of them are listed
> in the downref registry. The other 4 downrefs are listed below
>
> RFC2315
> RFC4050
> RFC4269
> RFC6234
>
> Thanks
> Suresh

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  Mon Feb 25 15:28:14 2013
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 98EAF21E8148; Mon, 25 Feb 2013 15:28:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.262
X-Spam-Level: 
X-Spam-Status: No, score=-102.262 tagged_above=-999 required=5 tests=[AWL=-0.262, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R8IUlHnP2EKc; Mon, 25 Feb 2013 15:28:14 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 27DDC21E8128; Mon, 25 Feb 2013 15:28:14 -0800 (PST)
Received: from vpn-cust-10-119-74-38.witopia.net (69.147.243.203.rdns.ubiquityservers.com [69.147.243.203] (may be forged)) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r1PNSDGb082966 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 25 Feb 2013 17:28:13 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Feb 2013 17:28:06 -0600
Message-Id: <03EE5FB0-F0D0-481D-99F9-1D45568C0AC5@nostrum.com>
To: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (shaman.nostrum.com: 69.147.243.203 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC/Telechat review of draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-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 Feb 2013 23:28: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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:  draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04
Reviewer: Ben Campbell
Review Date: 2013-02-25
IETF LC End Date: 2013-02-28
IESG Telechat date: 2013-02-28

Summary: Ready for publication as a proposed standard

Major issues:

None

Minor issues:

None

Nits/editorial comments:

-- Header:

I ca't help but enjoy the fact that the file name is longer than the =
draft title :-)  (No change needed)

-- section 2, last paragraph:

s/"For e.g."/"For example,"  =20



From jiangsheng@huawei.com  Mon Feb 25 19:37:40 2013
Return-Path: <jiangsheng@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 2F2AB21E80B3 for <gen-art@ietfa.amsl.com>; Mon, 25 Feb 2013 19:37:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D8Q8mfN8bkX8 for <gen-art@ietfa.amsl.com>; Mon, 25 Feb 2013 19:37:39 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0314E21E8166 for <gen-art@ietf.org>; Mon, 25 Feb 2013 19:37:37 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOU30304; Tue, 26 Feb 2013 03:37:37 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 26 Feb 2013 03:36:44 +0000
Received: from SZXEML455-HUB.china.huawei.com (10.82.67.198) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 26 Feb 2013 03:37:36 +0000
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.45]) by SZXEML455-HUB.china.huawei.com ([10.82.67.198]) with mapi id 14.01.0323.007; Tue, 26 Feb 2013 11:37:22 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Francis.Dupont@fdupont.fr" <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: review of draft-ietf-dhc-secure-dhcpv6-07.txt
Thread-Index: AQHOErXH6Fh0YRmQK0OFtap6STLOdZiLfuLg
Date: Tue, 26 Feb 2013 03:37:31 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923A00D742@szxeml545-mbx.china.huawei.com>
References: <201302241738.r1OHcIgu073206@givry.fdupont.fr>
In-Reply-To: <201302241738.r1OHcIgu073206@givry.fdupont.fr>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "dhc-chairs@tools.ietf.org" <dhc-chairs@tools.ietf.org>, "draft-ietf-dhc-secure-dhcpv6.all@tools.ietf.org" <draft-ietf-dhc-secure-dhcpv6.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-dhc-secure-dhcpv6-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: Tue, 26 Feb 2013 03:37:40 -0000

SGksIEZyYW5jaXMsDQoNClRoYW5rcyBzbyBtdWNoIGZvciB5b3VyIGRldGFpbGVkIHJldmlldy4g
WW91ciBjb21tZW50cyBhcmUgaW1wb3J0YW50IGZvciB1cyB0byBpbXByb3ZlIHRoZSBkcmFmdC4g
V2Ugd2lsbCB3b3JrIG9uIHRoYXQgaW4gdGhlIG5leHQgdXBkYXRlLiBNYXliZSBzb21lIHByaXZh
dGUgY29tbXVuaWNhdGlvbiB3aWxsIGJlIGZvciB5b3VyIGZ1cnRoZXIgYWR2aWNlcy4NCg0KTWFu
eSB0aGFua3MgYW5kIGJlc3QgcmVnYXJkcywNCg0KU2hlbmcNCg0KPi0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+RnJvbTogRnJhbmNpcy5EdXBvbnRAZmR1cG9udC5mciBbbWFpbHRvOkZyYW5j
aXMuRHVwb250QGZkdXBvbnQuZnJdDQo+U2VudDogTW9uZGF5LCBGZWJydWFyeSAyNSwgMjAxMyAx
OjM4IEFNDQo+VG86IGdlbi1hcnRAaWV0Zi5vcmcNCj5DYzogZHJhZnQtaWV0Zi1kaGMtc2VjdXJl
LWRoY3B2Ni5hbGxAdG9vbHMuaWV0Zi5vcmcNCj5TdWJqZWN0OiByZXZpZXcgb2YgZHJhZnQtaWV0
Zi1kaGMtc2VjdXJlLWRoY3B2Ni0wNy50eHQNCj4NCj5JIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJU
IHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBGb3IgYmFja2dyb3VuZCBvbg0KPkdlbi1BUlQsIHBs
ZWFzZSBzZWUgdGhlIEZBUSBhdA0KPg0KPjxodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVh
L2dlbi90cmFjL3dpa2kvR2VuQXJ0ZmFxPi4NCj4NCj5QbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21t
ZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBMYXN0IENhbGwgY29tbWVudHMNCj55b3UgbWF5IHJl
Y2VpdmUuDQo+DQo+RG9jdW1lbnQ6IGRyYWZ0LWlldGYtZGhjLXNlY3VyZS1kaGNwdjYtMDcudHh0
DQo+UmV2aWV3ZXI6IEZyYW5jaXMgRHVwb250DQo+UmV2aWV3IERhdGU6IDIwMTMwMjIwDQo+SUVU
RiBMQyBFbmQgRGF0ZTogMjAxMzAyMjUNCj5JRVNHIFRlbGVjaGF0IGRhdGU6IDIwMTMwMjI4DQo+
DQo+U3VtbWFyeTogTm90IFJlYWR5DQo+DQo+TWFqb3IgaXNzdWVzOiB0aGUgcHJvcG9zYWwgZmFp
bHMgdG8gcHJvdmlkZSB0aGUgZXhwZWN0ZWQgc2VjdXJpdHksDQo+IGluIHBhcnRpY3VsYXIgaXQg
ZG9lcyBub3RoaW5nIHJlYWwgYWdhaW5zdCByZXBsYXkgYW5kIHRoZSBiYXNpYw0KPiBmdW5jdGlv
biAoYW50aS1zcG9vZmluZykgcmVsaWVzIG9uIHByZS1jb25maWd1cmF0aW9uLg0KPg0KPk1pbm9y
IGlzc3Vlczogc29tZSBidXQgbWFqb3IgaXNzdWVzIHNob3VsZCBpbXBseSBlbm91Z2ggY2hhbmdl
cyB0byBtYWtlDQo+IHRoZW0gbW9yZSBjYW5kaWNhdGVzIGZvciBjb21tZW50cw0KPg0KPk5pdHMv
ZWRpdG9yaWFsIGNvbW1lbnRzOiAoaW5jbHVkaW5nIHRlY2huaWNhbCBjb21tZW50cykNCj4gLSBm
aXJzdCB0aGUgSS1EIGZvcm1hdCBpcyBub3QgZm9sbG93ZWQgKHByaW50ZWQgdGhlIDE3IHBhZ2Vz
IHdpdGgNCj4gIDQgcGFnZXMgcGVyIHNoZWV0IGdpdmVzIDkgc2hlZXRzLi4uKQ0KPg0KPiAtIEFi
c3RyYWN0IHBhZ2UgMjogSU1ITyB0aGUgQWJzdHJhY3Qgc2hvdWxkIGJlIGZpcnN0IChpLmUuLCBq
dXN0DQo+ICBhZnRlciB0aGUgdGl0bGUgYW5kIGJlZm9yZSB0aGUgU3RhdHVzIG9mIHRoaXMgTWVt
bykNCj4NCj4gLSBJIGtub3cgd2VsbCBTZU5EIHNvIHdoZW4gSSBjb21wYXJlIHRvIGl0IEkgY2Fu
IHNlZSBhIGxvdCBvZiBpc3N1ZXMuDQo+DQo+ICBUbyBzdW1tYXJpemUgU2VORCB1c2VzIDQgZGV2
aWNlczogbm9uY2VzLCB0aW1lc3RhbXBzLCBDR0FzIGFuZCBhIFBLSS4NCj4gIE5vbmNlcyBhbmQg
dGltZXN0YW1wcyBhcmUgZm9yIGFudGktcmVwbGF5IChJTUhPIG5vbmNlcyBoYXZlIGEgY3J5cHRv
DQo+ICBmdW5jdGlvbiB0b28gYXMgdGhleSBpbnRyb2R1Y2UgdW5wcmVkaWN0YWJsZSByYW5kb20g
aW4gbWVzc2FnZXMsDQo+ICBidXQgSSBkb24ndCBrbm93IGlmIGl0IGlzIGFuIGltcG9ydGFudCBw
b2ludCBvciBub3QpLiBDR0FzIGFyZSBmb3INCj4gIGF1dGhlbnRpY2F0aW9uIGFuZCBtZXNzYWdl
IGludGVncml0eS4gVGhlIFBLSSAoa25vd24gdG9kYXkgYXMgdGhlDQo+ICBSUEtJKSBpcyBmb3Ig
YXV0aG9yaXphdGlvbiwgaS5lLiwgdGhlIHByZWZpeCBpcyBjaGVja2VkIHRvIGJlIHJlYWxseQ0K
PiAgYXNzaWduZWQgdG8gdGhlIGVudGl0eSBydW5uaW5nIHRoZSByb3V0ZXIuDQo+DQo+ICBXaGVu
IEkgY29tcGFyZSB0byB0aGUgc2VjdXJlIERIQ1B2NiBwcm9wb3NhbCBJIGNhbiBnZXQgb25seSB0
aGUgQ0dBDQo+ICBwYXJ0LiBUaGVyZSBhcmUgdGltZXN0YW1wcyBidXQgb25lIHdheSBhbmQgd2l0
aG91dCBhbnkgdGV4dCBleHBsYWluaW5nDQo+ICBob3cgdG8gYXBwbHkgdGhlbSAoaS5lLiwgdGhl
IHByb3Bvc2FsIGlzIGluY29tcGxldGUgYWJvdXQgdGhpcyBwb2ludDoNCj4gIGFudGktcmVwbGF5
KS4NCj4NCj4gIFRoZSBhdXRob3JpemF0aW9uIHByb2JsZW0gaXMgbm90IGFkZHJlc3NlZCB1bnRp
bCB0aGUgZW5kIG9mIHRoZSBkb2N1bWVudA0KPiAgd2hlcmUgcHJlLWNvbmZpZ3VyYXRpb24gaXMg
aW50cm9kdWNlZC4gQlRXIHRoZSBjdXJyZW50IERIQ1B2NiBzZWN1cml0eQ0KPiAgaXMgbWFpbmx5
IHJlamVjdGVkIGJlY2F1c2UgaXQgcmVxdWlyZXMgcHJlLWNvbmZpZ3VyYXRpb24gKG9mIGNvdXJz
ZQ0KPiAgaXQgaGFzIG1hbnkgb3RoZXIgcHJvYmxlbXMgYnV0IHRoaXMgb3BlcmF0aW9uYWwgb25l
IGlzIGFzIGZhciBhcyBJDQo+ICBrbm93IHRoZSBtb3N0IGJsb2NraW5nIG9uZSkuDQo+DQo+IC0g
MSBwYWdlIDM6IEknZCBsaWtlIHRvIHNlZSBhbnRpLXJlcGxheSBhbmQgYXV0aG9yaXphdGlvbiBp
c3N1ZXMgYXQNCj4gIGxlYXN0IG1lbnRpb25lZCBoZXJlLg0KPg0KPiAtIDMgYSBwYWdlIDM6IG93
bmVyc2hpcCBkb2Vzbid0IHByb3RlY3QgYWdhaW5zdCBmYWtlLCBpdCBwcm90ZWN0cw0KPiAgYWdh
aW5zdCBpbXBlcnNvbmF0aW9uLCBpLmUuLCB3aXRoIENHQXMgYSBmYWtlIHNlcnZlciBjYW4gbGF1
bmNoIGFuDQo+ICBhdHRhY2sgYnV0IG5vYm9keSBjYW4gaW1wZXJzb25hdGUgdGhlIGxlZ2ltYXRl
IHNlcnZlci4gU28gZWl0aGVyDQo+ICB0aGUgZGVzY3JpcHRpb24gb2YgdGhlIGF0dGFjayBpcyB3
cm9uZyBvciB0aGUgcHJvdGVjdGlvbiBtZWNoYW5pc20NCj4gIGlzIG5vdCB0aGUgcmlnaHQgb25l
Lg0KPg0KPiAtIDMgYiBwYWdlIDQ6IGkuZS4gLT4gaS5lLiwNCj4NCj4gLSAzIGMgcGFnZSA0IChj
b21tZW50KTogaW4gZmFjdCB0aGUgcmVhc29uIElQc2VjIGlzIHJhcmVseSB1c2VkIHRvIHByb3Rl
Y3QNCj4gIHJlbGF5L3NlcnZlciBjb21tdW5pY2F0aW9uIGlzIG5vdCBiZWNhdXNlIElQc2VjIGlz
IGhhcmQgYnV0IGJlY2F1c2UNCj4gIHVzdWFsbHkgdGhpcyBjb21tdW5pY2F0aW9uIGlzIGluc2lk
ZSB0aGUgSVNQIGludGVybmFsIGluZnJhc3RydWN0dXJlDQo+ICBzbyBpcyBub3Qgc3ViamVjdCB0
byBlYXN5IGF0dGFja3MuIFdpdGggb3RoZXIgd29yZHMgdGhlIHZ1bG5lcmFibGUNCj4gIHBhcnQg
aXMgdGhlIGNsaWVudC9hZ2VudCBjb21tdW5pY2F0aW9uIG92ZXIgYSB2ZXJ5IHVucHJvdGVjdGVk
IExBTiwNCj4gIGEgd2lyZWxlc3MgTEFOIGZvciBpbnN0YW5jZSwgd2hlcmUgb2YgY291cnNlIElQ
c2VjIGlzIG5vdCBhcHBsaWNhYmxlLg0KPg0KPiAtIDQgcGFnZSA0OiBhYm92ZW1lbnRpb25lZCAt
PiBhYm92ZSBtZW50aW9uZWQgb3IgYWJvdmUtbWVudGlvbmVkPw0KPg0KPiAtIDQgcGFnZSA1OiBy
ZXBsYXkgcHJvdGVjdGlvbiBpcyBtZW50aW9uZWQsIHRoZXJlIGlzIGEgdGltZXN0YW1wIGZpZWxk
DQo+ICBpbiB0aGUgc2lnbmF0dXJlIG9wdGlvbiBidXQgbm90aGluZyBhYm91dCBob3cgdG8gdXNl
IGl0Li4uDQo+DQo+IC0gNC4yIHBhZ2UgNTogSU1ITyB0aGUgdGV4dCBhYm91dCBjb2xsaXNpb24g
Y291bGQgYmUgcmVtb3ZlZDogaXQgaXMNCj4gIHdlbGwga25vd24gY29sbGlzaW9ucyBhcmUgbm90
IGEgcHJvYmxlbSBpbiB0aGlzIGNhc2UuIEFuZCBhbGdvDQo+ICBhZ2lsaXR5IGlzIHNvbWV0aGlu
ZyBvbmUgd2FudHMgYSBwcmlvcmksIHNvIGl0IGRvZXNuJ3QgbmVlZCBhIGJhZA0KPiAgYXJndW1l
bnQgdG8gc3VwcG9ydCBpdC4NCj4gIEJUVyBpZiB5b3UgY2FuJ3QgZmluZCBhIGdlbmVyYWwgSUVU
RiBkb2N1bWVudCBleHBsYWluaW5nIHdoeSBhbGdvDQo+ICBhZ2lsaXR5IGlzIGdvb2Qgd2UgY2Fu
IGFzayB0aGUgc2VjdXJpdHkgZGlyZWN0b3JhdGUgdG8gbWFrZSBhIGZvcm1hbA0KPiAgc3RhdGVt
ZW50LiBJbiBhbnljYXNlIHlvdSBzaG91bGQgZ2V0IHNvbWV0aGluZyB0byByZWZlcmVuY2UuLi4N
Cj4NCj4gLSA1LjIgcGFnZSA4OiBpbiB0aGUgc2lnbmF0dXJlIHBsZWFzZSBwdXQgdGhlIHRhZyB2
YWx1ZSBpbiBpdHMgb3duIGxpbmUNCj4gIChzbyBpbXBsZW1lbnRvcnMgY2FuIG1vcmUgZWFzaWx5
IGN1dCBhbmQgcGFzdGUgaXQpLg0KPg0KPiAtIDUuMiBwYWdlIDk6IEkgYW0gbm90IHN1cmUgdGhl
IHdvcmRpbmcgb2YgdGhlIHBhZGRpbmcgaXMgdmVyeSBjb3JyZWN0Li4uDQo+DQo+IC0gNS40IHBh
Z2UgMTA6IHNlY3Rpb24gNS4xIGFuZCA1LjIgLT4gc2VjdGlvbnMNCj4NCj4gLSA2LjIgcGFnZSAx
Mjogd2hlcmUgaXMgdGhlIHRleHQgYWJvdXQgdGltZXN0YW1wcz8gV2l0aCB0aGUgY3VycmVudA0K
PiAgcHJvY2Vzc2luZyBydWxlcyBhIHJlbGF5IGF0dGFjayBpcyB0cml2aWFsIChzbyBlaXRoZXIg
eW91IHJlbW92ZQ0KPiAgYW50aS1yZXBsYXkgZnJvbSB0aGUgdGhyZWF0cyB0aGUgcHJvcG9zYWwg
ZGVhbHMgd2l0aCwgb3IgeW91IGNvbXBsZXRlDQo+ICB0aGUgcHJvcG9zYWwpLg0KPg0KPiAtIDYu
MiBwYWdlIDEyOiBzb21lb25lIHN1Z2dlc3RlZCBmb3IgRE5TU0VDIHRvIGF2b2lkIHNpbGx5IGxh
cmdlIFJTQQ0KPiAgZXhwb25lbnRzIHRvby4gKGNvbW1lbnQgKGFzIHlvdSB3cm90ZSBwcnVkZW50
IHByYWN0aWNlLi4uKSkNCj4NCj4gLSA3IHBhZ2VzIDE0IGFuZCAxNTogSSBoYXZlIG5vdGhpbmcg
YWdhaW5zdCB0aGlzIHNlY3VyaXR5IGNvbnNpZGVyYXRpb25zIGJ1dA0KPiAgdW5mb3J0dW5hdGVs
eSBhcyB0aGV5IGFyZSB3ZWxsIHdyaXR0ZW4gdGhleSBraWxsIG1vc3Qgb2YgdGhlIGludGVyZXN0
cw0KPiAgaW4gdGhlIHByb3Bvc2FsOg0KPiAgICAtIGFudGktc3Bvb2ZpbmcgcHJvdmlkZWQgYnkg
cHJlLWNvbmZpZ3VyYXRpb24gKGkuZS4sIHlvdSBjYW4gYWxzbw0KPiAgICAgcHJlLWNvbmZpZ3Vy
ZWQgc2hhcmVkIHNlY3JldHMgZm9yIGF1dGhlbnRpY2F0aW9uL2ludGVncml0eSkNCj4gICAgLSBu
byBkb3duZ3JhZGUgcHJvdGVjdGlvbiB3aGVuIGNvbXBhdGliaWxpdHkgaXMga2VwdC4NCj4gICAg
LSBhbm90aGVyIHRleHQgYWJvdXQgY29sbGlzaW9ucyAocGxlYXNlIGtlZXAgdGhpcyBvbmUgYW5k
IHJlbW92ZSB0aGUNCj4gICAgIHNlY3Rpb24gNC4yIG9uZSkNCj4NCj4gLSA5IHBhZ2UgMTc6IElN
SE8gRG9ybXMgLT4gRHJvbXMgLi4uDQo+DQo+UmVnYXJkcw0KPg0KPkZyYW5jaXMuRHVwb250QGZk
dXBvbnQuZnINCg==

From brian.e.carpenter@gmail.com  Tue Feb 26 04:26:33 2013
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 9BF1F21F8A5A for <gen-art@ietfa.amsl.com>; Tue, 26 Feb 2013 04:26:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.803
X-Spam-Level: 
X-Spam-Status: No, score=-102.803 tagged_above=-999 required=5 tests=[AWL=0.796, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tkO3r3eosjeA for <gen-art@ietfa.amsl.com>; Tue, 26 Feb 2013 04:26:32 -0800 (PST)
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by ietfa.amsl.com (Postfix) with ESMTP id 7657F21F88B6 for <gen-art@ietf.org>; Tue, 26 Feb 2013 04:26:27 -0800 (PST)
Received: by mail-wi0-f173.google.com with SMTP id hq4so4758428wib.12 for <gen-art@ietf.org>; Tue, 26 Feb 2013 04:26:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=e5Up/R5vfTo4bqEQ/wJZ7+EFG+bnO4PM2MYwuu0L0ys=; b=t3z8rQIJxCAFoLfinp+cm8V8dRA39zxTOVCx0xWt87FqGbN6wbu69KCSP94VVqjoWS 5evVtOlcJC8Mhd4xnfGyo4WAmFakz2UYOHCLo4KzSI0M1N2quZ/c00S0ownsZ/EiJrn0 d8bARu8jIRH1+0NlV9KD6/PWfcGJSxNcziCQv/YidhDmyTx+LWxhNN9CNYd+O03P6lSA 9Z1usdmo67A9Yb1FC8nsVmE4Mx6JeoBL/Xk6c/VMWCWq1YBav1wQziNoym8V3kMKPQpH XOZBoEe4IglzGlRqzOT9xBmLSCkMREMMJPEfHMbt43RjAivC+4/E7z5X20/vSaVsifQ5 V83w==
X-Received: by 10.194.62.170 with SMTP id z10mr26024028wjr.34.1361881584227; Tue, 26 Feb 2013 04:26:24 -0800 (PST)
Received: from [128.232.110.102] (c102.al.cl.cam.ac.uk. [128.232.110.102]) by mx.google.com with ESMTPS id fx5sm1595317wib.11.2013.02.26.04.26.22 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Feb 2013 04:26:23 -0800 (PST)
Message-ID: <512CA9F4.7060902@gmail.com>
Date: Tue, 26 Feb 2013 12:26:28 +0000
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>,  draft-ietf-behave-nat64-discovery-heuristic.all@tools.ietf.org
References: <20130225154415.24964.48372.idtracker@ietfa.amsl.com>
In-Reply-To: <20130225154415.24964.48372.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Gen-art] I-D Action: draft-ietf-behave-nat64-discovery-heuristic-14.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, 26 Feb 2013 12:26:33 -0000

For the record, I'm happy with this version too.

Regards
   Brian

From Simo.Veikkolainen@nokia.com  Wed Feb 27 23:26:24 2013
Return-Path: <Simo.Veikkolainen@nokia.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 7C03721F8AF2; Wed, 27 Feb 2013 23:26:24 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hHaMetezrF76; Wed, 27 Feb 2013 23:26:22 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 040A321F8B33; Wed, 27 Feb 2013 23:26:21 -0800 (PST)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-da01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r1S7QHjL010051; Thu, 28 Feb 2013 09:26:20 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.56]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 28 Feb 2013 09:26:19 +0200
Received: from 008-AM1MPN1-025.mgdnok.nokia.com ([169.254.5.248]) by 008-AM1MMR1-001.mgdnok.nokia.com ([65.54.30.56]) with mapi id 14.02.0318.003; Thu, 28 Feb 2013 07:26:07 +0000
From: <Simo.Veikkolainen@nokia.com>
To: <alexey.melnikov@isode.com>, <draft-ietf-mmusic-sdp-cs.all@tools.ietf.org>
Thread-Topic: Gen-ART LC review of draft-ietf-mmusic-sdp-cs-17
Thread-Index: AQHOCSOKi6GTTOrWcEeEXEgcJqJULJiO9TDQ
Date: Thu, 28 Feb 2013 07:31:07 +0000
Message-ID: <D09DAE6B636851459F7575D146EFB54B1C875EC9@008-AM1MPN1-025.mgdnok.nokia.com>
References: <511A4188.6030101@isode.com>
In-Reply-To: <511A4188.6030101@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-version: 3.5.9.3
x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Nokia Internal Use Only;Project=None;
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IieUVVR+P20VDCzpg3HHXu3iIt34TClchC1lFMW65RFph3Xs1oFZJ8BKEw2gEkvxl2XUs8mQ1ArncdQoz2fDkqH2kzfuUztXefWQ1JyU6IUmOQbX47W+L1fS+L8bG+PEiD23yATCS6tPhi9FhDKqrwtPfnbuvC4vaLSG4vIhUT5aV44jzSJzVrqdG/k1x56DxZXop+VoQ4+jiJ40oQC2/rufZDEt3399umrkV5ZTZCz3eCoDFaIWfxXT6JNWiZyBkw==
x-originating-ip: [10.236.10.80]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 28 Feb 2013 07:26:19.0574 (UTC) FILETIME=[E7003560:01CE1584]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Thu, 28 Feb 2013 00:18:01 -0800
Cc: gen-art@ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mmusic-sdp-cs-17
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 Feb 2013 07:26:24 -0000

Hello Alexey,

Thank you for the review. Please find my answers inline [SV].

-----Original Message-----
From: ext Alexey Melnikov [mailto:alexey.melnikov@isode.com]=20
Sent: 12. helmikuuta 2013 15:20
To: draft-ietf-mmusic-sdp-cs.all@tools.ietf.org
Cc: gen-art@ietf.org; The IESG
Subject: Gen-ART LC review of draft-ietf-mmusic-sdp-cs-17

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-mmusic-sdp-cs-17
Reviewer: Alexey Melnikov
Review Date: 2013-02-12
IETF LC End Date: 2013-02-01
IESG Telechat date: N/A


Summary: This draft is ready for publication as a Standard Track RFC (with =
some nits/minor issues):

Major issues:

Minor issues:

5.2.2.  Media Descriptions

    When "RTP/AVP" is used in the <proto> field, the <fmt> subfield
    contains the RTP payload type numbers.  We use the <fmt> subfield to
    indicate the list of available codecs over the circuit-switched
    bearer, by re-using the conventions and payload type numbers defined
    for RTP/AVP.  The RTP audio and video media types, which, when
    applied to PSTN circuit-switched bearers, represent merely an audio
    or video codec.  The endpoint SHOULD only use those payload type
    whose corresponding codecs is available for PSTN media streams.

Why is this a SHOULD? What are possible reasons for violating it?

[SV] This is clarified in the following paragraph:

   In some cases, the endpoint is not able to determine the list of
   available codecs for circuit-switched media streams.  In this case,
   in order to be syntactically compliant with SDP [RFC4566], the
   endpoint MUST include a single dash ("-") in the <fmt> subfield.

[SV] Other option is to say that in cases where the endpoint is able to det=
ermine the RTP payload numbers, it MUST use those, and in cases when it is =
not, it MUST use the "dash".

5.6.1.  Generating the Initial Offer

    The <fmt> subfield carries the payload type number(s) the endpoint is
    wishing to use.  Payload type numbers in this case refer to the
    codecs that the endpoint wishes to use on the PSTN media stream. For
    example, if the endpoint wishes to use the GSM codec, it would add
    payload type number 3 in the list of codecs.  The list of payload
    types SHOULD only contain those codecs the endpoint is able to use on
    the PSTN bearer.

Again, a SHOULD similar to the one above. Can you please explain the reason=
ing for it?

[SV] See above.

    If the Offerer is only able to become the passive party in the
    circuit-switched bearer setup, it MUST add the "callerid", "uuie"
    and/or "dtmf" subfields,

This text is a bit awkward as you specify this field as extensible. So I=20
think you need to add a choice for extensions here.

 [SV] We changed the text to read:

	    If the Offerer is only able to become the passive party in
	    the circuit-switched bearer setup, it MUST add at least
	    one of the possible correlation mechanisms, but MUST NOT
	    specify values for those subfields.

Similar text in section 5.6.2

    but MUST NOT specify values for those
    subfields.

5.6.2.  Generating the Answer

    If the Answerer becomes the active party, it MUST add any of the
    "callerid", "uuie" or "dtmf" subfield values.

[SV] Changed the text in 5.6.2 to read

	 If the Answerer becomes the active party, it MUST=20
	 add a value to any of the possible subfields.
	 =20
	  If the Answerer becomes the passive party, it MUST NOT add
	  any values to the subfields in the "cs-correlation" attribute.

8.3.  Registration of new "addrtype" values


    Note to IANA: The current "addrtype" sub-registry structure does not
    capture the fact that a given addrtype is defined in the context of a
    particular "nettype".  The sub-registry structure should be to
    correct that as part of this registration.

Did you mean "should be corrected as part ..."

[SV] We discussed this Note to IANA with the ADs, and as a result the note =
will be removed (and no context will be added for addrtype values in the IA=
NA registry).

Nits/editorial comments:

5.3.3.  Considerations on correlations

    Passive endpoints should expect an incoming CS call for setting up
    the audio bearer.  Passive endpoints MAY suppress the incoming CS
    alert during a certain time periods.  Additional restrictions can be
    applied, such as the passive endpoint not alerting incoming calls
    originated from the number that was observed uduring the offer/answer

Typo: during

[SV]. Fixed.

    negotiation.


5.7.  Formal Syntax

    The following is the formal Augmented Backus-Naur Form (ABNF)
    [RFC5234] syntax that supports the extensions defined in this
    specification.  The syntax is built above the SDP [RFC4566] and the
    tel URI [RFC3966] grammars.  Implementations according to this
    specification MUST be compliant with this syntax.

    Figure 2 shows the formal syntax of the extensions defined in this
    memo.

            ; extension to the connection field originally specified
            ; in RFC 4566

            connection-field   =3D  [%x63 "=3D" nettype SP addrtype SP
            connection-address CRLF]
            ;nettype and addrtype are defined in RFC 4566

            connection-address /=3D  global-number-digits / "-"
            ; global-number-digits specified in RFC 3966

This is good, but you don't specify where CRLF, HEXDIG are defined. I=20
can guess, but it would be better if a reader doesn't have to guess.

[SV] Added comment lines in ABNF that CRLF and DIGIT are defined in RFC5234=
 (there was already a reference to RFC534 for HEXDIG).

            ;subrules for correlation attribute
            attribute          /=3D cs-correlation-attr
            ; attribute defined in RFC 4566
            cs-correlation-attr =3D "cs-correlation:" corr-mechanisms
            corr-mechanisms    =3D corr-mech *(SP corr-mech)
            corr-mech          =3D caller-id-mech / uuie-mech /
                                 dtmf-mech / ext-mech
            caller-id-mech     =3D "callerid" [":" caller-id-value]
            caller-id-value    =3D "+" 1*15DIGIT
            uuie-mech          =3D "uuie" [":" uuie-value]
            uuie-value         =3D 1*65(HEXDIG HEXDIG)
                                 ;This represents up to 130 HEXDIG
                                 ; (65 octets)
                                 ;HEXDIG defined in RFC5234
                                 ;HEXDIG defined as 0-9, A-F
            dtmf-mech          =3D "dtmf" [":" dtmf-value]
            dtmf-value         =3D 1*32(DIGIT / %x41-44 / %x23 / %x2A )
            ;0-9, A-D, '#' and '*'
            ext-mech           =3D ext-mech-name [":" ext-mech-value]
            ext-mech-name      =3D token
            ext-mech-value     =3D token
            ; token is specified in RFC4566

Regards,
Simo


From alexey.melnikov@isode.com  Thu Feb 28 02:36:14 2013
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 2093021F8AD4; Thu, 28 Feb 2013 02:36:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.454
X-Spam-Level: 
X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OekBBPGm1exs; Thu, 28 Feb 2013 02:36:13 -0800 (PST)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id E461C21F8AB4; Thu, 28 Feb 2013 02:36:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1362047771; d=isode.com; s=selector; i=@isode.com; bh=xuQnay2hUetKqIetDc+fFIO6Ed777GeOz73Xyst/37s=; 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=hdscDAUqk8sfWOI+cZd59Trun/jOb4zUmhn6NU0j91cI0Y4lKjEhz+1v+/jN+bb+lKx8p8 LXHl4ypZ8Z18xURgHBC1N6tPW3tNHzA0UHaCGZOf+2sEpNPu2i0tg1LVV4y/ocFGPsMd9N MTqAlwRCItT8gbqnUhmtNI34wGDf96U=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <US8zGQA60DN-@waldorf.isode.com>; Thu, 28 Feb 2013 10:36:11 +0000
Message-ID: <512F331F.9040902@isode.com>
Date: Thu, 28 Feb 2013 10:36:15 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: Simo.Veikkolainen@nokia.com
References: <511A4188.6030101@isode.com> <D09DAE6B636851459F7575D146EFB54B1C875EC9@008-AM1MPN1-025.mgdnok.nokia.com>
In-Reply-To: <D09DAE6B636851459F7575D146EFB54B1C875EC9@008-AM1MPN1-025.mgdnok.nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, iesg@ietf.org, draft-ietf-mmusic-sdp-cs.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mmusic-sdp-cs-17
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 Feb 2013 10:36:14 -0000

On 28/02/2013 07:31, Simo.Veikkolainen@nokia.com wrote:
> Hello Alexey,
Hi Simo,
Thank you for the response.
> Thank you for the review. Please find my answers inline [SV].
>
> -----Original Message-----
> From: ext Alexey Melnikov [mailto:alexey.melnikov@isode.com]
> Sent: 12. helmikuuta 2013 15:20
> To: draft-ietf-mmusic-sdp-cs.all@tools.ietf.org
> Cc: gen-art@ietf.org; The IESG
> Subject: Gen-ART LC review of draft-ietf-mmusic-sdp-cs-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-mmusic-sdp-cs-17
> Reviewer: Alexey Melnikov
> Review Date: 2013-02-12
> IETF LC End Date: 2013-02-01
> IESG Telechat date: N/A
>
>
> Summary: This draft is ready for publication as a Standard Track RFC (with some nits/minor issues):
>
> Major issues:
>
> Minor issues:
>
> 5.2.2.  Media Descriptions
>
>      When "RTP/AVP" is used in the <proto> field, the <fmt> subfield
>      contains the RTP payload type numbers.  We use the <fmt> subfield to
>      indicate the list of available codecs over the circuit-switched
>      bearer, by re-using the conventions and payload type numbers defined
>      for RTP/AVP.  The RTP audio and video media types, which, when
>      applied to PSTN circuit-switched bearers, represent merely an audio
>      or video codec.  The endpoint SHOULD only use those payload type
>      whose corresponding codecs is available for PSTN media streams.
>
> Why is this a SHOULD? What are possible reasons for violating it?
>
> [SV] This is clarified in the following paragraph:
>
>     In some cases, the endpoint is not able to determine the list of
>     available codecs for circuit-switched media streams.  In this case,
>     in order to be syntactically compliant with SDP [RFC4566], the
>     endpoint MUST include a single dash ("-") in the <fmt> subfield.
>
> [SV] Other option is to say that in cases where the endpoint is able to determine the RTP payload numbers, it MUST use those, and in cases when it is not, it MUST use the "dash".
I think this would be much better!
> 5.6.1.  Generating the Initial Offer
>
>      The <fmt> subfield carries the payload type number(s) the endpoint is
>      wishing to use.  Payload type numbers in this case refer to the
>      codecs that the endpoint wishes to use on the PSTN media stream. For
>      example, if the endpoint wishes to use the GSM codec, it would add
>      payload type number 3 in the list of codecs.  The list of payload
>      types SHOULD only contain those codecs the endpoint is able to use on
>      the PSTN bearer.
>
> Again, a SHOULD similar to the one above. Can you please explain the reasoning for it?
>
> [SV] See above.
>
>      If the Offerer is only able to become the passive party in the
>      circuit-switched bearer setup, it MUST add the "callerid", "uuie"
>      and/or "dtmf" subfields,
>
> This text is a bit awkward as you specify this field as extensible. So I
> think you need to add a choice for extensions here.
>
>   [SV] We changed the text to read:
>
> 	    If the Offerer is only able to become the passive party in
> 	    the circuit-switched bearer setup, it MUST add at least
> 	    one of the possible correlation mechanisms, but MUST NOT
> 	    specify values for those subfields.
>
> Similar text in section 5.6.2
>
>      but MUST NOT specify values for those
>      subfields.
Looks good.
> 5.6.2.  Generating the Answer
>
>      If the Answerer becomes the active party, it MUST add any of the
>      "callerid", "uuie" or "dtmf" subfield values.
>
> [SV] Changed the text in 5.6.2 to read
>
> 	 If the Answerer becomes the active party, it MUST
> 	 add a value to any of the possible subfields.
> 	
> 	  If the Answerer becomes the passive party, it MUST NOT add
> 	  any values to the subfields in the "cs-correlation" attribute.
Looks good.
>
> 8.3.  Registration of new "addrtype" values
>
>
>      Note to IANA: The current "addrtype" sub-registry structure does not
>      capture the fact that a given addrtype is defined in the context of a
>      particular "nettype".  The sub-registry structure should be to
>      correct that as part of this registration.
>
> Did you mean "should be corrected as part ..."
>
> [SV] We discussed this Note to IANA with the ADs, and as a result the note will be removed (and no context will be added for addrtype values in the IANA registry).
>
> Nits/editorial comments:
>
> 5.3.3.  Considerations on correlations
>
>      Passive endpoints should expect an incoming CS call for setting up
>      the audio bearer.  Passive endpoints MAY suppress the incoming CS
>      alert during a certain time periods.  Additional restrictions can be
>      applied, such as the passive endpoint not alerting incoming calls
>      originated from the number that was observed uduring the offer/answer
>
> Typo: during
>
> [SV]. Fixed.
>
>      negotiation.
>
>
> 5.7.  Formal Syntax
>
>      The following is the formal Augmented Backus-Naur Form (ABNF)
>      [RFC5234] syntax that supports the extensions defined in this
>      specification.  The syntax is built above the SDP [RFC4566] and the
>      tel URI [RFC3966] grammars.  Implementations according to this
>      specification MUST be compliant with this syntax.
>
>      Figure 2 shows the formal syntax of the extensions defined in this
>      memo.
>
>              ; extension to the connection field originally specified
>              ; in RFC 4566
>
>              connection-field   =  [%x63 "=" nettype SP addrtype SP
>              connection-address CRLF]
>              ;nettype and addrtype are defined in RFC 4566
>
>              connection-address /=  global-number-digits / "-"
>              ; global-number-digits specified in RFC 3966
>
> This is good, but you don't specify where CRLF, HEXDIG are defined. I
> can guess, but it would be better if a reader doesn't have to guess.
>
> [SV] Added comment lines in ABNF that CRLF and DIGIT are defined in RFC5234 (there was already a reference to RFC534 for HEXDIG).
Thanks.
>
>              ;subrules for correlation attribute
>              attribute          /= cs-correlation-attr
>              ; attribute defined in RFC 4566
>              cs-correlation-attr = "cs-correlation:" corr-mechanisms
>              corr-mechanisms    = corr-mech *(SP corr-mech)
>              corr-mech          = caller-id-mech / uuie-mech /
>                                   dtmf-mech / ext-mech
>              caller-id-mech     = "callerid" [":" caller-id-value]
>              caller-id-value    = "+" 1*15DIGIT
>              uuie-mech          = "uuie" [":" uuie-value]
>              uuie-value         = 1*65(HEXDIG HEXDIG)
>                                   ;This represents up to 130 HEXDIG
>                                   ; (65 octets)
>                                   ;HEXDIG defined in RFC5234
>                                   ;HEXDIG defined as 0-9, A-F
>              dtmf-mech          = "dtmf" [":" dtmf-value]
>              dtmf-value         = 1*32(DIGIT / %x41-44 / %x23 / %x2A )
>              ;0-9, A-D, '#' and '*'
>              ext-mech           = ext-mech-name [":" ext-mech-value]
>              ext-mech-name      = token
>              ext-mech-value     = token
>              ; token is specified in RFC4566
>
> Regards,
> Simo
>



From Simo.Veikkolainen@nokia.com  Thu Feb 28 02:48:16 2013
Return-Path: <Simo.Veikkolainen@nokia.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 09C1821F8B96; Thu, 28 Feb 2013 02:48:16 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M5H2rjyZazGm; Thu, 28 Feb 2013 02:48:15 -0800 (PST)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 9C93C21F8523; Thu, 28 Feb 2013 02:48:14 -0800 (PST)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r1SAmBNa010568; Thu, 28 Feb 2013 12:48:11 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.57]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 28 Feb 2013 12:48:11 +0200
Received: from 008-AM1MPN1-025.mgdnok.nokia.com ([169.254.5.248]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi id 14.02.0318.003; Thu, 28 Feb 2013 10:48:22 +0000
From: <Simo.Veikkolainen@nokia.com>
To: <alexey.melnikov@isode.com>
Thread-Topic: Gen-ART LC review of draft-ietf-mmusic-sdp-cs-17
Thread-Index: AQHOCSOKi6GTTOrWcEeEXEgcJqJULJiO9TDQgAA3Z4CAAACncA==
Date: Thu, 28 Feb 2013 10:48:30 +0000
Message-ID: <D09DAE6B636851459F7575D146EFB54B1C87712E@008-AM1MPN1-025.mgdnok.nokia.com>
References: <511A4188.6030101@isode.com> <D09DAE6B636851459F7575D146EFB54B1C875EC9@008-AM1MPN1-025.mgdnok.nokia.com> <512F331F.9040902@isode.com>
In-Reply-To: <512F331F.9040902@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.21.82.215]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 28 Feb 2013 10:48:11.0522 (UTC) FILETIME=[1A48CE20:01CE15A1]
X-Nokia-AV: Clean
Cc: gen-art@ietf.org, iesg@ietf.org, draft-ietf-mmusic-sdp-cs.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mmusic-sdp-cs-17
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 Feb 2013 10:48:16 -0000

Below one comment [SV].

-----Original Message-----
From: ext Alexey Melnikov [mailto:alexey.melnikov@isode.com]=20
Sent: 28 February, 2013 12:36
To: Veikkolainen Simo (Nokia-CTO/Espoo)
Cc: draft-ietf-mmusic-sdp-cs.all@tools.ietf.org; gen-art@ietf.org; iesg@iet=
f.org
Subject: Re: Gen-ART LC review of draft-ietf-mmusic-sdp-cs-17

On 28/02/2013 07:31, Simo.Veikkolainen@nokia.com wrote:
> Hello Alexey,
Hi Simo,
Thank you for the response.
> Thank you for the review. Please find my answers inline [SV].
>
> -----Original Message-----
> From: ext Alexey Melnikov [mailto:alexey.melnikov@isode.com]
> Sent: 12. helmikuuta 2013 15:20
> To: draft-ietf-mmusic-sdp-cs.all@tools.ietf.org
> Cc: gen-art@ietf.org; The IESG
> Subject: Gen-ART LC review of draft-ietf-mmusic-sdp-cs-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/G=
enArtfaq>.
>
> Please resolve these comments along with any other Last Call comments you=
 may receive.
>
> Document: draft-ietf-mmusic-sdp-cs-17
> Reviewer: Alexey Melnikov
> Review Date: 2013-02-12
> IETF LC End Date: 2013-02-01
> IESG Telechat date: N/A
>
>
> Summary: This draft is ready for publication as a Standard Track RFC (wit=
h some nits/minor issues):
>
> Major issues:
>
> Minor issues:
>
> 5.2.2.  Media Descriptions
>
>      When "RTP/AVP" is used in the <proto> field, the <fmt> subfield
>      contains the RTP payload type numbers.  We use the <fmt> subfield to
>      indicate the list of available codecs over the circuit-switched
>      bearer, by re-using the conventions and payload type numbers defined
>      for RTP/AVP.  The RTP audio and video media types, which, when
>      applied to PSTN circuit-switched bearers, represent merely an audio
>      or video codec.  The endpoint SHOULD only use those payload type
>      whose corresponding codecs is available for PSTN media streams.
>
> Why is this a SHOULD? What are possible reasons for violating it?
>
> [SV] This is clarified in the following paragraph:
>
>     In some cases, the endpoint is not able to determine the list of
>     available codecs for circuit-switched media streams.  In this case,
>     in order to be syntactically compliant with SDP [RFC4566], the
>     endpoint MUST include a single dash ("-") in the <fmt> subfield.
>
> [SV] Other option is to say that in cases where the endpoint is able to d=
etermine the RTP payload numbers, it MUST use those, and in cases when it i=
s not, it MUST use the "dash".
I think this would be much better!

[SV] Ok, we'll change the text as:

     If the endpoint is able to determine the list of available codecs for =
circuit-switched=20
    media streams, it MUST use the corresponding payload type numbers in th=
e <fmt>
    subfield.

> 5.6.1.  Generating the Initial Offer
>
>      The <fmt> subfield carries the payload type number(s) the endpoint i=
s
>      wishing to use.  Payload type numbers in this case refer to the
>      codecs that the endpoint wishes to use on the PSTN media stream. For
>      example, if the endpoint wishes to use the GSM codec, it would add
>      payload type number 3 in the list of codecs.  The list of payload
>      types SHOULD only contain those codecs the endpoint is able to use o=
n
>      the PSTN bearer.
>
> Again, a SHOULD similar to the one above. Can you please explain the reas=
oning for it?
>
> [SV] See above.

[SV] In this paragraph, I think it is sufficient just to replace the "SHOUL=
D" with "MUST", i.e.  "The list of payload types MUST only contain..."

Regards,
Simo

>      If the Offerer is only able to become the passive party in the
>      circuit-switched bearer setup, it MUST add the "callerid", "uuie"
>      and/or "dtmf" subfields,
>
> This text is a bit awkward as you specify this field as extensible. So=20
> I think you need to add a choice for extensions here.
>
>   [SV] We changed the text to read:
>
> 	    If the Offerer is only able to become the passive party in
> 	    the circuit-switched bearer setup, it MUST add at least
> 	    one of the possible correlation mechanisms, but MUST NOT
> 	    specify values for those subfields.
>
> Similar text in section 5.6.2
>
>      but MUST NOT specify values for those
>      subfields.
Looks good.
> 5.6.2.  Generating the Answer
>
>      If the Answerer becomes the active party, it MUST add any of the
>      "callerid", "uuie" or "dtmf" subfield values.
>
> [SV] Changed the text in 5.6.2 to read
>
> 	 If the Answerer becomes the active party, it MUST
> 	 add a value to any of the possible subfields.
> =09
> 	  If the Answerer becomes the passive party, it MUST NOT add
> 	  any values to the subfields in the "cs-correlation" attribute.
Looks good.
>
> 8.3.  Registration of new "addrtype" values
>
>
>      Note to IANA: The current "addrtype" sub-registry structure does not
>      capture the fact that a given addrtype is defined in the context of =
a
>      particular "nettype".  The sub-registry structure should be to
>      correct that as part of this registration.
>
> Did you mean "should be corrected as part ..."
>
> [SV] We discussed this Note to IANA with the ADs, and as a result the not=
e will be removed (and no context will be added for addrtype values in the =
IANA registry).
>
> Nits/editorial comments:
>
> 5.3.3.  Considerations on correlations
>
>      Passive endpoints should expect an incoming CS call for setting up
>      the audio bearer.  Passive endpoints MAY suppress the incoming CS
>      alert during a certain time periods.  Additional restrictions can be
>      applied, such as the passive endpoint not alerting incoming calls
>      originated from the number that was observed uduring the=20
> offer/answer
>
> Typo: during
>
> [SV]. Fixed.
>
>      negotiation.
>
>
> 5.7.  Formal Syntax
>
>      The following is the formal Augmented Backus-Naur Form (ABNF)
>      [RFC5234] syntax that supports the extensions defined in this
>      specification.  The syntax is built above the SDP [RFC4566] and the
>      tel URI [RFC3966] grammars.  Implementations according to this
>      specification MUST be compliant with this syntax.
>
>      Figure 2 shows the formal syntax of the extensions defined in this
>      memo.
>
>              ; extension to the connection field originally specified
>              ; in RFC 4566
>
>              connection-field   =3D  [%x63 "=3D" nettype SP addrtype SP
>              connection-address CRLF]
>              ;nettype and addrtype are defined in RFC 4566
>
>              connection-address /=3D  global-number-digits / "-"
>              ; global-number-digits specified in RFC 3966
>
> This is good, but you don't specify where CRLF, HEXDIG are defined. I=20
> can guess, but it would be better if a reader doesn't have to guess.
>
> [SV] Added comment lines in ABNF that CRLF and DIGIT are defined in RFC52=
34 (there was already a reference to RFC534 for HEXDIG).
Thanks.
>
>              ;subrules for correlation attribute
>              attribute          /=3D cs-correlation-attr
>              ; attribute defined in RFC 4566
>              cs-correlation-attr =3D "cs-correlation:" corr-mechanisms
>              corr-mechanisms    =3D corr-mech *(SP corr-mech)
>              corr-mech          =3D caller-id-mech / uuie-mech /
>                                   dtmf-mech / ext-mech
>              caller-id-mech     =3D "callerid" [":" caller-id-value]
>              caller-id-value    =3D "+" 1*15DIGIT
>              uuie-mech          =3D "uuie" [":" uuie-value]
>              uuie-value         =3D 1*65(HEXDIG HEXDIG)
>                                   ;This represents up to 130 HEXDIG
>                                   ; (65 octets)
>                                   ;HEXDIG defined in RFC5234
>                                   ;HEXDIG defined as 0-9, A-F
>              dtmf-mech          =3D "dtmf" [":" dtmf-value]
>              dtmf-value         =3D 1*32(DIGIT / %x41-44 / %x23 / %x2A )
>              ;0-9, A-D, '#' and '*'
>              ext-mech           =3D ext-mech-name [":" ext-mech-value]
>              ext-mech-name      =3D token
>              ext-mech-value     =3D token
>              ; token is specified in RFC4566
>
> Regards,
> Simo
>



From mahoney@nostrum.com  Thu Feb 28 13:41:32 2013
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 98B3121F88A9 for <gen-art@ietfa.amsl.com>; Thu, 28 Feb 2013 13:41:32 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D2F5KpHoczi1 for <gen-art@ietfa.amsl.com>; Thu, 28 Feb 2013 13:41:32 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id E92A221F8899 for <gen-art@ietf.org>; Thu, 28 Feb 2013 13:41:31 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r1SLfUBF049784 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 28 Feb 2013 15:41:31 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <512FCF0A.7070507@nostrum.com>
Date: Thu, 28 Feb 2013 15:41:30 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
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 (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-02-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 Feb 2013 21:41:32 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Peter Yee         2013-03-08   draft-ietf-intarea-nat-reveal-analysis-05

Roni Even         2013-03-26   draft-merkle-ikev2-ke-brainpool-03

Suresh Krishnan   2013-03-11   draft-ietf-manet-olsrv2-metrics-rationale-02


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

And 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


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:

