
From miguel.a.garcia@ericsson.com  Thu Jun  2 03:24:56 2011
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 4AEAFE076A for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 03:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.374
X-Spam-Level: 
X-Spam-Status: No, score=-6.374 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 0FruPJ11eshr for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 03:24:55 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 87F54E074D for <gen-art@ietf.org>; Thu,  2 Jun 2011 03:24:55 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c17ae00000262e-67-4de764f6f429
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 17.73.09774.6F467ED4; Thu,  2 Jun 2011 12:24:54 +0200 (CEST)
Received: from [159.107.24.213] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Thu, 2 Jun 2011 12:24:54 +0200
Message-ID: <4DE764F5.8020900@ericsson.com>
Date: Thu, 2 Jun 2011 12:24:53 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Attila_Tak=E1cs?= <Attila.Takacs@ericsson.com>, Lou Berger <lberger@labn.net>, Diego Caviglia <diego.caviglia@ericsson.com>, <donald.fedyk@alcatel-lucent.com>, Julien Meuric <julien.meuric@orange-ftgroup.com>, Deborah Brungard <db3546@att.com>, Adrian Farrel <adrian@olddog.co.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-01.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2011 10:24:56 -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-ccamp-asymm-bw-bidir-lsps-bis-01.txt
Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
Review Date: 2011-06-02	
IETF LC End Date: 2011-06-06

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

Well written document. There are no issues with it.

Regards,

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

From vkg@bell-labs.com  Thu Jun  2 08:41:28 2011
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 0AF6FE07CB for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 08:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.534
X-Spam-Level: 
X-Spam-Status: No, score=-106.534 tagged_above=-999 required=5 tests=[AWL=0.065, 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 15u7VzqJuWDU for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 08:41:27 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id E9EF1E06FD for <gen-art@ietf.org>; Thu,  2 Jun 2011 08:41:26 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p52FfLsh012825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 2 Jun 2011 10:41:21 -0500 (CDT)
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 p52FfKlj008938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 Jun 2011 10:41:21 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p52FfJdK027100; Thu, 2 Jun 2011 10:41:19 -0500 (CDT)
Message-ID: <4DE7AF28.3000801@bell-labs.com>
Date: Thu, 02 Jun 2011 10:41:28 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc14 Thunderbird/3.1.10
MIME-Version: 1.0
To: draft-ietf-dhc-dhcpv6-relay-supplied-options@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.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: General Area Review Team <gen-art@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>, "john_brzozowski@cable.comcast.com" <john_brzozowski@cable.comcast.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-relay-supplied-options-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: Thu, 02 Jun 2011 15:41:28 -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-dhcpv6-relay-supplied-options-06
Reviewer: Vijay K. Gurbani
Review Date: June-2-2011
IETF LC End Date: Unknown
IESG Telechat date: June-9-2011

Summary: This draft is ready as an Proposed Standard.

Major issues: 0
Minor issues: 2
Nits/editorial comments: 0

Minor issues:

- Abstract
   The abstract is written as one long sentence, which appears
   not to read well.  I would suggest the following text to
   impart more clarity, but please feel free to change as needed:

   DHCPv6 relay agents cannot communicate with DHCPv6 clients
   directly.  However, under some network configurations, the
   relay agent possess some attribute that would be useful to
   the DHCPv6 client.  This document describes a mechanism
   whereby the DHCPv6 relay agent can provide such attributes to
   the DHCPv6 server, who in turn can pass these on to the DHCPv6
   clients.

- Section 2
   "... the function of the relay agent is simply to deliver
   the payload from the server."  Is it "from" the server,
   or "to" the server?  Reading the text until Section 2, it
   appears that "to" the server is more appropriate.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (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  Thu Jun  2 08:48:02 2011
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 3288AE07F9 for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 08:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.542
X-Spam-Level: 
X-Spam-Status: No, score=-106.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 i1RwOf+bYlrK for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 08:48:01 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 6A08BE07DD for <gen-art@ietf.org>; Thu,  2 Jun 2011 08:48:01 -0700 (PDT)
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 p52FlxPH004288 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 2 Jun 2011 10:48:00 -0500 (CDT)
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 p52Flwgt011971 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 Jun 2011 10:47:59 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p52FlwlU003640; Thu, 2 Jun 2011 10:47:58 -0500 (CDT)
Message-ID: <4DE7B0B7.6010809@bell-labs.com>
Date: Thu, 02 Jun 2011 10:48:07 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc14 Thunderbird/3.1.10
MIME-Version: 1.0
To: draft-ietf-pppext-trill-protocol@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.10
Cc: General Area Review Team <gen-art@ietf.org>, carlsonj@workingcode.com, Jari Arkko <jari.arkko@piuha.net>
Subject: [Gen-art] Gen-ART review of draft-ietf-pppext-trill-protocol-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: Thu, 02 Jun 2011 15:48: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-pppext-trill-protocol-06
Reviewer: Vijay K. Gurbani
Review Date: June-2-2011
IETF LC End Date: June-8-2011
IESG Telechat date: June-9-2011

Summary: This draft is ready as an Proposed Standard.

Major issues: 0
Minor issues: 0
Nits/editorial comments: 0

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From jari.arkko@piuha.net  Thu Jun  2 09:34:45 2011
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 9C6D3E07AD for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 09:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, 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 xB5IxyKr0AN7 for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 09:34:45 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id CE5BFE07A2 for <gen-art@ietf.org>; Thu,  2 Jun 2011 09:34:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DFCEC2CC4D; Thu,  2 Jun 2011 19:34:43 +0300 (EEST)
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 vKR0-YWs+q3W; Thu,  2 Jun 2011 19:34:43 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 13B972CC3B; Thu,  2 Jun 2011 19:34:42 +0300 (EEST)
Message-ID: <4DE7BBA2.4090903@piuha.net>
Date: Thu, 02 Jun 2011 19:34:42 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
References: <4DE7B0B7.6010809@bell-labs.com>
In-Reply-To: <4DE7B0B7.6010809@bell-labs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, carlsonj@workingcode.com, draft-ietf-pppext-trill-protocol@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pppext-trill-protocol-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: Thu, 02 Jun 2011 16:34:45 -0000

Thanks for your review, Vijay!

jari

Vijay K. Gurbani kirjoitti:
> 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-pppext-trill-protocol-06
> Reviewer: Vijay K. Gurbani
> Review Date: June-2-2011
> IETF LC End Date: June-8-2011
> IESG Telechat date: June-9-2011
>
> Summary: This draft is ready as an Proposed Standard.
>
> Major issues: 0
> Minor issues: 0
> Nits/editorial comments: 0
>
> Thanks,
>
> - vijay


From mahoney@nostrum.com  Thu Jun  2 14:52:20 2011
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 47AD7E0833 for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 14:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TkDj6IOE6LHn for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 14:52:19 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 669FFE07AE for <gen-art@ietf.org>; Thu,  2 Jun 2011 14:52:19 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-50-31.dllstx.fios.verizon.net [173.71.50.31]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p52LqIvt095599 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 2 Jun 2011 16:52:18 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4DE80611.1070108@nostrum.com>
Date: Thu, 02 Jun 2011 16:52:17 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.50.31 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2011-06-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, 02 Jun 2011 21:52:20 -0000

Hi all,

Here's the link to the new LC assignments:
http://wiki.tools.ietf.org/dav/genart/reviewers-110602-lc.html

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 Jun  2 15:12:16 2011
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 9B78CE0830 for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 15:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yv-zYFUmbabX for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 15:12:16 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD46E0688 for <gen-art@ietf.org>; Thu,  2 Jun 2011 15:12:12 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-50-31.dllstx.fios.verizon.net [173.71.50.31]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p52MCBQg097404 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 2 Jun 2011 17:12:11 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4DE80ABB.906@nostrum.com>
Date: Thu, 02 Jun 2011 17:12:11 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.50.31 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2011-06-09 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, 02 Jun 2011 22:12:16 -0000

Hi all,

Assignments for the telechat can be found here:
http://wiki.tools.ietf.org/dav/genart/reviewers-110609-telechat.html

With the updated 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 Jun  2 20:31:12 2011
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 83A61E07EC for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 20:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.519
X-Spam-Level: 
X-Spam-Status: No, score=-102.519 tagged_above=-999 required=5 tests=[AWL=0.080, 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 yQxsK0op40RF for <gen-art@ietfa.amsl.com>; Thu,  2 Jun 2011 20:31:12 -0700 (PDT)
Received: from hermes.out.tigertech.net (hermes.out.tigertech.net [74.114.88.72]) by ietfa.amsl.com (Postfix) with ESMTP id 13627E07DE for <gen-art@ietf.org>; Thu,  2 Jun 2011 20:31:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id BF06943009F; Thu,  2 Jun 2011 20:31:11 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.101] (pool-71-161-52-156.clppva.btas.verizon.net [71.161.52.156]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 0BC9B4300E2; Thu,  2 Jun 2011 20:31:10 -0700 (PDT)
Message-ID: <4DE8557A.30205@joelhalpern.com>
Date: Thu, 02 Jun 2011 23:31:06 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4DE80611.1070108@nostrum.com>
In-Reply-To: <4DE80611.1070108@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, lionel.morand@orange-ftgroup.com
Subject: [Gen-art]  Review: draft-ietf-dime-local-keytran-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: Fri, 03 Jun 2011 03:31:12 -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-dime-local-keytran-10
     Diameter Attribute-Value Pairs for Cryptographic Key Transport
Reviewer: Joel M. Halpern
Review Date: 02-June-2011
IETF LC End Date: 14-June-2011
IESG Telechat date: N/A

Summary: This document is probably ready for publication as a proposed 
standard

Open Question:
     The document carefully and reasonably does not define the contents 
of the keying material AVP.  This reviewer presumes that those closer to 
the activity will know where the contents have been or will be defined. 
  Are they already defined, or will they be defined in future documents? 
  If they are already defined, would it make sense to state that, and 
identify the location?  (My confusion is that it would seem difficult 
for existing RFCs to define the format of a TLV that did not exist.  But 
that may be a failure of my understanding.)

Thank you,
Joel M. Halpern

From mary.ietf.barnes@gmail.com  Fri Jun  3 12:23:41 2011
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 12F4BE07D2 for <gen-art@ietfa.amsl.com>; Fri,  3 Jun 2011 12:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.575
X-Spam-Level: 
X-Spam-Status: No, score=-103.575 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 OzDBCgUCwABp for <gen-art@ietfa.amsl.com>; Fri,  3 Jun 2011 12:23:39 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id AB290E07B7 for <gen-art@ietf.org>; Fri,  3 Jun 2011 12:23:39 -0700 (PDT)
Received: by vws12 with SMTP id 12so2069981vws.31 for <gen-art@ietf.org>; Fri, 03 Jun 2011 12:23:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=j1+GrP1cgLvJ85GWVT/0pygJCWLnJG66ACGgCTKgCW0=; b=JNMUEuzEMjJBX/RZiV7KwaFf2lVx/s5Umqvx0h5PT4DJoLswC1ZEAQJIQSDd02OWXE etwmJGPWmxcVxueSLhPypHlnyyRbDp352vub87KX4a5SKRQftYY2qj7Rf45KZ8R4EuGf Cpl/jtQVR4g/LXtJojNdrzxMQSkfzK0QsH8YI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=qzkEPMpWC7h811P4cEAq37e1n7FtmSdtRq2ScXJuLdI/JUWi8I+uUN0/z6c4BDad1d 1n194c8FFuCaaqnFunJCk/X4OiS3SlSuEEix0eFBuHEpQcDEGyUhPlqLi40PomQdxPN8 tUXnsgKceuD6e8LG6xzaF5ot0vMrMMa4iEN1U=
MIME-Version: 1.0
Received: by 10.52.98.33 with SMTP id ef1mr101824vdb.23.1307129019056; Fri, 03 Jun 2011 12:23:39 -0700 (PDT)
Received: by 10.52.158.39 with HTTP; Fri, 3 Jun 2011 12:23:39 -0700 (PDT)
Date: Fri, 3 Jun 2011 14:23:39 -0500
Message-ID: <BANLkTiktp7foTwzdFQ1=5g0eu-kZL8NX_A@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: gen-art@ietf.org,  draft-ietf-radext-crypto-agility-requirements.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=20cf307f354adb416d04a4d3b0fe
Cc: Bernard Aboba <Bernard_Aboba@hotmail.com>
Subject: [Gen-art] Gen-ART Last Call Review: draft-ietf-radext-crypto-agility-requirements-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, 03 Jun 2011 19:23:41 -0000

--20cf307f354adb416d04a4d3b0fe
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

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

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

Document: draft-ietf-radext-crypto-agility-requirements-06.txt
Reviewer:  Mary Barnes
Review Date:  3 June 2011
IETF LC End Date:  14 June 2011


Summary:  Almost Ready.

The document is well written and concise.  My primary concerns (minor issue=
s
really) are the many references to the WG, mailing list, IETF meetings, tha=
t
while useful context for folks deeply involved in the activity, the
information is not relevant to a broader audience and clutters the document
IMHO.  In addition, there are a few cases where I think normative language
might be required (going along with the idea that normative language is
appropriate in an Informational document).

Major issue:

- None


Minor issue:

- Introduction: It's my understanding that published RFCs shouldn't
reference specific WGs and this sentence includes "when approved" which
doesn't fit in the body of an RFC. Also, it's my understanding that any
document published by a WG reflects consensus of that WG.  So, I would
suggest this sentence could be better stated as follows:
OLD: This memo,
     when approved, reflects the consensus of the RADIUS Extensions
     (RADEXT) Working Group of the IETF as to the features, properties and
     limitations of the crypto-agility work item for RADIUS.
NEW: This memo describes the features, properties and
     limitations of the crypto-agility solution for RADIUS.

- General.  I don't think you need references to the RADEXT WG since it a
product of that WG - it's listed in the document header and it's obvious in
the tools.  Folks that aren't familiar with IETF probably don't care what W=
G
produced the document.  Subsequent comments below give specific suggestions
around this.

- Introduction,second paragraph. I don't think this necessarily fits the
context of a published RFC. In general, the content of WG documents is base=
d
on mailing list discussion.  And, it's usual that an informational document
is published to provide the type of information that is noted in that
paragraph. So, I would think you could just delete that paragraph.

- Section 1.3.  I don't think the background is necessary. Certainly, the
motivation for this work is useful introductory information, but I think
that initial problem statement/objectives could be reworded in present
 tense in terms of objectives and what this document specifies.

- SEction 2. You could easily strike the first sentence in the first
paragraph without any loss of information. Does it really matter that the
definition was offered at IETF-68?

- Section 2, 4th paragraph.  Why is the second part of the first sentence a
SHOULD NOT?  What happens if this is done?  For example, does this require
additional specification of how the solution is still backwards compatible?
 It's generally a good idea to describe what might happen if someone doesn'=
t
abide by a SHOULD or SHOULD NOT.

- Section 4.2, 5th paragraph, 1st sentence.  Shouldn't the "need not" be
stated using normative language - i.e., stated as "OPTIONAL", something lik=
e
"Support for encryption of individual RADIUS attributes is OPTIONAL for
solutions that provide encryption of entire RADIUS packets".

- Section 4.2, "Limit key scope" paragraph. Should the "not required" be "i=
s
OPTIONAL"?

- Section 4.3, 3rd paragraph.  Shouldn't the "can be" be a "MAY be"? - i.e,
isn't this normative behavior in terms of describing how the requirements
for backwards compatibility can be satisfied or in some cases where they
can't?

- Section 4.3, 4th paragraph.  Shouldn't the "can omit" be a "MAY omit"?

- Section 4.3, 6th paragraph.  Shouldn't the "can be" be a "MAY be"?

- Section 4.6. This could be reworded to remove the references to IETF-70
and just state something like the following:
OLD:
   At the
   IETF-70 meeting, and leading up to that meeting, the RADEXT WG
   debated whether or not RFC 4107 would require a RADIUS Crypto-Agility
   solution to feature Automated Key Management (AKM).  The working
   group determined that AKM was not inherently required for RADIUS
   based on the following points:
NEW:
   Consideration was given as to
   whether or not RFC 4107 would require a RADIUS Crypto-Agility
   solution to feature Automated Key Management (AKM).  It was
   determined that AKM was not inherently required for RADIUS based
   on the following points:

Nits:
-----
- Section 4.6, 1st paragraph after the bulleted list: .., the same time, =
=85
 ->  =85, at the same time,...

--20cf307f354adb416d04a4d3b0fe
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>I am the assigned Gen-ART reviewer for this draft. For background on G=
en-ART, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/are=
a/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq</a>&gt;.</div>
<div><br></div><div>Please resolve these comments along with any other Last=
 Call comments you may receive.</div><div><br></div><div>Document: draft-ie=
tf-radext-crypto-agility-requirements-06.txt</div><div>Reviewer: =A0Mary Ba=
rnes=A0</div>
<div>Review Date: =A03 June 2011</div><div>IETF LC End Date: =A014 June 201=
1</div><div><br></div><div><br></div><div>Summary: =A0Almost Ready. =A0</di=
v><div><br></div><div>The document is well written and concise. =A0My prima=
ry concerns (minor issues really) are the many references to the WG, mailin=
g list, IETF meetings, that while useful context for folks deeply involved =
in the activity, the information is not relevant to a broader audience and =
clutters the document IMHO. =A0In addition, there are a few cases where I t=
hink normative language might be required (going along with the idea that n=
ormative language is appropriate in an Informational document).</div>
<div><br></div><div>Major issue:</div><div><br></div><div>- None=A0</div><d=
iv>=A0</div><div><br></div><div>Minor issue:</div><div><br></div><div>- Int=
roduction: It&#39;s my understanding that published RFCs shouldn&#39;t refe=
rence specific WGs and this sentence includes &quot;when approved&quot; whi=
ch doesn&#39;t fit in the body of an RFC. Also, it&#39;s my understanding t=
hat any document published by a WG reflects consensus of that WG. =A0So, I =
would suggest this sentence could be better stated as follows:</div>
<div>OLD: This memo,</div><div>=A0=A0 =A0 when approved, reflects the conse=
nsus of the RADIUS Extensions</div><div>=A0=A0 =A0 (RADEXT) Working Group o=
f the IETF as to the features, properties and</div><div>=A0=A0 =A0 limitati=
ons of the crypto-agility work item for RADIUS.=A0</div>
<div>NEW: This memo describes the features, properties and</div><div>=A0=A0=
 =A0 limitations of the crypto-agility solution for RADIUS.</div><div><br><=
/div><div>- General. =A0I don&#39;t think you need references to the RADEXT=
 WG since it a product of that WG - it&#39;s listed in the document header =
and it&#39;s obvious in the tools. =A0Folks that aren&#39;t familiar with I=
ETF probably don&#39;t care what WG produced the document. =A0Subsequent co=
mments below give specific suggestions around this.</div>
<div><br></div><div>- Introduction,second paragraph. I don&#39;t think this=
 necessarily fits the context of a published RFC. In general, the content o=
f WG documents is based on mailing list discussion. =A0And, it&#39;s usual =
that an informational document is published to provide the type of informat=
ion that is noted in that paragraph. So, I would think you could just delet=
e that paragraph.=A0</div>
<div><br></div><div>- Section 1.3. =A0I don&#39;t think the background is n=
ecessary. Certainly, the motivation for this work is useful introductory in=
formation, but I think that initial problem statement/objectives could be r=
eworded in present =A0 =A0tense in terms of objectives and what this docume=
nt specifies.=A0</div>
<div>=A0</div><div>- SEction 2. You could easily strike the first sentence =
in the first paragraph without any loss of information. Does it really matt=
er that the definition was offered at IETF-68?</div><div><br></div><div>- S=
ection 2, 4th paragraph. =A0Why is the second part of the first sentence a =
SHOULD NOT? =A0What happens if this is done? =A0For example, does this requ=
ire additional specification of how the solution is still backwards compati=
ble? =A0It&#39;s generally a good idea to describe what might happen if som=
eone doesn&#39;t abide by a SHOULD or SHOULD NOT.=A0</div>
<div><br></div><div>- Section 4.2, 5th paragraph, 1st sentence. =A0Shouldn&=
#39;t the &quot;need not&quot; be stated using normative language - i.e., s=
tated as &quot;OPTIONAL&quot;, something like &quot;Support for encryption =
of individual RADIUS attributes is OPTIONAL for solutions that provide encr=
yption of entire RADIUS packets&quot;.=A0</div>
<div><br></div><div>- Section 4.2, &quot;Limit key scope&quot; paragraph. S=
hould the &quot;not required&quot; be &quot;is OPTIONAL&quot;?</div><div><b=
r></div><div>- Section 4.3, 3rd paragraph. =A0Shouldn&#39;t the &quot;can b=
e&quot; be a &quot;MAY be&quot;? - i.e, isn&#39;t this normative behavior i=
n terms of describing how the requirements for backwards compatibility can =
be satisfied or in some cases where they can&#39;t?=A0</div>
<div><br></div><div>- Section 4.3, 4th paragraph. =A0Shouldn&#39;t the &quo=
t;can omit&quot; be a &quot;MAY omit&quot;? =A0</div><div><br></div><div>- =
Section 4.3, 6th paragraph. =A0Shouldn&#39;t the &quot;can be&quot; be a &q=
uot;MAY be&quot;?</div>
<div><br></div><div>- Section 4.6. This could be reworded to remove the ref=
erences to IETF-70 and just state something like the following:=A0</div><di=
v>OLD:</div><div>=A0=A0 At the</div><div>=A0=A0 IETF-70 meeting, and leadin=
g up to that meeting, the RADEXT WG</div>
<div>=A0=A0 debated whether or not RFC 4107 would require a RADIUS Crypto-A=
gility</div><div>=A0=A0 solution to feature Automated Key Management (AKM).=
 =A0The working</div><div>=A0=A0 group determined that AKM was not inherent=
ly required for RADIUS</div>
<div>=A0=A0 based on the following points:</div><div>NEW:=A0</div><div>=A0=
=A0 Consideration was given as to=A0</div><div>=A0=A0 whether or not RFC 41=
07 would require a RADIUS Crypto-Agility</div><div>=A0=A0 solution to featu=
re Automated Key Management (AKM). =A0It was=A0</div>
<div>=A0=A0 determined that AKM was not inherently required for RADIUS base=
d=A0</div><div>=A0=A0 on the following points: =A0 =A0</div><div><br></div>=
<div>Nits:</div><div>-----</div><div>- Section 4.6, 1st paragraph after the=
 bulleted list: .., the same time, =85 =A0-&gt; =A0=85, at the same time,..=
.</div>

--20cf307f354adb416d04a4d3b0fe--

From ben@nostrum.com  Fri Jun  3 13:09:54 2011
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 B147AE06BF; Fri,  3 Jun 2011 13:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.45
X-Spam-Level: 
X-Spam-Status: No, score=-101.45 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, 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 v0QaP27myuny; Fri,  3 Jun 2011 13:09:53 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D1E6DE07B3; Fri,  3 Jun 2011 13:09:52 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p53K9mLf021853 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 3 Jun 2011 15:09:50 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Fri, 3 Jun 2011 15:09:47 -0500
Message-Id: <5E434E92-2EB7-43B3-A29F-8410B1AC23AE@nostrum.com>
To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-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, 03 Jun 2011 20:09: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-dime-ikev2-psk-diameter-07
Reviewer: Ben Campbell
Review Date: 2011-06-03
IETF LC End Date: 2011-06-03


Summary:

This draft is almost ready for publication as a proposed standard. I =
have a question concerning the procedure for generating PSKs, and a =
number of minor and editorial comments.


Major issues:

The draft says that the procedure that the HAAA follows to generate the =
PSK is out of scope. But doesn't the IKE2 initiator need to understand =
the procedure? If the procedure is not defined somewhere, how you =
achieve any degree of interoperability?


Minor issues:

-- section 4.1, 1st paragraph:"The IDi payload extracted from the =
IKE_AUTH message MUST contain an identity that is meaningful for the =
Diameter infrastructure, such as a Network Access Identifier (NAI), =
since it is used by the IKEv2 Server to populate the User-Name AVP in =
the Diameter message. "

Do you mean that as a normative MUST, or a statement of fact? If =
normative, isn't that a requirement on the initiator?

-- section 10:

The security considerations should describe the threat models. We're =
talking about requesting an authentication key from a third party, which =
is tricky from a security perspective. Does the PSK have greater =
security concerns than for Diameter AVPs in general? In particular, what =
are the consequences if the PSK is disclosed or tampered with?=20

-- section 10, 1st paragraph: "Furthermore, any agents that process =
IKEv2-PSK-Answer messages can see the contents of the Key AVP. For this =
reason, this specification strongly recommends avoiding Diameter agents =
when they cannot be trusted to keep the keys secret."

Should that be normative? Is there no way to protect the PSK AVP from =
diameter agents? E.g. can it be encrypted?

-- section 10, 2nd paragraph: "this specification also recommends the =
use of nonces included in IKEv2-PSK-Request."

Actually, the spec requires it using a normative SHALL.


Nits/editorial comments:

-- IDNits reports an out-of-date reference

-- Section 1, general:

It's probably worth elaborating that we are talking about a PSK used =
during the IKEv2 authentication process, which is distinct from any =
shared secrets negotiated by IKE for use in the resulting SA.

-- Section 1, paragraph 1, 1st sentence:

The use, and lack of, commas in this sentence is confusing. It's easy to =
parse as saying IKE2 is a protocol and a set of algorithms, when I think =
you meant to say that the resulting SA has a set of algorithms along =
with the shared secret.

-- section 4.1, 2nd paragraph: "message is routed to the IKEv2 Peer=92s =
HAAA."

What routes it? ( be careful not to let passive voice obscure =
responsibilities)

-- section 4.2, paragraph 1: "The HAAA may maintain state or may be =
stateless"

What kind of state? I assume from the following sentences you mean =
Diameter session state, but it should be explicit.

-- "indicated by presence or absence of the Auth-Session-State AVP."

In what message(s)?

-- section 4.2, paragraph 2:

This sentence is long and hard to parse. Can it be broken up?

-- section 5.1, last paragraph: "SHALL be used to identify the =
appropriate PSK."

Shall be used by what? (passive voice obscures responsibility)

-- 5.2, last paragraph: "associated key SHALL NOT be used if the =
lifetime has expired."

SHALL NOT be used by what?

-- section 8, first paragraph: "whether the AVP MAY be encrypted."

I don't see anything about encryption in the table.

-- section 8, AVP table:

Are all the Key* AVPs intended to have the same code? I assume not, but =
mixing in TBD with the various TBD* placeholders is confusing.

-- section 9:

Consider a note to the RFC editor to change all occurances of TBD(x) =
with the IANA assignment throughout the entire document. Since these are =
scattered throughout the doc, the intent may not be obvious to them.



From brian.e.carpenter@gmail.com  Sat Jun  4 13:16:02 2011
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 E9B4121F84ED for <gen-art@ietfa.amsl.com>; Sat,  4 Jun 2011 13:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101
X-Spam-Level: 
X-Spam-Status: No, score=-101 tagged_above=-999 required=5 tests=[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 zSQZwOPOQDhL for <gen-art@ietfa.amsl.com>; Sat,  4 Jun 2011 13:16:02 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id EE47021F84E9 for <gen-art@ietf.org>; Sat,  4 Jun 2011 13:16:01 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2086385fxm.31 for <gen-art@ietf.org>; Sat, 04 Jun 2011 13:16:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type; bh=Yavs8FfHbOL4tcsGOy+oM8UWlrdBZ3eHGSqkPftT6BA=; b=cUkGD6llCyoOdHv/my4NDUm99Lof2Unriw2TqEJUOQahi3J/bBy08TkVC7inh16Dxh J84FiUjtGgw20xbqoKzuBz+87iudb7V5r13ErSCxkRRu1PqzF8hXSPNhH4YOtveVrrkO i0Dp92kYfOA0ip2PVzrXxcmWato3Q9cjwx5aU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; b=Z5ir99wC5THU7n4EXI71XQvsS5CZxdXdOk/2s6N6la4YhyFK8c1JLBnKJ0TBYVGzX1 o8Djwia2SBZMD1xXr8AauMvQeFUO5DKQfebUSwRjglypST8FhNo1iYH+ki07z+JRdd/7 kyiiO1KswdkgHLiizk6XFKga7m3k77N9Cwh6w=
Received: by 10.223.143.17 with SMTP id s17mr3552134fau.34.1307218560891; Sat, 04 Jun 2011 13:16:00 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id r10sm854964fah.26.2011.06.04.13.15.57 (version=SSLv3 cipher=OTHER); Sat, 04 Jun 2011 13:16:00 -0700 (PDT)
Message-ID: <4DEA9277.4020702@gmail.com>
Date: Sun, 05 Jun 2011 08:15:51 +1200
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-tcpm-persist.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------040005010709080008030908"
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Sat, 04 Jun 2011 20:16:03 -0000

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

Please see attached review.





--------------040005010709080008030908
Content-Type: text/plain;
 name="draft-ietf-tcpm-persist-04-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-tcpm-persist-04-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZyb20geW91ciBkb2N1bWVudCBzaGVwaGVy
ZA0Kb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoN
CkRvY3VtZW50OiBkcmFmdC1pZXRmLXRjcG0tcGVyc2lzdC0wNC50eHQNClJldmlld2VyOiBC
cmlhbiBDYXJwZW50ZXINClJldmlldyBEYXRlOiAyMDExLTA2LTA1DQpJRVRGIExDIEVuZCBE
YXRlOiAyMDExLTA2LTAzDQpJRVNHIFRlbGVjaGF0IGRhdGU6IDIwMTEtMDYtMDkNCg0KU3Vt
bWFyeTogQWxtb3N0IHJlYWR5LCBidXQuLi4NCi0tLS0tLS0tDQoNCkNvbW1lbnQ6IA0KLS0t
LS0tLS0NCg0KKFRoZXNlIGFyZSBteSBMYXN0IENhbGwgY29tbWVudHMsIHRvIHdoaWNoIEkn
dmUgc2VlbiBubyByZXNwb25zZSBzbyBmYXIuKQ0KDQpJIGhhdmUgbm8gcHJvYmxlbSB3aXRo
IHRoZSBtZXNzYWdlIG9mIHRoaXMgZHJhZnQsIGJ1dCB0aGVyZSBhcmUgcHJvYmxlbXMgaW4N
CnRoZSB3YXkgdGhlIG1lc3NhZ2UgaXMgZGVsaXZlcmVkLg0KDQpNYWpvciBpc3N1ZXM6DQot
LS0tLS0tLS0tLS0tDQoNCldoeSBpcyB0aGlzIEluZm9ybWF0aW9uYWw/IElmIGl0IG1hdHRl
cnMsIGl0IHNob3VsZCBiZSBhIFN0YW5kYXJkcyBUcmFjaw0KZG9jdW1lbnQgdXBkYXRpbmcg
UkZDIDExMjIuDQoNCklmIGl0J3Mgbm90IGEgU3RhbmRhcmRzIFRyYWNrIGRvY3VtZW50LCB3
aHkgaXMgaXQgdXNpbmcgUkZDIDIxMTkgbGFuZ3VhZ2U/DQoNCiIgIFRoZSBwcm9ibGVtIGlz
IGFwcGxpY2FibGUgdG8gVENQIGFuZCBUQ1AgZGVyaXZlZCBmbG93LWNvbnRyb2xsZWQNCiAg
IHRyYW5zcG9ydCBwcm90b2NvbHMgbGlrZSBTQ1RQLiINCg0KVGhpcyBzdGF0ZW1lbnQgaXMg
bm90IG11Y2ggdXNlIG9uIGl0cyBvd24uIERvZXMgdGhpcyBkcmFmdCBhcHBseSB0byBTQ1RQ
Pw0KSWYgaXQgZG9lcywgd2hpY2ggdGV4dCBpbiB0aGUgU0NUUCBzcGVjIGlzIGFmZmVjdGVk
Pw0KDQpJbXBvcnRhbnQgZWRpdG9yaWFsIGlzc3VlczoNCi0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KDQpUaGUgZHJhZnQgc2F5czoNCg0KKGJlZ2luIHF1b3RlIGZyb20gZHJhZnQt
aWV0Zi10Y3BtLXBlcnNpc3QtMDQpDQoxLiAgSW50cm9kdWN0aW9uDQoNCiAgIFNlY3Rpb24g
NC4yLjIuMTcgb2YgUmVxdWlyZW1lbnRzIGZvciBJbnRlcm5ldCBIb3N0cyBbUkZDMTEyMl0g
c2F5czoNCg0KICAgICAgIkEgVENQIE1BWSBrZWVwIGl0cyBvZmZlcmVkIHJlY2VpdmUgd2lu
ZG93IGNsb3NlZCBpbmRlZmluaXRlbHkuDQogICAgICBBcyBsb25nIGFzIHRoZSByZWNlaXZp
bmcgVENQIGNvbnRpbnVlcyB0byBzZW5kIGFja25vd2xlZGdtZW50cyBpbg0KICAgICAgcmVz
cG9uc2UgdG8gdGhlIHByb2JlIHNlZ21lbnRzLCB0aGUgc2VuZGluZyBUQ1AgTVVTVCBhbGxv
dyB0aGUNCiAgICAgIGNvbm5lY3Rpb24gdG8gc3RheSBvcGVuLiINCg0KICAgICAgRElTQ1VT
U0lPTjoNCg0KICAgICAgICAgSXQgaXMgZXh0cmVtZWx5IGltcG9ydGFudCB0byByZW1lbWJl
ciB0aGF0IEFDSyAoYWNrbm93bGVkZ21lbnQpDQogICAgICAgICBzZWdtZW50cyB0aGF0IGNv
bnRhaW4gbm8gZGF0YSBhcmUgbm90IHJlbGlhYmx5IHRyYW5zbWl0dGVkIGJ5DQogICAgICAg
ICBUQ1AuDQooZW5kIHF1b3RlIGZyb20gZHJhZnQtaWV0Zi10Y3BtLXBlcnNpc3QtMDQpDQoN
ClRoZSBjbG9zaW5nIHF1b3RhdGlvbiBtYXJrIGlzIGluY29ycmVjdGx5IHBsYWNlZCAtIGl0
IGJlbG9uZ3MgYWZ0ZXIgDQonVENQLicgbm90IGFmdGVyICdvcGVuLicuIFRoZSByZWFkZXIg
d2lsbCBiZSBtaXNsZWQgYnkgdGhpcy4gWW91IG1pZ2h0DQpjb25zaWRlciBldmVuIGNsZWFy
ZXIgZmxhZ3MgZm9yIHRoZSBleHRyYWN0LCBhcyBJIGhhdmUgdXNlZCBhYm92ZS4NCg0KDQoo
YmVnaW4gcXVvdGUgZnJvbSBkcmFmdC1pZXRmLXRjcG0tcGVyc2lzdC0wNCkNCjUuICBDbGFy
aWZpY2F0aW9uIFJlZ2FyZGluZyBSRkMgMTEyMiBSZXF1aXJlbWVudHMNCg0KICAgQXMgc3Rh
dGVkIGluIFJlcXVpcmVtZW50cyBmb3IgSW50ZXJuZXQgSG9zdHMgW1JGQzExMjJdLCBhIFRD
UA0KICAgaW1wbGVtZW50YXRpb24gTVVTVCBOT1QgY2xvc2UgYSBjb25uZWN0aW9uIG1lcmVs
eSBiZWNhdXNlIGl0IHNlZW1zIHRvDQogICBiZSBzdHVjayBpbiB0aGUgWldQIG9yIHBlcnNp
c3QgY29uZGl0aW9uLiAgVW5zdGF0ZWQgaW4gUkZDIDExMjIsIGJ1dA0KICAgaW1wbGljaXQg
Zm9yIHN5c3RlbSByb2J1c3RuZXNzLCBhIFRDUCBpbXBsZW1lbnRhdGlvbiBNVVNUIGFsbG93
DQogICBjb25uZWN0aW9ucyBpbiB0aGUgWldQIG9yIHBlcnNpc3QgY29uZGl0aW9uIHRvIGJl
IGNsb3NlZCBvciBhYm9ydGVkDQogICBieSB0aGVpciBhcHBsaWNhdGlvbnMgb3Igb3RoZXIg
cmVzb3VyY2UgbWFuYWdlbWVudCByb3V0aW5lcyBpbiB0aGUNCiAgIG9wZXJhdGluZyBzeXN0
ZW0uDQooZW5kIHF1b3RlIGZyb20gZHJhZnQtaWV0Zi10Y3BtLXBlcnNpc3QtMDQpDQoNCkJv
dGggdGhlc2Ugc2VudGVuY2VzIHNlZW0gdG8gYXNzZXJ0IHRoaW5ncyBhYm91dCBSRkMgMTEy
MiwgYW5kIGFib3V0IHRoZSBzdGF0ZQ0Kb2YgbWluZCBvZiBpdHMgZWRpdG9yLCB0aGF0IEkg
aGF2ZSBubyByZWFzb24gdG8gYmVsaWV2ZS4gUkZDIDExMjIgZG9lc24ndA0Kc2F5IGFueXRo
aW5nIGFib3V0IHRoZSBNVVNUIE5PVCBiZWluZyAibWVyZWx5IGJlY2F1c2UiIGFueXRoaW5n
IC0gdGhlIHN0YXRlbWVudA0KaW4gc2VjdGlvbiA0LjIuMi4xNyBpcyBjb21wbGV0ZWx5IHVu
YW1iaWd1b3VzLiBBbmQgSSBkb24ndCBzZWUgYW55IGdyb3VuZHMgZm9yDQphc3NlcnRpbmcg
dGhhdCB0aGUgc2Vjb25kIHNlbnRlbmNlIGlzIGFueSB3YXkgaW1wbGljaXQgaW4gUkZDIDEx
MjIuIFF1aXRlIHRoZQ0Kb3Bwb3NpdGUgLSB5b3UgYXJlIGRvY3VtZW50aW5nIGFuIG92ZXJz
aWdodC4gSSB0aGluayB5b3Ugc2hvdWxkIHNheSBzby4gRm9yDQpleGFtcGxlOg0KDQo1LiAg
VXBkYXRlIHRvIFJGQyAxMTIyIFJlcXVpcmVtZW50cw0KDQogICBSZXF1aXJlbWVudHMgZm9y
IEludGVybmV0IEhvc3RzIFtSRkMxMTIyXSBzdGF0ZXMgdGhhdCBhIFRDUA0KICAgaW1wbGVt
ZW50YXRpb24gTVVTVCBOT1QgY2xvc2UgYSBjb25uZWN0aW9uIGlmIGl0IHNlZW1zIHRvDQog
ICBiZSBzdHVjayBpbiB0aGUgWldQIG9yIHBlcnNpc3QgY29uZGl0aW9uLCBhcyBsb25nIGFz
IGFja293bGVkZ2VtZW50cw0KICAgYXJlIGJlaW5nIHJlY2VpdmVkLiBUaGUgcHJlc2VudCBk
b2N1bWVudCB1cGRhdGVzIHRoaXMgcmVxdWlyZW1lbnQgYnkNCiAgIGFkZGluZyB0aGF0IGEg
VENQIGltcGxlbWVudGF0aW9uIE1VU1QgYWxsb3cgY29ubmVjdGlvbnMgaW4gdGhlIFpXUA0K
ICAgb3IgcGVyc2lzdCBjb25kaXRpb24gdG8gYmUgY2xvc2VkIG9yIGFib3J0ZWQgYnkgdGhl
aXIgYXBwbGljYXRpb25zIG9yDQogICBvdGhlciByZXNvdXJjZSBtYW5hZ2VtZW50IHJvdXRp
bmVzIGluIHRoZSBvcGVyYXRpbmcgc3lzdGVtLg0KDQpNaW5vciBlZGl0b3JpYWwNCi0tLS0t
LS0tLS0tLS0tLQ0KDQpUaGVzZSBhcmUgZXhhbXBsZXMgLSBJIHRoaW5rIHRoZSBFbmdsaXNo
IG5lZWRzIGEgZ2VuZXJhbCB0aWR5LXVwOg0KDQoiICBQZXIgUmVxdWlyZW1lbnRzIGZvciBJ
bnRlcm5ldCBIb3N0cyBbUkZDMTEyMl0gYXMgbG9uZyBhcyB0aGUgQUNLJ3MNCiAgIGFyZSBi
ZWluZyByZWNlaXZlZCBmb3Igd2luZG93IHByb2JlcywgYSBjb25uZWN0aW9uIGNhbiBjb250
aW51ZSB0bw0KICAgc3RheSBpbiB0aGUgcGVyc2lzdCBjb25kaXRpb24uIg0KDQpUaGUgdXNl
IG9mICJQZXIiIGxpa2UgdGhpcyBpcywgd2VsbCwgc2xvcHB5LiAiQWNjb3JkaW5nIHRvLi4u
IiB3b3VsZCBiZSBiZXR0ZXIuDQpUaGVyZSBpcyBhIG1pc3NpbmcgY29tbWEgYWZ0ZXIgIltS
RkMxMTIyXSIuDQoiQUNLJ3MiIHNob3VsZCBiZSAiQUNLcyIuDQoNCiIgIFN5c3RlbXMgdGhh
dCBhZGhlcmUgdG9vIHN0cmljdGx5IHRvIHRoZSBhYm92ZSB2ZXJiaWFnZSBvZg0KICAgUmVx
dWlyZW1lbnRzIGZvciBJbnRlcm5ldCBIb3N0cyBbUkZDMTEyMl0uLi4iDQoNCkl0IGlzbid0
ICJ2ZXJiaWFnZSIsIHdoaWNoIG1lYW5zICJUaGUgdXNlIG9mIG1hbnkgd29yZHMgd2l0aG91
dCBuZWNlc3NpdHksIG9yIHdpdGggDQpsaXR0bGUgc2Vuc2U7IGEgc3VwZXJhYnVuZGFuY2Ug
b2Ygd29yZHM7IHZlcmJvc2l0eTsgd29yZGluZXNzIiBhY2NvcmRpbmcgdG8gbXkgDQpmYXZv
dXJpdGUgb24tbGluZSBkaWN0aW9uYXJ5LiBJdCBpcyBqdXN0ICJ3b3JkaW5nIi4NCg0KDQo=
--------------040005010709080008030908--

From ananth@cisco.com  Sat Jun  4 14:53:48 2011
Return-Path: <ananth@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 1E78E21F84F9 for <gen-art@ietfa.amsl.com>; Sat,  4 Jun 2011 14:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level: 
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[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 HEeaIXocnXnn for <gen-art@ietfa.amsl.com>; Sat,  4 Jun 2011 14:53:47 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2DC0E21F84D0 for <gen-art@ietf.org>; Sat,  4 Jun 2011 14:53:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ananth@cisco.com; l=10474; q=dns/txt; s=iport; t=1307224427; x=1308434027; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=jExaycOu8yJEZN/zm7OEJE5oxRmy4PzlpsaddIAdegU=; b=OdNVyEIDyLAaRfLiax9XFIN5MHT6g52EFC2KVgaHctlrR1Nk/kIlLlKm /F6F6+b19M2fdkk+9+Vg/LjaG5RdlgfnmYeaskcWYnNob0btSzpBtP44S oipcES0ksiybjHMZt3FghI5oxSxDpZtapHSM8/26ABXqWdVkaP0cKLxTa c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEBAKuo6k2rRDoG/2dsb2JhbABThEqTHI1rdXepLI0Jj26BK4NsgQoEhnSOVoQohmE
X-IronPort-AV: E=Sophos;i="4.65,321,1304294400"; d="scan'208";a="330226945"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-3.cisco.com with ESMTP; 04 Jun 2011 21:53:46 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p54LrkW0014393; Sat, 4 Jun 2011 21:53:46 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 4 Jun 2011 14:53:46 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Sat, 4 Jun 2011 14:51:53 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <4DEA9277.4020702@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
Thread-Index: Acwi9EPj+JNClqKKQcKAjNrIPPtH/QACOTvQ
References: <4DEA9277.4020702@gmail.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, <draft-ietf-tcpm-persist.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
X-OriginalArrivalTime: 04 Jun 2011 21:53:46.0747 (UTC) FILETIME=[E1394CB0:01CC2301]
Cc: David Harrington <ietfdbh@comcast.net>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Sat, 04 Jun 2011 21:53:48 -0000

SGkgQnJpYW4sDQogICAgU29ycnkgYWJvdXQgdGhlIGRlbGF5LCBJIGhhZCBjaGF0dGVkIHdpdGgg
dGhlIGNvLWF1dGhvcnMgYW5kIGhhdmUgYmVlbiB3YW50aW5nIHRvIHJlcGx5IHRvIHRoaXMgZW1h
aWwsIGJ1dCBqdXN0IGZvdW5kIHRpbWUuDQoNCkkgYW0gZW5jbG9zaW5nIHRoZSBvcmlnaW5hbCBh
bmQgdGhlIHJlc3BvbnNlcy4gUmVzcG9uc2VzIGFyZSBwcmVmaXhlZCB3aXRoIEFOQT4gZm9yIGVh
c2llciByZWFkYWJpbGl0eS4NCg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT0gTGFzdCBjYWxsIGNvbW1lbnRzID09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT0NCltSZXNwb25zZXMgYXJlIHByZWZpeGVkIHdpdGggQU5BPl0NCg0KSSBh
bSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9yIGJhY2tn
cm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6Ly93aWtpLnRv
b2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0KDQpQbGVhc2Ugd2Fp
dCBmb3IgZGlyZWN0aW9uIGZyb20geW91ciBkb2N1bWVudCBzaGVwaGVyZA0Kb3IgQUQgYmVmb3Jl
IHBvc3RpbmcgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoNCkRvY3VtZW50OiBkcmFmdC1p
ZXRmLXRjcG0tcGVyc2lzdC0wNC50eHQNClJldmlld2VyOiBCcmlhbiBDYXJwZW50ZXINClJldmll
dyBEYXRlOiAyMDExLTA2LTA1DQpJRVRGIExDIEVuZCBEYXRlOiAyMDExLTA2LTAzDQpJRVNHIFRl
bGVjaGF0IGRhdGU6IDIwMTEtMDYtMDkNCg0KU3VtbWFyeTogQWxtb3N0IHJlYWR5LCBidXQuLi4N
Ci0tLS0tLS0tDQoNCkNvbW1lbnQ6IA0KLS0tLS0tLS0NCg0KKFRoZXNlIGFyZSBteSBMYXN0IENh
bGwgY29tbWVudHMsIHRvIHdoaWNoIEkndmUgc2VlbiBubyByZXNwb25zZSBzbyBmYXIuKQ0KDQpB
TkE+IGFwb2xvZ2llcyBmb3IgdGhlIGRlbGF5Lg0KDQpJIGhhdmUgbm8gcHJvYmxlbSB3aXRoIHRo
ZSBtZXNzYWdlIG9mIHRoaXMgZHJhZnQsIGJ1dCB0aGVyZSBhcmUgcHJvYmxlbXMgaW4NCnRoZSB3
YXkgdGhlIG1lc3NhZ2UgaXMgZGVsaXZlcmVkLg0KDQpNYWpvciBpc3N1ZXM6DQotLS0tLS0tLS0t
LS0tDQoNCldoeSBpcyB0aGlzIEluZm9ybWF0aW9uYWw/IElmIGl0IG1hdHRlcnMsIGl0IHNob3Vs
ZCBiZSBhIFN0YW5kYXJkcyBUcmFjaw0KZG9jdW1lbnQgdXBkYXRpbmcgUkZDIDExMjIuDQoNCkFO
QT4gSSBhZ3JlZSwgaXQgc2hvdWxkIGhhdmUgYmVlbiBhIHN0YW5kYXJkcyB0cmFjayBkb2N1bWVu
dCBzaW5jZSBpdCBjbGFyaWZpZXMgdGhlIFJGQyAxMTIyIHdvcmRpbmcuIEkgYmVsaWV2ZSB0aGUg
VENQTSBjaGFpcnMgYW5kIFdHIGdyb3VwIGhhZCANCkFOQT4gYXBwcm92ZWQgdXMgdG8gY29tZSB1
cCB3aXRoIGEgaW5mb3JtYXRpb25hbCBSRkMgdGhhdCBjbGFyaWZpZXMgdGhlIGludGVudGlvbiBv
ZiBSRkMgMTEyMiByZWdhcmRpbmcgcGVyc2lzdCBzdGF0ZS4gV2UgaGF2ZSBubyBwcm9ibGVtcyBt
YWtpbmcgQU5BPiB0aGlzIGEgc3RhbmRhcmRzIHRyYWNrLCBJJ2xsIGxlYXZlIGl0IHRvIHRoZSBj
aGFpcnMgdG8gY29tbWVudCBvbiB0aGlzLg0KDQpJZiBpdCdzIG5vdCBhIFN0YW5kYXJkcyBUcmFj
ayBkb2N1bWVudCwgd2h5IGlzIGl0IHVzaW5nIFJGQyAyMTE5IGxhbmd1YWdlPw0KDQpBTkE+IEkg
dGhpbmsgd2UgbmVlZCB0byByZW1vdmUgdGhlIFJGQyAyMTE5IGxhbmd1YWdlIGlmIHRoZSB0YXJn
ZXQgaXMgaW5mb3JtYXRpb25hbC4NCg0KIiAgVGhlIHByb2JsZW0gaXMgYXBwbGljYWJsZSB0byBU
Q1AgYW5kIFRDUCBkZXJpdmVkIGZsb3ctY29udHJvbGxlZA0KICAgdHJhbnNwb3J0IHByb3RvY29s
cyBsaWtlIFNDVFAuIg0KDQpUaGlzIHN0YXRlbWVudCBpcyBub3QgbXVjaCB1c2Ugb24gaXRzIG93
bi4gRG9lcyB0aGlzIGRyYWZ0IGFwcGx5IHRvIFNDVFA/DQpJZiBpdCBkb2VzLCB3aGljaCB0ZXh0
IGluIHRoZSBTQ1RQIHNwZWMgaXMgYWZmZWN0ZWQ/DQoNCg0KQU5BPiBTQ1RQIHBlcnNpc3Qgc3Rh
dGUgaGFuZGxpbmcgaXMgdGhlIHNhbWUgYXMgcmVjb21tZW5kZWQgZm9yIFRDUC4gUkZDIDQ5NjAg
aXNuJ3QgdmVyeSBjbGVhciBhYm91dCB0aGlzIGFzcGVjdCwgYnV0IGl0IHN1cHBvcnRzIHRoZSBy
ZWNlaXZlciANCkFOQT4ga2VlcGluZyBpdHMgd2luZG93IG9wZW4gaW5kZWZpbml0ZWx5Li4gc2Vj
dGlvbiA2LjEgZnJvbSBSRkMgNDk2MCA6DQoNCiAgICAgIElmIHRoZSBzZW5kZXIgY29udGludWVz
IHRvIHJlY2VpdmUgbmV3IHBhY2tldHMgZnJvbSB0aGUgcmVjZWl2ZXINCiAgICAgIHdoaWxlIGRv
aW5nIHplcm8gd2luZG93IHByb2JpbmcsIHRoZSB1bmFja25vd2xlZGdlZCB3aW5kb3cgcHJvYmVz
DQogICAgICBzaG91bGQgbm90IGluY3JlbWVudCB0aGUgZXJyb3IgY291bnRlciBmb3IgdGhlIGFz
c29jaWF0aW9uIG9yIGFueQ0KICAgICAgZGVzdGluYXRpb24gdHJhbnNwb3J0IGFkZHJlc3MuICBU
aGlzIGlzIGJlY2F1c2UgdGhlIHJlY2VpdmVyIE1BWQ0KICAgICAga2VlcCBpdHMgd2luZG93IGNs
b3NlZCBmb3IgYW4gaW5kZWZpbml0ZSB0aW1lLiAgUmVmZXIgdG8gU2VjdGlvbg0KICAgICAgNi4y
IG9uIHRoZSByZWNlaXZlciBiZWhhdmlvciB3aGVuIGl0IGFkdmVydGlzZXMgYSB6ZXJvIHdpbmRv
dy4NCiAgICAgIFRoZSBzZW5kZXIgU0hPVUxEIHNlbmQgdGhlIGZpcnN0IHplcm8gd2luZG93IHBy
b2JlIGFmdGVyIDEgUlRPDQogICAgICB3aGVuIGl0IGRldGVjdHMgdGhhdCB0aGUgcmVjZWl2ZXIg
aGFzIGNsb3NlZCBpdHMgd2luZG93IGFuZCBTSE9VTEQNCiAgICAgIGluY3JlYXNlIHRoZSBwcm9i
ZSBpbnRlcnZhbCBleHBvbmVudGlhbGx5IGFmdGVyd2FyZHMuICBBbHNvIG5vdGUNCiAgICAgIHRo
YXQgdGhlIGN3bmQgU0hPVUxEIGJlIGFkanVzdGVkIGFjY29yZGluZyB0byBTZWN0aW9uIDcuMi4x
LiAgWmVybw0KICAgICAgd2luZG93IHByb2JpbmcgZG9lcyBub3QgYWZmZWN0IHRoZSBjYWxjdWxh
dGlvbiBvZiBjd25kLg0KQU5BPiBJIHJlbWVtYmVyIGNoZWNraW5nIHdpdGggUmFuZGFsbCBTdGV3
YXJ0IG9uIHRoZSBhcHBsaWNhYmlsaXR5IG9mIHRoaXMgZHJhZnQgdG8gU0NUUCBiZWZvcmUgd2Ug
bWFkZSB0aGlzIGNsYWltLi4gYnV0IHdlIGFyZSBvcGVuIHRvIGFueSANCkFOQT4gc3VnZ2VzdGlv
biBoZXJlLg0KDQpJbXBvcnRhbnQgZWRpdG9yaWFsIGlzc3VlczoNCi0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KDQpUaGUgZHJhZnQgc2F5czoNCg0KKGJlZ2luIHF1b3RlIGZyb20gZHJhZnQt
aWV0Zi10Y3BtLXBlcnNpc3QtMDQpDQoxLiAgSW50cm9kdWN0aW9uDQoNCiAgIFNlY3Rpb24gNC4y
LjIuMTcgb2YgUmVxdWlyZW1lbnRzIGZvciBJbnRlcm5ldCBIb3N0cyBbUkZDMTEyMl0gc2F5czoN
Cg0KICAgICAgIkEgVENQIE1BWSBrZWVwIGl0cyBvZmZlcmVkIHJlY2VpdmUgd2luZG93IGNsb3Nl
ZCBpbmRlZmluaXRlbHkuDQogICAgICBBcyBsb25nIGFzIHRoZSByZWNlaXZpbmcgVENQIGNvbnRp
bnVlcyB0byBzZW5kIGFja25vd2xlZGdtZW50cyBpbg0KICAgICAgcmVzcG9uc2UgdG8gdGhlIHBy
b2JlIHNlZ21lbnRzLCB0aGUgc2VuZGluZyBUQ1AgTVVTVCBhbGxvdyB0aGUNCiAgICAgIGNvbm5l
Y3Rpb24gdG8gc3RheSBvcGVuLiINCg0KICAgICAgRElTQ1VTU0lPTjoNCg0KICAgICAgICAgSXQg
aXMgZXh0cmVtZWx5IGltcG9ydGFudCB0byByZW1lbWJlciB0aGF0IEFDSyAoYWNrbm93bGVkZ21l
bnQpDQogICAgICAgICBzZWdtZW50cyB0aGF0IGNvbnRhaW4gbm8gZGF0YSBhcmUgbm90IHJlbGlh
Ymx5IHRyYW5zbWl0dGVkIGJ5DQogICAgICAgICBUQ1AuDQooZW5kIHF1b3RlIGZyb20gZHJhZnQt
aWV0Zi10Y3BtLXBlcnNpc3QtMDQpDQoNClRoZSBjbG9zaW5nIHF1b3RhdGlvbiBtYXJrIGlzIGlu
Y29ycmVjdGx5IHBsYWNlZCAtIGl0IGJlbG9uZ3MgYWZ0ZXIgDQonVENQLicgbm90IGFmdGVyICdv
cGVuLicuIFRoZSByZWFkZXIgd2lsbCBiZSBtaXNsZWQgYnkgdGhpcy4gWW91IG1pZ2h0DQpjb25z
aWRlciBldmVuIGNsZWFyZXIgZmxhZ3MgZm9yIHRoZSBleHRyYWN0LCBhcyBJIGhhdmUgdXNlZCBh
Ym92ZS4NCg0KQU5BPiBTdXJlIHdlIGNhbiBmaXggdGhpcy4gR29vZCBjYXRjaC4NCg0KKGJlZ2lu
IHF1b3RlIGZyb20gZHJhZnQtaWV0Zi10Y3BtLXBlcnNpc3QtMDQpDQo1LiAgQ2xhcmlmaWNhdGlv
biBSZWdhcmRpbmcgUkZDIDExMjIgUmVxdWlyZW1lbnRzDQoNCiAgIEFzIHN0YXRlZCBpbiBSZXF1
aXJlbWVudHMgZm9yIEludGVybmV0IEhvc3RzIFtSRkMxMTIyXSwgYSBUQ1ANCiAgIGltcGxlbWVu
dGF0aW9uIE1VU1QgTk9UIGNsb3NlIGEgY29ubmVjdGlvbiBtZXJlbHkgYmVjYXVzZSBpdCBzZWVt
cyB0bw0KICAgYmUgc3R1Y2sgaW4gdGhlIFpXUCBvciBwZXJzaXN0IGNvbmRpdGlvbi4gIFVuc3Rh
dGVkIGluIFJGQyAxMTIyLCBidXQNCiAgIGltcGxpY2l0IGZvciBzeXN0ZW0gcm9idXN0bmVzcywg
YSBUQ1AgaW1wbGVtZW50YXRpb24gTVVTVCBhbGxvdw0KICAgY29ubmVjdGlvbnMgaW4gdGhlIFpX
UCBvciBwZXJzaXN0IGNvbmRpdGlvbiB0byBiZSBjbG9zZWQgb3IgYWJvcnRlZA0KICAgYnkgdGhl
aXIgYXBwbGljYXRpb25zIG9yIG90aGVyIHJlc291cmNlIG1hbmFnZW1lbnQgcm91dGluZXMgaW4g
dGhlDQogICBvcGVyYXRpbmcgc3lzdGVtLg0KKGVuZCBxdW90ZSBmcm9tIGRyYWZ0LWlldGYtdGNw
bS1wZXJzaXN0LTA0KQ0KDQpCb3RoIHRoZXNlIHNlbnRlbmNlcyBzZWVtIHRvIGFzc2VydCB0aGlu
Z3MgYWJvdXQgUkZDIDExMjIsIGFuZCBhYm91dCB0aGUgc3RhdGUNCm9mIG1pbmQgb2YgaXRzIGVk
aXRvciwgdGhhdCBJIGhhdmUgbm8gcmVhc29uIHRvIGJlbGlldmUuIFJGQyAxMTIyIGRvZXNuJ3QN
CnNheSBhbnl0aGluZyBhYm91dCB0aGUgTVVTVCBOT1QgYmVpbmcgIm1lcmVseSBiZWNhdXNlIiBh
bnl0aGluZyAtIHRoZSBzdGF0ZW1lbnQNCmluIHNlY3Rpb24gNC4yLjIuMTcgaXMgY29tcGxldGVs
eSB1bmFtYmlndW91cy4gQW5kIEkgZG9uJ3Qgc2VlIGFueSBncm91bmRzIGZvcg0KYXNzZXJ0aW5n
IHRoYXQgdGhlIHNlY29uZCBzZW50ZW5jZSBpcyBhbnkgd2F5IGltcGxpY2l0IGluIFJGQyAxMTIy
LiBRdWl0ZSB0aGUNCm9wcG9zaXRlIC0geW91IGFyZSBkb2N1bWVudGluZyBhbiBvdmVyc2lnaHQu
IEkgdGhpbmsgeW91IHNob3VsZCBzYXkgc28uIEZvcg0KZXhhbXBsZToNCg0KNS4gIFVwZGF0ZSB0
byBSRkMgMTEyMiBSZXF1aXJlbWVudHMNCg0KICAgUmVxdWlyZW1lbnRzIGZvciBJbnRlcm5ldCBI
b3N0cyBbUkZDMTEyMl0gc3RhdGVzIHRoYXQgYSBUQ1ANCiAgIGltcGxlbWVudGF0aW9uIE1VU1Qg
Tk9UIGNsb3NlIGEgY29ubmVjdGlvbiBpZiBpdCBzZWVtcyB0bw0KICAgYmUgc3R1Y2sgaW4gdGhl
IFpXUCBvciBwZXJzaXN0IGNvbmRpdGlvbiwgYXMgbG9uZyBhcyBhY2tvd2xlZGdlbWVudHMNCiAg
IGFyZSBiZWluZyByZWNlaXZlZC4gVGhlIHByZXNlbnQgZG9jdW1lbnQgdXBkYXRlcyB0aGlzIHJl
cXVpcmVtZW50IGJ5DQogICBhZGRpbmcgdGhhdCBhIFRDUCBpbXBsZW1lbnRhdGlvbiBNVVNUIGFs
bG93IGNvbm5lY3Rpb25zIGluIHRoZSBaV1ANCiAgIG9yIHBlcnNpc3QgY29uZGl0aW9uIHRvIGJl
IGNsb3NlZCBvciBhYm9ydGVkIGJ5IHRoZWlyIGFwcGxpY2F0aW9ucyBvcg0KICAgb3RoZXIgcmVz
b3VyY2UgbWFuYWdlbWVudCByb3V0aW5lcyBpbiB0aGUgb3BlcmF0aW5nIHN5c3RlbS4NCg0KQU5B
PiBFeGNlbGxlbnQgY2F0Y2ghLiAgSSBhbSBjb21mb3J0YWJsZSB1c2luZyB0aGUgYWJvdmUgdGV4
dCB3aGljaCB5b3Ugc3VnZ2VzdGVkLiANCg0KTWlub3IgZWRpdG9yaWFsDQotLS0tLS0tLS0tLS0t
LS0NCg0KVGhlc2UgYXJlIGV4YW1wbGVzIC0gSSB0aGluayB0aGUgRW5nbGlzaCBuZWVkcyBhIGdl
bmVyYWwgdGlkeS11cDoNCg0KIiAgUGVyIFJlcXVpcmVtZW50cyBmb3IgSW50ZXJuZXQgSG9zdHMg
W1JGQzExMjJdIGFzIGxvbmcgYXMgdGhlIEFDSydzDQogICBhcmUgYmVpbmcgcmVjZWl2ZWQgZm9y
IHdpbmRvdyBwcm9iZXMsIGEgY29ubmVjdGlvbiBjYW4gY29udGludWUgdG8NCiAgIHN0YXkgaW4g
dGhlIHBlcnNpc3QgY29uZGl0aW9uLiINCg0KVGhlIHVzZSBvZiAiUGVyIiBsaWtlIHRoaXMgaXMs
IHdlbGwsIHNsb3BweS4gIkFjY29yZGluZyB0by4uLiIgd291bGQgYmUgYmV0dGVyLg0KVGhlcmUg
aXMgYSBtaXNzaW5nIGNvbW1hIGFmdGVyICJbUkZDMTEyMl0iLg0KIkFDSydzIiBzaG91bGQgYmUg
IkFDS3MiLg0KDQpBTkE+IFBvaW50IHRha2VuLCB3aWxsIGNvcnJlY3QgaXQuDQoNCiIgIFN5c3Rl
bXMgdGhhdCBhZGhlcmUgdG9vIHN0cmljdGx5IHRvIHRoZSBhYm92ZSB2ZXJiaWFnZSBvZg0KICAg
UmVxdWlyZW1lbnRzIGZvciBJbnRlcm5ldCBIb3N0cyBbUkZDMTEyMl0uLi4iDQoNCkl0IGlzbid0
ICJ2ZXJiaWFnZSIsIHdoaWNoIG1lYW5zICJUaGUgdXNlIG9mIG1hbnkgd29yZHMgd2l0aG91dCBu
ZWNlc3NpdHksIG9yIHdpdGggDQpsaXR0bGUgc2Vuc2U7IGEgc3VwZXJhYnVuZGFuY2Ugb2Ygd29y
ZHM7IHZlcmJvc2l0eTsgd29yZGluZXNzIiBhY2NvcmRpbmcgdG8gbXkgDQpmYXZvdXJpdGUgb24t
bGluZSBkaWN0aW9uYXJ5LiBJdCBpcyBqdXN0ICJ3b3JkaW5nIi4NCg0KQU5BPiBJIHRoaW5rIGV2
ZW4gb3RoZXIgSUVTRyByZXZpZXdlciBhbHNvIHBvaW50ZWQgdGhpcyBvdXQgKFN0ZXdhcnQgPykg
Q29ycmVjdGVkIGFscmVhZHkgSSBndWVzcywgaWYgbm90IHdpbGwgY29ycmVjdCBpdC4NCg0KQU5B
PiBUaGFua3MgZm9yIHlvdXIgdmFsdWFibGUgY29tbWVudHMsIEJyYWluLiBXaWxsIGluY29ycG9y
YXRlIHRoZW0uDQoNCkFOQT4gQXMgZmFyIGFzIHRoZSBjb21tZW50IG9uIHN0YW5kYXJkcyB0cmFj
ayB2ZXJzdXMgaW5mb3JtYXRpb25hbCwgbXkgcHJlZmVyZW5jZSB3YXMgdG8gZ28gd2l0aCBzdGFu
ZGFyZHMgc2luY2UgaXQgY2FuIGJlIGNvbnN0cnVlZCBhcyBhIHVwZGF0ZSANCkFOQT4gdG8gUkZD
IDExMjIuIEknbGwgbGVhdmUgaXQgdG8gdGhlIGNoYWlycyB0byBjb21tZW50IGZ1cnRoZXIgb24g
dGhpcy4gIEkgYW0gYWxzbyBjb3B5aW5nIERhdmlkIEhhcnJpbmd0b24gaW4gdGhlIGxvb3Agc2lu
Y2UgaGlzIHF1ZXN0aW9uIA0KQU5BPiBhbHNvIGNlbnRlcmVkIGFyb3VuZCB0aGUgUkZDIDIxMTkg
bGFuZ3VhZ2UuLi4NCg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT0gRW5kIExhc3QgY2FsbCBjb21tZW50cyA9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0N
Cg0KVGhhbmtzLA0KLUFuYW50aGENCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJv
bTogQnJpYW4gRSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21d
DQo+IFNlbnQ6IFNhdHVyZGF5LCBKdW5lIDA0LCAyMDExIDE6MTYgUE0NCj4gVG86IGRyYWZ0LWll
dGYtdGNwbS1wZXJzaXN0LmFsbEB0b29scy5pZXRmLm9yZzsgR2VuZXJhbCBBcmVhIFJldmlldw0K
PiBUZWFtDQo+IFN1YmplY3Q6IEdlbi1BUlQgdGVsZWNoYXQgcmV2aWV3IG9mIGRyYWZ0LWlldGYt
dGNwbS1wZXJzaXN0LTA0LnR4dA0KPiANCj4gUGxlYXNlIHNlZSBhdHRhY2hlZCByZXZpZXcuDQo+
IA0KPiANCj4gDQoNCg==

From brian.e.carpenter@gmail.com  Sat Jun  4 21:10:03 2011
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 80D5621F84D1 for <gen-art@ietfa.amsl.com>; Sat,  4 Jun 2011 21:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=1.300,  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 c3Vhqbh+wjjN for <gen-art@ietfa.amsl.com>; Sat,  4 Jun 2011 21:10:02 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1EAB421F84D0 for <gen-art@ietf.org>; Sat,  4 Jun 2011 21:09:58 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2174838fxm.31 for <gen-art@ietf.org>; Sat, 04 Jun 2011 21:09:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=psK6CG5BhLJvAvzIt+rkS3PyB2i8oJ7cyGYfFQhb7Ig=; b=iRBWo30FIbT1Ww2MDr6S+wodlZk0Zx24P1Ms2Vyb1fqD2OzA06S6glyBycrM362Ymi 5QvuASWzO/C6ve3vIw2tcgIWDo4cJ0Z47Un3d3L+LOu3oHGbpl9dGxkY5CmQQP0t3erR mECUAFPqgQOTpPT3N0KQHzqZSJn7EytdZyIHo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=YIhvKupVctBTyrjJQ4vY3xZ706O2+s3+/p/ce/8MJclzVSivUuALZrFCF1ljSYg7c6 viFoNTauZkCOyFyRM/yZlpcD9+ne4/sHnBQGYXWjh9aHTGlQVv09KkLRvQQ/8g0sIkKF zpwlwt7T4t1W2PUXP9TRNMgoX3j6GluPa+H9Y=
Received: by 10.223.76.219 with SMTP id d27mr1341535fak.87.1307246998081; Sat, 04 Jun 2011 21:09:58 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id c1sm928460faa.37.2011.06.04.21.09.53 (version=SSLv3 cipher=OTHER); Sat, 04 Jun 2011 21:09:57 -0700 (PDT)
Message-ID: <4DEB018A.9060708@gmail.com>
Date: Sun, 05 Jun 2011 16:09:46 +1200
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: Wesley Eddy <wes@mti-systems.com>
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com> <4DEAF316.4060701@mti-systems.com>
In-Reply-To: <4DEAF316.4060701@mti-systems.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: David Harrington <ietfdbh@comcast.net>, draft-ietf-tcpm-persist.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Sun, 05 Jun 2011 04:10:03 -0000

Hi Wes,

> In TCPM, it was determined that RFC 1122 is not wrong or flawed, just
> potentially unclear. 

That's a judgment call that the WG's entitled to make, of course.

(Side comment: it would be useful for reviewers outside the WG
if writeups noted why a document was in a particular category
when there might be some question about it.)

> There are many non-standards-track RFCs that include 2119 language,

True, where the document is self-contained (e.g. an Experimental
specification). But it goes with my previous point - either it's
normative, in which case it should be standards track, or it isn't,
in which case using RFC 2119 seems inconsistent.

This is definitely IMHO but I see from Dave Harrington's DISCUSS that
he has the same questions.

Regards
   Brian Carpenter




On 2011-06-05 15:08, Wesley Eddy wrote:
> Just commenting on the non-editorial portion:
> 
> On 6/4/2011 5:51 PM, Anantha Ramaiah (ananth) wrote:
>>
>> ...
>>
>> Why is this Informational? If it matters, it should be a Standards Track
>> document updating RFC 1122.
>>
>> ANA>  I agree, it should have been a standards track document since it
>> clarifies the RFC 1122 wording. I believe the TCPM chairs and WG group
>> had
>> ANA>  approved us to come up with a informational RFC that clarifies
>> the intention of RFC 1122 regarding persist state. We have no problems
>> making ANA>  this a standards track, I'll leave it to the chairs to
>> comment on this.
> 
> In TCPM, it was determined that RFC 1122 is not wrong or flawed, just
> potentially unclear.
> 
> The current draft is a clarification rather than actually augmenting,
> correcting, extending, or updating any of the specs and guidance in
> 1122.
> 
> As I recall, Informational was purposefully chosen by TCPM; this is
> more implementation guidance than anything warranting standards track.
> As for adding Updates 1122, this may be a good idea; I don't recall if
> it was specifically discussed by the WG.  I noticed at least one other
> RFC which includes clarifications is Informational and doesn't Update
> its parent documents (RFC 4718 is the example)
> 
> 
>> If it's not a Standards Track document, why is it using RFC 2119
>> language?
>>
>> ANA>  I think we need to remove the RFC 2119 language if the target is
>> informational.
> 
> There are many non-standards-track RFCs that include 2119 language, so
> it's unclear what the hangup is here.  That said, I think either way,
> the meaning of this document will be clear, so don't have strong
> personal feelings one way or the other.
> 
> 

From wes@mti-systems.com  Sat Jun  4 20:08:11 2011
Return-Path: <wes@mti-systems.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 5E90D11E808B for <gen-art@ietfa.amsl.com>; Sat,  4 Jun 2011 20:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AnLQrMFtNNuz for <gen-art@ietfa.amsl.com>; Sat,  4 Jun 2011 20:08:10 -0700 (PDT)
Received: from omr5.networksolutionsemail.com (omr5.networksolutionsemail.com [205.178.146.55]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB6711E8077 for <gen-art@ietf.org>; Sat,  4 Jun 2011 20:08:07 -0700 (PDT)
Received: from cm-omr6 (mail.networksolutionsemail.com [205.178.146.50]) by omr5.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id p553869b007173 for <gen-art@ietf.org>; Sat, 4 Jun 2011 23:08:06 -0400
Authentication-Results: cm-omr6 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [174.130.37.23] ([174.130.37.23:7647] helo=[192.168.1.104]) by cm-omr6 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 1D/83-17003-513FAED4; Sat, 04 Jun 2011 23:08:06 -0400
Message-ID: <4DEAF316.4060701@mti-systems.com>
Date: Sat, 04 Jun 2011 23:08:06 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 04 Jun 2011 21:11:29 -0700
Cc: David Harrington <ietfdbh@comcast.net>, General Area Review Team <gen-art@ietf.org>, draft-ietf-tcpm-persist.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Sun, 05 Jun 2011 03:08:11 -0000

Just commenting on the non-editorial portion:

On 6/4/2011 5:51 PM, Anantha Ramaiah (ananth) wrote:
>
> ...
>
> Why is this Informational? If it matters, it should be a Standards Track
> document updating RFC 1122.
>
> ANA>  I agree, it should have been a standards track document since it clarifies the RFC 1122 wording. I believe the TCPM chairs and WG group had
> ANA>  approved us to come up with a informational RFC that clarifies the intention of RFC 1122 regarding persist state. We have no problems making ANA>  this a standards track, I'll leave it to the chairs to comment on this.

In TCPM, it was determined that RFC 1122 is not wrong or flawed, just
potentially unclear.

The current draft is a clarification rather than actually augmenting,
correcting, extending, or updating any of the specs and guidance in
1122.

As I recall, Informational was purposefully chosen by TCPM; this is
more implementation guidance than anything warranting standards track.
As for adding Updates 1122, this may be a good idea; I don't recall if
it was specifically discussed by the WG.  I noticed at least one other
RFC which includes clarifications is Informational and doesn't Update
its parent documents (RFC 4718 is the example)


> If it's not a Standards Track document, why is it using RFC 2119 language?
>
> ANA>  I think we need to remove the RFC 2119 language if the target is informational.

There are many non-standards-track RFCs that include 2119 language, so
it's unclear what the hangup is here.  That said, I think either way,
the meaning of this document will be clear, so don't have strong
personal feelings one way or the other.


-- 
Wes Eddy
MTI Systems

From ananth@cisco.com  Sun Jun  5 00:21:46 2011
Return-Path: <ananth@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 8D44B9E8005 for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 00:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.3
X-Spam-Level: 
X-Spam-Status: No, score=-9.3 tagged_above=-999 required=5 tests=[AWL=1.300, 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 R+kSCvUwMPlq for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 00:21:41 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 885A79E8004 for <gen-art@ietf.org>; Sun,  5 Jun 2011 00:21:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ananth@cisco.com; l=4906; q=dns/txt; s=iport; t=1307258501; x=1308468101; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=FNgC9D+LRYzMLxjgM03Z/EhJ/nEDjwZ6SR7aC5bzATs=; b=P36ef8Y2iJ8TriVyQ4fSa8rL97yZxoG2EYnEXWHspYZmru3WPe93T6Kg ZFxICSm1XQmsUtMgdTxw+9B8J+SqXe45MqyXY4ua8I9Wq1Icmymh/hKmF G9XLjmq0XMh8s8s7AuED42l46MxwNCKtrWFI+x6ginI1osmKDrEGQnPeM o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhMBAEku602rRDoH/2dsb2JhbABThEqTEY1rdXeoaY0Jj12BK4NsgQoEhnSOVoQohmE
X-IronPort-AV: E=Sophos;i="4.65,322,1304294400"; d="scan'208";a="330361746"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-3.cisco.com with ESMTP; 05 Jun 2011 07:21:22 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p557LL6i008731; Sun, 5 Jun 2011 07:21:21 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 5 Jun 2011 00:21:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Sun, 5 Jun 2011 00:21:20 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <4DEB018A.9060708@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
Thread-Index: AcwjNnEUoPKIVgGjRjumizBTr6URowAGZb3g
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com> <4DEAF316.4060701@mti-systems.com> <4DEB018A.9060708@gmail.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Wesley Eddy" <wes@mti-systems.com>
X-OriginalArrivalTime: 05 Jun 2011 07:21:21.0822 (UTC) FILETIME=[2BA15BE0:01CC2351]
Cc: David Harrington <ietfdbh@comcast.net>, General Area Review Team <gen-art@ietf.org>, draft-ietf-tcpm-persist.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Sun, 05 Jun 2011 07:21:46 -0000

U28sIEkgYW0gYSBiaXQgY29uZnVzZWQsIGp1c3QgdG8gc3VtbWFyaXplIG15IHVuZGVyc3RhbmRp
bmcgc28gZmFyIDotDQoNCi0gaWYgdGhlIGRvY3VtZW50IHN0YXR1cyBpcyBzdGFuZGFyZHMgdHJh
Y2ssIHRoZW4gdGhlcmUgaXMgbm8gaXNzdWUuDQotIGlmIHRoZSBkb2N1bWVudCBzdGF0dXMgaXMg
aW5mb3JtYXRpb25hbCwgdGhlbiByZW1vdmUgdGhlIFJGQyAyMTE5IHVzYWdlLiBUaGVuIEkgYW0g
YWZyYWlkIHRoZSBtZXNzYWdlIG9mIHRoZSBkcmFmdCBiZWNvbWVzIGF0IHRoZSBiZXN0IGR1Ymlv
dXMuDQotIHJldGFpbiBpdCBhcyBpbmZvcm1hdGlvbmFsLCBidXQgdXNlICJ1cGRhdGVzIDExMjIi
LiBDYW4gdGhpcyBiZSBkb25lPyBJIGFtIG5vdCBzdXJlLi4NCg0KSG93IGRvIHdlIG1vdmUgZm9y
d2FyZCBvbiB0aGlzIG9uZT8NCg0KLUFuYW50aGENCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KPiBGcm9tOiBCcmlhbiBFIENhcnBlbnRlciBbbWFpbHRvOmJyaWFuLmUuY2FycGVudGVy
QGdtYWlsLmNvbV0NCj4gU2VudDogU2F0dXJkYXksIEp1bmUgMDQsIDIwMTEgOToxMCBQTQ0KPiBU
bzogV2VzbGV5IEVkZHkNCj4gQ2M6IEFuYW50aGEgUmFtYWlhaCAoYW5hbnRoKTsgZHJhZnQtaWV0
Zi10Y3BtLQ0KPiBwZXJzaXN0LmFsbEB0b29scy5pZXRmLm9yZzsgR2VuZXJhbCBBcmVhIFJldmll
dyBUZWFtOyBEYXZpZCBIYXJyaW5ndG9uDQo+IFN1YmplY3Q6IFJlOiBHZW4tQVJUIHRlbGVjaGF0
IHJldmlldyBvZiBkcmFmdC1pZXRmLXRjcG0tcGVyc2lzdC0wNC50eHQNCj4gDQo+IEhpIFdlcywN
Cj4gDQo+ID4gSW4gVENQTSwgaXQgd2FzIGRldGVybWluZWQgdGhhdCBSRkMgMTEyMiBpcyBub3Qg
d3Jvbmcgb3IgZmxhd2VkLCBqdXN0DQo+ID4gcG90ZW50aWFsbHkgdW5jbGVhci4NCj4gDQo+IFRo
YXQncyBhIGp1ZGdtZW50IGNhbGwgdGhhdCB0aGUgV0cncyBlbnRpdGxlZCB0byBtYWtlLCBvZiBj
b3Vyc2UuDQo+IA0KPiAoU2lkZSBjb21tZW50OiBpdCB3b3VsZCBiZSB1c2VmdWwgZm9yIHJldmll
d2VycyBvdXRzaWRlIHRoZSBXRw0KPiBpZiB3cml0ZXVwcyBub3RlZCB3aHkgYSBkb2N1bWVudCB3
YXMgaW4gYSBwYXJ0aWN1bGFyIGNhdGVnb3J5DQo+IHdoZW4gdGhlcmUgbWlnaHQgYmUgc29tZSBx
dWVzdGlvbiBhYm91dCBpdC4pDQo+IA0KPiA+IFRoZXJlIGFyZSBtYW55IG5vbi1zdGFuZGFyZHMt
dHJhY2sgUkZDcyB0aGF0IGluY2x1ZGUgMjExOSBsYW5ndWFnZSwNCj4gDQo+IFRydWUsIHdoZXJl
IHRoZSBkb2N1bWVudCBpcyBzZWxmLWNvbnRhaW5lZCAoZS5nLiBhbiBFeHBlcmltZW50YWwNCj4g
c3BlY2lmaWNhdGlvbikuIEJ1dCBpdCBnb2VzIHdpdGggbXkgcHJldmlvdXMgcG9pbnQgLSBlaXRo
ZXIgaXQncw0KPiBub3JtYXRpdmUsIGluIHdoaWNoIGNhc2UgaXQgc2hvdWxkIGJlIHN0YW5kYXJk
cyB0cmFjaywgb3IgaXQgaXNuJ3QsDQo+IGluIHdoaWNoIGNhc2UgdXNpbmcgUkZDIDIxMTkgc2Vl
bXMgaW5jb25zaXN0ZW50Lg0KPiANCj4gVGhpcyBpcyBkZWZpbml0ZWx5IElNSE8gYnV0IEkgc2Vl
IGZyb20gRGF2ZSBIYXJyaW5ndG9uJ3MgRElTQ1VTUyB0aGF0DQo+IGhlIGhhcyB0aGUgc2FtZSBx
dWVzdGlvbnMuDQo+IA0KPiBSZWdhcmRzDQo+ICAgIEJyaWFuIENhcnBlbnRlcg0KPiANCj4gDQo+
IA0KPiANCj4gT24gMjAxMS0wNi0wNSAxNTowOCwgV2VzbGV5IEVkZHkgd3JvdGU6DQo+ID4gSnVz
dCBjb21tZW50aW5nIG9uIHRoZSBub24tZWRpdG9yaWFsIHBvcnRpb246DQo+ID4NCj4gPiBPbiA2
LzQvMjAxMSA1OjUxIFBNLCBBbmFudGhhIFJhbWFpYWggKGFuYW50aCkgd3JvdGU6DQo+ID4+DQo+
ID4+IC4uLg0KPiA+Pg0KPiA+PiBXaHkgaXMgdGhpcyBJbmZvcm1hdGlvbmFsPyBJZiBpdCBtYXR0
ZXJzLCBpdCBzaG91bGQgYmUgYSBTdGFuZGFyZHMNCj4gVHJhY2sNCj4gPj4gZG9jdW1lbnQgdXBk
YXRpbmcgUkZDIDExMjIuDQo+ID4+DQo+ID4+IEFOQT4gIEkgYWdyZWUsIGl0IHNob3VsZCBoYXZl
IGJlZW4gYSBzdGFuZGFyZHMgdHJhY2sgZG9jdW1lbnQgc2luY2UNCj4gaXQNCj4gPj4gY2xhcmlm
aWVzIHRoZSBSRkMgMTEyMiB3b3JkaW5nLiBJIGJlbGlldmUgdGhlIFRDUE0gY2hhaXJzIGFuZCBX
Rw0KPiBncm91cA0KPiA+PiBoYWQNCj4gPj4gQU5BPiAgYXBwcm92ZWQgdXMgdG8gY29tZSB1cCB3
aXRoIGEgaW5mb3JtYXRpb25hbCBSRkMgdGhhdCBjbGFyaWZpZXMNCj4gPj4gdGhlIGludGVudGlv
biBvZiBSRkMgMTEyMiByZWdhcmRpbmcgcGVyc2lzdCBzdGF0ZS4gV2UgaGF2ZSBubw0KPiBwcm9i
bGVtcw0KPiA+PiBtYWtpbmcgQU5BPiAgdGhpcyBhIHN0YW5kYXJkcyB0cmFjaywgSSdsbCBsZWF2
ZSBpdCB0byB0aGUgY2hhaXJzIHRvDQo+ID4+IGNvbW1lbnQgb24gdGhpcy4NCj4gPg0KPiA+IElu
IFRDUE0sIGl0IHdhcyBkZXRlcm1pbmVkIHRoYXQgUkZDIDExMjIgaXMgbm90IHdyb25nIG9yIGZs
YXdlZCwganVzdA0KPiA+IHBvdGVudGlhbGx5IHVuY2xlYXIuDQo+ID4NCj4gPiBUaGUgY3VycmVu
dCBkcmFmdCBpcyBhIGNsYXJpZmljYXRpb24gcmF0aGVyIHRoYW4gYWN0dWFsbHkgYXVnbWVudGlu
ZywNCj4gPiBjb3JyZWN0aW5nLCBleHRlbmRpbmcsIG9yIHVwZGF0aW5nIGFueSBvZiB0aGUgc3Bl
Y3MgYW5kIGd1aWRhbmNlIGluDQo+ID4gMTEyMi4NCj4gPg0KPiA+IEFzIEkgcmVjYWxsLCBJbmZv
cm1hdGlvbmFsIHdhcyBwdXJwb3NlZnVsbHkgY2hvc2VuIGJ5IFRDUE07IHRoaXMgaXMNCj4gPiBt
b3JlIGltcGxlbWVudGF0aW9uIGd1aWRhbmNlIHRoYW4gYW55dGhpbmcgd2FycmFudGluZyBzdGFu
ZGFyZHMNCj4gdHJhY2suDQo+ID4gQXMgZm9yIGFkZGluZyBVcGRhdGVzIDExMjIsIHRoaXMgbWF5
IGJlIGEgZ29vZCBpZGVhOyBJIGRvbid0IHJlY2FsbA0KPiBpZg0KPiA+IGl0IHdhcyBzcGVjaWZp
Y2FsbHkgZGlzY3Vzc2VkIGJ5IHRoZSBXRy4gIEkgbm90aWNlZCBhdCBsZWFzdCBvbmUNCj4gb3Ro
ZXINCj4gPiBSRkMgd2hpY2ggaW5jbHVkZXMgY2xhcmlmaWNhdGlvbnMgaXMgSW5mb3JtYXRpb25h
bCBhbmQgZG9lc24ndCBVcGRhdGUNCj4gPiBpdHMgcGFyZW50IGRvY3VtZW50cyAoUkZDIDQ3MTgg
aXMgdGhlIGV4YW1wbGUpDQo+ID4NCj4gPg0KPiA+PiBJZiBpdCdzIG5vdCBhIFN0YW5kYXJkcyBU
cmFjayBkb2N1bWVudCwgd2h5IGlzIGl0IHVzaW5nIFJGQyAyMTE5DQo+ID4+IGxhbmd1YWdlPw0K
PiA+Pg0KPiA+PiBBTkE+ICBJIHRoaW5rIHdlIG5lZWQgdG8gcmVtb3ZlIHRoZSBSRkMgMjExOSBs
YW5ndWFnZSBpZiB0aGUgdGFyZ2V0DQo+IGlzDQo+ID4+IGluZm9ybWF0aW9uYWwuDQo+ID4NCj4g
PiBUaGVyZSBhcmUgbWFueSBub24tc3RhbmRhcmRzLXRyYWNrIFJGQ3MgdGhhdCBpbmNsdWRlIDIx
MTkgbGFuZ3VhZ2UsDQo+IHNvDQo+ID4gaXQncyB1bmNsZWFyIHdoYXQgdGhlIGhhbmd1cCBpcyBo
ZXJlLiAgVGhhdCBzYWlkLCBJIHRoaW5rIGVpdGhlciB3YXksDQo+ID4gdGhlIG1lYW5pbmcgb2Yg
dGhpcyBkb2N1bWVudCB3aWxsIGJlIGNsZWFyLCBzbyBkb24ndCBoYXZlIHN0cm9uZw0KPiA+IHBl
cnNvbmFsIGZlZWxpbmdzIG9uZSB3YXkgb3IgdGhlIG90aGVyLg0KPiA+DQo+ID4NCg==

From brian.e.carpenter@gmail.com  Sun Jun  5 13:16:17 2011
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 1EE1D21F84F5 for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 13:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.949
X-Spam-Level: 
X-Spam-Status: No, score=-102.949 tagged_above=-999 required=5 tests=[AWL=0.650, 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 wgF5Npvn77xe for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 13:16:16 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1612D21F84FB for <gen-art@ietf.org>; Sun,  5 Jun 2011 13:16:15 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2402400fxm.31 for <gen-art@ietf.org>; Sun, 05 Jun 2011 13:16:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=gD4plPltgn7MKdwJPcO4WjgEiL/UPUgq1LpV99q1Y8A=; b=YRxAS2he/CQOOqElEaa57GpLyvM0bnfPSxJ7LpXFXcpcJ2ZQXPxZLyFPiYqYdW9vVs 0qNUIuPcLCZrc9RZrvRDRWgQEPau/NrNeasQYXuvhMGHPKshr2GcPA36/UM05h0tsczv lcU/7lgqN7wFQC7pIeFlBuznKzDspCCOKljwM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=A/KciR7tpn/Vhdp+OsDPDRV2HoxHZvAPL8dAGQ5CiyNkajLFfM77HT2hu/7GoASESA iYKnhrR9tSUK9tU+tMUm6KTkKDz+f0llzYR3Y5i/4wdJc6/IoJPXurBwJsGdAvMQSnT4 IYqtaa3VaN4p2p5w5sSbojW/NUFYiT69Qj8fI=
Received: by 10.223.6.198 with SMTP id a6mr35447faa.128.1307304975215; Sun, 05 Jun 2011 13:16:15 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id c1sm1113911faa.37.2011.06.05.13.16.10 (version=SSLv3 cipher=OTHER); Sun, 05 Jun 2011 13:16:14 -0700 (PDT)
Message-ID: <4DEBE403.1020305@gmail.com>
Date: Mon, 06 Jun 2011 08:16:03 +1200
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: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com> <4DEAF316.4060701@mti-systems.com> <4DEB018A.9060708@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Wesley Eddy <wes@mti-systems.com>, David Harrington <ietfdbh@comcast.net>, General Area Review Team <gen-art@ietf.org>, draft-ietf-tcpm-persist.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Sun, 05 Jun 2011 20:16:17 -0000

Hi,

As my review said - please wait for instructions from the document
shepherd. The IESG discussion is what counts. My opinion is only
my opinion.

Regards
   Brian

On 2011-06-05 19:21, Anantha Ramaiah (ananth) wrote:
> So, I am a bit confused, just to summarize my understanding so far :-
> 
> - if the document status is standards track, then there is no issue.
> - if the document status is informational, then remove the RFC 2119 usage. Then I am afraid the message of the draft becomes at the best dubious.
> - retain it as informational, but use "updates 1122". Can this be done? I am not sure..
> 
> How do we move forward on this one?
> 
> -Anantha
> 
>> -----Original Message-----
>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: Saturday, June 04, 2011 9:10 PM
>> To: Wesley Eddy
>> Cc: Anantha Ramaiah (ananth); draft-ietf-tcpm-
>> persist.all@tools.ietf.org; General Area Review Team; David Harrington
>> Subject: Re: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
>>
>> Hi Wes,
>>
>>> In TCPM, it was determined that RFC 1122 is not wrong or flawed, just
>>> potentially unclear.
>> That's a judgment call that the WG's entitled to make, of course.
>>
>> (Side comment: it would be useful for reviewers outside the WG
>> if writeups noted why a document was in a particular category
>> when there might be some question about it.)
>>
>>> There are many non-standards-track RFCs that include 2119 language,
>> True, where the document is self-contained (e.g. an Experimental
>> specification). But it goes with my previous point - either it's
>> normative, in which case it should be standards track, or it isn't,
>> in which case using RFC 2119 seems inconsistent.
>>
>> This is definitely IMHO but I see from Dave Harrington's DISCUSS that
>> he has the same questions.
>>
>> Regards
>>    Brian Carpenter
>>
>>
>>
>>
>> On 2011-06-05 15:08, Wesley Eddy wrote:
>>> Just commenting on the non-editorial portion:
>>>
>>> On 6/4/2011 5:51 PM, Anantha Ramaiah (ananth) wrote:
>>>> ...
>>>>
>>>> Why is this Informational? If it matters, it should be a Standards
>> Track
>>>> document updating RFC 1122.
>>>>
>>>> ANA>  I agree, it should have been a standards track document since
>> it
>>>> clarifies the RFC 1122 wording. I believe the TCPM chairs and WG
>> group
>>>> had
>>>> ANA>  approved us to come up with a informational RFC that clarifies
>>>> the intention of RFC 1122 regarding persist state. We have no
>> problems
>>>> making ANA>  this a standards track, I'll leave it to the chairs to
>>>> comment on this.
>>> In TCPM, it was determined that RFC 1122 is not wrong or flawed, just
>>> potentially unclear.
>>>
>>> The current draft is a clarification rather than actually augmenting,
>>> correcting, extending, or updating any of the specs and guidance in
>>> 1122.
>>>
>>> As I recall, Informational was purposefully chosen by TCPM; this is
>>> more implementation guidance than anything warranting standards
>> track.
>>> As for adding Updates 1122, this may be a good idea; I don't recall
>> if
>>> it was specifically discussed by the WG.  I noticed at least one
>> other
>>> RFC which includes clarifications is Informational and doesn't Update
>>> its parent documents (RFC 4718 is the example)
>>>
>>>
>>>> If it's not a Standards Track document, why is it using RFC 2119
>>>> language?
>>>>
>>>> ANA>  I think we need to remove the RFC 2119 language if the target
>> is
>>>> informational.
>>> There are many non-standards-track RFCs that include 2119 language,
>> so
>>> it's unclear what the hangup is here.  That said, I think either way,
>>> the meaning of this document will be clear, so don't have strong
>>> personal feelings one way or the other.
>>>
>>>

From alexey.melnikov@isode.com  Sun Jun  5 13:42:09 2011
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 6249021F84E4; Sun,  5 Jun 2011 13:42:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.856
X-Spam-Level: 
X-Spam-Status: No, score=-101.856 tagged_above=-999 required=5 tests=[AWL=0.743, 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 LbSi3sB7yhWR; Sun,  5 Jun 2011 13:42:07 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id B826121F84D4; Sun,  5 Jun 2011 13:42:06 -0700 (PDT)
Received: from [188.28.52.10] (188.28.52.10.threembb.co.uk [188.28.52.10])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TevqGgA-uQif@rufus.isode.com>; Sun, 5 Jun 2011 21:42:03 +0100
Message-ID: <4DEBE9FF.1030801@isode.com>
Date: Sun, 05 Jun 2011 21:41:35 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: draft-ietf-dnsext-dnssec-registry-fixes.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, iesg@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-dnsext-dnssec-registry-fixes-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, 05 Jun 2011 20:42:09 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>. Please
resolve these comments along with any other Last Call comments you may
receive.

Document: draft-ietf-dnsext-dnssec-registry-fixes-08
Reviewer: Alexey Melnikov
Review Date: 2011-06-05
IETF LC End Date: 2011-06-09
IESG Telechat date:


Summary: not ready for publication as a Proposed Standard, but should be 
easy to fix

Major issues:

Firstly, looking at the difference between this document and the IANA 
registry 
<http://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xml> 
I can see that they have different list of RFC numbers in the rightmost 
collumn. Is this intentional and is the list in the RFC is actually correct?

Secondly, as somebody else already pointed out during the IETF LC the 
range 123-251 is Reserved by [RFC6014] and this is not mentioned in the 
draft.


2.3.  Specifying New Algorithms and Updating Status of Existing Entries

    [RFC6014] establishes a parallel procedure for adding a registry
    entry for a new algorithm other than a standards track document.
    Algorithms entered into the registry using that procedure do not have
    a listed compliance status.  Specifications that follow this path do
    not need to obsolete or update this document.

    Adding a newly specified algorithm to the registry with a compliance
    status SHALL entail obsolescing this document and replacing the
    registry table (with the new algorithm entry).  Altering the status
    column value of any existing algorithm in the registry SHALL entail
    obsoleting this document and replacing the registry table.

    This document cannot be updated, only made obsolete and replaced by a
    successor document.

My personal opinion is that replacing the whole table every time a 
change to a single algorithm implementation status needs to be made is a 
mistake and that will lead to exactly the kind of trouble that this 
document demonstrates: the document is introducing errors to the 
registry. I trust the WG understands what exactly it is doing.

Minor issues:

Abstract

This reads like a compressed version of the Introduction section and it 
is hard to understand before one actually reads the Introduction 
section. Some comments below in attempt to make this a bit clearer:

    The DNS Security Extensions (DNSSEC) requires the use of
    cryptographic algorithm suites for generating digital signatures over
    DNS data.  There is currently an IANA registry for these algorithms
    that is incomplete in that it lacks the implementation status

Maybe "the recommended implementation status"? Before I read the rest of 
the document I thought that that field is about deployment status.

    of each
    algorithm.  This document provides an applicability statement on
    algorithm implementation compliance status for DNSSEC
    implementations.  This status is to measure compliance to this RFC
    only.

Is the last quoted sentence needed here? I would drop it, as it seems 
out of context here.

    This document replaces that registry table with a new IANA
    registry table for Domain Name System Security (DNSSEC) Algorithm
    Numbers that lists (or assigns) each algorithm's status based on the
    current reference.


The Abstract is missing the list of documents being updated and there is 
one obsolete reference (which is intentional according to the 
shepherding write-up).

Nits: none



From Michael.Scharf@alcatel-lucent.com  Sun Jun  5 13:39:16 2011
Return-Path: <Michael.Scharf@alcatel-lucent.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D36821F84E4 for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 13:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=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 NE0lxnvuWPIH for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 13:39:15 -0700 (PDT)
Received: from mailrelay2.alcatel.de (mailrelay2.alcatel.de [194.113.59.96]) by ietfa.amsl.com (Postfix) with ESMTP id 2E63721F84D0 for <gen-art@ietf.org>; Sun,  5 Jun 2011 13:39:14 -0700 (PDT)
Received: from SLFSNX.rcs.alcatel-research.de (slfsn1.rcs.de.alcatel-lucent.com [149.204.60.98]) by mailrelay2.alcatel.de (8.14.3/8.14.3/ICT) with ESMTP id p55Kd4gl019572; Sun, 5 Jun 2011 22:39:04 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 5 Jun 2011 22:39:01 +0200
Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C0607B26D@SLFSNX.rcs.alcatel-research.de>
In-Reply-To: <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
Thread-Index: AcwjNnEUoPKIVgGjRjumizBTr6URowAGZb3gABudxbA=
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com> <4DEAF316.4060701@mti-systems.com> <4DEB018A.9060708@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com>
From: "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>, "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Wesley Eddy" <wes@mti-systems.com>
X-Scanned-By: MIMEDefang 2.64 on 149.204.45.73
X-Mailman-Approved-At: Sun, 05 Jun 2011 15:02:30 -0700
Cc: David Harrington <ietfdbh@comcast.net>, General Area Review Team <gen-art@ietf.org>, draft-ietf-tcpm-persist.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Sun, 05 Jun 2011 20:39:16 -0000

I am not sure whether there was or would be WG consensus for standards
track. We might have to ask the WG that question.

Compared to that, removing RFC 2119 language could probably be a much
simpler and faster solution. And I don't understand why that would
affect the content of the draft that much.

Michael


> -----Original Message-----
> From: Anantha Ramaiah (ananth) [mailto:ananth@cisco.com]=20
> Sent: Sunday, June 05, 2011 9:21 AM
> To: Brian E Carpenter; Wesley Eddy
> Cc: draft-ietf-tcpm-persist.all@tools.ietf.org; General Area=20
> Review Team; David Harrington
> Subject: RE: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
>=20
> So, I am a bit confused, just to summarize my understanding so far :-
>=20
> - if the document status is standards track, then there is no issue.
> - if the document status is informational, then remove the=20
> RFC 2119 usage. Then I am afraid the message of the draft=20
> becomes at the best dubious.
> - retain it as informational, but use "updates 1122". Can=20
> this be done? I am not sure..
>=20
> How do we move forward on this one?
>=20
> -Anantha
>=20
> > -----Original Message-----
> > From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> > Sent: Saturday, June 04, 2011 9:10 PM
> > To: Wesley Eddy
> > Cc: Anantha Ramaiah (ananth); draft-ietf-tcpm-=20
> > persist.all@tools.ietf.org; General Area Review Team; David=20
> Harrington
> > Subject: Re: Gen-ART telechat review of=20
> draft-ietf-tcpm-persist-04.txt
> >=20
> > Hi Wes,
> >=20
> > > In TCPM, it was determined that RFC 1122 is not wrong or flawed,=20
> > > just potentially unclear.
> >=20
> > That's a judgment call that the WG's entitled to make, of course.
> >=20
> > (Side comment: it would be useful for reviewers outside the WG if=20
> > writeups noted why a document was in a particular category=20
> when there=20
> > might be some question about it.)
> >=20
> > > There are many non-standards-track RFCs that include 2119=20
> language,
> >=20
> > True, where the document is self-contained (e.g. an Experimental=20
> > specification). But it goes with my previous point - either it's=20
> > normative, in which case it should be standards track, or=20
> it isn't, in=20
> > which case using RFC 2119 seems inconsistent.
> >=20
> > This is definitely IMHO but I see from Dave Harrington's=20
> DISCUSS that=20
> > he has the same questions.
> >=20
> > Regards
> >    Brian Carpenter
> >=20
> >=20
> >=20
> >=20
> > On 2011-06-05 15:08, Wesley Eddy wrote:
> > > Just commenting on the non-editorial portion:
> > >
> > > On 6/4/2011 5:51 PM, Anantha Ramaiah (ananth) wrote:
> > >>
> > >> ...
> > >>
> > >> Why is this Informational? If it matters, it should be a=20
> Standards
> > Track
> > >> document updating RFC 1122.
> > >>
> > >> ANA>  I agree, it should have been a standards track=20
> document since
> > it
> > >> clarifies the RFC 1122 wording. I believe the TCPM chairs and WG
> > group
> > >> had
> > >> ANA>  approved us to come up with a informational RFC that=20
> > >> ANA> clarifies
> > >> the intention of RFC 1122 regarding persist state. We have no
> > problems
> > >> making ANA>  this a standards track, I'll leave it to=20
> the chairs to=20
> > >> comment on this.
> > >
> > > In TCPM, it was determined that RFC 1122 is not wrong or flawed,=20
> > > just potentially unclear.
> > >
> > > The current draft is a clarification rather than actually=20
> > > augmenting, correcting, extending, or updating any of the=20
> specs and=20
> > > guidance in 1122.
> > >
> > > As I recall, Informational was purposefully chosen by=20
> TCPM; this is=20
> > > more implementation guidance than anything warranting standards
> > track.
> > > As for adding Updates 1122, this may be a good idea; I=20
> don't recall
> > if
> > > it was specifically discussed by the WG.  I noticed at least one
> > other
> > > RFC which includes clarifications is Informational and doesn't=20
> > > Update its parent documents (RFC 4718 is the example)
> > >
> > >
> > >> If it's not a Standards Track document, why is it using RFC 2119=20
> > >> language?
> > >>
> > >> ANA>  I think we need to remove the RFC 2119 language if=20
> the target
> > is
> > >> informational.
> > >
> > > There are many non-standards-track RFCs that include 2119=20
> language,
> > so
> > > it's unclear what the hangup is here.  That said, I think either=20
> > > way, the meaning of this document will be clear, so don't have=20
> > > strong personal feelings one way or the other.
> > >
> > >
>=20

From ananth@cisco.com  Sun Jun  5 17:19:01 2011
Return-Path: <ananth@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 785E111E8082 for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 17:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.949
X-Spam-Level: 
X-Spam-Status: No, score=-9.949 tagged_above=-999 required=5 tests=[AWL=0.650,  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 4pPI6T+9Q3mD for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 17:19:00 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 98B6B11E807A for <gen-art@ietf.org>; Sun,  5 Jun 2011 17:19:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ananth@cisco.com; l=6170; q=dns/txt; s=iport; t=1307319540; x=1308529140; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=9CLggzO6InbCP/SMNJ941ONrLowxgZDwa/+nxXbpxtA=; b=NlkiabKhMG9h7fu7X3uyoMqjPMTwJX2VB6PWUmVg5B57gJ9UFGkaGGDj Yyw5eufNgvpuDgXJ/hyI4I7nAkVNBeVmvNovwHuCBuvax83QjGH+9e3Mz jLXFnv6a1pONdWFzpKkQozWG8fOXmy1qLLa5K86etAjSo0fqMp6ae92fM Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggBABgc7E2rRDoG/2dsb2JhbABTl1aOYHeqK5xlhiEEhnSOVoQohmE
X-IronPort-AV: E=Sophos;i="4.65,324,1304294400"; d="scan'208";a="330619930"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-3.cisco.com with ESMTP; 06 Jun 2011 00:19:00 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p560J0sI023073; Mon, 6 Jun 2011 00:19:00 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 5 Jun 2011 17:19:00 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 5 Jun 2011 17:18:58 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC580CE2C434@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0607B26D@SLFSNX.rcs.alcatel-research.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
Thread-Index: AcwjNnEUoPKIVgGjRjumizBTr6URowAGZb3gABudxbAAB7fskA==
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com> <4DEAF316.4060701@mti-systems.com> <4DEB018A.9060708@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com> <133D9897FB9C5E4E9DF2779DC91E947C0607B26D@SLFSNX.rcs.alcatel-research.de>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>, "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Wesley Eddy" <wes@mti-systems.com>
X-OriginalArrivalTime: 06 Jun 2011 00:19:00.0329 (UTC) FILETIME=[55562590:01CC23DF]
Cc: David Harrington <ietfdbh@comcast.net>, General Area Review Team <gen-art@ietf.org>, draft-ietf-tcpm-persist.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Mon, 06 Jun 2011 00:19:01 -0000

Michael,
    I am sometimes confused with the thinking of *some* TCPM work group
members esp., for such simple drafts(harmless drafts). Now, what if it
is a standards track document, would it be harmful to the internet? Or
if it is informational it would be considered less harmful ? I simply
don't get the point.=20
    At this point I wanted to mention that we have really removed a lot
of contents like API guidance for implemenmters etc., from this draft.
The draft as it stands now is purely a clarification of RFC 1122's
persist behavior which was the original intent for which there was a
reasonable consensus. The WG members need to explain clearly why  they
are nervous about making it a standards track, FWIW, lets take the
urgent pointer clarification RFC which was recently issued (RFC 6093),
that is a standards track document. It simply clarifies the intentions
and usage of urgent pointer, and it is harmless. This document is very
similar to that, IMO.

$0.02,
-Anantha


> -----Original Message-----
> From: SCHARF, Michael [mailto:Michael.Scharf@alcatel-lucent.com]
> Sent: Sunday, June 05, 2011 1:39 PM
> To: Anantha Ramaiah (ananth); Brian E Carpenter; Wesley Eddy
> Cc: draft-ietf-tcpm-persist.all@tools.ietf.org; General Area Review
> Team; David Harrington
> Subject: RE: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
>=20
> I am not sure whether there was or would be WG consensus for standards
> track. We might have to ask the WG that question.
>=20
> Compared to that, removing RFC 2119 language could probably be a much
> simpler and faster solution. And I don't understand why that would
> affect the content of the draft that much.
>=20
> Michael
>=20
>=20
> > -----Original Message-----
> > From: Anantha Ramaiah (ananth) [mailto:ananth@cisco.com]
> > Sent: Sunday, June 05, 2011 9:21 AM
> > To: Brian E Carpenter; Wesley Eddy
> > Cc: draft-ietf-tcpm-persist.all@tools.ietf.org; General Area
> > Review Team; David Harrington
> > Subject: RE: Gen-ART telechat review of draft-ietf-tcpm-persist-
> 04.txt
> >
> > So, I am a bit confused, just to summarize my understanding so far
:-
> >
> > - if the document status is standards track, then there is no issue.
> > - if the document status is informational, then remove the
> > RFC 2119 usage. Then I am afraid the message of the draft
> > becomes at the best dubious.
> > - retain it as informational, but use "updates 1122". Can
> > this be done? I am not sure..
> >
> > How do we move forward on this one?
> >
> > -Anantha
> >
> > > -----Original Message-----
> > > From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> > > Sent: Saturday, June 04, 2011 9:10 PM
> > > To: Wesley Eddy
> > > Cc: Anantha Ramaiah (ananth); draft-ietf-tcpm-
> > > persist.all@tools.ietf.org; General Area Review Team; David
> > Harrington
> > > Subject: Re: Gen-ART telechat review of
> > draft-ietf-tcpm-persist-04.txt
> > >
> > > Hi Wes,
> > >
> > > > In TCPM, it was determined that RFC 1122 is not wrong or flawed,
> > > > just potentially unclear.
> > >
> > > That's a judgment call that the WG's entitled to make, of course.
> > >
> > > (Side comment: it would be useful for reviewers outside the WG if
> > > writeups noted why a document was in a particular category
> > when there
> > > might be some question about it.)
> > >
> > > > There are many non-standards-track RFCs that include 2119
> > language,
> > >
> > > True, where the document is self-contained (e.g. an Experimental
> > > specification). But it goes with my previous point - either it's
> > > normative, in which case it should be standards track, or
> > it isn't, in
> > > which case using RFC 2119 seems inconsistent.
> > >
> > > This is definitely IMHO but I see from Dave Harrington's
> > DISCUSS that
> > > he has the same questions.
> > >
> > > Regards
> > >    Brian Carpenter
> > >
> > >
> > >
> > >
> > > On 2011-06-05 15:08, Wesley Eddy wrote:
> > > > Just commenting on the non-editorial portion:
> > > >
> > > > On 6/4/2011 5:51 PM, Anantha Ramaiah (ananth) wrote:
> > > >>
> > > >> ...
> > > >>
> > > >> Why is this Informational? If it matters, it should be a
> > Standards
> > > Track
> > > >> document updating RFC 1122.
> > > >>
> > > >> ANA>  I agree, it should have been a standards track
> > document since
> > > it
> > > >> clarifies the RFC 1122 wording. I believe the TCPM chairs and
WG
> > > group
> > > >> had
> > > >> ANA>  approved us to come up with a informational RFC that
> > > >> ANA> clarifies
> > > >> the intention of RFC 1122 regarding persist state. We have no
> > > problems
> > > >> making ANA>  this a standards track, I'll leave it to
> > the chairs to
> > > >> comment on this.
> > > >
> > > > In TCPM, it was determined that RFC 1122 is not wrong or flawed,
> > > > just potentially unclear.
> > > >
> > > > The current draft is a clarification rather than actually
> > > > augmenting, correcting, extending, or updating any of the
> > specs and
> > > > guidance in 1122.
> > > >
> > > > As I recall, Informational was purposefully chosen by
> > TCPM; this is
> > > > more implementation guidance than anything warranting standards
> > > track.
> > > > As for adding Updates 1122, this may be a good idea; I
> > don't recall
> > > if
> > > > it was specifically discussed by the WG.  I noticed at least one
> > > other
> > > > RFC which includes clarifications is Informational and doesn't
> > > > Update its parent documents (RFC 4718 is the example)
> > > >
> > > >
> > > >> If it's not a Standards Track document, why is it using RFC
2119
> > > >> language?
> > > >>
> > > >> ANA>  I think we need to remove the RFC 2119 language if
> > the target
> > > is
> > > >> informational.
> > > >
> > > > There are many non-standards-track RFCs that include 2119
> > language,
> > > so
> > > > it's unclear what the hangup is here.  That said, I think either
> > > > way, the meaning of this document will be clear, so don't have
> > > > strong personal feelings one way or the other.
> > > >
> > > >
> >

From wes@mti-systems.com  Sun Jun  5 20:20:43 2011
Return-Path: <wes@mti-systems.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 5972911E8092 for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 20:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id etwrqvqijgd2 for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 20:20:41 -0700 (PDT)
Received: from omr17.networksolutionsemail.com (omr17.networksolutionsemail.com [205.178.146.67]) by ietfa.amsl.com (Postfix) with ESMTP id 615EB11E8086 for <gen-art@ietf.org>; Sun,  5 Jun 2011 20:20:38 -0700 (PDT)
Received: from cm-omr2 (mail.networksolutionsemail.com [205.178.146.50]) by omr17.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id p563Kb36013900 for <gen-art@ietf.org>; Sun, 5 Jun 2011 23:20:37 -0400
Authentication-Results: cm-omr2 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [174.130.37.23] ([174.130.37.23:22390] helo=[192.168.1.104]) by cm-omr2 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 73/47-02428-4874CED4; Sun, 05 Jun 2011 23:20:37 -0400
Message-ID: <4DEC4786.8030401@mti-systems.com>
Date: Sun, 05 Jun 2011 23:20:38 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com> <4DEAF316.4060701@mti-systems.com> <4DEB018A.9060708@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com> <133D9897FB9C5E4E9DF2779DC91E947C0607B26D@SLFSNX.rcs.alcatel-research.de> <0C53DCFB700D144284A584F54711EC580CE2C434@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC580CE2C434@xmb-sjc-21c.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: David Harrington <ietfdbh@comcast.net>, draft-ietf-tcpm-persist.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Mon, 06 Jun 2011 03:20:43 -0000

On 6/5/2011 8:18 PM, Anantha Ramaiah (ananth) wrote:
> Michael,
>      I am sometimes confused with the thinking of *some* TCPM work group
> members esp., for such simple drafts(harmless drafts). Now, what if it
> is a standards track document, would it be harmful to the internet? Or
> if it is informational it would be considered less harmful ? I simply
> don't get the point.
>      At this point I wanted to mention that we have really removed a lot
> of contents like API guidance for implemenmters etc., from this draft.
> The draft as it stands now is purely a clarification of RFC 1122's
> persist behavior which was the original intent for which there was a
> reasonable consensus. The WG members need to explain clearly why  they
> are nervous about making it a standards track, FWIW, lets take the
> urgent pointer clarification RFC which was recently issued (RFC 6093),
> that is a standards track document. It simply clarifies the intentions
> and usage of urgent pointer, and it is harmless. This document is very
> similar to that, IMO.
>


This document contains no protocol and alters no protocol.

I don't agree with attempting any comparison with RFC 6093.  That RFC
changed the specification of the urgent pointer, whereas this
draft does not change the TCP specification one iota.

It's hard to see how Standards Track is appropriate for this draft.

I agree with Michael that "MUST" versus "must" should make little
difference to a reader; they'll get the point.

-- 
Wes Eddy
MTI Systems

From brian.e.carpenter@gmail.com  Sun Jun  5 20:39:32 2011
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 D37FD11E80AD for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 20:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.166
X-Spam-Level: 
X-Spam-Status: No, score=-103.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 vopJbC7BmpxJ for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 20:39:32 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id CF82C11E8088 for <gen-art@ietf.org>; Sun,  5 Jun 2011 20:39:31 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2516311fxm.31 for <gen-art@ietf.org>; Sun, 05 Jun 2011 20:39:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bRlOaaLxUERQOcaLY8XR6aZMuJ2YMAR1WH9m6bb4EG8=; b=N7he7NM91xm2YhJr1N2VT/v/zVwRF+uiZlkjzfQoU+9R/TfQvrF961EACwILEHD6kx waPpfGbl6g/QEzYcnPex2N4L7qH1XEbQXIiCR6RAUtsXrz19Sf2UyFGSpHcpfvcuJMJY HeOfqicanf1jl02dNj47DTfQBwwHvzfeozs20=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=PgIOnsB5W/u0RKKLP4kWsqxE3O2PLslXFClhEA7a+/74GXvBf30SE657yvwgIyzFw8 r0xMs9TxwpyywE5Ain3p5lYMSZq9xGTS8FO0bnqbqrMCedcTqQk/3EEinmEXhu+3NqNz lQllfmp4w1R6e9Ak+mUbGBKTAasOUOuhnYfSQ=
Received: by 10.223.48.139 with SMTP id r11mr2053147faf.63.1307331570642; Sun, 05 Jun 2011 20:39:30 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id 11sm1182485fax.12.2011.06.05.20.39.25 (version=SSLv3 cipher=OTHER); Sun, 05 Jun 2011 20:39:29 -0700 (PDT)
Message-ID: <4DEC4BE0.9040006@gmail.com>
Date: Mon, 06 Jun 2011 15:39:12 +1200
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: Wesley Eddy <wes@mti-systems.com>
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com> <4DEAF316.4060701@mti-systems.com> <4DEB018A.9060708@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com> <133D9897FB9C5E4E9DF2779DC91E947C0607B26D@SLFSNX.rcs.alcatel-research.de> <0C53DCFB700D144284A584F54711EC580CE2C434@xmb-sjc-21c.amer.cisco.com> <4DEC4786.8030401@mti-systems.com>
In-Reply-To: <4DEC4786.8030401@mti-systems.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: David Harrington <ietfdbh@comcast.net>, "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>, draft-ietf-tcpm-persist.all@tools.ietf.org, "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Mon, 06 Jun 2011 03:39:32 -0000

Wes,

> This document contains no protocol and alters no protocol. 

True, but it makes a strong statement about what implementations
must do. I had a quick look, and most implementation guidelines
are Informational, although one or two (e.g. RFC 5625) are BCP.

It would be a lot clearer to a new reader if the title indicated
that it's an implementation guideline - I certainly started reading
on the assumption that it was a protocol update, which as you say,
it isn't.

I'm sure the IESG will come back with a proposed resolution.

Regards
   Brian

On 2011-06-06 15:20, Wesley Eddy wrote:
> On 6/5/2011 8:18 PM, Anantha Ramaiah (ananth) wrote:
>> Michael,
>>      I am sometimes confused with the thinking of *some* TCPM work group
>> members esp., for such simple drafts(harmless drafts). Now, what if it
>> is a standards track document, would it be harmful to the internet? Or
>> if it is informational it would be considered less harmful ? I simply
>> don't get the point.
>>      At this point I wanted to mention that we have really removed a lot
>> of contents like API guidance for implemenmters etc., from this draft.
>> The draft as it stands now is purely a clarification of RFC 1122's
>> persist behavior which was the original intent for which there was a
>> reasonable consensus. The WG members need to explain clearly why  they
>> are nervous about making it a standards track, FWIW, lets take the
>> urgent pointer clarification RFC which was recently issued (RFC 6093),
>> that is a standards track document. It simply clarifies the intentions
>> and usage of urgent pointer, and it is harmless. This document is very
>> similar to that, IMO.
>>
> 
> 
> This document contains no protocol and alters no protocol.
> 
> I don't agree with attempting any comparison with RFC 6093.  That RFC
> changed the specification of the urgent pointer, whereas this
> draft does not change the TCP specification one iota.
> 
> It's hard to see how Standards Track is appropriate for this draft.
> 
> I agree with Michael that "MUST" versus "must" should make little
> difference to a reader; they'll get the point.
> 

From ananth@cisco.com  Sun Jun  5 23:29:08 2011
Return-Path: <ananth@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 494BC11E80C1 for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 23:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.166
X-Spam-Level: 
X-Spam-Status: No, score=-10.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 jekcUQFo8lyu for <gen-art@ietfa.amsl.com>; Sun,  5 Jun 2011 23:29:07 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id 8708411E80C0 for <gen-art@ietf.org>; Sun,  5 Jun 2011 23:29:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ananth@cisco.com; l=945; q=dns/txt; s=iport; t=1307341747; x=1308551347; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=3zvth6T8z/k5yIS8TGp+eEGQWayGiyuBvNxFsmJNLfg=; b=DHRWcsz/iUWGM5UjquKcG9P1/BS0jc4o6YwJI+2szIUs8UUXML+Xm+1o HtYZzHQWnP/xYHule1nWJEkKSokLHcqvw4yK6z729GfjqIK31h8yIKOOT zb6o5d7LXYGIjH3V06jrqvJt8UWO+A76f39JIa2jqRS9HsyuIXntixI2c M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOBy7E2rRDoJ/2dsb2JhbABTpjZ3iHGkG50FhiEEhnSOVosJ
X-IronPort-AV: E=Sophos;i="4.65,325,1304294400"; d="scan'208";a="460172103"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-1.cisco.com with ESMTP; 06 Jun 2011 06:29:07 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p566T6nt021861; Mon, 6 Jun 2011 06:29:06 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 5 Jun 2011 23:29:06 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 5 Jun 2011 23:29:04 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC580CE2C49C@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <4DEC4786.8030401@mti-systems.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
Thread-Index: Acwj+LaSkvXPIm4GQOqDIHBXxwTw/gAF3hpw
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com> <4DEAF316.4060701@mti-systems.com> <4DEB018A.9060708@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com> <133D9897FB9C5E4E9DF2779DC91E947C0607B26D@SLFSNX.rcs.alcatel-research.de> <0C53DCFB700D144284A584F54711EC580CE2C434@xmb-sjc-21c.amer.cisco.com> <4DEC4786.8030401@mti-systems.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Wesley Eddy" <wes@mti-systems.com>
X-OriginalArrivalTime: 06 Jun 2011 06:29:06.0316 (UTC) FILETIME=[0922DCC0:01CC2413]
Cc: David Harrington <ietfdbh@comcast.net>, draft-ietf-tcpm-persist.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Mon, 06 Jun 2011 06:29:08 -0000

Hi Wes,

>=20
> This document contains no protocol and alters no protocol.

But it documents (clarifies) a protocol action namely persist condition,
FWIW.

>=20
> I don't agree with attempting any comparison with RFC 6093.  That RFC
> changed the specification of the urgent pointer, whereas this
> draft does not change the TCP specification one iota.

Fair enough.

>=20
> It's hard to see how Standards Track is appropriate for this draft.

Well, if a document updates a standards track document, then I don't see
any issues making the updating document a standards track.

>=20
> I agree with Michael that "MUST" versus "must" should make little
> difference to a reader; they'll get the point.

Brain's point was that if we documenting an oversight then lets be
honest about it. In the same spirits, why do we want even change the
"MUST" to must.. Just to make the document informational? Beats me..

-Anantha

From alexey.melnikov@isode.com  Mon Jun  6 04:18:08 2011
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 6C6F711E8125; Mon,  6 Jun 2011 04:18:08 -0700 (PDT)
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=-0.300, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, 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 v2IEJcpUi+SG; Mon,  6 Jun 2011 04:18:07 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 8A70C11E80D6; Mon,  6 Jun 2011 04:18:07 -0700 (PDT)
Received: from [188.29.83.203] (188.29.83.203.threembb.co.uk [188.29.83.203])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Tey3aQA-uawF@rufus.isode.com>; Mon, 6 Jun 2011 12:18:03 +0100
Message-ID: <4DECB756.1010603@isode.com>
Date: Mon, 06 Jun 2011 12:17:42 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: draft-ietf-v6ops-6to4-advisory.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, iesg@ietf.org
Subject: [Gen-art]  Gen-ART LC review of draft-ietf-v6ops-6to4-advisory-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: Mon, 06 Jun 2011 11:18: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-ietf-v6ops-6to4-advisory-01.txt
Reviewer: Alexey Melnikov
Review Date: 2011-06-06
IETF LC End Date: 2011-06-16
IESG Telechat date:



Summary: ready (with nits) for publication as an Informational RFC.

Major issues: none

Minor issues: none

Nits:

2.1.  Router 6to4

    Some 6to4 routers are also configured as "Relay routers."  They
    behave as just described, but in addition they obtain native IPv6
    connectivity with a normal IPv6 prefix.  They announce an IPv6 route
    to 2002::/16.  For example, assume that the 6to4 router at
    190.0.2.187 is a relay router, whose address on the 6to4 side is
    2002:c000:2bb::1.  Suppose that a host with the 6to4 address 2002:
    c000:2aa::123 sends an IPv6 packet to a native IPv6 destination such
    as 2001:db8:123:456::321.  Assume that the 6to4 router at 192.0.2.170
    has its IPv6 default route set to 2002:c000:2bb::1, i.e. the relay.
    The packet will be delivered to the relay, encapsulated in IPv4.
    After decapsulation, the relay will forward the packet into native
    IPv6 for delivery.

I might be getting confused, but is "the relay" in the last 2 quoted 
sentences mean 2 different things?

    When the remote host replies, the packet (source
    2001:db8:123:456::321, destination 2002:c000:2aa::123) will find a
    route to 2002::/16 and hence be delivered to a 6to4 relay.  The
    process will be reversed and the packet will be encapsulated and
    forwarded to the 6to4 router at 192.0.2.170 for final delivery.


3.  Problems Observed

    7.  Bogus Address Failure: By design, 6to4 does not work and will not
        activate itself if the available V4ADDR is a private address
        [RFC1918].  However it will also not work if the available V4ADDR
        is a "bogon", i.e. a global address that is being used by the
        operator as a private address.  A common case of this is a legacy
        wireless network using 1.1.1.0/24 as if it was a private address.
        In this case, 6to4 will assume it is connected to the global
        Internet, but there is certainly no working return path.

        This failure mode will also occur if an ISP is operating a
        Carrier Grade NAT between its customers and the Internet, and is

I think adding a reference to an RFC that defines the term would be 
useful here. (I've seen the term with a proper reference recently, but I 
don't remember the name of the document.)

        using global public address space as if it were private space to
        do so.

4.5.  Content providers and their ISPs

    Content providers who do embed the relay function in this way could,
    in theory, accept inbound 6to4 traffic as well.  This is highly
    unadvisable since, according the the rules of 6to4, they would then
    have to relay traffic for other IPv6 destinations too.  So they
    should not be reachable via 192.88.99.1.  Also, they should certainly
    not create an AAAA record for their 6to4 address - their inbound IPv6
    access should be native, and advertising a 6to4 address might well
    lead to uRPF ingress filtering problems.

What is uRPF?


    [RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
               via IPv4 Clouds", RFC 3056, February 2001.

    [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
               RFC 3068, June 2001.

I believe these 2 references need to be Normative, as they are required 
to understand this document.


From mccap@petoni.org  Mon Jun  6 06:11:28 2011
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 C1EAA11E8133 for <gen-art@ietfa.amsl.com>; Mon,  6 Jun 2011 06:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CkpctOb2Qwv7 for <gen-art@ietfa.amsl.com>; Mon,  6 Jun 2011 06:11:28 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 19B9511E8132 for <gen-art@ietf.org>; Mon,  6 Jun 2011 06:11:27 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2798117fxm.31 for <gen-art@ietf.org>; Mon, 06 Jun 2011 06:11:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.28.220 with SMTP id n28mr5286701fac.101.1307365886284; Mon, 06 Jun 2011 06:11:26 -0700 (PDT)
Received: by 10.223.54.88 with HTTP; Mon, 6 Jun 2011 06:11:26 -0700 (PDT)
X-Originating-IP: [108.111.188.105]
Date: Mon, 6 Jun 2011 08:11:26 -0500
Message-ID: <BANLkTikzLkXL9=e4HGDra5t2F2+Pz0rBkA@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org,  draft-meadors-multiple-attachments-ediint.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] Gen-ART Telechat Review of draft-meadors-multiple-attachments-ediint-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: Mon, 06 Jun 2011 13:11:28 -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-meadors-multiple-attachments-ediint-12
Reviewer: Pete McCann
Review Date: 2011-06-06
IETF LC End Date:
IESG Telechat date: 2011-06-09

Summary: Ready.

Major issues: none

Minor issues: none

Nits/editorial comments:

My nit from the last review was not addressed.  Maybe it is a non-issue?

There is a space in the declaration of boundary=" INNER-BOUNDARY";
in the example in section 3.  I am not sure whether this was intentional
or whether it will mess up a standard MIME parser, but you may want
to remove it.

From fred@cisco.com  Mon Jun  6 10:16:30 2011
Return-Path: <fred@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 8277C11E81B1; Mon,  6 Jun 2011 10:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.149
X-Spam-Level: 
X-Spam-Status: No, score=-110.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, 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 2qPJ5lREe4Lk; Mon,  6 Jun 2011 10:16:29 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id B84FC11E81B0; Mon,  6 Jun 2011 10:16:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=4157; q=dns/txt; s=iport; t=1307380589; x=1308590189; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=l2wfOAf7+eowtjGYD7O7yjvdl2Td64AoeyABRdW1Asc=; b=Gcl04o78HCT1zZ10uTHKN8/CgswQSjqRUT0DCl4czo7Y/slf4wv+VGvG M7kocpMFXHvm+MOdIjoJuJ+sp8ZUE/OHlYF5S/VCoq2RWSwzZCB+3mEHI nrILjdynHTWtpXxUQ0JVAVmwHQ1FbjfvafZZrb+a1rV5coJvuXtU+rWUn s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EABEK7U2rRDoI/2dsb2JhbABTpiR3iHGiZZ1shiEEhnSKBYRIixI
X-IronPort-AV: E=Sophos;i="4.65,327,1304294400"; d="scan'208";a="331148695"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-3.cisco.com with ESMTP; 06 Jun 2011 17:16:29 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p56HGNhA020920; Mon, 6 Jun 2011 17:16:28 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Mon, 06 Jun 2011 10:16:29 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Mon, 06 Jun 2011 10:16:29 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4DECB756.1010603@isode.com>
Date: Mon, 6 Jun 2011 10:16:13 -0700
Message-Id: <674B45C9-0E00-447E-87D7-8EECB69CE80E@cisco.com>
References: <4DECB756.1010603@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: gen-art@ietf.org, draft-ietf-v6ops-6to4-advisory.all@tools.ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-6to4-advisory-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: Mon, 06 Jun 2011 17:16:30 -0000

Thanks Alexey

Brian, I would presume that the IESG will be looking for an update =
responsive to these comments.

On Jun 6, 2011, at 4:17 AM, 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.
>=20
>=20
> Document: draft-ietf-v6ops-6to4-advisory-01.txt
> Reviewer: Alexey Melnikov
> Review Date: 2011-06-06
> IETF LC End Date: 2011-06-16
> IESG Telechat date:
>=20
>=20
>=20
> Summary: ready (with nits) for publication as an Informational RFC.
>=20
> Major issues: none
>=20
> Minor issues: none
>=20
> Nits:
>=20
> 2.1.  Router 6to4
>=20
>   Some 6to4 routers are also configured as "Relay routers."  They
>   behave as just described, but in addition they obtain native IPv6
>   connectivity with a normal IPv6 prefix.  They announce an IPv6 route
>   to 2002::/16.  For example, assume that the 6to4 router at
>   190.0.2.187 is a relay router, whose address on the 6to4 side is
>   2002:c000:2bb::1.  Suppose that a host with the 6to4 address 2002:
>   c000:2aa::123 sends an IPv6 packet to a native IPv6 destination such
>   as 2001:db8:123:456::321.  Assume that the 6to4 router at =
192.0.2.170
>   has its IPv6 default route set to 2002:c000:2bb::1, i.e. the relay.
>   The packet will be delivered to the relay, encapsulated in IPv4.
>   After decapsulation, the relay will forward the packet into native
>   IPv6 for delivery.
>=20
> I might be getting confused, but is "the relay" in the last 2 quoted =
sentences mean 2 different things?
>=20
>   When the remote host replies, the packet (source
>   2001:db8:123:456::321, destination 2002:c000:2aa::123) will find a
>   route to 2002::/16 and hence be delivered to a 6to4 relay.  The
>   process will be reversed and the packet will be encapsulated and
>   forwarded to the 6to4 router at 192.0.2.170 for final delivery.
>=20
>=20
> 3.  Problems Observed
>=20
>   7.  Bogus Address Failure: By design, 6to4 does not work and will =
not
>       activate itself if the available V4ADDR is a private address
>       [RFC1918].  However it will also not work if the available =
V4ADDR
>       is a "bogon", i.e. a global address that is being used by the
>       operator as a private address.  A common case of this is a =
legacy
>       wireless network using 1.1.1.0/24 as if it was a private =
address.
>       In this case, 6to4 will assume it is connected to the global
>       Internet, but there is certainly no working return path.
>=20
>       This failure mode will also occur if an ISP is operating a
>       Carrier Grade NAT between its customers and the Internet, and is
>=20
> I think adding a reference to an RFC that defines the term would be =
useful here. (I've seen the term with a proper reference recently, but I =
don't remember the name of the document.)
>=20
>       using global public address space as if it were private space to
>       do so.
>=20
> 4.5.  Content providers and their ISPs
>=20
>   Content providers who do embed the relay function in this way could,
>   in theory, accept inbound 6to4 traffic as well.  This is highly
>   unadvisable since, according the the rules of 6to4, they would then
>   have to relay traffic for other IPv6 destinations too.  So they
>   should not be reachable via 192.88.99.1.  Also, they should =
certainly
>   not create an AAAA record for their 6to4 address - their inbound =
IPv6
>   access should be native, and advertising a 6to4 address might well
>   lead to uRPF ingress filtering problems.
>=20
> What is uRPF?
>=20
>=20
>   [RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
>              via IPv4 Clouds", RFC 3056, February 2001.
>=20
>   [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
>              RFC 3068, June 2001.
>=20
> I believe these 2 references need to be Normative, as they are =
required to understand this document.
>=20


From ananth@cisco.com  Mon Jun  6 10:40:19 2011
Return-Path: <ananth@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 DF3B511E8198 for <gen-art@ietfa.amsl.com>; Mon,  6 Jun 2011 10:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.339
X-Spam-Level: 
X-Spam-Status: No, score=-10.339 tagged_above=-999 required=5 tests=[AWL=0.260, 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 KYM-LyBUAOlW for <gen-art@ietfa.amsl.com>; Mon,  6 Jun 2011 10:40:19 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF1C11E8090 for <gen-art@ietf.org>; Mon,  6 Jun 2011 10:40:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ananth@cisco.com; l=1558; q=dns/txt; s=iport; t=1307382019; x=1308591619; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=R5mwF0T4HX6rs8WWiFy4MTXw46Mta53R1RCUU9yMcj8=; b=N+te+ahir1NmCfjQ/ZniQ1l/2EETdhnE8RvrQ38jp+90QkjpZthLi/BJ xvj/1uf3n5e9D3/BnFirNZoeCNCVyqED3XGzB9FTm7HuPSinNLC4IkUuu BnNO9hXj+pg/qurb4q6zAWn97DFrC57h7nuXW5lq2RTVtQJlCw5RizIYg s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwBAFQQ7U2rRDoI/2dsb2JhbABTl0KOYneIcaJ0nXKGIQSGdI5Wiwk
X-IronPort-AV: E=Sophos;i="4.65,327,1304294400"; d="scan'208";a="371183494"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-2.cisco.com with ESMTP; 06 Jun 2011 17:40:19 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p56HeJpe015772; Mon, 6 Jun 2011 17:40:19 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 6 Jun 2011 10:40:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 6 Jun 2011 10:40:17 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC580CE2C61B@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC580CE2C49C@xmb-sjc-21c.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
Thread-Index: Acwj+LaSkvXPIm4GQOqDIHBXxwTw/gAF3hpwABgPECA=
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com> <4DEAF316.4060701@mti-systems.com> <4DEB018A.9060708@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com> <133D9897FB9C5E4E9DF2779DC91E947C0607B26D@SLFSNX.rcs.alcatel-research.de> <0C53DCFB700D144284A584F54711EC580CE2C434@xmb-sjc-21c.amer.cisco.com> <4DEC4786.8030401@mti-systems.com> <0C53DCFB700D144284A584F54711EC580CE2C49C@xmb-sjc-21c.amer.cisco.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Wesley Eddy" <wes@mti-systems.com>
X-OriginalArrivalTime: 06 Jun 2011 17:40:18.0857 (UTC) FILETIME=[CD70F190:01CC2470]
Cc: David Harrington <ietfdbh@comcast.net>, draft-ietf-tcpm-persist.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Mon, 06 Jun 2011 17:40:20 -0000

Sorry about an inadvertent typo below :-

> Brain's point was that if we documenting an oversight then lets be

Should be :-

Brian's point was that, if we are documenting .....

-Anantha


> -----Original Message-----
> From: Anantha Ramaiah (ananth)
> Sent: Sunday, June 05, 2011 11:29 PM
> To: Wesley Eddy
> Cc: SCHARF, Michael; Brian E Carpenter; draft-ietf-tcpm-
> persist.all@tools.ietf.org; General Area Review Team; David Harrington
> Subject: RE: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
>=20
> Hi Wes,
>=20
> >
> > This document contains no protocol and alters no protocol.
>=20
> But it documents (clarifies) a protocol action namely persist
> condition,
> FWIW.
>=20
> >
> > I don't agree with attempting any comparison with RFC 6093.  That
RFC
> > changed the specification of the urgent pointer, whereas this
> > draft does not change the TCP specification one iota.
>=20
> Fair enough.
>=20
> >
> > It's hard to see how Standards Track is appropriate for this draft.
>=20
> Well, if a document updates a standards track document, then I don't
> see
> any issues making the updating document a standards track.
>=20
> >
> > I agree with Michael that "MUST" versus "must" should make little
> > difference to a reader; they'll get the point.
>=20
> Brain's point was that if we documenting an oversight then lets be
> honest about it. In the same spirits, why do we want even change the
> "MUST" to must.. Just to make the document informational? Beats me..
>=20
> -Anantha

From david.borman@windriver.com  Mon Jun  6 14:19:39 2011
Return-Path: <david.borman@windriver.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 BE88111E81BB for <gen-art@ietfa.amsl.com>; Mon,  6 Jun 2011 14:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[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 myD+ob7lxL6b for <gen-art@ietfa.amsl.com>; Mon,  6 Jun 2011 14:19:38 -0700 (PDT)
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by ietfa.amsl.com (Postfix) with ESMTP id B808B11E8175 for <gen-art@ietf.org>; Mon,  6 Jun 2011 14:19:37 -0700 (PDT)
Received: from ALA-HCB.corp.ad.wrs.com (ala-hcb [147.11.189.41]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id p56LJY2T014730 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Jun 2011 14:19:34 -0700 (PDT)
Received: from ALA-MBB.corp.ad.wrs.com ([169.254.2.242]) by ALA-HCB.corp.ad.wrs.com ([147.11.189.41]) with mapi id 14.01.0255.000; Mon, 6 Jun 2011 14:19:34 -0700
From: "Borman, David" <david.borman@windriver.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: Gen-ART telechat review of draft-ietf-tcpm-persist-04.txt
Thread-Index: AQHMIvRPnPpnqCoCC0a1mlgRY0WdqJSuMqqAgABYWgCAABE7AIAANYYAgADe3oCAAD11AIAAMsEAgAAFMACAAShBAA==
Date: Mon, 6 Jun 2011 21:19:33 +0000
Message-ID: <1F9BD01B-43B8-41F8-B49B-98C48A4010E1@windriver.com>
References: <4DEA9277.4020702@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3CE@xmb-sjc-21c.amer.cisco.com> <4DEAF316.4060701@mti-systems.com> <4DEB018A.9060708@gmail.com> <0C53DCFB700D144284A584F54711EC580CE2C3EE@xmb-sjc-21c.amer.cisco.com> <133D9897FB9C5E4E9DF2779DC91E947C0607B26D@SLFSNX.rcs.alcatel-research.de> <0C53DCFB700D144284A584F54711EC580CE2C434@xmb-sjc-21c.amer.cisco.com> <4DEC4786.8030401@mti-systems.com> <4DEC4BE0.9040006@gmail.com>
In-Reply-To: <4DEC4BE0.9040006@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.25.34.20]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A2AC0A806CA6FA43B6CEA3E8D6AB840A@corp.ad.wrs.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 06 Jun 2011 14:21:42 -0700
Cc: "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>, Wesley Eddy <wes@mti-systems.com>, General Area Review Team <gen-art@ietf.org>, "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, "<draft-ietf-tcpm-persist.all@tools.ietf.org>" <draft-ietf-tcpm-persist.all@tools.ietf.org>, David Harrington <ietfdbh@comcast.net>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-tcpm-persist-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: Mon, 06 Jun 2011 21:19:39 -0000

The persist document can be summed up in one sentence: Connections that are=
 in persist (zero window probe) are no different than any other connection =
in established state.

When RFC 1122 was written, there existed TCP implementations that were drop=
ping connections in persist state, treating connections that did not move f=
orward the same as connections that weren't getting any ACKs.  RFC 1122 sai=
d, no, as long as you are getting ACK responses, the connection is still va=
lid, and TCP shouldn't be timing out the connection.

Some TCP implementors read that as meaning that connections in persist stat=
e had to be handled specially, and swung the pendulum to the other extreme,=
 and wouldn't drop connections in persist state even when under the exact s=
ame circumstances they would drop other connections in established state.

This ID is trying to get the pendulum back to the center.  From the perspec=
tive of the TCP protocol, as long as ACKs are being received to probes whil=
e in persist state, the connection is valid.  Other things outside the TCP =
protocol, such as applications or the OS, can decide to terminate any TCP c=
onnection for any reason.  An application exits.  The OS is running out of =
resources and decides to abort TCP connections.  Someone shuts down the com=
puter.  There are lots of things outside of the TCP protocol that can cause=
 TCP connections to be aborted.

This ID is not changing anything in the TCP protocol.  It is only correctin=
g how some implementors had mis-interpreted RFC 1122, and this mis-interpre=
tation is by no means universal.  The WG consensus was that this makes it I=
nformational.

			-David Borman

On Jun 5, 2011, at 10:39 PM, Brian E Carpenter wrote:

> Wes,
>=20
>> This document contains no protocol and alters no protocol.=20
>=20
> True, but it makes a strong statement about what implementations
> must do. I had a quick look, and most implementation guidelines
> are Informational, although one or two (e.g. RFC 5625) are BCP.
>=20
> It would be a lot clearer to a new reader if the title indicated
> that it's an implementation guideline - I certainly started reading
> on the assumption that it was a protocol update, which as you say,
> it isn't.
>=20
> I'm sure the IESG will come back with a proposed resolution.
>=20
> Regards
>   Brian
>=20
> On 2011-06-06 15:20, Wesley Eddy wrote:
>> On 6/5/2011 8:18 PM, Anantha Ramaiah (ananth) wrote:
>>> Michael,
>>>     I am sometimes confused with the thinking of *some* TCPM work group
>>> members esp., for such simple drafts(harmless drafts). Now, what if it
>>> is a standards track document, would it be harmful to the internet? Or
>>> if it is informational it would be considered less harmful ? I simply
>>> don't get the point.
>>>     At this point I wanted to mention that we have really removed a lot
>>> of contents like API guidance for implemenmters etc., from this draft.
>>> The draft as it stands now is purely a clarification of RFC 1122's
>>> persist behavior which was the original intent for which there was a
>>> reasonable consensus. The WG members need to explain clearly why  they
>>> are nervous about making it a standards track, FWIW, lets take the
>>> urgent pointer clarification RFC which was recently issued (RFC 6093),
>>> that is a standards track document. It simply clarifies the intentions
>>> and usage of urgent pointer, and it is harmless. This document is very
>>> similar to that, IMO.
>>>=20
>>=20
>>=20
>> This document contains no protocol and alters no protocol.
>>=20
>> I don't agree with attempting any comparison with RFC 6093.  That RFC
>> changed the specification of the urgent pointer, whereas this
>> draft does not change the TCP specification one iota.
>>=20
>> It's hard to see how Standards Track is appropriate for this draft.
>>=20
>> I agree with Michael that "MUST" versus "must" should make little
>> difference to a reader; they'll get the point.
>>=20


From paul.hoffman@vpnc.org  Mon Jun  6 15:12:38 2011
Return-Path: <paul.hoffman@vpnc.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 D39E911E81D1; Mon,  6 Jun 2011 15:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, 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 QVfxiTZsQ7UQ; Mon,  6 Jun 2011 15:12:38 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id AAE1011E81D2; Mon,  6 Jun 2011 15:12:37 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p56MCVq1028807 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Jun 2011 15:12:31 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com>
Date: Mon, 6 Jun 2011 15:12:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 06 Jun 2011 22:12:39 -0000

On May 29, 2011, at 4:13 AM, Roni Even wrote:

> Major issues:
>=20
> 1.       I am not sure how the IANA consideration section is in-line =
with the IANA consideration section of RFC5892. Maybe some clarification =
text would be helpful.

We think that the IANA considerations here are, in fact, what RFC 5892 =
was designed for. That is, RFC 5892 says that the registry will be =
updated ("IANA has created a registry with the derived properties for =
the versions of Unicode released after (and including) version 5.2"), =
and this is such an update. Please let me know if that doesn't match =
your understanding.

> 2.       The IANA registry for derived property value has RFC 5892, =
does this draft want to change the reference, how will it be done.

Section 2 of the draft is pretty clear here: "No change to RFC 5892 is =
needed based on the changes made in Unicode 6.0".

>   I think that it relates also to the issue of whether this draft =
updates RFC 5892.

And here too.

--Paul Hoffman


From brian.e.carpenter@gmail.com  Mon Jun  6 16:38:52 2011
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 3839B1F0C4F; Mon,  6 Jun 2011 16:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.38
X-Spam-Level: 
X-Spam-Status: No, score=-102.38 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619, 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 0gcqdhaNwHO5; Mon,  6 Jun 2011 16:38:51 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4CCF91F0C4D; Mon,  6 Jun 2011 16:38:51 -0700 (PDT)
Received: by gwb20 with SMTP id 20so2150266gwb.31 for <multiple recipients>; Mon, 06 Jun 2011 16:38:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=pwlzp030vXNLuSMNDem9Bm/YQrw+S2un6/F3X/CVbZg=; b=ZhDg4I84zJJet7uSSUjKaESMvWCoMbUuaiAFw68FrBkYOEAE0epPeOCMqo3k/6+AfZ Z6q4JET+R4RE2IAePHWYOjJkFKXWBeSWL9qVacJrALREzFBEkegPWQUBQkdGP39AgB/4 cZmRQMDUYU6//F9sCbMieTUNnncMeHeVjUHlg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=slMuIy7ZPORB/cvwQm0O6GnFaWVoInVE77u91zeZe4KOVCtQ+SQy0pL0lreZ/AfLc8 yoVf38qSa5i3Mv6Hp5z/E/QQvZDFYaOHt7hz2+I+uZ09qlrbBDLdLqfCb9Cq0zc37zk3 Y2WI/xeAqAn52VZJOTLEgSu3/Y4cOtLoVAGJ4=
Received: by 10.236.103.104 with SMTP id e68mr5658624yhg.188.1307403529053; Mon, 06 Jun 2011 16:38:49 -0700 (PDT)
Received: from [10.71.2.198] ([12.68.183.2]) by mx.google.com with ESMTPS id i62sm3571231yhm.52.2011.06.06.16.38.45 (version=SSLv3 cipher=OTHER); Mon, 06 Jun 2011 16:38:48 -0700 (PDT)
Message-ID: <4DED64FD.1020209@gmail.com>
Date: Tue, 07 Jun 2011 11:38:37 +1200
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: Fred Baker <fred@cisco.com>
References: <4DECB756.1010603@isode.com> <674B45C9-0E00-447E-87D7-8EECB69CE80E@cisco.com>
In-Reply-To: <674B45C9-0E00-447E-87D7-8EECB69CE80E@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-v6ops-6to4-advisory.all@tools.ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-6to4-advisory-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: Mon, 06 Jun 2011 23:38:52 -0000

Fred,

See my comments in line. I'm on travel, but should be able to do an update
if necessary, after the LC ends.

Alexey,

Thanks for the review.

On 2011-06-07 05:16, Fred Baker wrote:
> Thanks Alexey
> 
> Brian, I would presume that the IESG will be looking for an update responsive to these comments.
> 
> On Jun 6, 2011, at 4:17 AM, 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-v6ops-6to4-advisory-01.txt
>> Reviewer: Alexey Melnikov
>> Review Date: 2011-06-06
>> IETF LC End Date: 2011-06-16
>> IESG Telechat date:
>>
>>
>>
>> Summary: ready (with nits) for publication as an Informational RFC.
>>
>> Major issues: none
>>
>> Minor issues: none
>>
>> Nits:
>>
>> 2.1.  Router 6to4
>>
>>   Some 6to4 routers are also configured as "Relay routers."  They
>>   behave as just described, but in addition they obtain native IPv6
>>   connectivity with a normal IPv6 prefix.  They announce an IPv6 route
>>   to 2002::/16.  For example, assume that the 6to4 router at
>>   190.0.2.187 is a relay router, whose address on the 6to4 side is
>>   2002:c000:2bb::1.  Suppose that a host with the 6to4 address 2002:
>>   c000:2aa::123 sends an IPv6 packet to a native IPv6 destination such
>>   as 2001:db8:123:456::321.  Assume that the 6to4 router at 192.0.2.170
>>   has its IPv6 default route set to 2002:c000:2bb::1, i.e. the relay.
>>   The packet will be delivered to the relay, encapsulated in IPv4.
>>   After decapsulation, the relay will forward the packet into native
>>   IPv6 for delivery.
>>
>> I might be getting confused, but is "the relay" in the last 2 quoted sentences mean 2 different things?

No, it is the same relay - I can clarify that of course.

>>   When the remote host replies, the packet (source
>>   2001:db8:123:456::321, destination 2002:c000:2aa::123) will find a
>>   route to 2002::/16 and hence be delivered to a 6to4 relay.  The
>>   process will be reversed and the packet will be encapsulated and
>>   forwarded to the 6to4 router at 192.0.2.170 for final delivery.
>>
>>
>> 3.  Problems Observed
>>
>>   7.  Bogus Address Failure: By design, 6to4 does not work and will not
>>       activate itself if the available V4ADDR is a private address
>>       [RFC1918].  However it will also not work if the available V4ADDR
>>       is a "bogon", i.e. a global address that is being used by the
>>       operator as a private address.  A common case of this is a legacy
>>       wireless network using 1.1.1.0/24 as if it was a private address.
>>       In this case, 6to4 will assume it is connected to the global
>>       Internet, but there is certainly no working return path.
>>
>>       This failure mode will also occur if an ISP is operating a
>>       Carrier Grade NAT between its customers and the Internet, and is
>>
>> I think adding a reference to an RFC that defines the term would be useful here. (I've seen the term with a proper reference recently, but I don't remember the name of the document.)

I think at the moment it will have to be a work-in-progress reference
(draft-ietf-behave-lsn-requirements)

>>       using global public address space as if it were private space to
>>       do so.
>>
>> 4.5.  Content providers and their ISPs
>>
>>   Content providers who do embed the relay function in this way could,
>>   in theory, accept inbound 6to4 traffic as well.  This is highly
>>   unadvisable since, according the the rules of 6to4, they would then
>>   have to relay traffic for other IPv6 destinations too.  So they
>>   should not be reachable via 192.88.99.1.  Also, they should certainly
>>   not create an AAAA record for their 6to4 address - their inbound IPv6
>>   access should be native, and advertising a 6to4 address might well
>>   lead to uRPF ingress filtering problems.
>>
>> What is uRPF?

unicast reverse path forwarding (RPF) [RFC3704]

I can add a reference.
>>
>>
>>   [RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
>>              via IPv4 Clouds", RFC 3056, February 2001.
>>
>>   [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
>>              RFC 3068, June 2001.
>>
>> I believe these 2 references need to be Normative, as they are required to understand this document.

True, but this is an informational document, so why would any references be normative?

    Brian

From fred@cisco.com  Mon Jun  6 16:58:10 2011
Return-Path: <fred@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 7540121F84EE; Mon,  6 Jun 2011 16:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.782
X-Spam-Level: 
X-Spam-Status: No, score=-110.782 tagged_above=-999 required=5 tests=[AWL=-0.183, 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 z8oAV0EFWcr8; Mon,  6 Jun 2011 16:58:09 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfa.amsl.com (Postfix) with ESMTP id DCC1021F84EB; Mon,  6 Jun 2011 16:58:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=955; q=dns/txt; s=iport; t=1307404689; x=1308614289; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=4M7bdtUBp5aqxgJXd5SLEfjTx2sYcmeiFHl+BPagzNk=; b=N0q04R63XApy4AkLhSXv0WkCsC6Sa36udzVoghY2kqhXEFgQymK4tnP5 jtAiNoQRoGVi93+UPAar4JoMOH5TZgqHkdmbS17k/zQx62tf8ckDZuuzD 4DT+f7xlT3Zw5LSKHYh/sHDWvUt2XG+9YA1HiohYFgI+QInsh1DfQb7BF o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EADxo7U2rRDoJ/2dsb2JhbABTphd3rCOeFYYhBIZ1ig6ETIsW
X-IronPort-AV: E=Sophos;i="4.65,328,1304294400"; d="scan'208";a="371415238"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-2.cisco.com with ESMTP; 06 Jun 2011 23:58:09 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p56Nw3Th032406; Mon, 6 Jun 2011 23:58:09 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Mon, 06 Jun 2011 16:58:09 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Mon, 06 Jun 2011 16:58:09 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4DED64FD.1020209@gmail.com>
Date: Mon, 6 Jun 2011 16:57:52 -0700
Message-Id: <64814768-703C-4805-B273-F9D2EBE11B7D@cisco.com>
References: <4DECB756.1010603@isode.com> <674B45C9-0E00-447E-87D7-8EECB69CE80E@cisco.com> <4DED64FD.1020209@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: gen-art@ietf.org, draft-ietf-v6ops-6to4-advisory.all@tools.ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-6to4-advisory-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: Mon, 06 Jun 2011 23:58:10 -0000

On Jun 6, 2011, at 4:38 PM, Brian E Carpenter wrote:

>>>  [RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
>>>             via IPv4 Clouds", RFC 3056, February 2001.
>>>=20
>>>  [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
>>>             RFC 3068, June 2001.
>>=20
>> I believe these 2 references need to be Normative, as they are =
required to understand this document.
>=20
> True, but this is an informational document, so why would any =
references be normative?

This is something we spoke about in the working group, and you answered =
me the same way. I think he's not saying (and I was not saying then) =
that the references are normative for the Internet. They're saying that, =
unlike an informative reference (which may give you a deeper =
understanding but for most of the document are optional reading), you =
can't understand this document if you don't understand those two.=

From brian.e.carpenter@gmail.com  Mon Jun  6 19:28:18 2011
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 84BD711E80A3; Mon,  6 Jun 2011 19:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.88
X-Spam-Level: 
X-Spam-Status: No, score=-102.88 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619, 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 JV3ybyogM9Rh; Mon,  6 Jun 2011 19:28:18 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id CE7D211E8090; Mon,  6 Jun 2011 19:28:17 -0700 (PDT)
Received: by yib18 with SMTP id 18so1129174yib.31 for <multiple recipients>; Mon, 06 Jun 2011 19:28:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=NqgEZpz79iDwGYpbeA2IhFjiZeAZfWMqlrMa7M7vj7Q=; b=cgyMS6fEg6lDaqMYDQehAEifg06jy8yG50brx9I92UpJZDhbhaP+TlQo382AxY/ir0 a4vR8Z7A6kB752hfr1LhJoOD6B6dk54vrtS2aHWerwxYdbJajgZ0YgLlDUBqQVPK9K3t 8TwjlN/5kIUOdFPUky72V+BciqGhj2MUCYbOk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=EN6v5K96FjwRTWriIUjjdsII3wK1x92H8jdUcWZGVnRw6W0ngIQRcWPh3W6gINwZCX 0A2/CUhMxonZEWi0vXVwMck0LXTOCJ3IoQZhkwxooi/yIxedpQUWMXHuVtNeMgr7pggv 2skVfaFLMNw6wcYT3FgXrXNYJlui7K8GKL5nc=
Received: by 10.236.183.194 with SMTP id q42mr7054628yhm.43.1307413697315; Mon, 06 Jun 2011 19:28:17 -0700 (PDT)
Received: from [10.71.5.29] ([12.68.183.2]) by mx.google.com with ESMTPS id n29sm3648770yhj.68.2011.06.06.19.28.15 (version=SSLv3 cipher=OTHER); Mon, 06 Jun 2011 19:28:16 -0700 (PDT)
Message-ID: <4DED8CB9.4090800@gmail.com>
Date: Tue, 07 Jun 2011 14:28:09 +1200
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: Fred Baker <fred@cisco.com>
References: <4DECB756.1010603@isode.com> <674B45C9-0E00-447E-87D7-8EECB69CE80E@cisco.com> <4DED64FD.1020209@gmail.com> <64814768-703C-4805-B273-F9D2EBE11B7D@cisco.com>
In-Reply-To: <64814768-703C-4805-B273-F9D2EBE11B7D@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-v6ops-6to4-advisory.all@tools.ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-6to4-advisory-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: Tue, 07 Jun 2011 02:28:18 -0000

On 2011-06-07 11:57, Fred Baker wrote:
> On Jun 6, 2011, at 4:38 PM, Brian E Carpenter wrote:
> 
>>>>  [RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
>>>>             via IPv4 Clouds", RFC 3056, February 2001.
>>>>
>>>>  [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
>>>>             RFC 3068, June 2001.
>>> I believe these 2 references need to be Normative, as they are required to understand this document.
>> True, but this is an informational document, so why would any references be normative?
> 
> This is something we spoke about in the working group, and you answered me the same way. I think he's not saying (and I was not saying then) that the references are normative for the Internet. They're saying that, unlike an informative reference (which may give you a deeper understanding but for most of the document are optional reading), you can't understand this document if you don't understand those two.

Correct, but (process weanie hat on) I don't see anything in the discussion of rules
for references in RFC 2026 that requires any such consideration in non-standards track
documents. I don't want to change this unless directed by the IESG.

   Brian

From fred@cisco.com  Mon Jun  6 19:54:56 2011
Return-Path: <fred@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 55BBD11E8090; Mon,  6 Jun 2011 19:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.688
X-Spam-Level: 
X-Spam-Status: No, score=-110.688 tagged_above=-999 required=5 tests=[AWL=-0.089, 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 7wi+kD14SuQD; Mon,  6 Jun 2011 19:54:55 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id E499411E8082; Mon,  6 Jun 2011 19:54:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1400; q=dns/txt; s=iport; t=1307415295; x=1308624895; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=SF4Dll4OZnkI/zt3lVD5e6V5OrBFRj6ym6olzlk+cSs=; b=GADsIVnGbboU0xMCKVxChJuiDBc/fZYe00FRTK4JpN3lxPVwUQVXQkvY yVgnf/AyllczWRfFgsXGnxQb1NITE0CUvem6F8A6iXZBcjD/lWuhDkxjJ +FIZF+JVjR31wK/QxHjfVBlpn9OsfWH8o8NtxGMQ0Lm9fWMjI5WV0JwVh Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAKWS7U2rRDoI/2dsb2JhbABTphh3iHGicp4OhiEEhnWKDoRMixY
X-IronPort-AV: E=Sophos;i="4.65,330,1304294400"; d="scan'208";a="709225967"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-6.cisco.com with ESMTP; 07 Jun 2011 02:54:54 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p572sn7X023321; Tue, 7 Jun 2011 02:54:54 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Mon, 06 Jun 2011 19:54:54 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Mon, 06 Jun 2011 19:54:54 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4DED8CB9.4090800@gmail.com>
Date: Mon, 6 Jun 2011 19:54:38 -0700
Message-Id: <A026384F-91FE-4496-B4C6-4C49B0DAB0C1@cisco.com>
References: <4DECB756.1010603@isode.com> <674B45C9-0E00-447E-87D7-8EECB69CE80E@cisco.com> <4DED64FD.1020209@gmail.com> <64814768-703C-4805-B273-F9D2EBE11B7D@cisco.com> <4DED8CB9.4090800@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: gen-art@ietf.org, draft-ietf-v6ops-6to4-advisory.all@tools.ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-6to4-advisory-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: Tue, 07 Jun 2011 02:54:56 -0000

On Jun 6, 2011, at 7:28 PM, Brian E Carpenter wrote:

> On 2011-06-07 11:57, Fred Baker wrote:
>> On Jun 6, 2011, at 4:38 PM, Brian E Carpenter wrote:
>>=20
>>>>> [RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
>>>>>            via IPv4 Clouds", RFC 3056, February 2001.
>>>>>=20
>>>>> [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay =
Routers",
>>>>>            RFC 3068, June 2001.
>>>> I believe these 2 references need to be Normative, as they are =
required to understand this document.
>>> True, but this is an informational document, so why would any =
references be normative?
>>=20
>> This is something we spoke about in the working group, and you =
answered me the same way. I think he's not saying (and I was not saying =
then) that the references are normative for the Internet. They're saying =
that, unlike an informative reference (which may give you a deeper =
understanding but for most of the document are optional reading), you =
can't understand this document if you don't understand those two.
>=20
> Correct, but (process weanie hat on) I don't see anything in the =
discussion of rules
> for references in RFC 2026 that requires any such consideration in =
non-standards track
> documents. I don't want to change this unless directed by the IESG.

OK, we'll wait for Russ' usual "discuss" saying "do what he said".=

From alexey.melnikov@isode.com  Tue Jun  7 03:10:33 2011
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 97DC411E80CC; Tue,  7 Jun 2011 03:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5SWKOpU-1uzH; Tue,  7 Jun 2011 03:10:33 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 771D8228004; Tue,  7 Jun 2011 03:10:26 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Te34=QA-uScB@rufus.isode.com>; Tue, 7 Jun 2011 11:10:06 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4DEDF8F3.1010308@isode.com>
Date: Tue, 07 Jun 2011 11:09:55 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Fred Baker <fred@cisco.com>
References: <4DECB756.1010603@isode.com> <674B45C9-0E00-447E-87D7-8EECB69CE80E@cisco.com> <4DED64FD.1020209@gmail.com> <64814768-703C-4805-B273-F9D2EBE11B7D@cisco.com>
In-Reply-To: <64814768-703C-4805-B273-F9D2EBE11B7D@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-v6ops-6to4-advisory.all@tools.ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-6to4-advisory-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: Tue, 07 Jun 2011 10:10:33 -0000

Fred Baker wrote:

>On Jun 6, 2011, at 4:38 PM, Brian E Carpenter wrote:
>  
>
>>>> [RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
>>>>            via IPv4 Clouds", RFC 3056, February 2001.
>>>>
>>>> [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
>>>>            RFC 3068, June 2001.
>>>>        
>>>>
>>>I believe these 2 references need to be Normative, as they are required to understand this document.
>>>      
>>>
>>True, but this is an informational document, so why would any references be normative?
>>    
>>
>This is something we spoke about in the working group, and you answered me the same way. I think he's not saying (and I was not saying then) that the references are normative for the Internet. They're saying that, unlike an informative reference (which may give you a deeper understanding but for most of the document are optional reading), you can't understand this document if you don't understand those two.
>
Correct. And that is the definition of a Normative reference.


From alexey.melnikov@isode.com  Tue Jun  7 03:10:34 2011
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 0A039228003; Tue,  7 Jun 2011 03:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 55OwSS+Y3Ted; Tue,  7 Jun 2011 03:10:33 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id F33F911E80E3; Tue,  7 Jun 2011 03:10:26 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Te35BAA-uSsD@rufus.isode.com>; Tue, 7 Jun 2011 11:10:12 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4DEDF8FA.5080506@isode.com>
Date: Tue, 07 Jun 2011 11:10:02 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4DECB756.1010603@isode.com> <674B45C9-0E00-447E-87D7-8EECB69CE80E@cisco.com> <4DED64FD.1020209@gmail.com> <64814768-703C-4805-B273-F9D2EBE11B7D@cisco.com> <4DED8CB9.4090800@gmail.com>
In-Reply-To: <4DED8CB9.4090800@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-v6ops-6to4-advisory.all@tools.ietf.org, Fred Baker <fred@cisco.com>, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-6to4-advisory-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: Tue, 07 Jun 2011 10:10:34 -0000

Brian E Carpenter wrote:

>On 2011-06-07 11:57, Fred Baker wrote:
>  
>
>>On Jun 6, 2011, at 4:38 PM, Brian E Carpenter wrote:
>>
>>    
>>
>>>>> [RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
>>>>>            via IPv4 Clouds", RFC 3056, February 2001.
>>>>>
>>>>> [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
>>>>>            RFC 3068, June 2001.
>>>>>          
>>>>>
>>>>I believe these 2 references need to be Normative, as they are required to understand this document.
>>>>        
>>>>
>>>True, but this is an informational document, so why would any references be normative?
>>>      
>>>
>>This is something we spoke about in the working group, and you answered me the same way. I think he's not saying (and I was not saying then) that the references are normative for the Internet. They're saying that, unlike an informative reference (which may give you a deeper understanding but for most of the document are optional reading), you can't understand this document if you don't understand those two.
>>    
>>
>
>Correct, but (process weanie hat on) I don't see anything in the discussion of rules
>for references in RFC 2026 that requires any such consideration in non-standards track
>documents. I don't want to change this unless directed by the IESG.
>  
>
This is not covered by RFC 2026, it is covered by the IESG statement on 
Normative/Informative references 
<http://www.ietf.org/iesg/statement/normative-informative.html>, which 
reads:

Within an RFC, references to other documents fall into two general 
categories: "normative" and "informative". Normative references specify 
documents that must be read to understand or implement the technology in 
the new RFC, or whose technology must be present for the technology in 
the new RFC to work. An informative reference is not normative; rather, 
it only provides additional information. For example, an informative 
reference might provide background or historical information. 
Informative references are not required to implement the technology in 
the RFC.

[...]

Note 3: The normative/informative distinction is relevant in any 
document that amounts to a technical specification, even if its intended 
status is Experimental or Informational.


From ron.even.tlv@gmail.com  Tue Jun  7 03:56:03 2011
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 96A3B21F84D5; Tue,  7 Jun 2011 03:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 0UlywTFsUoQt; Tue,  7 Jun 2011 03:56:02 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 74E9721F84EB; Tue,  7 Jun 2011 03:56:02 -0700 (PDT)
Received: by qwc23 with SMTP id 23so3557767qwc.31 for <multiple recipients>; Tue, 07 Jun 2011 03:56:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=wiEO+dpxqKaqszSJC/01xghHneWE6gbWRUZf9yzB85U=; b=jxaVft1jReydb1peu3hXFS7I+MJJ6D6xzb/0au1bNutQT2qc3vpixfB1TBMrPVtZoL zfnR1AHpYwjBP21q/O3H0ysaF+H1kQRCmJoamWUULdlysoGbeRlwbIBNyGEr+Bt+wgbU EGK4Lyz3yvSaW+SnLQ5f738TQ47q222FDLKGI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=ECiq55to3FSAD47L/+8bsIYXS8i6O7UVV+mAekjhzUhfjW36AFN+zEQiKhvAMnsJQ2 LkOuozs9V1uUDNRG6srrZYHozRE+Yi3RiKSPl4RME20PMV/BRjoeRO7Rz+5R4dQGmilo DszAagpiGXwrSx0X9/ItkvIyUULCckNGo80+w=
Received: by 10.229.20.210 with SMTP id g18mr4296151qcb.115.1307444161674; Tue, 07 Jun 2011 03:56:01 -0700 (PDT)
Received: from YOUR6108 (user-0ccehtm.cable.mindspring.com [24.199.71.182]) by mx.google.com with ESMTPS id m16sm3497913qck.16.2011.06.07.03.55.59 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Jun 2011 03:55:59 -0700 (PDT)
From: "rontlv" <ron.even.tlv@gmail.com>
To: "'Paul Hoffman'" <paul.hoffman@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org>
In-Reply-To: <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org>
Date: Tue, 7 Jun 2011 13:56:08 +0300
Message-ID: <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acwklte7796Bb4noSxWY8eQukloclgAaX0Mw
Content-Language: he
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 07 Jun 2011 10:56:03 -0000

Hi Paul,

The IANA registry is in
http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml#idnabis-ta
bles-properties
I saw that in the beginning it has as reference RFC 5892 for the whole
table. Will it stay this way after the change proposed in this draft and
just the three individual values will change based on 1.1, 1.2 and 1.3? or
are there no changes in the IANA registry at all. This is unclear to me
according to the section 3 of your draft.

Section 5.1 of RFC5892 says "If non-backward-compatible changes or other
problems arise during the
   creation or designated expert review of the table of derived property
   values, they should be flagged for the IESG." . My question was if the
change is backward compatible. The 5892bis draft does not say it.

Thanks
Roni




> -----Original Message-----
> From: Paul Hoffman [mailto:paul.hoffman@vpnc.org]
> Sent: Tuesday, June 07, 2011 1:13 AM
> To: Roni Even
> Cc: draft-faltstrom-5892bis.all@tools.ietf.org; gen-art@ietf.org;
> 'IETF-Discussion list'
> Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
> 
> On May 29, 2011, at 4:13 AM, Roni Even wrote:
> 
> > Major issues:
> >
> > 1.       I am not sure how the IANA consideration section is in-line
> with the IANA consideration section of RFC5892. Maybe some
> clarification text would be helpful.
> 
> We think that the IANA considerations here are, in fact, what RFC 5892
> was designed for. That is, RFC 5892 says that the registry will be
> updated ("IANA has created a registry with the derived properties for
> the versions of Unicode released after (and including) version 5.2"),
> and this is such an update. Please let me know if that doesn't match
> your understanding.
> 
> > 2.       The IANA registry for derived property value has RFC 5892,
> does this draft want to change the reference, how will it be done.
> 
> Section 2 of the draft is pretty clear here: "No change to RFC 5892 is
> needed based on the changes made in Unicode 6.0".
> 
> >   I think that it relates also to the issue of whether this draft
> updates RFC 5892.
> 
> And here too.
> 
> --Paul Hoffman
> 
> 
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 6185 (20110606) __________
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
> 
 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6186 (20110607) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 


From miguel.a.garcia@ericsson.com  Tue Jun  7 05:07:48 2011
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 5742B21F8472 for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 05:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.372
X-Spam-Level: 
X-Spam-Status: No, score=-6.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 bzVUZqKPWE46 for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 05:07:47 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 191B621F8471 for <gen-art@ietf.org>; Tue,  7 Jun 2011 05:07:46 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c17ae00000262e-5b-4dee14924c09
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id FA.BA.09774.2941EED4; Tue,  7 Jun 2011 14:07:46 +0200 (CEST)
Received: from [159.107.24.207] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.137.0; Tue, 7 Jun 2011 14:07:44 +0200
Message-ID: <4DEE148F.7030506@ericsson.com>
Date: Tue, 7 Jun 2011 14:07:43 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: jeanlouis.leroux@orange-ftgroup.com,  Thomas Morin <thomas.morin@orange-ftgroup.com>, vincent.parfait@orange-ftgroup.com, lufang@cisco.com,  lei.wang@telenor.com, y.kamite@ntt.com, shane@level3.net,  Loa Andersson <loa@pi.nu>, Adrian Farrel <adrian@olddog.co.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-mpls-mp-ldp-reqs-08.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 12:07:48 -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-mp-ldp-reqs-08.txt
Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
Review Date: 2011-06-07
IESG Telechat date: 2011-06-09

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

I reviewed version 07 during the Last Call period, and I had just not so 
important comments. All of them have been successfully addressed.

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

From brian.e.carpenter@gmail.com  Tue Jun  7 07:20:25 2011
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 3ACE011E8132; Tue,  7 Jun 2011 07:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.905
X-Spam-Level: 
X-Spam-Status: No, score=-102.905 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619, 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 aBLClPC0h7re; Tue,  7 Jun 2011 07:20:24 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7861D11E812A; Tue,  7 Jun 2011 07:20:24 -0700 (PDT)
Received: by gyf3 with SMTP id 3so2681946gyf.31 for <multiple recipients>; Tue, 07 Jun 2011 07:20:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=G+6ZcGsa97IHFbjHARwSZ+BxPfy66Xya2ddjdQrUUGo=; b=tYJGIszFcPQ8WNcW38V1284XrDz+cxPaJmifKsM59+rU6qYfChl9Yr/gblSETw9iYm TtZ/ByXgwTdL6pCaM4p8XGstVA08uNSamZa4RWNYrTh50IwtwXSqqwq+udgVAWVTz3K+ ANnmO9AtiuS5tJ65wnziWKLXTCpGkZig72anc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=qVMB7e21xDrBokn4NmICQm3iu2G5FeRKP6AB03Yk0O3RdBnKZ6RpLmyo8YlgpI4yJ3 RH64NnBcMftEQ5CYJ5sAVhf7DxqpB61kWndVf/NUbXVH4DEZBi6L8BTYCzQPPBuKaxdG w5z7RLxrAxSX8Rn3DTExpGDDmkI0czt59/lVM=
Received: by 10.236.200.135 with SMTP id z7mr219529yhn.146.1307456423888; Tue, 07 Jun 2011 07:20:23 -0700 (PDT)
Received: from [10.71.7.161] ([12.68.183.2]) by mx.google.com with ESMTPS id w70sm139563yhl.59.2011.06.07.07.20.22 (version=SSLv3 cipher=OTHER); Tue, 07 Jun 2011 07:20:23 -0700 (PDT)
Message-ID: <4DEE33A3.2000000@gmail.com>
Date: Wed, 08 Jun 2011 02:20:19 +1200
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: Alexey Melnikov <alexey.melnikov@isode.com>
References: <4DECB756.1010603@isode.com> <674B45C9-0E00-447E-87D7-8EECB69CE80E@cisco.com> <4DED64FD.1020209@gmail.com> <64814768-703C-4805-B273-F9D2EBE11B7D@cisco.com> <4DED8CB9.4090800@gmail.com> <4DEDF8FA.5080506@isode.com>
In-Reply-To: <4DEDF8FA.5080506@isode.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-v6ops-6to4-advisory.all@tools.ietf.org, Fred Baker <fred@cisco.com>, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-6to4-advisory-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: Tue, 07 Jun 2011 14:20:25 -0000

On 2011-06-07 22:10, Alexey Melnikov wrote:
> Brian E Carpenter wrote:
> 
>> On 2011-06-07 11:57, Fred Baker wrote:
>>  
>>
>>> On Jun 6, 2011, at 4:38 PM, Brian E Carpenter wrote:
>>>
>>>   
>>>>>> [RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
>>>>>>            via IPv4 Clouds", RFC 3056, February 2001.
>>>>>>
>>>>>> [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
>>>>>>            RFC 3068, June 2001.
>>>>>>         
>>>>> I believe these 2 references need to be Normative, as they are
>>>>> required to understand this document.
>>>>>       
>>>> True, but this is an informational document, so why would any
>>>> references be normative?
>>>>     
>>> This is something we spoke about in the working group, and you
>>> answered me the same way. I think he's not saying (and I was not
>>> saying then) that the references are normative for the Internet.
>>> They're saying that, unlike an informative reference (which may give
>>> you a deeper understanding but for most of the document are optional
>>> reading), you can't understand this document if you don't understand
>>> those two.
>>>   
>>
>> Correct, but (process weanie hat on) I don't see anything in the
>> discussion of rules
>> for references in RFC 2026 that requires any such consideration in
>> non-standards track
>> documents. I don't want to change this unless directed by the IESG.
>>  
>>
> This is not covered by RFC 2026, it is covered by the IESG statement on
> Normative/Informative references
> <http://www.ietf.org/iesg/statement/normative-informative.html>, which
> reads:
> 
> Within an RFC, references to other documents fall into two general
> categories: "normative" and "informative". Normative references specify
> documents that must be read to understand or implement the technology in
> the new RFC, or whose technology must be present for the technology in
> the new RFC to work. An informative reference is not normative; rather,
> it only provides additional information. For example, an informative
> reference might provide background or historical information.
> Informative references are not required to implement the technology in
> the RFC.
> 
> [...]
> 
> Note 3: The normative/informative distinction is relevant in any
> document that amounts to a technical specification, even if its intended
> status is Experimental or Informational.

Dang! You know, I almost remember drafting that Note myself ;-)

Sure, of course I will do what the ADs tell me.

   Brian

From paul.hoffman@vpnc.org  Tue Jun  7 09:38:53 2011
Return-Path: <paul.hoffman@vpnc.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 1FF1711E807A; Tue,  7 Jun 2011 09:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.339
X-Spam-Level: 
X-Spam-Status: No, score=-102.339 tagged_above=-999 required=5 tests=[AWL=0.260, 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 53TZpTebZwSl; Tue,  7 Jun 2011 09:38:52 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id E75A511E8193; Tue,  7 Jun 2011 09:38:51 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p57GcjUe094182 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2011 09:38:46 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
Date: Tue, 7 Jun 2011 09:38:47 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <406033A9-BDB9-406C-84E9-194B1BF7B21C@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
To: rontlv <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 07 Jun 2011 16:38:53 -0000

On Jun 7, 2011, at 3:56 AM, rontlv wrote:

> The IANA registry is in
> =
http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml#idnabis-=
ta
> bles-properties
> I saw that in the beginning it has as reference RFC 5892 for the whole
> table. Will it stay this way after the change proposed in this draft =
and
> just the three individual values will change based on 1.1, 1.2 and =
1.3? or
> are there no changes in the IANA registry at all. This is unclear to =
me
> according to the section 3 of your draft.

The table will likely change, based on the input of the expert reviewer. =
I assume that a reference to this RFC-to-be would be added to the top of =
the table, next to "[RFC5892]". That is, this would be an additional =
reference, not a replacement. But that's up to IANA.

> Section 5.1 of RFC5892 says "If non-backward-compatible changes or =
other
> problems arise during the
>   creation or designated expert review of the table of derived =
property
>   values, they should be flagged for the IESG." . My question was if =
the
> change is backward compatible. The 5892bis draft does not say it.

The draft says:
   This imply the derived property value differs
   depending on whether the property definitions used are from Unicode
   5.2 or 6.0.
We intended that as "non-backwards-compatible"; we can change the =
wording to make that explicit.

--Paul Hoffman


From ron.even.tlv@gmail.com  Tue Jun  7 12:30:45 2011
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 D3EF011E8226; Tue,  7 Jun 2011 12:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 LrcUYX503Q1J; Tue,  7 Jun 2011 12:30:45 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 218C311E821F; Tue,  7 Jun 2011 12:30:44 -0700 (PDT)
Received: by vws12 with SMTP id 12so4897833vws.31 for <multiple recipients>; Tue, 07 Jun 2011 12:30:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=T9qDryzpUn7FCWEm53zONvJ4XGkui3huVr8hLvnDEm4=; b=qqxpj9Llfi0NUc3CbS2Myc/XKC+oVZ4l9FSWlaIGNGjHf6aUFIvKE9QzycBkW8AZGq mRQGv858rZQUNJpigaU16kirgSKfMQvRczXId1VIHbQTKKUlJSK3UVeNhD/pVfBUY/kZ OMEDi+w5tGAv/VxNq829XphewosSE60ivPbD0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=GW9+371tquc6xl4UpP61y4yWfH0oCc6H1bUhVWdoaLtXwB+fwsHjR6qm61iP3TePHi 7YmOh9Uyvvh16CMLUZaKB4NkvHRUYmnsshrvSxdKHpdjUal9rHq4JWX2/DWIRE7DRo34 dQIv3vEqKJ4NbtArmMd5I2bIDNyk2fqK69bWs=
Received: by 10.52.175.129 with SMTP id ca1mr184559vdc.168.1307475042749; Tue, 07 Jun 2011 12:30:42 -0700 (PDT)
Received: from YOUR6108 (user-0ccehtm.cable.mindspring.com [24.199.71.182]) by mx.google.com with ESMTPS id cf7sm223129vdb.14.2011.06.07.12.30.41 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Jun 2011 12:30:41 -0700 (PDT)
From: "rontlv" <ron.even.tlv@gmail.com>
To: "'Paul Hoffman'" <paul.hoffman@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <406033A9-BDB9-406C-84E9-194B1BF7B21C@vpnc.org>
In-Reply-To: <406033A9-BDB9-406C-84E9-194B1BF7B21C@vpnc.org>
Date: Tue, 7 Jun 2011 22:30:40 +0300
Message-ID: <4dee7c61.a75b340a.22ed.1857@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwlMWG4EDYJW5yAR9WCStSlitXx4AAF7Gow
Content-Language: he
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 07 Jun 2011 19:30:46 -0000

Hi Paul,
My understanding that the new value does not replace the current one since
5892bis is not updating rfc5892. So should the IANA registry reflect that
you are not replacing the current value or is my understanding wrong
Roni Even

> -----Original Message-----
> From: Paul Hoffman [mailto:paul.hoffman@vpnc.org]
> Sent: Tuesday, June 07, 2011 7:39 PM
> To: rontlv
> Cc: draft-faltstrom-5892bis.all@tools.ietf.org; gen-art@ietf.org;
> 'IETF-Discussion list'
> Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
> 
> On Jun 7, 2011, at 3:56 AM, rontlv wrote:
> 
> > The IANA registry is in
> > http://www.iana.org/assignments/idnabis-tables/idnabis-
> tables.xml#idnabis-ta
> > bles-properties
> > I saw that in the beginning it has as reference RFC 5892 for the
> whole
> > table. Will it stay this way after the change proposed in this draft
> and
> > just the three individual values will change based on 1.1, 1.2 and
> 1.3? or
> > are there no changes in the IANA registry at all. This is unclear to
> me
> > according to the section 3 of your draft.
> 
> The table will likely change, based on the input of the expert
> reviewer. I assume that a reference to this RFC-to-be would be added to
> the top of the table, next to "[RFC5892]". That is, this would be an
> additional reference, not a replacement. But that's up to IANA.
> 
> > Section 5.1 of RFC5892 says "If non-backward-compatible changes or
> other
> > problems arise during the
> >   creation or designated expert review of the table of derived
> property
> >   values, they should be flagged for the IESG." . My question was if
> the
> > change is backward compatible. The 5892bis draft does not say it.
> 
> The draft says:
>    This imply the derived property value differs
>    depending on whether the property definitions used are from Unicode
>    5.2 or 6.0.
> We intended that as "non-backwards-compatible"; we can change the
> wording to make that explicit.
> 
> --Paul Hoffman
> 
> 
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 6186 (20110607) __________
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
> 
 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6188 (20110607) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 


From paul.hoffman@vpnc.org  Tue Jun  7 14:43:55 2011
Return-Path: <paul.hoffman@vpnc.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 3D87C11E819F; Tue,  7 Jun 2011 14:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.382
X-Spam-Level: 
X-Spam-Status: No, score=-102.382 tagged_above=-999 required=5 tests=[AWL=0.217, 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 pZaeGIemDXVW; Tue,  7 Jun 2011 14:43:54 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3A58E11E8071; Tue,  7 Jun 2011 14:43:53 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p57LhjP3013927 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2011 14:43:45 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
Date: Tue, 7 Jun 2011 14:43:46 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
To: rontlv <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 07 Jun 2011 21:43:55 -0000

On Jun 7, 2011, at 3:56 AM, rontlv wrote:

> The IANA registry is in
> =
http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml#idnabis-=
ta
> bles-properties
> I saw that in the beginning it has as reference RFC 5892 for the whole
> table. Will it stay this way after the change proposed in this draft =
and
> just the three individual values will change based on 1.1, 1.2 and =
1.3? or
> are there no changes in the IANA registry at all. This is unclear to =
me
> according to the section 3 of your draft.
>=20
> Section 5.1 of RFC5892 says "If non-backward-compatible changes or =
other
> problems arise during the
>   creation or designated expert review of the table of derived =
property
>   values, they should be flagged for the IESG." . My question was if =
the
> change is backward compatible. The 5892bis draft does not say it.

Ah, very good catch! My earlier comment about us listing this new RFC in =
the registry is, in fact, wrong.

When we wrote RFC 5892, we said:
   IANA has created a registry with the derived properties for the
   versions of Unicode released after (and including) version 5.2. =20
That's one registry that has the properties for most current version of =
Unicode at any given time. Thus, the registry would be updated *even if* =
we didn't publish 5892bis. We are not updating either 5892, nor the =
registry, by publishing 5892bis. We are simply giving IETF consensus =
advice about what we think the expert reviewer who updates the registry =
should consider.

Our IANA considerations in 5892bis are:
   IANA is to update the derived property value registry according to
   RFC 5892 and property values as defined in The Unicode Standard
   version 6.0.
That might sound like they are initiating the registry update, but they =
really aren't: the update was already specified in 5892. We can change =
the IANA considerations to reflect that:
   IANA will update the derived property value registry according to
   RFC 5892 and property values as defined in The Unicode Standard
   version 6.0, regardless of the content of this RFC.

--Paul Hoffman


From suresh.krishnan@ericsson.com  Tue Jun  7 15:31:07 2011
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 49EE111E8078 for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 15:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K4zgzIYg8-UG for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 15:31:06 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC9111E8072 for <gen-art@ietf.org>; Tue,  7 Jun 2011 15:31:06 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p57MV4ss029002 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 7 Jun 2011 17:31:05 -0500
Received: from [142.133.10.107] (147.117.20.214) by eusaamw0712.eamcs.ericsson.se (147.117.20.182) with Microsoft SMTP Server id 8.3.137.0; Tue, 7 Jun 2011 18:31:04 -0400
Message-ID: <4DEEA636.4000208@ericsson.com>
Date: Tue, 7 Jun 2011 18:29:10 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-sieve-external-lists.all@tools.ietf.org
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-sieve-external-lists-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 22:31:07 -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-sieve-external-lists-09
Reviewer: Suresh Krishnan
Review Date: 2011/06/07
IESG Telechat date: 2011/06/09

Summary: This draft is ready for publication as a Proposed Standard but
it has a minor issue.

Minor
=====

* Section 2.2:

This following text is a bit handwavy. Is this by design? How can the 
sieve implementation identify the list as one that has an open 
subscriber list. Is the sieve engine expected to try one of these 
methods first and failover into another. Is there an expectation that 
all sieve implementations will actually be capable of invoking both 
these mechanisms?

"For some lists, the Sieve engine might directly retrieve the list and
make its own comparison.  Other lists might not work that way -- they
might provide a way to ask if a value is in the list, but not permit
retrieval of the list itself."

Thanks
Suresh












From ben@nostrum.com  Tue Jun  7 15:35:14 2011
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 5D58D11E80FF; Tue,  7 Jun 2011 15:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.15
X-Spam-Level: 
X-Spam-Status: No, score=-101.15 tagged_above=-999 required=5 tests=[AWL=-0.850, BAYES_00=-2.599, MANGLED_LIST=2.3, 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 sLm1j8I7Ouvx; Tue,  7 Jun 2011 15:35:14 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5D9A411E8072; Tue,  7 Jun 2011 15:35:13 -0700 (PDT)
Received: from [10.0.1.6] (cpe-76-187-75-59.tx.res.rr.com [76.187.75.59]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p57MZ9iq062444 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2011 17:35:11 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 7 Jun 2011 17:35:10 -0500
Message-Id: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com>
To: draft-ietf-dnsext-rfc2672bis-dname.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 76.187.75.59 is authenticated by a trusted mechanism)
Cc: The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 22:35:14 -0000

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

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

Document: draft-ietf-dnsext-rfc2672bis-dname-22
Reviewer: Ben Campbell
Review Date: 2011-06-07
IETF LC End Date:2011-06-09
IESG Telechat date: (if known)

Summary:

This draft does not seem to be quite ready for publication, in that it =
professes to obsolete RFC 2672, but does not cover all the material from =
that RFC or explain the absence of the missing material. I also have a =
few editorial comments that should be considered prior to final =
publication.

Major issues:

This draft professes to obsolete RFC2672, but there are multiple =
sections of that RFC that are not replicated here, nor are their absence =
explained. I assume, since this draft obsoletes RFC2672, it is expected =
to completely replace it where an implementor would no longer be =
expected to read 2672.

-- section 4.2 of RFC2672, "Processing by Resolvers", is not replicated =
here, or if it is, it's in a substantially different form.=20

-- section 5, "examples of use" is not replicated here. Similar examples =
are mentioned in the introduction, but the detail is removed.

None

Minor issues:

None

Nits/editorial comments:

-- IDNits has some comments, please check.

-- Abstract: "This is a revision of the original specification in RFC =
2672, also aligning RFC 3363 and RFC 4294 with this revision."

The heading says this obsoletes 2672 and updates the other two. It's =
probably worth explicitly using those words here.

-- 3.1, 1st paragraph: "Relevant includes the following cases:"

Awkward sentence. Maybe "Relevant cases include the following:"?

-- 3.1, 5th paragraph: "is synthesized and included in the answer =
section"

What synthesized it? The server? (passive voice obscures responsibility)=20=


-- ... "The DNAME has an RRSIG"

A _signed_ DNAME has an RRSIG, right?

-- 4, 4th paragraph: "...should be revised..."

This document actually executes the revision, right? Better to say "this =
document revises..." rather than "should be revised"

-- ..., 7th paragraph: "...replaced with the word "DELETED"."

Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?


From barryleiba@gmail.com  Tue Jun  7 15:36:23 2011
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 7045711E8101 for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 15:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[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 olS2w8GkR9Tv for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 15:36:23 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id E461C11E8072 for <gen-art@ietf.org>; Tue,  7 Jun 2011 15:36:22 -0700 (PDT)
Received: by gxk19 with SMTP id 19so2955940gxk.31 for <gen-art@ietf.org>; Tue, 07 Jun 2011 15:36:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=76qIK6ygx1W5suA38PRcP4GmT5eTEUFo6pbgga3jfck=; b=pOXyKP8SRbGwFSq5gCCQ0sJMJLk+lM5zaL/HDkXuEzxyBwNYACGhFzSpGfPiAKeGPt XVkTQDjR9VCzpgjSAqb4SLYhGJEhJbWIHBAP06fjzY7T1gDIk2bI32dZhp5ddAPGAM3U bMCeQX92ZMKmJEb+nkou/lY9COErGHRk5PNv0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=J4nnxQBWGs7tV0I/nh8De3K7khOH8TZfm1Vy/Ym17f6iok0v10A4fIqio1iWle3IDH Mg3zaJPgGQQ0HG7/M9mIe0GUexEjcfcbEgS+VvcXoF5wwm3kavKqFYAQg9Qg3tMreumv vvG7m99WXV+QDa/XOTWPU4d3jnwaAorozs+30=
MIME-Version: 1.0
Received: by 10.236.184.71 with SMTP id r47mr1308078yhm.190.1307486182253; Tue, 07 Jun 2011 15:36:22 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.236.42.200 with HTTP; Tue, 7 Jun 2011 15:36:22 -0700 (PDT)
In-Reply-To: <4DEEA636.4000208@ericsson.com>
References: <4DEEA636.4000208@ericsson.com>
Date: Tue, 7 Jun 2011 18:36:22 -0400
X-Google-Sender-Auth: QbSLRu6qELjxu_u_2yQJpiobjoA
Message-ID: <BANLkTimfkBUOu60=xorZ=VRfqY_zB_hsRQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-sieve-external-lists.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-sieve-external-lists-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 22:36:23 -0000

Thanks, Suresh, for the review.

> This following text is a bit handwavy. Is this by design? How can the sie=
ve
> implementation identify the list as one that has an open subscriber list.=
 Is
> the sieve engine expected to try one of these methods first and failover
> into another. Is there an expectation that all sieve implementations will
> actually be capable of invoking both these mechanisms?
>
> "For some lists, the Sieve engine might directly retrieve the list and
> make its own comparison. =A0Other lists might not work that way -- they
> might provide a way to ask if a value is in the list, but not permit
> retrieval of the list itself."

Yes, it's vague by design.  The Sieve engine needs to be integrated
with the list handling -- this is saying that for some that's done
simply by having the Sieve engine retrieve the list and search it, but
for other lists it's done through some sort of API by which it
searches the list.  In any case, the Sieve engine needs to know how to
access each list that it supports... and that access is out of scope
here.

Barry

From suresh.krishnan@ericsson.com  Tue Jun  7 15:53:29 2011
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 BB54B11E81AE for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 15:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.2
X-Spam-Level: 
X-Spam-Status: No, score=-106.2 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, 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 JN8hBKLUe4Ab for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 15:53:27 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id ECBC011E80CF for <gen-art@ietf.org>; Tue,  7 Jun 2011 15:53:26 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p57MrPnL012352; Tue, 7 Jun 2011 17:53:27 -0500
Received: from [142.133.10.107] (147.117.20.214) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.3.137.0; Tue, 7 Jun 2011 18:53:19 -0400
Message-ID: <4DEEAB6D.7060407@ericsson.com>
Date: Tue, 7 Jun 2011 18:51:25 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-l3vpn-ibgp.all@tools.ietf.org
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art]  Gen-ART Telechat review of draft-ietf-l3vpn-ibgp-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, 07 Jun 2011 22:53:29 -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-l3vpn-ibgp-07
Reviewer: Suresh Krishnan
Review Date: 2011/06/07
IESG Telechat date: 2011/06/09

Summary: This draft is ready for publication as a Proposed Standard but
it has two minor issues.

Minor
=====

* Section 5

Since the Extended Length bit is not being set in the Attribute Flags, 
the Length can only be 1 octet (as opposed to 1 or 2 octets as shown in 
the figure right? This needs to be clarified.

* Security Considerations

Since the ATTR_SET can contain arbitrary customer attributes, is it 
possible that a set of customers can perform a memory exhaustion attack 
on the PE routers? I understand the same can occur when the customer is 
using communities but I think it is worth mentioning.

Thanks
Suresh

From pedro.r.marques@gmail.com  Tue Jun  7 16:16:01 2011
Return-Path: <pedro.r.marques@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 D181311E808A for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 16:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level: 
X-Spam-Status: No, score=-2.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 uiAM3RK8-c2F for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 16:16:01 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id F1A6111E8071 for <gen-art@ietf.org>; Tue,  7 Jun 2011 16:16:00 -0700 (PDT)
Received: by iyn15 with SMTP id 15so6433910iyn.31 for <gen-art@ietf.org>; Tue, 07 Jun 2011 16:16:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=qsc5CzFa4vcyGDCew4V3wpB5X2vqHOvcktoq5btFG8I=; b=D/g/g9Hpjia/iGegorFItDmNAIE5In7tVs8jq63emglRTND7fKd7U/tcqejPyTO32s P0k1cSa3J3LWEYSJF5444dxNaFyjtMh8GgbLECQ21gztO7n0OWZFXLTgzMsRlnP3Ktfk Lb6oSs2gWm4UNjGVZ9Q+ahpJovrOxun+VL5JM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=coKexaha/T3exBgWdJNe7uYXMI4KMI2swF6UnMYmWRph9DIpL107k62LyIn8GSXCwV ttyBPGSZDQKSVbNqte3dPzbmhfiSfxjjAvixLdVxNk+04/fQmAykNQWgUfMJj69u7qSS LomFTx1LSrx3qDEjEcFJFv9uEE5OuZNA/p9ZY=
MIME-Version: 1.0
Received: by 10.43.59.140 with SMTP id wo12mr10019782icb.408.1307488559747; Tue, 07 Jun 2011 16:15:59 -0700 (PDT)
Received: by 10.42.164.8 with HTTP; Tue, 7 Jun 2011 16:15:59 -0700 (PDT)
In-Reply-To: <4DEEAB6D.7060407@ericsson.com>
References: <4DEEAB6D.7060407@ericsson.com>
Date: Tue, 7 Jun 2011 16:15:59 -0700
Message-ID: <BANLkTinG96r2_5i-LRD2hL+5t58jaLuP4RRJbMKMvtduBecP-A@mail.gmail.com>
From: Pedro Marques <pedro.r.marques@gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Tue, 07 Jun 2011 16:26:45 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-l3vpn-ibgp.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-l3vpn-ibgp-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, 07 Jun 2011 23:16:02 -0000

Suresh,
Thank you for the review.

Regarding Section 5:
The Length can be either 1 or 2 octets. 4271 defines Attr Flags.
Bit 0 is the Optional bit; Bit 1 is the Transitive bit;  Bit 3 is the
Extended length bit.

This document specified that bits 0 and 1 must be set to 1 (Optional +
transitive). The Extended length bit must be set according to the
attribute payload as per 4271.

The convention is the same as for any other BGP attribute.

I'll add a clarification to this effect.

Regarding security considerations:
- The resource management considerations exist regarding routes as
well as attributes, with or without this specification. I don't mind
highlighting it, if you believe that improves the specification.

thanks,
  Pedro.

On Tue, Jun 7, 2011 at 3:51 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-ietf-l3vpn-ibgp-07
> Reviewer: Suresh Krishnan
> Review Date: 2011/06/07
> IESG Telechat date: 2011/06/09
>
> Summary: This draft is ready for publication as a Proposed Standard but
> it has two minor issues.
>
> Minor
> =====
>
> * Section 5
>
> Since the Extended Length bit is not being set in the Attribute Flags, the
> Length can only be 1 octet (as opposed to 1 or 2 octets as shown in the
> figure right? This needs to be clarified.
>
> * Security Considerations
>
> Since the ATTR_SET can contain arbitrary customer attributes, is it possible
> that a set of customers can perform a memory exhaustion attack on the PE
> routers? I understand the same can occur when the customer is using
> communities but I think it is worth mentioning.
>
> Thanks
> Suresh
>

From john-ietf@jck.com  Tue Jun  7 18:24:25 2011
Return-Path: <john-ietf@jck.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 E732B11E8154; Tue,  7 Jun 2011 18:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4t287JLDcAfZ; Tue,  7 Jun 2011 18:24:25 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 2703B11E80FE; Tue,  7 Jun 2011 18:24:25 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QU7VI-0003I2-K4; Tue, 07 Jun 2011 21:24:16 -0400
Date: Tue, 07 Jun 2011 21:24:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, rontlv <ron.even.tlv@gmail.com>
Message-ID: <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM>
In-Reply-To: <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 08 Jun 2011 01:24:26 -0000

--On Tuesday, June 07, 2011 14:43 -0700 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

>> Section 5.1 of RFC5892 says "If non-backward-compatible
>> changes or other problems arise during the
>>   creation or designated expert review of the table of
>>   derived property values, they should be flagged for the
>>   IESG." . My question was if the change is backward
>> compatible. The 5892bis draft does not say it.
> 
> Ah, very good catch! My earlier comment about us listing this
> new RFC in the registry is, in fact, wrong.
> 
> When we wrote RFC 5892, we said:
>    IANA has created a registry with the derived properties for
> the    versions of Unicode released after (and including)
> version 5.2.   

> That's one registry that has the properties for
> most current version of Unicode at any given time. Thus, the
> registry would be updated *even if* we didn't publish 5892bis.
> We are not updating either 5892, nor the registry, by
> publishing 5892bis. We are simply giving IETF consensus advice
> about what we think the expert reviewer who updates the
> registry should consider.
> 
> Our IANA considerations in 5892bis are:
>    IANA is to update the derived property value registry
> according to    RFC 5892 and property values as defined in The
> Unicode Standard    version 6.0.

> That might sound like they are initiating the registry update,
> but they really aren't: the update was already specified in
> 5892. We can change the IANA considerations to reflect that:

> IANA will update the derived property value registry according
> to    RFC 5892 and property values as defined in The Unicode
> Standard    version 6.0, regardless of the content of this RFC.

Paul,

I think this is an improvement but there is one issue about
which we have slightly different impressions.   I hope the
difference can be resolved without needing yet more tedious
arguments about documentation.  Indeed, if such arguments are
required, I'd prefer that we just forget about it.

Anyway, your comments above about "most current version" imply
to me that IANA should keep derived property tables for the most
current version only.  My expectation when 5982 was completed
was that IANA was expected to keep derived property tables,
clearly identified by version, for each and every Unicode
version from 5.2 forward.  In other words, the tables for the
[most] current version would be added to, not replace, whatever
previous version tables were around.  The reasons for this, in
terms of systems and implementations in various stages of
development, implementation, and deployment, seem obvious... but
maybe it was too obvious to some of us at the time to get the
wording exactly right.

     john


From paul.hoffman@vpnc.org  Tue Jun  7 19:45:55 2011
Return-Path: <paul.hoffman@vpnc.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 78D5721F84FA; Tue,  7 Jun 2011 19:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, 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 KvrIiajBvDBN; Tue,  7 Jun 2011 19:45:54 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id E62C421F84F1; Tue,  7 Jun 2011 19:45:43 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p582jaN4027228 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2011 19:45:37 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM>
Date: Tue, 7 Jun 2011 19:45:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org> <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 08 Jun 2011 02:45:55 -0000

On Jun 7, 2011, at 6:24 PM, John C Klensin wrote:

> I think this is an improvement but there is one issue about
> which we have slightly different impressions.   I hope the
> difference can be resolved without needing yet more tedious
> arguments about documentation.  Indeed, if such arguments are
> required, I'd prefer that we just forget about it.
>=20
> Anyway, your comments above about "most current version" imply
> to me that IANA should keep derived property tables for the most
> current version only.  My expectation when 5982 was completed
> was that IANA was expected to keep derived property tables,
> clearly identified by version, for each and every Unicode
> version from 5.2 forward.  In other words, the tables for the
> [most] current version would be added to, not replace, whatever
> previous version tables were around.  The reasons for this, in
> terms of systems and implementations in various stages of
> development, implementation, and deployment, seem obvious... but
> maybe it was too obvious to some of us at the time to get the
> wording exactly right.

While your interpretation could be one thing we might have meant, it is =
not what is reflected in the RFC or the registry. RFC 5892 says:

5.1.  IDNA-Derived Property Value Registry

   IANA has created a registry with the derived properties for the
   versions of Unicode released after (and including) version 5.2.  The
   derived property value is to be calculated in cooperation with a
   designated expert [RFC5226] according to the specifications in
   Sections 2 and 3 and not by copying the non-normative table found in
   Appendix B.

   If non-backward-compatible changes or other problems arise during the
   creation or designated expert review of the table of derived property
   values, they should be flagged for the IESG.  Changes to the rules
   (as specified in Sections 2 and 3), including BackwardCompatible
   (Section 2.7) (a set that is at release of this document is empty)
   require IETF Review, as described in RFC 5226 [RFC5226].

Note that every reference to the registry is singular. Also, the =
registry at =
<http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml> =
doesn't mention "5.2" at all.

If the registry definition does not talk about keeping versions, and the =
registry itself doesn't look like it tried, it may be implausible to =
think that IANA would just start to do so in some future. To me, "a =
registry" means a single registry.

--Paul Hoffman


From kathleen.moriarty@emc.com  Tue Jun  7 20:26:35 2011
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 240F211E8078; Tue,  7 Jun 2011 20:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NYeC+zw6dfrb; Tue,  7 Jun 2011 20:26:34 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 6D7F811E80A1; Tue,  7 Jun 2011 20:26:33 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p583PqkM012726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jun 2011 23:25:56 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Tue, 7 Jun 2011 23:25:45 -0400
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p583CmYR010742; Tue, 7 Jun 2011 23:12:48 -0400
Received: from mx06a.corp.emc.com ([169.254.1.35]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Tue, 7 Jun 2011 23:12:31 -0400
From: <kathleen.moriarty@emc.com>
To: <gen-art@ietf.org>, <draft-ietf-ccamp-gmpls-vcat-lcas.all@tools.ietf.org>
Date: Tue, 7 Jun 2011 23:12:46 -0400
Thread-Topic: Gen-ART Review of draft-ietf-ccamp-gmpls-vcat-lcas-13
Thread-Index: AcwlifDJA02LvIUmTaytRRieWDyXtg==
Message-ID: <AE31510960917D478171C79369B660FA0DBBD21060@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: diego.caviglia@marconi.com, hhelvoort@huawei.com, rabbat@alum.mit.edu, gregb@grotto-networking.com, ietf@ietf.org
Subject: [Gen-art] Gen-ART Review of draft-ietf-ccamp-gmpls-vcat-lcas-13
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, 08 Jun 2011 03:26:35 -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-ccamp-gmpls-vcat-lcas
Reviewer: Kathleen Moriarty
Review Date: June 7, 2011
IETF LC End Date:
IESG Telechat date: (if known)

Summary:  The document is ready with nits listed below.

Major issues:

Minor issues:

Nits/editorial comments:

Consider breaking the first sentence of the abstract into two sentences.
From: This document describes requirements for, and use of, the
   Generalized Multi-Protocol Label Switching (GMPLS) control plane in
   support of the Virtual Concatenation (VCAT) layer 1 inverse
   multiplexing data plane mechanism and its companion Link Capacity
   Adjustment Scheme (LCAS) which can be used for hitless dynamic
   resizing of the inverse multiplex group.

To: This document describes requirements for, and use of, the
   Generalized Multi-Protocol Label Switching (GMPLS) control plane in
   support of the Virtual Concatenation (VCAT) layer 1 inverse
   multiplexing data plane mechanism and its companion Link Capacity
   Adjustment Scheme (LCAS).  The LCAS can be used for hitless dynamic
   resizing of the inverse multiplex group.


Consider changing the dashes to commas in the paragraph before section 2.4:
From: Identification of the VCG and its associated members. This
       provides information that allows the endpoints to differentiate
       multiple VCGs and to tell what members - label switched paths
       (LSPs)- to associate with a particular VCG.
To: Identification of the VCG and its associated members. This
       provides information that allows the endpoints to differentiate
       multiple VCGs and to tell what member, label switched paths
       (LSPs), to associate with a particular VCG.

Section 3:  There is a mix of dashes and double dashes used at the start of=
 definitions.  Please make the usage consistent (the last one only has one =
dash).  Consider a : instead of double dashes.

Last sentence before section 4:

Add a comma:
From: SONET VCAT group) which is composed of 7 virtually concatenated VC-
   4s (or STS-3c).
To:     SONET VCAT group), which is composed of 7 virtually concatenated VC=
-
   4s (or STS-3c).


Consider breaking the last sentence of the second to last paragraph of Sect=
ion 4.2 up into multiple sentences:
"A node that receives a Path
   message that contains changed fields will process the full Path
   message and, based on the new value of NVC, it will add a component
   signal to the VCAT group, and switch the new timeslot based on the
   new label information."

There is a stray "." Before the last sentence of section 5 and the sentence=
 is indented and I don't think that was intentional.
"          . Conceptual containment relationship between VCG, VCAT
   calls, control plane LSPs, and data plane connections."

Section 5.1, last bullet is another definition, look for consistency in how=
 they are formatted.



_______________________________________________
Gen-art mailing list
Gen-art@ietf.org<mailto:Gen-art@ietf.org>
https://www.ietf.org/mailman/listinfo/gen-art




From vint@google.com  Tue Jun  7 21:08:28 2011
Return-Path: <vint@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 59A8E11E8093 for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 21:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 QKJAEPuMe0xr for <gen-art@ietfa.amsl.com>; Tue,  7 Jun 2011 21:08:27 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 19C5411E807D for <gen-art@ietf.org>; Tue,  7 Jun 2011 21:08:26 -0700 (PDT)
Received: from hpaq11.eem.corp.google.com (hpaq11.eem.corp.google.com [172.25.149.11]) by smtp-out.google.com with ESMTP id p5848PLW006530 for <gen-art@ietf.org>; Tue, 7 Jun 2011 21:08:26 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307506106; bh=RHod9YhkiCqFB7aqNJeoDJChIqQ=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=TEQA45X6thDe86ukUXoT6ZhlhzYpnYiMmy+eVrdN75mxY21T1GbkA4JB8vSUYqHr5 aOejuwEUIaWu61XjmMX/w==
Received: from qyj19 (qyj19.prod.google.com [10.241.83.83]) by hpaq11.eem.corp.google.com with ESMTP id p5847ruJ013837 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <gen-art@ietf.org>; Tue, 7 Jun 2011 21:08:24 -0700
Received: by qyj19 with SMTP id 19so1996749qyj.16 for <gen-art@ietf.org>; Tue, 07 Jun 2011 21:08:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=h6PhemJ6yOrLTYNPLImApqCFdo2TixipzbaBvQGYMIw=; b=P15y/JB/C+4oZTWy7UDxjyaOlolq7IxOFwZlSqWP/JsATOCUlh2jsU+++MQGtQdU7X 7G2RyX38lnxiS1g6Q4sQ==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QYUMtIUuODpGJ4/MJH1bzusLtVkrKBGTCJZRaAIN8iniU5sL1AKAaDAJpoAxd98Yxn SZYltEynZFSwI/k1CltQ==
MIME-Version: 1.0
Received: by 10.229.251.13 with SMTP id mq13mr5169877qcb.36.1307506102789; Tue, 07 Jun 2011 21:08:22 -0700 (PDT)
Received: by 10.229.7.20 with HTTP; Tue, 7 Jun 2011 21:08:22 -0700 (PDT)
In-Reply-To: <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org> <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM> <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
Date: Wed, 8 Jun 2011 00:08:22 -0400
Message-ID: <BANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com>
From: Vint Cerf <vint@google.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=00163630f39bcc672904a52b7c46
X-System-Of-Record: true
Cc: John C Klensin <john-ietf@jck.com>, gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 08 Jun 2011 04:08:28 -0000

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

setting aside interpretation and semantics for a moment, would there be
utility in maintaining tables for each instance of Unicode?

v


On Tue, Jun 7, 2011 at 10:45 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On Jun 7, 2011, at 6:24 PM, John C Klensin wrote:
>
> > I think this is an improvement but there is one issue about
> > which we have slightly different impressions.   I hope the
> > difference can be resolved without needing yet more tedious
> > arguments about documentation.  Indeed, if such arguments are
> > required, I'd prefer that we just forget about it.
> >
> > Anyway, your comments above about "most current version" imply
> > to me that IANA should keep derived property tables for the most
> > current version only.  My expectation when 5982 was completed
> > was that IANA was expected to keep derived property tables,
> > clearly identified by version, for each and every Unicode
> > version from 5.2 forward.  In other words, the tables for the
> > [most] current version would be added to, not replace, whatever
> > previous version tables were around.  The reasons for this, in
> > terms of systems and implementations in various stages of
> > development, implementation, and deployment, seem obvious... but
> > maybe it was too obvious to some of us at the time to get the
> > wording exactly right.
>
> While your interpretation could be one thing we might have meant, it is not
> what is reflected in the RFC or the registry. RFC 5892 says:
>
> 5.1.  IDNA-Derived Property Value Registry
>
>   IANA has created a registry with the derived properties for the
>    versions of Unicode released after (and including) version 5.2.  The
>   derived property value is to be calculated in cooperation with a
>   designated expert [RFC5226] according to the specifications in
>   Sections 2 and 3 and not by copying the non-normative table found in
>   Appendix B.
>
>   If non-backward-compatible changes or other problems arise during the
>   creation or designated expert review of the table of derived property
>    values, they should be flagged for the IESG.  Changes to the rules
>   (as specified in Sections 2 and 3), including BackwardCompatible
>   (Section 2.7) (a set that is at release of this document is empty)
>   require IETF Review, as described in RFC 5226 [RFC5226].
>
> Note that every reference to the registry is singular. Also, the registry
> at <http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml>
> doesn't mention "5.2" at all.
>
> If the registry definition does not talk about keeping versions, and the
> registry itself doesn't look like it tried, it may be implausible to think
> that IANA would just start to do so in some future. To me, "a registry"
> means a single registry.
>
> --Paul Hoffman
>
>

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

setting aside interpretation and semantics for a moment, would there be uti=
lity in maintaining tables for each instance of Unicode?<div><br></div><div=
>v</div><div><br><br><div class=3D"gmail_quote">On Tue, Jun 7, 2011 at 10:4=
5 PM, Paul Hoffman <span dir=3D"ltr">&lt;<a href=3D"mailto:paul.hoffman@vpn=
c.org">paul.hoffman@vpnc.org</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;"><div class=3D"im">On Jun 7, 2011, at 6:24 P=
M, John C Klensin wrote:<br>
<br>
&gt; I think this is an improvement but there is one issue about<br>
&gt; which we have slightly different impressions. =A0 I hope the<br>
&gt; difference can be resolved without needing yet more tedious<br>
&gt; arguments about documentation. =A0Indeed, if such arguments are<br>
&gt; required, I&#39;d prefer that we just forget about it.<br>
&gt;<br>
&gt; Anyway, your comments above about &quot;most current version&quot; imp=
ly<br>
&gt; to me that IANA should keep derived property tables for the most<br>
&gt; current version only. =A0My expectation when 5982 was completed<br>
&gt; was that IANA was expected to keep derived property tables,<br>
&gt; clearly identified by version, for each and every Unicode<br>
&gt; version from 5.2 forward. =A0In other words, the tables for the<br>
&gt; [most] current version would be added to, not replace, whatever<br>
&gt; previous version tables were around. =A0The reasons for this, in<br>
&gt; terms of systems and implementations in various stages of<br>
&gt; development, implementation, and deployment, seem obvious... but<br>
&gt; maybe it was too obvious to some of us at the time to get the<br>
&gt; wording exactly right.<br>
<br>
</div>While your interpretation could be one thing we might have meant, it =
is not what is reflected in the RFC or the registry. RFC 5892 says:<br>
<br>
5.1. =A0IDNA-Derived Property Value Registry<br>
<div class=3D"im"><br>
 =A0 IANA has created a registry with the derived properties for the<br>
</div> =A0 versions of Unicode released after (and including) version 5.2. =
=A0The<br>
 =A0 derived property value is to be calculated in cooperation with a<br>
 =A0 designated expert [RFC5226] according to the specifications in<br>
 =A0 Sections 2 and 3 and not by copying the non-normative table found in<b=
r>
 =A0 Appendix B.<br>
<div class=3D"im"><br>
 =A0 If non-backward-compatible changes or other problems arise during the<=
br>
 =A0 creation or designated expert review of the table of derived property<=
br>
</div> =A0 values, they should be flagged for the IESG. =A0Changes to the r=
ules<br>
 =A0 (as specified in Sections 2 and 3), including BackwardCompatible<br>
 =A0 (Section 2.7) (a set that is at release of this document is empty)<br>
 =A0 require IETF Review, as described in RFC 5226 [RFC5226].<br>
<br>
Note that every reference to the registry is singular. Also, the registry a=
t &lt;<a href=3D"http://www.iana.org/assignments/idnabis-tables/idnabis-tab=
les.xml" target=3D"_blank">http://www.iana.org/assignments/idnabis-tables/i=
dnabis-tables.xml</a>&gt; doesn&#39;t mention &quot;5.2&quot; at all.<br>

<br>
If the registry definition does not talk about keeping versions, and the re=
gistry itself doesn&#39;t look like it tried, it may be implausible to thin=
k that IANA would just start to do so in some future. To me, &quot;a regist=
ry&quot; means a single registry.<br>

<font color=3D"#888888"><br>
--Paul Hoffman<br>
<br>
</font></blockquote></div><br></div>

--00163630f39bcc672904a52b7c46--

From alexey.melnikov@isode.com  Wed Jun  8 04:50:36 2011
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 6B132228010; Wed,  8 Jun 2011 04:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.126
X-Spam-Level: 
X-Spam-Status: No, score=-102.126 tagged_above=-999 required=5 tests=[AWL=0.472, 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 MBLSBQJe1OEU; Wed,  8 Jun 2011 04:50:35 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 6B24311E8081; Wed,  8 Jun 2011 04:50:34 -0700 (PDT)
Received: from [188.28.88.132] (188.28.88.132.threembb.co.uk [188.28.88.132])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Te9iBAA-uZZV@rufus.isode.com>; Wed, 8 Jun 2011 12:50:31 +0100
Message-ID: <4DEF61F1.6040502@isode.com>
Date: Wed, 08 Jun 2011 12:50:09 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Vint Cerf <vint@google.com>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org> <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM> <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org> <BANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com>
In-Reply-To: <BANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------020800040609000909040608"
Cc: IETF-Discussion list <ietf@ietf.org>, gen-art@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, John C Klensin <john-ietf@jck.com>, draft-faltstrom-5892bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 08 Jun 2011 11:50:36 -0000

This is a multi-part message in MIME format.
--------------020800040609000909040608
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Vint Cerf wrote:

> setting aside interpretation and semantics for a moment, would there 
> be utility in maintaining tables for each instance of Unicode?

Yes, because developers will have different versions of Unicode 
available to them. It would also help developers to migrate by seeing 
what has changed between versions.

> v
>
> On Tue, Jun 7, 2011 at 10:45 PM, Paul Hoffman <paul.hoffman@vpnc.org 
> <mailto:paul.hoffman@vpnc.org>> wrote:
>
>     On Jun 7, 2011, at 6:24 PM, John C Klensin wrote:
>
>     > I think this is an improvement but there is one issue about
>     > which we have slightly different impressions.   I hope the
>     > difference can be resolved without needing yet more tedious
>     > arguments about documentation.  Indeed, if such arguments are
>     > required, I'd prefer that we just forget about it.
>     >
>     > Anyway, your comments above about "most current version" imply
>     > to me that IANA should keep derived property tables for the most
>     > current version only.  My expectation when 5982 was completed
>     > was that IANA was expected to keep derived property tables,
>     > clearly identified by version, for each and every Unicode
>     > version from 5.2 forward.  In other words, the tables for the
>     > [most] current version would be added to, not replace, whatever
>     > previous version tables were around.  The reasons for this, in
>     > terms of systems and implementations in various stages of
>     > development, implementation, and deployment, seem obvious... but
>     > maybe it was too obvious to some of us at the time to get the
>     > wording exactly right.
>
>     While your interpretation could be one thing we might have meant,
>     it is not what is reflected in the RFC or the registry. RFC 5892 says:
>
>     5.1.  IDNA-Derived Property Value Registry
>
>       IANA has created a registry with the derived properties for the
>       versions of Unicode released after (and including) version 5.2.  The
>       derived property value is to be calculated in cooperation with a
>       designated expert [RFC5226] according to the specifications in
>       Sections 2 and 3 and not by copying the non-normative table found in
>       Appendix B.
>
>       If non-backward-compatible changes or other problems arise
>     during the
>       creation or designated expert review of the table of derived
>     property
>       values, they should be flagged for the IESG.  Changes to the rules
>       (as specified in Sections 2 and 3), including BackwardCompatible
>       (Section 2.7) (a set that is at release of this document is empty)
>       require IETF Review, as described in RFC 5226 [RFC5226].
>
>     Note that every reference to the registry is singular. Also, the
>     registry at
>     <http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml>
>     doesn't mention "5.2" at all.
>
>     If the registry definition does not talk about keeping versions,
>     and the registry itself doesn't look like it tried, it may be
>     implausible to think that IANA would just start to do so in some
>     future. To me, "a registry" means a single registry.
>
>     --Paul Hoffman
>


--------------020800040609000909040608
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Vint Cerf wrote:<br>
<blockquote cite="midBANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com"
 type="cite">setting aside interpretation and semantics for a moment,
would there be utility in maintaining tables for each instance of
Unicode?</blockquote>
Yes, because developers will have different versions of Unicode
available to them. It would also help developers to migrate by seeing
what has changed between versions.<br>
<blockquote cite="midBANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com"
 type="cite">
  <div>v<br>
  <br>
  <div class="gmail_quote">On Tue, Jun 7, 2011 at 10:45 PM, Paul
Hoffman <span dir="ltr">&lt;<a href="mailto:paul.hoffman@vpnc.org">paul.hoffman@vpnc.org</a>&gt;</span>
wrote:<br>
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
    <div class="im">On Jun 7, 2011, at 6:24 PM, John C Klensin wrote:<br>
    <br>
&gt; I think this is an improvement but there is one issue about<br>
&gt; which we have slightly different impressions. &nbsp; I hope the<br>
&gt; difference can be resolved without needing yet more tedious<br>
&gt; arguments about documentation. &nbsp;Indeed, if such arguments are<br>
&gt; required, I'd prefer that we just forget about it.<br>
&gt;<br>
&gt; Anyway, your comments above about "most current version" imply<br>
&gt; to me that IANA should keep derived property tables for the most<br>
&gt; current version only. &nbsp;My expectation when 5982 was completed<br>
&gt; was that IANA was expected to keep derived property tables,<br>
&gt; clearly identified by version, for each and every Unicode<br>
&gt; version from 5.2 forward. &nbsp;In other words, the tables for the<br>
&gt; [most] current version would be added to, not replace, whatever<br>
&gt; previous version tables were around. &nbsp;The reasons for this, in<br>
&gt; terms of systems and implementations in various stages of<br>
&gt; development, implementation, and deployment, seem obvious... but<br>
&gt; maybe it was too obvious to some of us at the time to get the<br>
&gt; wording exactly right.<br>
    <br>
    </div>
While your interpretation could be one thing we might have meant, it is
not what is reflected in the RFC or the registry. RFC 5892 says:<br>
    <br>
5.1. &nbsp;IDNA-Derived Property Value Registry<br>
    <div class="im"><br>
&nbsp; IANA has created a registry with the derived properties for the<br>
    </div>
&nbsp; versions of Unicode released after (and including) version 5.2. &nbsp;The<br>
&nbsp; derived property value is to be calculated in cooperation with a<br>
&nbsp; designated expert [RFC5226] according to the specifications in<br>
&nbsp; Sections 2 and 3 and not by copying the non-normative table found in<br>
&nbsp; Appendix B.<br>
    <div class="im"><br>
&nbsp; If non-backward-compatible changes or other problems arise during the<br>
&nbsp; creation or designated expert review of the table of derived property<br>
    </div>
&nbsp; values, they should be flagged for the IESG. &nbsp;Changes to the rules<br>
&nbsp; (as specified in Sections 2 and 3), including BackwardCompatible<br>
&nbsp; (Section 2.7) (a set that is at release of this document is empty)<br>
&nbsp; require IETF Review, as described in RFC 5226 [RFC5226].<br>
    <br>
Note that every reference to the registry is singular. Also, the
registry at &lt;<a
 href="http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml"
 target="_blank">http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml</a>&gt;
doesn't mention "5.2" at all.<br>
    <br>
If the registry definition does not talk about keeping versions, and
the registry itself doesn't look like it tried, it may be implausible
to think that IANA would just start to do so in some future. To me, "a
registry" means a single registry.<br>
    <font color="#888888"><br>
--Paul Hoffman</font></blockquote>
  </div>
  </div>
</blockquote>
<br>
</body>
</html>

--------------020800040609000909040608--

From alexey.melnikov@isode.com  Wed Jun  8 04:55:36 2011
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 302A211E80BE; Wed,  8 Jun 2011 04:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 5J5zgRRR4Fe8; Wed,  8 Jun 2011 04:55:35 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 127BB11E80BC; Wed,  8 Jun 2011 04:55:34 -0700 (PDT)
Received: from [188.28.88.132] (188.28.88.132.threembb.co.uk [188.28.88.132])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Te9jKwA-ucR3@rufus.isode.com>; Wed, 8 Jun 2011 12:55:33 +0100
Message-ID: <4DEF631C.1070306@isode.com>
Date: Wed, 08 Jun 2011 12:55:08 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org> <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM> <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
In-Reply-To: <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 08 Jun 2011 11:55:36 -0000

Paul Hoffman wrote:

>On Jun 7, 2011, at 6:24 PM, John C Klensin wrote:
>  
>
>>I think this is an improvement but there is one issue about
>>which we have slightly different impressions.   I hope the
>>difference can be resolved without needing yet more tedious
>>arguments about documentation.  Indeed, if such arguments are
>>required, I'd prefer that we just forget about it.
>>
>>Anyway, your comments above about "most current version" imply
>>to me that IANA should keep derived property tables for the most
>>current version only.  My expectation when 5982 was completed
>>was that IANA was expected to keep derived property tables,
>>clearly identified by version, for each and every Unicode
>>version from 5.2 forward.  In other words, the tables for the
>>[most] current version would be added to, not replace, whatever
>>previous version tables were around.  The reasons for this, in
>>terms of systems and implementations in various stages of
>>development, implementation, and deployment, seem obvious... but
>>maybe it was too obvious to some of us at the time to get the
>>wording exactly right.
>>
That was my impression as well when I reviewed RFC 5982 while on IESG.

>While your interpretation could be one thing we might have meant, it is not what is reflected in the RFC or the registry. RFC 5892 says:
>
>5.1.  IDNA-Derived Property Value Registry
>
>   IANA has created a registry with the derived properties for the
>   versions of Unicode released after (and including) version 5.2.  The
>   derived property value is to be calculated in cooperation with a
>   designated expert [RFC5226] according to the specifications in
>   Sections 2 and 3 and not by copying the non-normative table found in
>   Appendix B.
>
>   If non-backward-compatible changes or other problems arise during the
>   creation or designated expert review of the table of derived property
>   values, they should be flagged for the IESG.  Changes to the rules
>   (as specified in Sections 2 and 3), including BackwardCompatible
>   (Section 2.7) (a set that is at release of this document is empty)
>   require IETF Review, as described in RFC 5226 [RFC5226].
>
>Note that every reference to the registry is singular.
>
There is a single registry, but multiple versions of Unicode.

>Also, the registry at <http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml> doesn't mention "5.2" at all.
>
That might be an error created when the registry got setup by IANA.

>If the registry definition does not talk about keeping versions, and the registry itself doesn't look like it tried, it may be implausible to think that IANA would just start to do so in some future. To me, "a registry" means a single registry.
>  
>


From john-ietf@jck.com  Wed Jun  8 04:56:23 2011
Return-Path: <john-ietf@jck.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 E0D0F11E80C9; Wed,  8 Jun 2011 04:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JGUEKQWNWVTA; Wed,  8 Jun 2011 04:56:23 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 4C5B411E80C5; Wed,  8 Jun 2011 04:56:23 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QUHMq-000DeK-Uk; Wed, 08 Jun 2011 07:56:13 -0400
Date: Wed, 08 Jun 2011 07:56:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Vint Cerf <vint@google.com>
Message-ID: <71EE769EE4C39C799F40668D@PST.JCK.COM>
In-Reply-To: <4DEF61F1.6040502@isode.com>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com>       <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org>            <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>            <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org>            <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM>            <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>            <BANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com> <4DEF61F1.6040502@isode.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: gen-art@ietf.org, IETF-Discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, draft-faltstrom-5892bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-faltstrom-5892bis-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, 08 Jun 2011 11:56:24 -0000

+1

--On Wednesday, June 08, 2011 12:50 +0100 Alexey Melnikov
<alexey.melnikov@isode.com> wrote:

> Vint Cerf wrote:
> 
>> setting aside interpretation and semantics for a moment,
>> would there  be utility in maintaining tables for each
>> instance of Unicode?
> 
> Yes, because developers will have different versions of
> Unicode available to them. It would also help developers to
> migrate by seeing what has changed between versions.





From scottr.nist@gmail.com  Wed Jun  8 10:08:03 2011
Return-Path: <scottr.nist@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 3AC1B21F84C3; Wed,  8 Jun 2011 10:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, 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 7qSiVctsRzpw; Wed,  8 Jun 2011 10:08:02 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3E821F84BF; Wed,  8 Jun 2011 10:08:01 -0700 (PDT)
Received: by wyb29 with SMTP id 29so596238wyb.31 for <multiple recipients>; Wed, 08 Jun 2011 10:08:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=3+nB5MoMzXiCA6EkJpBEqEvHywS5vWis6vkM6lqEUGQ=; b=drPq9LIkW3qDPDxH1gv/WbSZj+SqDT+aAM0IvNyeNlvzfS6tRY+tOZb0SB5pWbeu4x UWFAP2IiRZmNs4Qd6L1+kyAqQbrsOrGqgRc9O8P6lUzadWMt2BSaHMAwPbZ2kDOZtH3R E5fhWffcxQZEmUqGfRO9mDW5TSzn86iy9WzeM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=eLkP0gOVo/3tycYhD8MJ+MRwLlxPnJYnzYJtJl0uQWklm+7tSAcAQt5Da+0xI2CEoy LXXCK/3agHfvBQSnZ0Nv9uz5ZevCB+F+YHhRd9Drk9SJ675/LnEzQZVuwNCk/83PvwiW TO7ERxFsxyIJ8lot+BvelndfGFeIuO5XJUR10=
MIME-Version: 1.0
Received: by 10.216.14.199 with SMTP id d49mr7456449wed.65.1307552880440; Wed, 08 Jun 2011 10:08:00 -0700 (PDT)
Received: by 10.216.87.21 with HTTP; Wed, 8 Jun 2011 10:08:00 -0700 (PDT)
In-Reply-To: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com>
Date: Wed, 8 Jun 2011 13:08:00 -0400
Message-ID: <BANLkTikRmTLjuzUE8_nxMeyrL5sPFppqVg@mail.gmail.com>
From: Scott Rose <scottr.nist@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=001485f9a7c8f6b71104a5366044
X-Mailman-Approved-At: Wed, 08 Jun 2011 10:11:34 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-ietf-dnsext-rfc2672bis-dname.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: scott.rose@nist.gov
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, 08 Jun 2011 17:08:03 -0000

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

Perhaps the document should only update RFC 2672 instead of obsoleting it?

As for the nits:


On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> wrote:
>
>  Nits/editorial comments:



 -- IDNits has some comments, please check.



> -- Abstract: "This is a revision of the original specification in RFC 2672,
> also aligning RFC 3363 and RFC 4294 with this revision."
>

The heading says this obsoletes 2672 and updates the other two. It's
> probably worth explicitly using those words here.
>

Will change to say that this doc updates all three RFC's.


>  -- 3.1, 1st paragraph: "Relevant includes the following cases:"


> Awkward sentence. Maybe "Relevant cases include the following:"?
>
>
Will re-write to make it flow better.


>  -- 3.1, 5th paragraph: "is synthesized and included in the answer
> section"



What synthesized it? The server? (passive voice obscures responsibility)
>
> The caching servers in this case.  Will re-write to clarify that.


>  -- ... "The DNAME has an RRSIG"


> A _signed_ DNAME has an RRSIG, right?
>
> Correct, will make more explicit.



> -- 4, 4th paragraph: "...should be revised..."
>
> This document actually executes the revision, right? Better to say "this
> document revises..." rather than "should be revised"
>
>
Yes, will correct.


> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>
> Won't that just leave the word "deleted" hanging on page without
> explanation? Wouldn't it be better to just simply delete it?
>
>
Maybe, but I think the logic was that if there is some text there (just
something), it can be cleanly referenced (i.e. "DELETED [RFCXXXX]")if
someone is making a revised version of the RFC for some purpose.  Purely
deleting it accomplishes the task, but this provides a good "hook" for a
paper trail.

Scott

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

<div>Perhaps the document should only update RFC 2672 instead of obsoleting=
 it? =A0<br></div><div><br></div><div>As for the nits:<br></div><div><br></=
div><div><br></div><div class=3D"gmail_quote">On Tue, Jun 7, 2011 at 6:35 P=
M, Ben Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com">be=
n@nostrum.com</a>&gt;</span> wrote: =A0<blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
=A0Nits/editorial comments:=A0</blockquote><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;">
=A0-- IDNits has some comments, please check. =A0</blockquote><div>=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex;">
-- Abstract: &quot;This is a revision of the original specification in RFC =
2672, also aligning RFC 3363 and RFC 4294 with this revision.&quot;<br>
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;">
The heading says this obsoletes 2672 and updates the other two. It&#39;s pr=
obably worth explicitly using those words here.<br></blockquote><div><br></=
div><div>Will change to say that this doc updates all three RFC&#39;s.</div=
>
<div>=A0=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- 3.1, 1st paragraph: =
&quot;Relevant includes the following cases:&quot;=A0</blockquote><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;">

<br>
Awkward sentence. Maybe &quot;Relevant cases include the following:&quot;?<=
br>
<br></blockquote><div><br></div><div>Will re-write to make it flow better.<=
/div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- 3.1, 5th paragraph=
: &quot;is synthesized and included in the answer section&quot;=A0</blockqu=
ote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">=A0</blockquote><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex;">
What synthesized it? The server? (passive voice obscures responsibility)<br=
>
<br></blockquote><div>The caching servers in this case. =A0Will re-write to=
 clarify that.=A0</div><div>=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- =
... &quot;The DNAME has an RRSIG&quot;=A0</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<br>
A _signed_ DNAME has an RRSIG, right?<br>
<br></blockquote><div>Correct, will make more explicit.</div><div><br></div=
><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;">
-- 4, 4th paragraph: &quot;...should be revised...&quot;<br>
<br>
This document actually executes the revision, right? Better to say &quot;th=
is document revises...&quot; rather than &quot;should be revised&quot;<br>
<br></blockquote><div><br></div><div>Yes, will correct.</div><div>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
-- ..., 7th paragraph: &quot;...replaced with the word &quot;DELETED&quot;.=
&quot;<br>
<br>
Won&#39;t that just leave the word &quot;deleted&quot; hanging on page with=
out explanation? Wouldn&#39;t it be better to just simply delete it?<br>
<br>
</blockquote></div><div><br></div><div>Maybe, but I think the logic was tha=
t if there is some text there (just something), it can be cleanly reference=
d (i.e. &quot;DELETED [RFCXXXX]&quot;)if someone is making a revised versio=
n of the RFC for some purpose. =A0Purely deleting it accomplishes the task,=
 but this provides a good &quot;hook&quot; for a paper trail.</div>
<div><br></div><div>Scott</div>

--001485f9a7c8f6b71104a5366044--

From scottr.nist@gmail.com  Wed Jun  8 10:11:14 2011
Return-Path: <scottr.nist@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 CE11721F8544; Wed,  8 Jun 2011 10:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, 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 Q4joNbc-bneJ; Wed,  8 Jun 2011 10:11:14 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id A361E21F8526; Wed,  8 Jun 2011 10:11:13 -0700 (PDT)
Received: by wyb29 with SMTP id 29so598633wyb.31 for <multiple recipients>; Wed, 08 Jun 2011 10:11:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=8S1qwCCAyHfuiVFf1TRFTj+KDzSg//LFMIIf2z2YWWQ=; b=Ltedcm1PWLFdWg8sEDP5FsyXtp72hvJ8OuohwBLMpjq+fcqwwJ9127n04r9LH50Hjx jgW8uq0RrJm7FFrU9SZqTexp7J4jB6FUS3hDfaQnKQfW0JUngPZEiK+5+AGUDldQo/M5 11swVboFX0BrYIlouvJtwcY694Cgx8VsBeHQM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=T/h2mZHjq/OtQ3rtjZQgqw6Evd1YfXV4Ck8sZgZ11+EN9VN4e0qLTQW+j8zCPdwSfR 2pWN1tEsWzMeCknhyb3AL7Ccs0gyLKe5w/z5/ryhono1uAKeNHWIM4I73SUBKPizB0zy gjY5smQ9aY60esuLD12HKMe6grxAD0oXU+iSc=
MIME-Version: 1.0
Received: by 10.216.145.206 with SMTP id p56mr5225022wej.80.1307553072689; Wed, 08 Jun 2011 10:11:12 -0700 (PDT)
Received: by 10.216.87.21 with HTTP; Wed, 8 Jun 2011 10:11:12 -0700 (PDT)
In-Reply-To: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com>
Date: Wed, 8 Jun 2011 13:11:12 -0400
Message-ID: <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com>
From: Scott Rose <scottr.nist@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=0016e6de04446c33f304a5366cb7
X-Mailman-Approved-At: Wed, 08 Jun 2011 10:11:34 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-ietf-dnsext-rfc2672bis-dname.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: scott.rose@nist.gov
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, 08 Jun 2011 17:11:14 -0000

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

Perhaps the document should only update RFC 2672 instead of obsoleting it?

As for the nits:


On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> wrote:
>
>  Nits/editorial comments:



 -- IDNits has some comments, please check.



> -- Abstract: "This is a revision of the original specification in RFC 2672,
> also aligning RFC 3363 and RFC 4294 with this revision."
>

The heading says this obsoletes 2672 and updates the other two. It's
> probably worth explicitly using those words here.
>

Will change to say that this doc updates all three RFC's.


>  -- 3.1, 1st paragraph: "Relevant includes the following cases:"


> Awkward sentence. Maybe "Relevant cases include the following:"?
>
>
Will re-write to make it flow better.


>  -- 3.1, 5th paragraph: "is synthesized and included in the answer
> section"



What synthesized it? The server? (passive voice obscures responsibility)
>
> The caching servers in this case.  Will re-write to clarify that.


>  -- ... "The DNAME has an RRSIG"


> A _signed_ DNAME has an RRSIG, right?
>
> Correct, will make more explicit.



> -- 4, 4th paragraph: "...should be revised..."
>
> This document actually executes the revision, right? Better to say "this
> document revises..." rather than "should be revised"
>
>
Yes, will correct.


> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>
> Won't that just leave the word "deleted" hanging on page without
> explanation? Wouldn't it be better to just simply delete it?
>
>
Maybe, but I think the logic was that if there is some text there (just
something), it can be cleanly referenced (i.e. "DELETED [RFCXXXX]")if
someone is making a revised version of the RFC for some purpose.  Purely
deleting it accomplishes the task, but this provides a good "hook" for a
paper trail.

Scott

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

<div>Perhaps the document should only update RFC 2672 instead of obsoleting=
 it? =A0<br></div><div><br></div><div>As for the nits:<br></div><div><br></=
div><div><br></div><div class=3D"gmail_quote">On Tue, Jun 7, 2011 at 6:35 P=
M, Ben Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com">be=
n@nostrum.com</a>&gt;</span> wrote: =A0<blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
=A0Nits/editorial comments:=A0</blockquote><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;">
=A0-- IDNits has some comments, please check. =A0</blockquote><div>=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex;">
-- Abstract: &quot;This is a revision of the original specification in RFC =
2672, also aligning RFC 3363 and RFC 4294 with this revision.&quot;<br>
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;">
The heading says this obsoletes 2672 and updates the other two. It&#39;s pr=
obably worth explicitly using those words here.<br></blockquote><div><br></=
div><div>Will change to say that this doc updates all three RFC&#39;s.</div=
>
<div>=A0=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- 3.1, 1st paragraph: =
&quot;Relevant includes the following cases:&quot;=A0</blockquote><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;">

<br>
Awkward sentence. Maybe &quot;Relevant cases include the following:&quot;?<=
br>
<br></blockquote><div><br></div><div>Will re-write to make it flow better.<=
/div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- 3.1, 5th paragraph=
: &quot;is synthesized and included in the answer section&quot;=A0</blockqu=
ote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">=A0</blockquote><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex;">
What synthesized it? The server? (passive voice obscures responsibility)<br=
>
<br></blockquote><div>The caching servers in this case. =A0Will re-write to=
 clarify that.=A0</div><div>=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- =
... &quot;The DNAME has an RRSIG&quot;=A0</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<br>
A _signed_ DNAME has an RRSIG, right?<br>
<br></blockquote><div>Correct, will make more explicit.</div><div><br></div=
><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;">
-- 4, 4th paragraph: &quot;...should be revised...&quot;<br>
<br>
This document actually executes the revision, right? Better to say &quot;th=
is document revises...&quot; rather than &quot;should be revised&quot;<br>
<br></blockquote><div><br></div><div>Yes, will correct.</div><div>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
-- ..., 7th paragraph: &quot;...replaced with the word &quot;DELETED&quot;.=
&quot;<br>
<br>
Won&#39;t that just leave the word &quot;deleted&quot; hanging on page with=
out explanation? Wouldn&#39;t it be better to just simply delete it?<br>
<br>
</blockquote></div><div><br></div><div>Maybe, but I think the logic was tha=
t if there is some text there (just something), it can be cleanly reference=
d (i.e. &quot;DELETED [RFCXXXX]&quot;)if someone is making a revised versio=
n of the RFC for some purpose. =A0Purely deleting it accomplishes the task,=
 but this provides a good &quot;hook&quot; for a paper trail.</div>
<div><br></div><div>Scott</div>

--0016e6de04446c33f304a5366cb7--

From wassim.haddad@ericsson.com  Wed Jun  8 11:18:45 2011
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 275AD11E80CE for <gen-art@ietfa.amsl.com>; Wed,  8 Jun 2011 11:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TrWE9kQjgOE3 for <gen-art@ietfa.amsl.com>; Wed,  8 Jun 2011 11:18:44 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA1011E8095 for <gen-art@ietf.org>; Wed,  8 Jun 2011 11:18:44 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p58IIboo013979 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 8 Jun 2011 13:18:43 -0500
Received: from [155.53.235.40] (147.117.20.214) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.3.137.0; Wed, 8 Jun 2011 14:18:37 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 8 Jun 2011 11:18:36 -0700
Message-ID: <ED17301A-B22F-42AA-B260-035A08500602@ericsson.com>
To: Gen-art <gen-art@ietf.org>, <draft-ietf-dhc-duid-uuid.all@tools.ietf.org>
MIME-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [Gen-art]  Gen-ART LC review of draft-ietf-dhc-duid-uuid
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, 08 Jun 2011 18:18:45 -0000

I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at=20
<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-duid-uuid-03
Document title: Definition of the UUID-based DHCPv6 Unique Identifier =
(DUID-UUID)

Reviewer: Wassim Haddad
Review Date: 08-June-2011
IETF LC End Date: 01-June-2011
IESG Telechat date: 09-June-2011

Summary: This document is ready for publication as a proposed standard

- Major Issue(s): None
- Minor Issue(s): None

- Editorial:

Section 2: One issue that has arisen concerns ... devices that employ


Regards,

Wassim H.






From vkg@bell-labs.com  Wed Jun  8 12:08:43 2011
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 1E87411E814D for <gen-art@ietfa.amsl.com>; Wed,  8 Jun 2011 12:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 mG2-yi9hwjxo for <gen-art@ietfa.amsl.com>; Wed,  8 Jun 2011 12:08:39 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 5465111E8124 for <gen-art@ietf.org>; Wed,  8 Jun 2011 12:08:39 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p58J8Peo029085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Jun 2011 14:08:25 -0500 (CDT)
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 p58J8O5J017900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 8 Jun 2011 14:08:25 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p58J8Mb6004482; Wed, 8 Jun 2011 14:08:22 -0500 (CDT)
Message-ID: <4DEFC8C1.6050609@bell-labs.com>
Date: Wed, 08 Jun 2011 14:08:49 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc14 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: draft-ietf-ipfix-configuration-model@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.9
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, General Area Review Team <gen-art@ietf.org>, Nevil Brownlee <n.brownlee@auckland.ac.nz>, quittek@neclab.eu
Subject: [Gen-art] Gen-ART review of draft-ietf-ipfix-configuration-model-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, 08 Jun 2011 19:08:43 -0000

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

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

Document: draft-ietf-ipfix-configuration-model-09
Reviewer: Vijay K. Gurbani
Review Date: June-8-2011
IETF LC End Date: June-15-2011
IESG Telechat date: Unknown

Summary: This draft is ready as an Proposed Standard.

Major issues: 0
Minor issues: 0
Nits/editorial comments: 1

Nits:

- There are references in the Abstract, which could probably
   be removed and replaced in the body of the draft.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From suresh.krishnan@ericsson.com  Wed Jun  8 13:22:02 2011
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 C3F4D1F0657 for <gen-art@ietfa.amsl.com>; Wed,  8 Jun 2011 13:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.399
X-Spam-Level: 
X-Spam-Status: No, score=-106.399 tagged_above=-999 required=5 tests=[AWL=0.200, 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 6AO8lobtZAK8 for <gen-art@ietfa.amsl.com>; Wed,  8 Jun 2011 13:22:02 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id 238451F0C35 for <gen-art@ietf.org>; Wed,  8 Jun 2011 13:21:54 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p58KLdgT007870; Wed, 8 Jun 2011 15:21:42 -0500
Received: from [142.133.10.107] (147.117.20.214) by eusaamw0712.eamcs.ericsson.se (147.117.20.182) with Microsoft SMTP Server id 8.3.137.0; Wed, 8 Jun 2011 16:21:33 -0400
Message-ID: <4DEFD94C.4070707@ericsson.com>
Date: Wed, 8 Jun 2011 16:19:24 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
References: <4DEEA636.4000208@ericsson.com> <BANLkTimfkBUOu60=xorZ=VRfqY_zB_hsRQ@mail.gmail.com>
In-Reply-To: <BANLkTimfkBUOu60=xorZ=VRfqY_zB_hsRQ@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-sieve-external-lists.all@tools.ietf.org" <draft-ietf-sieve-external-lists.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-sieve-external-lists-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 20:22:02 -0000

Hi Barry,
   That makes sense. Please consider my concern resolved.

Thanks
Suresh

On 11-06-07 06:36 PM, Barry Leiba wrote:
> Thanks, Suresh, for the review.
> 
>> This following text is a bit handwavy. Is this by design? How can the sieve
>> implementation identify the list as one that has an open subscriber list. Is
>> the sieve engine expected to try one of these methods first and failover
>> into another. Is there an expectation that all sieve implementations will
>> actually be capable of invoking both these mechanisms?
>>
>> "For some lists, the Sieve engine might directly retrieve the list and
>> make its own comparison.  Other lists might not work that way -- they
>> might provide a way to ask if a value is in the list, but not permit
>> retrieval of the list itself."
> 
> Yes, it's vague by design.  The Sieve engine needs to be integrated
> with the list handling -- this is saying that for some that's done
> simply by having the Sieve engine retrieve the list and search it, but
> for other lists it's done through some sort of API by which it
> searches the list.  In any case, the Sieve engine needs to know how to
> access each list that it supports... and that access is out of scope
> here.
> 
> Barry


From suresh.krishnan@ericsson.com  Wed Jun  8 13:46:59 2011
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 B2E7211E8199 for <gen-art@ietfa.amsl.com>; Wed,  8 Jun 2011 13:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.066
X-Spam-Level: 
X-Spam-Status: No, score=-106.066 tagged_above=-999 required=5 tests=[AWL=-0.266, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, 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 ARFpgINtJg4f for <gen-art@ietfa.amsl.com>; Wed,  8 Jun 2011 13:46:59 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id BA52711E818A for <gen-art@ietf.org>; Wed,  8 Jun 2011 13:46:57 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p58KkqKE012664; Wed, 8 Jun 2011 15:46:55 -0500
Received: from [142.133.10.107] (147.117.20.214) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.3.137.0; Wed, 8 Jun 2011 16:46:48 -0400
Message-ID: <4DEFDF38.6080602@ericsson.com>
Date: Wed, 8 Jun 2011 16:44:40 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Pedro Marques <pedro.r.marques@gmail.com>
References: <4DEEAB6D.7060407@ericsson.com> <BANLkTinG96r2_5i-LRD2hL+5t58jaLuP4RRJbMKMvtduBecP-A@mail.gmail.com>
In-Reply-To: <BANLkTinG96r2_5i-LRD2hL+5t58jaLuP4RRJbMKMvtduBecP-A@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-l3vpn-ibgp.all@tools.ietf.org" <draft-ietf-l3vpn-ibgp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-l3vpn-ibgp-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, 08 Jun 2011 20:46:59 -0000

Hi Pedro,
   Thanks for the quick reply. Please find comments inline.

On 11-06-07 07:15 PM, Pedro Marques wrote:
> Suresh,
> Thank you for the review.
> 
> Regarding Section 5:
> The Length can be either 1 or 2 octets. 4271 defines Attr Flags.
> Bit 0 is the Optional bit; Bit 1 is the Transitive bit;  Bit 3 is the
> Extended length bit.
> 
> This document specified that bits 0 and 1 must be set to 1 (Optional +
> transitive). The Extended length bit must be set according to the
> attribute payload as per 4271.
> 
> The convention is the same as for any other BGP attribute.
> 
> I'll add a clarification to this effect.

Perfect. I did read up on Section 4.3 of RFC4271 before I sent my review 
but it was not clear whether setting the bit was per attribute type code 
or it was runtime. I think a clarification would be good here.

> 
> Regarding security considerations:
> - The resource management considerations exist regarding routes as
> well as attributes, with or without this specification. I don't mind
> highlighting it, if you believe that improves the specification.

I do believe this is worth mentioning, but I leave it up to your 
discretion on whether you want to add any text.

Thanks
Suresh


From kyle@drummondgroup.com  Wed Jun  8 14:23:47 2011
Return-Path: <kyle@drummondgroup.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 DD9F11F0C51 for <gen-art@ietfa.amsl.com>; Wed,  8 Jun 2011 14:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 TVdM26NZIpip for <gen-art@ietfa.amsl.com>; Wed,  8 Jun 2011 14:23:45 -0700 (PDT)
Received: from oproxy8-pub.bluehost.com (oproxy8-pub.bluehost.com [69.89.22.20]) by ietfa.amsl.com (Postfix) with SMTP id 835221F0C55 for <gen-art@ietf.org>; Wed,  8 Jun 2011 14:23:43 -0700 (PDT)
Received: (qmail 19191 invoked by uid 0); 8 Jun 2011 21:23:43 -0000
Received: from unknown (HELO box579.bluehost.com) (66.147.242.179) by oproxy8.bluehost.com with SMTP; 8 Jun 2011 21:23:43 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=drummondgroup.com; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=cLbeJ36fQb+oF4e/eEmRPqq5BRwpnmqaEcsvVQOoR6e/cLsQNRguWqEUrG2X7HUO0tn4aeCzf2yCW6Osv4WMmzJ2XJPHQjX10KAkWy72JQOekU++1SCI3T8yU5JIa5my;
Received: from c-76-18-162-113.hsd1.tn.comcast.net ([76.18.162.113] helo=KyleHP) by box579.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <kyle@drummondgroup.com>) id 1QUQE2-0006th-Lv; Wed, 08 Jun 2011 15:23:42 -0600
From: "Kyle Meadors" <kyle@drummondgroup.com>
To: "'Pete McCann'" <mccap@petoni.org>, <gen-art@ietf.org>, <draft-meadors-multiple-attachments-ediint.all@tools.ietf.org>
References: <BANLkTikzLkXL9=e4HGDra5t2F2+Pz0rBkA@mail.gmail.com>
In-Reply-To: <BANLkTikzLkXL9=e4HGDra5t2F2+Pz0rBkA@mail.gmail.com>
Date: Wed, 8 Jun 2011 16:23:42 -0500
Message-ID: <01ed01cc2622$5808ff70$081afe50$@drummondgroup.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ67URRpdYz2C89XIkVYJCfJ4H92JNWadnA
Content-Language: en-us
X-Identified-User: {1133:box579.bluehost.com:drummon1:drummondgroup.com} {sentby:smtp auth 76.18.162.113 authed with kyle@drummondgroup.com}
X-Mailman-Approved-At: Wed, 08 Jun 2011 14:28:07 -0700
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-meadors-multiple-attachments-ediint-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, 08 Jun 2011 21:23:47 -0000

To Pete Resnick, do you want me to correct this whitespace and resubmit? =
It
was not intentional and should be corrected?

Kyle Meadors
Drummond Group Inc.
=A0
* * * I will be out of the office the week of July 4-8 * * *
* * * I will be out of the office=A0August 4-5=A0* * *
=A0
* * * * * * * * * * * * * * * * * * * * * * * *
CONFIDENTIALITY DISCLAIMER
This email, including attachments, is confidential and proprietary. It
constitutes exclusive communication solely to the addressee. Any entity
other than the intended addressee is prohibited from use of this
communication for any purpose. This email, including attachments, may =
not be
distributed, whole or in part.
* * * * * * * * * * * * * * * * * * * * * * * *


-----Original Message-----
From: Pete McCann [mailto:mccap@petoni.org]=20
Sent: Monday, June 06, 2011 8:11 AM
To: gen-art@ietf.org;
draft-meadors-multiple-attachments-ediint.all@tools.ietf.org
Subject: Gen-ART Telechat Review of
draft-meadors-multiple-attachments-ediint-12

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-meadors-multiple-attachments-ediint-12
Reviewer: Pete McCann
Review Date: 2011-06-06
IETF LC End Date:
IESG Telechat date: 2011-06-09

Summary: Ready.

Major issues: none

Minor issues: none

Nits/editorial comments:

My nit from the last review was not addressed.  Maybe it is a non-issue?

There is a space in the declaration of boundary=3D" INNER-BOUNDARY"; in =
the
example in section 3.  I am not sure whether this was intentional or =
whether
it will mess up a standard MIME parser, but you may want to remove it.


From ben@nostrum.com  Wed Jun  8 14:50:44 2011
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 05D3121F8531; Wed,  8 Jun 2011 14:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.016
X-Spam-Level: 
X-Spam-Status: No, score=-102.016 tagged_above=-999 required=5 tests=[AWL=0.583, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 v8oMtPCEN4jn; Wed,  8 Jun 2011 14:50:43 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 14C2021F84DB; Wed,  8 Jun 2011 14:50:33 -0700 (PDT)
Received: from [10.0.1.6] (cpe-76-187-75-59.tx.res.rr.com [76.187.75.59]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p58LoRTw089804 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 8 Jun 2011 16:50:28 -0500 (CDT) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-8-697628755
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com>
Date: Wed, 8 Jun 2011 16:50:26 -0500
Message-Id: <42646542-15D4-4ABF-A65F-A0F3361D049A@nostrum.com>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com> <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com>
To: scott.rose@nist.gov
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 76.187.75.59 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-ietf-dnsext-rfc2672bis-dname.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 21:50:44 -0000

--Apple-Mail-8-697628755
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks for the response! Comments below, eliding the bits I think need =
no further comment.

On Jun 8, 2011, at 12:11 PM, Scott Rose wrote:

> Perhaps the document should only update RFC 2672 instead of obsoleting =
it? =20

That would resolve my concern, if it fits with the intent of the work =
group.


>=20
> As for the nits:
>=20
>=20
> On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> wrote: =20=

>=20

[...]

> Yes, will correct.
> =20
> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>=20
> Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?
>=20
>=20
> Maybe, but I think the logic was that if there is some text there =
(just something), it can be cleanly referenced (i.e. "DELETED =
[RFCXXXX]")if someone is making a revised version of the RFC for some =
purpose.  Purely deleting it accomplishes the task, but this provides a =
good "hook" for a paper trail.
>=20

Okay. On reflection, it's not like we really render the updates the old =
RFC documents.


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


--Apple-Mail-8-697628755
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Thanks for the response! Comments below, eliding the bits I think =
need no further comment.</div><br><div><div>On Jun 8, 2011, at 12:11 PM, =
Scott Rose wrote:</div><br class=3D"Apple-interchange-newline"><blockquote=
 type=3D"cite"><div>Perhaps the document should only update RFC 2672 =
instead of obsoleting it? =
&nbsp;<br></div></blockquote><div><br></div><div>That would resolve my =
concern, if it fits with the intent of the work =
group.</div><div><br></div><br><blockquote =
type=3D"cite"><div><br></div><div>As for the =
nits:<br></div><div><br></div><div><br></div><div class=3D"gmail_quote">On=
 Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <span dir=3D"ltr">&lt;<a =
href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a>&gt;</span> wrote: =
&nbsp;<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc =
solid;padding-left:1ex;"><br></blockquote></div></blockquote><div><br></di=
v><div>[...]</div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div>Yes, will =
correct.</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, =
204, 204); border-left-style: solid; padding-left: 1ex; position: =
static; z-index: auto; ">
-- ..., 7th paragraph: "...replaced with the word "DELETED"."<br>
<br>
Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?<br>
<br>
</blockquote></div><div><br></div><div>Maybe, but I think the logic was =
that if there is some text there (just something), it can be cleanly =
referenced (i.e. "DELETED [RFCXXXX]")if someone is making a revised =
version of the RFC for some purpose. &nbsp;Purely deleting it =
accomplishes the task, but this provides a good "hook" for a paper =
trail.</div>
<div><br></div></blockquote><div><br></div><div>Okay. On reflection, =
it's not like we really render the updates the old RFC =
documents.</div><div><br></div><br><blockquote =
type=3D"cite"><div>Scott</div>
_______________________________________________<br>Gen-art mailing =
list<br><a =
href=3D"mailto:Gen-art@ietf.org">Gen-art@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/gen-art<br></blockquote></div><br></body></html>=

--Apple-Mail-8-697628755--

From mahoney@nostrum.com  Thu Jun  9 14:49:34 2011
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 083E511E811B for <gen-art@ietfa.amsl.com>; Thu,  9 Jun 2011 14:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLY8A8Se3EFM for <gen-art@ietfa.amsl.com>; Thu,  9 Jun 2011 14:49:33 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 229FF11E80F5 for <gen-art@ietf.org>; Thu,  9 Jun 2011 14:49:32 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-49-161.dllstx.fios.verizon.net [71.170.49.161]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p59LnVPi034300 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 9 Jun 2011 16:49:31 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4DF13FEB.7010005@nostrum.com>
Date: Thu, 09 Jun 2011 16:49:31 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 71.170.49.161 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2011-06-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: Thu, 09 Jun 2011 21:49:34 -0000

Hi all,

Here's the link to the new LC assignments:
http://wiki.tools.ietf.org/dav/genart/reviewers-110609-lc.html

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 jmh@joelhalpern.com  Thu Jun  9 16:31:28 2011
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 03FE01F0C69 for <gen-art@ietfa.amsl.com>; Thu,  9 Jun 2011 16:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dqd5qnK7sY-m for <gen-art@ietfa.amsl.com>; Thu,  9 Jun 2011 16:31:25 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob-ipv6.tigertech.net [IPv6:2604:4f00::1:0:0:22]) by ietfa.amsl.com (Postfix) with ESMTP id A046A1F0C65 for <gen-art@ietf.org>; Thu,  9 Jun 2011 16:31:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id F142A3245A95; Thu,  9 Jun 2011 16:31:22 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.101] (pool-71-161-51-49.clppva.btas.verizon.net [71.161.51.49]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 76FC83228BE3; Thu,  9 Jun 2011 16:31:22 -0700 (PDT)
Message-ID: <4DF157C6.7070000@joelhalpern.com>
Date: Thu, 09 Jun 2011 19:31:18 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4D41B9B3.9070501@nostrum.com>
In-Reply-To: <4D41B9B3.9070501@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]    review: draft-ietf-rmt-bb-fec-raptorq-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: Thu, 09 Jun 2011 23:31:28 -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.   This is a re-review for telechat purposes.

Document: draft-ietf-rmt-bb-fec-raptorq-06
     RaptorQ Forward Error Correction Scheme for Object Delivery
Reviewer: Joel M. Halpern
Review Date: 9-June-2011
IETF LC End Date: 17-June-2011
IESG Telechat date: N/A

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


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


From elwynd@dial.pipex.com  Fri Jun 10 10:58:04 2011
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 4649311E81D0; Fri, 10 Jun 2011 10:58:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 34ROB+yfNq0H; Fri, 10 Jun 2011 10:58:03 -0700 (PDT)
Received: from b.painless.aaisp.net.uk (b.painless.aaisp.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 02A2211E810F; Fri, 10 Jun 2011 10:58:02 -0700 (PDT)
Received: from 250.254.187.81.in-addr.arpa ([81.187.254.250]) by b.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1QV5y2-0007mN-1f; Fri, 10 Jun 2011 18:57:58 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Fri, 10 Jun 2011 19:01:54 +0100
Message-Id: <1307728914.22973.2654.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-pcn-cl-edge-behaviour.all@tools.ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Fri, 10 Jun 2011 17:58:04 -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-pcn-cl-edge-behaviour-08 
Reviewer: Elwyn Davies
Review Date: 10 June 2011
IETF LC End Date: 10 June 2011
IESG Telechat date: (if known) -

Summary:
In my opinion, there are a number of areas that need significant work
and at least one open issue (the stability question from s3.3.1) that
needs to be addressed before this document is ready for the IESG.

Major issues:
The draft contains partial definitions of two control protocols (egress
-> decision point; decision point -> ingress).  It does not make it
clear whether the reader is expected to get full definitions of these
protocols here or whether there will be another document that specifies
these protocols completely.  As is stands one could build the protocols
and pretty much guarantee that they would not be interoperable with
other implementations since message formats are not included although
high level specs are.  The document needs to be much clearer about what
is expected to happen here.
 
Use of EXP codepoint: My understanding of what is said in RFC 5696 is
that EXP is supposed to be left for other (non=PCN) systems to use.
This draft uses it.  Is this sensible? Is this whole draft experimental
really?

s3.3.1:
> [CL-specific] The outcome of the comparison is not very sensitive
>       to the value of the CLE-limit in practice, because when threshold-
>       marking occurs it tends to persist long enough that threshold-
>       marked traffic becomes a large proportion of the received traffic
>       in a given interval.
This statement worries me.  It sounds like a characteristic of an
unstable system.  If the value is that non-critical why are we
bothering?

Minor issues:
s1.1: definition of PCN-Traffic etc:  
> The same network will carry traffic of other Diffserv BAs.
Just to be sure: Does this or does this not imply that *all* traffic in
a PCN network must have a non-empty DSCP marking, i.e. that *all*
traffic must be attached to some specific Diffserv BA? This should be
clarified whichever is true. 

s1.1: T-fail:  I notice from s3.1 that PCN-ingress nodes also have to
make reports on request.  Should T-fail or some other timer apply to
non-return of info from ingress points?  What would a (probably
non-colocated) decision point do if it lost contact with the ingress? 

s2/s3.2.1: The use of PM and EXP codepoints for ThM and ETM appear to be
reversed in these two sections!!  Which way round is intended?

s3.2.1/s3.2.2:  Neither section mentions T-meas but I assume that this
is supposed to be (either or both) the sampling period in the egress
node or the period between reports.  It is unclear if they are allowed
to be different and if they are which one is T-meas.  However s3.2.3
appears to imply that T-meas is probably the time between reports.  This
all needs to be much clearer.

s3.2.1/3.2.2: In s3.2.2, para 2:
> If so configured (e.g., because multipath routing is
>    being used, as explained in the previous section), the PCN-egress-
>    node MUST also report the set of flow identifiers of PCN-flows for
>    which excess-traffic-marking was observed in the most recent
>    measurement interval.
This is a requirement for a protocol that you may or may not be
defining. Confusing.

s3.2.3/s3.2.2: The first paragraph of s3.2.3 suggests that the report
from an egress may not always contain the calculated value of the CLE,
but s3.2.2 has a MUST for the report to contain this value.
Consistency!!!

s6:  The potential introduction of a centralized decision point appears
to provide additional attack points beyond the architecture in RFC 5559.
It appears to me that the requests for information about specific flows
to the ingress are ighly vulnerable as they (probably) contain all the
information needed to craft a DoS attack on the flow.

Nits/editorial comments:
General: Consistency of naming for timing paramters t-meas/T-meas, etc.

s1.1: I think it would be worth reproducing the CL-specific definitions:
PCN-threshold-rate and threshold-marked since they are specific.

s1.1: 
> Congestion level estimate (CLE)
>       A value derived from the measurement of PCN-packets received at a
>       PCN-egress-node for a given ingress-egress-aggregate, representing
>       the ratio of marked to total PCN-traffic (measured in octets)
            ^^^^^                                 ^^^^^^^^^^^^^^^^^^
>       received over a short period.
The ratio is (hopefully) dimensionless.  Maybe '(each measured in octets)' ?

s2:
> the PCN-domain satisfies the conditions specified in [RFC5696];
This may be a bit pedantic but I am not sure that RFC 5696 actually sets
out conditions for the domain.  It sets out rules for encoding markings
and allowed transitions.  Maybe s/conditions/packet markings and allowed
transitions/.

s3.1, para 1 and several other instances: s/collocated/co(-)located/

s3.2.1, para 5: s/statistical variance/statistical variation/





From suresh.krishnan@ericsson.com  Tue Jun 14 08:28:29 2011
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 39C531F0C38 for <gen-art@ietfa.amsl.com>; Tue, 14 Jun 2011 08:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.499
X-Spam-Level: 
X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 4AIoQmt7w1F8 for <gen-art@ietfa.amsl.com>; Tue, 14 Jun 2011 08:28:28 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id EBD8A1F0C34 for <gen-art@ietf.org>; Tue, 14 Jun 2011 08:28:26 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p5EFSOBc010587; Tue, 14 Jun 2011 10:28:26 -0500
Received: from [142.133.10.107] (147.117.20.214) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.3.137.0; Tue, 14 Jun 2011 11:28:21 -0400
Message-ID: <4DF77D38.30501@ericsson.com>
Date: Tue, 14 Jun 2011 11:24:40 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, "draft-ietf-l3vpn-mvpn-infra-addrs.all@tools.ietf.org" <draft-ietf-l3vpn-mvpn-infra-addrs.all@tools.ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-l3vpn-mvpn-infra-addrs-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: Tue, 14 Jun 2011 15:28:30 -0000

I am the assigned Gen-ART reviewer for
draft-ietf-l3vpn-mvpn-infra-addrs-04.txt

For background on Gen-ART, please see the FAQ at
<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.

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

Summary: This draft has addressed my comments on version -02 and is
ready for publication as an Proposed Standard.

Thanks
Suresh












From elwynd@dial.pipex.com  Tue Jun 14 10:20:57 2011
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 EDCF59E800B; Tue, 14 Jun 2011 10:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oZRuPGc46wQ2; Tue, 14 Jun 2011 10:20:55 -0700 (PDT)
Received: from a.painless.aaisp.net.uk (auth.a.painless.aaisp.net.uk [IPv6:2001:8b0:0:30:230:48ff:fe72:d05c]) by ietfa.amsl.com (Postfix) with ESMTP id 1C13A9E800A; Tue, 14 Jun 2011 10:20:53 -0700 (PDT)
Received: from study.folly.org.uk ([81.187.254.244]) by a.painless.aaisp.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1QWXIG-0003if-Pz; Tue, 14 Jun 2011 18:20:49 +0100
Message-ID: <4DF7986B.5020108@dial.pipex.com>
Date: Tue, 14 Jun 2011 18:20:43 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: philip.eardley@bt.com
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk> <9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pcn@ietf.org, General Area Reviwing Team <gen-art@ietf.org>, ietfdbh@comcast.net
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Tue, 14 Jun 2011 17:20:57 -0000

Hi, Phil.

It strikes me that the first and second points below are something which 
David Harrington perhaps ought to give an opinion on. He has got to 
defend it to the IESG.

On the first point, my feeling is that neither the requirements doc nor 
this doc is sufficient to guarantee an interoperable implementation.  
There seems to me to be a cleft stick here (irrespective of whether this 
ends up as informational or experimental.) The WG is is specifying 
pieces of functionality that go in two or more different types of boxes 
(three if there is a separate implementation of the central decision 
point). If the system is going to be generally deployable or even to be 
experimented with there may be different implementations.  The box types 
communicate using the information specifications in the doc.  This 
appears to require protocol definitions.  Where they are defined is 
another issue but I feel it has either to be in this doc or in another 
doc referenced from this.  If they aren't specified I can't see that 
anybody will be interested in making commercial implementations.

I see David didn't make any comment about this situation in his write 
up, so maybe I am over reacting.

Regards,
Elwyn





On 13/06/2011 18:04, philip.eardley@bt.com wrote:
> Elwyn,
>
> Thanks for the detailed review.
> A few follow-ups in-line
> Thanks
> phil
>
> --
> Major issues:
> The draft contains partial definitions of two control protocols (egress
> ->  decision point; decision point ->  ingress).  It does not make it
> clear whether the reader is expected to get full definitions of these
> protocols here or whether there will be another document that specifies
> these protocols completely.  As is stands one could build the protocols
> and pretty much guarantee that they would not be interoperable with
> other implementations since message formats are not included although
> high level specs are.  The document needs to be much clearer about what
> is expected to happen here.
>
> [phil] there is another document, " Requirements for Signaling of (Pre-) Congestion Information in a DiffServ Domain" [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requirements-04] that deals with your issue to some extent. It doesn't specify message formats but does at least specify better what information the messages must contain. My understanding is that unfortunately the WG doesn't feel it has the effort to specify these protocols completely.
>
>
> Use of EXP codepoint: My understanding of what is said in RFC 5696 is
> that EXP is supposed to be left for other (non=PCN) systems to use.
> This draft uses it.  Is this sensible? Is this whole draft experimental
> really?
> [phil] the intention of rfc5696 was that the EXP codepoint is for experimental *PCN* encodings - ie beyond the baseline. For instance, the CL behaviour needs separate codepoints for (PCN) threshold-marking and (PCN) excess-traffic-marking&  this would require using the EXP codepoint.
> However...... There is currently some discussion on what PCN encodings to specify beyond the baseline. At the time we wrote the baseline, we envisaged the need for several encodings - however it now seems that one may be enough, in which case there may possibly be just one PCN encoding (ie a revised 5696 that now uses the 01 codepoint), so possibly may be Standards track - ??
> Anyway, i take your point that we need to think about Status.
>
> s3.3.1:
>> [CL-specific] The outcome of the comparison is not very sensitive
>>        to the value of the CLE-limit in practice, because when threshold-
>>        marking occurs it tends to persist long enough that threshold-
>>        marked traffic becomes a large proportion of the received traffic
>>        in a given interval.
> This statement worries me.  It sounds like a characteristic of an
> unstable system.  If the value is that non-critical why are we
> bothering?
>
> [phil] admission control system. imagine the pcn-domain has one bottleneck link. If it can cope with the current number of calls (their bandwidth), then no pkts gets threshold-marked, so the CLE = 0. If there are too many, then all pkts gets threshold-marked, so the CLE = 1. If there is almost exactly the right number of calls, then threshold-marking will tend to be on for a while, then off for a while (perhaps when several flows are transmitting less traffic than normal), so the CLE will jiggle about between 0&  1. If the CLE is<  CLE-limit (say CLE-limit = 0.6&  current CLE = 0.5), when a new call admission request happens to arrive then it gets admitted. But then there's more traffic and it's likely that the CLE will rise to 1 - hence another admission request will get blocked. When a call finishes, then the reverse is true.
>
> Now suppose we had in fact configured CLE-limit = 0.4, then in the scenario above the call request would have been blocked. However, (1) the PCN-domain has only admitted one fewer call, (2) a short time later, either the CLE happens to be lower or a call departs, and then the next admission request is accepted.
>
> All this means that it doesn't matter much exactly what you set CLE-limit to - it barely affects the average number of calls admitted. The argument above is hand-wavy, but lots of simulations have been done that show this is true (I hope i'm representing the results correctly)
> So the lack of sensitivity to CLE-limit seems like a good thing.
>
>
> Minor issues:
>
> s6:  The potential introduction of a centralized decision point appears
> to provide additional attack points beyond the architecture in RFC 5559.
> It appears to me that the requests for information about specific flows
> to the ingress are ighly vulnerable as they (probably) contain all the
> information needed to craft a DoS attack on the flow.
>
> [phil] seems a good point to me
>


-- 
Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
For more information, see http://www.oxfam.org.uk/get_involved/fundraise/walk/ and follow us on Twitter at http://twitter.com/CambOxfamWalk.


From tom111.taylor@bell.net  Tue Jun 14 11:20:15 2011
Return-Path: <tom111.taylor@bell.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 F2A9A11E816D; Tue, 14 Jun 2011 11:20:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.652
X-Spam-Level: 
X-Spam-Status: No, score=-101.652 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, 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 3K-rw4NCh-sx; Tue, 14 Jun 2011 11:20:14 -0700 (PDT)
Received: from blu0-omc2-s35.blu0.hotmail.com (blu0-omc2-s35.blu0.hotmail.com [65.55.111.110]) by ietfa.amsl.com (Postfix) with ESMTP id 6264011E812E; Tue, 14 Jun 2011 11:20:14 -0700 (PDT)
Received: from BLU0-SMTP55 ([65.55.111.72]) by blu0-omc2-s35.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 14 Jun 2011 11:20:13 -0700
X-Originating-IP: [76.70.76.63]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP55DD09E2A668AAAEE411E5D8680@phx.gbl>
Received: from [192.168.2.17] ([76.70.76.63]) by BLU0-SMTP55.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 14 Jun 2011 11:20:12 -0700
Date: Tue, 14 Jun 2011 14:20:12 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Elwyn Davies <elwynd@dial.pipex.com>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk>	<9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net> <4DF7986B.5020108@dial.pipex.com>
In-Reply-To: <4DF7986B.5020108@dial.pipex.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Jun 2011 18:20:13.0214 (UTC) FILETIME=[B3E4D3E0:01CC2ABF]
Cc: pcn@ietf.org, philip.eardley@bt.com, General Area Reviwing Team <gen-art@ietf.org>
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Tue, 14 Jun 2011 18:20:15 -0000

Well, Elwyn, here's the problem: apparently the likelihood of these ever 
being deployed is vanishingly small. So a protocol could be defined, but 
it would be wasted effort. (It's also outside the PCN charter, most 
likely because RSVP was supposed to be the transport. But that's another 
story ...)

In fact, I and a couple of others started to define a Diameter 
application to do the job. I'm not sure how realistic that would have 
been, in terms of messaging load. Diameter transport is supposed to be 
over TLS these days.

Tom T.

On 14/06/2011 1:20 PM, Elwyn Davies wrote:
> Hi, Phil.
>
> It strikes me that the first and second points below are something which
> David Harrington perhaps ought to give an opinion on. He has got to
> defend it to the IESG.
>
> On the first point, my feeling is that neither the requirements doc nor
> this doc is sufficient to guarantee an interoperable implementation.
> There seems to me to be a cleft stick here (irrespective of whether this
> ends up as informational or experimental.) The WG is is specifying
> pieces of functionality that go in two or more different types of boxes
> (three if there is a separate implementation of the central decision
> point). If the system is going to be generally deployable or even to be
> experimented with there may be different implementations. The box types
> communicate using the information specifications in the doc. This
> appears to require protocol definitions. Where they are defined is
> another issue but I feel it has either to be in this doc or in another
> doc referenced from this. If they aren't specified I can't see that
> anybody will be interested in making commercial implementations.
>
> I see David didn't make any comment about this situation in his write
> up, so maybe I am over reacting.
>
> Regards,
> Elwyn
>
>
...

From violeta.cakulev@alcatel-lucent.com  Tue Jun 14 12:11:20 2011
Return-Path: <violeta.cakulev@alcatel-lucent.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BED811E80D3; Tue, 14 Jun 2011 12:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.449
X-Spam-Level: 
X-Spam-Status: No, score=-5.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, 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 tGs9JUJYGz+j; Tue, 14 Jun 2011 12:11:19 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id E97C61F0C38; Tue, 14 Jun 2011 12:11:18 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p5EJBG9S008898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 14 Jun 2011 14:11:16 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p5EJB98T014009 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 14 Jun 2011 14:11:16 -0500
Received: from USNAVSXCHMBSA3.ndc.alcatel-lucent.com ([135.3.39.126]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Tue, 14 Jun 2011 14:11:09 -0500
From: "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
To: Ben Campbell <ben@nostrum.com>, "draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Date: Tue, 14 Jun 2011 14:11:08 -0500
Thread-Topic: Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
Thread-Index: AcwiKj7iku9VGVqtSm+aoaC5QK0s2QImgLkw
Message-ID: <AAE76B481E7A0E4C96610790A852B9A6250A4F81A5@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
References: <5E434E92-2EB7-43B3-A29F-8410B1AC23AE@nostrum.com>
In-Reply-To: <5E434E92-2EB7-43B3-A29F-8410B1AC23AE@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
X-Mailman-Approved-At: Tue, 14 Jun 2011 12:12:39 -0700
Cc: The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-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, 14 Jun 2011 19:11:20 -0000

Ben,
Thanks for the comments.
Please see inline [VC].

-Violeta

-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com]
Sent: Friday, June 03, 2011 4:10 PM
To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org; gen-art@ietf.org=
 Review Team
Cc: The IETF
Subject: Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07

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-dime-ikev2-psk-diameter-07
Reviewer: Ben Campbell
Review Date: 2011-06-03
IETF LC End Date: 2011-06-03


Summary:

This draft is almost ready for publication as a proposed standard. I have a=
 question concerning the procedure for generating PSKs, and a number of min=
or and editorial comments.


Major issues:

The draft says that the procedure that the HAAA follows to generate the PSK=
 is out of scope. But doesn't the IKE2 initiator need to understand the pro=
cedure? If the procedure is not defined somewhere, how you achieve any degr=
ee of interoperability?
[VC] Indeed the IKEv2 initiator needs to understand the procedure. However,=
 this draft focuses on IKEv2 server, as a Diameter client, to the Diameter =
server communication for IKEv2 with pre-shared key based authentication, an=
d specifies Diameter application for this communication. It is left to spec=
ifications that make use of this Diameter application to specify where the =
PSK comes from and how it is generated. There are two 3GPP2 specs that make=
 use of this Diameter application and both of those specs specify generatio=
n of the PSK. Statements to clarify this are added in v8.


Minor issues:

-- section 4.1, 1st paragraph:"The IDi payload extracted from the IKE_AUTH =
message MUST contain an identity that is meaningful for the Diameter infras=
tructure, such as a Network Access Identifier (NAI), since it is used by th=
e IKEv2 Server to populate the User-Name AVP in the Diameter message. "

Do you mean that as a normative MUST, or a statement of fact? If normative,=
 isn't that a requirement on the initiator?
[VC] Good point. It is changed to statement of fact in v8.

-- section 10:

The security considerations should describe the threat models. We're talkin=
g about requesting an authentication key from a third party, which is trick=
y from a security perspective. Does the PSK have greater security concerns =
than for Diameter AVPs in general? In particular, what are the consequences=
 if the PSK is disclosed or tampered with?
[VC] If the PSK is disclosed to an adversary then it would present a securi=
ty breach.  Hence we recommend that the PSK be short-lived.  As well,
the assumption is that the IKEv2 Server and the Diameter Server where the P=
SK is generated are in a trusted relationship. They may be in the same Admi=
nistrative domain (typical case) or third party but nevertheless there is a=
 trust relationship between them.  As such we assume that there is an appro=
priate security mechanism to protect the communication between these server=
s.  For example the IKEV2 Server and the Diameter server would be deployed =
in the same secure network or would utilize transport layer security as spe=
cified by Diameter 3588 specification. We added statements in v8 to reflect=
 this.

-- section 10, 1st paragraph: "Furthermore, any agents that process IKEv2-P=
SK-Answer messages can see the contents of the Key AVP. For this reason, th=
is specification strongly recommends avoiding Diameter agents when they can=
not be trusted to keep the keys secret."

Should that be normative? Is there no way to protect the PSK AVP from diame=
ter agents? E.g. can it be encrypted?
[VC] It is hard to use normative text here as this application can be used =
for many uses cases. Depending on the use case it may be possible to encryp=
t the PSK, however it is not possible to make it a requirement.

-- section 10, 2nd paragraph: "this specification also recommends the use o=
f nonces included in IKEv2-PSK-Request."

Actually, the spec requires it using a normative SHALL.
[VC] In v8 it is aligned as 'recommended' throughout the document.


Nits/editorial comments:

-- IDNits reports an out-of-date reference
[VC] I missed this one in v8. This will be fixed in v9.

-- Section 1, general:

It's probably worth elaborating that we are talking about a PSK used during=
 the IKEv2 authentication process, which is distinct from any shared secret=
s negotiated by IKE for use in the resulting SA.
[VC] In v8 there are statements clarifying that it is a PSK used for IKEv2 =
authentication.


-- Section 1, paragraph 1, 1st sentence:

The use, and lack of, commas in this sentence is confusing. It's easy to pa=
rse as saying IKE2 is a protocol and a set of algorithms, when I think you =
meant to say that the resulting SA has a set of algorithms along with the s=
hared secret.
[VC] Changed in v8 to 'The Internet Key Exchange version 2 (IKEv2) protocol=
 [RFC5996] is
   used to mutually authenticate two parities and to establish a
   security association (SA) that can be used to efficiently secure the
   communication between the IKEv2 Peer and Server, for example, using
   Encapsulating Security Payload (ESP) [RFC4303] and/or Authentication
   Header (AH) [RFC4302].'

-- section 4.1, 2nd paragraph: "message is routed to the IKEv2 Peer's HAAA.=
"

What routes it? ( be careful not to let passive voice obscure responsibilit=
ies)
[VC] Changed in v8 to 'The IKEv2 Server sends the IKEv2-PSK-Request message=
 to the IKEv2
   Peer's HAAA.'

-- section 4.2, paragraph 1: "The HAAA may maintain state or may be statele=
ss"

What kind of state? I assume from the following sentences you mean Diameter=
 session state, but it should be explicit.
[VC] Changed in v8 to 'The HAAA may maintain Diameter session state or may =
be stateless.'

-- "indicated by presence or absence of the Auth-Session-State AVP."

In what message(s)?
[VC] This is clarified by adding that it is the Answer message.

-- section 4.2, paragraph 2:

This sentence is long and hard to parse. Can it be broken up?
[VC] Based on some other comments this sentence is removed.

-- section 5.1, last paragraph: "SHALL be used to identify the appropriate =
PSK."

Shall be used by what? (passive voice obscures responsibility)
[VC] Changed in v8 to 'If
   included, it contains the Security Parameter Index (SPI) that HAAA
   SHALL use to identify the appropriate PSK.'

-- 5.2, last paragraph: "associated key SHALL NOT be used if the lifetime h=
as expired."

SHALL NOT be used by what?
[VC] In v8 changed to: 'The Key-Lifetime AVP may be
   included and if it is included then the associated key SHALL NOT be
   used by the receiver of the answer if the lifetime has expired.'

-- section 8, first paragraph: "whether the AVP MAY be encrypted."

I don't see anything about encryption in the table.
[VC] The text referring to encryption is deleted.

-- section 8, AVP table:

Are all the Key* AVPs intended to have the same code? I assume not, but mix=
ing in TBD with the various TBD* placeholders is confusing.
[VC] These AVPs are being defined in another ietf draft that has not been p=
ublished yet. There is Note 1 clarifying it.


-- section 9:

Consider a note to the RFC editor to change all occurances of TBD(x) with t=
he IANA assignment throughout the entire document. Since these are scattere=
d throughout the doc, the intent may not be obvious to them.
[VC] We will do that.


From ben@nostrum.com  Wed Jun 15 09:02:07 2011
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 084F411E811F; Wed, 15 Jun 2011 09:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KI5KxCeqSMNJ; Wed, 15 Jun 2011 09:02:06 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8854311E8081; Wed, 15 Jun 2011 09:02:04 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5FG1tDE090642 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 15 Jun 2011 11:01:56 -0500 (CDT) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <AAE76B481E7A0E4C96610790A852B9A6250A4F81A5@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
Date: Wed, 15 Jun 2011 11:01:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A6A10F5-5C34-494A-B922-EAB9DDE73551@nostrum.com>
References: <5E434E92-2EB7-43B3-A29F-8410B1AC23AE@nostrum.com> <AAE76B481E7A0E4C96610790A852B9A6250A4F81A5@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
To: "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-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, 15 Jun 2011 16:02:07 -0000

Thanks for the response. Comments inline. I deleted sections that appear =
not to need further discussion.

Thanks!

Ben.

On Jun 14, 2011, at 2:11 PM, Cakulev, Violeta (Violeta) wrote:

>=20
> Ben,
> Thanks for the comments.
> Please see inline [VC].
>=20
> -Violeta
>=20
> -----Original Message-----
> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Friday, June 03, 2011 4:10 PM
> To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org; =
gen-art@ietf.org Review Team
> Cc: The IETF
> Subject: Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-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>.
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-dime-ikev2-psk-diameter-07
> Reviewer: Ben Campbell
> Review Date: 2011-06-03
> IETF LC End Date: 2011-06-03
>=20
>=20
> Summary:
>=20
> This draft is almost ready for publication as a proposed standard. I =
have a question concerning the procedure for generating PSKs, and a =
number of minor and editorial comments.
>=20
>=20
> Major issues:
>=20
> The draft says that the procedure that the HAAA follows to generate =
the PSK is out of scope. But doesn't the IKE2 initiator need to =
understand the procedure? If the procedure is not defined somewhere, how =
you achieve any degree of interoperability?
> [VC] Indeed the IKEv2 initiator needs to understand the procedure. =
However, this draft focuses on IKEv2 server, as a Diameter client, to =
the Diameter server communication for IKEv2 with pre-shared key based =
authentication, and specifies Diameter application for this =
communication. It is left to specifications that make use of this =
Diameter application to specify where the PSK comes from and how it is =
generated. There are two 3GPP2 specs that make use of this Diameter =
application and both of those specs specify generation of the PSK. =
Statements to clarify this are added in v8.

The effect of this is that this spec, as written, cannot be implemented =
in an interoperable way. I don't think that meets the usual expectations =
for a proposed standard. Now, I realize there are some situations where =
the IETF has chosen this approach, and deliberately created a standards =
track RFC that must be profiled for actual use--but hopefully that's the =
exception rather than the rule.  I guess it's up to the IESG to decide =
if that is reasonable in this instance. (I'm explicitly not counting =
situations where the IETF puts out a standard as a series of modular =
RFCs, since I gather there's no immediate intent to publish PSK =
generation RFCs.)

Additionally, whether or not PSK generation mechanisms are specified in =
the IETF vs somewhere else, how does an implementation (that might =
support more than one such mechanism) know which to use for any given =
SA? Is there a negotiation mechanism?

>=20
>=20
> Minor issues:
>=20

[...]

> -- section 10:
>=20
> The security considerations should describe the threat models. We're =
talking about requesting an authentication key from a third party, which =
is tricky from a security perspective. Does the PSK have greater =
security concerns than for Diameter AVPs in general? In particular, what =
are the consequences if the PSK is disclosed or tampered with?
> [VC] If the PSK is disclosed to an adversary then it would present a =
security breach.  Hence we recommend that the PSK be short-lived.  As =
well,
> the assumption is that the IKEv2 Server and the Diameter Server where =
the PSK is generated are in a trusted relationship. They may be in the =
same Administrative domain (typical case) or third party but =
nevertheless there is a trust relationship between them.  As such we =
assume that there is an appropriate security mechanism to protect the =
communication between these servers.  For example the IKEV2 Server and =
the Diameter server would be deployed in the same secure network or =
would utilize transport layer security as specified by Diameter 3588 =
specification. We added statements in v8 to reflect this.

Thanks, that probably helps (pending seeing the actual text).

>=20
> -- section 10, 1st paragraph: "Furthermore, any agents that process =
IKEv2-PSK-Answer messages can see the contents of the Key AVP. For this =
reason, this specification strongly recommends avoiding Diameter agents =
when they cannot be trusted to keep the keys secret."
>=20
> Should that be normative? Is there no way to protect the PSK AVP from =
diameter agents? E.g. can it be encrypted?
> [VC] It is hard to use normative text here as this application can be =
used for many uses cases. Depending on the use case it may be possible =
to encrypt the PSK, however it is not possible to make it a requirement.

I don't see why a "SHOULD" or "RECOMMENDED" would cause problems here, =
along with some short explanation of why it might not always be =
possible. Otherwise, the text says "strongly recommends", when, without =
normative text, such recommendation is really pretty weak.

>=20
> -- section 10, 2nd paragraph: "this specification also recommends the =
use of nonces included in IKEv2-PSK-Request."
>=20
> Actually, the spec requires it using a normative SHALL.
> [VC] In v8 it is aligned as 'recommended' throughout the document.
>=20

I'm curious why you chose to weaken the rest of the text, vs =
strengthening the comment in the security considerations? (Also, is that =
"recommended" or "RECOMMENDED"?)

> Nits/editorial comments:
>=20

[...]

> -- section 8, first paragraph: "whether the AVP MAY be encrypted."
>=20
> I don't see anything about encryption in the table.
> [VC] The text referring to encryption is deleted.
>=20

So how does an implementor know if it can be encrypted?

[...]=

From avi@bridgewatersystems.com  Wed Jun 15 11:00:06 2011
Return-Path: <avi@bridgewatersystems.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 63F6911E8089; Wed, 15 Jun 2011 11:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186,  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 sf6+x4fysW7G; Wed, 15 Jun 2011 11:00:05 -0700 (PDT)
Received: from mail51.messagelabs.com (mail51.messagelabs.com [216.82.241.99]) by ietfa.amsl.com (Postfix) with ESMTP id BC33B11E8081; Wed, 15 Jun 2011 11:00:04 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-4.tower-51.messagelabs.com!1308160803!54325837!1
X-StarScan-Version: 6.2.17; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 32580 invoked from network); 15 Jun 2011 18:00:03 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-4.tower-51.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jun 2011 18:00:03 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Wed, 15 Jun 2011 14:00:01 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Ben Campbell <ben@nostrum.com>, "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
Date: Wed, 15 Jun 2011 14:00:00 -0400
Thread-Topic: [Gen-art] Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
Thread-Index: AcwrhgvFOik9rUJmTxibBzvGi52JYQ==
Message-ID: <CA1E6771.1A314%avi@bridgewatersystems.com>
In-Reply-To: <4A6A10F5-5C34-494A-B922-EAB9DDE73551@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.12.0.110505
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-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, 15 Jun 2011 18:00:06 -0000

Hi Ben,

Please see inline...

-- Avi Lior
--Bridgewater Systems



>>eview Date: 2011-06-03
>> IETF LC End Date: 2011-06-03
>>=20
>>=20
>> Summary:
>>=20
>> This draft is almost ready for publication as a proposed standard. I
>>have a question concerning the procedure for generating PSKs, and a
>>number of minor and editorial comments.
>>=20
>>=20
>> Major issues:
>>=20
>> The draft says that the procedure that the HAAA follows to generate the
>>PSK is out of scope. But doesn't the IKE2 initiator need to understand
>>the procedure? If the procedure is not defined somewhere, how you
>>achieve any degree of interoperability?
>> [VC] Indeed the IKEv2 initiator needs to understand the procedure.
>>However, this draft focuses on IKEv2 server, as a Diameter client, to
>>the Diameter server communication for IKEv2 with pre-shared key based
>>authentication, and specifies Diameter application for this
>>communication. It is left to specifications that make use of this
>>Diameter application to specify where the PSK comes from and how it is
>>generated. There are two 3GPP2 specs that make use of this Diameter
>>application and both of those specs specify generation of the PSK.
>>Statements to clarify this are added in v8.
>
>The effect of this is that this spec, as written, cannot be implemented
>in an interoperable way. I don't think that meets the usual expectations
>for a proposed standard. Now, I realize there are some situations where
>the IETF has chosen this approach, and deliberately created a standards
>track RFC that must be profiled for actual use--but hopefully that's the
>exception rather than the rule.  I guess it's up to the IESG to decide if
>that is reasonable in this instance. (I'm explicitly not counting
>situations where the IETF puts out a standard as a series of modular
>RFCs, since I gather there's no immediate intent to publish PSK
>generation RFCs.)
>
>Additionally, whether or not PSK generation mechanisms are specified in
>the IETF vs somewhere else, how does an implementation (that might
>support more than one such mechanism) know which to use for any given SA?
>Is there a negotiation mechanism?

I agree with your comments in general. What we need to keep in mind though
is the intent of this draft, which is to deliver the PSK key to the IKEv2
server.  The issues you discuss relating to PSK are issues that are there
with or without this document.  The document uses all the information that
is available in IKEv2 to fetch that PSK and to allow a PSK to be derived
(via the nonces). =20


>
>>=20
>>=20
>> Minor issues:
>>=20
>
>[...]

>[...]
>
>>=20
>> -- section 10, 1st paragraph: "Furthermore, any agents that process
>>IKEv2-PSK-Answer messages can see the contents of the Key AVP. For this
>>reason, this specification strongly recommends avoiding Diameter agents
>>when they cannot be trusted to keep the keys secret."
>>=20
>> Should that be normative? Is there no way to protect the PSK AVP from
>>diameter agents? E.g. can it be encrypted?
>> [VC] It is hard to use normative text here as this application can be
>>used for many uses cases. Depending on the use case it may be possible
>>to encrypt the PSK, however it is not possible to make it a requirement.
>
>I don't see why a "SHOULD" or "RECOMMENDED" would cause problems here,
>along with some short explanation of why it might not always be possible.
>Otherwise, the text says "strongly recommends", when, without normative
>text, such recommendation is really pretty weak.

I may be okay with using stronger terms (SHOULD or RECOMMEND).  I actually
wish now that this entire paragraph be deleted. The reason being is that
the security issues relating to multi-hop Diameter communication is well
understood and documented in 3588 (and we already make a reference to that
document).  I don't see a need for recommendation.

[...]

>> Nits/editorial comments:
>>=20
>
>[...]
>
>> -- section 8, first paragraph: "whether the AVP MAY be encrypted."
>>=20
>> I don't see anything about encryption in the table.
>> [VC] The text referring to encryption is deleted.
>>=20
>
>So how does an implementor know if it can be encrypted?

We used an old style of table which is not really used.  There is no end
to end encryption mechanisms in Diameter.  And Diameter provides transport
level security (integrity and privacy protection).  If the end to end
encryption that is between the Diameter Client (IKEv2 Server) and the
Diameter Server (where the PSK is stored/generated) is needed it would
have to be built on-top of this document - so the implementor will know.

>
>[...]


From miguel.a.garcia@ericsson.com  Thu Jun 16 03:58:59 2011
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 AA37E21F851E for <gen-art@ietfa.amsl.com>; Thu, 16 Jun 2011 03:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.571
X-Spam-Level: 
X-Spam-Status: No, score=-6.571 tagged_above=-999 required=5 tests=[AWL=0.028,  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 fC5smJ-a47Wy for <gen-art@ietfa.amsl.com>; Thu, 16 Jun 2011 03:58:59 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id CE1C521F851C for <gen-art@ietf.org>; Thu, 16 Jun 2011 03:58:58 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c17ae00000262e-4e-4df9e1f10ae0
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 79.E1.09774.1F1E9FD4; Thu, 16 Jun 2011 12:58:58 +0200 (CEST)
Received: from [159.107.24.192] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.137.0; Thu, 16 Jun 2011 12:58:53 +0200
Message-ID: <4DF9E1EC.3040300@ericsson.com>
Date: Thu, 16 Jun 2011 12:58:52 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: <volker.hilt@alcatel-lucent.com>, <eric.noel@att.com>, Charles Shen <charles@cs.columbia.edu>, <aabdelal@sonusnet.com>, Salvatore Loreto <salvatore.loreto@ericsson.com>, Robert Sparks <rjsparks@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-soc-overload-design-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: Thu, 16 Jun 2011 10:58:59 -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-soc-overload-design-06.txt
Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
Review Date: 2011-06-16
IETF LC End Date: 2011-06-14
IESG Telechat date:

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

The document is well written with a clear language.

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

From mahoney@nostrum.com  Thu Jun 16 14:32:23 2011
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 951AA11E8324 for <gen-art@ietfa.amsl.com>; Thu, 16 Jun 2011 14:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UC8OksxMR10u for <gen-art@ietfa.amsl.com>; Thu, 16 Jun 2011 14:32:23 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9023711E8319 for <gen-art@ietf.org>; Thu, 16 Jun 2011 14:32:22 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-49-161.dllstx.fios.verizon.net [71.170.49.161]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5GLWKW1056270 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 16 Jun 2011 16:32:21 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4DFA7664.7000706@nostrum.com>
Date: Thu, 16 Jun 2011 16:32:20 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 71.170.49.161 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2011-06-16
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, 16 Jun 2011 21:32:23 -0000

Hi all,

Here's the link to the new LC assignments:
http://wiki.tools.ietf.org/dav/genart/reviewers-110616-lc.html

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 Jun 16 14:54:08 2011
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 1079711E814E for <gen-art@ietfa.amsl.com>; Thu, 16 Jun 2011 14:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DEYmW+UFZp70 for <gen-art@ietfa.amsl.com>; Thu, 16 Jun 2011 14:54:07 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1B47C11E80CF for <gen-art@ietf.org>; Thu, 16 Jun 2011 14:54:06 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-49-161.dllstx.fios.verizon.net [71.170.49.161]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5GLs4IW058153 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 16 Jun 2011 16:54:04 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4DFA7B7C.2020302@nostrum.com>
Date: Thu, 16 Jun 2011 16:54:04 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 71.170.49.161 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2011-06-23 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, 16 Jun 2011 21:54:08 -0000

Hi all,

Assignments for the telechat can be found here:
http://wiki.tools.ietf.org/dav/genart/reviewers-110623-telechat.html

With the updated 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 Jun 16 20:05:31 2011
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 9AAAF21F8511 for <gen-art@ietfa.amsl.com>; Thu, 16 Jun 2011 20:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 4u5ajkA5rq3I for <gen-art@ietfa.amsl.com>; Thu, 16 Jun 2011 20:05:31 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob-ipv6.tigertech.net [IPv6:2604:4f00::1:0:0:22]) by ietfa.amsl.com (Postfix) with ESMTP id 02E5A21F850B for <gen-art@ietf.org>; Thu, 16 Jun 2011 20:05:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 225BF3245882; Thu, 16 Jun 2011 20:05:30 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-44.clppva.btas.verizon.net [71.161.50.44]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 9BAE43245802; Thu, 16 Jun 2011 20:05:29 -0700 (PDT)
Message-ID: <4DFAC477.3000107@joelhalpern.com>
Date: Thu, 16 Jun 2011 23:05:27 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>,  General Area Review Team <gen-art@ietf.org>
References: <AANLkTin0WX-ziACaGAhYWvRFLVhnr17pdfVFcfhox_j+@mail.gmail.com>	<AANLkTinUNGqP_6K4geFsLtLGtLg6+VXiikOxQqiSfrJy@mail.gmail.com>
In-Reply-To: <AANLkTinUNGqP_6K4geFsLtLGtLg6+VXiikOxQqiSfrJy@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art]  [gen-art] review: draft-ietf-fecframe-framework-15.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, 17 Jun 2011 03:05:31 -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-fecframe-framework-15.txt
     Forward Error Correction (FEC) Framework
Reviewer: Joel M. Halpern
Review Date: 16-June-2011
IESG Telechat date: 22=June-2011

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

Major issues: None

Minor issues:
    None, my earlier concerns have all been well-addressed.

From mccap@petoni.org  Fri Jun 17 08:31:09 2011
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 D67DC11E817D for <gen-art@ietfa.amsl.com>; Fri, 17 Jun 2011 08:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBCSdv6m1NUT for <gen-art@ietfa.amsl.com>; Fri, 17 Jun 2011 08:31:09 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id DB4E111E8179 for <gen-art@ietf.org>; Fri, 17 Jun 2011 08:31:08 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2100946fxm.31 for <gen-art@ietf.org>; Fri, 17 Jun 2011 08:31:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.98.4 with SMTP id o4mr2654411fan.120.1308324666081; Fri, 17 Jun 2011 08:31:06 -0700 (PDT)
Received: by 10.223.54.88 with HTTP; Fri, 17 Jun 2011 08:31:06 -0700 (PDT)
X-Originating-IP: [64.53.131.166]
Date: Fri, 17 Jun 2011 10:31:06 -0500
Message-ID: <BANLkTinE1rYQ-v5aQ6QKugPwX_Oi0EmUUA@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-dkim-mailinglists.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-dkim-mailinglists-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 15:31:10 -0000

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

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


Document: draft-ietf-dkim-mailinglists-11
Reviewer: Pete McCann
Review Date: 2011-06-06
IETF LC End Date: 2011-06-17
IESG Telechat date: 2011-06-23

Summary:  Ready

Major issues: None

Minor issues:

Section 5.6: in general, the techniques outlined in this
section could be used by any recipient, not just MLMs.
Perhaps this is how ADSP should have been specified.


Nits/Editorial:

Section 3.3:
   resending MLM typically make
SHOULD BE:
   resending MLM typically makes

   Therefore not seen
SHOULD BE:
   Therefore this is not seen

Section 5.6:
   would have accommodate
SHOULD BE:
   would have to accommodate

From mccap@petoni.org  Fri Jun 17 11:02:16 2011
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 8771A11E8146 for <gen-art@ietfa.amsl.com>; Fri, 17 Jun 2011 11:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lMXiPQg+gIgz for <gen-art@ietfa.amsl.com>; Fri, 17 Jun 2011 11:02:15 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 800F211E8118 for <gen-art@ietf.org>; Fri, 17 Jun 2011 11:02:15 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2187249fxm.31 for <gen-art@ietf.org>; Fri, 17 Jun 2011 11:02:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.111.132 with SMTP id s4mr2892267fap.6.1308333732931; Fri, 17 Jun 2011 11:02:12 -0700 (PDT)
Received: by 10.223.54.88 with HTTP; Fri, 17 Jun 2011 11:02:12 -0700 (PDT)
X-Originating-IP: [64.53.131.166]
Date: Fri, 17 Jun 2011 13:02:12 -0500
Message-ID: <BANLkTi=S1Vn_GMOFnOTWby7Vtq4TyFJdeA@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-sipcore-location-conveyance-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: Fri, 17 Jun 2011 18:02: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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-sipcore-location-conveyance-08
Reviewer: Pete McCann
Review Date: June 17 2011
IETF LC End Date:
IESG Telechat date: June 23 2011

Summary: Ready

Major issues: none

Minor issues: none

Nits/editorial comments:

Section 3:
   therefore any of the diagrams the SIP intermediary receives the SIP
   request is potentially an LR
SHOULD BE:
   therefore in any of the diagrams the SIP intermediary that receives the SIP
   request is potentially an LR

Section 3.3:
   in order to be location recipient
SHOULD BE:
   in order to be a location recipient

   It could be the case that
   a SIP intermediary which does not perform location-based routing but
   does care when Alice includes her location;
SHOULD BE:
   It could be the case that
   a SIP intermediary which does not perform location-based routing
   does care when Alice includes her location;

From msk@cloudmark.com  Fri Jun 17 11:32:26 2011
Return-Path: <msk@cloudmark.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 242FE9E8011 for <gen-art@ietfa.amsl.com>; Fri, 17 Jun 2011 11:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.143
X-Spam-Level: 
X-Spam-Status: No, score=-103.143 tagged_above=-999 required=5 tests=[AWL=-0.544, 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 yagWZkPmH+82 for <gen-art@ietfa.amsl.com>; Fri, 17 Jun 2011 11:32:25 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 9A6DF9E8010 for <gen-art@ietf.org>; Fri, 17 Jun 2011 11:32:25 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Fri, 17 Jun 2011 11:32:25 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Pete McCann <mccap@petoni.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dkim-mailinglists.all@tools.ietf.org" <draft-ietf-dkim-mailinglists.all@tools.ietf.org>
Date: Fri, 17 Jun 2011 11:32:24 -0700
Thread-Topic: Gen-ART Telechat Review of draft-ietf-dkim-mailinglists-11
Thread-Index: AcwtA5ugtlGkhGPTT+W/1yXngqMIuwAFvE2g
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC488F@EXCH-C2.corp.cloudmark.com>
References: <BANLkTinE1rYQ-v5aQ6QKugPwX_Oi0EmUUA@mail.gmail.com>
In-Reply-To: <BANLkTinE1rYQ-v5aQ6QKugPwX_Oi0EmUUA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 17 Jun 2011 12:19:51 -0700
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-dkim-mailinglists-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 18:32:26 -0000

> -----Original Message-----
> From: Pete McCann [mailto:mccap@petoni.org]
> Sent: Friday, June 17, 2011 8:31 AM
> To: gen-art@ietf.org; draft-ietf-dkim-mailinglists.all@tools.ietf.org
> Subject: Gen-ART Telechat Review of draft-ietf-dkim-mailinglists-11
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.

Hi Pete,

> Section 5.6: in general, the techniques outlined in this
> section could be used by any recipient, not just MLMs.
> Perhaps this is how ADSP should have been specified.

A lot of this document reveals operational experience gained since ADSP was=
 published, so you're probably right about these points (unfortunately).

> Section 3.3:
>    resending MLM typically make
> SHOULD BE:
>    resending MLM typically makes

Fixed.

>    Therefore not seen
> SHOULD BE:
>    Therefore this is not seen

Fixed.

> Section 5.6:
>    would have accommodate
> SHOULD BE:
>    would have to accommodate

Fixed.

Thank you!

-MSK


From ben@nostrum.com  Fri Jun 17 12:24:36 2011
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 0C7589E8030; Fri, 17 Jun 2011 12:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=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 f3Uimor1-TP8; Fri, 17 Jun 2011 12:24:35 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 144E19E8023; Fri, 17 Jun 2011 12:24:34 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5HJOW66076206 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 17 Jun 2011 14:24:33 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Jun 2011 14:24:32 -0500
Message-Id: <AE70A313-F36C-4870-A0E8-8F3172F35D53@nostrum.com>
To: draft-ietf-v6ops-6to4-to-historic.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-v6ops-6to4-to-historic-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 19:24: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>.

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

Document: draft-ietf-v6ops-6to4-to-historic-04
Reviewer: Ben Campbell
Review Date: 2011-06-17
IETF LC End Date: 2011-06-20
IESG Telechat date: 2011-06-23

Summary:

The draft is essentially ready for publication as an informational RFC. =
I have a few editorial comments that may be worth considering prior to =
final publication.

Major issues: None

Minor issues: None

Nits/editorial comments:

-- general:=20

Idnits reports some potential issues. please check.

-- abstract:

The headers say this draft obsoletes these RFCs. Does moving to =
historical obsolete then in that sense? Perhaps the abstract should say =
something like "obsoletes, and moves to historical"

-- section 1, 2nd paragraph: "...designed to help transitioning the =
Internet..."

Help transition, help in transitioning, or help the transition of

-- section 1, last paragraph:

Please expand 6rd on first mention. Also, Is this meant as an explicit =
recommendation of 6rd as an alternative?

-- section 3, third paragraph: "...same operational burden has manually =
configured tunnels..."

s/has/as

-- section 3, first bullet: "... and in the case the relay is overloaded =
packet loss."

"overloaded, packet loss."

-- section 3, third bullet: "...customer relationship or..."

"... customer relationship between the end-user and the relay operator, =
or..."

-- section 3, 4th bullet: "In case of the reverse path 6to4 relay and =
the anycast forward 6to4 relay, these have to be open for any address. =
Only limited by the scope of the routing advertisement. "

Awkward sentence followed by a sentence fragment. Can these be reworded?

-- section 3, 5th bullet: "black hole"

Please define "black hole" in this context, or use a more descriptive =
(I.e. less jargony) term.


-- section 4, 2nd paragraph: "It is expected that disabling 6to4 in the =
IPv6 Internet will take some time."

Who expects it? The IETF? v6ops? The authors? (or can we just drop "It =
is expected that")

"...deploy native IPv6 service."

s/service/services

-- section 4, numbered list:

It's not clear to me why this is a numbered list rather than an ordinary =
paragraph


From ben@nostrum.com  Fri Jun 17 14:44:32 2011
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 C75C711E80B9; Fri, 17 Jun 2011 14:44:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level: 
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, 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 I9K9QUcW5Y6g; Fri, 17 Jun 2011 14:44:32 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DABA311E807F; Fri, 17 Jun 2011 14:44:31 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5HLiTHI088638 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 17 Jun 2011 16:44:30 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Jun 2011 16:44:29 -0500
Message-Id: <11976922-3BC1-4094-9F6C-D287DD5D0926@nostrum.com>
To: draft-law-rfc4869bis.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-law-rfc4869bis-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: Fri, 17 Jun 2011 21:44:32 -0000

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

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

Document: draft-law-rfc4869bis-01
Reviewer: Ben Campbell=09
Review Date: 2011-06-17
IETF LC End Date: 2011-06-13

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


Major issues: None

Minor issues: None

Nits/editorial comments:

-- section 4, 2nd paragraph:

Is this paragraph intended to recommend any specific action for =
implementors?=

From suresh.krishnan@ericsson.com  Fri Jun 17 14:58:19 2011
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 1BF1811E811B for <gen-art@ietfa.amsl.com>; Fri, 17 Jun 2011 14:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.507
X-Spam-Level: 
X-Spam-Status: No, score=-106.507 tagged_above=-999 required=5 tests=[AWL=0.092, 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 t-ca0vn+du+U for <gen-art@ietfa.amsl.com>; Fri, 17 Jun 2011 14:58:18 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id 51ACE11E807F for <gen-art@ietf.org>; Fri, 17 Jun 2011 14:58:18 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p5HLo2pP007343; Fri, 17 Jun 2011 16:50:06 -0500
Received: from [142.133.10.107] (147.117.20.214) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.3.137.0; Fri, 17 Jun 2011 17:49:59 -0400
Message-ID: <4DFBCAF6.60304@ericsson.com>
Date: Fri, 17 Jun 2011 17:45:26 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-l3vpn-mvpn-infra-addrs.all@tools.ietf.org" <draft-ietf-l3vpn-mvpn-infra-addrs.all@tools.ietf.org>
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-l3vpn-mvpn-infra-addrs-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, 17 Jun 2011 21:58:19 -0000

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

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

Document: draft-ietf-l3vpn-mvpn-infra-addrs-04.txt
Reviewer: Suresh Krishnan
Review Date: 2011/06/17
IESG Telechat date: 2011/06/23

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

Thanks
Suresh



From ben@nostrum.com  Fri Jun 17 15:10:59 2011
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 1B63411E8122; Fri, 17 Jun 2011 15:10:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, 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 OnYW0CVAmnUD; Fri, 17 Jun 2011 15:10:58 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 23F2211E807F; Fri, 17 Jun 2011 15:10:56 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5HMAsQx091038 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 17 Jun 2011 17:10:55 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Jun 2011 17:10:54 -0500
Message-Id: <EEBDA95D-FC72-4498-A9D1-D7F4E7596314@nostrum.com>
To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-dime-ikev2-psk-diameter-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: Fri, 17 Jun 2011 22:10:59 -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-dime-ikev2-psk-diameter-08
Reviewer: Ben Campbell
Review Date: 2011-06-17
IESG Telechat date: 2011-06-23

Summary: This draft is almost ready for publication as a proposed =
standard. I still have a concern about the generation of the PSK.

Major issues:

In my initial Gen-ART review, I made the following comment: The draft =
says that the procedure that the HAAA follows to generate the PSK is out =
of scope. But doesn't the IKE2 initiator need to understand the =
procedure? If the procedure is not defined somewhere, how you achieve =
any degree of interoperability?

The author responded that the PSK generation was in fact important for =
interoperability, but that the specific procedures have been =
intentionally left to other specifications. It is up to specifications =
that use this Diameter application to define the PSK generation =
mechanism. Further, the author indicated 2 3GPP2 specs that have done =
this.

I am still concerned that this means that this specification cannot be =
implemented in an interoperable way without effectively profiling it. =
There is no apparent coordination on how such profiling may be done, and =
by whom. I think this is likely to result in implementation islands that =
can't talk to each other. I recognize that there is precedent for doing =
this, but I think it is something that should not be done without =
careful consideration, particularly in a standards track RFC. I leave it =
to the IESG to confirm whether it is appropriate in this circumstance.

I further note that there is  no apparent way to negotiate or declare =
what PSK generation mechanism might be used, if an implementation =
supports more than one.

Minor Issues: None
Editorial Comments: None



From alexey.melnikov@isode.com  Fri Jun 17 15:22:43 2011
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 469D911E8146; Fri, 17 Jun 2011 15:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z9S7Rvqu4F3d; Fri, 17 Jun 2011 15:22:42 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 50E0311E812F; Fri, 17 Jun 2011 15:22:33 -0700 (PDT)
Received: from [192.168.20.2] ((unknown) [212.183.140.0])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TfvTowA-uUmo@rufus.isode.com>; Fri, 17 Jun 2011 23:22:29 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4DFBD34B.7000900@isode.com>
Date: Fri, 17 Jun 2011 23:20:59 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: draft-burgin-ipsec-suiteb-profile.all@tools.ietf.org
References: <4D9C8D2A.7080605@nostrum.com>
In-Reply-To: <4D9C8D2A.7080605@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, iesg@ietf.org
Subject: [Gen-art] Gen-Art Last Call Review: draft-burgin-ipsec-suiteb-profile-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: Fri, 17 Jun 2011 22:22:43 -0000

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

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

Document: draft-burgin-ipsec-suiteb-profile-00
Reviewer: Alexey Melnikov
Review Date: 17-June-2011
IETF LC End Date: 13-July-2011
IESG Telechat

Summary: not ready, but issues are not difficult to address

Major issues:

4.3.  Suite B IKEv2 Authentication

    If configured at a minimum level of security of 128 bits, a system
    MUST use either ECDSA-256 or ECDSA-384 for IKE authentication.  It
    is allowable for one party to authenticate with ECDSA-256 and the
    other party to authenticate with ECDSA-384.  This flexibility will
    allow interoperability between an initiator and a responder that
    have different sizes of ECDSA authentication keys.

    Initiators and responders in a system configured at a minimum level
    of security of 128 bits MUST be able to verify ECDSA-256 signatures
    and SHOULD be able to verify ECDSA-384 signatures.

The last SHOULD seems to mean that at the minimum level of security of 
128 bits
it is possible to have a situation when a responder might be unable
to verify ECDSA-384 signatures used by an initiator.

Is this truly desirable?


5.  Suite B Security Associations (SAs) for IKEv2 and IPsec

    An initiator in a system configured at a minimum level of security
    of 128 bits MUST offer one or more of the four suites:
    Suite-B-GCM-128, Suite-B-GMAC-128, Suite-B-GCM-256 or
    Suite-B-GMAC-256 [RFC4869bis].  Suite-B-GCM-128 and
    Suite-B-GMAC-128, if offered, must appear in the IKEv2 and IPsec SA
    payloads before any offerings of Suite-B-GCM-256 and
    Suite-B-GMAC-256.

Does this mean that the responder needs to support all 4?
I think it does (or otherwise there is a chance of non interoperability),
but it would be better to state that explicitly.

    A responder configured in a system at a minimum level of security
    of 128 bits SHOULD accept the first Suite B UI suite offered by the

Is this a new requirement in this document, or is this repeating a 
general requirement stated in another document? If the latter, a 
reference is needed here, ideally accompanied by some text stating that 
the requirement comes from another document.

Similar text later in the same section.

    initiator that it can accommodate.  If none of the four suites are
    offered, the responder MUST return a Notify payload with the error
    "NO_PROPOSAL_CHOSEN".

8.  Additional Requirements

    Suite B IPsec compliant systems MUST support IKEv2 and MUST NOT use
    IKEv1.  However, to accommodate backward compatibility, a Suite B
    IPsec compliant system can be configured to use IKEv1 so long as only
    IKEv2 is used between a Suite B compliant initiator and responder.

You lost me here. Can you please explain what is the meaning of
the second sentence?

    The administrative user interface, (UI), for a system that conforms
    to this profile MUST allow the operator to specify a single suite.
    If only one suite is specified in the administrative UI, the IKEv2
    implementation MUST only offer algorithms for that one suite.

This requirement is unusual, because IETF documents rarely have 
requirements on UIs. Can you please elaborate what is this trying to 
achieve?


Minor issues:

3.  Suite B Requirements

       Curve        NIST name       SECG name   IANA assigned DH group #
       -----------------------------------------------------------------
       P-256       nistp256        secp256r1               19
       P-384       nistp384        secp384r1               20

This doesn't tell where to look for the IANA assigned DH group.
An Informative reference would be nice.

10.  IANA Considerations

    TBD.

I think this needs to be replaced with a statement saying that this 
document doesn't require any new actions from IANA, because all 
algorithm are already registered in RFCs referenced by this document.


idnits 2.12.12 reports:

   Miscellaneous warnings:
 
----------------------------------------------------------------------------

   -- The document has a disclaimer for pre-RFC5378 work, but was first
      submitted on or after 10 November 2008.  Does it really need the
      disclaimer?

Please double check that that is intentional.


Nits/editorial comments:

7.  Generating Keying Material for the IKE SA

    IKEv2, [RFC5996], allows for the reuse of Diffie-Hellman ephemeral
    keys. Section 5.6.4.3 of NIST SP800-56A states that an ephemeral
    private key MUST be used in exactly one key establishment
    transaction and MUST be zeroized after its use.

Is "zeroized" a correct verb?



From Francis.Dupont@fdupont.fr  Sat Jun 18 15:00:29 2011
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 A847D11E80E2 for <gen-art@ietfa.amsl.com>; Sat, 18 Jun 2011 15:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-MTklaNy0+M for <gen-art@ietfa.amsl.com>; Sat, 18 Jun 2011 15:00:29 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id DF55211E80BC for <gen-art@ietf.org>; Sat, 18 Jun 2011 15:00:28 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p5IM0RpQ031229; Sun, 19 Jun 2011 00:00:27 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201106182200.p5IM0RpQ031229@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Sun, 19 Jun 2011 00:00:27 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-savi-fcfs.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-savi-fcfs-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 22:00: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-savi-fcfs-09.txt
Reviewer: Francis Dupont
Review Date: 20110530
IETF LC End Date: 20110526
IESG Telechat date: unknown

Summary: Ready with nits

Major issues: None

Minor issues:
 - the main issue is the name of the draft, fortunately it should be solved
  with the publication as an RFC (the name doesn't suggest what the document
  is about, in particular the fact it is based on IPv6 ND snooping).

Nits/editorial comments:
 - many, many occurrences: i.e. -> i.e., and e.g. -> e.g.,
  (IMHO in the middle ' i.e. ' -> ', i.e.,' but ask the RFC Editor)

 - Abstract page 1: please avoid abbrevs in the abstract (FCFS and SAVI)
  even there are in the title.

 - ToC 3 and Appendix A page 24: behaviour -> behavior
 (and 2.3 page 5, 3.2.3 pages 13 and 14, etc)

 - Introduction page 4: same comment about the Introduction (BTW abbrevs
  must be introduced here even they already are in the Abstract)

 - 2.3 page 5: my speller complains about Neighbour (English vs American),
  IMHO we can ignore it.

 - 2.6 page 9 (figure): SWICTH-B -> SWITCH-B

 - 3.2.3 page 13: millisconds -> milliseconds
  (and pages 14 and 16 millisecs -> milliseconds)

 - 6 page 23: Add missing countries (USA and Spain)

 - A.1.1 page 25: 802.1x -> 802.1X

 - A.1.1 page 26: Access Node(DSLAM) -> Access Node (DSLAM)

 - A.1.1.1 page 26: sub-case:SAVI -> sub-case: SAVI

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Jun 18 15:14:37 2011
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 129FD11E811D for <gen-art@ietfa.amsl.com>; Sat, 18 Jun 2011 15:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aVJB6UCvo3GO for <gen-art@ietfa.amsl.com>; Sat, 18 Jun 2011 15:14:36 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id D5C6E11E80BC for <gen-art@ietf.org>; Sat, 18 Jun 2011 15:14:35 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p5IMEYER032166; Sun, 19 Jun 2011 00:14:34 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201106182214.p5IMEYER032166@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Sun, 19 Jun 2011 00:14:34 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-pcn-sm-edge-behaviour.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-pcn-sm-edge-behaviour-05.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, 18 Jun 2011 22:14:37 -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-pcn-sm-edge-behaviour-05.txt
Reviewer: Francis Dupont
Review Date: 201106017
IETF LC End Date: 20110610
IESG Telechat date: unknown

Summary: Ready with nits

Major issues: None

Minor issues:
 - more than 5 authors

 - the American spelling for behaviour is behavior

 - there is a problem with security considerations (5.8 page 16 and
  6 page 17)

Nits/editorial comments:
 - Toc page 2 and 8 page 17: Acknowledgements -> Acknowledgements

 - 1.1 page 6, 3.2.3 page 8, and etc: signalling -> signaling

 - 3.1 page 7, 4 page 13, and etc: collocated -> co-located?

 - 5.2.1 page 14: tunnelled -> tunneled, signalled -> signaled

 - Authors' Addresses page 19: add missing Country

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Jun 18 15:38:38 2011
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 E184421F8556 for <gen-art@ietfa.amsl.com>; Sat, 18 Jun 2011 15:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVAj+kPDglhN for <gen-art@ietfa.amsl.com>; Sat, 18 Jun 2011 15:38:38 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 080C121F8555 for <gen-art@ietf.org>; Sat, 18 Jun 2011 15:38:34 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p5IMcXWx033542; Sun, 19 Jun 2011 00:38:33 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201106182238.p5IMcXWx033542@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Sun, 19 Jun 2011 00:38:33 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat-00.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, 18 Jun 2011 22:38: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-v6ops-ipv6-multihoming-without-ipv6nat-00.txt
Reviewer: Francis Dupont
Review Date: 20110618
IETF LC End Date: 20110623
IESG Telechat date: unknown

Summary: Not Ready

Major issues: the "DNS resolver" selection problem is not a DNS problem:
 it comes from a common use of the DNS which is not in the DNS model.
 I agree it is a real world problem but its origin IMHO requires more care
 about its explaination.
 I suggest to ask the DNSOP WG about what to do (and to get the correct
 terminology, IMHO resolver -> caching server). BTW DNSSEC could change
 this: it makes views of not local domains more coherent and the different
 kinds of DNSSEC aware resolvers (*not* caching servers) are host software.

Minor issues:
 - I don't understand why the notion (and well known term) of
  ingress filtering is not used...

 - I have a mixed feeling about the whole document: IMHO it is more
  in the scope of the mif WG, and I am not convinced by it at the
  exception of the negative points (i.e., multi-homing in IPv6 still
  doesn't work at it should...). So what is its real goal?

Nits/editorial comments:
 - 1 page 3: missing comma? in
   "Whenever a host or small network (which does not meet minimum IPv6
   allocation criteria) is connected to multiple upstream networks IPv6
                                                                  ^ ,
   address is assigned by each respective service provider resulting in
   hosts with more than one active IPv6 addresses."

 - 1 page 3: definced -> defined?

 - 1 page 4: in its standard model, the DNS is location independent so
  any caching servers should return the same thing... (cf major issue)

 - 1 page 4: resolvers -> caching servers

 - 1 page 4: introduce thee uRPF abbrev (or better use 'ingress
  filtering')

 - 3.1 page 6 (comment): the explaination of scenario 2 strongly
  suggests the use of DHCPv6!

 - 3.3 page 8: another place where 'ingress filtering' is better

 - 3.3 page 8 (and further): there are hosts which manages multiple
 default routers (BTW this doesn't solve the problem at all, the
 text is just not accurate as it assumes no such host exists)

 - 3.3 page 9: ie, -> i.e.,

 - 3.3 page 9: policy routing (Cisco term, Juniper has the same thing
  with a different name) allows a router to determine which traffic
  should be sent to which network (i.e., the text is false).

 - 7.2 page 15: coexistence -> co-existence (i.e., I believe the title
  is right)

 - 8 page 16: his -> its (the policy distributor is a device)

Regards

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Sat Jun 18 16:08:00 2011
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 DBBF711E811B for <gen-art@ietfa.amsl.com>; Sat, 18 Jun 2011 16:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TW4lOFVoahbd for <gen-art@ietfa.amsl.com>; Sat, 18 Jun 2011 16:08:00 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id BC74311E80B3 for <gen-art@ietf.org>; Sat, 18 Jun 2011 16:07:59 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p5IN7wSO035372; Sun, 19 Jun 2011 01:07:58 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201106182307.p5IN7wSO035372@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Sun, 19 Jun 2011 01:07:58 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-netlmm-pmipv6-mib.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-netlmm-pmipv6-mib-05.txt (resent???)
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, 18 Jun 2011 23:08:01 -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-netlmm-pmipv6-mib-05.txt
Reviewer: Francis Dupont
Review Date: 20110527
IETF LC End Date: 20110512
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - Toc page 2 and 9 page 67: Acknowledgements -> Acknowledgments

 - 5 page 7: incoherent zip/country order for Japan

 - 5 page 9: pmip6Stats:pmip6BindingRegcounters ->
                                       ^
             pmip6Stats:pmip6BindingRegcounters
  (fortunately it is in a comment, but an ASN.1 comment :-)

 - 5 page 16: reindent pmip6MagProxyCOATable description
 (same pages 39 and 40 for pmip6LmaMinDelayBeforeBCEDelete)

 - 5 page 22 (pmip6MagBLlMnIdentifier): bad wording (the two is for
  the length, not the value).
  same page 28 for pmip6BindingMnLlIdentifier

 - 5 page 24: reformat pmip6MagBLAccessTechnologyType description

 - 5 page 24 (pmip6MagBLTimeRecentlyAccepted):
  acknowledgement -> acknowledgment
  (same page 29 for pmip6BindingMagLinkLocalAddress,
   page 30 for pmip6MissingMnIdentifierOption,
   page 31 for pmip6NotLMAForThisMobileNode, etc)

 - 5 page 31 (pmip6MissingMnIdentifierOption): router. -> router,

 - 5 page 37 (pmip6CounterDiscontinuityTime): viz. ???

 - 5 page 41 (pmip6LmaTimestampValidityWindow): bad wording:
  length of time ???

 - 5 page 50 (pmip6CoreReadOnlyCompliance): missing final '.' in
  description 

 - 6 page 63: extra space in 'pmip6MobileNodeGeneratedTimestampInUse :'

 - 6 page 63: IPSec -> IPsec

 - 10 page 67: presentation should be uniformized.

Regards

Francis.Dupont@fdupont.fr

PS: I don't remember if I sent this review, so anyway I resend it.

From alexey.melnikov@isode.com  Sun Jun 19 08:01:15 2011
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 6F8AE21F84F9; Sun, 19 Jun 2011 08:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.364
X-Spam-Level: 
X-Spam-Status: No, score=-102.364 tagged_above=-999 required=5 tests=[AWL=0.235, 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 AGY9MDwpFqfa; Sun, 19 Jun 2011 08:01:15 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id CE2FB21F84E8; Sun, 19 Jun 2011 08:01:14 -0700 (PDT)
Received: from [188.29.231.218] (188.29.231.218.threembb.co.uk [188.29.231.218])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Tf4POAA-uT15@rufus.isode.com>; Sun, 19 Jun 2011 16:01:13 +0100
Message-ID: <4DFE0F23.7050706@isode.com>
Date: Sun, 19 Jun 2011 16:00:51 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: gen-art@ietf.org
References: <4D9C8D2A.7080605@nostrum.com> <4DFBD34B.7000900@isode.com>
In-Reply-To: <4DFBD34B.7000900@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-burgin-ipsec-suiteb-profile.all@tools.ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-Art Last Call Review: draft-burgin-ipsec-suiteb-profile-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: Sun, 19 Jun 2011 15:01:15 -0000

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-burgin-ipsec-suiteb-profile-00
> Reviewer: Alexey Melnikov
> Review Date: 17-June-2011
> IETF LC End Date: 13-July-2011
> IESG Telechat
>
> Summary: not ready, but issues are not difficult to address

This was a bit harsh/unclear. I meant:

    This draft is on the right track but has open issues, described in the review.



From glenn@cysols.com  Mon Jun 20 01:10:44 2011
Return-Path: <glenn@cysols.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 3223721F84F2 for <gen-art@ietfa.amsl.com>; Mon, 20 Jun 2011 01:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 mpOaVFc5vkao for <gen-art@ietfa.amsl.com>; Mon, 20 Jun 2011 01:10:43 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by ietfa.amsl.com (Postfix) with ESMTP id 6B25821F84F1 for <gen-art@ietf.org>; Mon, 20 Jun 2011 01:10:43 -0700 (PDT)
Received: from [192.168.0.193] (cookie.win2004.cysol.co.jp [192.168.0.193]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id p5K8AHOL005376 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 20 Jun 2011 17:10:18 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4DFF0068.5020709@cysols.com>
Date: Mon, 20 Jun 2011 17:10:16 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@fdupont.fr>
References: <201106182307.p5IN7wSO035372@givry.fdupont.fr>
In-Reply-To: <201106182307.p5IN7wSO035372@givry.fdupont.fr>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 20 Jun 2011 01:21:41 -0700
Cc: draft-ietf-netlmm-pmipv6-mib.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] review of draft-ietf-netlmm-pmipv6-mib-05.txt (resent???)
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, 20 Jun 2011 08:10:44 -0000

Francis,
       Thanks for the detailed review. We are currently
working on the DISCUSSes of the IESG. We will post a
revised draft shortly.

       Glenn

(2011/06/19 8:07), Francis Dupont 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-netlmm-pmipv6-mib-05.txt
> Reviewer: Francis Dupont
> Review Date: 20110527
> IETF LC End Date: 20110512
> IESG Telechat date: unknown
> 
> Summary: Ready
> 
> Major issues: None
> 
> Minor issues: None
> 
> Nits/editorial comments:
>   - Toc page 2 and 9 page 67: Acknowledgements ->  Acknowledgments
> 
>   - 5 page 7: incoherent zip/country order for Japan
> 
>   - 5 page 9: pmip6Stats:pmip6BindingRegcounters ->
>                                         ^
>               pmip6Stats:pmip6BindingRegcounters
>    (fortunately it is in a comment, but an ASN.1 comment :-)
> 
>   - 5 page 16: reindent pmip6MagProxyCOATable description
>   (same pages 39 and 40 for pmip6LmaMinDelayBeforeBCEDelete)
> 
>   - 5 page 22 (pmip6MagBLlMnIdentifier): bad wording (the two is for
>    the length, not the value).
>    same page 28 for pmip6BindingMnLlIdentifier
> 
>   - 5 page 24: reformat pmip6MagBLAccessTechnologyType description
> 
>   - 5 page 24 (pmip6MagBLTimeRecentlyAccepted):
>    acknowledgement ->  acknowledgment
>    (same page 29 for pmip6BindingMagLinkLocalAddress,
>     page 30 for pmip6MissingMnIdentifierOption,
>     page 31 for pmip6NotLMAForThisMobileNode, etc)
> 
>   - 5 page 31 (pmip6MissingMnIdentifierOption): router. ->  router,
> 
>   - 5 page 37 (pmip6CounterDiscontinuityTime): viz. ???
> 
>   - 5 page 41 (pmip6LmaTimestampValidityWindow): bad wording:
>    length of time ???
> 
>   - 5 page 50 (pmip6CoreReadOnlyCompliance): missing final '.' in
>    description
> 
>   - 6 page 63: extra space in 'pmip6MobileNodeGeneratedTimestampInUse :'
> 
>   - 6 page 63: IPSec ->  IPsec
> 
>   - 10 page 67: presentation should be uniformized.
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: I don't remember if I sent this review, so anyway I resend it.


From rbarnes@bbn.com  Mon Jun 20 06:53:37 2011
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 AE99011E808A for <gen-art@ietfa.amsl.com>; Mon, 20 Jun 2011 06:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.166
X-Spam-Level: 
X-Spam-Status: No, score=-106.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 2fFKVz5mK4-Q for <gen-art@ietfa.amsl.com>; Mon, 20 Jun 2011 06:53:34 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 09D1511E815B for <gen-art@ietf.org>; Mon, 20 Jun 2011 06:53:31 -0700 (PDT)
Received: from [128.89.253.103] (port=57085 helo=[172.27.17.202]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1QYeuu-0009SN-Vh; Mon, 20 Jun 2011 09:53:29 -0400
From: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 20 Jun 2011 09:53:27 -0400
Message-Id: <D419748A-BB53-4550-AD22-DB2216706C71@bbn.com>
To: General Area Review Team <gen-art@ietf.org>, draft-ietf-opsawg-mib-floats@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Subject: [Gen-art] review of draft-ietf-opsawg-mib-floats-02.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, 20 Jun 2011 13:53:37 -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-opsawg-mib-floats-02.txt
Reviewer: Richard Barnes
Review Date: 20110620
IETF LC End Date: 20110615
IESG Telechat date: 20110623

Summary: Ready

Major issues: None

Minor issues: None

From randy_presuhn@mindspring.com  Mon Jun 20 10:06:24 2011
Return-Path: <randy_presuhn@mindspring.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 1603011E80C1 for <gen-art@ietfa.amsl.com>; Mon, 20 Jun 2011 10:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.299
X-Spam-Level: 
X-Spam-Status: No, score=-101.299 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 cd2y7kL8XWjl for <gen-art@ietfa.amsl.com>; Mon, 20 Jun 2011 10:06:23 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 6A0F411E80B5 for <gen-art@ietf.org>; Mon, 20 Jun 2011 10:06:23 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=tRH7HBrejM5KJhFK8pktptgT4hHu2qGwl0FI3UCcs9hVQFL5rwMu2tySP+7ey4kI; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.60.6.109] (helo=oemcomputer) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1QYhvW-00028D-L5; Mon, 20 Jun 2011 13:06:18 -0400
Message-ID: <000901cc2f6c$f97b90e0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>, "General Area Review Team" <gen-art@ietf.org>, <draft-ietf-opsawg-mib-floats@tools.ietf.org>
References: <D419748A-BB53-4550-AD22-DB2216706C71@bbn.com>
Date: Mon, 20 Jun 2011 10:10:36 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888cc964a8bf633b38277968a7d98f1103bba51023d5c9ef7ca350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.60.6.109
Subject: Re: [Gen-art] review of draft-ietf-opsawg-mib-floats-02.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, 20 Jun 2011 17:06:24 -0000

Hi -

Thank you for the prompt (and concise!) review.

Randy

----- Original Message ----- 
> From: "Richard L. Barnes" <rbarnes@bbn.com>
> To: "General Area Review Team" <gen-art@ietf.org>; <draft-ietf-opsawg-mib-floats@tools.ietf.org>
> Sent: Monday, June 20, 2011 6:53 AM
> Subject: review of draft-ietf-opsawg-mib-floats-02.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>.
> 
> Please resolve these comments along with any other Last Call comments 
> you may receive.
> 
> Document: draft-ietf-opsawg-mib-floats-02.txt
> Reviewer: Richard Barnes
> Review Date: 20110620
> IETF LC End Date: 20110615
> IESG Telechat date: 20110623
> 
> Summary: Ready
> 
> Major issues: None
> 
> Minor issues: None


From scott.brim@gmail.com  Mon Jun 20 13:04:26 2011
Return-Path: <scott.brim@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 2EF6F1F0C63 for <gen-art@ietfa.amsl.com>; Mon, 20 Jun 2011 13:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v6qDnZnIJjWp for <gen-art@ietfa.amsl.com>; Mon, 20 Jun 2011 13:04:25 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id A5C041F0C38 for <gen-art@ietf.org>; Mon, 20 Jun 2011 13:04:25 -0700 (PDT)
Received: by iwn39 with SMTP id 39so1408051iwn.31 for <gen-art@ietf.org>; Mon, 20 Jun 2011 13:04:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=atnvc21ogCtCEljOhqj2sQbKOPVH3Ieegx2VLiNcFVQ=; b=Z0JlnW0vLiPrHGuLH2De25TxjdGzO3pYYnjbafrZQbdjbaD2Ooe8kCgT3ixKeAoSWU deEk5/7uIu5njx8XHhD7UYSmlhZUzjP3Ki5mSEhTMYl7BoGSRBNnNYiKFl+38XS2IEpz 25bC45Id/frw5486yVxWhJh256SeMBrVw1PbY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=CddNXL1YD8aVdJ/FUVg+o3puPNc0pPdoep1DKLPHTnkuwziCMdQSPE7HssWiOgJgpS kYc3BL6IbumTvAnpbpNy49AkVF6IU/srf3ay/e6RKP2BGYJUCHMr4wOhd+dJbp+W5WrU qeWEJVAzYFkpcABEnFIo/dvu04ipq87dbue4g=
Received: by 10.231.61.83 with SMTP id s19mr5550982ibh.19.1308600265056; Mon, 20 Jun 2011 13:04:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.15.198 with HTTP; Mon, 20 Jun 2011 13:04:05 -0700 (PDT)
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 20 Jun 2011 16:04:05 -0400
Message-ID: <BANLkTikHuCmJyVbKCPQD42NqMBzk9V-KJA@mail.gmail.com>
To: gen-art <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] change of status
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, 20 Jun 2011 20:04:26 -0000

FYI July 8th will be my last day at Cisco.  I'll be taking advantage
of the early retirement package to take a little time to get my life
organized and set up to do something else.  I'll be consulting for
Internet2 part time for the next few months and then we'll see what
happens -- I would like to get more into non-profit user advocacy, but
still keep up technical work and still make some money :-).  Anyway, I
definitely will not be in Quebec, and probably won't be in Taiwan.  I
won't miss Cisco but I will miss working with everyone at the IETF,
and I'm going to try to find ways to collaborate with you in whatever
I end up doing for work.  In the meantime, Jean: I'll finish out the
reviews on my list but could you immediately reduce my quota to 0?

Thanks, and I'll have more to say soon ... Scott

From Attila.Takacs@ericsson.com  Tue Jun 21 03:35:00 2011
Return-Path: <Attila.Takacs@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 46B7B11E80B4 for <gen-art@ietfa.amsl.com>; Tue, 21 Jun 2011 03:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iq5zaJaEfQFj for <gen-art@ietfa.amsl.com>; Tue, 21 Jun 2011 03:34:59 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 7F5D211E807C for <gen-art@ietf.org>; Tue, 21 Jun 2011 03:34:59 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c17ae00000262e-e2-4e0073d2ea6c
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id FD.6F.09774.2D3700E4; Tue, 21 Jun 2011 12:34:58 +0200 (CEST)
Received: from ESESSCMS0365.eemea.ericsson.se ([169.254.1.89]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Tue, 21 Jun 2011 12:34:56 +0200
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: Miguel Garcia A <miguel.a.garcia@ericsson.com>, Lou Berger <lberger@labn.net>, Diego Caviglia <diego.caviglia@ericsson.com>, "donald.fedyk@alcatel-lucent.com" <donald.fedyk@alcatel-lucent.com>, Julien Meuric <julien.meuric@orange-ftgroup.com>, Deborah Brungard <db3546@att.com>, Adrian Farrel <adrian@olddog.co.uk>
Date: Tue, 21 Jun 2011 12:34:55 +0200
Thread-Topic: Gen-ART review of draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-01.txt
Thread-Index: AcwhD1AjXT0eQK8bT32wZgCWOhpXygO6i35A
Message-ID: <6477E10CC7D76444A479B9AC31F262A9E53183C6@ESESSCMS0365.eemea.ericsson.se>
References: <4DE764F5.8020900@ericsson.com>
In-Reply-To: <4DE764F5.8020900@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
X-Mailman-Approved-At: Tue, 21 Jun 2011 05:10:20 -0700
Cc: General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-01.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 10:35:00 -0000

Hi Miguel,
Thanks for the review!
Attila=20

-----Original Message-----
From: Miguel Garcia A=20
Sent: Thursday, June 02, 2011 12:25 PM
To: Attila Takacs; Lou Berger; Diego Caviglia; donald.fedyk@alcatel-lucent.=
com; Julien Meuric; Deborah Brungard; Adrian Farrel
Cc: General Area Review Team
Subject: Gen-ART review of draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-01.txt

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

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

Document: draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-01.txt
Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
Review Date: 2011-06-02=09
IETF LC End Date: 2011-06-06

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

Well written document. There are no issues with it.

Regards,

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

From ietfdbh@comcast.net  Tue Jun 21 12:49:34 2011
Return-Path: <ietfdbh@comcast.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 5E9F81F0C73 for <gen-art@ietfa.amsl.com>; Tue, 21 Jun 2011 12:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.113, 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 KntcJnKIDq2G for <gen-art@ietfa.amsl.com>; Tue, 21 Jun 2011 12:49:32 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8B5091F0C71 for <gen-art@ietf.org>; Tue, 21 Jun 2011 12:49:32 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta05.westchester.pa.mail.comcast.net with comcast id yjn41g0011vXlb855jpZpw; Tue, 21 Jun 2011 19:49:33 +0000
Received: from davidPC ([67.189.235.106]) by omta17.westchester.pa.mail.comcast.net with comcast id yjpX1g0082JQnJT3djpXCA; Tue, 21 Jun 2011 19:49:32 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Elwyn Davies'" <elwynd@dial.pipex.com>, <philip.eardley@bt.com>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk> <9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net> <4DF7986B.5020108@dial.pipex.com>
In-Reply-To: <4DF7986B.5020108@dial.pipex.com>
Date: Tue, 21 Jun 2011 15:49:25 -0400
Message-ID: <33B5B2B1686A45B6A3739D9D9EB234C7@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16807
Thread-Index: Acwqt2w5hFeN+fVjQuWGiyHiFNXbHAFjCY5A
Cc: pcn@ietf.org, 'General Area Reviwing Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Tue, 21 Jun 2011 19:49:35 -0000

Hi,

The WG was chartered to specify the 
(3) encoding and transport of (pre-)congestion information
 between the interior and domain egress
... and ...
(5) encoding and transport of (pre-)congestion information
 between the egress and the controlling domain ingress 

I interpret that to mean the transport protocol and the message
formats should be specified in the documents.
I have to agree with Elwyn that lack of such formats means
implementations are likely to not be interoperable.
I am not sure what protocols would be suitable for these tasks; other
readers may have similar concerns.

I think the specification would benefit from a mandatory-to-implement
protocol expected to carry the configuration and reported information.
At a minimum, there should be a clear information model (RFC3444)
about the information to be transported.
The data type and range of values should be included in the
information model for each counter and configuration variable.
I think it would be better to specify a mandatory-to-implement
protocol, or at least a recommended-to-implement protocol, and a
corresponding data model to ensure interoperability.

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

> -----Original Message-----
> From: Elwyn Davies [mailto:elwynd@dial.pipex.com] 
> Sent: Tuesday, June 14, 2011 1:21 PM
> To: philip.eardley@bt.com
> Cc: pcn@ietf.org; ietfdbh@comcast.net; General Area Reviwing Team
> Subject: Re: Gen-art LC review of
draft-ietf-pcn-cl-edge-behaviour-08
> 
> Hi, Phil.
> 
> It strikes me that the first and second points below are 
> something which 
> David Harrington perhaps ought to give an opinion on. He has got to 
> defend it to the IESG.
> 
> On the first point, my feeling is that neither the 
> requirements doc nor 
> this doc is sufficient to guarantee an interoperable implementation.

> There seems to me to be a cleft stick here (irrespective of 
> whether this 
> ends up as informational or experimental.) The WG is is specifying 
> pieces of functionality that go in two or more different 
> types of boxes 
> (three if there is a separate implementation of the central decision

> point). If the system is going to be generally deployable or 
> even to be 
> experimented with there may be different implementations.  
> The box types 
> communicate using the information specifications in the doc.  This 
> appears to require protocol definitions.  Where they are defined is 
> another issue but I feel it has either to be in this doc or 
> in another 
> doc referenced from this.  If they aren't specified I can't see that

> anybody will be interested in making commercial implementations.
> 
> I see David didn't make any comment about this situation in his
write 
> up, so maybe I am over reacting.
> 
> Regards,
> Elwyn
> 
> 
> 
> 
> 
> On 13/06/2011 18:04, philip.eardley@bt.com wrote:
> > Elwyn,
> >
> > Thanks for the detailed review.
> > A few follow-ups in-line
> > Thanks
> > phil
> >
> > --
> > Major issues:
> > The draft contains partial definitions of two control 
> protocols (egress
> > ->  decision point; decision point ->  ingress).  It does 
> not make it
> > clear whether the reader is expected to get full 
> definitions of these
> > protocols here or whether there will be another document 
> that specifies
> > these protocols completely.  As is stands one could build 
> the protocols
> > and pretty much guarantee that they would not be interoperable
with
> > other implementations since message formats are not 
> included although
> > high level specs are.  The document needs to be much 
> clearer about what
> > is expected to happen here.
> >
> > [phil] there is another document, " Requirements for 
> Signaling of (Pre-) Congestion Information in a DiffServ 
> Domain" 
> [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requireme
> nts-04] that deals with your issue to some extent. It doesn't 
> specify message formats but does at least specify better what 
> information the messages must contain. My understanding is 
> that unfortunately the WG doesn't feel it has the effort to 
> specify these protocols completely.
> >
> >
> > Use of EXP codepoint: My understanding of what is said in 
> RFC 5696 is
> > that EXP is supposed to be left for other (non=PCN) systems to
use.
> > This draft uses it.  Is this sensible? Is this whole draft 
> experimental
> > really?
> > [phil] the intention of rfc5696 was that the EXP codepoint 
> is for experimental *PCN* encodings - ie beyond the baseline. 
> For instance, the CL behaviour needs separate codepoints for 
> (PCN) threshold-marking and (PCN) excess-traffic-marking&  
> this would require using the EXP codepoint.
> > However...... There is currently some discussion on what 
> PCN encodings to specify beyond the baseline. At the time we 
> wrote the baseline, we envisaged the need for several 
> encodings - however it now seems that one may be enough, in 
> which case there may possibly be just one PCN encoding (ie a 
> revised 5696 that now uses the 01 codepoint), so possibly may 
> be Standards track - ??
> > Anyway, i take your point that we need to think about Status.
> >
> > s3.3.1:
> >> [CL-specific] The outcome of the comparison is not very sensitive
> >>        to the value of the CLE-limit in practice, because 
> when threshold-
> >>        marking occurs it tends to persist long enough that 
> threshold-
> >>        marked traffic becomes a large proportion of the 
> received traffic
> >>        in a given interval.
> > This statement worries me.  It sounds like a characteristic of an
> > unstable system.  If the value is that non-critical why are we
> > bothering?
> >
> > [phil] admission control system. imagine the pcn-domain has 
> one bottleneck link. If it can cope with the current number 
> of calls (their bandwidth), then no pkts gets 
> threshold-marked, so the CLE = 0. If there are too many, then 
> all pkts gets threshold-marked, so the CLE = 1. If there is 
> almost exactly the right number of calls, then 
> threshold-marking will tend to be on for a while, then off 
> for a while (perhaps when several flows are transmitting less 
> traffic than normal), so the CLE will jiggle about between 0& 
>  1. If the CLE is<  CLE-limit (say CLE-limit = 0.6&  current 
> CLE = 0.5), when a new call admission request happens to 
> arrive then it gets admitted. But then there's more traffic 
> and it's likely that the CLE will rise to 1 - hence another 
> admission request will get blocked. When a call finishes, 
> then the reverse is true.
> >
> > Now suppose we had in fact configured CLE-limit = 0.4, then 
> in the scenario above the call request would have been 
> blocked. However, (1) the PCN-domain has only admitted one 
> fewer call, (2) a short time later, either the CLE happens to 
> be lower or a call departs, and then the next admission 
> request is accepted.
> >
> > All this means that it doesn't matter much exactly what you 
> set CLE-limit to - it barely affects the average number of 
> calls admitted. The argument above is hand-wavy, but lots of 
> simulations have been done that show this is true (I hope i'm 
> representing the results correctly)
> > So the lack of sensitivity to CLE-limit seems like a good thing.
> >
> >
> > Minor issues:
> >
> > s6:  The potential introduction of a centralized decision 
> point appears
> > to provide additional attack points beyond the architecture 
> in RFC 5559.
> > It appears to me that the requests for information about 
> specific flows
> > to the ingress are ighly vulnerable as they (probably) 
> contain all the
> > information needed to craft a DoS attack on the flow.
> >
> > [phil] seems a good point to me
> >
> 
> 
> -- 
> Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
> For more information, see 
> http://www.oxfam.org.uk/get_involved/fundraise/walk/ and 
> follow us on Twitter at http://twitter.com/CambOxfamWalk.
> 
> 


From tom111.taylor@bell.net  Tue Jun 21 17:31:08 2011
Return-Path: <tom111.taylor@bell.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 3ED2F11E8092; Tue, 21 Jun 2011 17:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.678
X-Spam-Level: 
X-Spam-Status: No, score=-101.678 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, 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 WCQTjohAFlqo; Tue, 21 Jun 2011 17:31:07 -0700 (PDT)
Received: from blu0-omc2-s36.blu0.hotmail.com (blu0-omc2-s36.blu0.hotmail.com [65.55.111.111]) by ietfa.amsl.com (Postfix) with ESMTP id C50BE11E8079; Tue, 21 Jun 2011 17:31:06 -0700 (PDT)
Received: from BLU0-SMTP78 ([65.55.111.72]) by blu0-omc2-s36.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 21 Jun 2011 17:31:05 -0700
X-Originating-IP: [76.70.76.63]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl>
Received: from [192.168.2.17] ([76.70.76.63]) by BLU0-SMTP78.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 21 Jun 2011 17:31:05 -0700
Date: Tue, 21 Jun 2011 20:31:04 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk>	<9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net>	<4DF7986B.5020108@dial.pipex.com> <33B5B2B1686A45B6A3739D9D9EB234C7@davidPC>
In-Reply-To: <33B5B2B1686A45B6A3739D9D9EB234C7@davidPC>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Jun 2011 00:31:05.0597 (UTC) FILETIME=[AC3D42D0:01CC3073]
Cc: pcn@ietf.org, philip.eardley@bt.com, 'General Area Reviwing Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 00:31:08 -0000

OK, I'll take up the good work. Just to start with, I propose to submit 
interim updates as I wished I had back a few months ago. I'll go on from 
there.

On 21/06/2011 3:49 PM, David Harrington wrote:
> Hi,
>
> The WG was chartered to specify the
> (3) encoding and transport of (pre-)congestion information
>   between the interior and domain egress
> ... and ...
> (5) encoding and transport of (pre-)congestion information
>   between the egress and the controlling domain ingress
>
> I interpret that to mean the transport protocol and the message
> formats should be specified in the documents.
> I have to agree with Elwyn that lack of such formats means
> implementations are likely to not be interoperable.
> I am not sure what protocols would be suitable for these tasks; other
> readers may have similar concerns.
>
> I think the specification would benefit from a mandatory-to-implement
> protocol expected to carry the configuration and reported information.
> At a minimum, there should be a clear information model (RFC3444)
> about the information to be transported.
> The data type and range of values should be included in the
> information model for each counter and configuration variable.
> I think it would be better to specify a mandatory-to-implement
> protocol, or at least a recommended-to-implement protocol, and a
> corresponding data model to ensure interoperability.
>
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)
>
>> -----Original Message-----
>> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
>> Sent: Tuesday, June 14, 2011 1:21 PM
>> To: philip.eardley@bt.com
>> Cc: pcn@ietf.org; ietfdbh@comcast.net; General Area Reviwing Team
>> Subject: Re: Gen-art LC review of
> draft-ietf-pcn-cl-edge-behaviour-08
>>
>> Hi, Phil.
>>
>> It strikes me that the first and second points below are
>> something which
>> David Harrington perhaps ought to give an opinion on. He has got to
>> defend it to the IESG.
>>
>> On the first point, my feeling is that neither the
>> requirements doc nor
>> this doc is sufficient to guarantee an interoperable implementation.
>
>> There seems to me to be a cleft stick here (irrespective of
>> whether this
>> ends up as informational or experimental.) The WG is is specifying
>> pieces of functionality that go in two or more different
>> types of boxes
>> (three if there is a separate implementation of the central decision
>
>> point). If the system is going to be generally deployable or
>> even to be
>> experimented with there may be different implementations.
>> The box types
>> communicate using the information specifications in the doc.  This
>> appears to require protocol definitions.  Where they are defined is
>> another issue but I feel it has either to be in this doc or
>> in another
>> doc referenced from this.  If they aren't specified I can't see that
>
>> anybody will be interested in making commercial implementations.
>>
>> I see David didn't make any comment about this situation in his
> write
>> up, so maybe I am over reacting.
>>
>> Regards,
>> Elwyn
>>
>>
>>
>>
>>
>> On 13/06/2011 18:04, philip.eardley@bt.com wrote:
>>> Elwyn,
>>>
>>> Thanks for the detailed review.
>>> A few follow-ups in-line
>>> Thanks
>>> phil
>>>
>>> --
>>> Major issues:
>>> The draft contains partial definitions of two control
>> protocols (egress
>>> ->   decision point; decision point ->   ingress).  It does
>> not make it
>>> clear whether the reader is expected to get full
>> definitions of these
>>> protocols here or whether there will be another document
>> that specifies
>>> these protocols completely.  As is stands one could build
>> the protocols
>>> and pretty much guarantee that they would not be interoperable
> with
>>> other implementations since message formats are not
>> included although
>>> high level specs are.  The document needs to be much
>> clearer about what
>>> is expected to happen here.
>>>
>>> [phil] there is another document, " Requirements for
>> Signaling of (Pre-) Congestion Information in a DiffServ
>> Domain"
>> [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requireme
>> nts-04] that deals with your issue to some extent. It doesn't
>> specify message formats but does at least specify better what
>> information the messages must contain. My understanding is
>> that unfortunately the WG doesn't feel it has the effort to
>> specify these protocols completely.
>>>
>>>
>>> Use of EXP codepoint: My understanding of what is said in
>> RFC 5696 is
>>> that EXP is supposed to be left for other (non=PCN) systems to
> use.
>>> This draft uses it.  Is this sensible? Is this whole draft
>> experimental
>>> really?
>>> [phil] the intention of rfc5696 was that the EXP codepoint
>> is for experimental *PCN* encodings - ie beyond the baseline.
>> For instance, the CL behaviour needs separate codepoints for
>> (PCN) threshold-marking and (PCN) excess-traffic-marking&
>> this would require using the EXP codepoint.
>>> However...... There is currently some discussion on what
>> PCN encodings to specify beyond the baseline. At the time we
>> wrote the baseline, we envisaged the need for several
>> encodings - however it now seems that one may be enough, in
>> which case there may possibly be just one PCN encoding (ie a
>> revised 5696 that now uses the 01 codepoint), so possibly may
>> be Standards track - ??
>>> Anyway, i take your point that we need to think about Status.
>>>
>>> s3.3.1:
>>>> [CL-specific] The outcome of the comparison is not very sensitive
>>>>         to the value of the CLE-limit in practice, because
>> when threshold-
>>>>         marking occurs it tends to persist long enough that
>> threshold-
>>>>         marked traffic becomes a large proportion of the
>> received traffic
>>>>         in a given interval.
>>> This statement worries me.  It sounds like a characteristic of an
>>> unstable system.  If the value is that non-critical why are we
>>> bothering?
>>>
>>> [phil] admission control system. imagine the pcn-domain has
>> one bottleneck link. If it can cope with the current number
>> of calls (their bandwidth), then no pkts gets
>> threshold-marked, so the CLE = 0. If there are too many, then
>> all pkts gets threshold-marked, so the CLE = 1. If there is
>> almost exactly the right number of calls, then
>> threshold-marking will tend to be on for a while, then off
>> for a while (perhaps when several flows are transmitting less
>> traffic than normal), so the CLE will jiggle about between 0&
>>   1. If the CLE is<   CLE-limit (say CLE-limit = 0.6&   current
>> CLE = 0.5), when a new call admission request happens to
>> arrive then it gets admitted. But then there's more traffic
>> and it's likely that the CLE will rise to 1 - hence another
>> admission request will get blocked. When a call finishes,
>> then the reverse is true.
>>>
>>> Now suppose we had in fact configured CLE-limit = 0.4, then
>> in the scenario above the call request would have been
>> blocked. However, (1) the PCN-domain has only admitted one
>> fewer call, (2) a short time later, either the CLE happens to
>> be lower or a call departs, and then the next admission
>> request is accepted.
>>>
>>> All this means that it doesn't matter much exactly what you
>> set CLE-limit to - it barely affects the average number of
>> calls admitted. The argument above is hand-wavy, but lots of
>> simulations have been done that show this is true (I hope i'm
>> representing the results correctly)
>>> So the lack of sensitivity to CLE-limit seems like a good thing.
>>>
>>>
>>> Minor issues:
>>>
>>> s6:  The potential introduction of a centralized decision
>> point appears
>>> to provide additional attack points beyond the architecture
>> in RFC 5559.
>>> It appears to me that the requests for information about
>> specific flows
>>> to the ingress are ighly vulnerable as they (probably)
>> contain all the
>>> information needed to craft a DoS attack on the flow.
>>>
>>> [phil] seems a good point to me
>>>
>>
>>
>> --
>> Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
>> For more information, see
>> http://www.oxfam.org.uk/get_involved/fundraise/walk/ and
>> follow us on Twitter at http://twitter.com/CambOxfamWalk.
>>
>>
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>
>

From Ruediger.Geib@telekom.de  Tue Jun 21 23:21:40 2011
Return-Path: <Ruediger.Geib@telekom.de>
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 8175F11E8070; Tue, 21 Jun 2011 23:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 MMkESjCZkqc1; Tue, 21 Jun 2011 23:21:39 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id 6B45711E8094; Tue, 21 Jun 2011 23:21:37 -0700 (PDT)
Received: from he110890.emea1.cds.t-internal.com ([10.134.92.131]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 22 Jun 2011 08:21:29 +0200
Received: from HE111648.emea1.cds.t-internal.com ([169.254.5.233]) by he110890 ([10.134.92.131]) with mapi; Wed, 22 Jun 2011 08:21:29 +0200
From: <Ruediger.Geib@telekom.de>
To: <tom111.taylor@bell.net>, <ietfdbh@comcast.net>
Date: Wed, 22 Jun 2011 08:21:27 +0200
Thread-Topic: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08
Thread-Index: Acwwc7boE6jGovIWQu6iS4tZohCwJQAMITDQ
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk> <9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net> <4DF7986B.5020108@dial.pipex.com>	<33B5B2B1686A45B6A3739D9D9EB234C7@davidPC> <BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl>
In-Reply-To: <BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 21 Jun 2011 23:38:59 -0700
Cc: pcn@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 06:21:40 -0000

Hi Tom,

which work are you taking up?

- specifying the madatory to implement protocol.
- or specifying a minimum clear information model (RFC3444).

I prefer the latter above the former.


Regards,

Ruediger

-----Original Message-----
From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of Tom T=
aylor
Sent: Wednesday, June 22, 2011 2:31 AM
To: David Harrington
Cc: pcn@ietf.org; 'Elwyn Davies'; 'General Area Reviwing Team'
Subject: Re: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08

OK, I'll take up the good work. Just to start with, I propose to submit
interim updates as I wished I had back a few months ago. I'll go on from
there.

On 21/06/2011 3:49 PM, David Harrington wrote:
> Hi,
>
> The WG was chartered to specify the
> (3) encoding and transport of (pre-)congestion information
>   between the interior and domain egress
> ... and ...
> (5) encoding and transport of (pre-)congestion information
>   between the egress and the controlling domain ingress
>
> I interpret that to mean the transport protocol and the message
> formats should be specified in the documents.
> I have to agree with Elwyn that lack of such formats means
> implementations are likely to not be interoperable.
> I am not sure what protocols would be suitable for these tasks; other
> readers may have similar concerns.
>
> I think the specification would benefit from a mandatory-to-implement
> protocol expected to carry the configuration and reported information.
> At a minimum, there should be a clear information model (RFC3444)
> about the information to be transported.
> The data type and range of values should be included in the
> information model for each counter and configuration variable.
> I think it would be better to specify a mandatory-to-implement
> protocol, or at least a recommended-to-implement protocol, and a
> corresponding data model to ensure interoperability.
>
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)
>
>> -----Original Message-----
>> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
>> Sent: Tuesday, June 14, 2011 1:21 PM
>> To: philip.eardley@bt.com
>> Cc: pcn@ietf.org; ietfdbh@comcast.net; General Area Reviwing Team
>> Subject: Re: Gen-art LC review of
> draft-ietf-pcn-cl-edge-behaviour-08
>>
>> Hi, Phil.
>>
>> It strikes me that the first and second points below are
>> something which
>> David Harrington perhaps ought to give an opinion on. He has got to
>> defend it to the IESG.
>>
>> On the first point, my feeling is that neither the
>> requirements doc nor
>> this doc is sufficient to guarantee an interoperable implementation.
>
>> There seems to me to be a cleft stick here (irrespective of
>> whether this
>> ends up as informational or experimental.) The WG is is specifying
>> pieces of functionality that go in two or more different
>> types of boxes
>> (three if there is a separate implementation of the central decision
>
>> point). If the system is going to be generally deployable or
>> even to be
>> experimented with there may be different implementations.
>> The box types
>> communicate using the information specifications in the doc.  This
>> appears to require protocol definitions.  Where they are defined is
>> another issue but I feel it has either to be in this doc or
>> in another
>> doc referenced from this.  If they aren't specified I can't see that
>
>> anybody will be interested in making commercial implementations.
>>
>> I see David didn't make any comment about this situation in his
> write
>> up, so maybe I am over reacting.
>>
>> Regards,
>> Elwyn
>>
>>
>>
>>
>>
>> On 13/06/2011 18:04, philip.eardley@bt.com wrote:
>>> Elwyn,
>>>
>>> Thanks for the detailed review.
>>> A few follow-ups in-line
>>> Thanks
>>> phil
>>>
>>> --
>>> Major issues:
>>> The draft contains partial definitions of two control
>> protocols (egress
>>> ->   decision point; decision point ->   ingress).  It does
>> not make it
>>> clear whether the reader is expected to get full
>> definitions of these
>>> protocols here or whether there will be another document
>> that specifies
>>> these protocols completely.  As is stands one could build
>> the protocols
>>> and pretty much guarantee that they would not be interoperable
> with
>>> other implementations since message formats are not
>> included although
>>> high level specs are.  The document needs to be much
>> clearer about what
>>> is expected to happen here.
>>>
>>> [phil] there is another document, " Requirements for
>> Signaling of (Pre-) Congestion Information in a DiffServ
>> Domain"
>> [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requireme
>> nts-04] that deals with your issue to some extent. It doesn't
>> specify message formats but does at least specify better what
>> information the messages must contain. My understanding is
>> that unfortunately the WG doesn't feel it has the effort to
>> specify these protocols completely.
>>>
>>>
>>> Use of EXP codepoint: My understanding of what is said in
>> RFC 5696 is
>>> that EXP is supposed to be left for other (non=3DPCN) systems to
> use.
>>> This draft uses it.  Is this sensible? Is this whole draft
>> experimental
>>> really?
>>> [phil] the intention of rfc5696 was that the EXP codepoint
>> is for experimental *PCN* encodings - ie beyond the baseline.
>> For instance, the CL behaviour needs separate codepoints for
>> (PCN) threshold-marking and (PCN) excess-traffic-marking&
>> this would require using the EXP codepoint.
>>> However...... There is currently some discussion on what
>> PCN encodings to specify beyond the baseline. At the time we
>> wrote the baseline, we envisaged the need for several
>> encodings - however it now seems that one may be enough, in
>> which case there may possibly be just one PCN encoding (ie a
>> revised 5696 that now uses the 01 codepoint), so possibly may
>> be Standards track - ??
>>> Anyway, i take your point that we need to think about Status.
>>>
>>> s3.3.1:
>>>> [CL-specific] The outcome of the comparison is not very sensitive
>>>>         to the value of the CLE-limit in practice, because
>> when threshold-
>>>>         marking occurs it tends to persist long enough that
>> threshold-
>>>>         marked traffic becomes a large proportion of the
>> received traffic
>>>>         in a given interval.
>>> This statement worries me.  It sounds like a characteristic of an
>>> unstable system.  If the value is that non-critical why are we
>>> bothering?
>>>
>>> [phil] admission control system. imagine the pcn-domain has
>> one bottleneck link. If it can cope with the current number
>> of calls (their bandwidth), then no pkts gets
>> threshold-marked, so the CLE =3D 0. If there are too many, then
>> all pkts gets threshold-marked, so the CLE =3D 1. If there is
>> almost exactly the right number of calls, then
>> threshold-marking will tend to be on for a while, then off
>> for a while (perhaps when several flows are transmitting less
>> traffic than normal), so the CLE will jiggle about between 0&
>>   1. If the CLE is<   CLE-limit (say CLE-limit =3D 0.6&   current
>> CLE =3D 0.5), when a new call admission request happens to
>> arrive then it gets admitted. But then there's more traffic
>> and it's likely that the CLE will rise to 1 - hence another
>> admission request will get blocked. When a call finishes,
>> then the reverse is true.
>>>
>>> Now suppose we had in fact configured CLE-limit =3D 0.4, then
>> in the scenario above the call request would have been
>> blocked. However, (1) the PCN-domain has only admitted one
>> fewer call, (2) a short time later, either the CLE happens to
>> be lower or a call departs, and then the next admission
>> request is accepted.
>>>
>>> All this means that it doesn't matter much exactly what you
>> set CLE-limit to - it barely affects the average number of
>> calls admitted. The argument above is hand-wavy, but lots of
>> simulations have been done that show this is true (I hope i'm
>> representing the results correctly)
>>> So the lack of sensitivity to CLE-limit seems like a good thing.
>>>
>>>
>>> Minor issues:
>>>
>>> s6:  The potential introduction of a centralized decision
>> point appears
>>> to provide additional attack points beyond the architecture
>> in RFC 5559.
>>> It appears to me that the requests for information about
>> specific flows
>>> to the ingress are ighly vulnerable as they (probably)
>> contain all the
>>> information needed to craft a DoS attack on the flow.
>>>
>>> [phil] seems a good point to me
>>>
>>
>>
>> --
>> Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
>> For more information, see
>> http://www.oxfam.org.uk/get_involved/fundraise/walk/ and
>> follow us on Twitter at http://twitter.com/CambOxfamWalk.
>>
>>
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>
>
_______________________________________________
PCN mailing list
PCN@ietf.org
https://www.ietf.org/mailman/listinfo/pcn

From philip.eardley@bt.com  Wed Jun 22 01:16:48 2011
Return-Path: <philip.eardley@bt.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 CCA0F21F846D; Wed, 22 Jun 2011 01:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.971
X-Spam-Level: 
X-Spam-Status: No, score=-102.971 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 Jzkdj9VtJWnE; Wed, 22 Jun 2011 01:16:47 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp62.intersmtp.COM [62.239.224.235]) by ietfa.amsl.com (Postfix) with ESMTP id 035BD21F8469; Wed, 22 Jun 2011 01:16:47 -0700 (PDT)
Received: from EVMHT68-UKRD.domain1.systemhost.net (10.36.3.105) by RDW083A006ED62.smtp-e2.hygiene.service (10.187.98.11) with Microsoft SMTP Server (TLS) id 8.3.159.2; Wed, 22 Jun 2011 09:16:46 +0100
Received: from EMV65-UKRD.domain1.systemhost.net ([169.254.2.222]) by EVMHT68-UKRD.domain1.systemhost.net ([10.36.3.105]) with mapi; Wed, 22 Jun 2011 09:16:45 +0100
From: <philip.eardley@bt.com>
To: <Ruediger.Geib@telekom.de>, <tom111.taylor@bell.net>, <ietfdbh@comcast.net>
Date: Wed, 22 Jun 2011 09:16:43 +0100
Thread-Topic: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08
Thread-Index: Acwwc7boE6jGovIWQu6iS4tZohCwJQAMITDQAAPKtvA=
Message-ID: <9510D26531EF184D9017DF24659BB87F32E07BCC20@EMV65-UKRD.domain1.systemhost.net>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk> <9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net> <4DF7986B.5020108@dial.pipex.com>	<33B5B2B1686A45B6A3739D9D9EB234C7@davidPC> <BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl> <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com>
In-Reply-To: <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: pcn@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 08:16:49 -0000

Personally I think it unlikely that the WG would ever complete the former

The latter might be plausible, though having flicked at 3444 i can't tell e=
xactly what we're missing. It seems to say that an information model is an =
absrtact model about relationships between objects and can be defined infor=
mally - (since I havent consciously written one, I'm being vague) - the com=
bination of CL & signalling reqts seems quite close to this?

Thanks for progressing Tom.
phil

-----Original Message-----
From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of Ruedi=
ger.Geib@telekom.de
Sent: 22 June 2011 07:21
To: tom111.taylor@bell.net; ietfdbh@comcast.net
Cc: pcn@ietf.org; gen-art@ietf.org; elwynd@dial.pipex.com
Subject: Re: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08

Hi Tom,

which work are you taking up?

- specifying the madatory to implement protocol.
- or specifying a minimum clear information model (RFC3444).

I prefer the latter above the former.


Regards,

Ruediger

-----Original Message-----
From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of Tom T=
aylor
Sent: Wednesday, June 22, 2011 2:31 AM
To: David Harrington
Cc: pcn@ietf.org; 'Elwyn Davies'; 'General Area Reviwing Team'
Subject: Re: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08

OK, I'll take up the good work. Just to start with, I propose to submit
interim updates as I wished I had back a few months ago. I'll go on from
there.

On 21/06/2011 3:49 PM, David Harrington wrote:
> Hi,
>
> The WG was chartered to specify the
> (3) encoding and transport of (pre-)congestion information
>   between the interior and domain egress
> ... and ...
> (5) encoding and transport of (pre-)congestion information
>   between the egress and the controlling domain ingress
>
> I interpret that to mean the transport protocol and the message
> formats should be specified in the documents.
> I have to agree with Elwyn that lack of such formats means
> implementations are likely to not be interoperable.
> I am not sure what protocols would be suitable for these tasks; other
> readers may have similar concerns.
>
> I think the specification would benefit from a mandatory-to-implement
> protocol expected to carry the configuration and reported information.
> At a minimum, there should be a clear information model (RFC3444)
> about the information to be transported.
> The data type and range of values should be included in the
> information model for each counter and configuration variable.
> I think it would be better to specify a mandatory-to-implement
> protocol, or at least a recommended-to-implement protocol, and a
> corresponding data model to ensure interoperability.
>
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)
>
>> -----Original Message-----
>> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
>> Sent: Tuesday, June 14, 2011 1:21 PM
>> To: philip.eardley@bt.com
>> Cc: pcn@ietf.org; ietfdbh@comcast.net; General Area Reviwing Team
>> Subject: Re: Gen-art LC review of
> draft-ietf-pcn-cl-edge-behaviour-08
>>
>> Hi, Phil.
>>
>> It strikes me that the first and second points below are
>> something which
>> David Harrington perhaps ought to give an opinion on. He has got to
>> defend it to the IESG.
>>
>> On the first point, my feeling is that neither the
>> requirements doc nor
>> this doc is sufficient to guarantee an interoperable implementation.
>
>> There seems to me to be a cleft stick here (irrespective of
>> whether this
>> ends up as informational or experimental.) The WG is is specifying
>> pieces of functionality that go in two or more different
>> types of boxes
>> (three if there is a separate implementation of the central decision
>
>> point). If the system is going to be generally deployable or
>> even to be
>> experimented with there may be different implementations.
>> The box types
>> communicate using the information specifications in the doc.  This
>> appears to require protocol definitions.  Where they are defined is
>> another issue but I feel it has either to be in this doc or
>> in another
>> doc referenced from this.  If they aren't specified I can't see that
>
>> anybody will be interested in making commercial implementations.
>>
>> I see David didn't make any comment about this situation in his
> write
>> up, so maybe I am over reacting.
>>
>> Regards,
>> Elwyn
>>
>>
>>
>>
>>
>> On 13/06/2011 18:04, philip.eardley@bt.com wrote:
>>> Elwyn,
>>>
>>> Thanks for the detailed review.
>>> A few follow-ups in-line
>>> Thanks
>>> phil
>>>
>>> --
>>> Major issues:
>>> The draft contains partial definitions of two control
>> protocols (egress
>>> ->   decision point; decision point ->   ingress).  It does
>> not make it
>>> clear whether the reader is expected to get full
>> definitions of these
>>> protocols here or whether there will be another document
>> that specifies
>>> these protocols completely.  As is stands one could build
>> the protocols
>>> and pretty much guarantee that they would not be interoperable
> with
>>> other implementations since message formats are not
>> included although
>>> high level specs are.  The document needs to be much
>> clearer about what
>>> is expected to happen here.
>>>
>>> [phil] there is another document, " Requirements for
>> Signaling of (Pre-) Congestion Information in a DiffServ
>> Domain"
>> [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requireme
>> nts-04] that deals with your issue to some extent. It doesn't
>> specify message formats but does at least specify better what
>> information the messages must contain. My understanding is
>> that unfortunately the WG doesn't feel it has the effort to
>> specify these protocols completely.
>>>
>>>
>>> Use of EXP codepoint: My understanding of what is said in
>> RFC 5696 is
>>> that EXP is supposed to be left for other (non=3DPCN) systems to
> use.
>>> This draft uses it.  Is this sensible? Is this whole draft
>> experimental
>>> really?
>>> [phil] the intention of rfc5696 was that the EXP codepoint
>> is for experimental *PCN* encodings - ie beyond the baseline.
>> For instance, the CL behaviour needs separate codepoints for
>> (PCN) threshold-marking and (PCN) excess-traffic-marking&
>> this would require using the EXP codepoint.
>>> However...... There is currently some discussion on what
>> PCN encodings to specify beyond the baseline. At the time we
>> wrote the baseline, we envisaged the need for several
>> encodings - however it now seems that one may be enough, in
>> which case there may possibly be just one PCN encoding (ie a
>> revised 5696 that now uses the 01 codepoint), so possibly may
>> be Standards track - ??
>>> Anyway, i take your point that we need to think about Status.
>>>
>>> s3.3.1:
>>>> [CL-specific] The outcome of the comparison is not very sensitive
>>>>         to the value of the CLE-limit in practice, because
>> when threshold-
>>>>         marking occurs it tends to persist long enough that
>> threshold-
>>>>         marked traffic becomes a large proportion of the
>> received traffic
>>>>         in a given interval.
>>> This statement worries me.  It sounds like a characteristic of an
>>> unstable system.  If the value is that non-critical why are we
>>> bothering?
>>>
>>> [phil] admission control system. imagine the pcn-domain has
>> one bottleneck link. If it can cope with the current number
>> of calls (their bandwidth), then no pkts gets
>> threshold-marked, so the CLE =3D 0. If there are too many, then
>> all pkts gets threshold-marked, so the CLE =3D 1. If there is
>> almost exactly the right number of calls, then
>> threshold-marking will tend to be on for a while, then off
>> for a while (perhaps when several flows are transmitting less
>> traffic than normal), so the CLE will jiggle about between 0&
>>   1. If the CLE is<   CLE-limit (say CLE-limit =3D 0.6&   current
>> CLE =3D 0.5), when a new call admission request happens to
>> arrive then it gets admitted. But then there's more traffic
>> and it's likely that the CLE will rise to 1 - hence another
>> admission request will get blocked. When a call finishes,
>> then the reverse is true.
>>>
>>> Now suppose we had in fact configured CLE-limit =3D 0.4, then
>> in the scenario above the call request would have been
>> blocked. However, (1) the PCN-domain has only admitted one
>> fewer call, (2) a short time later, either the CLE happens to
>> be lower or a call departs, and then the next admission
>> request is accepted.
>>>
>>> All this means that it doesn't matter much exactly what you
>> set CLE-limit to - it barely affects the average number of
>> calls admitted. The argument above is hand-wavy, but lots of
>> simulations have been done that show this is true (I hope i'm
>> representing the results correctly)
>>> So the lack of sensitivity to CLE-limit seems like a good thing.
>>>
>>>
>>> Minor issues:
>>>
>>> s6:  The potential introduction of a centralized decision
>> point appears
>>> to provide additional attack points beyond the architecture
>> in RFC 5559.
>>> It appears to me that the requests for information about
>> specific flows
>>> to the ingress are ighly vulnerable as they (probably)
>> contain all the
>>> information needed to craft a DoS attack on the flow.
>>>
>>> [phil] seems a good point to me
>>>
>>
>>
>> --
>> Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
>> For more information, see
>> http://www.oxfam.org.uk/get_involved/fundraise/walk/ and
>> follow us on Twitter at http://twitter.com/CambOxfamWalk.
>>
>>
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>
>
_______________________________________________
PCN mailing list
PCN@ietf.org
https://www.ietf.org/mailman/listinfo/pcn
_______________________________________________
PCN mailing list
PCN@ietf.org
https://www.ietf.org/mailman/listinfo/pcn

From tom111.taylor@bell.net  Wed Jun 22 02:49:15 2011
Return-Path: <tom111.taylor@bell.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 9126611E80CE; Wed, 22 Jun 2011 02:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.307
X-Spam-Level: 
X-Spam-Status: No, score=-100.307 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, MSGID_FROM_MTA_HEADER=0.803, 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 DsvST++YjooP; Wed, 22 Jun 2011 02:49:15 -0700 (PDT)
Received: from blu0-omc2-s24.blu0.hotmail.com (blu0-omc2-s24.blu0.hotmail.com [65.55.111.99]) by ietfa.amsl.com (Postfix) with ESMTP id 10FAE11E807F; Wed, 22 Jun 2011 02:49:14 -0700 (PDT)
Received: from BLU0-SMTP15 ([65.55.111.72]) by blu0-omc2-s24.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 22 Jun 2011 02:46:09 -0700
X-Originating-IP: [65.94.104.44]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP154C265676B0E7EA4E24C1D8500@phx.gbl>
Received: from [192.168.2.17] ([65.94.104.44]) by BLU0-SMTP15.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 22 Jun 2011 02:46:08 -0700
Date: Wed, 22 Jun 2011 05:46:07 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Ruediger.Geib@telekom.de
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk>	<9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net>	<4DF7986B.5020108@dial.pipex.com>	<33B5B2B1686A45B6A3739D9D9EB234C7@davidPC> <BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl> <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com>
In-Reply-To: <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Jun 2011 09:46:08.0875 (UTC) FILETIME=[368A33B0:01CC30C1]
Cc: pcn@ietf.org, gen-art@ietf.org, ietfdbh@comcast.net
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 09:49:15 -0000

The CL and SM drafts should definitely specify the information models. 
In my own mind, the actual protocol specification belongs in another 
document, since it would be common to the two models. Other edge 
behaviours (e.g. the piggybacking approach) would require their own 
protocol solutions.

Seriously, would Diameter make sense as the protocol? If so, the work is 
mostly done and I would just revive draft-huang-dime-pcn-collection and 
bring it up to date.

On 22/06/2011 2:21 AM, Ruediger.Geib@telekom.de wrote:
> Hi Tom,
>
> which work are you taking up?
>
> - specifying the madatory to implement protocol.
> - or specifying a minimum clear information model (RFC3444).
>
> I prefer the latter above the former.
>
>
>..

From karagian@cs.utwente.nl  Wed Jun 22 02:52:07 2011
Return-Path: <karagian@cs.utwente.nl>
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 728C911E807F; Wed, 22 Jun 2011 02:52:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.306
X-Spam-Level: 
X-Spam-Status: No, score=-0.306 tagged_above=-999 required=5 tests=[AWL=-1.198, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,  MIME_QP_LONG_LINE=1.396]
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 F8KiQagqtoD1; Wed, 22 Jun 2011 02:52:06 -0700 (PDT)
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD9911E80CF; Wed, 22 Jun 2011 02:52:05 -0700 (PDT)
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id p5M9oR83023533;  Wed, 22 Jun 2011 11:50:27 +0200 (MEST)
Received: from 130.89.12.129 (auth. user karagian@imap1.ewi.utwente.nl) by webmail.cs.utwente.nl with HTTP; Wed, 22 Jun 2011 09:51:47 +0000
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>, "tom111.taylor@bell.net" <tom111.taylor@bell.net>, "ietfdbh@comcast.net" <ietfdbh@comcast.net>
Date: Wed, 22 Jun 2011 09:51:47 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <EONaCqVv.1308736307.0423440.karagian@ewi.utwente.nl>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F32E07BCC20@EMV65-UKRD.domain1.systemhost.net>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Errors-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Wed, 22 Jun 2011 11:50:39 +0200 (MEST)
Cc: "pcn@ietf.org" <pcn@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 09:52:07 -0000

Hi all,

I agree with Phil regarding the fact that the Information model can be
described as an abstract model informally to show the relationships
between objects. In particular RFC 3444 mentions:

   "IMs can be defined in an informal way, using natural languages such
   as English.  An example of such an IM is provided by RFC 3290 [9],
   which describes a conceptual model of a Diffserv Router and specifies
   the relationships between the components of such a router that need
   to be managed."

Regarding the possible options to support interoperability, I also think
that the latter might be plausible. I see three options of implementing
this:

1) each PCN edge behaviour draft will contain such an information model

2) a default information model will be included in the signaling
requirements draft

3) a new draft should be started by the PCN WG to describe such an
information model


With which option should we proceed?


Please also note that I have started modifying the following draft that
can be used as an example of how a signaling protocol can be applied to
support an PCN edge behaviour.
http://tools.ietf.org/html/draft-lefaucheur-rsvp-ecn-01

The target is to submit this draft to tsvwg. However, I do not think that
I will be able to submit this draft before the submission deadline (4th
of July). Tom and Francois were willing to help on commenting and/or
contributing to this.


Best regards,
Georgios




On 6/22/2011, "philip.eardley@bt.com" <philip.eardley@bt.com> wrote:

>Personally I think it unlikely that the WG would ever complete the former
>
>The latter might be plausible, though having flicked at 3444 i can't tell ex=
actly what we're missing. It seems to say that an information model is an abs=
rtact model about relationships between objects and can be defined informally=
 - (since I havent consciously written one, I'm being vague) - the combinatio=
n of CL & signalling reqts seems quite close to this?
>
>Thanks for progressing Tom.
>phil
>
>-----Original Message-----
>From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of Ruedig=
er.Geib@telekom.de
>Sent: 22 June 2011 07:21
>To: tom111.taylor@bell.net; ietfdbh@comcast.net
>Cc: pcn@ietf.org; gen-art@ietf.org; elwynd@dial.pipex.com
>Subject: Re: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08
>
>Hi Tom,
>
>which work are you taking up?
>
>- specifying the madatory to implement protocol.
>- or specifying a minimum clear information model (RFC3444).
>
>I prefer the latter above the former.
>
>
>Regards,
>
>Ruediger
>
>-----Original Message-----
>From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of Tom Ta=
ylor
>Sent: Wednesday, June 22, 2011 2:31 AM
>To: David Harrington
>Cc: pcn@ietf.org; 'Elwyn Davies'; 'General Area Reviwing Team'
>Subject: Re: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08
>
>OK, I'll take up the good work. Just to start with, I propose to submit
>interim updates as I wished I had back a few months ago. I'll go on from
>there.
>
>On 21/06/2011 3:49 PM, David Harrington wrote:
>> Hi,
>>
>> The WG was chartered to specify the
>> (3) encoding and transport of (pre-)congestion information
>>   between the interior and domain egress
>> ... and ...
>> (5) encoding and transport of (pre-)congestion information
>>   between the egress and the controlling domain ingress
>>
>> I interpret that to mean the transport protocol and the message
>> formats should be specified in the documents.
>> I have to agree with Elwyn that lack of such formats means
>> implementations are likely to not be interoperable.
>> I am not sure what protocols would be suitable for these tasks; other
>> readers may have similar concerns.
>>
>> I think the specification would benefit from a mandatory-to-implement
>> protocol expected to carry the configuration and reported information.
>> At a minimum, there should be a clear information model (RFC3444)
>> about the information to be transported.
>> The data type and range of values should be included in the
>> information model for each counter and configuration variable.
>> I think it would be better to specify a mandatory-to-implement
>> protocol, or at least a recommended-to-implement protocol, and a
>> corresponding data model to ensure interoperability.
>>
>> David Harrington
>> Director, IETF Transport Area
>> ietfdbh@comcast.net (preferred for ietf)
>> dbharrington@huaweisymantec.com
>> +1 603 828 1401 (cell)
>>
>>> -----Original Message-----
>>> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
>>> Sent: Tuesday, June 14, 2011 1:21 PM
>>> To: philip.eardley@bt.com
>>> Cc: pcn@ietf.org; ietfdbh@comcast.net; General Area Reviwing Team
>>> Subject: Re: Gen-art LC review of
>> draft-ietf-pcn-cl-edge-behaviour-08
>>>
>>> Hi, Phil.
>>>
>>> It strikes me that the first and second points below are
>>> something which
>>> David Harrington perhaps ought to give an opinion on. He has got to
>>> defend it to the IESG.
>>>
>>> On the first point, my feeling is that neither the
>>> requirements doc nor
>>> this doc is sufficient to guarantee an interoperable implementation.
>>
>>> There seems to me to be a cleft stick here (irrespective of
>>> whether this
>>> ends up as informational or experimental.) The WG is is specifying
>>> pieces of functionality that go in two or more different
>>> types of boxes
>>> (three if there is a separate implementation of the central decision
>>
>>> point). If the system is going to be generally deployable or
>>> even to be
>>> experimented with there may be different implementations.
>>> The box types
>>> communicate using the information specifications in the doc.  This
>>> appears to require protocol definitions.  Where they are defined is
>>> another issue but I feel it has either to be in this doc or
>>> in another
>>> doc referenced from this.  If they aren't specified I can't see that
>>
>>> anybody will be interested in making commercial implementations.
>>>
>>> I see David didn't make any comment about this situation in his
>> write
>>> up, so maybe I am over reacting.
>>>
>>> Regards,
>>> Elwyn
>>>
>>>
>>>
>>>
>>>
>>> On 13/06/2011 18:04, philip.eardley@bt.com wrote:
>>>> Elwyn,
>>>>
>>>> Thanks for the detailed review.
>>>> A few follow-ups in-line
>>>> Thanks
>>>> phil
>>>>
>>>> --
>>>> Major issues:
>>>> The draft contains partial definitions of two control
>>> protocols (egress
>>>> ->   decision point; decision point ->   ingress).  It does
>>> not make it
>>>> clear whether the reader is expected to get full
>>> definitions of these
>>>> protocols here or whether there will be another document
>>> that specifies
>>>> these protocols completely.  As is stands one could build
>>> the protocols
>>>> and pretty much guarantee that they would not be interoperable
>> with
>>>> other implementations since message formats are not
>>> included although
>>>> high level specs are.  The document needs to be much
>>> clearer about what
>>>> is expected to happen here.
>>>>
>>>> [phil] there is another document, " Requirements for
>>> Signaling of (Pre-) Congestion Information in a DiffServ
>>> Domain"
>>> [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requireme
>>> nts-04] that deals with your issue to some extent. It doesn't
>>> specify message formats but does at least specify better what
>>> information the messages must contain. My understanding is
>>> that unfortunately the WG doesn't feel it has the effort to
>>> specify these protocols completely.
>>>>
>>>>
>>>> Use of EXP codepoint: My understanding of what is said in
>>> RFC 5696 is
>>>> that EXP is supposed to be left for other (non=3DPCN) systems to
>> use.
>>>> This draft uses it.  Is this sensible? Is this whole draft
>>> experimental
>>>> really?
>>>> [phil] the intention of rfc5696 was that the EXP codepoint
>>> is for experimental *PCN* encodings - ie beyond the baseline.
>>> For instance, the CL behaviour needs separate codepoints for
>>> (PCN) threshold-marking and (PCN) excess-traffic-marking&
>>> this would require using the EXP codepoint.
>>>> However...... There is currently some discussion on what
>>> PCN encodings to specify beyond the baseline. At the time we
>>> wrote the baseline, we envisaged the need for several
>>> encodings - however it now seems that one may be enough, in
>>> which case there may possibly be just one PCN encoding (ie a
>>> revised 5696 that now uses the 01 codepoint), so possibly may
>>> be Standards track - ??
>>>> Anyway, i take your point that we need to think about Status.
>>>>
>>>> s3.3.1:
>>>>> [CL-specific] The outcome of the comparison is not very sensitive
>>>>>         to the value of the CLE-limit in practice, because
>>> when threshold-
>>>>>         marking occurs it tends to persist long enough that
>>> threshold-
>>>>>         marked traffic becomes a large proportion of the
>>> received traffic
>>>>>         in a given interval.
>>>> This statement worries me.  It sounds like a characteristic of an
>>>> unstable system.  If the value is that non-critical why are we
>>>> bothering?
>>>>
>>>> [phil] admission control system. imagine the pcn-domain has
>>> one bottleneck link. If it can cope with the current number
>>> of calls (their bandwidth), then no pkts gets
>>> threshold-marked, so the CLE =3D 0. If there are too many, then
>>> all pkts gets threshold-marked, so the CLE =3D 1. If there is
>>> almost exactly the right number of calls, then
>>> threshold-marking will tend to be on for a while, then off
>>> for a while (perhaps when several flows are transmitting less
>>> traffic than normal), so the CLE will jiggle about between 0&
>>>   1. If the CLE is<   CLE-limit (say CLE-limit =3D 0.6&   current
>>> CLE =3D 0.5), when a new call admission request happens to
>>> arrive then it gets admitted. But then there's more traffic
>>> and it's likely that the CLE will rise to 1 - hence another
>>> admission request will get blocked. When a call finishes,
>>> then the reverse is true.
>>>>
>>>> Now suppose we had in fact configured CLE-limit =3D 0.4, then
>>> in the scenario above the call request would have been
>>> blocked. However, (1) the PCN-domain has only admitted one
>>> fewer call, (2) a short time later, either the CLE happens to
>>> be lower or a call departs, and then the next admission
>>> request is accepted.
>>>>
>>>> All this means that it doesn't matter much exactly what you
>>> set CLE-limit to - it barely affects the average number of
>>> calls admitted. The argument above is hand-wavy, but lots of
>>> simulations have been done that show this is true (I hope i'm
>>> representing the results correctly)
>>>> So the lack of sensitivity to CLE-limit seems like a good thing.
>>>>
>>>>
>>>> Minor issues:
>>>>
>>>> s6:  The potential introduction of a centralized decision
>>> point appears
>>>> to provide additional attack points beyond the architecture
>>> in RFC 5559.
>>>> It appears to me that the requests for information about
>>> specific flows
>>>> to the ingress are ighly vulnerable as they (probably)
>>> contain all the
>>>> information needed to craft a DoS attack on the flow.
>>>>
>>>> [phil] seems a good point to me
>>>>
>>>
>>>
>>> --
>>> Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
>>> For more information, see
>>> http://www.oxfam.org.uk/get_involved/fundraise/walk/ and
>>> follow us on Twitter at http://twitter.com/CambOxfamWalk.
>>>
>>>
>>
>> _______________________________________________
>> PCN mailing list
>> PCN@ietf.org
>> https://www.ietf.org/mailman/listinfo/pcn
>>
>>
>_______________________________________________
>PCN mailing list
>PCN@ietf.org
>https://www.ietf.org/mailman/listinfo/pcn
>_______________________________________________
>PCN mailing list
>PCN@ietf.org
>https://www.ietf.org/mailman/listinfo/pcn
>_______________________________________________
>PCN mailing list
>PCN@ietf.org
>https://www.ietf.org/mailman/listinfo/pcn

From ot@cisco.com  Wed Jun 22 03:16:56 2011
Return-Path: <ot@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 41CE111E80DB; Wed, 22 Jun 2011 03:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 O2+eh0ko8bYt; Wed, 22 Jun 2011 03:16:55 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0650A11E80CF; Wed, 22 Jun 2011 03:16:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=2875; q=dns/txt; s=iport; t=1308737815; x=1309947415; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=95F6SG1wQ8nAyw6TlorXsW8PEKTAgt8tfjjIgVA5CVM=; b=elyDQ9tgVP2q4f21TTLWVur0Socu4ylqTJI/o0VDVzEZpExWiWffO7Yf H+xkJSt9y93CKb8EeovVnIT8wmFp5Kh1aacCSxzs+ggPDmQAzl5cN6PyQ w0gdtxZpUd38mjh0VdX8epVPPuDJc8A+U2SQsxUtsJ2dHqlzU7NgiFWR0 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIvAAU6Q/khR/2dsb2JhbABUpw53iHOhDJ5Ahi0EkWqQDg
X-IronPort-AV: E=Sophos;i="4.65,405,1304294400"; d="scan'208";a="95896028"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 22 Jun 2011 10:16:23 +0000
Received: from dhcp-osl-vl300-64-103-53-166.cisco.com (dhcp-osl-vl300-64-103-53-166.cisco.com [64.103.53.166]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5MAGNlm021263; Wed, 22 Jun 2011 10:16:23 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <AE70A313-F36C-4870-A0E8-8F3172F35D53@nostrum.com>
Date: Wed, 22 Jun 2011 12:16:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B5436E8-50C4-45F8-AEC9-56A2C14F19DC@cisco.com>
References: <AE70A313-F36C-4870-A0E8-8F3172F35D53@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Wed, 22 Jun 2011 04:54:53 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-v6ops-6to4-to-historic.all@tools.ietf.org, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-v6ops-6to4-to-historic-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, 22 Jun 2011 10:16:56 -0000

Ben,

splendid comments! I've tried to incorporate all of them, and will =
either issue a new revision or make the changes during AUTH48 depending =
on other LC feedback.

cheers,
Ole

> 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-v6ops-6to4-to-historic-04
> Reviewer: Ben Campbell
> Review Date: 2011-06-17
> IETF LC End Date: 2011-06-20
> IESG Telechat date: 2011-06-23
>=20
> Summary:
>=20
> The draft is essentially ready for publication as an informational =
RFC. I have a few editorial comments that may be worth considering prior =
to final publication.
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
>=20
> -- general:=20
>=20
> Idnits reports some potential issues. please check.
>=20
> -- abstract:
>=20
> The headers say this draft obsoletes these RFCs. Does moving to =
historical obsolete then in that sense? Perhaps the abstract should say =
something like "obsoletes, and moves to historical"
>=20
> -- section 1, 2nd paragraph: "...designed to help transitioning the =
Internet..."
>=20
> Help transition, help in transitioning, or help the transition of
>=20
> -- section 1, last paragraph:
>=20
> Please expand 6rd on first mention. Also, Is this meant as an explicit =
recommendation of 6rd as an alternative?
>=20
> -- section 3, third paragraph: "...same operational burden has =
manually configured tunnels..."
>=20
> s/has/as
>=20
> -- section 3, first bullet: "... and in the case the relay is =
overloaded packet loss."
>=20
> "overloaded, packet loss."
>=20
> -- section 3, third bullet: "...customer relationship or..."
>=20
> "... customer relationship between the end-user and the relay =
operator, or..."
>=20
> -- section 3, 4th bullet: "In case of the reverse path 6to4 relay and =
the anycast forward 6to4 relay, these have to be open for any address. =
Only limited by the scope of the routing advertisement. "
>=20
> Awkward sentence followed by a sentence fragment. Can these be =
reworded?
>=20
> -- section 3, 5th bullet: "black hole"
>=20
> Please define "black hole" in this context, or use a more descriptive =
(I.e. less jargony) term.
>=20
>=20
> -- section 4, 2nd paragraph: "It is expected that disabling 6to4 in =
the IPv6 Internet will take some time."
>=20
> Who expects it? The IETF? v6ops? The authors? (or can we just drop "It =
is expected that")
>=20
> "...deploy native IPv6 service."
>=20
> s/service/services
>=20
> -- section 4, numbered list:
>=20
> It's not clear to me why this is a numbered list rather than an =
ordinary paragraph
>=20


From ietfdbh@comcast.net  Wed Jun 22 07:10:05 2011
Return-Path: <ietfdbh@comcast.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 AFF0221F84FA for <gen-art@ietfa.amsl.com>; Wed, 22 Jun 2011 07:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.493
X-Spam-Level: 
X-Spam-Status: No, score=-102.493 tagged_above=-999 required=5 tests=[AWL=0.106, 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 3FOGSm9heLxp for <gen-art@ietfa.amsl.com>; Wed, 22 Jun 2011 07:10:04 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by ietfa.amsl.com (Postfix) with ESMTP id DB0A221F84F8 for <gen-art@ietf.org>; Wed, 22 Jun 2011 07:10:03 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta01.westchester.pa.mail.comcast.net with comcast id z27u1g0051c6gX8512A4za; Wed, 22 Jun 2011 14:10:04 +0000
Received: from davidPC ([67.189.235.106]) by omta23.westchester.pa.mail.comcast.net with comcast id z2A01g0272JQnJT3j2A1m6; Wed, 22 Jun 2011 14:10:03 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <philip.eardley@bt.com>, <Ruediger.Geib@telekom.de>, <tom111.taylor@bell.net>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk><9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net><4DF7986B.5020108@dial.pipex.com>	<33B5B2B1686A45B6A3739D9D9EB234C7@davidPC><BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl> <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com> <9510D26531EF184D9017DF24659BB87F32E07BCC20@EMV65-UKRD.domain1.systemhost.net>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F32E07BCC20@EMV65-UKRD.domain1.systemhost.net>
Date: Wed, 22 Jun 2011 10:09:55 -0400
Message-ID: <C84665FB1B554A07B8E9249518D5385A@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16807
Thread-Index: Acwwc7boE6jGovIWQu6iS4tZohCwJQAMITDQAAPKtvAAC27UgA==
Cc: pcn@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 14:10:05 -0000

Hi,

The main thing you are missing is an explanation of how you will
achieve interoperability.
The charter calls for specification of the encoding and transport of
the information between points in the system:
> > (3) encoding and transport of (pre-)congestion information
> >   between the interior and domain egress
> > ... and ...
> > (5) encoding and transport of (pre-)congestion information
> >   between the egress and the controlling domain ingress

How will the information get from the interior to the domain egress,
if the PCN processing for the interior node is implemented by vendor A
and the PCN processing for the domain egress node is implemented by
vendor B? In what message format will vendor A send it so that it can
be interpreted consistently by the receiver, regardless of which
vendor implements the receiver? What format validation shoudl be
performed by teh receiever, what conditions constitute a receiving
error, and what error codes should be returned by the receiver that
will be understood by the sender? 

Ditto for the players in 5)

The specification as written seems imcomplete because it does not deal
with specifying the encoding and transport of the information. Am I
just missing it, or is it really just not there? An information model
can help to understand the properties of the data to be transported,
but it doesn't really solve the problem of transporting the data in a
standardized, interoperable manner. You will need to work hard to
convince me that there is strong TECHNICAL justification for not
providing REQUIRED (or at least RECOMMENDED) protocols and message
formats/data models involved. I would likely need to work hard
subsequently to convince the IESG.

If the problem is that the WG has no energy, we can solve that in a
much simpler way than updating these documents - we can just close the
WG. If the WG doesn't have enough energy to complete these documents
first, we can abandon the documents. That could save everybody a lot
of time - WG editors, WG reviewers, WG chairs, the AD, IETF Last Call
reviewers from various directorates, the IESG, IANA ... 

I think the Internet would benefit from this technology, and I would
consider abandoning these documents at this point an awful waste of
time, given how much work has been put into them already, so I
STRONGLY encourage the WG to find the energy to complete their
agreed-upon deliverables, but if it is WG consensus to abandon them, I
guess I would have to accept that WG consensus. 

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

> -----Original Message-----
> From: philip.eardley@bt.com [mailto:philip.eardley@bt.com] 
> Sent: Wednesday, June 22, 2011 4:17 AM
> To: Ruediger.Geib@telekom.de; tom111.taylor@bell.net; 
> ietfdbh@comcast.net
> Cc: pcn@ietf.org; gen-art@ietf.org; elwynd@dial.pipex.com
> Subject: RE: [PCN] Gen-art LC review of 
> draft-ietf-pcn-cl-edge-behaviour-08
> 
> Personally I think it unlikely that the WG would ever 
> complete the former
> 
> The latter might be plausible, though having flicked at 3444 
> i can't tell exactly what we're missing. It seems to say that 
> an information model is an absrtact model about relationships 
> between objects and can be defined informally - (since I 
> havent consciously written one, I'm being vague) - the 
> combination of CL & signalling reqts seems quite close to this?
> 
> Thanks for progressing Tom.
> phil
> 
> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On 
> Behalf Of Ruediger.Geib@telekom.de
> Sent: 22 June 2011 07:21
> To: tom111.taylor@bell.net; ietfdbh@comcast.net
> Cc: pcn@ietf.org; gen-art@ietf.org; elwynd@dial.pipex.com
> Subject: Re: [PCN] Gen-art LC review of 
> draft-ietf-pcn-cl-edge-behaviour-08
> 
> Hi Tom,
> 
> which work are you taking up?
> 
> - specifying the madatory to implement protocol.
> - or specifying a minimum clear information model (RFC3444).
> 
> I prefer the latter above the former.
> 
> 
> Regards,
> 
> Ruediger
> 
> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On 
> Behalf Of Tom Taylor
> Sent: Wednesday, June 22, 2011 2:31 AM
> To: David Harrington
> Cc: pcn@ietf.org; 'Elwyn Davies'; 'General Area Reviwing Team'
> Subject: Re: [PCN] Gen-art LC review of 
> draft-ietf-pcn-cl-edge-behaviour-08
> 
> OK, I'll take up the good work. Just to start with, I propose 
> to submit
> interim updates as I wished I had back a few months ago. I'll 
> go on from
> there.
> 
> On 21/06/2011 3:49 PM, David Harrington wrote:
> > Hi,
> >
> > The WG was chartered to specify the
> > (3) encoding and transport of (pre-)congestion information
> >   between the interior and domain egress
> > ... and ...
> > (5) encoding and transport of (pre-)congestion information
> >   between the egress and the controlling domain ingress
> >
> > I interpret that to mean the transport protocol and the message
> > formats should be specified in the documents.
> > I have to agree with Elwyn that lack of such formats means
> > implementations are likely to not be interoperable.
> > I am not sure what protocols would be suitable for these 
> tasks; other
> > readers may have similar concerns.
> >
> > I think the specification would benefit from a 
> mandatory-to-implement
> > protocol expected to carry the configuration and reported 
> information.
> > At a minimum, there should be a clear information model (RFC3444)
> > about the information to be transported.
> > The data type and range of values should be included in the
> > information model for each counter and configuration variable.
> > I think it would be better to specify a mandatory-to-implement
> > protocol, or at least a recommended-to-implement protocol, and a
> > corresponding data model to ensure interoperability.
> >
> > David Harrington
> > Director, IETF Transport Area
> > ietfdbh@comcast.net (preferred for ietf)
> > dbharrington@huaweisymantec.com
> > +1 603 828 1401 (cell)
> >
> >> -----Original Message-----
> >> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
> >> Sent: Tuesday, June 14, 2011 1:21 PM
> >> To: philip.eardley@bt.com
> >> Cc: pcn@ietf.org; ietfdbh@comcast.net; General Area Reviwing Team
> >> Subject: Re: Gen-art LC review of
> > draft-ietf-pcn-cl-edge-behaviour-08
> >>
> >> Hi, Phil.
> >>
> >> It strikes me that the first and second points below are
> >> something which
> >> David Harrington perhaps ought to give an opinion on. He has got
to
> >> defend it to the IESG.
> >>
> >> On the first point, my feeling is that neither the
> >> requirements doc nor
> >> this doc is sufficient to guarantee an interoperable 
> implementation.
> >
> >> There seems to me to be a cleft stick here (irrespective of
> >> whether this
> >> ends up as informational or experimental.) The WG is is
specifying
> >> pieces of functionality that go in two or more different
> >> types of boxes
> >> (three if there is a separate implementation of the 
> central decision
> >
> >> point). If the system is going to be generally deployable or
> >> even to be
> >> experimented with there may be different implementations.
> >> The box types
> >> communicate using the information specifications in the doc.
This
> >> appears to require protocol definitions.  Where they are defined
is
> >> another issue but I feel it has either to be in this doc or
> >> in another
> >> doc referenced from this.  If they aren't specified I 
> can't see that
> >
> >> anybody will be interested in making commercial implementations.
> >>
> >> I see David didn't make any comment about this situation in his
> > write
> >> up, so maybe I am over reacting.
> >>
> >> Regards,
> >> Elwyn
> >>
> >>
> >>
> >>
> >>
> >> On 13/06/2011 18:04, philip.eardley@bt.com wrote:
> >>> Elwyn,
> >>>
> >>> Thanks for the detailed review.
> >>> A few follow-ups in-line
> >>> Thanks
> >>> phil
> >>>
> >>> --
> >>> Major issues:
> >>> The draft contains partial definitions of two control
> >> protocols (egress
> >>> ->   decision point; decision point ->   ingress).  It does
> >> not make it
> >>> clear whether the reader is expected to get full
> >> definitions of these
> >>> protocols here or whether there will be another document
> >> that specifies
> >>> these protocols completely.  As is stands one could build
> >> the protocols
> >>> and pretty much guarantee that they would not be interoperable
> > with
> >>> other implementations since message formats are not
> >> included although
> >>> high level specs are.  The document needs to be much
> >> clearer about what
> >>> is expected to happen here.
> >>>
> >>> [phil] there is another document, " Requirements for
> >> Signaling of (Pre-) Congestion Information in a DiffServ
> >> Domain"
> >> [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requireme
> >> nts-04] that deals with your issue to some extent. It doesn't
> >> specify message formats but does at least specify better what
> >> information the messages must contain. My understanding is
> >> that unfortunately the WG doesn't feel it has the effort to
> >> specify these protocols completely.
> >>>
> >>>
> >>> Use of EXP codepoint: My understanding of what is said in
> >> RFC 5696 is
> >>> that EXP is supposed to be left for other (non=PCN) systems to
> > use.
> >>> This draft uses it.  Is this sensible? Is this whole draft
> >> experimental
> >>> really?
> >>> [phil] the intention of rfc5696 was that the EXP codepoint
> >> is for experimental *PCN* encodings - ie beyond the baseline.
> >> For instance, the CL behaviour needs separate codepoints for
> >> (PCN) threshold-marking and (PCN) excess-traffic-marking&
> >> this would require using the EXP codepoint.
> >>> However...... There is currently some discussion on what
> >> PCN encodings to specify beyond the baseline. At the time we
> >> wrote the baseline, we envisaged the need for several
> >> encodings - however it now seems that one may be enough, in
> >> which case there may possibly be just one PCN encoding (ie a
> >> revised 5696 that now uses the 01 codepoint), so possibly may
> >> be Standards track - ??
> >>> Anyway, i take your point that we need to think about Status.
> >>>
> >>> s3.3.1:
> >>>> [CL-specific] The outcome of the comparison is not very
sensitive
> >>>>         to the value of the CLE-limit in practice, because
> >> when threshold-
> >>>>         marking occurs it tends to persist long enough that
> >> threshold-
> >>>>         marked traffic becomes a large proportion of the
> >> received traffic
> >>>>         in a given interval.
> >>> This statement worries me.  It sounds like a characteristic of
an
> >>> unstable system.  If the value is that non-critical why are we
> >>> bothering?
> >>>
> >>> [phil] admission control system. imagine the pcn-domain has
> >> one bottleneck link. If it can cope with the current number
> >> of calls (their bandwidth), then no pkts gets
> >> threshold-marked, so the CLE = 0. If there are too many, then
> >> all pkts gets threshold-marked, so the CLE = 1. If there is
> >> almost exactly the right number of calls, then
> >> threshold-marking will tend to be on for a while, then off
> >> for a while (perhaps when several flows are transmitting less
> >> traffic than normal), so the CLE will jiggle about between 0&
> >>   1. If the CLE is<   CLE-limit (say CLE-limit = 0.6&   current
> >> CLE = 0.5), when a new call admission request happens to
> >> arrive then it gets admitted. But then there's more traffic
> >> and it's likely that the CLE will rise to 1 - hence another
> >> admission request will get blocked. When a call finishes,
> >> then the reverse is true.
> >>>
> >>> Now suppose we had in fact configured CLE-limit = 0.4, then
> >> in the scenario above the call request would have been
> >> blocked. However, (1) the PCN-domain has only admitted one
> >> fewer call, (2) a short time later, either the CLE happens to
> >> be lower or a call departs, and then the next admission
> >> request is accepted.
> >>>
> >>> All this means that it doesn't matter much exactly what you
> >> set CLE-limit to - it barely affects the average number of
> >> calls admitted. The argument above is hand-wavy, but lots of
> >> simulations have been done that show this is true (I hope i'm
> >> representing the results correctly)
> >>> So the lack of sensitivity to CLE-limit seems like a good thing.
> >>>
> >>>
> >>> Minor issues:
> >>>
> >>> s6:  The potential introduction of a centralized decision
> >> point appears
> >>> to provide additional attack points beyond the architecture
> >> in RFC 5559.
> >>> It appears to me that the requests for information about
> >> specific flows
> >>> to the ingress are ighly vulnerable as they (probably)
> >> contain all the
> >>> information needed to craft a DoS attack on the flow.
> >>>
> >>> [phil] seems a good point to me
> >>>
> >>
> >>
> >> --
> >> Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
> >> For more information, see
> >> http://www.oxfam.org.uk/get_involved/fundraise/walk/ and
> >> follow us on Twitter at http://twitter.com/CambOxfamWalk.
> >>
> >>
> >
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcn
> >
> >
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
> 


From ietfdbh@comcast.net  Wed Jun 22 07:18:34 2011
Return-Path: <ietfdbh@comcast.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 39F1421F84C4 for <gen-art@ietfa.amsl.com>; Wed, 22 Jun 2011 07:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.098, 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 4zHjuxK9iuAs for <gen-art@ietfa.amsl.com>; Wed, 22 Jun 2011 07:18:32 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfa.amsl.com (Postfix) with ESMTP id 82EF221F84C1 for <gen-art@ietf.org>; Wed, 22 Jun 2011 07:18:32 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta13.westchester.pa.mail.comcast.net with comcast id z2GG1g0050vyq2s5D2JZ0u; Wed, 22 Jun 2011 14:18:33 +0000
Received: from davidPC ([67.189.235.106]) by omta05.westchester.pa.mail.comcast.net with comcast id z2JX1g00u2JQnJT3R2JXWR; Wed, 22 Jun 2011 14:18:32 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <Ruediger.Geib@telekom.de>, <tom111.taylor@bell.net>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk><9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net><4DF7986B.5020108@dial.pipex.com>	<33B5B2B1686A45B6A3739D9D9EB234C7@davidPC> <BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl> <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com>
In-Reply-To: <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com>
Date: Wed, 22 Jun 2011 10:18:25 -0400
Message-ID: <CBD54BA0E2E04568888F338F05107101@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16807
Thread-Index: Acwwc7boE6jGovIWQu6iS4tZohCwJQAMITDQABCht2A=
Cc: pcn@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 14:18:34 -0000

Hi,

Let me clear that an abstract information model alone is not likely to
satisfy the concern, which is interoperability.

> > I think it would be better to specify a mandatory-to-implement
> > protocol, or at least a recommended-to-implement protocol, and a
> > corresponding data model to ensure interoperability.

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

> -----Original Message-----
> From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de] 
> Sent: Wednesday, June 22, 2011 2:21 AM
> To: tom111.taylor@bell.net; ietfdbh@comcast.net
> Cc: pcn@ietf.org; elwynd@dial.pipex.com; gen-art@ietf.org
> Subject: RE: [PCN] Gen-art LC review of 
> draft-ietf-pcn-cl-edge-behaviour-08
> 
> Hi Tom,
> 
> which work are you taking up?
> 
> - specifying the madatory to implement protocol.
> - or specifying a minimum clear information model (RFC3444).
> 
> I prefer the latter above the former.
> 
> 
> Regards,
> 
> Ruediger
> 
> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On 
> Behalf Of Tom Taylor
> Sent: Wednesday, June 22, 2011 2:31 AM
> To: David Harrington
> Cc: pcn@ietf.org; 'Elwyn Davies'; 'General Area Reviwing Team'
> Subject: Re: [PCN] Gen-art LC review of 
> draft-ietf-pcn-cl-edge-behaviour-08
> 
> OK, I'll take up the good work. Just to start with, I propose 
> to submit
> interim updates as I wished I had back a few months ago. I'll 
> go on from
> there.
> 
> On 21/06/2011 3:49 PM, David Harrington wrote:
> > Hi,
> >
> > The WG was chartered to specify the
> > (3) encoding and transport of (pre-)congestion information
> >   between the interior and domain egress
> > ... and ...
> > (5) encoding and transport of (pre-)congestion information
> >   between the egress and the controlling domain ingress
> >
> > I interpret that to mean the transport protocol and the message
> > formats should be specified in the documents.
> > I have to agree with Elwyn that lack of such formats means
> > implementations are likely to not be interoperable.
> > I am not sure what protocols would be suitable for these 
> tasks; other
> > readers may have similar concerns.
> >
> > I think the specification would benefit from a 
> mandatory-to-implement
> > protocol expected to carry the configuration and reported 
> information.
> > At a minimum, there should be a clear information model (RFC3444)
> > about the information to be transported.
> > The data type and range of values should be included in the
> > information model for each counter and configuration variable.
> > I think it would be better to specify a mandatory-to-implement
> > protocol, or at least a recommended-to-implement protocol, and a
> > corresponding data model to ensure interoperability.
> >
> > David Harrington
> > Director, IETF Transport Area
> > ietfdbh@comcast.net (preferred for ietf)
> > dbharrington@huaweisymantec.com
> > +1 603 828 1401 (cell)
> >
> >> -----Original Message-----
> >> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
> >> Sent: Tuesday, June 14, 2011 1:21 PM
> >> To: philip.eardley@bt.com
> >> Cc: pcn@ietf.org; ietfdbh@comcast.net; General Area Reviwing Team
> >> Subject: Re: Gen-art LC review of
> > draft-ietf-pcn-cl-edge-behaviour-08
> >>
> >> Hi, Phil.
> >>
> >> It strikes me that the first and second points below are
> >> something which
> >> David Harrington perhaps ought to give an opinion on. He has got
to
> >> defend it to the IESG.
> >>
> >> On the first point, my feeling is that neither the
> >> requirements doc nor
> >> this doc is sufficient to guarantee an interoperable 
> implementation.
> >
> >> There seems to me to be a cleft stick here (irrespective of
> >> whether this
> >> ends up as informational or experimental.) The WG is is
specifying
> >> pieces of functionality that go in two or more different
> >> types of boxes
> >> (three if there is a separate implementation of the 
> central decision
> >
> >> point). If the system is going to be generally deployable or
> >> even to be
> >> experimented with there may be different implementations.
> >> The box types
> >> communicate using the information specifications in the doc.
This
> >> appears to require protocol definitions.  Where they are defined
is
> >> another issue but I feel it has either to be in this doc or
> >> in another
> >> doc referenced from this.  If they aren't specified I 
> can't see that
> >
> >> anybody will be interested in making commercial implementations.
> >>
> >> I see David didn't make any comment about this situation in his
> > write
> >> up, so maybe I am over reacting.
> >>
> >> Regards,
> >> Elwyn
> >>
> >>
> >>
> >>
> >>
> >> On 13/06/2011 18:04, philip.eardley@bt.com wrote:
> >>> Elwyn,
> >>>
> >>> Thanks for the detailed review.
> >>> A few follow-ups in-line
> >>> Thanks
> >>> phil
> >>>
> >>> --
> >>> Major issues:
> >>> The draft contains partial definitions of two control
> >> protocols (egress
> >>> ->   decision point; decision point ->   ingress).  It does
> >> not make it
> >>> clear whether the reader is expected to get full
> >> definitions of these
> >>> protocols here or whether there will be another document
> >> that specifies
> >>> these protocols completely.  As is stands one could build
> >> the protocols
> >>> and pretty much guarantee that they would not be interoperable
> > with
> >>> other implementations since message formats are not
> >> included although
> >>> high level specs are.  The document needs to be much
> >> clearer about what
> >>> is expected to happen here.
> >>>
> >>> [phil] there is another document, " Requirements for
> >> Signaling of (Pre-) Congestion Information in a DiffServ
> >> Domain"
> >> [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requireme
> >> nts-04] that deals with your issue to some extent. It doesn't
> >> specify message formats but does at least specify better what
> >> information the messages must contain. My understanding is
> >> that unfortunately the WG doesn't feel it has the effort to
> >> specify these protocols completely.
> >>>
> >>>
> >>> Use of EXP codepoint: My understanding of what is said in
> >> RFC 5696 is
> >>> that EXP is supposed to be left for other (non=PCN) systems to
> > use.
> >>> This draft uses it.  Is this sensible? Is this whole draft
> >> experimental
> >>> really?
> >>> [phil] the intention of rfc5696 was that the EXP codepoint
> >> is for experimental *PCN* encodings - ie beyond the baseline.
> >> For instance, the CL behaviour needs separate codepoints for
> >> (PCN) threshold-marking and (PCN) excess-traffic-marking&
> >> this would require using the EXP codepoint.
> >>> However...... There is currently some discussion on what
> >> PCN encodings to specify beyond the baseline. At the time we
> >> wrote the baseline, we envisaged the need for several
> >> encodings - however it now seems that one may be enough, in
> >> which case there may possibly be just one PCN encoding (ie a
> >> revised 5696 that now uses the 01 codepoint), so possibly may
> >> be Standards track - ??
> >>> Anyway, i take your point that we need to think about Status.
> >>>
> >>> s3.3.1:
> >>>> [CL-specific] The outcome of the comparison is not very
sensitive
> >>>>         to the value of the CLE-limit in practice, because
> >> when threshold-
> >>>>         marking occurs it tends to persist long enough that
> >> threshold-
> >>>>         marked traffic becomes a large proportion of the
> >> received traffic
> >>>>         in a given interval.
> >>> This statement worries me.  It sounds like a characteristic of
an
> >>> unstable system.  If the value is that non-critical why are we
> >>> bothering?
> >>>
> >>> [phil] admission control system. imagine the pcn-domain has
> >> one bottleneck link. If it can cope with the current number
> >> of calls (their bandwidth), then no pkts gets
> >> threshold-marked, so the CLE = 0. If there are too many, then
> >> all pkts gets threshold-marked, so the CLE = 1. If there is
> >> almost exactly the right number of calls, then
> >> threshold-marking will tend to be on for a while, then off
> >> for a while (perhaps when several flows are transmitting less
> >> traffic than normal), so the CLE will jiggle about between 0&
> >>   1. If the CLE is<   CLE-limit (say CLE-limit = 0.6&   current
> >> CLE = 0.5), when a new call admission request happens to
> >> arrive then it gets admitted. But then there's more traffic
> >> and it's likely that the CLE will rise to 1 - hence another
> >> admission request will get blocked. When a call finishes,
> >> then the reverse is true.
> >>>
> >>> Now suppose we had in fact configured CLE-limit = 0.4, then
> >> in the scenario above the call request would have been
> >> blocked. However, (1) the PCN-domain has only admitted one
> >> fewer call, (2) a short time later, either the CLE happens to
> >> be lower or a call departs, and then the next admission
> >> request is accepted.
> >>>
> >>> All this means that it doesn't matter much exactly what you
> >> set CLE-limit to - it barely affects the average number of
> >> calls admitted. The argument above is hand-wavy, but lots of
> >> simulations have been done that show this is true (I hope i'm
> >> representing the results correctly)
> >>> So the lack of sensitivity to CLE-limit seems like a good thing.
> >>>
> >>>
> >>> Minor issues:
> >>>
> >>> s6:  The potential introduction of a centralized decision
> >> point appears
> >>> to provide additional attack points beyond the architecture
> >> in RFC 5559.
> >>> It appears to me that the requests for information about
> >> specific flows
> >>> to the ingress are ighly vulnerable as they (probably)
> >> contain all the
> >>> information needed to craft a DoS attack on the flow.
> >>>
> >>> [phil] seems a good point to me
> >>>
> >>
> >>
> >> --
> >> Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
> >> For more information, see
> >> http://www.oxfam.org.uk/get_involved/fundraise/walk/ and
> >> follow us on Twitter at http://twitter.com/CambOxfamWalk.
> >>
> >>
> >
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcn
> >
> >
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
> 


From philip.eardley@bt.com  Wed Jun 22 07:36:35 2011
Return-Path: <philip.eardley@bt.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 6EC9821F8440; Wed, 22 Jun 2011 07:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.686
X-Spam-Level: 
X-Spam-Status: No, score=-102.686 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_72=0.6, 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 njvZjua5W5rp; Wed, 22 Jun 2011 07:36:34 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp63.intersmtp.COM [62.239.224.236]) by ietfa.amsl.com (Postfix) with ESMTP id B09D421F843A; Wed, 22 Jun 2011 07:36:33 -0700 (PDT)
Received: from EVMHT62-UKRD.domain1.systemhost.net (10.36.3.128) by RDW083A007ED63.smtp-e3.hygiene.service (10.187.98.12) with Microsoft SMTP Server (TLS) id 8.3.159.2; Wed, 22 Jun 2011 15:36:26 +0100
Received: from EMV65-UKRD.domain1.systemhost.net ([169.254.2.222]) by EVMHT62-UKRD.domain1.systemhost.net ([10.36.3.128]) with mapi; Wed, 22 Jun 2011 15:36:26 +0100
From: <philip.eardley@bt.com>
To: <ietfdbh@comcast.net>, <Ruediger.Geib@telekom.de>, <tom111.taylor@bell.net>
Date: Wed, 22 Jun 2011 15:36:24 +0100
Thread-Topic: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08
Thread-Index: Acwwc7boE6jGovIWQu6iS4tZohCwJQAMITDQAAPKtvAAC27UgAABWtlQ
Message-ID: <9510D26531EF184D9017DF24659BB87F32E084F2BB@EMV65-UKRD.domain1.systemhost.net>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk><9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net><4DF7986B.5020108@dial.pipex.com> <33B5B2B1686A45B6A3739D9D9EB234C7@davidPC><BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl> <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com> <9510D26531EF184D9017DF24659BB87F32E07BCC20@EMV65-UKRD.domain1.systemhost.net> <C84665FB1B554A07B8E9249518D5385A@davidPC>
In-Reply-To: <C84665FB1B554A07B8E9249518D5385A@davidPC>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: pcn@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 14:36:36 -0000

I take your point that ideally there would be an explanation of how to achi=
eve interoperability and that it would have formats, error codes etc specif=
ied. I guess this would be a rfc3444 Data Model.

Reading your (DH's) latest email, it sounds like you'd need this (rather th=
an what I thought an Information Model might be - which it sounded earlier =
would be sufficient)

I agree with all your comments about shutting the WG; I guess something wor=
th discussing f2f in Quebec, informally & in the wg session.

Whatever, there is still the stuff on standardising the 3-in-1 encoding - w=
hich can proceed whatever we decide on this. We had some discussions a week=
 or two back, which seem to have stopped (not sure we really reached a conc=
lusion though!)

Best wishes,
phil

-----Original Message-----
From: David Harrington [mailto:ietfdbh@comcast.net]
Sent: 22 June 2011 15:10
To: Eardley,PL,Philip,DES8 R; Ruediger.Geib@telekom.de; tom111.taylor@bell.=
net
Cc: pcn@ietf.org; gen-art@ietf.org; elwynd@dial.pipex.com
Subject: RE: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08

Hi,

The main thing you are missing is an explanation of how you will
achieve interoperability.
The charter calls for specification of the encoding and transport of
the information between points in the system:
> > (3) encoding and transport of (pre-)congestion information
> >   between the interior and domain egress
> > ... and ...
> > (5) encoding and transport of (pre-)congestion information
> >   between the egress and the controlling domain ingress

How will the information get from the interior to the domain egress,
if the PCN processing for the interior node is implemented by vendor A
and the PCN processing for the domain egress node is implemented by
vendor B? In what message format will vendor A send it so that it can
be interpreted consistently by the receiver, regardless of which
vendor implements the receiver? What format validation shoudl be
performed by teh receiever, what conditions constitute a receiving
error, and what error codes should be returned by the receiver that
will be understood by the sender?

Ditto for the players in 5)

The specification as written seems imcomplete because it does not deal
with specifying the encoding and transport of the information. Am I
just missing it, or is it really just not there? An information model
can help to understand the properties of the data to be transported,
but it doesn't really solve the problem of transporting the data in a
standardized, interoperable manner. You will need to work hard to
convince me that there is strong TECHNICAL justification for not
providing REQUIRED (or at least RECOMMENDED) protocols and message
formats/data models involved. I would likely need to work hard
subsequently to convince the IESG.

If the problem is that the WG has no energy, we can solve that in a
much simpler way than updating these documents - we can just close the
WG. If the WG doesn't have enough energy to complete these documents
first, we can abandon the documents. That could save everybody a lot
of time - WG editors, WG reviewers, WG chairs, the AD, IETF Last Call
reviewers from various directorates, the IESG, IANA ...

I think the Internet would benefit from this technology, and I would
consider abandoning these documents at this point an awful waste of
time, given how much work has been put into them already, so I
STRONGLY encourage the WG to find the energy to complete their
agreed-upon deliverables, but if it is WG consensus to abandon them, I
guess I would have to accept that WG consensus.

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

> -----Original Message-----
> From: philip.eardley@bt.com [mailto:philip.eardley@bt.com]
> Sent: Wednesday, June 22, 2011 4:17 AM
> To: Ruediger.Geib@telekom.de; tom111.taylor@bell.net;
> ietfdbh@comcast.net
> Cc: pcn@ietf.org; gen-art@ietf.org; elwynd@dial.pipex.com
> Subject: RE: [PCN] Gen-art LC review of
> draft-ietf-pcn-cl-edge-behaviour-08
>
> Personally I think it unlikely that the WG would ever
> complete the former
>
> The latter might be plausible, though having flicked at 3444
> i can't tell exactly what we're missing. It seems to say that
> an information model is an absrtact model about relationships
> between objects and can be defined informally - (since I
> havent consciously written one, I'm being vague) - the
> combination of CL & signalling reqts seems quite close to this?
>
> Thanks for progressing Tom.
> phil
>
> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On
> Behalf Of Ruediger.Geib@telekom.de
> Sent: 22 June 2011 07:21
> To: tom111.taylor@bell.net; ietfdbh@comcast.net
> Cc: pcn@ietf.org; gen-art@ietf.org; elwynd@dial.pipex.com
> Subject: Re: [PCN] Gen-art LC review of
> draft-ietf-pcn-cl-edge-behaviour-08
>
> Hi Tom,
>
> which work are you taking up?
>
> - specifying the madatory to implement protocol.
> - or specifying a minimum clear information model (RFC3444).
>
> I prefer the latter above the former.
>
>
> Regards,
>
> Ruediger
>
> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On
> Behalf Of Tom Taylor
> Sent: Wednesday, June 22, 2011 2:31 AM
> To: David Harrington
> Cc: pcn@ietf.org; 'Elwyn Davies'; 'General Area Reviwing Team'
> Subject: Re: [PCN] Gen-art LC review of
> draft-ietf-pcn-cl-edge-behaviour-08
>
> OK, I'll take up the good work. Just to start with, I propose
> to submit
> interim updates as I wished I had back a few months ago. I'll
> go on from
> there.
>
> On 21/06/2011 3:49 PM, David Harrington wrote:
> > Hi,
> >
> > The WG was chartered to specify the
> > (3) encoding and transport of (pre-)congestion information
> >   between the interior and domain egress
> > ... and ...
> > (5) encoding and transport of (pre-)congestion information
> >   between the egress and the controlling domain ingress
> >
> > I interpret that to mean the transport protocol and the message
> > formats should be specified in the documents.
> > I have to agree with Elwyn that lack of such formats means
> > implementations are likely to not be interoperable.
> > I am not sure what protocols would be suitable for these
> tasks; other
> > readers may have similar concerns.
> >
> > I think the specification would benefit from a
> mandatory-to-implement
> > protocol expected to carry the configuration and reported
> information.
> > At a minimum, there should be a clear information model (RFC3444)
> > about the information to be transported.
> > The data type and range of values should be included in the
> > information model for each counter and configuration variable.
> > I think it would be better to specify a mandatory-to-implement
> > protocol, or at least a recommended-to-implement protocol, and a
> > corresponding data model to ensure interoperability.
> >
> > David Harrington
> > Director, IETF Transport Area
> > ietfdbh@comcast.net (preferred for ietf)
> > dbharrington@huaweisymantec.com
> > +1 603 828 1401 (cell)
> >
> >> -----Original Message-----
> >> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
> >> Sent: Tuesday, June 14, 2011 1:21 PM
> >> To: philip.eardley@bt.com
> >> Cc: pcn@ietf.org; ietfdbh@comcast.net; General Area Reviwing Team
> >> Subject: Re: Gen-art LC review of
> > draft-ietf-pcn-cl-edge-behaviour-08
> >>
> >> Hi, Phil.
> >>
> >> It strikes me that the first and second points below are
> >> something which
> >> David Harrington perhaps ought to give an opinion on. He has got
to
> >> defend it to the IESG.
> >>
> >> On the first point, my feeling is that neither the
> >> requirements doc nor
> >> this doc is sufficient to guarantee an interoperable
> implementation.
> >
> >> There seems to me to be a cleft stick here (irrespective of
> >> whether this
> >> ends up as informational or experimental.) The WG is is
specifying
> >> pieces of functionality that go in two or more different
> >> types of boxes
> >> (three if there is a separate implementation of the
> central decision
> >
> >> point). If the system is going to be generally deployable or
> >> even to be
> >> experimented with there may be different implementations.
> >> The box types
> >> communicate using the information specifications in the doc.
This
> >> appears to require protocol definitions.  Where they are defined
is
> >> another issue but I feel it has either to be in this doc or
> >> in another
> >> doc referenced from this.  If they aren't specified I
> can't see that
> >
> >> anybody will be interested in making commercial implementations.
> >>
> >> I see David didn't make any comment about this situation in his
> > write
> >> up, so maybe I am over reacting.
> >>
> >> Regards,
> >> Elwyn
> >>
> >>
> >>
> >>
> >>
> >> On 13/06/2011 18:04, philip.eardley@bt.com wrote:
> >>> Elwyn,
> >>>
> >>> Thanks for the detailed review.
> >>> A few follow-ups in-line
> >>> Thanks
> >>> phil
> >>>
> >>> --
> >>> Major issues:
> >>> The draft contains partial definitions of two control
> >> protocols (egress
> >>> ->   decision point; decision point ->   ingress).  It does
> >> not make it
> >>> clear whether the reader is expected to get full
> >> definitions of these
> >>> protocols here or whether there will be another document
> >> that specifies
> >>> these protocols completely.  As is stands one could build
> >> the protocols
> >>> and pretty much guarantee that they would not be interoperable
> > with
> >>> other implementations since message formats are not
> >> included although
> >>> high level specs are.  The document needs to be much
> >> clearer about what
> >>> is expected to happen here.
> >>>
> >>> [phil] there is another document, " Requirements for
> >> Signaling of (Pre-) Congestion Information in a DiffServ
> >> Domain"
> >> [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requireme
> >> nts-04] that deals with your issue to some extent. It doesn't
> >> specify message formats but does at least specify better what
> >> information the messages must contain. My understanding is
> >> that unfortunately the WG doesn't feel it has the effort to
> >> specify these protocols completely.
> >>>
> >>>
> >>> Use of EXP codepoint: My understanding of what is said in
> >> RFC 5696 is
> >>> that EXP is supposed to be left for other (non=3DPCN) systems to
> > use.
> >>> This draft uses it.  Is this sensible? Is this whole draft
> >> experimental
> >>> really?
> >>> [phil] the intention of rfc5696 was that the EXP codepoint
> >> is for experimental *PCN* encodings - ie beyond the baseline.
> >> For instance, the CL behaviour needs separate codepoints for
> >> (PCN) threshold-marking and (PCN) excess-traffic-marking&
> >> this would require using the EXP codepoint.
> >>> However...... There is currently some discussion on what
> >> PCN encodings to specify beyond the baseline. At the time we
> >> wrote the baseline, we envisaged the need for several
> >> encodings - however it now seems that one may be enough, in
> >> which case there may possibly be just one PCN encoding (ie a
> >> revised 5696 that now uses the 01 codepoint), so possibly may
> >> be Standards track - ??
> >>> Anyway, i take your point that we need to think about Status.
> >>>
> >>> s3.3.1:
> >>>> [CL-specific] The outcome of the comparison is not very
sensitive
> >>>>         to the value of the CLE-limit in practice, because
> >> when threshold-
> >>>>         marking occurs it tends to persist long enough that
> >> threshold-
> >>>>         marked traffic becomes a large proportion of the
> >> received traffic
> >>>>         in a given interval.
> >>> This statement worries me.  It sounds like a characteristic of
an
> >>> unstable system.  If the value is that non-critical why are we
> >>> bothering?
> >>>
> >>> [phil] admission control system. imagine the pcn-domain has
> >> one bottleneck link. If it can cope with the current number
> >> of calls (their bandwidth), then no pkts gets
> >> threshold-marked, so the CLE =3D 0. If there are too many, then
> >> all pkts gets threshold-marked, so the CLE =3D 1. If there is
> >> almost exactly the right number of calls, then
> >> threshold-marking will tend to be on for a while, then off
> >> for a while (perhaps when several flows are transmitting less
> >> traffic than normal), so the CLE will jiggle about between 0&
> >>   1. If the CLE is<   CLE-limit (say CLE-limit =3D 0.6&   current
> >> CLE =3D 0.5), when a new call admission request happens to
> >> arrive then it gets admitted. But then there's more traffic
> >> and it's likely that the CLE will rise to 1 - hence another
> >> admission request will get blocked. When a call finishes,
> >> then the reverse is true.
> >>>
> >>> Now suppose we had in fact configured CLE-limit =3D 0.4, then
> >> in the scenario above the call request would have been
> >> blocked. However, (1) the PCN-domain has only admitted one
> >> fewer call, (2) a short time later, either the CLE happens to
> >> be lower or a call departs, and then the next admission
> >> request is accepted.
> >>>
> >>> All this means that it doesn't matter much exactly what you
> >> set CLE-limit to - it barely affects the average number of
> >> calls admitted. The argument above is hand-wavy, but lots of
> >> simulations have been done that show this is true (I hope i'm
> >> representing the results correctly)
> >>> So the lack of sensitivity to CLE-limit seems like a good thing.
> >>>
> >>>
> >>> Minor issues:
> >>>
> >>> s6:  The potential introduction of a centralized decision
> >> point appears
> >>> to provide additional attack points beyond the architecture
> >> in RFC 5559.
> >>> It appears to me that the requests for information about
> >> specific flows
> >>> to the ingress are ighly vulnerable as they (probably)
> >> contain all the
> >>> information needed to craft a DoS attack on the flow.
> >>>
> >>> [phil] seems a good point to me
> >>>
> >>
> >>
> >> --
> >> Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
> >> For more information, see
> >> http://www.oxfam.org.uk/get_involved/fundraise/walk/ and
> >> follow us on Twitter at http://twitter.com/CambOxfamWalk.
> >>
> >>
> >
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcn
> >
> >
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>


From Ruediger.Geib@telekom.de  Wed Jun 22 08:01:59 2011
Return-Path: <Ruediger.Geib@telekom.de>
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 8057011E808E; Wed, 22 Jun 2011 08:01:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 3WHsODZc-duJ; Wed, 22 Jun 2011 08:01:58 -0700 (PDT)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by ietfa.amsl.com (Postfix) with ESMTP id 6352E11E807A; Wed, 22 Jun 2011 08:01:57 -0700 (PDT)
Received: from he110889.emea1.cds.t-internal.com ([10.134.92.130]) by tcmail71.telekom.de with ESMTP/TLS/AES128-SHA; 22 Jun 2011 17:01:42 +0200
Received: from HE111648.emea1.cds.t-internal.com ([169.254.5.233]) by HE110889.emea1.cds.t-internal.com ([fe80::841f:f92c:15ca:8526%16]) with mapi; Wed, 22 Jun 2011 17:01:42 +0200
From: <Ruediger.Geib@telekom.de>
To: <ietfdbh@comcast.net>, <tom111.taylor@bell.net>
Date: Wed, 22 Jun 2011 17:01:41 +0200
Thread-Topic: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08
Thread-Index: Acwwc7boE6jGovIWQu6iS4tZohCwJQAMITDQABCht2AAAQKP8A==
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF0D0A@HE111648.emea1.cds.t-internal.com>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk><9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net><4DF7986B.5020108@dial.pipex.com> <33B5B2B1686A45B6A3739D9D9EB234C7@davidPC> <BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl> <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com> <CBD54BA0E2E04568888F338F05107101@davidPC>
In-Reply-To: <CBD54BA0E2E04568888F338F05107101@davidPC>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 22 Jun 2011 08:16:02 -0700
Cc: pcn@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 15:01:59 -0000

Hi David,

Interoperability would result if no feedback signaling is required.
I'm co-author of a draft describing such a solution. Unfortunately
the remaining participants of the WG favour signaling based solutions,
hence perspectives aren't bright for the draft supported by me.

To me, the WG has worked largely successfully. The mechanisms
standardised so far are fairly good.

Regards,

Ruediger


-----Original Message-----
From: David Harrington [mailto:ietfdbh@comcast.net]
Sent: Wednesday, June 22, 2011 4:18 PM
To: Geib, R=FCdiger; tom111.taylor@bell.net
Cc: pcn@ietf.org; elwynd@dial.pipex.com; gen-art@ietf.org
Subject: RE: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08

Hi,

Let me clear that an abstract information model alone is not likely to
satisfy the concern, which is interoperability.

> > I think it would be better to specify a mandatory-to-implement
> > protocol, or at least a recommended-to-implement protocol, and a
> > corresponding data model to ensure interoperability.

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

> -----Original Message-----
> From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]
> Sent: Wednesday, June 22, 2011 2:21 AM
> To: tom111.taylor@bell.net; ietfdbh@comcast.net
> Cc: pcn@ietf.org; elwynd@dial.pipex.com; gen-art@ietf.org
> Subject: RE: [PCN] Gen-art LC review of
> draft-ietf-pcn-cl-edge-behaviour-08
>
> Hi Tom,
>
> which work are you taking up?
>
> - specifying the madatory to implement protocol.
> - or specifying a minimum clear information model (RFC3444).
>
> I prefer the latter above the former.
>
>
> Regards,
>
> Ruediger
>
> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On
> Behalf Of Tom Taylor
> Sent: Wednesday, June 22, 2011 2:31 AM
> To: David Harrington
> Cc: pcn@ietf.org; 'Elwyn Davies'; 'General Area Reviwing Team'
> Subject: Re: [PCN] Gen-art LC review of
> draft-ietf-pcn-cl-edge-behaviour-08
>
> OK, I'll take up the good work. Just to start with, I propose
> to submit
> interim updates as I wished I had back a few months ago. I'll
> go on from
> there.
>
> On 21/06/2011 3:49 PM, David Harrington wrote:
> > Hi,
> >
> > The WG was chartered to specify the
> > (3) encoding and transport of (pre-)congestion information
> >   between the interior and domain egress
> > ... and ...
> > (5) encoding and transport of (pre-)congestion information
> >   between the egress and the controlling domain ingress
> >
> > I interpret that to mean the transport protocol and the message
> > formats should be specified in the documents.
> > I have to agree with Elwyn that lack of such formats means
> > implementations are likely to not be interoperable.
> > I am not sure what protocols would be suitable for these
> tasks; other
> > readers may have similar concerns.
> >
> > I think the specification would benefit from a
> mandatory-to-implement
> > protocol expected to carry the configuration and reported
> information.
> > At a minimum, there should be a clear information model (RFC3444)
> > about the information to be transported.
> > The data type and range of values should be included in the
> > information model for each counter and configuration variable.
> > I think it would be better to specify a mandatory-to-implement
> > protocol, or at least a recommended-to-implement protocol, and a
> > corresponding data model to ensure interoperability.
> >
> > David Harrington
> > Director, IETF Transport Area
> > ietfdbh@comcast.net (preferred for ietf)
> > dbharrington@huaweisymantec.com
> > +1 603 828 1401 (cell)
> >
> >> -----Original Message-----
> >> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
> >> Sent: Tuesday, June 14, 2011 1:21 PM
> >> To: philip.eardley@bt.com
> >> Cc: pcn@ietf.org; ietfdbh@comcast.net; General Area Reviwing Team
> >> Subject: Re: Gen-art LC review of
> > draft-ietf-pcn-cl-edge-behaviour-08
> >>
> >> Hi, Phil.
> >>
> >> It strikes me that the first and second points below are
> >> something which
> >> David Harrington perhaps ought to give an opinion on. He has got
to
> >> defend it to the IESG.
> >>
> >> On the first point, my feeling is that neither the
> >> requirements doc nor
> >> this doc is sufficient to guarantee an interoperable
> implementation.
> >
> >> There seems to me to be a cleft stick here (irrespective of
> >> whether this
> >> ends up as informational or experimental.) The WG is is
specifying
> >> pieces of functionality that go in two or more different
> >> types of boxes
> >> (three if there is a separate implementation of the
> central decision
> >
> >> point). If the system is going to be generally deployable or
> >> even to be
> >> experimented with there may be different implementations.
> >> The box types
> >> communicate using the information specifications in the doc.
This
> >> appears to require protocol definitions.  Where they are defined
is
> >> another issue but I feel it has either to be in this doc or
> >> in another
> >> doc referenced from this.  If they aren't specified I
> can't see that
> >
> >> anybody will be interested in making commercial implementations.
> >>
> >> I see David didn't make any comment about this situation in his
> > write
> >> up, so maybe I am over reacting.
> >>
> >> Regards,
> >> Elwyn
> >>
> >>
> >>
> >>
> >>
> >> On 13/06/2011 18:04, philip.eardley@bt.com wrote:
> >>> Elwyn,
> >>>
> >>> Thanks for the detailed review.
> >>> A few follow-ups in-line
> >>> Thanks
> >>> phil
> >>>
> >>> --
> >>> Major issues:
> >>> The draft contains partial definitions of two control
> >> protocols (egress
> >>> ->   decision point; decision point ->   ingress).  It does
> >> not make it
> >>> clear whether the reader is expected to get full
> >> definitions of these
> >>> protocols here or whether there will be another document
> >> that specifies
> >>> these protocols completely.  As is stands one could build
> >> the protocols
> >>> and pretty much guarantee that they would not be interoperable
> > with
> >>> other implementations since message formats are not
> >> included although
> >>> high level specs are.  The document needs to be much
> >> clearer about what
> >>> is expected to happen here.
> >>>
> >>> [phil] there is another document, " Requirements for
> >> Signaling of (Pre-) Congestion Information in a DiffServ
> >> Domain"
> >> [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requireme
> >> nts-04] that deals with your issue to some extent. It doesn't
> >> specify message formats but does at least specify better what
> >> information the messages must contain. My understanding is
> >> that unfortunately the WG doesn't feel it has the effort to
> >> specify these protocols completely.
> >>>
> >>>
> >>> Use of EXP codepoint: My understanding of what is said in
> >> RFC 5696 is
> >>> that EXP is supposed to be left for other (non=3DPCN) systems to
> > use.
> >>> This draft uses it.  Is this sensible? Is this whole draft
> >> experimental
> >>> really?
> >>> [phil] the intention of rfc5696 was that the EXP codepoint
> >> is for experimental *PCN* encodings - ie beyond the baseline.
> >> For instance, the CL behaviour needs separate codepoints for
> >> (PCN) threshold-marking and (PCN) excess-traffic-marking&
> >> this would require using the EXP codepoint.
> >>> However...... There is currently some discussion on what
> >> PCN encodings to specify beyond the baseline. At the time we
> >> wrote the baseline, we envisaged the need for several
> >> encodings - however it now seems that one may be enough, in
> >> which case there may possibly be just one PCN encoding (ie a
> >> revised 5696 that now uses the 01 codepoint), so possibly may
> >> be Standards track - ??
> >>> Anyway, i take your point that we need to think about Status.
> >>>
> >>> s3.3.1:
> >>>> [CL-specific] The outcome of the comparison is not very
sensitive
> >>>>         to the value of the CLE-limit in practice, because
> >> when threshold-
> >>>>         marking occurs it tends to persist long enough that
> >> threshold-
> >>>>         marked traffic becomes a large proportion of the
> >> received traffic
> >>>>         in a given interval.
> >>> This statement worries me.  It sounds like a characteristic of
an
> >>> unstable system.  If the value is that non-critical why are we
> >>> bothering?
> >>>
> >>> [phil] admission control system. imagine the pcn-domain has
> >> one bottleneck link. If it can cope with the current number
> >> of calls (their bandwidth), then no pkts gets
> >> threshold-marked, so the CLE =3D 0. If there are too many, then
> >> all pkts gets threshold-marked, so the CLE =3D 1. If there is
> >> almost exactly the right number of calls, then
> >> threshold-marking will tend to be on for a while, then off
> >> for a while (perhaps when several flows are transmitting less
> >> traffic than normal), so the CLE will jiggle about between 0&
> >>   1. If the CLE is<   CLE-limit (say CLE-limit =3D 0.6&   current
> >> CLE =3D 0.5), when a new call admission request happens to
> >> arrive then it gets admitted. But then there's more traffic
> >> and it's likely that the CLE will rise to 1 - hence another
> >> admission request will get blocked. When a call finishes,
> >> then the reverse is true.
> >>>
> >>> Now suppose we had in fact configured CLE-limit =3D 0.4, then
> >> in the scenario above the call request would have been
> >> blocked. However, (1) the PCN-domain has only admitted one
> >> fewer call, (2) a short time later, either the CLE happens to
> >> be lower or a call departs, and then the next admission
> >> request is accepted.
> >>>
> >>> All this means that it doesn't matter much exactly what you
> >> set CLE-limit to - it barely affects the average number of
> >> calls admitted. The argument above is hand-wavy, but lots of
> >> simulations have been done that show this is true (I hope i'm
> >> representing the results correctly)
> >>> So the lack of sensitivity to CLE-limit seems like a good thing.
> >>>
> >>>
> >>> Minor issues:
> >>>
> >>> s6:  The potential introduction of a centralized decision
> >> point appears
> >>> to provide additional attack points beyond the architecture
> >> in RFC 5559.
> >>> It appears to me that the requests for information about
> >> specific flows
> >>> to the ingress are ighly vulnerable as they (probably)
> >> contain all the
> >>> information needed to craft a DoS attack on the flow.
> >>>
> >>> [phil] seems a good point to me
> >>>
> >>
> >>
> >> --
> >> Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
> >> For more information, see
> >> http://www.oxfam.org.uk/get_involved/fundraise/walk/ and
> >> follow us on Twitter at http://twitter.com/CambOxfamWalk.
> >>
> >>
> >
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcn
> >
> >
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>


From ietfdbh@comcast.net  Wed Jun 22 08:40:41 2011
Return-Path: <ietfdbh@comcast.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 86ADC11E80D7 for <gen-art@ietfa.amsl.com>; Wed, 22 Jun 2011 08:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.504
X-Spam-Level: 
X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.095, 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 z0O-ZlnM3oih for <gen-art@ietfa.amsl.com>; Wed, 22 Jun 2011 08:40:40 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by ietfa.amsl.com (Postfix) with ESMTP id 8481B11E80BA for <gen-art@ietf.org>; Wed, 22 Jun 2011 08:40:24 -0700 (PDT)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta14.westchester.pa.mail.comcast.net with comcast id z3Ur1g0030bG4ec5E3gR0Q; Wed, 22 Jun 2011 15:40:25 +0000
Received: from davidPC ([67.189.235.106]) by omta03.westchester.pa.mail.comcast.net with comcast id z3gK1g0032JQnJT3P3gLmh; Wed, 22 Jun 2011 15:40:22 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <Ruediger.Geib@telekom.de>, <tom111.taylor@bell.net>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk><9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net><4DF7986B.5020108@dial.pipex.com><33B5B2B1686A45B6A3739D9D9EB234C7@davidPC> <BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl> <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com> <CBD54BA0E2E04568888F338F05107101@davidPC> <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF0D0A@HE111648.emea1.cds.t-internal.com>
In-Reply-To: <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF0D0A@HE111648.emea1.cds.t-internal.com>
Date: Wed, 22 Jun 2011 11:40:10 -0400
Message-ID: <EF0792E001AD4A1F89459D8F1FCAF90F@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16807
Thread-Index: Acwwc7boE6jGovIWQu6iS4tZohCwJQAMITDQABCht2AAAQKP8AABTocg
Cc: pcn@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 15:40:41 -0000

Hi Ruediger,

Off the top of my head, I would think a signaling approach could
provide for a more coordinated response. YMMV.
I trust the WG had technical reasons for prefering a feedback
signaling approach.=20
I consider the WG to be the experts in this space, so you don't need
to convince me, you need to convince them.

I think this WG has produced some very good documents, including those
under review now.
I think the WG is busy working on other specs right now, thinking they
had completed the CL and SM docs.
However, as Elwyn and I observed in GenArt and AD reviews, the CL and
SM documents still seem incomplete.
They seem to be missing interoperable transport and interoperable data
models.

I hope the WG still has energy, and can redirect some of its energy to
completing these documents so we can get them approved as RFCs.=20

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

> -----Original Message-----
> From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]=20
> Sent: Wednesday, June 22, 2011 11:02 AM
> To: ietfdbh@comcast.net; tom111.taylor@bell.net
> Cc: pcn@ietf.org; elwynd@dial.pipex.com; gen-art@ietf.org
> Subject: RE: [PCN] Gen-art LC review of=20
> draft-ietf-pcn-cl-edge-behaviour-08
>=20
> Hi David,
>=20
> Interoperability would result if no feedback signaling is required.
> I'm co-author of a draft describing such a solution. Unfortunately
> the remaining participants of the WG favour signaling based
solutions,
> hence perspectives aren't bright for the draft supported by me.
>=20
> To me, the WG has worked largely successfully. The mechanisms
> standardised so far are fairly good.
>=20
> Regards,
>=20
> Ruediger
>=20
>=20
> -----Original Message-----
> From: David Harrington [mailto:ietfdbh@comcast.net]
> Sent: Wednesday, June 22, 2011 4:18 PM
> To: Geib, R=FCdiger; tom111.taylor@bell.net
> Cc: pcn@ietf.org; elwynd@dial.pipex.com; gen-art@ietf.org
> Subject: RE: [PCN] Gen-art LC review of=20
> draft-ietf-pcn-cl-edge-behaviour-08
>=20
> Hi,
>=20
> Let me clear that an abstract information model alone is not likely
to
> satisfy the concern, which is interoperability.
>=20
> > > I think it would be better to specify a mandatory-to-implement
> > > protocol, or at least a recommended-to-implement protocol, and a
> > > corresponding data model to ensure interoperability.
>=20
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)
>=20
> > -----Original Message-----
> > From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]
> > Sent: Wednesday, June 22, 2011 2:21 AM
> > To: tom111.taylor@bell.net; ietfdbh@comcast.net
> > Cc: pcn@ietf.org; elwynd@dial.pipex.com; gen-art@ietf.org
> > Subject: RE: [PCN] Gen-art LC review of
> > draft-ietf-pcn-cl-edge-behaviour-08
> >
> > Hi Tom,
> >
> > which work are you taking up?
> >
> > - specifying the madatory to implement protocol.
> > - or specifying a minimum clear information model (RFC3444).
> >
> > I prefer the latter above the former.
> >
> >
> > Regards,
> >
> > Ruediger
> >
> > -----Original Message-----
> > From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On
> > Behalf Of Tom Taylor
> > Sent: Wednesday, June 22, 2011 2:31 AM
> > To: David Harrington
> > Cc: pcn@ietf.org; 'Elwyn Davies'; 'General Area Reviwing Team'
> > Subject: Re: [PCN] Gen-art LC review of
> > draft-ietf-pcn-cl-edge-behaviour-08
> >
> > OK, I'll take up the good work. Just to start with, I propose
> > to submit
> > interim updates as I wished I had back a few months ago. I'll
> > go on from
> > there.
> >
> > On 21/06/2011 3:49 PM, David Harrington wrote:
> > > Hi,
> > >
> > > The WG was chartered to specify the
> > > (3) encoding and transport of (pre-)congestion information
> > >   between the interior and domain egress
> > > ... and ...
> > > (5) encoding and transport of (pre-)congestion information
> > >   between the egress and the controlling domain ingress
> > >
> > > I interpret that to mean the transport protocol and the message
> > > formats should be specified in the documents.
> > > I have to agree with Elwyn that lack of such formats means
> > > implementations are likely to not be interoperable.
> > > I am not sure what protocols would be suitable for these
> > tasks; other
> > > readers may have similar concerns.
> > >
> > > I think the specification would benefit from a
> > mandatory-to-implement
> > > protocol expected to carry the configuration and reported
> > information.
> > > At a minimum, there should be a clear information model
(RFC3444)
> > > about the information to be transported.
> > > The data type and range of values should be included in the
> > > information model for each counter and configuration variable.
> > > I think it would be better to specify a mandatory-to-implement
> > > protocol, or at least a recommended-to-implement protocol, and a
> > > corresponding data model to ensure interoperability.
> > >
> > > David Harrington
> > > Director, IETF Transport Area
> > > ietfdbh@comcast.net (preferred for ietf)
> > > dbharrington@huaweisymantec.com
> > > +1 603 828 1401 (cell)
> > >
> > >> -----Original Message-----
> > >> From: Elwyn Davies [mailto:elwynd@dial.pipex.com]
> > >> Sent: Tuesday, June 14, 2011 1:21 PM
> > >> To: philip.eardley@bt.com
> > >> Cc: pcn@ietf.org; ietfdbh@comcast.net; General Area Reviwing
Team
> > >> Subject: Re: Gen-art LC review of
> > > draft-ietf-pcn-cl-edge-behaviour-08
> > >>
> > >> Hi, Phil.
> > >>
> > >> It strikes me that the first and second points below are
> > >> something which
> > >> David Harrington perhaps ought to give an opinion on. He has
got
> to
> > >> defend it to the IESG.
> > >>
> > >> On the first point, my feeling is that neither the
> > >> requirements doc nor
> > >> this doc is sufficient to guarantee an interoperable
> > implementation.
> > >
> > >> There seems to me to be a cleft stick here (irrespective of
> > >> whether this
> > >> ends up as informational or experimental.) The WG is is
> specifying
> > >> pieces of functionality that go in two or more different
> > >> types of boxes
> > >> (three if there is a separate implementation of the
> > central decision
> > >
> > >> point). If the system is going to be generally deployable or
> > >> even to be
> > >> experimented with there may be different implementations.
> > >> The box types
> > >> communicate using the information specifications in the doc.
> This
> > >> appears to require protocol definitions.  Where they are
defined
> is
> > >> another issue but I feel it has either to be in this doc or
> > >> in another
> > >> doc referenced from this.  If they aren't specified I
> > can't see that
> > >
> > >> anybody will be interested in making commercial
implementations.
> > >>
> > >> I see David didn't make any comment about this situation in his
> > > write
> > >> up, so maybe I am over reacting.
> > >>
> > >> Regards,
> > >> Elwyn
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On 13/06/2011 18:04, philip.eardley@bt.com wrote:
> > >>> Elwyn,
> > >>>
> > >>> Thanks for the detailed review.
> > >>> A few follow-ups in-line
> > >>> Thanks
> > >>> phil
> > >>>
> > >>> --
> > >>> Major issues:
> > >>> The draft contains partial definitions of two control
> > >> protocols (egress
> > >>> ->   decision point; decision point ->   ingress).  It does
> > >> not make it
> > >>> clear whether the reader is expected to get full
> > >> definitions of these
> > >>> protocols here or whether there will be another document
> > >> that specifies
> > >>> these protocols completely.  As is stands one could build
> > >> the protocols
> > >>> and pretty much guarantee that they would not be interoperable
> > > with
> > >>> other implementations since message formats are not
> > >> included although
> > >>> high level specs are.  The document needs to be much
> > >> clearer about what
> > >>> is expected to happen here.
> > >>>
> > >>> [phil] there is another document, " Requirements for
> > >> Signaling of (Pre-) Congestion Information in a DiffServ
> > >> Domain"
> > >> [http://tools.ietf.org/html/draft-ietf-pcn-signaling-requireme
> > >> nts-04] that deals with your issue to some extent. It doesn't
> > >> specify message formats but does at least specify better what
> > >> information the messages must contain. My understanding is
> > >> that unfortunately the WG doesn't feel it has the effort to
> > >> specify these protocols completely.
> > >>>
> > >>>
> > >>> Use of EXP codepoint: My understanding of what is said in
> > >> RFC 5696 is
> > >>> that EXP is supposed to be left for other (non=3DPCN) systems to
> > > use.
> > >>> This draft uses it.  Is this sensible? Is this whole draft
> > >> experimental
> > >>> really?
> > >>> [phil] the intention of rfc5696 was that the EXP codepoint
> > >> is for experimental *PCN* encodings - ie beyond the baseline.
> > >> For instance, the CL behaviour needs separate codepoints for
> > >> (PCN) threshold-marking and (PCN) excess-traffic-marking&
> > >> this would require using the EXP codepoint.
> > >>> However...... There is currently some discussion on what
> > >> PCN encodings to specify beyond the baseline. At the time we
> > >> wrote the baseline, we envisaged the need for several
> > >> encodings - however it now seems that one may be enough, in
> > >> which case there may possibly be just one PCN encoding (ie a
> > >> revised 5696 that now uses the 01 codepoint), so possibly may
> > >> be Standards track - ??
> > >>> Anyway, i take your point that we need to think about Status.
> > >>>
> > >>> s3.3.1:
> > >>>> [CL-specific] The outcome of the comparison is not very
> sensitive
> > >>>>         to the value of the CLE-limit in practice, because
> > >> when threshold-
> > >>>>         marking occurs it tends to persist long enough that
> > >> threshold-
> > >>>>         marked traffic becomes a large proportion of the
> > >> received traffic
> > >>>>         in a given interval.
> > >>> This statement worries me.  It sounds like a characteristic of
> an
> > >>> unstable system.  If the value is that non-critical why are we
> > >>> bothering?
> > >>>
> > >>> [phil] admission control system. imagine the pcn-domain has
> > >> one bottleneck link. If it can cope with the current number
> > >> of calls (their bandwidth), then no pkts gets
> > >> threshold-marked, so the CLE =3D 0. If there are too many, then
> > >> all pkts gets threshold-marked, so the CLE =3D 1. If there is
> > >> almost exactly the right number of calls, then
> > >> threshold-marking will tend to be on for a while, then off
> > >> for a while (perhaps when several flows are transmitting less
> > >> traffic than normal), so the CLE will jiggle about between 0&
> > >>   1. If the CLE is<   CLE-limit (say CLE-limit =3D 0.6&   current
> > >> CLE =3D 0.5), when a new call admission request happens to
> > >> arrive then it gets admitted. But then there's more traffic
> > >> and it's likely that the CLE will rise to 1 - hence another
> > >> admission request will get blocked. When a call finishes,
> > >> then the reverse is true.
> > >>>
> > >>> Now suppose we had in fact configured CLE-limit =3D 0.4, then
> > >> in the scenario above the call request would have been
> > >> blocked. However, (1) the PCN-domain has only admitted one
> > >> fewer call, (2) a short time later, either the CLE happens to
> > >> be lower or a call departs, and then the next admission
> > >> request is accepted.
> > >>>
> > >>> All this means that it doesn't matter much exactly what you
> > >> set CLE-limit to - it barely affects the average number of
> > >> calls admitted. The argument above is hand-wavy, but lots of
> > >> simulations have been done that show this is true (I hope i'm
> > >> representing the results correctly)
> > >>> So the lack of sensitivity to CLE-limit seems like a good
thing.
> > >>>
> > >>>
> > >>> Minor issues:
> > >>>
> > >>> s6:  The potential introduction of a centralized decision
> > >> point appears
> > >>> to provide additional attack points beyond the architecture
> > >> in RFC 5559.
> > >>> It appears to me that the requests for information about
> > >> specific flows
> > >>> to the ingress are ighly vulnerable as they (probably)
> > >> contain all the
> > >>> information needed to craft a DoS attack on the flow.
> > >>>
> > >>> [phil] seems a good point to me
> > >>>
> > >>
> > >>
> > >> --
> > >> Join the Cambridge Oxfam Walk on Sunday 15 May, 2011.
> > >> For more information, see
> > >> http://www.oxfam.org.uk/get_involved/fundraise/walk/ and
> > >> follow us on Twitter at http://twitter.com/CambOxfamWalk.
> > >>
> > >>
> > >
> > > _______________________________________________
> > > PCN mailing list
> > > PCN@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pcn
> > >
> > >
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcn
> >
>=20
>=20


From toby@moncaster.com  Wed Jun 22 08:58:11 2011
Return-Path: <toby@moncaster.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 7F0BE11E8144; Wed, 22 Jun 2011 08:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 BB59pPBLjeSX; Wed, 22 Jun 2011 08:58:10 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by ietfa.amsl.com (Postfix) with ESMTP id 6E08811E807A; Wed, 22 Jun 2011 08:58:10 -0700 (PDT)
Received: from TobysHP (host81-156-178-213.range81-156.btcentralplus.com [81.156.178.213]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0M5Kwt-1RXqAH3g1H-00zSm3; Wed, 22 Jun 2011 17:58:05 +0200
From: "Toby Moncaster" <toby@moncaster.com>
To: "'David Harrington'" <ietfdbh@comcast.net>, <philip.eardley@bt.com>, <Ruediger.Geib@telekom.de>, <tom111.taylor@bell.net>
References: <1307728914.22973.2654.camel@mightyatom.folly.org.uk><9510D26531EF184D9017DF24659BB87F32DF7BF594@EMV65-UKRD.domain1.systemhost.net><4DF7986B.5020108@dial.pipex.com>	<33B5B2B1686A45B6A3739D9D9EB234C7@davidPC><BLU0-SMTP7812F795389AD49E6A9DDFD8500@phx.gbl>	<580BEA5E3B99744AB1F5BFF5E9A3C67D08ADFF041B@HE111648.emea1.cds.t-internal.com>	<9510D26531EF184D9017DF24659BB87F32E07BCC20@EMV65-UKRD.domain1.systemhost.net> <C84665FB1B554A07B8E9249518D5385A@davidPC>
In-Reply-To: <C84665FB1B554A07B8E9249518D5385A@davidPC>
Date: Wed, 22 Jun 2011 16:57:57 +0100
Message-ID: <001c01cc30f5$2a82d5c0$7f888140$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acwwc7boE6jGovIWQu6iS4tZohCwJQAMITDQAAPKtvAAC27UgAAEu0pA
Content-Language: en-gb
X-Provags-ID: V02:K0:d4O/3gN4qUkLNds+3bVcpRTBah5Yk/jBI23Q/Y+eq9s zbmHoLw/66qd1e8DJhg/0Fiu3bh/YeDu2zrjCxNZldeLblcmTE N8tj76NfkLg751ag0yvzwean5GP9MypB5M8RYyXiUrOiADpx0V Oo2NrkLMhoe84oOEjjYhadgP0g5zmvoVCSLqKnBTrD3/Ik8XUz qDpmbwQsh+cXL7IGbEuYBnjewrjF/JjaitOARR5PvM=
X-Mailman-Approved-At: Wed, 22 Jun 2011 09:03:56 -0700
Cc: pcn@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-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: Wed, 22 Jun 2011 15:58:11 -0000

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> David Harrington
> Sent: 22 June 2011 15:10
> To: philip.eardley@bt.com; Ruediger.Geib@telekom.de;
> tom111.taylor@bell.net
> Cc: pcn@ietf.org; gen-art@ietf.org; elwynd@dial.pipex.com
> Subject: Re: [PCN] Gen-art LC review of draft-ietf-pcn-cl-edge-
> behaviour-08
> 
> Hi,


<SNIP>
> 
> If the problem is that the WG has no energy, we can solve that in a
> much simpler way than updating these documents - we can just close the
> WG. If the WG doesn't have enough energy to complete these documents
> first, we can abandon the documents. That could save everybody a lot
> of time - WG editors, WG reviewers, WG chairs, the AD, IETF Last Call
> reviewers from various directorates, the IESG, IANA ...

I think the issue may not be as simple as lack of WG energy so much as lack
of time available. Many in the WG are funded by external sources or work for
large companies, in the current straitened times they probably have to
justify their work to their bosses.

In theory I should have time to do lots of PCN stuff (as I am currently out
of work). However right now I am committed to doing lots of decorating, DIY
etc. My hope is that I can spend a productive few days at the start of July
and I will happily include reviewing other peoples work (as well as getting
3-in-1 encoding shipped). I would volunteer to write the interoperability
stuff, but I have zero experience of that so I would just get it wrong!

> 
> I think the Internet would benefit from this technology, and I would
> consider abandoning these documents at this point an awful waste of
> time, given how much work has been put into them already, so I
> STRONGLY encourage the WG to find the energy to complete their
> agreed-upon deliverables, but if it is WG consensus to abandon them, I
> guess I would have to accept that WG consensus.

I strongly feel it would be a waste to bin PCN at this stage. As you say
there has been some good work done and it would be a shame to lose it.

It sounds like there are a couple of people prepared to put energy into PCN
still and hopefully we can wrap this all up quickly.

Toby


> 
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)

</SNIP>




From scott.brim@gmail.com  Wed Jun 22 14:32:32 2011
Return-Path: <scott.brim@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 2513721F84E5 for <gen-art@ietfa.amsl.com>; Wed, 22 Jun 2011 14:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9zKsCFo6mSOC for <gen-art@ietfa.amsl.com>; Wed, 22 Jun 2011 14:32:31 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4041F21F84E6 for <gen-art@ietf.org>; Wed, 22 Jun 2011 14:32:31 -0700 (PDT)
Received: by iye7 with SMTP id 7so1411671iye.31 for <gen-art@ietf.org>; Wed, 22 Jun 2011 14:32:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=k+/UywdpQUa4ZjNDWwzn1sgyInCt2/clZqmjRxDaGKk=; b=XEqHM4GP+miihmIDaxKbw2RvQUO458pIfSBmOPWdHk7WSKKA/xKTohiTR0KQjnqcaN UvoONJTkhucpmZWBeLKnpQGj+N9chZK1Pl5fZfPwQJ4k7ekTUPRJ/Gb5DOCaS370/nJ+ kpGKWu2HyczZK+LcORwUbP5n6ocxh2Ime4F2k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=EQdjz757YcaBuakR/9y8CakWrUlRDdiCpkRNQ8MNc+6yC10FunE2+P27zB0o1mU+ys 2dU68kfOaAo1mKhAG4YrfvE8u7ReyKkXUpnYGFa6jOOIM4rHS0VpZB8qG1S2InwaE2vO 3SjG1yVM9uG8ypoQLcI8PmuRVWEsN45NkkLNk=
Received: by 10.231.117.24 with SMTP id o24mr133854ibq.69.1308778348051; Wed, 22 Jun 2011 14:32:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.15.198 with HTTP; Wed, 22 Jun 2011 14:32:08 -0700 (PDT)
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 22 Jun 2011 17:32:08 -0400
Message-ID: <BANLkTi=2bpqT=wdcABDZkSPDs3YqkhEX7g@mail.gmail.com>
To: gen-art <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] gen-art review of draft-ietf-mpls-loss-delay-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: Wed, 22 Jun 2011 21:32:32 -0000

Ready for publication as a proposed standard RFC.


That completes my current run of gen-art participation.  Please reduce
me to 0 per month but don't take me out totally yet, and let's find
out what the future brings.  There's a chance I'll have time to do
more in a few months.

Thanks, and see you later ... Scott

From mahoney@nostrum.com  Thu Jun 23 10:38:24 2011
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 23B8711E817E for <gen-art@ietfa.amsl.com>; Thu, 23 Jun 2011 10:38:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zIATkPBrgyjj for <gen-art@ietfa.amsl.com>; Thu, 23 Jun 2011 10:38:23 -0700 (PDT)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by ietfa.amsl.com (Postfix) with ESMTP id 8C24F11E80EF for <gen-art@ietf.org>; Thu, 23 Jun 2011 10:38:16 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-50-10.dllstx.fios.verizon.net [173.71.50.10]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5NHauK9094255 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 23 Jun 2011 12:37:01 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4E0379B7.6050801@nostrum.com>
Date: Thu, 23 Jun 2011 12:36:55 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: gen-art@ietf.org
References: <BANLkTi=2bpqT=wdcABDZkSPDs3YqkhEX7g@mail.gmail.com>
In-Reply-To: <BANLkTi=2bpqT=wdcABDZkSPDs3YqkhEX7g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.50.10 is authenticated by a trusted mechanism)
Subject: Re: [Gen-art] gen-art review of draft-ietf-mpls-loss-delay-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, 23 Jun 2011 17:38:24 -0000

Hi Scott,

Thanks for your reviews, and I wish you well in your new pursuits! Hope 
to see you back soon!

Jean

On 6/22/11 4:32 PM, Scott Brim wrote:
> Ready for publication as a proposed standard RFC.
>
>
> That completes my current run of gen-art participation.  Please reduce
> me to 0 per month but don't take me out totally yet, and let's find
> out what the future brings.  There's a chance I'll have time to do
> more in a few months.
>
> Thanks, and see you later ... Scott
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From mahoney@nostrum.com  Thu Jun 23 11:58:48 2011
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 8609A11E80C4 for <gen-art@ietfa.amsl.com>; Thu, 23 Jun 2011 11:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srsNsiGJFxMP for <gen-art@ietfa.amsl.com>; Thu, 23 Jun 2011 11:58:48 -0700 (PDT)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by ietfa.amsl.com (Postfix) with ESMTP id EDD9311E80E1 for <gen-art@ietf.org>; Thu, 23 Jun 2011 11:58:47 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-50-10.dllstx.fios.verizon.net [173.71.50.10]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5NIvVR6002097 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 23 Jun 2011 13:57:32 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4E038C9B.3070206@nostrum.com>
Date: Thu, 23 Jun 2011 13:57:31 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.50.10 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2011-06-23
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, 23 Jun 2011 18:58:48 -0000

Hi all,

Here's the link to the new LC assignments:
http://wiki.tools.ietf.org/dav/genart/reviewers-110623-lc.html

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 Jun 23 14:31:16 2011
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 5B2EA11E8199 for <gen-art@ietfa.amsl.com>; Thu, 23 Jun 2011 14:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NPZToKMElUCT for <gen-art@ietfa.amsl.com>; Thu, 23 Jun 2011 14:31:15 -0700 (PDT)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by ietfa.amsl.com (Postfix) with ESMTP id 4185B11E81B8 for <gen-art@ietf.org>; Thu, 23 Jun 2011 14:31:15 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-50-10.dllstx.fios.verizon.net [173.71.50.10]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5NLTwRf015957 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 23 Jun 2011 16:29:59 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4E03B056.2020309@nostrum.com>
Date: Thu, 23 Jun 2011 16:29:58 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.50.10 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2011-06-30 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, 23 Jun 2011 21:31:16 -0000

Hi all,

Assignments for the telechat can be found here:
http://wiki.tools.ietf.org/dav/genart/reviewers-110630-telechat.html

With the updated 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 Jun 23 19:54:08 2011
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 7903311E8097; Thu, 23 Jun 2011 19:54:08 -0700 (PDT)
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.189, 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 ZPoSzX+QHpLD; Thu, 23 Jun 2011 19:54:08 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1845511E8071; Thu, 23 Jun 2011 19:54:08 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by morbo.tigertech.net (Postfix) with ESMTP id DF983A63D8; Thu, 23 Jun 2011 19:18:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 8B56532466D4; Thu, 23 Jun 2011 19:17:13 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.49] (unknown [129.192.185.163]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id A3FE0324662A; Thu, 23 Jun 2011 19:17:12 -0700 (PDT)
Message-ID: <4E03F3A5.40905@joelhalpern.com>
Date: Thu, 23 Jun 2011 22:17:09 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4E038C9B.3070206@nostrum.com>
In-Reply-To: <4E038C9B.3070206@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Adrian Farrel <adrian@olddog.co.uk>, gen-art@ietf.org, IETF discussion list <ietf@ietf.org>, Loa Andersson <loa@pi.nu>
Subject: [Gen-art]  Review: draft-ietf-mpls-ldp-p2mp-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: Fri, 24 Jun 2011 02: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-ietf-mpls-ldp-p2mp-14
    Label Distribution Protocol Extensions for Point-to-Multipoint and
              Multipoint-to-Multipoint Label Switched Paths
Reviewer: Joel M. Halpern
Review Date: 23-June-2011
IETF LC End Date: 4-July-2011
IESG Telechat date: N/A

Summary:  This document is close to ready for publication as a Proposed 
Standard RFC>  Certain questions should be answered, and some minor 
issues considered.

Major issues:
     As I read the document, status codes (and stauts TLVs) are for 
reporting on the status of LSPs.  They are not for negotiating 
behaviors.  Thus, I find it very strange that make-before-break behavior 
(section 8) is requested (by a downstream device sending a request to an 
upstream device) by including a specific status code in the request. 
Has this technique been used in MPLS LDP before?

Minor issues:
     The definition (section 1.2)  of MP2MP LSPs should indicate that 
even though all nodes are allowed to send on the LSP, there is still a 
distinguished root node.

     The LDP MP Opaque Value Element extended type (section 2.3, second 
definition) seems to be gratuitous complexity, adding extra matching 
cases in the LDP processing path for no stated value.  Is there really 
believed to be a need for more than 254 types of Opaque values?  If so, 
explain it in the document.

     Section 3.3.1.3 begins by describing two methods for installing the 
upstream path of a MP2MPLSP.  After carefully describing both, it says 
to only and always use the second method.  Would it not be better to 
describe the constraint (that the upstream path must be in place all the 
way to the root before it claims to be established), and then describe 
the one method that meets taht.  Just don't describe a method that is 
not to be used.

Nits/editorial comments:

From Even.roni@huawei.com  Fri Jun 24 00:23:42 2011
Return-Path: <Even.roni@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 331BA11E816A; Fri, 24 Jun 2011 00:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 67sHek8Q+sps; Fri, 24 Jun 2011 00:23:41 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id E0BA011E80B7; Fri, 24 Jun 2011 00:23:40 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNA0021U9U0ZR@szxga04-in.huawei.com>; Fri, 24 Jun 2011 15:22:48 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNA00EUE9U0E4@szxga04-in.huawei.com>; Fri, 24 Jun 2011 15:22:48 +0800 (CST)
Received: from windows8d787f9 ([109.67.30.132]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LNA00J3T9TQ8T@szxml12-in.huawei.com>; Fri, 24 Jun 2011 15:22:48 +0800 (CST)
Date: Fri, 24 Jun 2011 10:20:36 +0300
From: Roni Even <Even.roni@huawei.com>
To: draft-ietf-ftpext2-hosts.all@tools.ietf.org
Message-id: <002e01cc323f$3d9e1340$b8da39c0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_Vzk+GHABmLcAda5ntdoGmA)"
Content-language: en-us
Thread-index: AcwyPzY4XJ2+70MeRCOBBRrApsM2qg==
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC review of draft-ietf-ftpext2-hosts-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 07:23:42 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_Vzk+GHABmLcAda5ntdoGmA)
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-ftpext2-hosts-02

Reviewer: Roni Even

Review Date:2011-6-21

IETF LC End Date: 2011-6-30

IESG Telechat date: 2011-6-30

 

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

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

 


--Boundary_(ID_Vzk+GHABmLcAda5ntdoGmA)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at &lt;<a href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Please resolve these comments along with any other Last Call comments you may receive.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-ftpext2-hosts-02<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"
 Calibri"
Roni Even<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review Date:2011&#8211;6&#8211;21<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC End Date: 2011&#8211;6&#8211;30<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG Telechat date: 2011-6-30<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: This draft is ready for publication as a standard track</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC.<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'
 ><o:p>&n
lass=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major issues:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor issues:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editorial comments:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

--Boundary_(ID_Vzk+GHABmLcAda5ntdoGmA)--

From scott.rose@nist.gov  Fri Jun 24 08:16:45 2011
Return-Path: <scott.rose@nist.gov>
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 150C722801C; Fri, 24 Jun 2011 08:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WG4BqBbAwLNU; Fri, 24 Jun 2011 08:16:44 -0700 (PDT)
Received: from smtp.nist.gov (rimp1.nist.gov [129.6.16.226]) by ietfa.amsl.com (Postfix) with ESMTP id 8A26F228006; Fri, 24 Jun 2011 08:16:43 -0700 (PDT)
Received: from 107-140.antd.nist.gov (107-140.antd.nist.gov [129.6.140.107]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id p5OFGU5T003194; Fri, 24 Jun 2011 11:16:32 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Scott Rose <scott.rose@nist.gov>
In-Reply-To: <42646542-15D4-4ABF-A65F-A0F3361D049A@nostrum.com>
Date: Fri, 24 Jun 2011 11:16:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <86B91666-359A-416F-8D22-A99F2A759BE9@nist.gov>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com> <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com> <42646542-15D4-4ABF-A65F-A0F3361D049A@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1084)
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: scott.rose@nist.gov
X-Mailman-Approved-At: Fri, 24 Jun 2011 08:17:53 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 15:16:45 -0000

FYI:
A new version (-23) of the dname-bis draft has been posted with the two =
sections re-added (resolver algorithm and examples of DNAME use). I =
haven't heard any comments from the DNSEXT WG on it, but it was only =
just posted.

Scott=20

On Jun 8, 2011, at 5:50 PM, Ben Campbell wrote:

> Thanks for the response! Comments below, eliding the bits I think need =
no further comment.
>=20
> On Jun 8, 2011, at 12:11 PM, Scott Rose wrote:
>=20
>> Perhaps the document should only update RFC 2672 instead of =
obsoleting it? =20
>=20
> That would resolve my concern, if it fits with the intent of the work =
group.
>=20
>=20
>>=20
>> As for the nits:
>>=20
>>=20
>> On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> wrote: =
=20
>>=20
>=20
> [...]
>=20
>> Yes, will correct.
>> =20
>> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>>=20
>> Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?
>>=20
>>=20
>> Maybe, but I think the logic was that if there is some text there =
(just something), it can be cleanly referenced (i.e. "DELETED =
[RFCXXXX]")if someone is making a revised version of the RFC for some =
purpose.  Purely deleting it accomplishes the task, but this provides a =
good "hook" for a paper trail.
>>=20
>=20
> Okay. On reflection, it's not like we really render the updates the =
old RFC documents.
>=20
>=20
>> Scott
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Scott Rose
NIST
scott.rose@nist.gov
+1 301-975-8439
Google Voice: +1 571-249-3671
http://www.dnsops.gov/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From ben@nostrum.com  Fri Jun 24 15:20:17 2011
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 D7E4711E80ED; Fri, 24 Jun 2011 15:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.471
X-Spam-Level: 
X-Spam-Status: No, score=-102.471 tagged_above=-999 required=5 tests=[AWL=0.128, 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 LwUOLsttYiwh; Fri, 24 Jun 2011 15:20:12 -0700 (PDT)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by ietfa.amsl.com (Postfix) with ESMTP id 6454211E80E7; Fri, 24 Jun 2011 15:20:12 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5OMItYG061207 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 Jun 2011 17:18:56 -0500 (CDT) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <86B91666-359A-416F-8D22-A99F2A759BE9@nist.gov>
Date: Fri, 24 Jun 2011 17:18:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <16FAD31E-CC87-4110-A43F-4DFBD46536A5@nostrum.com>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com> <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com> <42646542-15D4-4ABF-A65F-A0F3361D049A@nostrum.com> <86B91666-359A-416F-8D22-A99F2A759BE9@nist.gov>
To: Scott Rose <scott.rose@nist.gov>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 22:20:17 -0000

Thanks!

This version resolves all of my comments, with the exception that while =
the text now says the draft updates DNAME, the header still says it =
obsoletes RFC 2672. Is that the intent?

Thanks!

Ben.

On Jun 24, 2011, at 10:16 AM, Scott Rose wrote:

> FYI:
> A new version (-23) of the dname-bis draft has been posted with the =
two sections re-added (resolver algorithm and examples of DNAME use). I =
haven't heard any comments from the DNSEXT WG on it, but it was only =
just posted.
>=20
> Scott=20
>=20
> On Jun 8, 2011, at 5:50 PM, Ben Campbell wrote:
>=20
>> Thanks for the response! Comments below, eliding the bits I think =
need no further comment.
>>=20
>> On Jun 8, 2011, at 12:11 PM, Scott Rose wrote:
>>=20
>>> Perhaps the document should only update RFC 2672 instead of =
obsoleting it? =20
>>=20
>> That would resolve my concern, if it fits with the intent of the work =
group.
>>=20
>>=20
>>>=20
>>> As for the nits:
>>>=20
>>>=20
>>> On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> =
wrote: =20
>>>=20
>>=20
>> [...]
>>=20
>>> Yes, will correct.
>>>=20
>>> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>>>=20
>>> Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?
>>>=20
>>>=20
>>> Maybe, but I think the logic was that if there is some text there =
(just something), it can be cleanly referenced (i.e. "DELETED =
[RFCXXXX]")if someone is making a revised version of the RFC for some =
purpose.  Purely deleting it accomplishes the task, but this provides a =
good "hook" for a paper trail.
>>>=20
>>=20
>> Okay. On reflection, it's not like we really render the updates the =
old RFC documents.
>>=20
>>=20
>>> Scott
>>> _______________________________________________
>>> Gen-art mailing list
>>> Gen-art@ietf.org
>>> https://www.ietf.org/mailman/listinfo/gen-art
>>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Scott Rose
> NIST
> scott.rose@nist.gov
> +1 301-975-8439
> Google Voice: +1 571-249-3671
> http://www.dnsops.gov/
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20


From suresh.krishnan@ericsson.com  Sun Jun 26 20:17:44 2011
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 F077611E8098 for <gen-art@ietfa.amsl.com>; Sun, 26 Jun 2011 20:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.392
X-Spam-Level: 
X-Spam-Status: No, score=-105.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, 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 7XmZrwSZ0nN8 for <gen-art@ietfa.amsl.com>; Sun, 26 Jun 2011 20:17:44 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 519B611E808E for <gen-art@ietf.org>; Sun, 26 Jun 2011 20:17:41 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p5R3Hbl6020717 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 26 Jun 2011 22:17:40 -0500
Received: from [142.133.10.107] (147.117.20.214) by eusaamw0712.eamcs.ericsson.se (147.117.20.182) with Microsoft SMTP Server id 8.3.137.0; Sun, 26 Jun 2011 23:17:37 -0400
Message-ID: <4E07F4AC.8000005@ericsson.com>
Date: Sun, 26 Jun 2011 23:10:36 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-hammer-hostmeta.all@tools.ietf.org
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-hammer-hostmeta-16.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, 27 Jun 2011 03:17:45 -0000

I have been selected as the General Area Review Team (Gen-ART) reviewer
for this draft (for background on Gen-ART, please see
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-hammer-hostmeta-16.txt
Reviewer: Suresh Krishnan
Review Date: 2011/06/26
IESG Telechat date: 2011/06/30

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

Nits
====

The document has two downrefs that have not been called out in the 
writeup (RFC2818 and RFC4627)

Thanks
Suresh




From suresh.krishnan@ericsson.com  Sun Jun 26 21:28:13 2011
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 D6D4021F85A4 for <gen-art@ietfa.amsl.com>; Sun, 26 Jun 2011 21:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.996
X-Spam-Level: 
X-Spam-Status: No, score=-105.996 tagged_above=-999 required=5 tests=[AWL=0.603, 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 y6bd-3B1njJc for <gen-art@ietfa.amsl.com>; Sun, 26 Jun 2011 21:28:13 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id F1D9421F85A2 for <gen-art@ietf.org>; Sun, 26 Jun 2011 21:28:12 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p5R4SBnp021953 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 26 Jun 2011 23:28:12 -0500
Received: from [142.133.10.107] (147.117.20.214) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.3.137.0; Mon, 27 Jun 2011 00:28:11 -0400
Message-ID: <4E080535.3080403@ericsson.com>
Date: Mon, 27 Jun 2011 00:21:09 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-payload-rfc3016bis.all@tools.ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-payload-rfc3016bis-01.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2011 04:28:13 -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-payload-rfc3016bis-01.txt
Reviewer: Suresh Krishnan
Review Date: 2011/06/26
IESG Telechat date: 2011/06/30

Summary: This draft is ready for publication as Proposed Standard but 
has some editorial issues that need to be fixed.

Editorial
=========

* Section 1.1
The abbreviation VOP is used before definition. Please expand it before 
first use.

* Section 3
s/configurating/configuration/

* Section 6.1
s/AudioMuxElement/audioMuxElement/

Thanks
Suresh




From ron.even.tlv@gmail.com  Mon Jun 27 02:06:29 2011
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 9057D21F864F; Mon, 27 Jun 2011 02:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VKi2Qhk1PIxP; Mon, 27 Jun 2011 02:06:28 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2928721F863F; Mon, 27 Jun 2011 02:06:27 -0700 (PDT)
Received: by wyj26 with SMTP id 26so3451560wyj.31 for <multiple recipients>; Mon, 27 Jun 2011 02:06:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=BTQPDYnwyM0NrMmiL0kWtbdoD2z3A1Zf7U+Lb+xVpkE=; b=jHEem9vd+0gz0ggja1FSwKh8kW/mfENTWysWs8oiFe+E5+JlgZq5CrIs8QhBW97EIF x1Sk+NwSaM3UQ78speHXzsf3o+R9jMItA9r4XQ1CI3xOLqfwxwO/mx3XvWN0DGqzDF0e V0ZsTHWtdn6YX7JmN37hz78XAaLxllutcKFsk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; b=vVLIEkvp2aWnnrIQ1aKewqOaAPcD967+X4AnvViW4LLWsTR2j+Adr6jug+Q/PT8M2r XDuNgxHs78/IbBrVDlTCXrlSb49Z1ndOPQWDBBsGzcA9Pggc3b1YHmS1D87W6FHb3CP+ XpNTDminmdRiKKzvopb9mIg8vB1m+Oj1ScnXM=
Received: by 10.227.165.202 with SMTP id j10mr5345408wby.18.1309165586884; Mon, 27 Jun 2011 02:06:26 -0700 (PDT)
Received: from windows8d787f9 ([109.64.7.173]) by mx.google.com with ESMTPS id gg16sm556906wbb.17.2011.06.27.02.06.23 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Jun 2011 02:06:25 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-roll-of0.all@tools.ietf.org>
Date: Mon, 27 Jun 2011 12:04:20 +0300
Message-ID: <4e084811.90d1e30a.3d19.222f@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000F_01CC34C2.5BAF80F0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acw0qTMmkmCJF09OQ7OyctDJhB8Jjw==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC review of draft-ietf-roll-of0-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: Mon, 27 Jun 2011 09:06:29 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01CC34C2.5BAF80F0
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-roll-of0-14

Reviewer: Roni Even

Review Date:2011-6-27

IETF LC End Date: 2011-7-4

IESG Telechat date: 

 

Summary: This draft is ready for publication as a standard track RFC.
Please note the Nits.

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

1.       The "requirement language" is usually in the terminology section
and not with the abstract.

2.       In section 7.2 first paragraph replace "tthat" with "that"

3.       In section 7.2 third paragraph replace "he current Version Number"
with "the ."

 


------=_NextPart_000_000F_01CC34C2.5BAF80F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1157764602;
	mso-list-type:hybrid;
	mso-list-template-ids:1213479206 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-=
roll-of0-14<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:2011&#8211;6&#8211;27<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: 2011&#8211;7&#8211;4<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 a standard track</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC.&nbsp; =
Please note the Nits.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The =
&#8220;requirement language&quot; is usually in the terminology section =
and not with the abstract.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7.2 first paragraph replace &#8220;tthat&#8221; with =
&#8220;that&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7.2 third paragraph replace &#8220;he </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>current =
Version Number&#8221; with &#8220;the &#8230;&#8221;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_000F_01CC34C2.5BAF80F0--


From kathleen.moriarty@emc.com  Mon Jun 27 06:50:52 2011
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 EB28421F85F9; Mon, 27 Jun 2011 06:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bmrd7l6Uu06T; Mon, 27 Jun 2011 06:50:50 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2F821F86D3; Mon, 27 Jun 2011 06:12:13 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p5RD9MZW006068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jun 2011 09:09:23 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 27 Jun 2011 09:09:08 -0400
Received: from mxhub07.corp.emc.com (mxhub07.corp.emc.com [128.221.46.115]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p5RD8kaG032761; Mon, 27 Jun 2011 09:08:46 -0400
Received: from mx06a.corp.emc.com ([169.254.1.199]) by mxhub07.corp.emc.com ([128.221.46.115]) with mapi; Mon, 27 Jun 2011 09:08:46 -0400
From: <kathleen.moriarty@emc.com>
To: <gen-art@ietf.org>, <draft-li-pwe3-ms-pw-pon.all@tools.ietf.org>, <ietf@ietf.org>
Date: Mon, 27 Jun 2011 09:08:45 -0400
Thread-Topic: GEN-ART review for draft-li-pwe3-ms-pw-pon-03 
Thread-Index: Acw0y1h5B+aMJLm8RXy6PuQpHJ/2KA==
Message-ID: <AE31510960917D478171C79369B660FA0E0325329B@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: lihy@huawei.com, robin@huawei.com, adrian.farrel@huawei.com
Subject: [Gen-art] GEN-ART review for draft-li-pwe3-ms-pw-pon-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, 27 Jun 2011 13:50:52 -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-li-pwe3-ms-pw-pon-03
Reviewer:  Kathleen Moriarty
Review Date: June 27, 2011
IETF LC End Date:
IESG Telechat date: June 28, 2011

Summary:  This document is ready with nits.

Major issues:

Minor issues:

Nits/editorial comments:

The acronym PW is used in the abstract and is not defined until the introdu=
ction.  Please fix.

Paragraph 7 of the introduction, last sentence:
Change from "Besides coding and
   maintenance of these new protocols, a much powerful CPU and more
   memory are also necessary for them to run smoothly."
To: "Besides coding and
   maintenance of these new protocols, a much more powerful CPU and more
   memory are also necessary for them to run smoothly."
If you do not want to repeat the word more, consider the word additional to=
 replace the second instance of more.

Last paragraph of Section 4:
Consider changing from: "OMCI supports the configuration of a number of PW =
types including
   TDM, ATM, and Ethernet, and the protocol can also be used to allow
   the ONU to notify the OLT of the status of the AC."
To: "OMCI supports the configuration of a number of PW types including
   TDM, ATM, and Ethernet.  The protocol can also be used to allow
   the ONU to notify the OLT of the status of the AC."






From ice@cisco.com  Mon Jun 27 12:20:57 2011
Return-Path: <ice@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 14AE811E812A; Mon, 27 Jun 2011 12:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRtu85dtbiEh; Mon, 27 Jun 2011 12:20:56 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 133E711E80F8; Mon, 27 Jun 2011 12:20:55 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p5RJKrH4013381; Mon, 27 Jun 2011 21:20:53 +0200 (CEST)
Received: from [10.155.35.20] ([10.155.35.20]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p5RJKo4Q027276; Mon, 27 Jun 2011 21:20:51 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <4E03F3A5.40905@joelhalpern.com>
Date: Mon, 27 Jun 2011 21:20:50 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC16901C-F0F3-43D2-8D5B-67FFAAB9DC0E@cisco.com>
References: <4E038C9B.3070206@nostrum.com> <4E03F3A5.40905@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1081)
Cc: Adrian Farrel <adrian@olddog.co.uk>, gen-art@ietf.org, IETF discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Review: draft-ietf-mpls-ldp-p2mp-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: Mon, 27 Jun 2011 19:20:57 -0000

Hi Joel,

Thanks for the comments.

> Major issues:
>    As I read the document, status codes (and stauts TLVs) are for =
reporting on the status of LSPs.  They are not for negotiating =
behaviors.  Thus, I find it very strange that make-before-break behavior =
(section 8) is requested (by a downstream device sending a request to an =
upstream device) by including a specific status code in the request. Has =
this technique been used in MPLS LDP before?

Well, the status codes and TLVs are not restricted by RFC 5036 for any =
particular purpose. The MBB procedures requires to signal information =
about the LSP which is not part of the FEC. The status TLV seems a good =
way to do that. Also, the status of the LSP can be viewed as 'waiting on =
upstream LDP neighbor to respond for MBB purpose'. So I think its ok.

>=20
> Minor issues:
>    The definition (section 1.2)  of MP2MP LSPs should indicate that =
even though all nodes are allowed to send on the LSP, there is still a =
distinguished root node.

Ok, I will add that.

>=20
>    The LDP MP Opaque Value Element extended type (section 2.3, second =
definition) seems to be gratuitous complexity, adding extra matching =
cases in the LDP processing path for no stated value.  Is there really =
believed to be a need for more than 254 types of Opaque values?  If so, =
explain it in the document.

The opaque type was defined as a non-extensible one-octet field. This =
may be enough for the future, but you never know. I guess there are many =
examples in the IETF where fields seemed to be large enough but proved =
to be too small over time. So why not just document it now.

>=20
>    Section 3.3.1.3 begins by describing two methods for installing the =
upstream path of a MP2MPLSP.  After carefully describing both, it says =
to only and always use the second method.  Would it not be better to =
describe the constraint (that the upstream path must be in place all the =
way to the root before it claims to be established), and then describe =
the one method that meets taht.  Just don't describe a method that is =
not to be used.

That is a good comment, let me think about this for a bit.

Thx,

Ice.


>=20
> Nits/editorial comments:
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From sgundave@cisco.com  Mon Jun 27 16:28:56 2011
Return-Path: <sgundave@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 CF01D9E8005 for <gen-art@ietfa.amsl.com>; Mon, 27 Jun 2011 16:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.833
X-Spam-Level: 
X-Spam-Status: No, score=-7.833 tagged_above=-999 required=5 tests=[AWL=-0.699, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
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 bSpN--kjt7mv for <gen-art@ietfa.amsl.com>; Mon, 27 Jun 2011 16:28:55 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id B539A21F84DB for <gen-art@ietf.org>; Mon, 27 Jun 2011 16:28:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=25324; q=dns/txt; s=iport; t=1309217335; x=1310426935; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version; bh=zSl+tmiwwon01b5OPa/UTIPsPaZTH8M/oKx/PmOyy+4=; b=WJ2B2OAJq43f6v/xzJcrrWjT4RfnPPXHVxZKj9cVaORYqgr+agTF4p4Z cCWwysAM/SUHLeO0kIBBC90JaGG0YCA2B5FblASLFp0fzQpCu95wTUPzZ Xa+crQg4bcfvzCfPJmWpFGOX3CoAAaclUr62+DpGv+oD4JlUreJqLiPa3 w=;
X-Files: draft-ietf-netlmm-pmipv6-tc-mib-00.txt : 16387
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsYHAO0QCU6rRDoJ/2dsb2JhbABSglGGQZ0xcgJ3qxyeJoYwBIcsileEd4cyhBI
X-IronPort-AV: E=Sophos;i="4.65,434,1304294400";  d="txt'?scan'208,217";a="348470628"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-3.cisco.com with ESMTP; 27 Jun 2011 23:28:55 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5RNStol008150; Mon, 27 Jun 2011 23:28:55 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 27 Jun 2011 16:28:55 -0700
Received: from 128.107.112.115 ([128.107.112.115]) by xmb-sjc-214.amer.cisco.com ([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ; Mon, 27 Jun 2011 23:28:54 +0000
User-Agent: Microsoft-Entourage/12.30.0.110427
Date: Mon, 27 Jun 2011 16:28:51 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>, Dan Romascanu <dromasca@avaya.com>
Message-ID: <CA2E6045.1F0F1%sgundave@cisco.com>
Thread-Topic: TC draft supporting draft-ietf-netlmm-pmipv6-mib-05.txt (resent???)
Thread-Index: AcwvIagaJz8q2/KdQh2WKZcRpg18DgGAFCd2
In-Reply-To: <4DFF0068.5020709@cysols.com>
Mime-version: 1.0
Content-type: multipart/mixed; boundary="B_3392036933_13585424"
X-OriginalArrivalTime: 27 Jun 2011 23:28:55.0238 (UTC) FILETIME=[FB402660:01CC3521]
Cc: draft-ietf-netlmm-pmipv6-mib.all@tools.ietf.org, gen-art@ietf.org, "Glenn M. Keeni" <glenn@cysols.com>
Subject: [Gen-art] TC draft supporting draft-ietf-netlmm-pmipv6-mib-05.txt (resent???)
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, 27 Jun 2011 23:28:56 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3392036933_13585424
Content-type: multipart/alternative;
	boundary="B_3392036933_13599366"


--B_3392036933_13599366
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Hi Jari,

Attached is the TC draft for PMIPv6 ( a new document,   =AD00 version, with
the name draft-ietf-netlmm-pmipv6-tc-mib-00.txt).

Based on the IESG inputs, specifically Dan=B9s comment, our Editor (Glenn)
worked out on the TC draft for PMIPv6. Since, this work is tied to the MIB
which was the product of the NETLMM WG,  we are not sure where to post this
doc. *Please advise*,  if this will be an AD sponsored doc, or if we can
post it as a NETLMM draft. The tools would not allow us to post this
document with the current file name.

---
DISCUSS # 3=20
           This will require a separate PMIP6-TC-document.
----

Regards
Sri

>=20
>=20


--B_3392036933_13599366
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>TC draft supporting draft-ietf-netlmm-pmipv6-mib-05.txt (resent???)<=
/TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>Hi Jari,<BR>
<BR>
Attached is the TC draft for PMIPv6 ( a new document, &nbsp;&nbsp;&#8211;00=
 version, with the name draft-ietf-netlmm-pmipv6-tc-mib-00.txt). <BR>
<BR>
Based on the IESG inputs, specifically Dan&#8217;s comment, our Editor (Gle=
nn) worked out on the TC draft for PMIPv6. Since, this work is tied to the M=
IB which was the product of the NETLMM WG, &nbsp;we are not sure where to po=
st this doc. *Please advise*, &nbsp;if this will be an AD sponsored doc, or =
if we can post it as a NETLMM draft. The tools would not allow us to post th=
is document with the current file name.<BR>
<BR>
---<BR>
</SPAN></FONT><FONT SIZE=3D"2"><FONT FACE=3D"Consolas, Courier New, Courier"><S=
PAN STYLE=3D'font-size:10pt'>DISCUSS # 3 <BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This will=
 require a separate PMIP6-TC-document.<BR>
----<BR>
<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'>Regards<BR>
Sri<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3392036933_13599366--


--B_3392036933_13585424
Content-type: application/octet-stream; name="draft-ietf-netlmm-pmipv6-tc-mib-00.txt"
Content-disposition: attachment;
	filename="draft-ietf-netlmm-pmipv6-tc-mib-00.txt"
Content-transfer-encoding: base64

DQoNCg0KDQoNCg0KTkVUTE1NIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgR2xlbm4gTWFuc2ZpZWxkIEtlZW5pDQpJTlRFUk5FVC1EUkFGVCAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgQ3liZXIgU29sdXRpb25zIEluYy4NCklu
dGVuZGVkIFN0YXR1czogUHJvcG9zZWQgU3RhbmRhcmQgICAgICAgICAgICAgICAgICAgICAg
ICAgUy4gR3VuZGF2ZWxsaQ0KRXhwaXJlczogRGVjZW1iZXIgMjQsIDIwMTEgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIENpc2NvDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEp1bmUgMjUsIDIw
MTENCg0KICAgICAgICAgIFRleHR1YWwgQ29udmVudGlvbnMgZm9yIFByb3h5IE1vYmlsZSBJ
UHY2IE1hbmFnZW1lbnQNCiAgICAgICAgICAgICAgICA8ZHJhZnQtaWV0Zi1uZXRsbW0tcG1p
cHY2LXRjLW1pYi0wMC50eHQ+DQoNClN0YXR1cyBvZiB0aGlzIE1lbW8NCg0KDQogICBUaGlz
IEludGVybmV0LURyYWZ0IGlzIHN1Ym1pdHRlZCB0byBJRVRGIGluIGZ1bGwgY29uZm9ybWFu
Y2Ugd2l0aCB0aGUNCiAgIHByb3Zpc2lvbnMgb2YgQkNQIDc4IGFuZCBCQ1AgNzkuDQoNCiAg
IEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVybmV0
IEVuZ2luZWVyaW5nDQogICBUYXNrIEZvcmNlIChJRVRGKSwgaXRzIGFyZWFzLCBhbmQgaXRz
IHdvcmtpbmcgZ3JvdXBzLiAgTm90ZSB0aGF0DQogICBvdGhlciBncm91cHMgbWF5IGFsc28g
ZGlzdHJpYnV0ZSB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC0NCiAgIERyYWZ0cy4N
Cg0KICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEg
bWF4aW11bSBvZiBzaXggbW9udGhzDQogICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2Vk
LCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQ0KICAgdGltZS4gIEl0
IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2UN
CiAgIG1hdGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHBy
b2dyZXNzLiINCg0KICAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC1EcmFmdHMgY2Fu
IGJlIGFjY2Vzc2VkIGF0DQogICBodHRwOi8vd3d3LmlldGYub3JnL2lldGYvMWlkLWFic3Ry
YWN0cy50eHQuDQoNCiAgIFRoZSBsaXN0IG9mIEludGVybmV0LURyYWZ0IFNoYWRvdyBEaXJl
Y3RvcmllcyBjYW4gYmUgYWNjZXNzZWQgYXQNCiAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hh
ZG93Lmh0bWwuDQoNCiAgIFRoaXMgZG9jdW1lbnQgaXMgYSBwcm9kdWN0IG9mIHRoZSBORVRM
TU0gV29ya2luZyBHcm91cC4gQ29tbWVudHMNCiAgIHNob3VsZCBiZSBhZGRyZXNzZWQgdG8g
dGhlIGF1dGhvcnMgb3IgdGhlIG1haWxpbmcgbGlzdCBhdA0KICAgbmV0bG1tQGlldGYub3Jn
DQoNCiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUgb24gRGVjZW1iZXIgMjQs
IDIwMTEuDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpHbGVubiBNLiBLZWVuaS4gICAgICAg
IEV4cGlyZXM6IERlY2VtYmVyIDI0LCAyMDExICAgICAgICAgICAgICAgW1BhZ2UgMV0NCgwN
Cg0KDQoNCg0KDQpJbnRlcm5ldCBEcmFmdCAgICAgICAgICAgICAgICBwbWlwdjZNSUItVEMg
ICAgICAgICAgICAgICAgICAgICBKdW5lIDIwMTENCg0KDQpDb3B5cmlnaHQgTm90aWNlDQoN
CiAgIENvcHlyaWdodCAoYykgMjAxMSBJRVRGIFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVu
dGlmaWVkIGFzIHRoZQ0KICAgZG9jdW1lbnQgYXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2
ZWQuDQoNCiAgIFRoaXMgZG9jdW1lbnQgaXMgc3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJ
RVRGIFRydXN0J3MgTGVnYWwNCiAgIFByb3Zpc2lvbnMgUmVsYXRpbmcgdG8gSUVURiBEb2N1
bWVudHMNCiAgIChodHRwOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8pIGluIGVm
ZmVjdCBvbiB0aGUgZGF0ZSBvZg0KICAgcHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4g
UGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHMNCiAgIGNhcmVmdWxseSwgYXMgdGhleSBk
ZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQgcmVzdHJpY3Rpb25zIHdpdGgNCiAgIHJlc3BlY3Qg
dG8gdGhpcyBkb2N1bWVudC4gIENvZGUgQ29tcG9uZW50cyBleHRyYWN0ZWQgZnJvbSB0aGlz
DQogICBkb2N1bWVudCBtdXN0IGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZSB0ZXh0
IGFzIGRlc2NyaWJlZA0KICAgaW4gU2VjdGlvbiA0LmUgb2YgdGhlIFRydXN0IExlZ2FsIFBy
b3Zpc2lvbnMgYW5kIGFyZSBwcm92aWRlZA0KICAgd2l0aG91dCB3YXJyYW50eSBhcyBkZXNj
cmliZWQgaW4gdGhlIFNpbXBsaWZpZWQgQlNEIExpY2Vuc2UuDQoNCg0KQWJzdHJhY3QNCg0K
ICAgVGhpcyBtZW1vIGRlZmluZXMgYSBNYW5hZ2VtZW50IEluZm9ybWF0aW9uIEJhc2UgKE1J
QikgbW9kdWxlIHdoaWNoDQogICBjb250YWlucyBUZXh0dWFsIENvbnZlbnRpb25zIHRvIHJl
cHJlc2VudCBjb21tb25seSB1c2VkIFByb3h5DQogICBNb2JpbGUtSVB2NiAoUE1JUHY2KSBt
YW5hZ2VtZW50IGluZm9ybWF0aW9uLiAgVGhlIGludGVudCBpcyB0aGF0DQogICB0aGVzZSBU
RVhUVUFMIENPTlZFTlRJT05TIChUQ3MpIHdpbGwgYmUgaW1wb3J0ZWQgYW5kIHVzZWQgaW4g
UE1JUHY2DQogICByZWxhdGVkIE1JQiBtb2R1bGVzIHRoYXQgd291bGQgb3RoZXJ3aXNlIGRl
ZmluZSB0aGVpciBvd24NCiAgIHJlcHJlc2VudGF0aW9uKHMpLg0KDQoNCg0KDQpUYWJsZSBv
ZiBDb250ZW50cw0KDQogICAgICAgIDEuIEludHJvZHVjdGlvbiAuLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uICAzDQogICAgICAgIDIuIFRlcm1pbm9sb2d5IC4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uICAzDQogICAgICAgIDMuIFRoZSBJbnRlcm5l
dC1TdGFuZGFyZCBNYW5hZ2VtZW50IEZyYW1ld29yayAuLi4uICAzDQogICAgICAgIDQuIFRo
ZSBQcm94eSBNb2JpbGUgSVB2NiBUZXh0dWFsIENvbnZlbnRpb25zIE1JQiAuICA0DQogICAg
ICAgIDUuIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zIC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
ICA4DQogICAgICAgIDYuIElBTkEgQ29uc2lkZXJhdGlvbnMgLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uICA4DQogICAgICAgIDcuIFJlZmVyZW5jZXMgLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uICA4DQogICAgICAgIDggIEFja25vd2xlZGdtZW50cyAuLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDEwDQogICAgICAgIDkuIEF1dGhvcnMnIEFk
ZHJlc3NlcyAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDEwDQogICAgICAgICAgIEFw
cGVuZGl4IC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDExDQoNCg0K
DQoNCg0KDQoNCg0KR2xlbm4gTS4gS2VlbmkuICAgICAgICBFeHBpcmVzOiBEZWNlbWJlciAy
NCwgMjAxMSAgICAgICAgICAgICAgIFtQYWdlIDJdDQoMDQoNCg0KDQoNCg0KSW50ZXJuZXQg
RHJhZnQgICAgICAgICAgICAgICAgcG1pcHY2TUlCLVRDICAgICAgICAgICAgICAgICAgICAg
SnVuZSAyMDExDQoNCg0KMS4gSW50cm9kdWN0aW9uDQoNCiAgIFRoaXMgbWVtbyBkZWZpbmVz
IGEgTWFuYWdlbWVudCBJbmZvcm1hdGlvbiBCYXNlIChNSUIpIG1vZHVsZSB3aGljaA0KICAg
Y29udGFpbnMgVGV4dHVhbCBDb252ZW50aW9ucyB0byByZXByZXNlbnQgY29tbW9ubHkgdXNl
ZCBQcm94eQ0KICAgTW9iaWxlLUlQdjYgKFBNSVB2NikgbWFuYWdlbWVudCBpbmZvcm1hdGlv
bi4NCg0KMi4gVGVybWlub2xvZ3kNCg0KICAgVGhlIGtleSB3b3JkcyAiTVVTVCIsICJNVVNU
IE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLA0KICAgIlNIT1VMRCIs
ICJTSE9VTEQgTk9UIiwgIlJFQ09NTUVOREVEIiwgIk1BWSIsIGFuZCAiT1BUSU9OQUwiIGlu
IHRoaXMNCiAgIGRvY3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQg
aW4gUkZDIDIxMTkgW1JGQzIxMTldLg0KDQozLiBUaGUgSW50ZXJuZXQtU3RhbmRhcmQgTWFu
YWdlbWVudCBGcmFtZXdvcmsNCg0KICAgRm9yIGEgZGV0YWlsZWQgb3ZlcnZpZXcgb2YgdGhl
IGRvY3VtZW50cyB0aGF0IGRlc2NyaWJlIHRoZSBjdXJyZW50DQogICBJbnRlcm5ldC1TdGFu
ZGFyZCBNYW5hZ2VtZW50IEZyYW1ld29yaywgcGxlYXNlIHJlZmVyIHRvIHNlY3Rpb24gNyBv
Zg0KICAgUkZDIDM0MTAgW1JGQzM0MTBdLg0KDQogICBNYW5hZ2VkIG9iamVjdHMgYXJlIGFj
Y2Vzc2VkIHZpYSBhIHZpcnR1YWwgaW5mb3JtYXRpb24gc3RvcmUsIHRlcm1lZA0KICAgdGhl
IE1hbmFnZW1lbnQgSW5mb3JtYXRpb24gQmFzZSBvciBNSUIuICBNSUIgb2JqZWN0cyBhcmUg
Z2VuZXJhbGx5DQogICBhY2Nlc3NlZCB0aHJvdWdoIHRoZSBTaW1wbGUgTmV0d29yayBNYW5h
Z2VtZW50IFByb3RvY29sIChTTk1QKS4NCg0KICAgT2JqZWN0cyBpbiB0aGUgTUlCIGFyZSBk
ZWZpbmVkIHVzaW5nIHRoZSBtZWNoYW5pc21zIGRlZmluZWQgaW4gdGhlDQogICBTdHJ1Y3R1
cmUgb2YgTWFuYWdlbWVudCBJbmZvcm1hdGlvbiAoU01JKS4gIFRoaXMgbWVtbyBzcGVjaWZp
ZXMgYSBNSUINCiAgIG1vZHVsZSB0aGF0IGlzIGNvbXBsaWFudCB0byB0aGUgU01JdjIsIHdo
aWNoIGlzIGRlc2NyaWJlZCBpbiBTVEQgNTgsDQogICBSRkMgMjU3OCBbUkZDMjU3OF0sIFNU
RCA1OCwgUkZDIDI1NzkgW1JGQzI1NzldIGFuZCBTVEQgNTgsIFJGQyAyNTgwDQogICBbUkZD
MjU4MF0uDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpHbGVu
biBNLiBLZWVuaS4gICAgICAgIEV4cGlyZXM6IERlY2VtYmVyIDI0LCAyMDExICAgICAgICAg
ICAgICAgW1BhZ2UgM10NCgwNCg0KDQoNCg0KDQpJbnRlcm5ldCBEcmFmdCAgICAgICAgICAg
ICAgICBwbWlwdjZNSUItVEMgICAgICAgICAgICAgICAgICAgICBKdW5lIDIwMTENCg0KDQo0
LiAgVGhlIFByb3h5IE1vYmlsZSBJUHY2IFRleHR1YWwgQ29udmVudGlvbnMgTUlCDQoNCg0K
ICAgUE1JUHY2LVRDLU1JQiBERUZJTklUSU9OUyA6Oj0gQkVHSU4NCg0KICAgSU1QT1JUUw0K
ICAgICAgIE1PRFVMRS1JREVOVElUWSwgbWliLTINCiAgICAgICAgICAgICAgICAgRlJPTSBT
Tk1QdjItU01JICAgICAgICAtLSBbUkZDMjU3OF0NCiAgICAgICBURVhUVUFMLUNPTlZFTlRJ
T04NCiAgICAgICAgICAgICAgICAgRlJPTSBTTk1QdjItVEM7ICAgICAgICAtLSBbUkZDMjU3
OV0NCg0KICAgcG1pcDZUQ01JQiAgTU9EVUxFLUlERU5USVRZDQogICAgICAgTEFTVC1VUERB
VEVEICIyMDExMDYyNTAwMDBaIiAgICAgLS0gIDI1dGggSnVuZSwgMjAxMQ0KICAgICAgIE9S
R0FOSVpBVElPTiAiSUVURiBORVRMTU0gV29ya2luZyBHcm91cCINCiAgICAgICBDT05UQUNU
LUlORk8NCiAgICAgICAiICAgICAgICAgICAgICAgICAgICAgIEdsZW5uIE1hbnNmaWVsZCBL
ZWVuaQ0KICAgICAgICAgICAgICAgICAgICAgIFBvc3RhbDogQ3liZXIgU29sdXRpb25zIElu
Yy4NCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDYtNi0zLCBNaW5hbWkgWW9zaGlu
YXJpDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICBBb2JhLWt1LCBTZW5kYWksIEph
cGFuIDk4OS0zMjA0Lg0KICAgICAgICAgICAgICAgICAgICAgICAgIFRlbDogKzgxLTIyLTMw
My00MDEyDQogICAgICAgICAgICAgICAgICAgICAgICAgRmF4OiArODEtMjItMzAzLTQwMTUN
CiAgICAgICAgICAgICAgICAgICAgICBFLW1haWw6IGdsZW5uQGN5c29scy5jb20NCg0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgU3JpIEd1bmRhdmVsbGkNCiAgICAgICAgICAg
ICAgICAgICAgICBQb3N0YWw6IENpc2NvIFN5c3RlbXMNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIDE3MCBXLlRhc21hbiBEcml2ZSwNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIFNhbiBKb3NlLCBDQSA5NTEzNA0KICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgVVNBDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICBUZWw6ICsxLTQwOC01MjctNjEw
OQ0KICAgICAgICAgICAgICAgICAgICAgIEUtbWFpbDogc2d1bmRhdmVAY2lzY28uY29tDQoN
Cg0KICAgICAgICBTdXBwb3J0IEdyb3VwIEUtbWFpbDogbmV0bG1tQGlldGYub3JnDQogICAg
ICAgICINCg0KICAgICAgIERFU0NSSVBUSU9ODQogICAgICAgICAgICJUaGlzIE1JQiBtb2R1
bGUgcHJvdmlkZXMgdGV4dHVhbCBjb252ZW50aW9ucyBmb3INCiAgICAgICAgICAgIFByb3h5
IE1vYmlsZSBJUHY2IE1hbmFnZW1lbnQgaW5mb3JtYXRpb24uDQoNCiAgICAgICAgICAgIENv
cHlyaWdodCAoQykgVGhlIElFVEYgVHJ1c3QgKDIwMTEpLiBUaGlzIHZlcnNpb24gb2YNCiAg
ICAgICAgICAgIHRoaXMgTUlCIG1vZHVsZSBpcyBwYXJ0IG9mIFJGQyBYWFhYOyBzZWUgdGhl
IFJGQyBpdHNlbGYgZm9yDQogICAgICAgICAgICBmdWxsIGxlZ2FsIG5vdGljZXMuDQogICAg
ICAgICAgICINCiAgICAgIC0tIFJGQyBFZC46IHJlcGxhY2UgWFhYWCB3aXRoIHRoZSBhY3R1
YWwgUkZDIG51bWJlciAmIHJlbW92ZSB0aGlzDQoNCg0KDQpHbGVubiBNLiBLZWVuaS4gICAg
ICAgIEV4cGlyZXM6IERlY2VtYmVyIDI0LCAyMDExICAgICAgICAgICAgICAgW1BhZ2UgNF0N
CgwNCg0KDQoNCg0KDQpJbnRlcm5ldCBEcmFmdCAgICAgICAgICAgICAgICBwbWlwdjZNSUIt
VEMgICAgICAgICAgICAgICAgICAgICBKdW5lIDIwMTENCg0KDQogICAgICAtLSBub3RlDQoN
Cg0KICAgICAgIFJFVklTSU9OICIyMDExMDYyNTAwMDBaIiAgICAgLS0gIDI1dGggSnVuZSwg
MjAxMQ0KICAgICAgIERFU0NSSVBUSU9ODQogICAgICAgICAgICJUaGUgaW5pdGlhbCB2ZXJz
aW9uLCBwdWJsaXNoZWQgYXMgUkZDIFhYWFguIg0KDQogICAgICAtLSBSRkMgRWQuOiByZXBs
YWNlIFhYWFggd2l0aCB0aGUgYWN0dWFsIFJGQyBudW1iZXIgJiByZW1vdmUgdGhpcw0KICAg
ICAgLS0gbm90ZQ0KDQoNCiAgICAgICA6Oj0geyBtaWItMiBZWVlZIH0gICAgIC0tIFdpbGwg
YmUgYXNzaWduZWQgYnkgSUFOQQ0KDQogICAgICAtLSBJQU5BIFJlZy46IFBsZWFzZSBhc3Np
Z24gYSB2YWx1ZSBmb3IgIllZWVkiIHVuZGVyIHRoZQ0KICAgICAgLS0gJ21pYi0yJyBzdWJ0
cmVlIGFuZCByZWNvcmQgdGhlIGFzc2lnbm1lbnQgaW4gdGhlIFNNSQ0KICAgICAgLS0gTnVt
YmVycyByZWdpc3RyeS4NCg0KICAgICAgLS0gUkZDIEVkLjogV2hlbiB0aGUgYWJvdmUgYXNz
aWdubWVudCBoYXMgYmVlbiBtYWRlLCBwbGVhc2UNCiAgICAgIC0tICAgICByZW1vdmUgdGhl
IGFib3ZlIG5vdGUNCiAgICAgIC0tICAgICByZXBsYWNlICJZWVlZIiBoZXJlIHdpdGggdGhl
IGFzc2lnbmVkIHZhbHVlIGFuZA0KICAgICAgLS0gICAgIHJlbW92ZSB0aGlzIG5vdGUuDQoN
Cg0KDQogICAtLSAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tDQogICAtLSBUZXh0dWFsIENvbnZlbnRpb25zDQogICAtLSAt
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQoNCiAgICAgIFBtaXA2VGltZVN0YW1wNjQgIDo6PSAgVEVYVFVBTC1DT05WRU5U
SU9ODQogICAgICAgICAgU1RBVFVTICBjdXJyZW50DQogICAgICAgICAgREVTQ1JJUFRJT04N
CiAgICAgICAgICAgICAgIkEgNjQtYml0IHVuc2lnbmVkIGludGVnZXIgZmllbGQgY29udGFp
bmluZyBhIHRpbWVzdGFtcC4NCiAgICAgICAgICAgICAgIFRoZSB2YWx1ZSBpbmRpY2F0ZXMg
dGhlIGVsYXBzZWQgdGltZSBzaW5jZSBKYW51YXJ5IDEsDQogICAgICAgICAgICAgICAxOTcw
LCAwMDowMCBVVEMsIGJ5IHVzaW5nIGEgZml4ZWQgcG9pbnQgZm9ybWF0LiAgSW4gdGhpcw0K
ICAgICAgICAgICAgICAgZm9ybWF0LCB0aGUgaW50ZWdlciBudW1iZXIgb2Ygc2Vjb25kcyBp
cyBjb250YWluZWQgaW4gdGhlDQogICAgICAgICAgICAgICBmaXJzdCA0OCBiaXRzIG9mIHRo
ZSBmaWVsZCwgYW5kIHRoZSByZW1haW5pbmcgMTYgYml0cw0KICAgICAgICAgICAgICAgaW5k
aWNhdGUgdGhlIG51bWJlciBvZiAxLzY1NTM2IGZyYWN0aW9ucyBvZiBhIHNlY29uZC4NCiAg
ICAgICAgICAgICAgIg0KICAgICAgICAgIFJFRkVSRU5DRQ0KICAgICAgICAgICAgICAiUkZD
IDUyMTM6IFNlY3Rpb24gOC44Ig0KICAgICAgICAgIFNZTlRBWCAgQ291bnRlcjY0DQoNCg0K
DQoNCg0KDQoNCkdsZW5uIE0uIEtlZW5pLiAgICAgICAgRXhwaXJlczogRGVjZW1iZXIgMjQs
IDIwMTEgICAgICAgICAgICAgICBbUGFnZSA1XQ0KDA0KDQoNCg0KDQoNCkludGVybmV0IERy
YWZ0ICAgICAgICAgICAgICAgIHBtaXB2Nk1JQi1UQyAgICAgICAgICAgICAgICAgICAgIEp1
bmUgMjAxMQ0KDQoNCiAgICAgIFBtaXA2TU5JZGVudGlmaWVyICA6Oj0gIFRFWFRVQUwtQ09O
VkVOVElPTg0KICAgICAgICAgIERJU1BMQVktSElOVCAiMjU1YSINCiAgICAgICAgICBTVEFU
VVMgIGN1cnJlbnQNCiAgICAgICAgICBERVNDUklQVElPTg0KICAgICAgICAgICAgICAiVGhl
IGlkZW50aXR5IG9mIGEgbW9iaWxlIG5vZGUgaW4gdGhlIFByb3h5IE1vYmlsZSBJUHY2DQog
ICAgICAgICAgICAgICBkb21haW4uIFRoaXMgaXMgdGhlIHN0YWJsZSBpZGVudGlmaWVyIG9m
IGEgbW9iaWxlIG5vZGUNCiAgICAgICAgICAgICAgIHRoYXQgdGhlIG1vYmlsaXR5IGVudGl0
aWVzIGluIGEgUHJveHkgTW9iaWxlIElQdjYgZG9tYWluDQogICAgICAgICAgICAgICBjYW4g
YWx3YXlzIGFjcXVpcmUgYW5kIHVzZSBmb3IgcHJlZGljdGFibHkgaWRlbnRpZnlpbmcNCiAg
ICAgICAgICAgICAgIGEgbW9iaWxlIG5vZGUuIFZhcmlvdXMgZm9ybXMgb2YgaWRlbnRpZmll
cnMgY2FuIGJlIHVzZWQNCiAgICAgICAgICAgICAgIHRvIGlkZW50aWZ5IGEgbW9iaWxlIG5v
ZGUgKE1OKS4gIFR3byBleGFtcGxlcyBhcmUgYQ0KICAgICAgICAgICAgICAgTmV0d29yayBB
Y2Nlc3MgSWRlbnRpZmllciAoTkFJKSBbUkZDNDI4Ml0gYW5kIGFuIG9wYXF1ZQ0KICAgICAg
ICAgICAgICAgaWRlbnRpZmllciBhcHBsaWNhYmxlIHRvIGEgcGFydGljdWxhciBhcHBsaWNh
dGlvbi4NCiAgICAgICAgICAgICAgIg0KICAgICAgICAgIFJFRkVSRU5DRQ0KICAgICAgICAg
ICAgICAiUkZDIDQyODM6IFNlY3Rpb24gMyINCiAgICAgICAgICBTWU5UQVggIE9DVEVUIFNU
UklORyAoU0laRSAoMC4uMjU1KSkNCg0KICAgICAgUG1pcDZNTkxsSWRlbnRpZmllciA6Oj0g
IFRFWFRVQUwtQ09OVkVOVElPTg0KICAgICAgICAgIERJU1BMQVktSElOVCAiMjU1YSINCiAg
ICAgICAgICBTVEFUVVMgIGN1cnJlbnQNCiAgICAgICAgICBERVNDUklQVElPTg0KICAgICAg
ICAgICAgICAiQW4gaWRlbnRpZmllciB0aGF0IGlkZW50aWZpZXMgdGhlIGF0dGFjaGVkIGlu
dGVyZmFjZSBvZiBhDQogICAgICAgICAgICAgICBtb2JpbGUgbm9kZS4gIEZvciB0aG9zZSBp
bnRlcmZhY2VzIHRoYXQgaGF2ZSBhIGxpbmstbGF5ZXINCiAgICAgICAgICAgICAgIGlkZW50
aWZpZXIsIHRoaXMgaWRlbnRpZmllciBjYW4gYmUgYmFzZWQgb24gdGhhdC4gIFRoZQ0KICAg
ICAgICAgICAgICAgbGluay1sYXllciBpZGVudGlmaWVyLCBpbiBzb21lIGNhc2VzLCBpcyBn
ZW5lcmF0ZWQgYnkgdGhlDQogICAgICAgICAgICAgICBtb2JpbGUgbm9kZSBhbmQgY29udmV5
ZWQgdG8gdGhlIG1vYmlsZSBhY2Nlc3MgZ2F0ZXdheS4NCiAgICAgICAgICAgICAgIFRoaXMg
aWRlbnRpZmllciBvZiB0aGUgYXR0YWNoZWQgaW50ZXJmYWNlIG11c3QgYmUgc3RhYmxlDQog
ICAgICAgICAgICAgICBhcyBzZWVuIGJ5IGFueSBvZiB0aGUgbW9iaWxlIGFjY2VzcyBnYXRl
d2F5cyBpbiBhIGdpdmVuDQogICAgICAgICAgICAgICBQcm94eSBNb2JpbGUgSVB2NiBkb21h
aW4uIEluIHNvbWUgb3RoZXIgY2FzZXMsIHRoZXJlDQogICAgICAgICAgICAgICBtaWdodCBu
b3QgYmUgYW55IGxpbmstbGF5ZXIgaWRlbnRpZmllciBhc3NvY2lhdGVkIHdpdGgNCiAgICAg
ICAgICAgICAgIHRoZSBtb2JpbGUgbm9kZSdzIGludGVyZmFjZS4gQW4gaWRlbnRpZmllciB2
YWx1ZSBvZiBhbGwNCiAgICAgICAgICAgICAgIHplcm9lcyBpcyBub3QgY29uc2lkZXJlZCBh
IHZhbGlkIGlkZW50aWZpZXIgYW5kIGNhbm5vdA0KICAgICAgICAgICAgICAgYmUgdXNlZCBh
cyBhbiBpbnRlcmZhY2UgaWRlbnRpZmllci4NCiAgICAgICAgICAgICAgIg0KICAgICAgICAg
IFJFRkVSRU5DRQ0KICAgICAgICAgICAgICAiUkZDIDUyMTM6IFNlY3Rpb24gOC42Ig0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KR2xlbm4gTS4gS2VlbmkuICAgICAgICBFeHBpcmVzOiBE
ZWNlbWJlciAyNCwgMjAxMSAgICAgICAgICAgICAgIFtQYWdlIDZdDQoMDQoNCg0KDQoNCg0K
SW50ZXJuZXQgRHJhZnQgICAgICAgICAgICAgICAgcG1pcHY2TUlCLVRDICAgICAgICAgICAg
ICAgICAgICAgSnVuZSAyMDExDQoNCg0KICAgICAgUG1pcDZNTkluZGV4IDo6PSBURVhUVUFM
LUNPTlZFTlRJT04NCiAgICAgICAgICBESVNQTEFZLUhJTlQgImQiDQogICAgICAgICAgU1RB
VFVTICAgICAgIGN1cnJlbnQNCiAgICAgICAgICBERVNDUklQVElPTg0KICAgICAgICAgICAg
ICAiQSB1bmlxdWUgaW50ZWdlciB2YWx1ZSwgZ3JlYXRlciB0aGFuIHplcm8sIGFzc2lnbmVk
IHRvDQogICAgICAgICAgICAgICBlYWNoIG1vYmlsZSBub2RlIHRoYXQgaXMgY3VycmVudGx5
IGF0dGFjaGVkIHRvIHRoZQ0KICAgICAgICAgICAgICAgUE1JUHY2LURvbWFpbiBieSB0aGUg
bWFuYWdlbWVudCBzeXN0ZW0uDQogICAgICAgICAgICAgICBJdCBpcyByZWNvbW1lbmRlZCB0
aGF0IHRoZSB2YWx1ZXMgYXJlIGFzc2lnbmVkDQogICAgICAgICAgICAgICBjb250aWd1b3Vz
bHkgc3RhcnRpbmcgZnJvbSAxLiAgVGhlIHZhbHVlIGZvciBlYWNoIG1vYmlsZQ0KICAgICAg
ICAgICAgICAgbm9kZSBtdXN0IHJlbWFpbiBjb25zdGFudCBhdCBsZWFzdCBmcm9tIG9uZSBy
ZS0NCiAgICAgICAgICAgICAgIGluaXRpYWxpemF0aW9uIG9mIHRoZSBlbnRpdHkncyBuZXR3
b3JrIG1hbmFnZW1lbnQgc3lzdGVtDQogICAgICAgICAgICAgICB0byB0aGUgbmV4dCByZS1p
bml0aWFsaXphdGlvbi4NCiAgICAgICAgICAgICAgIg0KICAgICAgICAgIFNZTlRBWCAgICAg
ICBJbnRlZ2VyMzIgKDEuLjIxNDc0ODM2NDcpDQoNCg0KICAgICAgUG1pcDZQQlVBY2Nlc3NU
ZWNobm9sb2d5VHlwZSA6Oj0gIFRFWFRVQUwtQ09OVkVOVElPTg0KICAgICAgICAgIFNUQVRV
UyAgY3VycmVudA0KICAgICAgICAgIERFU0NSSVBUSU9ODQogICAgICAgICAgICAgICJUaGlz
IHNwZWNpZmllcyB0aGUgYWNjZXNzIHRlY2hub2xvZ3kgd2hpY2ggY29ubmVjdHMgdGhlDQog
ICAgICAgICAgICAgICBtb2JpbGUgbm9kZSB0byB0aGUgYWNjZXNzIGxpbmsgb24gdGhlIG1v
YmlsZSBhY2Nlc3MNCiAgICAgICAgICAgICAgIGdhdGV3YXkuDQogICAgICAgICAgICAgICIN
CiAgICAgICAgICBSRUZFUkVOQ0UNCiAgICAgICAgICAgICAgIlJGQyA1MjEzOiBTZWN0aW9u
IDguNSwNCiAgICAgICAgICAgICAgIGh0dHA6Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVudHMv
bW9iaWxpdHktcGFyYW1ldGVycy8NCiAgICAgICAgICAgICAgIG1vYmlsaXR5LXBhcmFtZXRl
cnMudHh0Ig0KICAgICAgICAgIFNZTlRBWCBJTlRFR0VSDQogICAgICAgICAg
ew0KICAgICAg
ICAgICAgICAgICAgICByZXNlcnZlZCAgICAgICAgICAgICAgICgwKSwNCiAgICAgICAgICAg
ICAgICAgICAgbG9naWNhbE5ldHdvcmtJbnRlcmZhY2UoMSksDQogICAgICAgICAgICAgICAg
ICAgIHBvaW50VG9Qb2ludEludGVyZmFjZSAgKDIpLA0KICAgICAgICAgICAgICAgICAgICBl
dGhlcm5ldCAgICAgICAgICAgICAgICgzKSwNCiAgICAgICAgICAgICAgICAgICAgd2lyZWxl
c3NMYW4gICAgICAgICAgICAoNCksDQogICAgICAgICAgICAgICAgICAgIHdpbWF4ICAgICAg
ICAgICAgICAgICAgKDUpLA0KICAgICAgICAgICAgICAgICAgICB0aHJlZUdQUEdFUkFOICAg
ICAgICAgICg2KSwNCiAgICAgICAgICAgICAgICAgICAgdGhyZWVHUFBVVFJBTiAgICAgICAg
ICAoNyksDQogICAgICAgICAgICAgICAgICAgIHRocmVlR1BQRVRSQU4gICAgICAgICAgKDgp
LA0KICAgICAgICAgICAgICAgICAgICB0aHJlZUdQUDJlSFJQRCAgICAgICAgICg5KSwNCiAg
ICAgICAgICAgICAgICAgICAgdGhyZWVHUFAySFJQRCAgICAgICAgICAoMTApLA0KICAgICAg
ICAgICAgICAgICAgICB0aHJlZUdQUDIxeFJUVCAgICAgICAgICgxMSksDQogICAgICAgICAg
ICAgICAgICAgIHRocmVlR1BQMlVNQiAgICAgICAgICAgKDEyKQ0KICAgICAgICAgIH0NCiAg
IEVORA0KDQoNCg0KDQpHbGVubiBNLiBLZWVuaS4gICAgICAgIEV4cGlyZXM6IERlY2VtYmVy
IDI0LCAyMDExICAgICAgICAgICAgICAgW1BhZ2UgN10NCgwNCg0KDQoNCg0KDQpJbnRlcm5l
dCBEcmFmdCAgICAgICAgICAgICAgICBwbWlwdjZNSUItVEMgICAgICAgICAgICAgICAgICAg
ICBKdW5lIDIwMTENCg0KDQo1LiBTZWN1cml0eSBDb25zaWRlcmF0aW9ucw0KDQoNCiAgIFRo
aXMgbW9kdWxlIGRvZXMgbm90IGRlZmluZSBhbnkgbWFuYWdlbWVudCBvYmplY3RzLiAgSW5z
dGVhZCwgaXQNCiAgIGRlZmluZXMgYSBzZXQgb2YgdGV4dHVhbCBjb252ZW50aW9ucyB3aGlj
aCBtYXkgYmUgdXNlZCBieSBvdGhlciBNSUINCiAgIG1vZHVsZXMgdG8gZGVmaW5lIG1hbmFn
ZW1lbnQgb2JqZWN0cy4gIE1lYW5pbmdmdWwgc2VjdXJpdHkNCiAgIGNvbnNpZGVyYXRpb25z
IGNhbiBvbmx5IGJlIHdyaXR0ZW4gaW4gdGhlIE1JQiBtb2R1bGVzIHRoYXQgZGVmaW5lDQog
ICBtYW5hZ2VtZW50IG9iamVjdHMuICBUaGlzIGRvY3VtZW50IGhhcyB0aGVyZWZvcmUgbm8g
aW1wYWN0IG9uIHRoZQ0KICAgc2VjdXJpdHkgb2YgdGhlIEludGVybmV0Lg0KDQoNCjYuICBJ
QU5BIENvbnNpZGVyYXRpb25zDQoNCiAgIFRoZSBNSUIgbW9kdWxlcyBpbiB0aGlzIGRvY3Vt
ZW50IHVzZSB0aGUgZm9sbG93aW5nIElBTkEtYXNzaWduZWQNCiAgIE9CSkVDVCBJREVOVElG
SUVSIHZhbHVlcyByZWNvcmRlZCBpbiB0aGUgU01JIE51bWJlcnMgcmVnaXN0cnk6DQoNCiAg
IERlc2NyaXB0b3IgICAgICAgIE9CSkVDVCBJREVOVElGSUVSIHZhbHVlDQogICAtLS0tLS0t
LS0tICAgICAgICAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQogICBwbWlwNlRDTUlCICAg
ICAgICB7IG1pYi0yIFlZWVkgfQ0KDQogICBJQU5BIFJlZy46IFBsZWFzZSBhc3NpZ24gYSB2
YWx1ZSB1bmRlciB0aGUgJ21pYi0yJyBzdWJ0cmVlDQogICAgICAgICAgICAgIGZvciB0aGUg
J3BtaXA2VENNSUInIE1PRFVMRS1JREVOVElUWSAgYW5kIHJlY29yZA0KICAgICAgICAgICAg
ICB0aGUgYXNzaWdubWVudCBpbiB0aGUgU01JIE51bWJlcnMgcmVnaXN0cnkuDQoNCiAgIFJG
QyBFZC46IFdoZW4gdGhlIGFib3ZlIGFzc2lnbm1lbnRzIGhhdmUgYmVlbiBtYWRlLCBwbGVh
c2UNCiAgICAgICAgICAgICAgLSByZW1vdmUgdGhlIGFib3ZlIG5vdGUNCiAgICAgICAgICAg
ICAgLSByZXBsYWNlICJZWVlZIiBoZXJlIHdpdGggdGhlIGFzc2lnbmVkIHZhbHVlcyBhbmQN
CiAgICAgICAgICAgICAgLSByZW1vdmUgdGhpcyBub3RlLg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQpHbGVubiBNLiBLZWVuaS4gICAgICAgIEV4cGlyZXM6IERl
Y2VtYmVyIDI0LCAyMDExICAgICAgICAgICAgICAgW1BhZ2UgOF0NCgwNCg0KDQoNCg0KDQpJ
bnRlcm5ldCBEcmFmdCAgICAgICAgICAgICAgICBwbWlwdjZNSUItVEMgICAgICAgICAgICAg
ICAgICAgICBKdW5lIDIwMTENCg0KDQo3LiAgUmVmZXJlbmNlcw0KDQo3LjEgTm9ybWF0aXZl
IFJlZmVyZW5jZXMNCg0KW1JGQzIxMTldICAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9y
IHVzZSBpbiBSRkNzIHRvIEluZGljYXRlDQogICAgICAgICAgICBSZXF1aXJlbWVudCBMZXZl
bHMiLCBCQ1AgMTQsIFJGQyAyMTE5LCBNYXJjaCAxOTk3DQoNCltSRkMyNTc4XSAgIE1jQ2xv
Z2hyaWUsIEsuLCBQZXJraW5zLCBELiwgU2Nob2Vud2FlbGRlciwgSi4sIENhc2UsIEouLA0K
ICAgICAgICAgICAgUm9zZSwgTS4sIGFuZCBTLiBXYWxkYnVzc2VyLCAiU3RydWN0dXJlIG9m
IE1hbmFnZW1lbnQNCiAgICAgICAgICAgIEluZm9ybWF0aW9uIFZlcnNpb24gMiAoU01JdjIp
IiwgU1REIDU4LCBSRkMgMjU3OCwNCiAgICAgICAgICAgIEFwcmlsIDE5OTkNCg0KW1JGQzI1
NzldICAgTWNDbG9naHJpZSwgSy4sIFBlcmtpbnMsIEQuLCBTY2hvZW53YWVsZGVyLCBKLiwg
Q2FzZSwgSi4sDQogICAgICAgICAgICBSb3NlLCBNLiwgYW5kIFMuIFdhbGRidXNzZXIsICJU
ZXh0dWFsIENvbnZlbnRpb25zIGZvcg0KICAgICAgICAgICAgU01JdjIiLCBTVEQgNTgsIFJG
QyAyNTc5LCBBcHJpbCAxOTk5DQoNCltSRkMyNTgwXSAgIE1jQ2xvZ2hyaWUsIEsuLCBQZXJr
aW5zLCBELiwgU2Nob2Vud2FlbGRlciwgSi4sIENhc2UsIEouLA0KICAgICAgICAgICAgUm9z
ZSwgTS4sIGFuZCBTLiBXYWxkYnVzc2VyLCAiQ29uZm9ybWFuY2UgU3RhdGVtZW50cyBmb3IN
CiAgICAgICAgICAgIFNNSXYyIiwgU1REIDU4LCBSRkMgMjU4MCwgQXByaWwgMTk5OQ0KDQpb
UkZDNTIxM10gICBHdW5kYXZlbGxpLCBTLiwgTGV1bmcsIEsuLCBEZXZhcmFwYWxsaSwgVi4s
IENob3dkaHVyeSwNCiAgICAgICAgICAgIEsuLCBhbmQgUGF0aWwsIEIuLCBQcm94eSBNb2Jp
bGUgSVB2NiksIFJGQyA1MjEzLA0KICAgICAgICAgICAgQXVndXN0IDIwMDguDQoNCg0KNy4y
ICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzDQoNCltSRkMzNDEwXSAgQ2FzZSwgSi4sIE11bmR5
LCBSLiwgUGFydGFpbiwgRC4sIGFuZCBCLiBTdGV3YXJ0LA0KICAgICAgICAgICAiSW50cm9k
dWN0aW9uIGFuZCBBcHBsaWNhYmlsaXR5IFN0YXRlbWVudHMgZm9yIHRoZQ0KICAgICAgICAg
ICBJbnRlcm5ldC1TdGFuZGFyZCBNYW5hZ2VtZW50IEZyYW1ld29yayIsIFJGQyAzNDEwLA0K
ICAgICAgICAgICBEZWNlbWJlciAyMDAyLg0KW1BNSVA2TUlCXSBLZWVuaSwgRy4sIEtvaWRl
LCBLLiwgR3VuZGF2ZWxsaSwgUy4sIGFuZCBXYWtpa2F3YSwgUi4sDQogICAgICAgICAgICJQ
cm94eSBNb2JpbGUgSVB2NiBNYW5hZ2VtZW50IEluZm9ybWF0aW9uIEJhc2UiLCBXb3JrIGlu
DQogICAgICAgICAgIFByb2dyZXNzLg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkds
ZW5uIE0uIEtlZW5pLiAgICAgICAgRXhwaXJlczogRGVjZW1iZXIgMjQsIDIwMTEgICAgICAg
ICAgICAgICBbUGFnZSA5XQ0KDA0KDQoNCg0KDQoNCkludGVybmV0IERyYWZ0ICAgICAgICAg
ICAgICAgIHBtaXB2Nk1JQi1UQyAgICAgICAgICAgICAgICAgICAgIEp1bmUgMjAxMQ0KDQoN
CjguICBBY2tub3dsZWRnbWVudHMNCiAgICBYWFhYWFgNCg0KOS4gIEF1dGhvcnMnIEFkZHJl
c3Nlcw0KDQogICBHbGVubiBNYW5zZmllbGQgS2VlbmkNCiAgIEN5YmVyIFNvbHV0aW9ucyBJ
bmMuDQogICA2LTYtMyBNaW5hbWkgWW9zaGluYXJpDQogICBBb2JhLWt1LCBTZW5kYWkgOTg5
LTMyMDQNCiAgIEphcGFuDQoNCiAgIFBob25lOiArODEtMjItMzAzLTQwMTINCiAgIEUtbWFp
bDogZ2xlbm5AY3lzb2xzLmNvbQ0KDQogICBTcmkgR3VuZGF2ZWxsaQ0KICAgQ2lzY28gU3lz
dGVtcw0KICAgMTcwIFcuVGFzbWFuIERyaXZlLA0KICAgU2FuIEpvc2UsIENBIDk1MTM0DQog
ICBVU0ENCg0KICAgUGhvbmU6ICsxLTQwOC01MjctNjEwOQ0KICAgRS1tYWlsOiBzZ3VuZGF2
ZUBjaXNjby5jb20NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQpHbGVubiBNLiBLZWVuaS4gICAgICAgIEV4cGlyZXM6IERlY2VtYmVyIDI0
LCAyMDExICAgICAgICAgICAgICBbUGFnZSAxMF0NCgwNCg0KDQoNCg0KDQpJbnRlcm5ldCBE
cmFmdCAgICAgICAgICAgICAgICBwbWlwdjZNSUItVEMgICAgICAgICAgICAgICAgICAgICBK
dW5lIDIwMTENCg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEFQUEVORElY
DQoNCg0KVGhpcyBzZWN0aW9uIGRvY3VtZW50cyB0aGUgZGV2ZWxvcG1lbnQgb2YgdGhlIGRy
YWZ0LiBJdCB3aWxsIGJlDQpkZWxldGVkIHdoZW4gdGhlIGRyYWZ0IGJlY29tZXMgYW4gUkZD
Lg0KDQpSZXZpc2lvbiBIaXN0b3J5Og0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkds
ZW5uIE0uIEtlZW5pLiAgICAgICAgRXhwaXJlczogRGVjZW1iZXIgMjQsIDIwMTEgICAgICAg
ICAgICAgIFtQYWdlIDExXQ0KDA0KDQoNCg==
--B_3392036933_13585424--


From glenn@cysols.com  Mon Jun 27 17:36:27 2011
Return-Path: <glenn@cysols.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 6249621F8562 for <gen-art@ietfa.amsl.com>; Mon, 27 Jun 2011 17:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 YCEuabo6IseO for <gen-art@ietfa.amsl.com>; Mon, 27 Jun 2011 17:36:27 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by ietfa.amsl.com (Postfix) with ESMTP id C576821F855F for <gen-art@ietf.org>; Mon, 27 Jun 2011 17:36:23 -0700 (PDT)
Received: from [192.168.0.193] (cookie.win2004.cysol.co.jp [192.168.0.193]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id p5S0Zm26052772 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 28 Jun 2011 09:35:48 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4E0921E2.9000000@cysols.com>
Date: Tue, 28 Jun 2011 09:35:46 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
References: <CA2E6045.1F0F1%sgundave@cisco.com>
In-Reply-To: <CA2E6045.1F0F1%sgundave@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Dan Romascanu <dromasca@avaya.com>, gen-art@ietf.org, Jari Arkko <jari.arkko@piuha.net>, draft-ietf-netlmm-pmipv6-mib.all@tools.ietf.org
Subject: Re: [Gen-art] TC draft supporting draft-ietf-netlmm-pmipv6-mib-05.txt (resent???)
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, 28 Jun 2011 00:36:27 -0000

Hi,
   To follow-up on Sri's mail, this document does not introduce new
material. The textual conventions have been taken out of
pmipv6-mib-05.txt and put into a new independent pmipv6-tc-mib-00.txt.
The revised pmipv6-mib-06.txt (yet to be posted) refers to 
pmipv6-tc-mib-00.txt.

   Glenn

(2011/06/28 8:28), Sri Gundavelli wrote:
> Hi Jari,
>
> Attached is the TC draft for PMIPv6 ( a new document,   ­00 version, with
> the name draft-ietf-netlmm-pmipv6-tc-mib-00.txt).
>
> Based on the IESG inputs, specifically Dan¹s comment, our Editor (Glenn)
> worked out on the TC draft for PMIPv6. Since, this work is tied to the MIB
> which was the product of the NETLMM WG,  we are not sure where to post this
> doc. *Please advise*,  if this will be an AD sponsored doc, or if we can
> post it as a NETLMM draft. The tools would not allow us to post this
> document with the current file name.
>
> ---
> DISCUSS # 3
>             This will require a separate PMIP6-TC-document.
> ----
>
> Regards
> Sri
>
>>
>>
>
>


From kwburgi@tycho.ncsc.mil  Tue Jun 28 08:05:38 2011
Return-Path: <kwburgi@tycho.ncsc.mil>
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 403C111E80F4; Tue, 28 Jun 2011 08:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rrQbXdfplYZQ; Tue, 28 Jun 2011 08:05:36 -0700 (PDT)
Received: from msux-gh1-uea02.nsa.gov (msux-gh1-uea02.nsa.gov [63.239.65.40]) by ietfa.amsl.com (Postfix) with ESMTP id 9222722800D; Tue, 28 Jun 2011 08:05:04 -0700 (PDT)
Received: from celebration.infosec.tycho.ncsc.mil (localhost [127.0.0.1]) by msux-gh1-uea02.nsa.gov (8.12.10/8.12.10) with ESMTP id p5SF51gJ016186; Tue, 28 Jun 2011 15:05:02 GMT
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 28 Jun 2011 11:05:02 -0400
Message-ID: <D22B261D1FA3CD48B0414DF484E43D32986F8C@celebration.infosec.tycho.ncsc.mil>
In-Reply-To: <4DFBD34B.7000900@isode.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Gen-art] Gen-Art Last Call Review: draft-burgin-ipsec-suiteb-profile-00
Thread-Index: AcwtPRWGmGWrY4fVRNa9LcyPVsb9DwIZM8OQ
References: <4D9C8D2A.7080605@nostrum.com> <4DFBD34B.7000900@isode.com>
From: "Burgin, Kelley W." <kwburgi@tycho.ncsc.mil>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>, <draft-burgin-ipsec-suiteb-profile.all@tools.ietf.org>
X-Mailman-Approved-At: Tue, 28 Jun 2011 08:54:05 -0700
Cc: gen-art@ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-Art Last Call Review: draft-burgin-ipsec-suiteb-profile-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: Tue, 28 Jun 2011 15:05:38 -0000

Thank you for the review. Comments inline below, noted with [kwb].

Kelley

-----Original Message-----
From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]=20
Sent: Friday, June 17, 2011 6:21 PM
To: draft-burgin-ipsec-suiteb-profile.all@tools.ietf.org
Cc: gen-art@ietf.org; iesg@ietf.org
Subject: [Gen-art] Gen-Art Last Call Review:
draft-burgin-ipsec-suiteb-profile-00

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-burgin-ipsec-suiteb-profile-00
Reviewer: Alexey Melnikov
Review Date: 17-June-2011
IETF LC End Date: 13-July-2011
IESG Telechat

Summary: not ready, but issues are not difficult to address

Major issues:

4.3.  Suite B IKEv2 Authentication

    If configured at a minimum level of security of 128 bits, a system
    MUST use either ECDSA-256 or ECDSA-384 for IKE authentication.  It
    is allowable for one party to authenticate with ECDSA-256 and the
    other party to authenticate with ECDSA-384.  This flexibility will
    allow interoperability between an initiator and a responder that
    have different sizes of ECDSA authentication keys.

    Initiators and responders in a system configured at a minimum level
    of security of 128 bits MUST be able to verify ECDSA-256 signatures
    and SHOULD be able to verify ECDSA-384 signatures.

The last SHOULD seems to mean that at the minimum level of security of=20
128 bits
it is possible to have a situation when a responder might be unable
to verify ECDSA-384 signatures used by an initiator.

Is this truly desirable?

[kwb] Would we like minLOS_128 devices to be able to also support the
192 bit sure, but there might be cases where they simply can't. That's
why it's a SHOULD and not a MUST.

5.  Suite B Security Associations (SAs) for IKEv2 and IPsec

    An initiator in a system configured at a minimum level of security
    of 128 bits MUST offer one or more of the four suites:
    Suite-B-GCM-128, Suite-B-GMAC-128, Suite-B-GCM-256 or
    Suite-B-GMAC-256 [RFC4869bis].  Suite-B-GCM-128 and
    Suite-B-GMAC-128, if offered, must appear in the IKEv2 and IPsec SA
    payloads before any offerings of Suite-B-GCM-256 and
    Suite-B-GMAC-256.

Does this mean that the responder needs to support all 4?
I think it does (or otherwise there is a chance of non
interoperability),
but it would be better to state that explicitly.

[kwb] I will add "A responder configured in a system at a minimum level
of security of 128 bits MUST support Suite-B-GCM-128 and
Suite-B-GMAC-128 and SHOULD support Suite-B-GCM-256 and
Suite-B-GMAC-256." To the beginning of the following paragraph.

    A responder configured in a system at a minimum level of security
    of 128 bits SHOULD accept the first Suite B UI suite offered by the

Is this a new requirement in this document, or is this repeating a=20
general requirement stated in another document? If the latter, a=20
reference is needed here, ideally accompanied by some text stating that=20
the requirement comes from another document.

Similar text later in the same section.

    initiator that it can accommodate.  If none of the four suites are
    offered, the responder MUST return a Notify payload with the error
    "NO_PROPOSAL_CHOSEN".

[kwb] These are new, so no reference is given.

8.  Additional Requirements

    Suite B IPsec compliant systems MUST support IKEv2 and MUST NOT use
    IKEv1.  However, to accommodate backward compatibility, a Suite B
    IPsec compliant system can be configured to use IKEv1 so long as
only
    IKEv2 is used between a Suite B compliant initiator and responder.

You lost me here. Can you please explain what is the meaning of
the second sentence?

[kwb] This means that the box can talk both IKEv1 and IKEv2 but when
they're talking in "Suite B mode" they can't use IKEv1.

    The administrative user interface, (UI), for a system that conforms
    to this profile MUST allow the operator to specify a single suite.
    If only one suite is specified in the administrative UI, the IKEv2
    implementation MUST only offer algorithms for that one suite.

This requirement is unusual, because IETF documents rarely have=20
requirements on UIs. Can you please elaborate what is this trying to=20
achieve?

[kwb] It is unusual, but the accompanying draft
(draft-law-rfc4869bis-01) defines Suite B User Interface suites (the
term UI is from RFC 4308) that this draft refers to so this seems like
the appropriate term. From RFC 4308: "These suites may be presented in
the administrative interface of the IPsec system."


Minor issues:

3.  Suite B Requirements

       Curve        NIST name       SECG name   IANA assigned DH group #
       -----------------------------------------------------------------
       P-256       nistp256        secp256r1               19
       P-384       nistp384        secp384r1               20

This doesn't tell where to look for the IANA assigned DH group.
An Informative reference would be nice.

[kwb] Will add "IANA has already registered these DH groups in
[IKEV2IANA]." after the table, and add to Informative References:
[IKEV2IANA] "Internet Key Exchange Version 2 (IKEv2) Parameters",
<http://www.iana.org>.

10.  IANA Considerations

    TBD.

I think this needs to be replaced with a statement saying that this=20
document doesn't require any new actions from IANA, because all=20
algorithm are already registered in RFCs referenced by this document.

[kwb] Will replace "TBD" with "None."

idnits 2.12.12 reports:

   Miscellaneous warnings:
=20
------------------------------------------------------------------------
----

   -- The document has a disclaimer for pre-RFC5378 work, but was first
      submitted on or after 10 November 2008.  Does it really need the
      disclaimer?

Please double check that that is intentional.

[kwb] This is intentional since this draft uses text from documents
published before 10 November 2008.

Nits/editorial comments:

7.  Generating Keying Material for the IKE SA

    IKEv2, [RFC5996], allows for the reuse of Diffie-Hellman ephemeral
    keys. Section 5.6.4.3 of NIST SP800-56A states that an ephemeral
    private key MUST be used in exactly one key establishment
    transaction and MUST be zeroized after its use.

Is "zeroized" a correct verb?

[kwb] The terms zeroize, zeroized, zeroizing are used in security
standards (e.g., RFCs 1319-1321, 4949).


From wassim.haddad@ericsson.com  Wed Jun 29 15:58:40 2011
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 712C011E80FC for <gen-art@ietfa.amsl.com>; Wed, 29 Jun 2011 15:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DzNFRcE7hi+R for <gen-art@ietfa.amsl.com>; Wed, 29 Jun 2011 15:58:40 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id E7EDC11E80F7 for <gen-art@ietf.org>; Wed, 29 Jun 2011 15:58:39 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p5TMwaQk029942 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Jun 2011 17:58:39 -0500
Received: from [155.53.234.137] (147.117.20.214) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.3.137.0; Wed, 29 Jun 2011 18:58:36 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 29 Jun 2011 15:58:35 -0700
Message-ID: <B4F75425-B05A-4D8E-8D9C-F98B121C8ECF@ericsson.com>
To: Gen-art <gen-art@ietf.org>
MIME-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: draft-ietf-mpls-tp-loss-delay-profile.all@tools.ietf.org
Subject: [Gen-art]  Review of draft-ietf-mpls-tp-loss-delay-profile-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: Wed, 29 Jun 2011 22:58:40 -0000

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

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

Document:  draft-ietf-mpls-tp-loss-delay-profile-03
Reviewer:  Wassim Haddad
Review Date: June 29, 2011
IETF LC End Date:
IESG Telechat date: June 30, 2011

Summary:  This document is ready to be published as Informational RFC

Major issues: None

Minor issues: None

Nits/editorial comments:

Page 1: Abstract: remove _the_ efficient and accurate measurement


Regards,

Wassim H.






From mccap@petoni.org  Wed Jun 29 20:48:05 2011
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 C50AC21F8581 for <gen-art@ietfa.amsl.com>; Wed, 29 Jun 2011 20:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MgOHFXP8uO2Y for <gen-art@ietfa.amsl.com>; Wed, 29 Jun 2011 20:48:05 -0700 (PDT)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id E7D9021F857C for <gen-art@ietf.org>; Wed, 29 Jun 2011 20:48:04 -0700 (PDT)
Received: by fxe4 with SMTP id 4so2350840fxe.27 for <gen-art@ietf.org>; Wed, 29 Jun 2011 20:48:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.95.153 with SMTP id d25mr2368814fan.4.1309405683859; Wed, 29 Jun 2011 20:48:03 -0700 (PDT)
Received: by 10.223.108.10 with HTTP; Wed, 29 Jun 2011 20:48:03 -0700 (PDT)
X-Originating-IP: [12.234.76.2]
Date: Wed, 29 Jun 2011 22:48:03 -0500
Message-ID: <BANLkTinZ414ycCgrGzjB7bCrZZakVD8DCw@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-appsawg-rfc3536bis.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-appsawg-rfc3536bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 03:48:05 -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-appsawg-rfc3536bis-04
Reviewer: Pete McCann
Review Date: 2011-06-29
IETF LC End Date:
IESG Telechat date: 2011-06-30

Summary: Ready

Major issues: none

Minor issues: none

Nits/editorial comments: none

From wassim.haddad@ericsson.com  Wed Jun 29 22:20:08 2011
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 7AEC611E812E for <gen-art@ietfa.amsl.com>; Wed, 29 Jun 2011 22:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1aekG0ZfnIF for <gen-art@ietfa.amsl.com>; Wed, 29 Jun 2011 22:20:07 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3D91D11E812B for <gen-art@ietf.org>; Wed, 29 Jun 2011 22:20:07 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p5U5JwEd009739 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Jun 2011 00:20:03 -0500
Received: from client-vpn-083.edd.ericsson.se (147.117.20.214) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.3.137.0; Thu, 30 Jun 2011 01:19:57 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 29 Jun 2011 22:19:54 -0700
Message-ID: <531B4730-590F-4CF1-A37F-C48FAB84A95E@ericsson.com>
To: Gen-art <gen-art@ietf.org>
MIME-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: draft-ietf-pim-mtid.all@tools.ietf.org
Subject: [Gen-art]  Review of draft-ietf-pim-mtid-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: Thu, 30 Jun 2011 05:20:08 -0000

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

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

Document:  draft-ietf-pim-mtid-08
Reviewer:  Wassim Haddad
Review Date: June 29, 2011
IETF LC End Date:
IESG Telechat date: June 30, 2011

Summary:  This document is ready to be published as a proposed standard.

Major issues: None

Minor issues: None

Nits/editorial comments: None


Regards,

Wassim H.






From Francis.Dupont@fdupont.fr  Thu Jun 30 06:53:59 2011
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 770E111E810D for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 06:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ekJzAhGCVs70 for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 06:53:58 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id E30E611E8100 for <gen-art@ietf.org>; Thu, 30 Jun 2011 06:53:56 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p5UDrtgA051241; Thu, 30 Jun 2011 15:53:55 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201106301353.p5UDrtgA051241@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: draft-ietf-dkim-rfc4871bis.all@tools.ietf.org
Date: Thu, 30 Jun 2011 15:53:55 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: gen-art@ietf.org
Subject: [Gen-art] (not yet) review of draft-ietf-dkim-rfc4871bis-12.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, 30 Jun 2011 13:53:59 -0000

It seems there is a debate about the draft-ietf-dkim-rfc4871bis-12.txt
document so I differ a bit the review (I am the assigned gen-art
reviewer) for the case a new version could be published soon...
 If I am wrong and I should review it ASAP please signal it to me
at my other Email (less spam and I read it at least once per day)
at fdupont@isc.org.

Thanks

Francis.Dupont@fdupont.fr

From suresh.krishnan@ericsson.com  Thu Jun 30 10:50:09 2011
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 B6AA311E82B1 for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 10:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.465
X-Spam-Level: 
X-Spam-Status: No, score=-106.465 tagged_above=-999 required=5 tests=[AWL=0.134, 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 SGxQ+WLuMEx4 for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 10:50:08 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id B117711E82AD for <gen-art@ietf.org>; Thu, 30 Jun 2011 10:50:08 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p5UHo745011141 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Jun 2011 12:50:08 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.253]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Thu, 30 Jun 2011 13:50:07 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "draft-ietf-karp-design-guide.all@tools.ietf.org" <draft-ietf-karp-design-guide.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Date: Thu, 30 Jun 2011 13:50:06 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-karp-design-guide-02.txt
Thread-Index: AQHMN04la/cmm47Ah0K3AkDu2sgGQQ==
Message-ID: <4FD1E7CD248BF84F86BD4814EDDDBCC1513D42BE33@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-karp-design-guide-02.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, 30 Jun 2011 17:50:09 -0000

I am the assigned Gen-ART reviewer for
draft-ietf-karp-design-guide-02.txt

For background on Gen-ART, please see the FAQ at
<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.

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

Summary: This draft is ready for publication as an Informational RFC but=20
please consider changing the abstract.

Minor
=3D=3D=3D=3D

* The abstract is a bit too long and covers things that are not relevant to=
=20
the document while distracting the reader from the actual purpose of the
document. Please consider reworking the abstract.

Thanks
Suresh =

From mahoney@nostrum.com  Thu Jun 30 14:42:36 2011
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 867D611E8328 for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 14:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B24E+uepH7o8 for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 14:42:35 -0700 (PDT)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB7A11E8323 for <gen-art@ietf.org>; Thu, 30 Jun 2011 14:42:35 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-50-10.dllstx.fios.verizon.net [173.71.50.10]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5ULfJKG068634 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 30 Jun 2011 16:41:19 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4E0CED7F.50609@nostrum.com>
Date: Thu, 30 Jun 2011 16:41:19 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.50.10 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2011-06-30
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, 30 Jun 2011 21:42:36 -0000

Hi all,

Here's the link to the new LC assignments:
http://wiki.tools.ietf.org/dav/genart/reviewers-110630-lc.html

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 Jun 30 14:44:54 2011
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 0904B11E8323 for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 14:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACwcx1e84ws7 for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 14:44:53 -0700 (PDT)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by ietfa.amsl.com (Postfix) with ESMTP id 3469E11E8314 for <gen-art@ietf.org>; Thu, 30 Jun 2011 14:44:53 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-50-10.dllstx.fios.verizon.net [173.71.50.10]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5ULhbWr068838 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 30 Jun 2011 16:43:37 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4E0CEE09.1080201@nostrum.com>
Date: Thu, 30 Jun 2011 16:43:37 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.50.10 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2011-07-14 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, 30 Jun 2011 21:44:54 -0000

Hi all,

Assignments for the telechat can be found here:
http://wiki.tools.ietf.org/dav/genart/reviewers-110714-telechat.html

With the updated 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 Jun 30 18:16:54 2011
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 B78FF11E8161 for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 18:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, 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 aYf2naSOIsPq for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 18:16:54 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF3E11E8090 for <gen-art@ietf.org>; Thu, 30 Jun 2011 18:16:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 8EFE73244271; Thu, 30 Jun 2011 18:16:17 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-33.clppva.btas.verizon.net [71.161.50.33]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 082E83228BE9; Thu, 30 Jun 2011 18:16:16 -0700 (PDT)
Message-ID: <4E0D1FDA.1030201@joelhalpern.com>
Date: Thu, 30 Jun 2011 21:16:10 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4E0CEE09.1080201@nostrum.com>
In-Reply-To: <4E0CEE09.1080201@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]  Review: draft-ietf-mpls-tp-identifiers-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, 01 Jul 2011 01:16: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-mpls-tp-identifiers-06
     MPLS-TP Identifiers
Reviewer: Joel M. Halpern
Review Date: 30-June-2011
IETF LC End Date: 11-July-2011
IESG Telechat date: 14-July-2011

Summary: This document is ready for publication as a proposed standard

Major issues:

Minor issues:

Nits/editorial comments:

From jmh@joelhalpern.com  Thu Jun 30 18:21:26 2011
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 C7A8111E80A6 for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 18:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, 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 dq-vRah7Kudr for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 18:21:26 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by ietfa.amsl.com (Postfix) with ESMTP id 6366611E8098 for <gen-art@ietf.org>; Thu, 30 Jun 2011 18:21:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 5E94A3244271; Thu, 30 Jun 2011 18:20:56 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-33.clppva.btas.verizon.net [71.161.50.33]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id D34BE3228BD8; Thu, 30 Jun 2011 18:20:55 -0700 (PDT)
Message-ID: <4E0D20F2.5050108@joelhalpern.com>
Date: Thu, 30 Jun 2011 21:20:50 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4DC1C9C8.8000509@nostrum.com>
In-Reply-To: <4DC1C9C8.8000509@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]   Review: draft-ietf-sidr-repos-struct-08.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 01:21:26 -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-sidr-repos-struct-08.txt
     A Profile for Resource Certificate Repository Structure
Reviewer: Joel M. Halpern
Review Date: 30-June-2011
IETF LC End Date: 18-May-2011
IESG Telechat date: 14-July-2011

Summary:  This document is ready for publication as a BCP.


From jmh@joelhalpern.com  Thu Jun 30 18:24:19 2011
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 00EAD11E8098 for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 18:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, 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 nvgtEaHbfBTA for <gen-art@ietfa.amsl.com>; Thu, 30 Jun 2011 18:24:18 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by ietfa.amsl.com (Postfix) with ESMTP id 84F3011E8198 for <gen-art@ietf.org>; Thu, 30 Jun 2011 18:24:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 79356325B2B3; Thu, 30 Jun 2011 18:23:48 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-33.clppva.btas.verizon.net [71.161.50.33]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id B28F03244271; Thu, 30 Jun 2011 18:23:47 -0700 (PDT)
Message-ID: <4E0D219E.9020505@joelhalpern.com>
Date: Thu, 30 Jun 2011 21:23:42 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4DE80611.1070108@nostrum.com>
In-Reply-To: <4DE80611.1070108@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, lionel.morand@orange-ftgroup.com
Subject: [Gen-art]   Review: draft-ietf-dime-local-keytran-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 01:24:19 -0000

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

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

Document: draft-ietf-dime-local-keytran-11
     Diameter Attribute-Value Pairs for Cryptographic Key Transport
Reviewer: Joel M. Halpern
Review Date: 30-June-2011
IETF LC End Date: 14-June-2011
IESG Telechat date: 14-July-2011

Summary: This document is presumably ready for publication as a proposed 
standard,

While I would have appreciated an answer to the quesiton below, that 
should not hold up publication.

Open Question:
     The document carefully and reasonably does not define the contents 
of the keying material AVP.  This reviewer presumes that those closer to 
the activity will know where the contents have been or will be defined. 
  Are they already defined, or will they be defined in future documents? 
  If they are already defined, would it make sense to state that, and 
identify the location?  (My confusion is that it would seem difficult 
for existing RFCs to define the format of a TLV that did not exist.  But 
that may be a failure of my understanding.)

Thank you,
Joel M. Halpern
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art

