
From mahoney@nostrum.com  Thu Nov  1 14:03:37 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C53621F8DB7 for <gen-art@ietfa.amsl.com>; Thu,  1 Nov 2012 14:03:37 -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 ilbwZwiiiyEq for <gen-art@ietfa.amsl.com>; Thu,  1 Nov 2012 14:03:36 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DEA7B21F87B2 for <gen-art@ietf.org>; Thu,  1 Nov 2012 14:03:09 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qA1L39Eb024508 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 1 Nov 2012 16:03:09 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <5092E38D.8070305@nostrum.com>
Date: Thu, 01 Nov 2012 16:03:09 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-11-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 21:03:37 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Alexey Melnikov   2012-11-12 draft-ietf-mmusic-sdp-media-capabilities-15

Christer Holmberg 2012-11-26    draft-nir-ipsecme-erx-07

Dan Romascanu     2012-11-13    draft-ietf-ipfix-a9n-07 *

David Black       2012-11-13 draft-ietf-radext-ipv6-access-13

Francis Dupont    2012-11-09 draft-ietf-v6ops-ra-guard-implementation-05 **

* On the 2012-11-15 telechat

** 2nd last call


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

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


The standard template is included below.

Thanks,

Jean

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From jmh@joelhalpern.com  Sat Nov  3 14:26:13 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E945921F9B59 for <gen-art@ietfa.amsl.com>; Sat,  3 Nov 2012 14:26:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[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 J7WftyvbfQrj for <gen-art@ietfa.amsl.com>; Sat,  3 Nov 2012 14:26:13 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 8A65C21F9A35 for <gen-art@ietf.org>; Sat,  3 Nov 2012 14:26:13 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 43976559903 for <gen-art@ietf.org>; Sat,  3 Nov 2012 14:26:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 390E91BD79B7; Sat,  3 Nov 2012 14:26:10 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [130.129.32.242] (unknown [130.129.32.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id E7E191BD79A0; Sat,  3 Nov 2012 14:26:09 -0700 (PDT)
Message-ID: <50958BEC.5040108@joelhalpern.com>
Date: Sat, 03 Nov 2012 17:26:04 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>,  General Area Review Team <gen-art@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B023C19@ESESSMB209.ericsson.se> <50954629.6040401@nostrum.com>
In-Reply-To: <50954629.6040401@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art]  Review: draft-nir-ipsecme-erx-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: Sat, 03 Nov 2012 21:26: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-nir-ipsecme-erx-07
     An IKEv2 Extension for Supporting ERP
Reviewer: Joel M. Halpern
Review Date: 3-November-2012
IETF LC End Date: 26-November-2012
IESG Telechat date:N/A

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



From elwynd@dial.pipex.com  Mon Nov  5 08:22:27 2012
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB51721F887C for <gen-art@ietfa.amsl.com>; Mon,  5 Nov 2012 08:22:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CjBSDTw8WUqJ for <gen-art@ietfa.amsl.com>; Mon,  5 Nov 2012 08:22:27 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 4A55221F8828 for <gen-art@ietf.org>; Mon,  5 Nov 2012 08:22:26 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1TVPRO-0005Sc-JK; Mon, 05 Nov 2012 16:22:22 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Mon, 05 Nov 2012 16:23:35 +0000
Message-Id: <1352132615.23621.1264.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-karp-ospf-analysis.all@tools.ietf.org
Subject: [Gen-art] Gen-art last call review of draft-ietf-karp-ospf-analysis-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 16:22:27 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive. (Sorry it is rather late).

Document: draft-ietf-karp-ospf-analysis-05
Reviewer: Elwyn Davies
Review Date: 5 November 2012
IETF LC End Date: 2012-10-17
IESG Telechat date: (if known) -

Summary: Almost ready.  Just a couple of minor nits.

Major issues:
None

Minor issues:
None

Nits/editorial comments:
s2.2:
> RFC 4552 [RFC4552] describes how the authentication header and
>    encapsulating security payload mechanism can be used to protect
>    OSPFv3 packets.
I guess this piece ought to say that AH, ESP, SPI etc come out of IPsec
and give a reference a bit earlier in the section - IPsec is mentioned
but no reference given in the 2nd para of the section.

s3, para 1: 
>    As discussed, neither version of OSPF meets the requirements of
>    inter-connection or intra-connection replay protection.
Neither of the discussions above mention the phrases 'inter-connection'
or 'intra-connection'.  For OSPFv3 this is implicit because 'no replay
protection is provided'.  For OSPFv2 it would be desirable to explain
how the problems outlined in s2.1 relate to these terms. 
   
s3, para 4: The first two sentences contain the phrase 
'a number of attacks that are possible because of a per-packet replay.'
Ther sentences can be easily combined

s3, para 5:
>    Unfortunately, OSPFv2 does
>    not have a procedure for dealing with sequence numbers reaching the
>    maximum age.
Is 'age' the correct term here?  'maximum value' perhaps?


From mahoney@nostrum.com  Thu Nov  8 14:12:42 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4FB621F85BB for <gen-art@ietfa.amsl.com>; Thu,  8 Nov 2012 14:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N4CFw9EcSczo for <gen-art@ietfa.amsl.com>; Thu,  8 Nov 2012 14:12:42 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3E721F84D3 for <gen-art@ietf.org>; Thu,  8 Nov 2012 14:12:42 -0800 (PST)
Received: from dhcp-14c2.meeting.ietf.org (dhcp-14c2.meeting.ietf.org [130.129.20.194]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qA8MCfF7027909 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 8 Nov 2012 16:12:41 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <509C2E59.10604@nostrum.com>
Date: Thu, 08 Nov 2012 17:12:41 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 130.129.20.194 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-11-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, 08 Nov 2012 22:12:42 -0000

Hi all,

The following reviewers have assignments:

Reviewer            LC end        Draft

Kathleen Moriarty   2012-11-21    draft-ietf-imapmove-command-02

Richard Barnes      2012-11-26    draft-ietf-mediactrl-mrb-16 **

** 2nd last call


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

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


The standard template is included below.

Thanks,

Jean

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mahoney@nostrum.com  Thu Nov  8 14:18:30 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7C021F84E9 for <gen-art@ietfa.amsl.com>; Thu,  8 Nov 2012 14:18:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sau+2cLrUdxY for <gen-art@ietfa.amsl.com>; Thu,  8 Nov 2012 14:18:29 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BB80D21F84DC for <gen-art@ietf.org>; Thu,  8 Nov 2012 14:18:27 -0800 (PST)
Received: from dhcp-14c2.meeting.ietf.org (dhcp-14c2.meeting.ietf.org [130.129.20.194]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qA8MIN7D028436 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 8 Nov 2012 16:18:24 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <509C2FAE.2070901@nostrum.com>
Date: Thu, 08 Nov 2012 17:18:22 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 130.129.20.194 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-11-15 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, 08 Nov 2012 22:18:30 -0000

Hi all,

The following reviewers have assignments:

Reviewer             LC end       Draft

Ben Campbell         2012-08-14   draft-ietf-mptcp-api-06 *

Ben Campbell         2012-10-23   draft-leiba-extended-doc-shepherd-01 *

Brian Carpenter      2012-11-09   draft-ietf-mpls-ipv6-pw-lsp-ping-03 **

Dan Romascanu        2012-11-13   draft-ietf-ipfix-a9n-07

Elwyn Davies         2012-10-17   draft-ietf-karp-ospf-analysis-05 **

Francis Dupont       2012-11-09   draft-ietf-v6ops-ra-guard-implementation-05 *

Joel Halpern         2012-03-20   draft-ietf-bmwg-protection-meth-12 *

Kathleen Moriarty    2012-11-01   draft-gont-intarea-obsolete-eid-option-01 **

Richard Barnes       2012-11-02   draft-ietf-pkix-caa-15

Roni Even            2012-11-06   draft-leiba-5322upd-from-group-07 **

Suresh Krishnan      2012-10-29   draft-ietf-dnsext-rfc2671bis-edns0-09 *

Suresh Krishnan      2012-11-09   draft-ietf-mpls-mldp-in-band-signaling-07

Wassim Haddad        2012-10-24   draft-ietf-xrblock-rtcp-xr-delay-10

* Earlier draft reviewed
** Already reviewed

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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From brian.e.carpenter@gmail.com  Fri Nov  9 11:49:37 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B57C21F860C for <gen-art@ietfa.amsl.com>; Fri,  9 Nov 2012 11:49:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.591
X-Spam-Level: 
X-Spam-Status: No, score=-103.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 6wOnmWwaBWuU for <gen-art@ietfa.amsl.com>; Fri,  9 Nov 2012 11:49:36 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6015E21F85F0 for <gen-art@ietf.org>; Fri,  9 Nov 2012 11:49:36 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so3205372pad.31 for <gen-art@ietf.org>; Fri, 09 Nov 2012 11:49:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=U9pkO65MI61uLgH+YunkyGlIIT2G9scIXq+kgRfmgaY=; b=d6OVD0apFyyCEz01Cx2jFbYg/Xx1JntXNN5yvQwmzj03lYqZHydw/YJ8RE1nm/UQ+M C6LZPy0R+SWYT/TX8u0MTaMzIrCNXMUTBkqGCdSZoYIb6gGA2da4JC7g0mR8ySftX0St fz9EuFGsiBK4j+E3hwMD6eaWHhz5Os0X+3RxfmLPwHI+xh5PULCsUak3c1Y0YfpuFvy/ v2HbprMRvg50rtx8rw3qM/IRIGkF7eG8EzDlFIw6WhJHschTGEKEcyMLiK3n+QZTJNrR 2ejrDAOqpt5BbqpUN8lw8eTjUEovhPQNEH368vLdjmovY9MSDxl/FF0BcDly23Sgr200 RnZA==
Received: by 10.68.238.34 with SMTP id vh2mr36942948pbc.6.1352490576224; Fri, 09 Nov 2012 11:49:36 -0800 (PST)
Received: from [130.129.19.51] (dhcp-1333.meeting.ietf.org. [130.129.19.51]) by mx.google.com with ESMTPS id ue7sm2410533pbc.53.2012.11.09.11.49.35 (version=SSLv3 cipher=OTHER); Fri, 09 Nov 2012 11:49:35 -0800 (PST)
Message-ID: <509D5E5B.3090002@gmail.com>
Date: Fri, 09 Nov 2012 19:49:47 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-mpls-ipv6-pw-lsp-ping.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------060702020502060403090906"
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 19:49:37 -0000

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

Please see attached review.

     Brian



--------------060702020502060403090906
Content-Type: text/plain;
 name="draft-ietf-mpls-ipv6-pw-lsp-ping-03-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-mpls-ipv6-pw-lsp-ping-03-carpenter.txt"

SSBoYXZlIGJlZW4gc2VsZWN0ZWQgYXMgdGhlIEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAo
R2VuLUFSVCkNCnJldmlld2VyIGZvciB0aGlzIGRyYWZ0IChmb3IgYmFja2dyb3VuZCBvbiBH
ZW4tQVJULCBwbGVhc2Ugc2VlDQpodHRwOi8vd3d3LmFsdmVzdHJhbmQubm8vaWV0Zi9nZW4v
YXJ0L2dlbi1hcnQtRkFRLmh0bWwpLg0KDQpQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZy
b20geW91ciBkb2N1bWVudCBzaGVwaGVyZA0Kb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcg
dmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLW1wbHMtaXB2
Ni1wdy1sc3AtcGluZy0wMy50eHQNClJldmlld2VyOiBCcmlhbiBDYXJwZW50ZXINClJldmll
dyBEYXRlOiAyMDEyLTExLTA5DQpJRVRGIExDIEVuZCBEYXRlOiAyMDEyLTExLTA5DQpJRVNH
IFRlbGVjaGF0IGRhdGU6IDIwMTItMTEtMTUNCg0KU3VtbWFyeTogIFJlYWR5DQotLS0tLS0t
LQ0KDQpDb21tZW50OiAgSSBjYW4ndCBmaW5kIGFueXRoaW5nIHRvIGNvbW1lbnQgb24hDQot
LS0tLS0tLQ==
--------------060702020502060403090906--

From cpignata@cisco.com  Fri Nov  9 12:51:49 2012
Return-Path: <cpignata@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 DC06C21F873F for <gen-art@ietfa.amsl.com>; Fri,  9 Nov 2012 12:51:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ys73d4RB8FRY for <gen-art@ietfa.amsl.com>; Fri,  9 Nov 2012 12:51:49 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 4409C21F86E0 for <gen-art@ietf.org>; Fri,  9 Nov 2012 12:51:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=185; q=dns/txt; s=iport; t=1352494309; x=1353703909; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=QmAPbIXLHdjO30TzMU+WiUOGH+hpyswxtZ4mZ3k3JiM=; b=SCi7m34B8d1haTIfccCIAbdjwV5azNzOCjkr4gY1yfkqlwZKmK9Y/OiK /Rda9ljWuuSI9ydCEFKweqxeROe7oeRQHG8Qs08Ydx7r99n9itiBlYBYT qbmcSEAHdASF/iBnlj2jg4hT7ZZMw49DIzTLs9vCU55bYa9eAp0op7x1z A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFAFpsnVCtJXHB/2dsb2JhbABEhVK9cIEIgiABBBIBJ1EBCCIUMRElAgQBEggah1YDD519li0NiVSLLIZRYQOUJo0HgyaBa4Jvghk
X-IronPort-AV: E=McAfee;i="5400,1158,6891"; a="140701054"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-6.cisco.com with ESMTP; 09 Nov 2012 20:51:49 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id qA9KpmoM021701 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 9 Nov 2012 20:51:48 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.217]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.001; Fri, 9 Nov 2012 14:51:48 -0600
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "draft-ietf-mpls-ipv6-pw-lsp-ping.all@tools.ietf.org" <draft-ietf-mpls-ipv6-pw-lsp-ping.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
Thread-Topic: Gen-ART telechat review of draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt
Thread-Index: AQHNvrNjhTtCxbsSl0WAUcfTi/cx3ZfiC3KA
Date: Fri, 9 Nov 2012 20:51:47 +0000
Message-ID: <95067C434CE250468B77282634C96ED320D84757@xmb-aln-x02.cisco.com>
In-Reply-To: <509D5E5B.3090002@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [10.21.108.126]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19350.005
x-tm-as-result: No--29.843200-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <015BD44289599C4CB9318D89B1703BD4@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 20:51:50 -0000

Thanks much for the review, Brian!

-- Carlos.

On 11/9/12 2:49 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

>Please see attached review.
>
>     Brian
>
>


From kathleen.moriarty@emc.com  Fri Nov  9 16:21:03 2012
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D742021F85A9; Fri,  9 Nov 2012 16:21:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.932
X-Spam-Level: 
X-Spam-Status: No, score=-2.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id St9KZj7lwgcg; Fri,  9 Nov 2012 16:21:02 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id BA07621F86CF; Fri,  9 Nov 2012 16:21:02 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qAA0KqDC029805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Nov 2012 19:20:54 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 9 Nov 2012 19:20:35 -0500
Received: from mxhub21.corp.emc.com (mxhub21.corp.emc.com [128.222.70.133]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qAA0KX0X010810; Fri, 9 Nov 2012 19:20:33 -0500
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub21.corp.emc.com ([128.222.70.133]) with mapi; Fri, 9 Nov 2012 19:20:33 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-radext-ipv6-access.all@tools.ietf.org" <draft-ietf-radext-ipv6-access.all@tools.ietf.org>
Date: Fri, 9 Nov 2012 19:20:31 -0500
Thread-Topic: Gen-art review of draft-ietf-radext-ipv6-access-13
Thread-Index: AQHNvsGVnCt/lgkBo0y5SDDImZ1WIg==
Message-ID: <F5063677821E3B4F81ACFB7905573F24092B0382@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "David.Miles@google.com" <David.Miles@google.com>, "sarikaya@ieee.org" <sarikaya@ieee.org>, "wdec@cisco.com" <wdec@cisco.com>, "blourdelet@aim.com" <blourdelet@aim.com>, "gwz@net-zen.net" <gwz@net-zen.net>
Subject: [Gen-art] Gen-art review of draft-ietf-radext-ipv6-access-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: Sat, 10 Nov 2012 00:21: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-radext-ipv6-access-13
Reviewer: Kathleen Moriarty
Review Date: November 9, 2012
IETF LC End Date: Tuesday
IESG Telechat date: (if known)

Summary:  The document is ready with nits.

Major issues:

Minor issues:

Nits/editorial comments:
Section 2, first sentence of second paragraph:
"a" should be "an" and protocols should be singular with either a or an.
In the depicted scenario the NAS may embed an IP addressing protocol (...

Section 3.1, first sentence:
Address does not need to have a capital "a".

Section 3.2, Third paragraph, first sentence,
Attribute does not need to have a capital "a"
Change from: A summary of the DNS-Server-IPv6-Address Attribute format is g=
iven
To:  A summary of the DNS-Server-IPv6-Address attribute format is given
=20
Section 3.3, First sentence:
Attribute does not need to be capitalized

Section 3.5, Attribute is capitalized here too and does not need to be, rec=
ommend searching through the document to replace them all with "attribute".

Section 3.6: Section Header, change lower case "attribute" to "Attribute" a=
s all the other section titles are capitalized.  The use of "attribute" in =
the body text of this section is already lower case.

Section 4: Change "Attribute" to "attribute"

Security Section:
The first sentence mischaracterizes the draft.  I think it should be someth=
ing more along the lines of the abstract:
>From the security section:
"This document describes the use of RADIUS for the purposes of
   authentication, authorization and accounting in IPv6-enabled
   networks. "
Abstract: "This document specifies additional IPv6 RADIUS attributes useful=
 in
   residential broadband network deployments. "

The following from the idnits report should be resolved:=20
Checking nits according to http://www.ietf.org/id-info/checklist :
  -------------------------------------------------------------------------=
---

  ** There are 2 instances of too long lines in the document, the longest o=
ne
     being 3 characters in excess of 72.

  =3D=3D There are 1 instance of lines with non-RFC2606-compliant FQDNs in =
the
     document.=

From wassim.haddad@ericsson.com  Sun Nov 11 16:55:29 2012
Return-Path: <wassim.haddad@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1BB521F84B2 for <gen-art@ietfa.amsl.com>; Sun, 11 Nov 2012 16:55:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACgGrkHqk4WD for <gen-art@ietfa.amsl.com>; Sun, 11 Nov 2012 16:55:29 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 306BD21F84B1 for <gen-art@ietf.org>; Sun, 11 Nov 2012 16:55:28 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id qAC0tQAt003216 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 11 Nov 2012 18:55:27 -0600
Received: from [164.48.125.41] (147.117.20.214) by eusaamw0712.eamcs.ericsson.se (147.117.20.182) with Microsoft SMTP Server id 8.3.279.1; Sun, 11 Nov 2012 19:55:25 -0500
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 11 Nov 2012 16:55:22 -0800
Message-ID: <7336C265-3ED4-4AFC-8C9D-32B67BE2244A@ericsson.com>
To: Gen-art <gen-art@ietf.org>
MIME-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Cc: draft-ietf-xrblock-rtcp-xr-delay.all@tools.ietf.org
Subject: [Gen-art]  Gen-ART review of draft-ietf-xrblock-rtcp-xr-delay-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: Mon, 12 Nov 2012 00:55:29 -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>

Document: draft-ietf-xrblock-rtcp-xr-delay-10
Reviewer:  Wassim Haddad
Review Date: 11 Nov 2012
IETF LC End Date: 24 Oct 2012
IETF Telechat Date: 15 Nov 2012

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

- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.







From jmh@joelhalpern.com  Mon Nov 12 08:22:35 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F03C421F84CD; Mon, 12 Nov 2012 08:22:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[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 KQwogQadDJ1i; Mon, 12 Nov 2012 08:22:34 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 119F021F8529; Mon, 12 Nov 2012 08:22:34 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 858AD558968; Mon, 12 Nov 2012 08:22:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 145A41C08E9; Mon, 12 Nov 2012 08:22:32 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-52-236.clppva.btas.verizon.net [71.161.52.236]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id CBA4A1C08F4; Mon, 12 Nov 2012 08:22:30 -0800 (PST)
Message-ID: <50A1223F.10902@joelhalpern.com>
Date: Mon, 12 Nov 2012 11:22:23 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
References: <4F5973CE.309@nostrum.com>
In-Reply-To: <4F5973CE.309@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ron Bonica <rbonica@juniper.net>, draft-ietf-bmwg-protection-meth.all@tools.ietf.org, bmwg@ietf.org, Al Morton <acmorton@att.com>
Subject: [Gen-art]   Review: draft-ietf-bmwg-protection-meth-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: Mon, 12 Nov 2012 16:22: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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-bmwg-protection-meth-12.txt
     Methodology for benchmarking MPLS protection mechanisms
Reviewer: Joel M. Halpern
Review Date: 12-November-2012
IETF LC End Date: 20-March-2012
IESG Telechat date: 15-November-2012

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

This reviewer notes with thanks that a number of his concerns from the 
March review have been well-addressed.


Major Comments:
     Section 5.7 is still internally inconsistent.  It says that "It is 
suggested that there be three or more traffic streams..." in the first 
paragraph.  The second paragraph then begins "At least 16 flows should 
be used, ..."  I have compared the definitions in RFC 4689, and I can 
not see how 3 streams (A group of packets treated as a single entity by 
the traffic receiver) can be 16 flows (one or more packets sharing a 
common intended pair of ingress and egress interfaces.)  I suspect that 
the issue is what traffic receiver is intended.  Is the intent that 
there be at least 3 LSPs with 16 or more flows running through them?


Minor Comments:
In section 5.1 "some" failure events are listed. It is unclear whether 
this list is the ones to be tested for, or just "some" events.  I think 
it is intended to be comprehensive, so why "some".

I presume that the use of the term Layer2 VC in section 6 is intended to 
refer to a pt-to-pt layer2 VPN component.  Is there an existing document 
where that term is used that way?  Could it be referenced?
For that matter, since the number of labels is the same in the Layer3 
cases and the Layer2 cases, could the Layer2 cases be omitted without 
loss of generality?



From dromasca@avaya.com  Mon Nov 12 09:32:26 2012
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9048A21F862E; Mon, 12 Nov 2012 09:32:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.914
X-Spam-Level: 
X-Spam-Status: No, score=-102.914 tagged_above=-999 required=5 tests=[AWL=-0.315, 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 yzDfewvuao7d; Mon, 12 Nov 2012 09:32:25 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 955C521F86CB; Mon, 12 Nov 2012 09:32:25 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAAEvoFDGmAcF/2dsb2JhbABEw1WBCIIeAQEBAQIBEh4KPwUNARUHDgYMDAdXAQQBGgEZh2IGC54mnAGRfmEDlxiEcYo2gnA
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="35752013"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 12 Nov 2012 12:25:09 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by co300216-co-erhwest-out.avaya.com with ESMTP; 12 Nov 2012 12:30:10 -0500
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, 12 Nov 2012 18:32:21 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04084693EB@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART review of draft-ietf-ipfix-a9n-07
Thread-Index: Ac3A+6vH5icZKWrlTQS9LiERx0FK1Q==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <gen-art@ietf.org>, "IETF IPFIX Working Group" <ipfix@ietf.org>
Cc: Ron Bonica <rbonica@juniper.net>
Subject: [Gen-art] Gen-ART review of draft-ietf-ipfix-a9n-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: Mon, 12 Nov 2012 17:32: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 wait for direction from your document shepherd or AD before
posting a new version of the draft.

Document: draft-ietf-ipfix-a9n-07.txt
Reviewer: Dan Romascanu
Review Date: 11/12/12
IETF LC End Date: 11/13/12
IESG Telechat date: 11/15/12

Summary: The draft is ready for publication, a few minor issues should
be clarified before approval and publication.

Major issues: None

Minor issues:

1. The definition of an aggregated flow in Section 2 reads:=20

> Aggregated Flow:   A Flow, as defined by
      [I-D.ietf-ipfix-protocol-rfc5101bis], derived from a set of zero
      or more original Flows within a defined Aggregation Interval.  The
      primary difference between a Flow and an Aggregated Flow in the
      general case is that the time interval (i.e., the two-tuple of
      start and end times) of a Flow is derived from information about
      the timing of the packets comprising the Flow, while the time
      interval of an Aggregated Flow is often externally imposed.  Note
      that an Aggregated Flow is defined in the context of an
      Intermediate Aggregation Process only.  Once an Aggregated Flow is
      exported, it is essentially a Flow as in
      [I-D.ietf-ipfix-protocol-rfc5101bis] and can be treated as such.


The way the second phrase is written confuses me. If 'the time interval
of an Aggregated Flow' is <often> externally imposed, this means that
there are exceptions? In which cases? And in these cases what is the
specific difference that makes that Flow to be Aggregated?=20

2. In Section 5.3.1 the URL quoted for the IPFIX Information Elements
registry http://www.iana.org/assignments/ipfix/ipfix.html does not
exist.=20

3. The IANA Note in section 7.2.4 is supposed to be left in the text? If
not, is it necessary to mention someplace else the issue of backwards
compatibility with the IE value in NetFlow version 9?=20

4. Same question for the IANA note in Section 10.=20



Nits/editorial comments:

1. Section 5.1.1:=20

> Each counter for an Original Flow is divided by the
      number of time _units_ the Original Flow covers, to derive a mean
      count rate.

What is the meaning of _units_?=20

2. Runing idnits leads to a number of formatting problems that I am sure
will be corrected by the RFC Editor.=20



From kathleen.moriarty@emc.com  Mon Nov 12 11:29:41 2012
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1581221F86D0; Mon, 12 Nov 2012 11:29:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HcK7fOTNnXEW; Mon, 12 Nov 2012 11:29:40 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4A321F8674; Mon, 12 Nov 2012 11:29:40 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qACJTcNB025188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Nov 2012 14:29:39 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 12 Nov 2012 14:29:24 -0500
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.222.70.135]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qACJTNdU006100; Mon, 12 Nov 2012 14:29:23 -0500
Received: from mxhub40.corp.emc.com (128.222.70.107) by mxhub23.corp.emc.com (128.222.70.135) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 12 Nov 2012 14:29:23 -0500
Received: from mx15a.corp.emc.com ([169.254.1.120]) by mxhub40.corp.emc.com ([128.222.70.107]) with mapi; Mon, 12 Nov 2012 14:29:22 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Fernando Gont <fgont@si6networks.com>
Date: Mon, 12 Nov 2012 14:29:21 -0500
Thread-Topic: Gen-art review of draft-gont-intarea-obsolete-eid-option-01
Thread-Index: Ac3BBbPEQVCEr9v4T8m5J7p7+zUXPQABjyIg
Message-ID: <F5063677821E3B4F81ACFB7905573F24CAF56B8C@MX15A.corp.emc.com>
References: <182B306DD37FAD4882AB1C1EBE2CA9020DCDDF9129@MX15A.corp.emc.com> <50A14350.9070705@si6networks.com>
In-Reply-To: <50A14350.9070705@si6networks.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: "draft-gont-intarea-obsolete-eid-option.all@tools.ietf.org" <draft-gont-intarea-obsolete-eid-option.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-gont-intarea-obsolete-eid-option-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, 12 Nov 2012 19:29:41 -0000

Thank you!

-----Original Message-----
From: Fernando Gont [mailto:fgont@si6networks.com]=20
Sent: Monday, November 12, 2012 1:43 PM
To: Moriarty, Kathleen
Cc: gen-art@ietf.org; draft-gont-intarea-obsolete-eid-option.all@tools.ietf=
.org; iesg@ietf.org
Subject: Re: Gen-art review of draft-gont-intarea-obsolete-eid-option-01

HI, Kathleen,

Thnas so much for your feedback. Please find my responses in-line...

On 10/25/2012 05:36 PM, Moriarty, Kathleen wrote:
> Summary:  The document needs a few small revisions. This document
> formally deprecates the IPv6 Endpoint Identification (EID) option
> (hex value 0x8a).

FWIW, I'll update the title to note that this in an IPv6 option.



> Major issues:
>=20
> Minor issues: RFC2119 is referenced, but not used.  I don't see the
> use of any RFC2119 language in the document, so it may be safe to
> remove this reference.

Will do.



> I don't think the reference for EID option is valid.  I also looked
> at the reference in the IANA page and that no longer contains a link.
> From a google search, it looks like this was an internet draft that
> was never published as an RFC and expired,
> http://ana-3.lcs.mit.edu/~jnc/nimrod/eidoption.txt Listing it as "A
> work in progress" when it is an expired draft s not appropriate.

Ok, I will update this references as indicated.



> Nits/editorial comments:
>=20
> I recommend changing the following portion of the abstract to state
> what is accomplished in this draft as the language is a little
> confusing: "possibly serving as a basis for providing advice" Since
> this draft doesn't actually provide the advice, just says it may
> provide a basis for providing the advice, I would recommend leaving
> this out of the abstract.

I've already applied such change -- thanks!



> Recommend removing "e.g." fromt he last sentence int he Security
> Considerations section as it is not needed. Change from: "However,
> formally deprecating this option may serve as a basis for e.g.
> providing advice about filtering packets containing such option (in a
> similar way to [I-D.ietf-opsec-ip-options-filtering] for the IPv4
> case)." TO: "However, formally deprecating this option may serve as a
> basis for providing advice about filtering packets containing such
> option (in a similar way to [I-D.ietf-opsec-ip-options-filtering] for
> the IPv4 case)."

I've removed such sentence altogether, upon suggestion by Wes Eddy.

Thanks!

Best regards,
--=20
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492






From fgont@si6networks.com  Mon Nov 12 10:43:51 2012
Return-Path: <fgont@si6networks.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 946E521F8790; Mon, 12 Nov 2012 10:43:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UpIDCMdGwpQR; Mon, 12 Nov 2012 10:43:50 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [93.186.182.34]) by ietfa.amsl.com (Postfix) with ESMTP id 967E421F878E; Mon, 12 Nov 2012 10:43:50 -0800 (PST)
Received: from [186.134.15.187] (helo=[192.168.123.122]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1TXyz3-0001sp-C6; Mon, 12 Nov 2012 19:43:45 +0100
Message-ID: <50A14350.9070705@si6networks.com>
Date: Mon, 12 Nov 2012 15:43:28 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
References: <182B306DD37FAD4882AB1C1EBE2CA9020DCDDF9129@MX15A.corp.emc.com>
In-Reply-To: <182B306DD37FAD4882AB1C1EBE2CA9020DCDDF9129@MX15A.corp.emc.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 12 Nov 2012 11:31:19 -0800
Cc: "draft-gont-intarea-obsolete-eid-option.all@tools.ietf.org" <draft-gont-intarea-obsolete-eid-option.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-gont-intarea-obsolete-eid-option-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, 12 Nov 2012 18:43:51 -0000

HI, Kathleen,

Thnas so much for your feedback. Please find my responses in-line...

On 10/25/2012 05:36 PM, Moriarty, Kathleen wrote:
> Summary:  The document needs a few small revisions. This document
> formally deprecates the IPv6 Endpoint Identification (EID) option
> (hex value 0x8a).

FWIW, I'll update the title to note that this in an IPv6 option.



> Major issues:
> 
> Minor issues: RFC2119 is referenced, but not used.  I don't see the
> use of any RFC2119 language in the document, so it may be safe to
> remove this reference.

Will do.



> I don't think the reference for EID option is valid.  I also looked
> at the reference in the IANA page and that no longer contains a link.
> From a google search, it looks like this was an internet draft that
> was never published as an RFC and expired,
> http://ana-3.lcs.mit.edu/~jnc/nimrod/eidoption.txt Listing it as "A
> work in progress" when it is an expired draft s not appropriate.

Ok, I will update this references as indicated.



> Nits/editorial comments:
> 
> I recommend changing the following portion of the abstract to state
> what is accomplished in this draft as the language is a little
> confusing: "possibly serving as a basis for providing advice" Since
> this draft doesn't actually provide the advice, just says it may
> provide a basis for providing the advice, I would recommend leaving
> this out of the abstract.

I've already applied such change -- thanks!



> Recommend removing "e.g." fromt he last sentence int he Security
> Considerations section as it is not needed. Change from: "However,
> formally deprecating this option may serve as a basis for e.g.
> providing advice about filtering packets containing such option (in a
> similar way to [I-D.ietf-opsec-ip-options-filtering] for the IPv4
> case)." TO: "However, formally deprecating this option may serve as a
> basis for providing advice about filtering packets containing such
> option (in a similar way to [I-D.ietf-opsec-ip-options-filtering] for
> the IPv4 case)."

I've removed such sentence altogether, upon suggestion by Wes Eddy.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From ben@nostrum.com  Mon Nov 12 13:48:19 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF40921F8614; Mon, 12 Nov 2012 13:48:19 -0800 (PST)
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 DVtdDy3PXS8X; Mon, 12 Nov 2012 13:48:13 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DEC3921F85EA; Mon, 12 Nov 2012 13:48:12 -0800 (PST)
Received: from [10.12.11.26] ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qACLmBlo077546 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 12 Nov 2012 15:48:12 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Nov 2012 15:48:11 -0600
Message-Id: <F8E095B8-9E98-4986-80B5-7C498BC07733@nostrum.com>
To: "<draft-ietf-mptcp-api.all@tools.ietf.org>" <draft-ietf-mptcp-api.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-mptcp-api-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 21:48:19 -0000

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

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

Document: draft-ietf-mptcp-api-06
Reviewer: Ben Campbell=09
Review Date: 2012-11-12
IESG Telechat date: 2012-11-15

Summary: This draft is basically ready for publication as an =
informational RFC. All of the comments from my Gen-ART review of version =
05 at IETF last call have been dealt with to my satisfaction in the =
draft or in email, save the one minor issue below.

Major issues:

Minor issues:

I made the following comment at last call. It's not a show stopper, but =
I think it should be considered:

> -- It seems like at least passing knowledge of the sockets API is =
needed to understand this document. I'm curious why the POSIX reference =
is informational rather than normative?

The authors indicated they believed the reference at the end of =
paragraph 3 of section 1 to be truly informational. However, I called =
out an mention at the beginning of the same paragraph that should have =
included a citation, and that I thought that citation would justify a =
normative reference. The authors added the citation in version 06, but =
the reference is still informational.


Nits/editorial comments:

IDNits reports that "A later version (-12) exists of
     draft-ietf-mptcp-multiaddressed-09"


From ben@nostrum.com  Mon Nov 12 14:05:55 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FED421F8578; Mon, 12 Nov 2012 14:05:55 -0800 (PST)
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 EQUwJoX5Os-e; Mon, 12 Nov 2012 14:05:54 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 46BC221F8580; Mon, 12 Nov 2012 14:05:53 -0800 (PST)
Received: from [10.12.11.26] ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qACM5k6s079224 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 12 Nov 2012 16:05:46 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <8414B0C3-C97E-4A1A-8F21-6387E85C8D84@nostrum.com>
Date: Mon, 12 Nov 2012 16:05:46 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <B46696E7-0199-48D6-B8BC-81BE4F35474C@nostrum.com>
References: <8414B0C3-C97E-4A1A-8F21-6387E85C8D84@nostrum.com>
To: draft-leiba-extended-doc-shepherd.all@tools.ietf.org
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review of draft-leiba-extended-doc-shepherd-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 22:05:55 -0000

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

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

Document: draft-leiba-extended-doc-shepherd-01
Reviewer: Ben Campbell=09
Review Date: 2012-11-12
IESG Telechat date: 2012-11-15

Summary: I have mixed feelings about this draft being published as an =
IETF stream RFC in it's current form.

Major issues:

This draft is not substantially changed since my Gen-ART review of =
version 00 at last call. I've copied that review in it's entirety below. =
There is a new section indicating that the ideas herein should be =
adapted to the circumstances. This helps, but I think my original =
comments still stand.

I am sympathetic to Adrian Farrel's DISCUSS position as updated on =
2012-11-05. OTOH, it seems like there should be a place to capture this =
sort of opinion document, and it's a bit large and involved to simply =
send to a mailing list for discussion.

On Oct 23, 2012, at 5:07 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document:  draft-leiba-extended-doc-shepherd-00
>=20
> Reviewer: Ben Campbell
> Review Date: 2012-10-23
> IETF LC End Date: 2012-10-23
>=20
> Summary: I'm not sure what to make of this draft. I think the opinions =
herein are worth capturing, but have mixed feelings about it belong in =
an informational RFC.
>=20
> Major issues:
>=20
> -- Process: I share some of the concerns that have been mentioned by =
others, namely that I'm not sure whether an individual opinion paper =
should be published as an informational RFC. OTOH, I'm not sure that it =
shouldn't. The operative words here are "I'm not sure." The opinions =
contained in the document are interesting, and likely of use to the =
community. I just wonder if another publication form might not be more =
appropriate.
>=20
> -- Content: It's hard to disagree with most of the activities in =
general, but it seems to me that much of the pre pubreq processes here =
are just things that Chairs should be doing anyway. I guess it doesn't =
hurt to call all of that "shepherding", but I don't think it's the same =
thing as "having a shepherd" in the PROTO sense.  I see the potential =
value of having continuity of responsibility throughout the entire =
process, but I also see value in the flexibility of deferring the =
shepherd selection until time for the proto writeup. (I recognize that =
you don't necessarily expect the same person to shepherd all phases--but =
if I read correctly you also seem to indicate a preference that they do =
so.)
>=20
> Minor issues:
>=20
> -- section 1, 4th paragraph: "It adds to what=92s in RFC 4858, =
intending to extend it, not replace it."
>=20
> Do you intend this to formally update 4858? It doesn't seem like it =
from the rest of the text, but one might infer otherwise from this =
sentence.
>=20
> -- section 4, 2nd paragraph: "... What it all boils down to is setting =
up one person who takes responsibility for following the progress of a =
document from Call for Adoption through Publication ..."
>=20
> The text offers examples of changing the responsible person during the =
process, but also mentions the advantages of continuity. If continuity =
is the real goal, then are the examples that show the role changing over =
the life of the draft are counterproductive?
>=20
>=20
> Nits/editorial comments:
>=20
> None.


From suresh.krishnan@ericsson.com  Tue Nov 13 16:07:59 2012
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCDF21F8684 for <gen-art@ietfa.amsl.com>; Tue, 13 Nov 2012 16:07:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MWeH1arIP+Nz for <gen-art@ietfa.amsl.com>; Tue, 13 Nov 2012 16:07:58 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3083D21F8679 for <gen-art@ietf.org>; Tue, 13 Nov 2012 16:07:53 -0800 (PST)
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 qAE0Dwh1029734; Tue, 13 Nov 2012 18:13:59 -0600
Received: from [142.133.194.42] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 13 Nov 2012 19:07:46 -0500
Message-ID: <50A2E0D1.5080301@ericsson.com>
Date: Tue, 13 Nov 2012 19:07:45 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: "draft-ietf-dnsext-rfc2671bis-edns0.all@tools.ietf.org" <draft-ietf-dnsext-rfc2671bis-edns0.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-dnsext-rfc2671bis-edns0-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, 14 Nov 2012 00:07: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
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-dnsext-rfc2671bis-edns0-09.txt
Reviewer: Suresh Krishnan
Review Date: 2012/11/13
IESG Telechat date: 2012/11/15

Summary: This draft has addressed all my comments on the -08 version and
is ready for publication as a Standard.

Thanks
Suresh



From suresh.krishnan@ericsson.com  Wed Nov 14 04:33:38 2012
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 102C221F85ED for <gen-art@ietfa.amsl.com>; Wed, 14 Nov 2012 04:33:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PguhkQheM8zD for <gen-art@ietfa.amsl.com>; Wed, 14 Nov 2012 04:33:37 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3A8DD21F84EC for <gen-art@ietf.org>; Wed, 14 Nov 2012 04:33:37 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id qAECXZ2f001090 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 14 Nov 2012 06:33:36 -0600
Received: from [164.48.125.25] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.32) with Microsoft SMTP Server (TLS) id 8.3.279.1; Wed, 14 Nov 2012 07:33:35 -0500
Message-ID: <50A38F97.208@ericsson.com>
Date: Wed, 14 Nov 2012 07:33:27 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: <draft-ietf-mpls-mldp-in-band-signaling.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-mpls-mldp-in-band-signaling-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 12:33:38 -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-mpls-mldp-in-band-signaling-07.txt
Reviewer: Suresh Krishnan
Review Date: 2012/11/13
IESG Telechat date: 2012/11/15

Summary: This draft is ready for publication as a Proposed Standard but
there are some minor comments that you may wish to address.

* Minor

The draft has the pre-5378 boilerplate but it is unclear to me why. I
went through the older versions to find draft-wijnands but that was
submitted first in 2009. Is this really necessary?

* Typos

Section 1.2

s/indentifying/identifying/

Section 2

s/particlar/particular/

Section 2.3

s/speccial/special/
s/nessesary/necessary/

Section 6
s/Adrial Farrel/Adrian Farrel/

Thanks
Suresh



From ben@nostrum.com  Wed Nov 14 15:39:47 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 524A521F8660; Wed, 14 Nov 2012 15:39:47 -0800 (PST)
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 OGeYkFykbtEv; Wed, 14 Nov 2012 15:39:46 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 60E8721F8651; Wed, 14 Nov 2012 15:39:46 -0800 (PST)
Received: from [10.12.11.26] ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qAENddqH070040 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 14 Nov 2012 17:39:41 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Wed, 14 Nov 2012 17:39:39 -0600
Message-Id: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com>
To: draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-karp-routing-tcp-analysis-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: Wed, 14 Nov 2012 23:39:47 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-ietf-karp-routing-tcp-analysis-05.txt
Reviewer: Ben Campbell
Review Date: 2012-11-14
IETF LC End Date: 2012-11-19

Summary: This draft is almost ready for publication as an informational =
RFC. There are a few minor issues and a number of editorial issues that =
should be considered prior to publication.

*** Major issues ***:

None

*** Minor issues *** :

-- section 2.2, last paragraph:

The IKE mention lacks context. Do you mean to suggest IKE with IPSec? I =
assume so, but there's been no mention of IPSec so far.

-- section 2.3.2:

It would be helpful for this section to describe whether privacy issues =
actually matter or not, rather than just stating the issues to be =
similar to those for other routing protocols.

-- section 3.1, 2nd paragraph:

Does this mean that privacy is really not needed, or just that LDP does =
not state a requirement for privacy?

-- Section 6 (Security Considerations), 4th paragraph:

If replay protection is required, shouldn't the draft discuss the =
details somewhere? I see only one mention in passing outside of this =
section.

*** Nits/editorial comments ***:

-- IDNits indicates some unused and obsoleted references. Please check.

-- The IANA considerations section is missing. If the draft makes =
requests of IANA, it should include the section and state that.

-- the short title is "The IANA considerations section is missing. If =
the draft makes requests of IANA, it should include the section and say =
that

-- The short title is "draft-ietf-karp-routing-tcp-analysis-05.txt". Is =
this draft in any way specific to TCP? If so, it would be helpful to =
mention that in the abstract and introduction.

-- Punctuation errors are pervasive, particularly in the early and late =
sections. These make it harder to read than it needs to be. In =
particular, I suggest the draft be proofread for missing commas and =
missing quotes (or other marks) around document titles.

-- Section 1, paragraph 1:

The cited doc name should be quoted, or otherwise marked. Also, it's not =
necessary to put the full reference here, since you are citing the =
references section.

-- Section 1, paragraph 1: "Four main steps were identified for that =
tightening:"

For what tightening? This is the first mention. Perhaps the previous =
sentence should have gone on to say "... and suggests steps to tighten =
the infrastructure against the attack"?

-- section 1, 1st paragraph after numbered list:

The end of the paragraph does not seem related to the beginning. I =
suggest a paragraph split before the sentence starting with "The OPSEC =
working group..."=20

-- section 1, 2nd to last paragraph: "current state of security method"

Missing article before "security method".

-- section 1.1:

Why is 2119 language needed? I see two potentially normative =
statements--but both of those merely describe the existing MAC =
requirements in TCP-AO. It would be better to state those in descriptive =
language (e.g. TCP-AO requires=85) and to drop the 2119 section =
entirely.=20

-- section 2.1,  5th paragraph:

A mention of SHA1 seems needed here. Section 2.3.1.2 states the concerns =
about TCP-md5 more clearly.

-- section 2.3.1.2, 1st paragraph: "As stated above..."

A section reference would be helpful.

-- section 4, 2nd paragraph: "In addition Improving TCP=92s Robustness =
to Blind In-Window Attacks."

sentence fragment.

-- section 4, 3rd paragraph:

It would have been helpful to mention the MKT manual config issue back =
in the "state of the security method" sections.



From jmh@joelhalpern.com  Wed Nov 14 16:14:28 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AF3921F874A for <gen-art@ietfa.amsl.com>; Wed, 14 Nov 2012 16:14:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[AWL=0.000, 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 NLTwUoRaQmSq for <gen-art@ietfa.amsl.com>; Wed, 14 Nov 2012 16:14:27 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id A59A821F8701 for <gen-art@ietf.org>; Wed, 14 Nov 2012 16:14:27 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id CBB92557FEF for <gen-art@ietf.org>; Wed, 14 Nov 2012 16:14:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 516851C074F; Wed, 14 Nov 2012 16:14:25 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-52-236.clppva.btas.verizon.net [71.161.52.236]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 5433D1C0540; Wed, 14 Nov 2012 16:14:24 -0800 (PST)
Message-ID: <50A433DC.1000801@joelhalpern.com>
Date: Wed, 14 Nov 2012 19:14:20 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
References: <20121114224037.7641.59220.idtracker@ietfa.amsl.com>
In-Reply-To: <20121114224037.7641.59220.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20121114224037.7641.59220.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ron Bonica <rbonica@juniper.net>, General Area Review Team <gen-art@ietf.org>, Al Morton <acmorton@att.com>, draft-ietf-bmwg-protection-meth.all@tools.ietf.org
Subject: [Gen-art] Fwd: I-D Action: draft-ietf-bmwg-protection-meth-13.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 00:14:28 -0000

These changes sufficiently address my concerns.
Thank you,
Joel


-------- Original Message --------
Subject: I-D Action: draft-ietf-bmwg-protection-meth-13.txt
Date: Wed, 14 Nov 2012 14:40:37 -0800
From: internet-drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org
CC: bmwg@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
  This draft is a work item of the Benchmarking Methodology Working 
Group of the IETF.

	Title           : Methodology for Benchmarking MPLS-TE Fast Reroute 
Protection
	Author(s)       : Rajiv Papneja
                           Samir Vapiwala
                           Jay Karthik
                           Scott Poretsky
                           Shankar Rao
                           JL. Le Roux
	Filename        : draft-ietf-bmwg-protection-meth-13.txt
	Pages           : 35
	Date            : 2012-11-14

Abstract:
    This draft describes the methodology for benchmarking MPLS Fast
    Reroute (FRR) protection mechanisms for link and node protection.
    This document provides test methodologies and testbed setup for
    measuring failover times of Fast Reroute techniques while considering
    factors (such as underlying links) that might impact
    recovery times for real-time applications bound to MPLS traffic
    engineered (MPLS-TE) tunnels.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bmwg-protection-meth

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-bmwg-protection-meth-13

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-bmwg-protection-meth-13


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt




From Francis.Dupont@fdupont.fr  Thu Nov 15 06:12:26 2012
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D72821F8568 for <gen-art@ietfa.amsl.com>; Thu, 15 Nov 2012 06:12:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[AWL=0.997,  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 9tv4jiosJAXR for <gen-art@ietfa.amsl.com>; Thu, 15 Nov 2012 06:12:26 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id A6D6A21F8577 for <gen-art@ietf.org>; Thu, 15 Nov 2012 06:12:25 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id qAFECNQF075518 for <gen-art@ietf.org>; Thu, 15 Nov 2012 15:12:24 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201211151412.qAFECNQF075518@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Thu, 15 Nov 2012 15:12:23 +0100
Sender: Francis.Dupont@fdupont.fr
Subject: [Gen-art] postpone draft-ietf-v6ops-ra-guard-implementation review
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 15 Nov 2012 14:12:26 -0000

A new version was published some hours ago and already received comments
in the mailing list... so I decided to postpone the review of the last
version (or the next one? :-) and to downgrade the status from Ready
(there were only editiorial comments about 04 version (last is 07))
to On the right track to get some time (including for the IESG).

Regards

Francis.Dupont@fdupont.fr

From mahoney@nostrum.com  Thu Nov 15 14:26:24 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E6E321F853B for <gen-art@ietfa.amsl.com>; Thu, 15 Nov 2012 14:26:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fh1cXL800xUm for <gen-art@ietfa.amsl.com>; Thu, 15 Nov 2012 14:26:23 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0F05521F8A3B for <gen-art@ietf.org>; Thu, 15 Nov 2012 14:26:17 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qAFMQHpZ004317 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 15 Nov 2012 16:26:17 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50A56C09.3030304@nostrum.com>
Date: Thu, 15 Nov 2012 16:26:17 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-11-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 22:26:24 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Francis Dupont    2012-11-26    draft-ietf-ppsp-problem-statement-11 **

Mary Barnes       2012-11-26    draft-ietf-netext-pmipv6-sipto-option-07

Martin Thomson    2012-11-26    draft-ietf-6man-uri-zoneid-05

Meral Shirazipour 2012-11-27    draft-ietf-lisp-eid-block-03

Peter McCann      2012-11-29    draft-ietf-softwire-6rd-radius-attrib-07 *
  
* on the 2012-11-29 telechat
** 2nd LC

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

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


The standard template is included below.

Thanks,

Jean

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mary.ietf.barnes@gmail.com  Fri Nov 16 11:12:16 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA96F21F8A67 for <gen-art@ietfa.amsl.com>; Fri, 16 Nov 2012 11:12:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.422
X-Spam-Level: 
X-Spam-Status: No, score=-103.422 tagged_above=-999 required=5 tests=[AWL=0.176, 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 5Arg4d6x5ymr for <gen-art@ietfa.amsl.com>; Fri, 16 Nov 2012 11:12:15 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADB021F8516 for <gen-art@ietf.org>; Fri, 16 Nov 2012 11:12:14 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so2510729lah.31 for <gen-art@ietf.org>; Fri, 16 Nov 2012 11:12:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=mXZ7v73r2AgMMkBICJsyhkMA3ItkgM+t0r5NzdzF9Lo=; b=0hB0WNYezdGi9RsRYuHVwff7P7v+/2AVTvc2sCROSuWychITT9C8dYlz/fnQEb7QcQ 8oPQUeV1f0HFneX3eJWHoZCjQRUPw69rn4CRZnCs8/Frmn9n1DxYhkY5+zEEh/OGd+6d gU9+3b/60eQVlBv/S0hZ0/iicNrDjTl2dwUETgA9k5gV2Ar1SQfbdV8uDeMZUxNdoNIn z1US3CbK3dVwxv+C9T54D11yRhSH0MbdPkXHXEzphI59RZU3khimv2iFBfRIY246TPeN Kd2gsHVZ3Pk2D4/wXKC2JZE+ptGRdAnz7og/aAXcOYVrfPehZJO9VTTqavp8NXSFkf44 IpBg==
MIME-Version: 1.0
Received: by 10.112.16.106 with SMTP id f10mr679632lbd.1.1353093133910; Fri, 16 Nov 2012 11:12:13 -0800 (PST)
Received: by 10.114.69.139 with HTTP; Fri, 16 Nov 2012 11:12:13 -0800 (PST)
Date: Fri, 16 Nov 2012 13:12:13 -0600
Message-ID: <CAHBDyN7u_vqiFAZkpgwt=Oc6PumjRJW3fvnHcidnPQqP7vdkjA@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-netext-pmipv6-sipto-option.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=f46d040167819842f304cea18bcb
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review: draft-ietf-netext-pmipv6-sipto-option-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 19:12:17 -0000

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

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-netext-pmipv6-sipto-option-07.txt
Reviewer:  Mary Barnes
Review Date:  16 Nov 2012
IETF LC End Date: 26 Nov 2012

Summary:  Almost Ready - comments/nits.

Minor comments/nits:
--------------------------

Section 1:
- 2nd paragraph
   I don't quite understand the intent of this sentence:
   "Example of such non-essential
   traffic is entirely a policy decision."
   I think you're trying to say that "It's a policy decision as to which
   traffic an operator deems as non-essential."
- 3rd paragraph
   I'm not quite sure what is "it" in the last clause in this sentence
below. Is the "it" the mobile node or the access network?  The "it" should
be replaced with whichever for readability.  Also, adding a "," before the
"which" might help as well.

   "If there is
   proper prefix coloring marking in the Router Advertisement messages
   which allows the mobile node to identify the IPv6 prefix assigned
   from the local access network, it can choose to use an address from
   that prefix for IP traffic flows that require offload."

Section 2:
- 1st paragraph:  "abbreviations" should be "terms".
- It also seems to me that this document doesn't need to define NAT unless
the term is being used in a manner different from the usual meaning. I
think a reference to RFC 2633 at the first usage of NAT would be sufficient.

Section 3:
- 1st paragraph - this sentence needs some fixes:
OLD:
   It is possible, the NAT function is co-located with
   the mobile access gateway, or its located some where in the edge of
   the access network.
NEW:
   It is possible for the NAT function to be co-located with
   the mobile access gateway or located somewhere in the edge of
   the access network.
 - 1st paragraph: "collacted" -> "co-located"

Section 3.2:
- 1st sub-bullet in the second bullet.
I'm not sure what this is trying to say.  Maybe the following change would
help.
OLD:
         Including the IPv4 Traffic Offload
         Selector option in the Proxy Binding Update, but without the
         Traffic Selector Sub-option serves as an indication that the
         mobile access gateway is not proposing any specific offload
         policy for that mobility session, but a request to the local
         mobility anchor to provide the IPv4 traffic offload flow
         selectors for that mobility session.
NEW:
         Including the IPv4 Traffic Offload
         Selector option in the Proxy Binding Update without the
         Traffic Selector Sub-option serves as an indication that the
         mobile access gateway is not proposing any specific offload
         policy for that mobility session, but rather it indicates
         a request to the local
         mobility anchor to provide the IPv4 traffic offload flow
         selectors for that mobility session.

- 2nd sub-bullet in the second bullet, 3rd sentence. I'm not sure what "In
that scenario" is referring to in this sentence:
         In that scenario, the Traffic Selector
         sub-option MUST be present in the IPv4 Traffic Offload Selector
         option (Section 4).
The previous sentence talks about two ways in which the policy may be
configured. Is it referring to one of those specific ways or is it
referring to the 1st sentence - i.e., In the case that the MAG includes its
proposed policy?

- 3rd bullet, 1st sentence - not clear.  Does the following reflect the
intent?
OLD:
      If there is no IPv4 Traffic Offload Selector option in the
      corresponding Proxy Binding Acknowledgement message, that the
      mobile access gateway receives in response to a Proxy Binding
      Update, it serves as an indication that the local mobility anchor
      did not enable IPv4 Traffic Offload support for that mobility
      session, and hence the local mobility anchor did not deliver IPv4
      flow selectors for that mobility session.

NEW:
      Lack of a IPv4 Traffic Offload Selector option in the
      corresponding Proxy Binding Acknowledgement message received by the
      mobile access gateway in response to a Proxy Binding
      Update indicates that the local mobility anchor
      did not enable IPv4 Traffic Offload support for that mobility
      session, and hence the local mobility anchor did not deliver IPv4
      flow selectors for that mobility session.

5th bullet: This one very long sentence needs some work for clarity with
one suggestion below (if I've interpreted the intent correctly):
OLD:
      If configuration variable, EnableIPTrafficOffloadSupport is set to
      a value of (0), and if the mobile access gateway has not included
      the IPv4 Traffic Offload Selector option in the Proxy Binding
      Update, but if the received Proxy Binding Acknowledgement message
      has the IPv4 Traffic Offload Selector option, then the mobile
      access gateway SHOULD ignore the option and process the rest of
      the message as per [RFC5213].
NEW:
      If the configuration variable EnableIPTrafficOffloadSupport
      is set to a value of (0) and the mobile access gateway has not
      included the IPv4 Traffic Offload Selector option in the Proxy
      Binding Update, but has received a Proxy Binding
      Acknowledgement message that has the IPv4 Traffic Offload Selector
      option, then the mobile access gateway SHOULD ignore the option
      and process the rest of the message as per [RFC5213].

- Traffic Selector Sub-option. It's not clear what this sentence is trying
to say:
      "This is an optional
      field when this option is used only a capability hint."
What is a "capability hint"?  That's not mentioned elsewhere in this
document. Also the phrase "is used only a" doesn't make sense.  Should it
be "is used only as a"?

IANA considerations:
- I could not find a definition of a "mobility header option" in RFC 6275.
I believe you are wanting to update the "Mobility Options" registry:
http://www.iana.org/assignments/mobility-parameters/mobility-parameters.xml#mobility-parameters-2
So, really, you are defining a new "Option Type" in the "Mobility Options"
namespace.  Is that correct?

- Note, you also should add a note to section 4 that the RFC editor should
replace <IANA-1> with the number that gets assigned.

Section 6:
- 1st paragraph, 1st sentence: "that control" -> "that controls"

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

<div><br></div><div>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.too=
ls.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/g=
en/trac/wiki/GenArtfaq</a>&gt;.</div>
<div><br></div><div>Please resolve these comments along with any other Last=
 Call comments=A0you may receive.</div><div><br></div><div>Document: draft-=
ietf-netext-pmipv6-sipto-option-07.txt</div><div>Reviewer: =A0Mary Barnes=
=A0</div>
<div>Review Date: =A016 Nov 2012</div><div>IETF LC End Date: 26 Nov 2012</d=
iv><div><br></div><div>Summary: =A0Almost Ready - comments/nits.</div><div>=
<br></div><div>Minor comments/nits:=A0</div><div>--------------------------=
</div>
<div><br></div><div>Section 1:</div><div>- 2nd paragraph =A0=A0</div><div>=
=A0 =A0I don&#39;t quite understand the intent of this sentence: =A0</div><=
div>=A0 =A0&quot;Example of such non-essential</div><div>=A0 =A0traffic is =
entirely a policy decision.&quot;</div>
<div>=A0 =A0I think you&#39;re trying to say that &quot;It&#39;s a policy d=
ecision as to which</div><div>=A0 =A0traffic an operator deems as non-essen=
tial.&quot;=A0</div><div>- 3rd paragraph</div><div>=A0 =A0I&#39;m not quite=
 sure what is &quot;it&quot; in the last clause in this sentence below. Is =
the &quot;it&quot; the mobile node or the access network? =A0The &quot;it&q=
uot; should be replaced with whichever for readability. =A0Also, adding a &=
quot;,&quot; before the &quot;which&quot; might help as well.=A0</div>
<div>=A0</div><div>=A0 =A0&quot;If there is</div><div>=A0 =A0proper prefix =
coloring marking in the Router Advertisement messages</div><div>=A0 =A0whic=
h allows the mobile node to identify the IPv6 prefix assigned</div><div>=A0=
 =A0from the local access network, it can choose to use an address from</di=
v>
<div>=A0 =A0that prefix for IP traffic flows that require offload.&quot;</d=
iv><div><br></div><div>Section 2:</div><div>- 1st paragraph: =A0&quot;abbre=
viations&quot; should be &quot;terms&quot;. =A0</div><div>- It also seems t=
o me that this document doesn&#39;t need to define NAT unless the term is b=
eing used in a manner different from the usual meaning. I think a reference=
 to RFC 2633 at the first usage of NAT would be sufficient.</div>
<div><br></div><div>Section 3:</div><div>- 1st paragraph - this sentence ne=
eds some fixes:</div><div>OLD:</div><div>=A0 =A0It is possible, the NAT fun=
ction is co-located with</div><div>=A0 =A0the mobile access gateway, or its=
 located some where in the edge of</div>
<div>=A0 =A0the access network.=A0</div><div>NEW:</div><div>=A0 =A0It is po=
ssible for the NAT function to be co-located with</div><div>=A0 =A0the mobi=
le access gateway or located somewhere in the edge of</div><div>=A0 =A0the =
access network.=A0</div>
<div>=A0- 1st paragraph: &quot;collacted&quot; -&gt; &quot;co-located&quot;=
</div><div><br></div><div>Section 3.2:</div><div>- 1st sub-bullet in the se=
cond bullet.=A0</div><div>I&#39;m not sure what this is trying to say. =A0M=
aybe the following change would help.</div>
<div>OLD:</div><div>=A0 =A0 =A0 =A0 =A0Including the IPv4 Traffic Offload</=
div><div>=A0 =A0 =A0 =A0 =A0Selector option in the Proxy Binding Update, bu=
t without the</div><div>=A0 =A0 =A0 =A0 =A0Traffic Selector Sub-option serv=
es as an indication that the</div>
<div>=A0 =A0 =A0 =A0 =A0mobile access gateway is not proposing any specific=
 offload</div><div>=A0 =A0 =A0 =A0 =A0policy for that mobility session, but=
 a request to the local</div><div>=A0 =A0 =A0 =A0 =A0mobility anchor to pro=
vide the IPv4 traffic offload flow</div>
<div>=A0 =A0 =A0 =A0 =A0selectors for that mobility session. =A0</div><div>=
NEW:=A0</div><div>=A0 =A0 =A0 =A0 =A0Including the IPv4 Traffic Offload</di=
v><div>=A0 =A0 =A0 =A0 =A0Selector option in the Proxy Binding Update witho=
ut the</div><div>=A0 =A0 =A0 =A0 =A0Traffic Selector Sub-option serves as a=
n indication that the</div>
<div>=A0 =A0 =A0 =A0 =A0mobile access gateway is not proposing any specific=
 offload</div><div>=A0 =A0 =A0 =A0 =A0policy for that mobility session, but=
 rather it indicates</div><div>=A0 =A0 =A0 =A0 =A0a request to the local</d=
iv><div>=A0 =A0 =A0 =A0 =A0mobility anchor to provide the IPv4 traffic offl=
oad flow</div>
<div>=A0 =A0 =A0 =A0 =A0selectors for that mobility session.</div><div><br>=
</div><div>- 2nd sub-bullet in the second bullet, 3rd sentence. I&#39;m not=
 sure what &quot;In that scenario&quot; is referring to in this sentence:</=
div><div>
=A0 =A0 =A0 =A0 =A0In that scenario, the Traffic Selector</div><div>=A0 =A0=
 =A0 =A0 =A0sub-option MUST be present in the IPv4 Traffic Offload Selector=
</div><div>=A0 =A0 =A0 =A0 =A0option (Section 4).=A0</div><div>The previous=
 sentence talks about two ways in which the policy may be configured. Is it=
 referring to one of those specific ways or is it referring to the 1st sent=
ence - i.e., In the case that the MAG includes its proposed policy? =A0</di=
v>
<div><br></div><div>- 3rd bullet, 1st sentence - not clear. =A0Does the fol=
lowing reflect the intent?=A0</div><div>OLD:</div><div>=A0 =A0 =A0 If there=
 is no IPv4 Traffic Offload Selector option in the</div><div>=A0 =A0 =A0 co=
rresponding Proxy Binding Acknowledgement message, that the</div>
<div>=A0 =A0 =A0 mobile access gateway receives in response to a Proxy Bind=
ing</div><div>=A0 =A0 =A0 Update, it serves as an indication that the local=
 mobility anchor</div><div>=A0 =A0 =A0 did not enable IPv4 Traffic Offload =
support for that mobility</div>
<div>=A0 =A0 =A0 session, and hence the local mobility anchor did not deliv=
er IPv4</div><div>=A0 =A0 =A0 flow selectors for that mobility session.=A0<=
/div><div><br></div><div>NEW:</div><div>=A0 =A0 =A0 Lack of a IPv4 Traffic =
Offload Selector option in the</div>
<div>=A0 =A0 =A0 corresponding Proxy Binding Acknowledgement message receiv=
ed by the</div><div>=A0 =A0 =A0 mobile access gateway in response to a Prox=
y Binding</div><div>=A0 =A0 =A0 Update indicates that the local mobility an=
chor</div><div>
=A0 =A0 =A0 did not enable IPv4 Traffic Offload support for that mobility</=
div><div>=A0 =A0 =A0 session, and hence the local mobility anchor did not d=
eliver IPv4</div><div>=A0 =A0 =A0 flow selectors for that mobility session.=
=A0</div><div><br>
</div><div>5th bullet: This one very long sentence needs some work for clar=
ity with one suggestion below (if I&#39;ve interpreted the intent correctly=
):</div><div>OLD:</div><div>=A0 =A0 =A0 If configuration variable, EnableIP=
TrafficOffloadSupport is set to</div>
<div>=A0 =A0 =A0 a value of (0), and if the mobile access gateway has not i=
ncluded</div><div>=A0 =A0 =A0 the IPv4 Traffic Offload Selector option in t=
he Proxy Binding</div><div>=A0 =A0 =A0 Update, but if the received Proxy Bi=
nding Acknowledgement message</div>
<div>=A0 =A0 =A0 has the IPv4 Traffic Offload Selector option, then the mob=
ile</div><div>=A0 =A0 =A0 access gateway SHOULD ignore the option and proce=
ss the rest of</div><div>=A0 =A0 =A0 the message as per [RFC5213].</div><di=
v>NEW:</div><div>
=A0 =A0 =A0 If the configuration variable EnableIPTrafficOffloadSupport=A0<=
/div><div>=A0 =A0 =A0 is set to a value of (0) and the mobile access gatewa=
y has not</div><div>=A0 =A0 =A0 included the IPv4 Traffic Offload Selector =
option in the Proxy =A0 =A0</div>
<div>=A0 =A0 =A0 Binding Update, but has received a Proxy Binding =A0 =A0 =
=A0</div><div>=A0 =A0 =A0 Acknowledgement message that has the IPv4 Traffic=
 Offload Selector=A0</div><div>=A0 =A0 =A0 option, then the mobile access g=
ateway SHOULD ignore the option=A0</div>
<div>=A0 =A0 =A0 and process the rest of the message as per [RFC5213].</div=
><div><br></div><div>- Traffic Selector Sub-option. It&#39;s not clear what=
 this sentence is trying to say:</div><div>=A0 =A0 =A0 &quot;This is an opt=
ional</div>
<div>=A0 =A0 =A0 field when this option is used only a capability hint.&quo=
t;</div><div>What is a &quot;capability hint&quot;? =A0That&#39;s not menti=
oned elsewhere in this document. Also the phrase &quot;is used only a&quot;=
 doesn&#39;t make sense. =A0Should it be &quot;is used only as a&quot;?=A0<=
/div>
<div><br></div><div>IANA considerations:</div><div>- I could not find a def=
inition of a &quot;mobility header option&quot; in RFC 6275. I believe you =
are wanting to update the &quot;Mobility Options&quot; registry:</div><div>
<a href=3D"http://www.iana.org/assignments/mobility-parameters/mobility-par=
ameters.xml#mobility-parameters-2">http://www.iana.org/assignments/mobility=
-parameters/mobility-parameters.xml#mobility-parameters-2</a></div><div>So,=
 really, you are defining a new &quot;Option Type&quot; in the &quot;Mobili=
ty Options&quot; namespace. =A0Is that correct? =A0</div>
<div><br></div><div>- Note, you also should add a note to section 4 that th=
e RFC editor should replace &lt;IANA-1&gt; with the number that gets assign=
ed. =A0</div><div><br></div><div>Section 6:</div><div>- 1st paragraph, 1st =
sentence: &quot;that control&quot; -&gt; &quot;that controls&quot;</div>

--f46d040167819842f304cea18bcb--

From martin.thomson@gmail.com  Fri Nov 16 12:22:24 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F00C21F8574 for <gen-art@ietfa.amsl.com>; Fri, 16 Nov 2012 12:22:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.87
X-Spam-Level: 
X-Spam-Status: No, score=-3.87 tagged_above=-999 required=5 tests=[AWL=-0.871,  BAYES_00=-2.599, J_CHICKENPOX_37=0.6, 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 1R7bH0SHN-XJ for <gen-art@ietfa.amsl.com>; Fri, 16 Nov 2012 12:22:23 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6311E21F850E for <gen-art@ietf.org>; Fri, 16 Nov 2012 12:22:23 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so2635084lbk.31 for <gen-art@ietf.org>; Fri, 16 Nov 2012 12:22:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=17UyaEG7aOJo9hkiDyPeM/F9+dBKN1U8wOEOAk2dLRk=; b=qQXW2r8FO/94FYL4a/bl0fpqErdagMgA+Ly7l1+SYStAeiCEkzOMlbe04SZG7oQZ/z 7XIPdtVNvmvfJ+fLUxwjPd7hwJWbqQYfqA2RPtkMZQ8KsoyeDuqf+rI5xGeFDf6NzC3K fOd1/mDuaN7kgh7P7CdyTaUoOu5RRkZUrPhS0JyJXT9dG9R7YJyHTc/x0afVnBZv5vtN 3146FVqmP1QHvM+Y7wFoloKBf88J1H/rWG+g2+ASg9DvKQ+WYcr51+4e1n+joIuk8pl+ Ym0VHM6ZekzXTyUtYPvFMC9hBUGOUsv2TxQfMBnMslVUQpR52uzvTjGwbyfEjCErU7br a92A==
MIME-Version: 1.0
Received: by 10.112.39.105 with SMTP id o9mr2379569lbk.123.1353097341989; Fri, 16 Nov 2012 12:22:21 -0800 (PST)
Received: by 10.112.83.2 with HTTP; Fri, 16 Nov 2012 12:22:21 -0800 (PST)
Date: Fri, 16 Nov 2012 12:22:21 -0800
Message-ID: <CABkgnnVo1LYt=LRbH8dPgaAaCY=GVNARC0y=E6E+bo5G=gNgag@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-6man-uri-zoneid-05.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [Gen-art] Gen-ART review of draft-ietf-6man-uri-zoneid-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 20:22:24 -0000

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

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

Document: draft-ietf-6man-uri-zoneid-05
Reviewer: Martin Thomson
Review Date: 2012-11-16
IETF LC End Date:  2012-11-26
IESG Telechat date: not scheduled

Summary:  This document is ready for publication as Proposed Standard,
with nits.

Nits/editorial comments:

The document could be made shorter by removing:

   We now present the necessary formal syntax.

   The 6man WG discussed and rejected an alternative in which the
   existing syntax of IPv6address would be extended by an option to add
   the ZoneID only for the case of link-local addresses.  It was felt
   that the present solution offers more flexibility for future uses and
   is more straightforward to implement.

This latter text might be put in the appendix, if it is necessary at
all.  The text in the security considerations is probably adequate.

The following statement implies "special" processing for zone IDs at user input:

   This document implies that all browsers should recognise a ZoneID
   preceded by an escaped "%".  In the spirit of "be liberal with what
   you accept", we also recommend that URI parsers accept bare "%" signs
   (i.e., a "%" not followed by two valid hexadecimal characters).  This
   makes it easy for a user to copy and paste a string such as
   "fe80::a%en1" from the output of a "ping" command and have it work.

Even though 01 is " two valid hexadecimal characters", U+01 is not a
valid URI character at that position.  Thus, the range of inferred
zone IDs is (potentially) larger than the text implies.

Browsers frequently accept (and display) URIs with unescaped parts.
This is just another example of that common logic.  Thus, this might
be phrased more simply as:

   Software that accepts URIs with unescaped portions can permit the
   entry of IPv6 addresses with an unescaped zone separator.

This allows implementations to infer behaviour, which is probably OK
in this context.

s/proxy/intermediary/

In the appendix, it might be worth noting that option 3 was selected.

From martin.thomson@gmail.com  Fri Nov 16 13:28:18 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBF3221F8B16 for <gen-art@ietfa.amsl.com>; Fri, 16 Nov 2012 13:28:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.824
X-Spam-Level: 
X-Spam-Status: No, score=-3.824 tagged_above=-999 required=5 tests=[AWL=-0.825, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, 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 YImjW+KFi8p5 for <gen-art@ietfa.amsl.com>; Fri, 16 Nov 2012 13:28:18 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id A84BD21F8B11 for <gen-art@ietf.org>; Fri, 16 Nov 2012 13:28:17 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so2672598lbk.31 for <gen-art@ietf.org>; Fri, 16 Nov 2012 13:28:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ZJ6dYFMRbEYBMiz8jqCgxJU3zwxqRKnlV2GyKpriPzw=; b=ApNslzbNefjlSCyAkJi1ZznyQvVbVwny2TEam3alT02yz3q0G30U9dPWR4jfs0sOG1 nddegzHm9gxKkzyq5dAWblGD21P50yleMOGcciX82+pffr3nXf0FlpcIsbSSI3wpS/Pb 9oK7m11bo3IVmstpEW80mZzVPwv7/HpWc4I3ktJP2EDxyrRdOr47J7Bc/hiXqdekMU9R jj6BzxjNzGy1ZA+9/R+re3XRu3X9CL78jjNRm/KxWPp0tq0aB0wTjicW4zVbBR2UtWIb byH4Nj+OUtd0h0tN9THb5dGhilCMJbzcwerTFkVRIlf3f67I+gpDnp0FeX4SJbOGomON 8hWg==
MIME-Version: 1.0
Received: by 10.152.145.169 with SMTP id sv9mr5550164lab.2.1353101296559; Fri, 16 Nov 2012 13:28:16 -0800 (PST)
Received: by 10.112.83.2 with HTTP; Fri, 16 Nov 2012 13:28:16 -0800 (PST)
In-Reply-To: <CABkgnnVo1LYt=LRbH8dPgaAaCY=GVNARC0y=E6E+bo5G=gNgag@mail.gmail.com>
References: <CABkgnnVo1LYt=LRbH8dPgaAaCY=GVNARC0y=E6E+bo5G=gNgag@mail.gmail.com>
Date: Fri, 16 Nov 2012 13:28:16 -0800
Message-ID: <CABkgnnUgXGhEm6WeVzuYs7ADAQgifkApJe0_JimYde9mK1ARhQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-6man-uri-zoneid.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-6man-uri-zoneid-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 21:28:18 -0000

Try again, this time with the right recipients.

On 16 November 2012 12:22, Martin Thomson <martin.thomson@gmail.com> wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>   <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-6man-uri-zoneid-05
> Reviewer: Martin Thomson
> Review Date: 2012-11-16
> IETF LC End Date:  2012-11-26
> IESG Telechat date: not scheduled
>
> Summary:  This document is ready for publication as Proposed Standard,
> with nits.
>
> Nits/editorial comments:
>
> The document could be made shorter by removing:
>
>    We now present the necessary formal syntax.
>
>    The 6man WG discussed and rejected an alternative in which the
>    existing syntax of IPv6address would be extended by an option to add
>    the ZoneID only for the case of link-local addresses.  It was felt
>    that the present solution offers more flexibility for future uses and
>    is more straightforward to implement.
>
> This latter text might be put in the appendix, if it is necessary at
> all.  The text in the security considerations is probably adequate.
>
> The following statement implies "special" processing for zone IDs at user input:
>
>    This document implies that all browsers should recognise a ZoneID
>    preceded by an escaped "%".  In the spirit of "be liberal with what
>    you accept", we also recommend that URI parsers accept bare "%" signs
>    (i.e., a "%" not followed by two valid hexadecimal characters).  This
>    makes it easy for a user to copy and paste a string such as
>    "fe80::a%en1" from the output of a "ping" command and have it work.
>
> Even though 01 is " two valid hexadecimal characters", U+01 is not a
> valid URI character at that position.  Thus, the range of inferred
> zone IDs is (potentially) larger than the text implies.
>
> Browsers frequently accept (and display) URIs with unescaped parts.
> This is just another example of that common logic.  Thus, this might
> be phrased more simply as:
>
>    Software that accepts URIs with unescaped portions can permit the
>    entry of IPv6 addresses with an unescaped zone separator.
>
> This allows implementations to infer behaviour, which is probably OK
> in this context.
>
> s/proxy/intermediary/
>
> In the appendix, it might be worth noting that option 3 was selected.

From brian.e.carpenter@gmail.com  Sat Nov 17 00:16:35 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A4EC21F8858 for <gen-art@ietfa.amsl.com>; Sat, 17 Nov 2012 00:16:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.27
X-Spam-Level: 
X-Spam-Status: No, score=-101.27 tagged_above=-999 required=5 tests=[AWL=-0.179, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YLcurjgFyMzE for <gen-art@ietfa.amsl.com>; Sat, 17 Nov 2012 00:16:35 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id C03D121F84F9 for <gen-art@ietf.org>; Sat, 17 Nov 2012 00:16:34 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id hm6so362139wib.13 for <gen-art@ietf.org>; Sat, 17 Nov 2012 00:16:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ugVp/08C4NKWPtOkibNwNHDADQMq7zPktZUPmysk3LM=; b=PTGAQxDwS0l4vqdWUVFXz1S2pfJSxSGxAcYIEdSp9mGSUeHOn6BeZUIwzqolstXjCC 6O6eMkxKZ0NuGVEhbONg/cfja39bbkndb1sEHN4pwmFAxWJ8d4OfYbW4rdwHeGj56Txs MtXM10DvDTkU13MvOQSYQh2vn5PVs5eR4qApt951cfEMpHIXKKw2hcYlMId7QSpq8DF/ znIjnIx7PP8CrqaR4ohW2Wf4Z9fCsCiGtZnrAxgF0LjFvMnFfZJ0CsQq1yMJ1P+jgIUb ZqBNb+z81I0UoQhxAbiK/5mWIH4kaxWii5mBs7HuB8dWQy7jFcCVE6D2ScH+ktJJSLGw YIeA==
Received: by 10.216.141.38 with SMTP id f38mr2806962wej.196.1353140193858; Sat, 17 Nov 2012 00:16:33 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-111.as13285.net. [2.102.216.111]) by mx.google.com with ESMTPS id d16sm3848294wiw.8.2012.11.17.00.16.31 (version=SSLv3 cipher=OTHER); Sat, 17 Nov 2012 00:16:32 -0800 (PST)
Message-ID: <50A747F0.2090407@gmail.com>
Date: Sat, 17 Nov 2012 08:16:48 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <CABkgnnVo1LYt=LRbH8dPgaAaCY=GVNARC0y=E6E+bo5G=gNgag@mail.gmail.com> <CABkgnnUgXGhEm6WeVzuYs7ADAQgifkApJe0_JimYde9mK1ARhQ@mail.gmail.com>
In-Reply-To: <CABkgnnUgXGhEm6WeVzuYs7ADAQgifkApJe0_JimYde9mK1ARhQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-6man-uri-zoneid.all@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-6man-uri-zoneid-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Nov 2012 08:16:35 -0000

Martin,

Thanks for the review, comments in-line.

On 16/11/2012 21:28, Martin Thomson wrote:
> Try again, this time with the right recipients.
> 
> On 16 November 2012 12:22, Martin Thomson <martin.thomson@gmail.com> wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>   <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-6man-uri-zoneid-05
>> Reviewer: Martin Thomson
>> Review Date: 2012-11-16
>> IETF LC End Date:  2012-11-26
>> IESG Telechat date: not scheduled
>>
>> Summary:  This document is ready for publication as Proposed Standard,
>> with nits.
>>
>> Nits/editorial comments:
>>
>> The document could be made shorter by removing:
>>
>>    We now present the necessary formal syntax.
>>
>>    The 6man WG discussed and rejected an alternative in which the
>>    existing syntax of IPv6address would be extended by an option to add
>>    the ZoneID only for the case of link-local addresses.  It was felt
>>    that the present solution offers more flexibility for future uses and
>>    is more straightforward to implement.
>>
>> This latter text might be put in the appendix, if it is necessary at
>> all.  The text in the security considerations is probably adequate.

There was quite a lot of discussion of this point in the WG, so
it seems best to record it. I agree it would fite in the appendix.

>>
>> The following statement implies "special" processing for zone IDs at user input:
>>
>>    This document implies that all browsers should recognise a ZoneID
>>    preceded by an escaped "%".  In the spirit of "be liberal with what
>>    you accept", we also recommend that URI parsers accept bare "%" signs
>>    (i.e., a "%" not followed by two valid hexadecimal characters).  This
>>    makes it easy for a user to copy and paste a string such as
>>    "fe80::a%en1" from the output of a "ping" command and have it work.
>>
>> Even though 01 is " two valid hexadecimal characters", U+01 is not a
>> valid URI character at that position.  Thus, the range of inferred

I don't quite understand that. RFC3986 section 2.1 says
  pct-encoded = "%" HEXDIG HEXDIG
with no restrictions on HEXDIG, so why is %01 disallowed?
(I agree it would be meaningless, but that's another matter).

>> zone IDs is (potentially) larger than the text implies.
>>
>> Browsers frequently accept (and display) URIs with unescaped parts.
>> This is just another example of that common logic.  Thus, this might
>> be phrased more simply as:
>>
>>    Software that accepts URIs with unescaped portions can permit the
>>    entry of IPv6 addresses with an unescaped zone separator.
>>
>> This allows implementations to infer behaviour, which is probably OK
>> in this context.

But it's very murky, as per the recent discussion under
"[whatwg] New URL Standard...".

>>
>> s/proxy/intermediary/

proxy or other intermediary?

>> In the appendix, it might be worth noting that option 3 was selected.

OK

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

From martin.thomson@gmail.com  Sun Nov 18 19:25:22 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B95C221F84EC for <gen-art@ietfa.amsl.com>; Sun, 18 Nov 2012 19:25:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.083
X-Spam-Level: 
X-Spam-Status: No, score=-4.083 tagged_above=-999 required=5 tests=[AWL=-0.484, 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 NxqPivw9cjMg for <gen-art@ietfa.amsl.com>; Sun, 18 Nov 2012 19:25:22 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id ED0A821F84EA for <gen-art@ietf.org>; Sun, 18 Nov 2012 19:25:21 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so3634172lbk.31 for <gen-art@ietf.org>; Sun, 18 Nov 2012 19:25:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=I5perplqLYoXxBv0ZnR3VQ/nrImtFHILXsPPiytS6xY=; b=PAxYOUaulfXVc/SsS6x9oeoOCdQTTjO4BgeVToeLPYkWKIIsv2oj3A559Ta3mGT/vC +FVkq4zjHVhn7lqxZWDGcNEtupiZLJHB5kCBIK5xYpjAg8dF28Q0PWibmdBTzlPhMlo5 xIWj0TWkWzPEFZp2hkX8IcO5ssU+puJJog9rMc3EagbaPh4EJJ3fgxIxZfha/ElbJLr3 6Lu2GBhgwLHWf2TWR10QRM0qXzBhTJy9FTxbi1ib0HweRictvrQ4+BlHWWJHJN5pSWOd qfjPV0ur75tVpgOffrf2IZZvDUNVUfrgSYkStZOgoLzH5+TmKg8+yuSVy4+349/zV4J7 1XmQ==
MIME-Version: 1.0
Received: by 10.112.86.104 with SMTP id o8mr4511973lbz.109.1353295520895; Sun, 18 Nov 2012 19:25:20 -0800 (PST)
Received: by 10.112.83.2 with HTTP; Sun, 18 Nov 2012 19:25:20 -0800 (PST)
In-Reply-To: <50A747F0.2090407@gmail.com>
References: <CABkgnnVo1LYt=LRbH8dPgaAaCY=GVNARC0y=E6E+bo5G=gNgag@mail.gmail.com> <CABkgnnUgXGhEm6WeVzuYs7ADAQgifkApJe0_JimYde9mK1ARhQ@mail.gmail.com> <50A747F0.2090407@gmail.com>
Date: Sun, 18 Nov 2012 19:25:20 -0800
Message-ID: <CABkgnnWkKy9bTyXtwubsjM5cd97xeCtPWMVnADOFq6BzWN+R9A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: draft-ietf-6man-uri-zoneid.all@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-6man-uri-zoneid-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2012 03:25:22 -0000

On 17 November 2012 00:16, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> I don't quite understand that. RFC3986 section 2.1 says
>   pct-encoded = "%" HEXDIG HEXDIG
> with no restrictions on HEXDIG, so why is %01 disallowed?
> (I agree it would be meaningless, but that's another matter).

Meaningless is precisely my point.  It's unclear what is exactly the
right behaviour in this situation, so hedging on the vague side,
inadvisable as that normally is, might be safest.

>>> s/proxy/intermediary/
>
> proxy or other intermediary?

Exactly.

From mjethanandani@gmail.com  Sun Nov 18 23:58:40 2012
Return-Path: <mjethanandani@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 6375821F84E8; Sun, 18 Nov 2012 23:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[AWL=-1.150, 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 6eBfwlC3bOiz; Sun, 18 Nov 2012 23:58:39 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 56CA521F8616; Sun, 18 Nov 2012 23:58:39 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so2074484dan.31 for <multiple recipients>; Sun, 18 Nov 2012 23:58:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=M4giSIc/BkvbUrg2BNJmFdxGpyBW2dBCS65v2obv+Jw=; b=P404mYWgADoqfYQubjn9dqwTL6a6xZ24bpniGZB+kLpsZGToB245vkfg0gwI62NjI/ 2f2MkgIHjmYFqGQjW+aVuJ2abYipY2O7+bwYijWnfNNDJxtfP6jY0s/OXrMA3tAmaFj/ Fp0hKQLFpIf8qby0K7Qymjqlk2yHZSoh3ilBbndxAaUlOUecpB5hBMEEJTjY5+LnRGGm JMRjyACpfz/ZBoW2FyJ7MEj+egNs5zsDx2on7dRffYLub56gaLx+o3vMUSYCNEusrszo NTBD+LVqT/f8dDeOX3qx0ZRnHCSyIhCj4ZMLMidGxSw3zeDd4kZ8uFcqr7Z0Vs/EURlk Yfrg==
Received: by 10.66.90.65 with SMTP id bu1mr33679867pab.31.1353311919024; Sun, 18 Nov 2012 23:58:39 -0800 (PST)
Received: from [192.168.1.123] (c-24-6-180-144.hsd1.ca.comcast.net. [24.6.180.144]) by mx.google.com with ESMTPS id l5sm5773034paz.14.2012.11.18.23.58.37 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 18 Nov 2012 23:58:38 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-36--804921993
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com>
Date: Sun, 18 Nov 2012 23:58:36 -0800
Message-Id: <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com>
References: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1085)
Cc: draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-karp-routing-tcp-analysis-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: Mon, 19 Nov 2012 07:58:40 -0000

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


On Nov 14, 2012, at 3:39 PM, Ben Campbell wrote:

> 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>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-karp-routing-tcp-analysis-05.txt
> Reviewer: Ben Campbell
> Review Date: 2012-11-14
> IETF LC End Date: 2012-11-19
>=20
> Summary: This draft is almost ready for publication as an =
informational RFC. There are a few minor issues and a number of =
editorial issues that should be considered prior to publication.
>=20
> *** Major issues ***:
>=20
> None
>=20
> *** Minor issues *** :
>=20
> -- section 2.2, last paragraph:
>=20
> The IKE mention lacks context. Do you mean to suggest IKE with IPSec? =
I assume so, but there's been no mention of IPSec so far.

No. It implies the use of IKEv2 protocol for performing mutual =
authentication and establishing SA. There is no suggestion of using IKE =
with IPSec.

How about this?

For point-to-point key management IKEv2[RFC5996] protocol provides ...


>=20
> -- section 2.3.2:
>=20
> It would be helpful for this section to describe whether privacy =
issues actually matter or not, rather than just stating the issues to be =
similar to those for other routing protocols.

Changed it to:

Labels, like routing information are distributed in the clear. There is =
currently no requirement for labels to be encrypted and that work is =
outside the scope of the KARP working group.

>=20
> -- section 3.1, 2nd paragraph:
>=20
> Does this mean that privacy is really not needed, or just that LDP =
does not state a requirement for privacy?

Further clarified it in this section.

Labels are similar to routing information which is distributed in the =
clear. It is important to ensure that routers exchaning labels are =
mutually authenticated and that there are no rogue peers or =
unauthenticated peers that can compromise the stability of the network. =
However, there is currently no requirement that the labels be encrypted.

>=20
> -- Section 6 (Security Considerations), 4th paragraph:
>=20
> If replay protection is required, shouldn't the draft discuss the =
details somewhere? I see only one mention in passing outside of this =
section.

I have moved the replay protection requirement to the gap analysis =
section.=20

However, this document is a analysis draft, and it is my understanding =
that details on what replay protection methods should be adopted, is =
best left to the routing protocols in question.=20

>=20
> *** Nits/editorial comments ***:
>=20
> -- IDNits indicates some unused and obsoleted references. Please =
check.

Found one unused reference and have removed it.

>=20
> -- The IANA considerations section is missing. If the draft makes =
requests of IANA, it should include the section and state that.

There are no IANA requests. I have gone ahead and added a section on =
IANA considerations and stated none are requested.

>=20
> -- the short title is "The IANA considerations section is missing. If =
the draft makes requests of IANA, it should include the section and say =
that

>=20
> -- The short title is "draft-ietf-karp-routing-tcp-analysis-05.txt". =
Is this draft in any way specific to TCP? If so, it would be helpful to =
mention that in the abstract and introduction.

Done.

>=20
> -- Punctuation errors are pervasive, particularly in the early and =
late sections. These make it harder to read than it needs to be. In =
particular, I suggest the draft be proofread for missing commas and =
missing quotes (or other marks) around document titles.
>=20
> -- Section 1, paragraph 1:
>=20
> The cited doc name should be quoted, or otherwise marked. Also, it's =
not necessary to put the full reference here, since you are citing the =
references section.
>=20
> -- Section 1, paragraph 1: "Four main steps were identified for that =
tightening:"
>=20
> For what tightening? This is the first mention. Perhaps the previous =
sentence should have gone on to say "... and suggests steps to tighten =
the infrastructure against the attack"?

Done.

>=20
> -- section 1, 1st paragraph after numbered list:
>=20
> The end of the paragraph does not seem related to the beginning. I =
suggest a paragraph split before the sentence starting with "The OPSEC =
working group..."=20

Done.

>=20
> -- section 1, 2nd to last paragraph: "current state of security =
method"
>=20
> Missing article before "security method".

Done.

>=20
> -- section 1.1:
>=20
> Why is 2119 language needed? I see two potentially normative =
statements--but both of those merely describe the existing MAC =
requirements in TCP-AO. It would be better to state those in descriptive =
language (e.g. TCP-AO requires=85) and to drop the 2119 section =
entirely.=20

Done.

>=20
> -- section 2.1,  5th paragraph:
>=20
> A mention of SHA1 seems needed here. Section 2.3.1.2 states the =
concerns about TCP-md5 more clearly.

The 6th paragraph states the concern and mentions SHA-1. Did you want =
something more to be included?

>=20
> -- section 2.3.1.2, 1st paragraph: "As stated above..."
>=20
> A section reference would be helpful.

Done.

>=20
> -- section 4, 2nd paragraph: "In addition Improving TCP=92s Robustness =
to Blind In-Window Attacks."
>=20
> sentence fragment.

Changed it to say:

In addition, the recommendations in Improving TCP's Robustness to Blind =
In-Window Attacks

>=20
> -- section 4, 3rd paragraph:
>=20
> It would have been helpful to mention the MKT manual config issue back =
in the "state of the security method" sections.
>=20

Good point. Moved the mention to section 2.2 - Keying issue.

>=20

Mahesh Jethanandani
mjethanandani@gmail.com




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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Nov 14, 2012, at 3:39 PM, Ben Campbell =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>I am the assigned Gen-ART reviewer for this draft. =
For background on<br>Gen-ART, please see the FAQ at<br><br>&lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br><br>Please =
resolve these comments along with any other Last Call comments<br>you =
may receive.<br><br>Document: =
draft-ietf-karp-routing-tcp-analysis-05.txt<br>Reviewer: Ben =
Campbell<br>Review Date: 2012-11-14<br>IETF LC End Date: =
2012-11-19<br><br>Summary: This draft is almost ready for publication as =
an informational RFC. There are a few minor issues and a number of =
editorial issues that should be considered prior to =
publication.<br><br>*** Major issues ***:<br><br>None<br><br>*** Minor =
issues *** :<br><br>-- section 2.2, last paragraph:<br><br>The IKE =
mention lacks context. Do you mean to suggest IKE with IPSec? I assume =
so, but there's been no mention of IPSec so =
far.<br></div></blockquote><div><br></div>No. It implies the use of =
IKEv2 protocol for performing mutual authentication and establishing SA. =
There is no suggestion of using IKE with =
IPSec.</div><div><br></div><div>How about =
this?</div><div><br></div><div><i>For point-to-point key management =
IKEv2[RFC5996] protocol provides =
...</i></div><div><br></div><div><br><blockquote type=3D"cite"><div><br>--=
 section 2.3.2:<br><br>It would be helpful for this section to describe =
whether privacy issues actually matter or not, rather than just stating =
the issues to be similar to those for other routing =
protocols.<br></div></blockquote><div><br></div>Changed it =
to:</div><div><br></div><div><i>Labels, like routing information are =
distributed in the clear. There is currently no requirement for labels =
to be encrypted and that work is outside the scope of the KARP working =
group.</i></div><div><br><blockquote type=3D"cite"><div><br>-- section =
3.1, 2nd paragraph:<br><br>Does this mean that privacy is really not =
needed, or just that LDP does not state a requirement for =
privacy?<br></div></blockquote><div><br></div>Further clarified it in =
this section.</div><div><br></div><div><i>Labels are similar to routing =
information which is distributed in the clear. It is important to ensure =
that routers exchaning labels are mutually authenticated and that there =
are no rogue peers or unauthenticated peers that can compromise the =
stability of the network. However, there is currently no requirement =
that the labels be encrypted.</i></div><div><br><blockquote =
type=3D"cite"><div><br>-- Section 6 (Security Considerations), 4th =
paragraph:<br><br>If replay protection is required, shouldn't the draft =
discuss the details somewhere? I see only one mention in passing outside =
of this section.<br></div></blockquote><div><br></div><div>I have moved =
the replay protection requirement to the gap analysis =
section.&nbsp;</div><div><br></div><div>However, this document is a =
analysis draft, and it is my understanding that details on what replay =
protection methods should be adopted, is best left to the routing =
protocols in question.&nbsp;</div></div><div><br><blockquote =
type=3D"cite"><div><br>*** Nits/editorial comments ***:<br><br>-- IDNits =
indicates some unused and obsoleted references. Please =
check.<br></div></blockquote><div><br></div>Found one unused reference =
and have removed it.</div><div><br><blockquote type=3D"cite"><div><br>-- =
The IANA considerations section is missing. If the draft makes requests =
of IANA, it should include the section and state =
that.<br></div></blockquote><div><br></div>There are no IANA requests. I =
have gone ahead and added a section on IANA considerations and stated =
none are requested.</div><div><br><blockquote type=3D"cite"><div><br>-- =
the short title is "The IANA considerations section is missing. If the =
draft makes requests of IANA, it should include the section and say =
that</div></blockquote></div><div><blockquote type=3D"cite"><div><br>-- =
The short title is "draft-ietf-karp-routing-tcp-analysis-05.txt". Is =
this draft in any way specific to TCP? If so, it would be helpful to =
mention that in the abstract and =
introduction.<br></div></blockquote><br>Done.</div><div><br><blockquote =
type=3D"cite"><div><br>-- Punctuation errors are pervasive, particularly =
in the early and late sections. These make it harder to read than it =
needs to be. In particular, I suggest the draft be proofread for missing =
commas and missing quotes (or other marks) around document =
titles.<br><br>-- Section 1, paragraph 1:<br><br>The cited doc name =
should be quoted, or otherwise marked. Also, it's not necessary to put =
the full reference here, since you are citing the references =
section.<br><br>-- Section 1, paragraph 1: "Four main steps were =
identified for that tightening:"<br><br>For what tightening? This is the =
first mention. Perhaps the previous sentence should have gone on to say =
"... and suggests steps to tighten the infrastructure against the =
attack"?<br></div></blockquote><div><br></div>Done.</div><div><br><blockqu=
ote type=3D"cite"><div><br>-- section 1, 1st paragraph after numbered =
list:<br><br>The end of the paragraph does not seem related to the =
beginning. I suggest a paragraph split before the sentence starting with =
"The OPSEC working group..." =
<br></div></blockquote><div><br></div>Done.</div><div><br><blockquote =
type=3D"cite"><div><br>-- section 1, 2nd to last paragraph: "current =
state of security method"<br><br>Missing article before "security =
method".<br></div></blockquote><div><br></div>Done.</div><div><br><blockqu=
ote type=3D"cite"><div><br>-- section 1.1:<br><br>Why is 2119 language =
needed? I see two potentially normative statements--but both of those =
merely describe the existing MAC requirements in TCP-AO. It would be =
better to state those in descriptive language (e.g. TCP-AO requires=85) =
and to drop the 2119 section entirely. =
<br></div></blockquote><div><br></div>Done.</div><div><br><blockquote =
type=3D"cite"><div><br>-- section 2.1, &nbsp;5th paragraph:<br><br>A =
mention of SHA1 seems needed here. Section 2.3.1.2 states the concerns =
about TCP-md5 more clearly.<br></div></blockquote><div><br></div>The 6th =
paragraph states the concern and mentions SHA-1. Did you want something =
more to be included?</div><div><br><blockquote type=3D"cite"><div><br>-- =
section 2.3.1.2, 1st paragraph: "As stated above..."<br><br>A section =
reference would be =
helpful.<br></div></blockquote><div><br></div>Done.</div><div><br><blockqu=
ote type=3D"cite"><div><br>-- section 4, 2nd paragraph: "In addition =
Improving TCP=92s Robustness to Blind In-Window =
Attacks."<br><br>sentence =
fragment.<br></div></blockquote><div><br></div>Changed it to =
say:</div><div><br></div><div><i>In addition, the recommendations in =
Improving TCP's Robustness to Blind In-Window =
Attacks</i></div><div><br><blockquote type=3D"cite"><div><br>-- section =
4, 3rd paragraph:<br><br>It would have been helpful to mention the MKT =
manual config issue back in the "state of the security method" =
sections.<br><br></div></blockquote><br>Good point. Moved the mention to =
section 2.2 - Keying issue.</div><div><br><blockquote =
type=3D"cite"><div><br></div></blockquote></div><br><div>
<div>Mahesh Jethanandani</div><div><a =
href=3D"mailto:mjethanandani@gmail.com">mjethanandani@gmail.com</a></div><=
div><br></div><br class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail-36--804921993--

From kathleen.moriarty@emc.com  Tue Nov 20 12:02:04 2012
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFA1F21F883D; Tue, 20 Nov 2012 12:02:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=-0.200, 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 EsL9rQ0sVy1y; Tue, 20 Nov 2012 12:02:04 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id CF7AE21F881B; Tue, 20 Nov 2012 12:02:03 -0800 (PST)
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 qAKK1mZj017071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Nov 2012 15:01:58 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Tue, 20 Nov 2012 15:01:32 -0500
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.222.70.135]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qAKK1UuH030789; Tue, 20 Nov 2012 15:01:30 -0500
Received: from mx15a.corp.emc.com ([169.254.1.120]) by mxhub23.corp.emc.com ([128.222.70.135]) with mapi; Tue, 20 Nov 2012 15:01:29 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Date: Tue, 20 Nov 2012 15:01:28 -0500
Thread-Topic: Gen-art review of draft-ietf-imapmove-command-02
Thread-Index: AQHNvgQbejPc/kQu40q3L/Q+w6y5IQ==
Message-ID: <F5063677821E3B4F81ACFB7905573F24092B036F@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "arnt@gulbrandsen.priv.no" <arnt@gulbrandsen.priv.no>
Subject: [Gen-art] Gen-art review of draft-ietf-imapmove-command-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: Tue, 20 Nov 2012 20:02: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-imapmove-command-02
Reviewer: Kathleen Moriarty
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:  The document needs a little more work before it is ready and shou=
ld address what happens when the series of commands fails to execute (loggi=
ng, revert, etc.).  This should just result in either an incomplete copy (s=
o maybe a garbled message or extra messages being left behind (expunge oper=
ations did not occur).  This document does not cover that case and does not=
 point to another standard that covers that question.

Major issues: =20

Minor issues:  The security consideration section and the main body of the =
document do not explain what happens when the series of commands fails to e=
xecute or any associated risks.  It should not result in mail being deleted=
, but rather being left in too many places or possible errors if the copy o=
peration did not complete (unless that is handled and just needs a refernce=
)?

Nits/editorial comments:
Section 3.3 third paragraph:  NOT and neither form a double negative, the p=
hrase should use either instead of neither:
The server MUST NOT leave a message in either mailbox

In the last sentence of this same paragraph, is there a reference to what h=
appens in the very last clause if the command fails?
   "Note that these restrictions only apply to
   individual messages and not to the command as a whole, which can fail
   partway through."

Section 3.3 paragraph 5, can you add more context or clean up the paragraph=
 to make it easier to follow:
"Note that the server may send EXPUNGEs for other messages as well, if
   any happen to have been expunged at the same time; this is normal
   IMAP operation."

Section 3.3, paragraph 6: remove duplicate "is allowed":
Change from:
"Note that moving a message to the currently selected mailbox (that
   is, where the source and target mailboxes are the same) is allowed
   when copying the message to the currently selected mailbox is
   allowed."
TO:
"Note that moving a message to the currently selected mailbox (that
   is, where the source and target mailboxes are the same) is allowed
   when copying the message to the currently selected mailbox."

Section 4.3, last sentence:
Replace 'that' with whatever it is referring to as it is not clear to the r=
eader.
"It can be unnecessarily difficult to process that usefully.)"

Section 6, Security Considerations, second paragraph, last sentence (change=
 with to when):
Change from:=20
 "Scanning with updated rules may
   also be required when messages are moved even with the underlying
   policy has not changed.
To:
   "Scanning with updated rules may
   also be required when messages are moved even when the underlying
   policy has not changed."

Thanks,
Kathleen=

From barryleiba@gmail.com  Tue Nov 20 13:26:32 2012
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 2619921F8787; Tue, 20 Nov 2012 13:26:32 -0800 (PST)
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 NsF78Ok+ERhp; Tue, 20 Nov 2012 13:26:31 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E03C221F8765; Tue, 20 Nov 2012 13:26:30 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so7425873vbb.31 for <multiple recipients>; Tue, 20 Nov 2012 13:26:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=JNGeZmgApZaYCrzCmcli+7GAMnx2rDgeT+t1RPWtFsY=; b=MS0N92OouH2M14APHjArjno+MyjdaxHjBT+GzAB8LDuhXs/sBTyIejZCbG+7pNAZP3 DL/Q+I2BxP9NGE7fWL8QqhxP4t0LLSnpXtYm4Lw4K9rdlqj6mHv0wL75E8zFEwDcxZaG x7eZQx26qnjylEgvV2jezhcy1VKlMKKvgAiTS2OEc6jwjLGfS9Wl2Fo9vhaRfY+CDGmd bCWBb/Itv/c+z3MpvBkFypgXKSB48Gx3Y4uTCFlq3Tb/53k+503VIDh/wEefU8KgbXX2 ZFatRNy/uraHRD7ZPP9A7kyR2ayYaTHBc+20k7TR1yBTvX8WdkZ/nm6suYJGS3c9Gqwo Z/uw==
MIME-Version: 1.0
Received: by 10.58.187.84 with SMTP id fq20mr23988478vec.25.1353446790308; Tue, 20 Nov 2012 13:26:30 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Tue, 20 Nov 2012 13:26:29 -0800 (PST)
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24092B036F@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24092B036F@MX15A.corp.emc.com>
Date: Tue, 20 Nov 2012 16:26:29 -0500
X-Google-Sender-Auth: HIfZSCbWBBguUs1i44Sd5we4qEg
Message-ID: <CALaySJ+5Y8rxCrPhi1OcCWK59mpCYOsRqNXw4KRkNXOz0WD3OQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ned+ietf@mrochek.com, "gen-art@ietf.org" <gen-art@ietf.org>, "arnt@gulbrandsen.priv.no" <arnt@gulbrandsen.priv.no>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-imapmove-command-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: Tue, 20 Nov 2012 21:26:32 -0000

Hi, Kathleen, and thanks for the review.  You left the document
shepherd and one of the editors off of the distribution list, so I'm
adding them in here.  Because of that, I'm not doing the trimming that
I'd normally do in my inline reply.

On Tue, Nov 20, 2012 at 3:01 PM, Moriarty, Kathleen
<kathleen.moriarty@emc.com> wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document:  draft-ietf-imapmove-command-02
> Reviewer: Kathleen Moriarty
> Review Date:
> IETF LC End Date:
> IESG Telechat date: (if known)
>
> Summary:  The document needs a little more work before it is ready and should
> address what happens when the series of commands fails to execute (logging,
> revert, etc.).  This should just result in either an incomplete copy (so maybe a
> garbled message or extra messages being left behind (expunge operations did
> not occur).  This document does not cover that case and does not point to another
> standard that covers that question.

This appears to be a repetition of the "minor issues" below, so I'm
responding to it there.

> Minor issues:  The security consideration section and the main body of the
> document do not explain what happens when the series of commands fails to
> execute or any associated risks.  It should not result in mail being deleted, but
> rather being left in too many places or possible errors if the copy operation did
> not complete (unless that is handled and just needs a refernce)?

What "series of commands" are you referring to?  The point here is
that there's *one* command, MOVE (or UID MOVE), which makes atomic a
function that is otherwise done with three separate commands (that
cause the problems you're noting, which is why we're creating a single
command to do it).  Is that really not explained sufficiently?  I
should think that the Introduction makes this clear.

As to what state the single MOVE command leaves things in, this
paragraph from Section 3 answers the questions you appear to have:

   Each message SHOULD either be moved or unaffected.  The server MUST
   NOT leave a message in neither mailbox, and SHOULD NOT leave a
   message in both mailboxes afterwards, even if the server returns a
   tagged NO response.  Note that these restrictions only apply to
   individual messages and not to the command as a whole, which can fail
   partway through.

See below for more discussion of that.

> Nits/editorial comments:
> Section 3.3 third paragraph:  NOT and neither form a double negative, the phrase should use either instead of neither:
> The server MUST NOT leave a message in either mailbox

Absolutely not!  The double negative is quite necessary and
intentional.  One possible outcome if the MOVE of a single message
should fail internally would be that the message would be in *neither*
mailbox... perhaps the server removed it from the source mailbox
before putting it into the target, and there was some internal error,
server crash, or power failure at that point.  This is saying that
such a thing MUST NOT happen.

> In the last sentence of this same paragraph, is there a reference to what happens in the very last clause if the command fails?
>    "Note that these restrictions only apply to
>    individual messages and not to the command as a whole, which can fail
>    partway through."

I don't understand what you're asking here either.  The MOVE command
can operate on a set of messages in one command.  The paragraph is
saying that it has to operate successfully (that is, as described in
the earlier part of the paragraph) on each message, but that the
command can fail in the middle, having moved some of the messages but
not others.  It doesn't have to roll back successful moves if it can't
finish the rest.  Maybe this would be clearer to you?:

   These restrictions apply to each message in the set to be moved.
   If the command fails partway through, some messages might be moved,
   while others will not have been.

> Section 3.3 paragraph 5, can you add more context or clean up the paragraph to make it easier to follow:
> "Note that the server may send EXPUNGEs for other messages as well, if
>    any happen to have been expunged at the same time; this is normal
>    IMAP operation."

No further context is needed for anyone familiar with IMAP.  The IMAP
protocol allows the server to send EXPUNGE responses for any message
at any time, and this is just a reminder of that.  It could be
removed, and it would change nothing.  But it would be a bad idea to
repeat what's explained at length in RFC 3501.

> Section 3.3, paragraph 6: remove duplicate "is allowed":
> Change from:
> "Note that moving a message to the currently selected mailbox (that
>    is, where the source and target mailboxes are the same) is allowed
>    when copying the message to the currently selected mailbox is
>    allowed."
> TO:
> "Note that moving a message to the currently selected mailbox (that
>    is, where the source and target mailboxes are the same) is allowed
>    when copying the message to the currently selected mailbox."

Yes, that probably got left there as the sentence was rephrased.  Thanks.

> Section 4.3, last sentence:
> Replace 'that' with whatever it is referring to as it is not clear to the reader.
> "It can be unnecessarily difficult to process that usefully.)"

Would "that sequence" make it clearer for you?

> Section 6, Security Considerations, second paragraph, last sentence (change with to when):
> Change from:
>  "Scanning with updated rules may
>    also be required when messages are moved even with the underlying
>    policy has not changed.
> To:
>    "Scanning with updated rules may
>    also be required when messages are moved even when the underlying
>    policy has not changed."

Yep; thanks.

Barry

From kathleen.moriarty@emc.com  Tue Nov 20 13:49:01 2012
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA70B21F87F2; Tue, 20 Nov 2012 13:49:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level: 
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.109,  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 4dS5XZQk2bGk; Tue, 20 Nov 2012 13:49:01 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id C83A021F87EC; Tue, 20 Nov 2012 13:49:00 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qAKLmr6d003024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Nov 2012 16:48:54 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 20 Nov 2012 16:48:38 -0500
Received: from mxhub04.corp.emc.com (mxhub04.corp.emc.com [10.254.141.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qAKLmbDL007741; Tue, 20 Nov 2012 16:48:38 -0500
Received: from mx15a.corp.emc.com ([169.254.1.120]) by mxhub04.corp.emc.com ([10.254.141.106]) with mapi; Tue, 20 Nov 2012 16:48:37 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Barry Leiba <barryleiba@computer.org>
Date: Tue, 20 Nov 2012 16:48:36 -0500
Thread-Topic: Gen-art review of draft-ietf-imapmove-command-02
Thread-Index: Ac3HZbsa2586j3c4TFyLuoasz78kNwAAI7cD
Message-ID: <F5063677821E3B4F81ACFB7905573F24CAF866CA@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24092B036F@MX15A.corp.emc.com>, <CALaySJ+5Y8rxCrPhi1OcCWK59mpCYOsRqNXw4KRkNXOz0WD3OQ@mail.gmail.com>
In-Reply-To: <CALaySJ+5Y8rxCrPhi1OcCWK59mpCYOsRqNXw4KRkNXOz0WD3OQ@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-EMM-MHVC: 1
Cc: "ned+ietf@mrochek.com" <ned+ietf@mrochek.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "arnt@gulbrandsen.priv.no" <arnt@gulbrandsen.priv.no>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-imapmove-command-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: Tue, 20 Nov 2012 21:49:02 -0000

Hi Barry,

Sure and sorry to have left off a few people, it was unintentional!

I'll explain where I was confused and think I am looking for a lot less tha=
n how you may have interpreted my comments, so this should be fairly easy t=
o resolve.  I added my new comments with [KMM] at the start of each line.

Thanks,
Kathleen
________________________________________
From: barryleiba@gmail.com [barryleiba@gmail.com] On Behalf Of Barry Leiba =
[barryleiba@computer.org]
Sent: Tuesday, November 20, 2012 4:26 PM
To: Moriarty, Kathleen
Cc: gen-art@ietf.org; iesg@ietf.org; arnt@gulbrandsen.priv.no; ned+ietf@mro=
chek.com; Alexey Melnikov
Subject: Re: Gen-art review of draft-ietf-imapmove-command-02

Hi, Kathleen, and thanks for the review.  You left the document
shepherd and one of the editors off of the distribution list, so I'm
adding them in here.  Because of that, I'm not doing the trimming that
I'd normally do in my inline reply.

On Tue, Nov 20, 2012 at 3:01 PM, Moriarty, Kathleen
<kathleen.moriarty@emc.com> wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document:  draft-ietf-imapmove-command-02
> Reviewer: Kathleen Moriarty
> Review Date:
> IETF LC End Date:
> IESG Telechat date: (if known)
>
> Summary:  The document needs a little more work before it is ready and sh=
ould
> address what happens when the series of commands fails to execute (loggin=
g,
> revert, etc.).  This should just result in either an incomplete copy (so =
maybe a
> garbled message or extra messages being left behind (expunge operations d=
id
> not occur).  This document does not cover that case and does not point to=
 another
> standard that covers that question.

This appears to be a repetition of the "minor issues" below, so I'm
responding to it there.

> Minor issues:  The security consideration section and the main body of th=
e
> document do not explain what happens when the series of commands fails to
> execute or any associated risks.  It should not result in mail being dele=
ted, but
> rather being left in too many places or possible errors if the copy opera=
tion did
> not complete (unless that is handled and just needs a refernce)?

What "series of commands" are you referring to?  The point here is
that there's *one* command, MOVE (or UID MOVE), which makes atomic a
function that is otherwise done with three separate commands (that
cause the problems you're noting, which is why we're creating a single
command to do it).  Is that really not explained sufficiently?  I
should think that the Introduction makes this clear.

As to what state the single MOVE command leaves things in, this
paragraph from Section 3 answers the questions you appear to have:

   Each message SHOULD either be moved or unaffected.  The server MUST
   NOT leave a message in neither mailbox, and SHOULD NOT leave a
   message in both mailboxes afterwards, even if the server returns a
   tagged NO response.  Note that these restrictions only apply to
   individual messages and not to the command as a whole, which can fail
   partway through.

[KMM]:  It was the last part of the last sentence that raised the confusion=
, "which can fail part way through."  What happens if it fails partway thro=
ugh?  If this is answered in another RFC, can there be a pointer added to t=
he RFC and section?  Or do you clarify this to say that a failure partway t=
hrough is not acceptable?  I was reading this last sentence as the MOVE com=
mand as a whole contained several operations and one of those operations co=
uld fail.

See below for more discussion of that.

> Nits/editorial comments:
> Section 3.3 third paragraph:  NOT and neither form a double negative, the=
 phrase should use either instead of neither:
> The server MUST NOT leave a message in either mailbox

Absolutely not!  The double negative is quite necessary and
intentional.  One possible outcome if the MOVE of a single message
should fail internally would be that the message would be in *neither*
mailbox... perhaps the server removed it from the source mailbox
before putting it into the target, and there was some internal error,
server crash, or power failure at that point.  This is saying that
such a thing MUST NOT happen.

[KMM]:  I think the correct grammar is to say either instead of neither and=
 it has the same meaning that you intended.  The message would not be in ei=
ther mailbox.

> In the last sentence of this same paragraph, is there a reference to what=
 happens in the very last clause if the command fails?
>    "Note that these restrictions only apply to
>    individual messages and not to the command as a whole, which can fail
>    partway through."

I don't understand what you're asking here either.  The MOVE command
can operate on a set of messages in one command.  The paragraph is
saying that it has to operate successfully (that is, as described in
the earlier part of the paragraph) on each message, but that the
command can fail in the middle, having moved some of the messages but
not others.  It doesn't have to roll back successful moves if it can't
finish the rest.  Maybe this would be clearer to you?:

   These restrictions apply to each message in the set to be moved.
   If the command fails partway through, some messages might be moved,
   while others will not have been.

[KMM]: Okay, now I am a bit more confused.  Can the set of operations fail?=
  Earlier in your response, you say it can't fail.  Then here, it says one =
of the operations can fail.  I am fine with either, I just want to make sur=
e it is clear to the reader.  Is there any logging required when it fails? =
 If this is specified in another IMAP document, maybe a quick reference wou=
ld be helpful?

> Section 3.3 paragraph 5, can you add more context or clean up the paragra=
ph to make it easier to follow:
> "Note that the server may send EXPUNGEs for other messages as well, if
>    any happen to have been expunged at the same time; this is normal
>    IMAP operation."

No further context is needed for anyone familiar with IMAP.  The IMAP
protocol allows the server to send EXPUNGE responses for any message
at any time, and this is just a reminder of that.  It could be
removed, and it would change nothing.  But it would be a bad idea to
repeat what's explained at length in RFC 3501.

[KMM]:  By context, I only meant on the wording, not references to other RF=
Cs.  Reading through this sentence, it would be helpful to know that you ar=
e talking about unrelated expunge operations, at least I think that is what=
 was intended and think it would be helpful to clarify that point with a fe=
w extra words.

> Section 3.3, paragraph 6: remove duplicate "is allowed":
> Change from:
> "Note that moving a message to the currently selected mailbox (that
>    is, where the source and target mailboxes are the same) is allowed
>    when copying the message to the currently selected mailbox is
>    allowed."
> TO:
> "Note that moving a message to the currently selected mailbox (that
>    is, where the source and target mailboxes are the same) is allowed
>    when copying the message to the currently selected mailbox."

Yes, that probably got left there as the sentence was rephrased.  Thanks.

> Section 4.3, last sentence:
> Replace 'that' with whatever it is referring to as it is not clear to the=
 reader.
> "It can be unnecessarily difficult to process that usefully.)"

Would "that sequence" make it clearer for you?

[KMM]:  Yes, "the sequence" works once you add the word sequence.  At the s=
tart of the parens, replacing 'it' would be helpful as well.

> Section 6, Security Considerations, second paragraph, last sentence (chan=
ge with to when):
> Change from:
>  "Scanning with updated rules may
>    also be required when messages are moved even with the underlying
>    policy has not changed.
> To:
>    "Scanning with updated rules may
>    also be required when messages are moved even when the underlying
>    policy has not changed."

Yep; thanks.

Barry


From barryleiba@gmail.com  Tue Nov 20 14:40:45 2012
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 1BD5E21F8659; Tue, 20 Nov 2012 14:40:45 -0800 (PST)
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=[AWL=-0.000, 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 pCkneBgPNZtp; Tue, 20 Nov 2012 14:40:44 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id A9B6B21F8667; Tue, 20 Nov 2012 14:40:43 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so4817397vcb.31 for <multiple recipients>; Tue, 20 Nov 2012 14:40:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=/bK36au/fEuF6qMJ0wVWk+eQMYw/Ls6Rd+sEGBrRWfI=; b=L62HCBSVntdA6/dd32PD98/iDADz9fZQzE1EFPPDmy69t81UnJNVCwYdxwji59EgJS rTTVrWF4TIUwXp9h9P88FK1Pz9RjM75ngbE9gDTJ3hJYbpssurdTdspIAN1lB8Cu8Ial EsV9Hwovoa1hUIJN3fNRIf4yq0W9mvcGIfUlDpDg9XXKE2MZLYD6rQe6+vdcO9V9IDVK fRRrnAXuNtaP4MazP06YHBVPScDUUyyMWl8mT+8EMXzk/IYcS/OlIkYPluttWfTDhOr8 xw21nSixAPNu07MdyX+op1fyyZa0I2qtRc+ISGtWcEyPy3FveNvtwqpCt7wCXuCIh1Tj 3Maw==
MIME-Version: 1.0
Received: by 10.220.119.196 with SMTP id a4mr26029644vcr.19.1353451242798; Tue, 20 Nov 2012 14:40:42 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Tue, 20 Nov 2012 14:40:42 -0800 (PST)
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24CAF866CA@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24092B036F@MX15A.corp.emc.com> <CALaySJ+5Y8rxCrPhi1OcCWK59mpCYOsRqNXw4KRkNXOz0WD3OQ@mail.gmail.com> <F5063677821E3B4F81ACFB7905573F24CAF866CA@MX15A.corp.emc.com>
Date: Tue, 20 Nov 2012 17:40:42 -0500
X-Google-Sender-Auth: Bwjjwjudg4zvzShIgdrNvuIKUOg
Message-ID: <CALaySJKWBY9KoFtTRM7hPmkPzKRUXfgDq5+fZFktfD6ykNzrUA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ned+ietf@mrochek.com" <ned+ietf@mrochek.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "arnt@gulbrandsen.priv.no" <arnt@gulbrandsen.priv.no>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-imapmove-command-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: Tue, 20 Nov 2012 22:40:45 -0000

> What "series of commands" are you referring to?  The point here is
> that there's *one* command, MOVE (or UID MOVE), which makes atomic a
> function that is otherwise done with three separate commands (that
> cause the problems you're noting, which is why we're creating a single
> command to do it).  Is that really not explained sufficiently?  I
> should think that the Introduction makes this clear.
>
> As to what state the single MOVE command leaves things in, this
> paragraph from Section 3 answers the questions you appear to have:
>
>    Each message SHOULD either be moved or unaffected.  The server MUST
>    NOT leave a message in neither mailbox, and SHOULD NOT leave a
>    message in both mailboxes afterwards, even if the server returns a
>    tagged NO response.  Note that these restrictions only apply to
>    individual messages and not to the command as a whole, which can fail
>    partway through.
>
> [KMM]:  It was the last part of the last sentence that raised the confusion,
> "which can fail part way through."  What happens if it fails partway through?
> If this is answered in another RFC, can there be a pointer added to the RFC
> and section?  Or do you clarify this to say that a failure partway through is
> not acceptable?  I was reading this last sentence as the MOVE command
> as a whole contained several operations and one of those operations could fail.

Got it.  Then this is really overlapping with this discussion, moved
up from below:

> The MOVE command
> can operate on a set of messages in one command.  The paragraph is
> saying that it has to operate successfully (that is, as described in
> the earlier part of the paragraph) on each message, but that the
> command can fail in the middle, having moved some of the messages but
> not others.  It doesn't have to roll back successful moves if it can't
> finish the rest.  Maybe this would be clearer to you?:
>
>    These restrictions apply to each message in the set to be moved.
>    If the command fails partway through, some messages might be moved,
>    while others will not have been.
>
> [KMM]: Okay, now I am a bit more confused.  Can the set of operations fail?
> Earlier in your response, you say it can't fail.  Then here, it says one of the
> operations can fail.  I am fine with either, I just want to make sure it is clear
> to the reader.  Is there any logging required when it fails?  If this is specified
> in another IMAP document, maybe a quick reference would be helpful?

I don't think we ever refer to "operations", so I'm still not sure
what you're confused about, but I am sure that you're confused.  So
let's try to sort that out.

The MOVE command can move a set of messages.  If the client sends
"MOVE 1:50 Banana", that's asking the server to move the first 50
messages from the currently selected mailbox into the mailbox called
"Banana".  Let's suppose that the currently selected mailbox is called
"Apple".

The paragraph in question, so we have the context here, says this:

   Each message SHOULD either be moved or unaffected.  The server MUST
   NOT leave a message in neither mailbox, and SHOULD NOT leave a
   message in both mailboxes afterwards, even if the server returns a
   tagged NO response.  Note that these restrictions only apply to
   individual messages and not to the command as a whole, which can fail
   partway through.

What that paragraph is *trying* to tell you is this:

The MOVE command has to leave each message in a reasonable state.
That means that for each message in the message set ("1:50"), either
the message should be moved, or the message should be unaffected
(sentence 1).  For each message in the message set, the server MUST
NOT make it disappear from both Apple and Banana, and SHOULD NOT leave
it in *both* Apple and Banana (sentence 2).  This stuff applies to
each message individually... it's allowable for the server to fail to
move all 50 messages, as long as the previous two sentences apply.

Do you (think you) understand *that*?

I'll propose a reformulation of that paragraph in a moment, but first...

>> Section 3.3 third paragraph:  NOT and neither form a double negative, the
>> phrase should use either instead of neither:
>> The server MUST NOT leave a message in either mailbox
>
> Absolutely not!  The double negative is quite necessary and
> intentional.  One possible outcome if the MOVE of a single message
> should fail internally would be that the message would be in *neither*
> mailbox... perhaps the server removed it from the source mailbox
> before putting it into the target, and there was some internal error,
> server crash, or power failure at that point.  This is saying that
> such a thing MUST NOT happen.
>
> [KMM]:  I think the correct grammar is to say either instead of neither
> and it has the same meaning that you intended.  The message would
> not be in either mailbox.

I think you're wrong.  "MUST NOT be in either mailbox" would mean that
it's not in Apple and it's also not in Banana.  Which is what you say
in your last comment, but it's not what we're trying to say.  There's
nothing grammatically or semantically wrong with the sentence as
written, and it says exactly what it's meant to say: that you MUST NOT
have the message be not in Apple and also not in Banana -- you have to
make sure it remains in one or the other.

Notwithstanding that it's correct, if a native English speaker can't
understand it, then it needs to be re-written (though we thought it
was nice and elegant as it is; sigh -- elegance has to give way to
understanding).

If I re-write the whole paragraph like this, is the whole thing clearer to you?:

   Because a MOVE applies to a set of messages, it might fail partway
   through the set.  Regardless of whether the command is successful in
   moving the entire set, each individual message SHOULD either be moved
   or unaffected.  The server MUST leave each message in a state where
   it is in at least one of the source or target mailboxes (no message can
   be lost or orphaned).  The server SHOULD NOT leave any message in
   both mailboxes (it would be bad for a partial failure to result in a bunch
   of duplicate messages).  This is true even if the server returns a tagged
   NO response to the command.

>> Section 3.3 paragraph 5, can you add more context or clean up the paragraph to make it easier to follow:
>> "Note that the server may send EXPUNGEs for other messages as well, if
>>    any happen to have been expunged at the same time; this is normal
>>    IMAP operation."
>
> No further context is needed for anyone familiar with IMAP.  The IMAP
> protocol allows the server to send EXPUNGE responses for any message
> at any time, and this is just a reminder of that.  It could be
> removed, and it would change nothing.  But it would be a bad idea to
> repeat what's explained at length in RFC 3501.
>
> [KMM]:  By context, I only meant on the wording, not references to other
> RFCs.  Reading through this sentence, it would be helpful to know that you
> are talking about unrelated expunge operations, at least I think that is what
> was intended and think it would be helpful to clarify that point with a few
> extra words.

Hm.  I'm still thinking that this is entirely unnecessary, because,
really, anyone familiar enough with IMAP to consider implementing this
will know exactly what this means.  I'll propose something, and we'll
see if the editors think it's useful to change:

OLD
   Note that the server may send EXPUNGEs for other messages as well, if
   any happen to have been expunged at the same time; this is normal
   IMAP operation.
NEW
   It is always the case in normal IMAP operation that the server might
   also send EXPUNGE responses that are not related to the MOVE, such
   as for other messages that happen to have been expunged at the same
   time.

>> Section 4.3, last sentence:
>> Replace 'that' with whatever it is referring to as it is not clear to the reader.
>> "It can be unnecessarily difficult to process that usefully.)"
>
> Would "that sequence" make it clearer for you?
>
> [KMM]:  Yes, "the sequence" works once you add the word sequence.  At the
> start of the parens, replacing 'it' would be helpful as well.

NEW
   (Sending COPYUID in the tagged OK, as described in the UIDPLUS
   specification, means that clients first receive an EXPUNGE for a
   message and afterwards COPYUID for the same message.  It can be
   unnecessarily difficult to process that sequence usefully.)

Barry

From kathleen.moriarty@emc.com  Tue Nov 20 15:29:09 2012
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19FCB21F8822; Tue, 20 Nov 2012 15:29:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.505
X-Spam-Level: 
X-Spam-Status: No, score=-2.505 tagged_above=-999 required=5 tests=[AWL=0.094,  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 cmP7i02G9s9y; Tue, 20 Nov 2012 15:29:08 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D78CD21F85EB; Tue, 20 Nov 2012 15:29:07 -0800 (PST)
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 qAKNT0oa016571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Nov 2012 18:29:00 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Tue, 20 Nov 2012 18:28:48 -0500
Received: from mxhub10.corp.emc.com (mxhub10.corp.emc.com [10.254.92.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qAKNSlf0002586; Tue, 20 Nov 2012 18:28:47 -0500
Received: from mx15a.corp.emc.com ([169.254.1.120]) by mxhub10.corp.emc.com ([10.254.92.105]) with mapi; Tue, 20 Nov 2012 18:28:47 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Barry Leiba <barryleiba@computer.org>
Date: Tue, 20 Nov 2012 18:24:18 -0500
Thread-Topic: Gen-art review of draft-ietf-imapmove-command-02
Thread-Index: Ac3HcCCknLNLF5DeQDiFqCp81JXKBAABglSj
Message-ID: <F5063677821E3B4F81ACFB7905573F24CAF866D3@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24092B036F@MX15A.corp.emc.com> <CALaySJ+5Y8rxCrPhi1OcCWK59mpCYOsRqNXw4KRkNXOz0WD3OQ@mail.gmail.com> <F5063677821E3B4F81ACFB7905573F24CAF866CA@MX15A.corp.emc.com>, <CALaySJKWBY9KoFtTRM7hPmkPzKRUXfgDq5+fZFktfD6ykNzrUA@mail.gmail.com>
In-Reply-To: <CALaySJKWBY9KoFtTRM7hPmkPzKRUXfgDq5+fZFktfD6ykNzrUA@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-EMM-MHVC: 1
Cc: "ned+ietf@mrochek.com" <ned+ietf@mrochek.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "arnt@gulbrandsen.priv.no" <arnt@gulbrandsen.priv.no>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-imapmove-command-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: Tue, 20 Nov 2012 23:29:09 -0000

Thank you, Barry!

I appreciate your patience on this and suggestions.  I am in the middle of =
some developers working on RFCs in MILE and the comments are leading me to =
be very specific... and I think they are obvious too.

I like all of your suggestions below.  For the second to last one, another =
alternate option closer to the original text for the editors to consider wo=
uld be:
OLD
   Note that the server may send EXPUNGEs for other messages as well, if
   any happen to have been expunged at the same time; this is normal
   IMAP operation.
NEW
   Note that the server may send unrelated EXPUNGE messages as well, if
   any happen to have been expunged at the same time; this is normal
   IMAP operation.

Thanks,
Kathleen

BTW, I can configure a sendmail.cf by hand, but have never programmed IMAP =
server code.  :-)
________________________________________
From: barryleiba@gmail.com [barryleiba@gmail.com] On Behalf Of Barry Leiba =
[barryleiba@computer.org]
Sent: Tuesday, November 20, 2012 5:40 PM
To: Moriarty, Kathleen
Cc: gen-art@ietf.org; iesg@ietf.org; arnt@gulbrandsen.priv.no; ned+ietf@mro=
chek.com; Alexey Melnikov
Subject: Re: Gen-art review of draft-ietf-imapmove-command-02

> What "series of commands" are you referring to?  The point here is
> that there's *one* command, MOVE (or UID MOVE), which makes atomic a
> function that is otherwise done with three separate commands (that
> cause the problems you're noting, which is why we're creating a single
> command to do it).  Is that really not explained sufficiently?  I
> should think that the Introduction makes this clear.
>
> As to what state the single MOVE command leaves things in, this
> paragraph from Section 3 answers the questions you appear to have:
>
>    Each message SHOULD either be moved or unaffected.  The server MUST
>    NOT leave a message in neither mailbox, and SHOULD NOT leave a
>    message in both mailboxes afterwards, even if the server returns a
>    tagged NO response.  Note that these restrictions only apply to
>    individual messages and not to the command as a whole, which can fail
>    partway through.
>
> [KMM]:  It was the last part of the last sentence that raised the confusi=
on,
> "which can fail part way through."  What happens if it fails partway thro=
ugh?
> If this is answered in another RFC, can there be a pointer added to the R=
FC
> and section?  Or do you clarify this to say that a failure partway throug=
h is
> not acceptable?  I was reading this last sentence as the MOVE command
> as a whole contained several operations and one of those operations could=
 fail.

Got it.  Then this is really overlapping with this discussion, moved
up from below:

> The MOVE command
> can operate on a set of messages in one command.  The paragraph is
> saying that it has to operate successfully (that is, as described in
> the earlier part of the paragraph) on each message, but that the
> command can fail in the middle, having moved some of the messages but
> not others.  It doesn't have to roll back successful moves if it can't
> finish the rest.  Maybe this would be clearer to you?:
>
>    These restrictions apply to each message in the set to be moved.
>    If the command fails partway through, some messages might be moved,
>    while others will not have been.
>
> [KMM]: Okay, now I am a bit more confused.  Can the set of operations fai=
l?
> Earlier in your response, you say it can't fail.  Then here, it says one =
of the
> operations can fail.  I am fine with either, I just want to make sure it =
is clear
> to the reader.  Is there any logging required when it fails?  If this is =
specified
> in another IMAP document, maybe a quick reference would be helpful?

I don't think we ever refer to "operations", so I'm still not sure
what you're confused about, but I am sure that you're confused.  So
let's try to sort that out.

The MOVE command can move a set of messages.  If the client sends
"MOVE 1:50 Banana", that's asking the server to move the first 50
messages from the currently selected mailbox into the mailbox called
"Banana".  Let's suppose that the currently selected mailbox is called
"Apple".

The paragraph in question, so we have the context here, says this:

   Each message SHOULD either be moved or unaffected.  The server MUST
   NOT leave a message in neither mailbox, and SHOULD NOT leave a
   message in both mailboxes afterwards, even if the server returns a
   tagged NO response.  Note that these restrictions only apply to
   individual messages and not to the command as a whole, which can fail
   partway through.

What that paragraph is *trying* to tell you is this:

The MOVE command has to leave each message in a reasonable state.
That means that for each message in the message set ("1:50"), either
the message should be moved, or the message should be unaffected
(sentence 1).  For each message in the message set, the server MUST
NOT make it disappear from both Apple and Banana, and SHOULD NOT leave
it in *both* Apple and Banana (sentence 2).  This stuff applies to
each message individually... it's allowable for the server to fail to
move all 50 messages, as long as the previous two sentences apply.

Do you (think you) understand *that*?

I'll propose a reformulation of that paragraph in a moment, but first...

>> Section 3.3 third paragraph:  NOT and neither form a double negative, th=
e
>> phrase should use either instead of neither:
>> The server MUST NOT leave a message in either mailbox
>
> Absolutely not!  The double negative is quite necessary and
> intentional.  One possible outcome if the MOVE of a single message
> should fail internally would be that the message would be in *neither*
> mailbox... perhaps the server removed it from the source mailbox
> before putting it into the target, and there was some internal error,
> server crash, or power failure at that point.  This is saying that
> such a thing MUST NOT happen.
>
> [KMM]:  I think the correct grammar is to say either instead of neither
> and it has the same meaning that you intended.  The message would
> not be in either mailbox.

I think you're wrong.  "MUST NOT be in either mailbox" would mean that
it's not in Apple and it's also not in Banana.  Which is what you say
in your last comment, but it's not what we're trying to say.  There's
nothing grammatically or semantically wrong with the sentence as
written, and it says exactly what it's meant to say: that you MUST NOT
have the message be not in Apple and also not in Banana -- you have to
make sure it remains in one or the other.

Notwithstanding that it's correct, if a native English speaker can't
understand it, then it needs to be re-written (though we thought it
was nice and elegant as it is; sigh -- elegance has to give way to
understanding).

If I re-write the whole paragraph like this, is the whole thing clearer to =
you?:

   Because a MOVE applies to a set of messages, it might fail partway
   through the set.  Regardless of whether the command is successful in
   moving the entire set, each individual message SHOULD either be moved
   or unaffected.  The server MUST leave each message in a state where
   it is in at least one of the source or target mailboxes (no message can
   be lost or orphaned).  The server SHOULD NOT leave any message in
   both mailboxes (it would be bad for a partial failure to result in a bun=
ch
   of duplicate messages).  This is true even if the server returns a tagge=
d
   NO response to the command.

>> Section 3.3 paragraph 5, can you add more context or clean up the paragr=
aph to make it easier to follow:
>> "Note that the server may send EXPUNGEs for other messages as well, if
>>    any happen to have been expunged at the same time; this is normal
>>    IMAP operation."
>
> No further context is needed for anyone familiar with IMAP.  The IMAP
> protocol allows the server to send EXPUNGE responses for any message
> at any time, and this is just a reminder of that.  It could be
> removed, and it would change nothing.  But it would be a bad idea to
> repeat what's explained at length in RFC 3501.
>
> [KMM]:  By context, I only meant on the wording, not references to other
> RFCs.  Reading through this sentence, it would be helpful to know that yo=
u
> are talking about unrelated expunge operations, at least I think that is =
what
> was intended and think it would be helpful to clarify that point with a f=
ew
> extra words.

Hm.  I'm still thinking that this is entirely unnecessary, because,
really, anyone familiar enough with IMAP to consider implementing this
will know exactly what this means.  I'll propose something, and we'll
see if the editors think it's useful to change:

OLD
   Note that the server may send EXPUNGEs for other messages as well, if
   any happen to have been expunged at the same time; this is normal
   IMAP operation.
NEW
   It is always the case in normal IMAP operation that the server might
   also send EXPUNGE responses that are not related to the MOVE, such
   as for other messages that happen to have been expunged at the same
   time.

>> Section 4.3, last sentence:
>> Replace 'that' with whatever it is referring to as it is not clear to th=
e reader.
>> "It can be unnecessarily difficult to process that usefully.)"
>
> Would "that sequence" make it clearer for you?
>
> [KMM]:  Yes, "the sequence" works once you add the word sequence.  At the
> start of the parens, replacing 'it' would be helpful as well.

NEW
   (Sending COPYUID in the tagged OK, as described in the UIDPLUS
   specification, means that clients first receive an EXPUNGE for a
   message and afterwards COPYUID for the same message.  It can be
   unnecessarily difficult to process that sequence usefully.)

Barry


From ned.freed@mrochek.com  Wed Nov 21 09:58:47 2012
Return-Path: <ned.freed@mrochek.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3150921F8633; Wed, 21 Nov 2012 09:58:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.422
X-Spam-Level: 
X-Spam-Status: No, score=-2.422 tagged_above=-999 required=5 tests=[AWL=0.177,  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 Rwu7tYuF27bZ; Wed, 21 Nov 2012 09:58:46 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8D1F521F861E; Wed, 21 Nov 2012 09:58:46 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OMVPM6RYDS0023RD@mauve.mrochek.com>; Wed, 21 Nov 2012 09:53:43 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OMGB2WUMLC00008S@mauve.mrochek.com>; Wed, 21 Nov 2012 09:53:40 -0800 (PST)
Message-id: <01OMVPM4IQL800008S@mauve.mrochek.com>
Date: Wed, 21 Nov 2012 09:42:55 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Tue, 20 Nov 2012 16:26:29 -0500" <CALaySJ+5Y8rxCrPhi1OcCWK59mpCYOsRqNXw4KRkNXOz0WD3OQ@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <F5063677821E3B4F81ACFB7905573F24092B036F@MX15A.corp.emc.com> <CALaySJ+5Y8rxCrPhi1OcCWK59mpCYOsRqNXw4KRkNXOz0WD3OQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: ned+ietf@mrochek.com, "gen-art@ietf.org" <gen-art@ietf.org>, "arnt@gulbrandsen.priv.no" <arnt@gulbrandsen.priv.no>, "iesg@ietf.org" <iesg@ietf.org>, "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-imapmove-command-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: Wed, 21 Nov 2012 17:58:47 -0000

> Hi, Kathleen, and thanks for the review.  You left the document
> shepherd and one of the editors off of the distribution list, so I'm
> adding them in here.  Because of that, I'm not doing the trimming that
> I'd normally do in my inline reply.

Thanks.

> ...

> > Section 3.3, paragraph 6: remove duplicate "is allowed":
> > Change from:
> > "Note that moving a message to the currently selected mailbox (that
> >    is, where the source and target mailboxes are the same) is allowed
> >    when copying the message to the currently selected mailbox is
> >    allowed."
> > TO:
> > "Note that moving a message to the currently selected mailbox (that
> >    is, where the source and target mailboxes are the same) is allowed
> >    when copying the message to the currently selected mailbox."

> Yes, that probably got left there as the sentence was rephrased.  Thanks.

Removed.

> > Section 6, Security Considerations, second paragraph, last sentence (change with to when):
> > Change from:
> >  "Scanning with updated rules may
> >    also be required when messages are moved even with the underlying
> >    policy has not changed.
> > To:
> >    "Scanning with updated rules may
> >    also be required when messages are moved even when the underlying
> >    policy has not changed."

> Yep; thanks.

Took me a while to realize that the reason I couldn't find the change is that
the change had already been made in the document.

Anyway: Fixed.

				Ned

From mahoney@nostrum.com  Wed Nov 21 10:35:29 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F099921F8721 for <gen-art@ietfa.amsl.com>; Wed, 21 Nov 2012 10:35:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gQSOyB0O08gQ for <gen-art@ietfa.amsl.com>; Wed, 21 Nov 2012 10:35:29 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 53FF021F86D9 for <gen-art@ietf.org>; Wed, 21 Nov 2012 10:35:29 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qALIZMGd050185 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Wed, 21 Nov 2012 12:35:28 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50AD1EEA.3020501@nostrum.com>
Date: Wed, 21 Nov 2012 12:35:22 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-11-29 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: Wed, 21 Nov 2012 18:35:30 -0000

Hi all,

The following reviewers have assignments:

Reviewer             LC end       Draft

Brian Carpenter      2012-11-09 draft-ietf-mpls-ipv6-pw-lsp-ping-03 **

Kathleen Moriarty    2012-11-21 draft-ietf-imapmove-command-02 **

Martin Thomson       2012-11-26 draft-ietf-6man-uri-zoneid-05 **

Peter McCann         2012-11-29 draft-ietf-softwire-6rd-radius-attrib-07

Peter Yee            2012-10-22 draft-ietf-nfsv4-federated-fs-protocol-14*

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

Roni Even            2012-11-19   draft-ietf-nea-pt-tls-08 *

* Earlier draft reviewed
** Already reviewed


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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From ned.freed@mrochek.com  Wed Nov 21 10:54:57 2012
Return-Path: <ned.freed@mrochek.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207AD21F879C; Wed, 21 Nov 2012 10:54:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.431
X-Spam-Level: 
X-Spam-Status: No, score=-2.431 tagged_above=-999 required=5 tests=[AWL=0.168,  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 acBgLdIexCht; Wed, 21 Nov 2012 10:54:56 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id D5A0321F8733; Wed, 21 Nov 2012 10:54:55 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OMVRKRSHQ80024M8@mauve.mrochek.com>; Wed, 21 Nov 2012 10:49:51 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OMGB2WUMLC00008S@mauve.mrochek.com>; Wed, 21 Nov 2012 10:49:48 -0800 (PST)
Message-id: <01OMVRKPZ35U00008S@mauve.mrochek.com>
Date: Wed, 21 Nov 2012 10:08:30 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Tue, 20 Nov 2012 17:40:42 -0500" <CALaySJKWBY9KoFtTRM7hPmkPzKRUXfgDq5+fZFktfD6ykNzrUA@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <F5063677821E3B4F81ACFB7905573F24092B036F@MX15A.corp.emc.com> <CALaySJ+5Y8rxCrPhi1OcCWK59mpCYOsRqNXw4KRkNXOz0WD3OQ@mail.gmail.com> <F5063677821E3B4F81ACFB7905573F24CAF866CA@MX15A.corp.emc.com> <CALaySJKWBY9KoFtTRM7hPmkPzKRUXfgDq5+fZFktfD6ykNzrUA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: "ned+ietf@mrochek.com" <ned+ietf@mrochek.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "arnt@gulbrandsen.priv.no" <arnt@gulbrandsen.priv.no>, "iesg@ietf.org" <iesg@ietf.org>, "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-imapmove-command-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: Wed, 21 Nov 2012 18:54:57 -0000

> >> Section 3.3 third paragraph:  NOT and neither form a double negative, the
> >> phrase should use either instead of neither:
> >> The server MUST NOT leave a message in either mailbox
> >
> > Absolutely not!  The double negative is quite necessary and
> > intentional.  One possible outcome if the MOVE of a single message
> > should fail internally would be that the message would be in *neither*
> > mailbox... perhaps the server removed it from the source mailbox
> > before putting it into the target, and there was some internal error,
> > server crash, or power failure at that point.  This is saying that
> > such a thing MUST NOT happen.
> >
> > [KMM]:  I think the correct grammar is to say either instead of neither
> > and it has the same meaning that you intended.  The message would
> > not be in either mailbox.

I'm going to have to push back just a bit here: Double negatives are *not* ipso
facto incorrect grammar. In fact the only case where they should be considered
bad grammar is when they are used incorrectly. The standard example of this is,
"I didn't see noone.", which actualy means, "I saw someone", and that's pretty
certain not to be the speaker's intent.

Far better authors than anyone party to this conversation have written things
like, "There never was no man nowhere so virtuous", so you'll have to pardon me
if I take exception to what's being asserted here.

Of course this doesn't mean the present usage isn't confusing. On that score I
also disagree - I think you're on outlier here - but I'm not sufficiently
enamoured of the present text to object to changing it.

> I think you're wrong.  "MUST NOT be in either mailbox" would mean that
> it's not in Apple and it's also not in Banana.  Which is what you say
> in your last comment, but it's not what we're trying to say.  There's
> nothing grammatically or semantically wrong with the sentence as
> written, and it says exactly what it's meant to say: that you MUST NOT
> have the message be not in Apple and also not in Banana -- you have to
> make sure it remains in one or the other.

> Notwithstanding that it's correct, if a native English speaker can't
> understand it, then it needs to be re-written (though we thought it
> was nice and elegant as it is; sigh -- elegance has to give way to
> understanding).

This principle, taken to its logical conclusion, results in an unsupportable
state of affairs. Like it or not, any text we write is going to be confusing to
someone, somewhere, and a line has to be drawn or we'll never be able to finish
anything.

I speak as someone who has been on the receiving end of comments on the MIME
specification for 20+ years, so this is something I know a *lot* about. 

The only sensible policy is to include the possibility that the text as written
actually is quite clear, and for whatever reason the reviewer's (lack of)
understanding does not in fact indicate that there is a problem.

This point isn't going to change the outcome in the present case, but I want to
be clear that I strongly object to the general principle stated here.

> If I re-write the whole paragraph like this, is the whole thing clearer to you?:

>    Because a MOVE applies to a set of messages, it might fail partway
>    through the set.  Regardless of whether the command is successful in
>    moving the entire set, each individual message SHOULD either be moved
>    or unaffected.  The server MUST leave each message in a state where
>    it is in at least one of the source or target mailboxes (no message can
>    be lost or orphaned).  The server SHOULD NOT leave any message in
>    both mailboxes (it would be bad for a partial failure to result in a bunch
>    of duplicate messages).  This is true even if the server returns a tagged
>    NO response to the command.

I think this actually makes the prohibition against losing messages a bit less
clear, but it significantly improves the discussion of the "leave the message
in both mailboxes" case, so overall it's an improvement and I'm going to put it
in.

> >> Section 3.3 paragraph 5, can you add more context or clean up the paragraph to make it easier to follow:
> >> "Note that the server may send EXPUNGEs for other messages as well, if
> >>    any happen to have been expunged at the same time; this is normal
> >>    IMAP operation."
> >
> > No further context is needed for anyone familiar with IMAP.  The IMAP
> > protocol allows the server to send EXPUNGE responses for any message
> > at any time, and this is just a reminder of that.  It could be
> > removed, and it would change nothing.  But it would be a bad idea to
> > repeat what's explained at length in RFC 3501.
> >
> > [KMM]:  By context, I only meant on the wording, not references to other
> > RFCs.  Reading through this sentence, it would be helpful to know that you
> > are talking about unrelated expunge operations, at least I think that is what
> > was intended and think it would be helpful to clarify that point with a few
> > extra words.

> Hm.  I'm still thinking that this is entirely unnecessary, because,
> really, anyone familiar enough with IMAP to consider implementing this
> will know exactly what this means.  I'll propose something, and we'll
> see if the editors think it's useful to change:

> OLD
>    Note that the server may send EXPUNGEs for other messages as well, if
>    any happen to have been expunged at the same time; this is normal
>    IMAP operation.
> NEW
>    It is always the case in normal IMAP operation that the server might
>    also send EXPUNGE responses that are not related to the MOVE, such
>    as for other messages that happen to have been expunged at the same
>    time.

Ick. "It is always the case" is one of several circumlocutory phrases I'm trying
to stop using, so no, I don't think this is useful change to make.

I much prefer this alternative Kathleen suggested in a subsequent message:

> NEW
>    Note that the server may send unrelated EXPUNGE messages as well, if
>    any happen to have been expunged at the same time; this is normal
>    IMAP operation.

I think this is a good change to make so I'm including it.

> >> Section 4.3, last sentence:
> >> Replace 'that' with whatever it is referring to as it is not clear to the reader.
> >> "It can be unnecessarily difficult to process that usefully.)"
> >
> > Would "that sequence" make it clearer for you?
> >
> > [KMM]:  Yes, "the sequence" works once you add the word sequence.  At the
> > start of the parens, replacing 'it' would be helpful as well.

> NEW
>    (Sending COPYUID in the tagged OK, as described in the UIDPLUS
>    specification, means that clients first receive an EXPUNGE for a
>    message and afterwards COPYUID for the same message.  It can be
>    unnecessarily difficult to process that sequence usefully.)

Yes, this is quite a bit better. Changed.

				Ned

From kathleen.moriarty@emc.com  Wed Nov 21 11:30:05 2012
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA9E121F8856; Wed, 21 Nov 2012 11:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.766
X-Spam-Level: 
X-Spam-Status: No, score=-2.766 tagged_above=-999 required=5 tests=[AWL=-0.167, 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 XoNb5BX8DtMk; Wed, 21 Nov 2012 11:30:05 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id CA81C21F87F1; Wed, 21 Nov 2012 11:30:04 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qALJTt53002902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Nov 2012 14:29:56 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 21 Nov 2012 14:29:34 -0500
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.222.70.135]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qALJTViH011759; Wed, 21 Nov 2012 14:29:32 -0500
Received: from mx15a.corp.emc.com ([169.254.1.120]) by mxhub23.corp.emc.com ([128.222.70.135]) with mapi; Wed, 21 Nov 2012 14:29:31 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Ned Freed <ned.freed@mrochek.com>, Barry Leiba <barryleiba@computer.org>
Date: Wed, 21 Nov 2012 14:26:36 -0500
Thread-Topic: Gen-art review of draft-ietf-imapmove-command-02
Thread-Index: Ac3IGb2KhDU7K3uHRbK5G7HSLyGttAABGHAs
Message-ID: <F5063677821E3B4F81ACFB7905573F24CAF866F7@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24092B036F@MX15A.corp.emc.com> <CALaySJ+5Y8rxCrPhi1OcCWK59mpCYOsRqNXw4KRkNXOz0WD3OQ@mail.gmail.com> <F5063677821E3B4F81ACFB7905573F24CAF866CA@MX15A.corp.emc.com> <CALaySJKWBY9KoFtTRM7hPmkPzKRUXfgDq5+fZFktfD6ykNzrUA@mail.gmail.com>, <01OMVRKPZ35U00008S@mauve.mrochek.com>
In-Reply-To: <01OMVRKPZ35U00008S@mauve.mrochek.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: "ned+ietf@mrochek.com" <ned+ietf@mrochek.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "arnt@gulbrandsen.priv.no" <arnt@gulbrandsen.priv.no>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-imapmove-command-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: Wed, 21 Nov 2012 19:30:06 -0000

Thanks for addressing the comments and making the text more clear.  That wa=
s the main objective of the comments.=20

Best regards,
Kathleen
________________________________________
From: Ned Freed [ned.freed@mrochek.com]
Sent: Wednesday, November 21, 2012 1:08 PM
To: Barry Leiba
Cc: Moriarty, Kathleen; gen-art@ietf.org; iesg@ietf.org; arnt@gulbrandsen.p=
riv.no; ned+ietf@mrochek.com; Alexey Melnikov
Subject: Re: Gen-art review of draft-ietf-imapmove-command-02

> >> Section 3.3 third paragraph:  NOT and neither form a double negative, =
the
> >> phrase should use either instead of neither:
> >> The server MUST NOT leave a message in either mailbox
> >
> > Absolutely not!  The double negative is quite necessary and
> > intentional.  One possible outcome if the MOVE of a single message
> > should fail internally would be that the message would be in *neither*
> > mailbox... perhaps the server removed it from the source mailbox
> > before putting it into the target, and there was some internal error,
> > server crash, or power failure at that point.  This is saying that
> > such a thing MUST NOT happen.
> >
> > [KMM]:  I think the correct grammar is to say either instead of neither
> > and it has the same meaning that you intended.  The message would
> > not be in either mailbox.

I'm going to have to push back just a bit here: Double negatives are *not* =
ipso
facto incorrect grammar. In fact the only case where they should be conside=
red
bad grammar is when they are used incorrectly. The standard example of this=
 is,
"I didn't see noone.", which actualy means, "I saw someone", and that's pre=
tty
certain not to be the speaker's intent.

Far better authors than anyone party to this conversation have written thin=
gs
like, "There never was no man nowhere so virtuous", so you'll have to pardo=
n me
if I take exception to what's being asserted here.

Of course this doesn't mean the present usage isn't confusing. On that scor=
e I
also disagree - I think you're on outlier here - but I'm not sufficiently
enamoured of the present text to object to changing it.

> I think you're wrong.  "MUST NOT be in either mailbox" would mean that
> it's not in Apple and it's also not in Banana.  Which is what you say
> in your last comment, but it's not what we're trying to say.  There's
> nothing grammatically or semantically wrong with the sentence as
> written, and it says exactly what it's meant to say: that you MUST NOT
> have the message be not in Apple and also not in Banana -- you have to
> make sure it remains in one or the other.

> Notwithstanding that it's correct, if a native English speaker can't
> understand it, then it needs to be re-written (though we thought it
> was nice and elegant as it is; sigh -- elegance has to give way to
> understanding).

This principle, taken to its logical conclusion, results in an unsupportabl=
e
state of affairs. Like it or not, any text we write is going to be confusin=
g to
someone, somewhere, and a line has to be drawn or we'll never be able to fi=
nish
anything.

I speak as someone who has been on the receiving end of comments on the MIM=
E
specification for 20+ years, so this is something I know a *lot* about.

The only sensible policy is to include the possibility that the text as wri=
tten
actually is quite clear, and for whatever reason the reviewer's (lack of)
understanding does not in fact indicate that there is a problem.

This point isn't going to change the outcome in the present case, but I wan=
t to
be clear that I strongly object to the general principle stated here.

> If I re-write the whole paragraph like this, is the whole thing clearer t=
o you?:

>    Because a MOVE applies to a set of messages, it might fail partway
>    through the set.  Regardless of whether the command is successful in
>    moving the entire set, each individual message SHOULD either be moved
>    or unaffected.  The server MUST leave each message in a state where
>    it is in at least one of the source or target mailboxes (no message ca=
n
>    be lost or orphaned).  The server SHOULD NOT leave any message in
>    both mailboxes (it would be bad for a partial failure to result in a b=
unch
>    of duplicate messages).  This is true even if the server returns a tag=
ged
>    NO response to the command.

I think this actually makes the prohibition against losing messages a bit l=
ess
clear, but it significantly improves the discussion of the "leave the messa=
ge
in both mailboxes" case, so overall it's an improvement and I'm going to pu=
t it
in.

> >> Section 3.3 paragraph 5, can you add more context or clean up the para=
graph to make it easier to follow:
> >> "Note that the server may send EXPUNGEs for other messages as well, if
> >>    any happen to have been expunged at the same time; this is normal
> >>    IMAP operation."
> >
> > No further context is needed for anyone familiar with IMAP.  The IMAP
> > protocol allows the server to send EXPUNGE responses for any message
> > at any time, and this is just a reminder of that.  It could be
> > removed, and it would change nothing.  But it would be a bad idea to
> > repeat what's explained at length in RFC 3501.
> >
> > [KMM]:  By context, I only meant on the wording, not references to othe=
r
> > RFCs.  Reading through this sentence, it would be helpful to know that =
you
> > are talking about unrelated expunge operations, at least I think that i=
s what
> > was intended and think it would be helpful to clarify that point with a=
 few
> > extra words.

> Hm.  I'm still thinking that this is entirely unnecessary, because,
> really, anyone familiar enough with IMAP to consider implementing this
> will know exactly what this means.  I'll propose something, and we'll
> see if the editors think it's useful to change:

> OLD
>    Note that the server may send EXPUNGEs for other messages as well, if
>    any happen to have been expunged at the same time; this is normal
>    IMAP operation.
> NEW
>    It is always the case in normal IMAP operation that the server might
>    also send EXPUNGE responses that are not related to the MOVE, such
>    as for other messages that happen to have been expunged at the same
>    time.

Ick. "It is always the case" is one of several circumlocutory phrases I'm t=
rying
to stop using, so no, I don't think this is useful change to make.

I much prefer this alternative Kathleen suggested in a subsequent message:

> NEW
>    Note that the server may send unrelated EXPUNGE messages as well, if
>    any happen to have been expunged at the same time; this is normal
>    IMAP operation.

I think this is a good change to make so I'm including it.

> >> Section 4.3, last sentence:
> >> Replace 'that' with whatever it is referring to as it is not clear to =
the reader.
> >> "It can be unnecessarily difficult to process that usefully.)"
> >
> > Would "that sequence" make it clearer for you?
> >
> > [KMM]:  Yes, "the sequence" works once you add the word sequence.  At t=
he
> > start of the parens, replacing 'it' would be helpful as well.

> NEW
>    (Sending COPYUID in the tagged OK, as described in the UIDPLUS
>    specification, means that clients first receive an EXPUNGE for a
>    message and afterwards COPYUID for the same message.  It can be
>    unnecessarily difficult to process that sequence usefully.)

Yes, this is quite a bit better. Changed.

                                Ned


From ben@nostrum.com  Wed Nov 21 15:13:05 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54FA821F84C4; Wed, 21 Nov 2012 15:13:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.121, 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 TNe4AXAf5M6S; Wed, 21 Nov 2012 15:13:04 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4EDB021F84C2; Wed, 21 Nov 2012 15:13:04 -0800 (PST)
Received: from [10.0.1.9] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qALNCx3D077248 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 21 Nov 2012 17:12:59 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com>
Date: Wed, 21 Nov 2012 17:12:57 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B3FEC40-3D96-4F77-A628-E80DFAEB2278@nostrum.com>
References: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com> <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-karp-routing-tcp-analysis-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: Wed, 21 Nov 2012 23:13:05 -0000

Hi, thanks for the response. I removed sections that didn't seem to need =
further comment:

On Nov 19, 2012, at 1:58 AM, Mahesh Jethanandani =
<mjethanandani@gmail.com> wrote:

[...]

>>=20
>> *** Minor issues *** :
>>=20
>> -- section 2.2, last paragraph:
>>=20
>> The IKE mention lacks context. Do you mean to suggest IKE with IPSec? =
I assume so, but there's been no mention of IPSec so far.
>=20
> No. It implies the use of IKEv2 protocol for performing mutual =
authentication and establishing SA. There is no suggestion of using IKE =
with IPSec.
>=20
> How about this?
>=20
> For point-to-point key management IKEv2[RFC5996] protocol provides ...

5996 describes IKEv2 as a component of IPSec, and a key-management =
mechanism for ESP and AH SAs. Now, I won't claim to be an IKE expert by =
any extent, but I think that if you mean to use IKE _without_ IPSec it =
would be good to add a sentence or two pointing that out. Or is there =
some other reference that could be used that describes using IKEv2 for =
non-IPSec SAs?

>=20
>=20
>>=20
>> -- section 2.3.2:
>>=20
>> It would be helpful for this section to describe whether privacy =
issues actually matter or not, rather than just stating the issues to be =
similar to those for other routing protocols.
>=20
> Changed it to:
>=20
> Labels, like routing information are distributed in the clear. There =
is currently no requirement for labels to be encrypted and that work is =
outside the scope of the KARP working group.

WFM

>=20
>>=20
>> -- section 3.1, 2nd paragraph:
>>=20
>> Does this mean that privacy is really not needed, or just that LDP =
does not state a requirement for privacy?
>=20
> Further clarified it in this section.
>=20
> Labels are similar to routing information which is distributed in the =
clear. It is important to ensure that routers exchaning labels are =
mutually authenticated and that there are no rogue peers or =
unauthenticated peers that can compromise the stability of the network. =
However, there is currently no requirement that the labels be encrypted.

Okay

>=20
>>=20
>> -- Section 6 (Security Considerations), 4th paragraph:
>>=20
>> If replay protection is required, shouldn't the draft discuss the =
details somewhere? I see only one mention in passing outside of this =
section.
>=20
> I have moved the replay protection requirement to the gap analysis =
section.=20
>=20
> However, this document is a analysis draft, and it is my understanding =
that details on what replay protection methods should be adopted, is =
best left to the routing protocols in question.=20

That's fine, pointing out the gap is sufficient.

>=20
>>=20
>> *** Nits/editorial comments ***:
>>=20
>> -- IDNits indicates some unused and obsoleted references. Please =
check.
>=20
> Found one unused reference and have removed it.

Seems like there were more than one. =46rom IDNits:

  =3D=3D Missing Reference: 'IRR' is mentioned on line 92, but not =
defined

  =3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit
     reference was found in the text

  =3D=3D Unused Reference: 'RFC3547' is defined on line 588, but no =
explicit
     reference was found in the text

  ** Obsolete normative reference: RFC 2385 (Obsoleted by RFC 5925)

  -- Obsolete informational reference (is this intentional?): RFC 2409
     (Obsoleted by RFC 4306)

  -- Obsolete informational reference (is this intentional?): RFC 3547
     (Obsoleted by RFC 6407)

[...]
>=20
>>=20
>> -- section 2.1,  5th paragraph:
>>=20
>> A mention of SHA1 seems needed here. Section 2.3.1.2 states the =
concerns about TCP-md5 more clearly.
>=20
> The 6th paragraph states the concern and mentions SHA-1. Did you want =
something more to be included?

No, sorry, on a re-read I think it's okay.

[...]

>>=20
>> -- section 4, 2nd paragraph: "In addition Improving TCP=92s =
Robustness to Blind In-Window Attacks."
>>=20
>> sentence fragment.
>=20
> Changed it to say:
>=20
> In addition, the recommendations in Improving TCP's Robustness to =
Blind In-Window Attacks
>=20

Am I correct in assuming this merges with the following sentence? =
Otherwise, it's still a fragment.

[...]

Thanks!

Ben.=

From michael.scharf@alcatel-lucent.com  Sun Nov 25 13:08:57 2012
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 82A8021F8671; Sun, 25 Nov 2012 13:08:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.57
X-Spam-Level: 
X-Spam-Status: No, score=-9.57 tagged_above=-999 required=5 tests=[AWL=0.679,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 wEwVQGjLRgYM; Sun, 25 Nov 2012 13:08:56 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 4C09121F8670; Sun, 25 Nov 2012 13:08:55 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id qAPL8nPd027881 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 25 Nov 2012 22:08:50 +0100
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Sun, 25 Nov 2012 22:08:49 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Ben Campbell <ben@nostrum.com>, "<draft-ietf-mptcp-api.all@tools.ietf.org>" <draft-ietf-mptcp-api.all@tools.ietf.org>
Date: Sun, 25 Nov 2012 22:04:04 +0100
Thread-Topic: Gen-ART Telechat Review of draft-ietf-mptcp-api-06
Thread-Index: Ac3BH3mVEcHOW901Qoi5DTQRmvy+2QKMO061
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AA0F399AE@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <F8E095B8-9E98-4986-80B5-7C498BC07733@nostrum.com>
In-Reply-To: <F8E095B8-9E98-4986-80B5-7C498BC07733@nostrum.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-mptcp-api-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: Sun, 25 Nov 2012 21:08:57 -0000

Ben,

That minor issue can easily be fixed. Actually, I don't have a strong opini=
on on the status on that reference. In fact, I understood from your last e-=
mail that informational status for that reference would be OK. After re-rea=
ding that e-mail, I realize that I just misunderstood your statement therei=
n. We'll change that.

Thanks

Michael

________________________________________
Von: ietf-bounces@ietf.org [ietf-bounces@ietf.org] im Auftrag von Ben Campb=
ell [ben@nostrum.com]
Gesendet: Montag, 12. November 2012 22:48
An: <draft-ietf-mptcp-api.all@tools.ietf.org>
Cc: gen-art@ietf.org Review Team; ietf@ietf.org List
Betreff: Gen-ART Telechat Review of draft-ietf-mptcp-api-06

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

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

Document: draft-ietf-mptcp-api-06
Reviewer: Ben Campbell
Review Date: 2012-11-12
IESG Telechat date: 2012-11-15

Summary: This draft is basically ready for publication as an informational =
RFC. All of the comments from my Gen-ART review of version 05 at IETF last =
call have been dealt with to my satisfaction in the draft or in email, save=
 the one minor issue below.

Major issues:

Minor issues:

I made the following comment at last call. It's not a show stopper, but I t=
hink it should be considered:

> -- It seems like at least passing knowledge of the sockets API is needed =
to understand this document. I'm curious why the POSIX reference is informa=
tional rather than normative?

The authors indicated they believed the reference at the end of paragraph 3=
 of section 1 to be truly informational. However, I called out an mention a=
t the beginning of the same paragraph that should have included a citation,=
 and that I thought that citation would justify a normative reference. The =
authors added the citation in version 06, but the reference is still inform=
ational.


Nits/editorial comments:

IDNits reports that "A later version (-12) exists of
     draft-ietf-mptcp-multiaddressed-09"=

From mjethanandani@gmail.com  Sun Nov 25 17:56:46 2012
Return-Path: <mjethanandani@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 CEC6D21F869B; Sun, 25 Nov 2012 17:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[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 NyswiWmSVs4S; Sun, 25 Nov 2012 17:56:46 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E043E21F8661; Sun, 25 Nov 2012 17:56:42 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so3108193vbb.31 for <multiple recipients>; Sun, 25 Nov 2012 17:56:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=uawVPv3zf6hdvvSh8dyA8OCbxFSvGJx61e6TmJZ3CLs=; b=D9mcBIKitEFHZVQNhgf38xWQ5vEI1eH40268Jcnq0FUQtZYfTW3JR7uDAFtoFId3ns 6F8clc/psVXjNgmC5/yoBhbFLoEr/Y3AkT10pSZj+N7lKsVWDUsgrGBzM+2rZlTPNUta p1jtOxRRJb8+JPX5AHjScYX9w63KWcmEqEsS0fhO8rE8vTsM7EAG61WRI5cwsunomq5B gOnitbMCLfZOLpBCHjQ8/xLb+GaEJW+F63Vjz4xLx/6m4RY/H/R0I50A06rUhmTqBPwq LgFu204M6OnQs7Lbq6SGWDXPCSPE+T3eVryS6W4G2y0LdvRpPOfTS2MMF+Cq7kNlfX4z Pj3A==
Received: by 10.220.220.7 with SMTP id hw7mr16705849vcb.17.1353895002265; Sun, 25 Nov 2012 17:56:42 -0800 (PST)
Received: from txw-scook-01.ciena.com (c-24-6-180-144.hsd1.ca.comcast.net. [24.6.180.144]) by mx.google.com with ESMTPS id y15sm7549351vdt.9.2012.11.25.17.56.40 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 25 Nov 2012 17:56:41 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-8--221838846
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <3B3FEC40-3D96-4F77-A628-E80DFAEB2278@nostrum.com>
Date: Sun, 25 Nov 2012 17:56:39 -0800
Message-Id: <F60EDDFC-0612-4636-AFC7-3D7FD9052D74@gmail.com>
References: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com> <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com> <3B3FEC40-3D96-4F77-A628-E80DFAEB2278@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1085)
Cc: draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-karp-routing-tcp-analysis-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: Mon, 26 Nov 2012 01:56:47 -0000

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

Further trimming it to sections that require a response.

On Nov 21, 2012, at 3:12 PM, Ben Campbell wrote:

>=20
>>>=20
>>> *** Minor issues *** :
>>>=20
>>> -- section 2.2, last paragraph:
>>>=20
>>> The IKE mention lacks context. Do you mean to suggest IKE with =
IPSec? I assume so, but there's been no mention of IPSec so far.
>>=20
>> No. It implies the use of IKEv2 protocol for performing mutual =
authentication and establishing SA. There is no suggestion of using IKE =
with IPSec.
>>=20
>> How about this?
>>=20
>> For point-to-point key management IKEv2[RFC5996] protocol provides =
...
>=20
> 5996 describes IKEv2 as a component of IPSec, and a key-management =
mechanism for ESP and AH SAs. Now, I won't claim to be an IKE expert by =
any extent, but I think that if you mean to use IKE _without_ IPSec it =
would be good to add a sentence or two pointing that out. Or is there =
some other reference that could be used that describes using IKEv2 for =
non-IPSec SAs?

Added this sentence.

Although IKEv2 is discussed as a component of IPsec, KMP can use just =
the mutual authentication and SA establishment portion of IKEv2.

>=20
>>=20
>>>=20
>>> *** Nits/editorial comments ***:
>>>=20
>>> -- IDNits indicates some unused and obsoleted references. Please =
check.
>>=20
>> Found one unused reference and have removed it.
>=20
> Seems like there were more than one. =46rom IDNits:
>=20
>  =3D=3D Missing Reference: 'IRR' is mentioned on line 92, but not =
defined
>=20
>  =3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit
>     reference was found in the text
>=20
>  =3D=3D Unused Reference: 'RFC3547' is defined on line 588, but no =
explicit
>     reference was found in the text
>=20
>  ** Obsolete normative reference: RFC 2385 (Obsoleted by RFC 5925)
>=20
>  -- Obsolete informational reference (is this intentional?): RFC 2409
>     (Obsoleted by RFC 4306)
>=20
>  -- Obsolete informational reference (is this intentional?): RFC 3547
>     (Obsoleted by RFC 6407)

I have removed these unused references.

>=20
>>>=20
>>> -- section 4, 2nd paragraph: "In addition Improving TCP=92s =
Robustness to Blind In-Window Attacks."
>>>=20
>>> sentence fragment.
>>=20
>> Changed it to say:
>>=20
>> In addition, the recommendations in Improving TCP's Robustness to =
Blind In-Window Attacks
>>=20
>=20
> Am I correct in assuming this merges with the following sentence? =
Otherwise, it's still a fragment.
>=20

Changed it to:

In addition, the recommendations in RFC 5961 should also be followed ...

Mahesh Jethanandani
mjethanandani@gmail.com




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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Further trimming it to sections that require a =
response.<div><br><div><div>On Nov 21, 2012, at 3:12 PM, Ben Campbell =
wrote:</div><br><blockquote type=3D"cite"><div><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">*** Minor issues *** =
:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- section 2.2, last =
paragraph:<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">The IKE mention lacks context. =
Do you mean to suggest IKE with IPSec? I assume so, but there's been no =
mention of IPSec so far.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">No. It implies =
the use of IKEv2 protocol for performing mutual authentication and =
establishing SA. There is no suggestion of using IKE with =
IPSec.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">How about =
this?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">For =
point-to-point key management IKEv2[RFC5996] protocol provides =
...<br></blockquote><br>5996 describes IKEv2 as a component of IPSec, =
and a key-management mechanism for ESP and AH SAs. Now, I won't claim to =
be an IKE expert by any extent, but I think that if you mean to use IKE =
_without_ IPSec it would be good to add a sentence or two pointing that =
out. Or is there some other reference that could be used that describes =
using IKEv2 for non-IPSec =
SAs?<br></div></blockquote><div><br></div>Added this =
sentence.</div><div><br></div><div><i>Although IKEv2 is discussed as a =
component of IPsec, KMP can use just the mutual authentication and SA =
establishment portion of IKEv2.</i></div><div><br><blockquote =
type=3D"cite"><div><br><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">*** Nits/editorial comments =
***:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- IDNits indicates some unused =
and obsoleted references. Please =
check.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Found one =
unused reference and have removed it.<br></blockquote><br>Seems like =
there were more than one. =46rom IDNits:<br><br> &nbsp;=3D=3D Missing =
Reference: 'IRR' is mentioned on line 92, but not defined<br><br> =
&nbsp;=3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit<br> &nbsp;&nbsp;&nbsp;&nbsp;reference was found in the =
text<br><br> &nbsp;=3D=3D Unused Reference: 'RFC3547' is defined on line =
588, but no explicit<br> &nbsp;&nbsp;&nbsp;&nbsp;reference was found in =
the text<br><br> &nbsp;** Obsolete normative reference: RFC 2385 =
(Obsoleted by RFC 5925)<br><br> &nbsp;-- Obsolete informational =
reference (is this intentional?): RFC 2409<br> =
&nbsp;&nbsp;&nbsp;&nbsp;(Obsoleted by RFC 4306)<br><br> &nbsp;-- =
Obsolete informational reference (is this intentional?): RFC 3547<br> =
&nbsp;&nbsp;&nbsp;&nbsp;(Obsoleted by RFC =
6407)<br></div></blockquote><div><br></div>I have removed these unused =
references.</div><div><br><blockquote type=3D"cite"><div><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- section 4, 2nd paragraph: "In =
addition Improving TCP=92s Robustness to Blind In-Window =
Attacks."<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">sentence =
fragment.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Changed it to =
say:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">In addition, =
the recommendations in Improving TCP's Robustness to Blind In-Window =
Attacks<br></blockquote><blockquote type=3D"cite"><br></blockquote><br>Am =
I correct in assuming this merges with the following sentence? =
Otherwise, it's still a =
fragment.<br><br></div></blockquote><br></div><div>Changed it =
to:</div><div><br></div><div><i>In addition, the recommendations in RFC =
5961 should also be followed ...</i></div><br><div>
<div>Mahesh Jethanandani</div><div><a =
href=3D"mailto:mjethanandani@gmail.com">mjethanandani@gmail.com</a></div><=
div><br></div><br class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail-8--221838846--

From alexey.melnikov@isode.com  Mon Nov 26 04:03:04 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD9C21F8588 for <gen-art@ietfa.amsl.com>; Mon, 26 Nov 2012 04:03:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nBUS9whrAhZi for <gen-art@ietfa.amsl.com>; Mon, 26 Nov 2012 04:03:03 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 51D8E21F8585 for <gen-art@ietf.org>; Mon, 26 Nov 2012 04:03:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1353931380; d=isode.com; s=selector; i=@isode.com; bh=WnJpnVLFhLuzTbOwhFbXJG9fsAj+19EfZTD84EvTuSc=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=m2P2HLsBRn22xQhyZk44/SZ89LXRlOuTp9jNstNO7pSpfxZo9PeumBKCr2xspiUeMtD3f6 nkIAsqG511wT25xntY3KS5+h4DjqzW/FJ0aoxY9fvOP91vVA5FwLUEoXKX7CXCp6rwY5eP sRnA7Yrz8r8KdYk1AcvketvMcrTsCVQ=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <ULNadAAbAgH8@statler.isode.com>; Mon, 26 Nov 2012 12:03:00 +0000
Message-ID: <50B35AAF.20104@isode.com>
Date: Mon, 26 Nov 2012 12:03:59 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mmusic-sdp-media-capabilities.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART review of draft-ietf-mmusic-sdp-media-capabilities-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 12:03: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-mmusic-sdp-media-capabilities-15
Reviewer: Alexey Melnikov
Review Date: 2012-11-26
IETF LC End Date: 2012-11-12
IESG Telechat date: not scheduled

Summary:  This document is ready for publication as Proposed Standard,
with nits.

Nits/editorial comments:

This might be obvious to a SIP implementer, but the media type/subtype 
definition RFC is not referenced anywhere. Should it be?

3.3.5.  The Latent Configuration Attribute

    Latent configurations may be announced by use of the latent
    configuration attribute, which is defined in a manner very similar to
    the potential configuration attribute.  The latent configuration
    attribute combines the properties of a media line and a potential
    configuration.  The media type (mt=) and the transport protocol(s)
    (t=) MUST be specified since the latent configuration is independent
    of any media line present.  In most cases, the media configuration
    (m=) parameter MUST be present as well (see Section 4 for examples).

This doesn't look like a correct use of MUST, please reword not to use 
any RFC 2119 keyword or at least provide a pointer to a document that 
contains the original requirement.

    The lcfg attribute is a media level attribute.

  [...]

    If a cryptographic attribute, such as the SDES "a=crypto:" attribute
    [RFC4568], is referenced by a latent configuration through an acap
    attribute, any keying material required in the conventional
    attribute, such as the SDES key/salt string, MUST be included in
    order to satisfy formatting rules for the attribute.  The actual
    value(s) of the keying material SHOULD be meaningless, and the

Can you please elaborate on what are you trying to say here?

    receiver of the lcfg attribute MUST ignore the values.

From hartmans@mit.edu  Mon Nov 26 09:38:14 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A0CF21F85AB for <gen-art@ietfa.amsl.com>; Mon, 26 Nov 2012 09:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NOXjiEygUhqE for <gen-art@ietfa.amsl.com>; Mon, 26 Nov 2012 09:38:13 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 8C7E521F84D3 for <gen-art@ietf.org>; Mon, 26 Nov 2012 09:38:13 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id D32FF201E2; Mon, 26 Nov 2012 12:36:36 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 001704149; Mon, 26 Nov 2012 12:38:01 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Elwyn Davies <elwynd@dial.pipex.com>
References: <1352132615.23621.1264.camel@mightyatom.folly.org.uk>
Date: Mon, 26 Nov 2012 12:38:01 -0500
In-Reply-To: <1352132615.23621.1264.camel@mightyatom.folly.org.uk> (Elwyn Davies's message of "Mon, 05 Nov 2012 16:23:35 +0000")
Message-ID: <tsl38zw2rk6.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-karp-ospf-analysis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-karp-ospf-analysis-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 17:38:14 -0000

Hi. Thanks for your review.
In my edit buffer, I have made changes that are responsive to all your comments except one
nit:


>>>>> "Elwyn" == Elwyn Davies <elwynd@dial.pipex.com> writes:
    Elwyn> s3, para 1:
    >> As discussed, neither version of OSPF meets the requirements of
    >> inter-connection or intra-connection replay protection.
    Elwyn> Neither of the discussions above mention the phrases
    Elwyn> 'inter-connection' or 'intra-connection'.  For OSPFv3 this is
    Elwyn> implicit because 'no replay protection is provided'.  For
    Elwyn> OSPFv2 it would be desirable to explain how the problems
    Elwyn> outlined in s2.1 relate to these terms.

Actually, the discussion in section 1 of requirements to meet did
discuss both inter-connection and intra-connection replay, referring
back to the requirements draft.
Also, the discussion in section 2 already included an explicit mention
of what created an inter-connection vulnerability.
I added a reference to intra-connection replay in the appropriate part
of section 2.

From mahoney@nostrum.com  Tue Nov 27 13:29:13 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E12C121F84D7 for <gen-art@ietfa.amsl.com>; Tue, 27 Nov 2012 13:29:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yLE+tBQMNUbI for <gen-art@ietfa.amsl.com>; Tue, 27 Nov 2012 13:29:13 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7593121F84DC for <gen-art@ietf.org>; Tue, 27 Nov 2012 13:29:12 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qARLT28j008075 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Tue, 27 Nov 2012 15:29:09 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50B5309D.3050206@nostrum.com>
Date: Tue, 27 Nov 2012 15:29:01 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-11-27
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 27 Nov 2012 21:29:14 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Peter Yee         2012-12-11  draft-ietf-avt-rtp-evrc-nw-08

Roni Even         2012-12-14  draft-daboo-ical-vcard-parameter-encoding-02

Suresh Krishnan   2012-12-10  draft-ietf-tcpm-initcwnd-06 *

* on the 2012-12-13 telechat


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

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


The standard template is included below.

Thanks,

Jean

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From meral.shirazipour@ericsson.com  Tue Nov 27 14:45:11 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 156FF21F85C0 for <gen-art@ietfa.amsl.com>; Tue, 27 Nov 2012 14:45:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rU1evv54KwFM for <gen-art@ietfa.amsl.com>; Tue, 27 Nov 2012 14:45:02 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id B712B21F8521 for <gen-art@ietf.org>; Tue, 27 Nov 2012 14:45:02 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id qARMrC0S021980; Tue, 27 Nov 2012 16:53:15 -0600
Received: from EUSAAHC001.ericsson.se (147.117.188.75) by eusaamw0711.eamcs.ericsson.se (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 27 Nov 2012 17:45:00 -0500
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0318.001; Tue, 27 Nov 2012 17:45:00 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-lisp-eid-block.all@tools.ietf.org" <draft-ietf-lisp-eid-block.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-lisp-eid-block-03
Thread-Index: Ac3M8KlZhsIM5qX1RWmhqrDsHxuSAg==
Date: Tue, 27 Nov 2012 22:45:00 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A02273E@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A02273Eeusaamb107ericsso_"
MIME-Version: 1.0
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-lisp-eid-block-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 22:45:12 -0000

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

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

Please resolve these comments along with the other Last Call comments you h=
ave receive.

Document: draft-ietf-lisp-eid-block-03
Reviewer: Meral Shirazipour
Review Date: 2012-11-27
IETF LC End Date: 2012-11-27
IESG Telechat date: NA

Summary:
This draft is almost ready for publication but I have some editorial commen=
ts.


Nits/editorial comments:
[Page 5], paragraph 4, "((i.e., a Data " ----> please remove extra "("
[Page 6], paragraph 1, "By defining an IPv6 EID Block is possible" --missin=
g 'it'--> "By defining an IPv6 EID Block it is possible "
[Page 6], paragraph 1, "the router so to natively" --remove 'so'--> "the ro=
uter to natively"
[Page 6], paragraph 1, "while facilitating its large-scale deployment"---> =
can "its" be replaced by LISP's ?
[Page 6], Section 4 title, "Expected use" --upper case--> "Expected Use"
[Page 6], Section 4, "Too guarantee" --typo--> "To guarantee"
[Page 6], Section 5, line 1, "allocation of a /16 prefix" --clarity--> "all=
ocation of a /16 IPv6 prefix"
[Page 7], Section 6,  "(Locator/ID Separation protocol)"--uppercase P--> "(=
Locator/ID Separation Protocol)"


Best Regards,
Meral

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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-CA" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at &lt;http://wiki.tools.ietf.=
org/area/gen/trac/wiki/GenArtfaq&gt; .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with the other L=
ast Call comments you have receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-lisp-eid-block-03<o:p></o:p></p=
>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2012-11-27<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2012-11-27<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is almost ready for publication but I hav=
e some editorial comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 5], paragraph 4, &quot;((i.e., a Data &quot; -=
---&gt; please remove extra &quot;(&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 6], paragraph 1, &quot;By defining an IPv6 EID=
 Block is possible&quot; --missing 'it'--&gt; &quot;By defining an IPv6 EID=
 Block it is possible &quot;<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 6], paragraph 1, &quot;the router so to native=
ly&quot; --remove 'so'--&gt; &quot;the router to natively&quot;<o:p></o:p><=
/p>
<p class=3D"MsoNormal">[Page 6], paragraph 1, &quot;while facilitating its =
large-scale deployment&quot;---&gt; can &quot;its&quot; be replaced by LISP=
's ?<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 6], Section 4 title, &quot;Expected use&quot; =
--upper case--&gt; &quot;Expected Use&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 6], Section 4, &quot;Too guarantee&quot; --typ=
o--&gt; &quot;To guarantee&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 6], Section 5, line 1, &quot;allocation of a /=
16 prefix&quot; --clarity--&gt; &quot;allocation of a /16 IPv6 prefix&quot;=
<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 7], Section 6,&nbsp; &quot;(Locator/ID Separat=
ion protocol)&quot;--uppercase P--&gt; &quot;(Locator/ID Separation Protoco=
l)&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A02273Eeusaamb107ericsso_--

From mccap@petoni.org  Tue Nov 27 19:57:20 2012
Return-Path: <mccap@petoni.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35F5E11E8099 for <gen-art@ietfa.amsl.com>; Tue, 27 Nov 2012 19:57:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rIslsOwz5FRP for <gen-art@ietfa.amsl.com>; Tue, 27 Nov 2012 19:57:19 -0800 (PST)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 40FFD11E8097 for <gen-art@ietf.org>; Tue, 27 Nov 2012 19:57:19 -0800 (PST)
Received: by mail-gg0-f172.google.com with SMTP id r1so609398ggn.31 for <gen-art@ietf.org>; Tue, 27 Nov 2012 19:57:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=RYe/T/zB0GErkyP3NDjIv4m/A7cridaouprbxvhKsjY=; b=EvbHFxs83xjnjLDhnmOGUNR9yzAIsPMmNi09WD9kvR4B4EAsthpmEDXWpVjCoDXSiR TGHDL2lRqsFEF1F5gM0Iu+l3Vt/GKHO+sjZ/M6WF+qiFRbXSWJTDy3EiLUnbHLJblcPs pppzKVF83/9z7m2lKwPvjeZbo7feoJk26BOnI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=RYe/T/zB0GErkyP3NDjIv4m/A7cridaouprbxvhKsjY=; b=be8VKFm/HN+RewcKKlwgsIedHM9rD9DHEXwjSjgo8Dynu5ydEr7lPef4RvKHSAqVXA fCG3N82oI/Y2yFg174zXB94pICPuqvQGCovxRsyhK14zZYTJNd9mebTvrfe2Y9ZzLDYj ywiq0cyaUT9TGzSLJsNPQcvHRZsrdedJNH1qFHqxCRG36122JIrq9eyXxH2Bcm4XV7DW aa0tYsYCqlYjRog20HxL1gdXTBR4VoCytiM0lFvZdhlFJN0xpw5gAdHMmMwIdnroRpyp qLb8Nc89ldXyQzI7gWfNgX/A5xD05mhmLHqcQKczD9qbHENBdGKMkezCXsbbaIdSuGD1 TnOg==
MIME-Version: 1.0
Received: by 10.236.147.208 with SMTP id t56mr17072608yhj.88.1354075038632; Tue, 27 Nov 2012 19:57:18 -0800 (PST)
Received: by 10.101.4.40 with HTTP; Tue, 27 Nov 2012 19:57:18 -0800 (PST)
X-Originating-IP: [68.45.157.93]
Date: Tue, 27 Nov 2012 22:57:18 -0500
Message-ID: <CACvMsLEtB7kWy3uhdt6H5=KA0fkW1umO5oJYRE4H5ZPUwzrinQ@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-softwire-6rd-radius-attrib.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnh7qCxrELbVd1REsomMFWal4aHgfh9NMPfCeORdeA+OsEWwbvqFvFQH36lGs2j/tLTM7Lh
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-softwire-6rd-radius-attrib-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, 28 Nov 2012 03:57:20 -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-softwire-6rd-radius-attrib-07
Reviewer:  Peter McCann
Review Date:  2012-11-27
IETF LC End Date:
IESG Telechat date: 2012-11-29

Summary: Ready

Major issues: None

Minor issues:

IPv4MaskLen doesn't need to be any more than 8bits long.

Nits/editorial comments: None

From jiangsheng@huawei.com  Thu Nov 29 00:03:00 2012
Return-Path: <jiangsheng@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFF1A21F89EB for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 00:02:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 XiKFlALGfsnx for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 00:02:59 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id ACD5D21F8937 for <gen-art@ietf.org>; Thu, 29 Nov 2012 00:02:58 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AMA05677; Thu, 29 Nov 2012 08:02:55 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 29 Nov 2012 08:02:01 +0000
Received: from SZXEML445-HUB.china.huawei.com (10.82.67.183) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 29 Nov 2012 08:02:13 +0000
Received: from SZXEML545-MBS.china.huawei.com ([169.254.2.174]) by szxeml445-hub.china.huawei.com ([10.82.67.183]) with mapi id 14.01.0323.003; Thu, 29 Nov 2012 16:02:08 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Pete McCann <mccap@petoni.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-softwire-6rd-radius-attrib.all@tools.ietf.org" <draft-ietf-softwire-6rd-radius-attrib.all@tools.ietf.org>
Thread-Topic: Gen-ART Telechat Review of draft-ietf-softwire-6rd-radius-attrib-07
Thread-Index: AQHNzRyH93TWGzQDK0uzykBUihO//JgAbvxA
Date: Thu, 29 Nov 2012 08:02:08 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9239FC4EA0@szxeml545-mbs.china.huawei.com>
References: <CACvMsLEtB7kWy3uhdt6H5=KA0fkW1umO5oJYRE4H5ZPUwzrinQ@mail.gmail.com>
In-Reply-To: <CACvMsLEtB7kWy3uhdt6H5=KA0fkW1umO5oJYRE4H5ZPUwzrinQ@mail.gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.140]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-softwire-6rd-radius-attrib-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 08:03:00 -0000

PkRvY3VtZW50OiAgIGRyYWZ0LWlldGYtc29mdHdpcmUtNnJkLXJhZGl1cy1hdHRyaWItMDcNCj5S
ZXZpZXdlcjogIFBldGVyIE1jQ2Fubg0KPlJldmlldyBEYXRlOiAgMjAxMi0xMS0yNw0KPklFVEYg
TEMgRW5kIERhdGU6DQo+SUVTRyBUZWxlY2hhdCBkYXRlOiAyMDEyLTExLTI5DQo+DQo+U3VtbWFy
eTogUmVhZHkNCj4NCj5NYWpvciBpc3N1ZXM6IE5vbmUNCj4NCj5NaW5vciBpc3N1ZXM6DQo+DQo+
SVB2NE1hc2tMZW4gZG9lc24ndCBuZWVkIHRvIGJlIGFueSBtb3JlIHRoYW4gOGJpdHMgbG9uZy4N
Cg0KSGksIFBldGUsDQoNClRoYW5rcyBmb3IgcmV2aWV3aW5nLiBUaGlzIGlzIGEgbWlzdGFrZS4g
SXQgd2FzIDhiaXRzIGluIDA2IHZlcnNpb24uIEkgZG9uJ3Qga25vdyB3aHkgSSBtYWtlIGl0IDMy
IGluIHRoaXMgdmVyc2lvbi4gSXQgd2lsbCBiZSBmaXhlZCBpbiB0aGUgbmV4dCB1cGRhdGUuDQoN
CkJlc3QgcmVnYXJkcywNCg0KU2hlbmcNCg0KPk5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOiBOb25l
DQo=

From housley@vigilsec.com  Thu Nov 29 06:24:16 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE92021F89BA for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 06:24:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.742
X-Spam-Level: 
X-Spam-Status: No, score=-102.742 tagged_above=-999 required=5 tests=[AWL=-0.143, 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 hvQlqfSFNSGF for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 06:24:16 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE8A21F88E8 for <gen-art@ietf.org>; Thu, 29 Nov 2012 06:24:16 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 615869A400B; Thu, 29 Nov 2012 09:24:20 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 2R6qyP2K6usQ; Thu, 29 Nov 2012 09:24:06 -0500 (EST)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D4C3D9A4016; Thu, 29 Nov 2012 09:24:18 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CABkgnnWkKy9bTyXtwubsjM5cd97xeCtPWMVnADOFq6BzWN+R9A@mail.gmail.com>
Date: Thu, 29 Nov 2012 09:24:12 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <41C6A3AE-A167-483A-8F84-E2A7D35F95AC@vigilsec.com>
References: <CABkgnnVo1LYt=LRbH8dPgaAaCY=GVNARC0y=E6E+bo5G=gNgag@mail.gmail.com> <CABkgnnUgXGhEm6WeVzuYs7ADAQgifkApJe0_JimYde9mK1ARhQ@mail.gmail.com> <50A747F0.2090407@gmail.com> <CABkgnnWkKy9bTyXtwubsjM5cd97xeCtPWMVnADOFq6BzWN+R9A@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: draft-ietf-6man-uri-zoneid.all@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-6man-uri-zoneid-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 14:24:17 -0000

I do not see changes based on this discussion.  There should be some, right?

Russ


On Nov 18, 2012, at 10:25 PM, Martin Thomson wrote:

> On 17 November 2012 00:16, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>> I don't quite understand that. RFC3986 section 2.1 says
>>  pct-encoded = "%" HEXDIG HEXDIG
>> with no restrictions on HEXDIG, so why is %01 disallowed?
>> (I agree it would be meaningless, but that's another matter).
> 
> Meaningless is precisely my point.  It's unclear what is exactly the
> right behaviour in this situation, so hedging on the vague side,
> inadvisable as that normally is, might be safest.
> 
>>>> s/proxy/intermediary/
>> 
>> proxy or other intermediary?
> 
> Exactly.


From brian.e.carpenter@gmail.com  Thu Nov 29 07:02:44 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9940421F8443 for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 07:02:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MI3KiWjPGDFK for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 07:02:44 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id D7A1621F843E for <gen-art@ietf.org>; Thu, 29 Nov 2012 07:02:43 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so3213883wgb.13 for <gen-art@ietf.org>; Thu, 29 Nov 2012 07:02:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=x8K+KH6N1v7icoHwWX7Ua2WGuyHIOVOrNmYN49sqQjw=; b=uTkJaxxA1yA90leIBvRZbmVQzeqOqvt30seQy5ku6iISvnhBsCPyc7M+Y9rQlVpDoS Y0IWGMgD423z0NoHodSsTrVsTvpygDdMnmFgSUH+0D3+/oKp4YYUiFFbug3N0ZXtiVJk KQ3yMZACA1SX8bqZB/6YIJ8kgBxs9/2Cp26nOHHyYRFYCuINf40PelSLhY3sEgRMQp1J q9/S2PLnta9SSt633TeDdGP9zWgmjXV0eohZTYwRNoMx8IseG1I8ZFl2BR0a1wjKqSHj keU+Fm7tsqAW3MPXMSzVTuyHMDbRaTWmUyVEw9Mrr1HVHNNudHS/aLeBj007lcO7/445 ly3w==
Received: by 10.216.200.6 with SMTP id y6mr9026736wen.131.1354201359926; Thu, 29 Nov 2012 07:02:39 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-103.as13285.net. [2.102.217.103]) by mx.google.com with ESMTPS id bd7sm2740009wib.8.2012.11.29.07.02.36 (version=SSLv3 cipher=OTHER); Thu, 29 Nov 2012 07:02:37 -0800 (PST)
Message-ID: <50B77918.8020702@gmail.com>
Date: Thu, 29 Nov 2012 15:02:48 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
References: <CABkgnnVo1LYt=LRbH8dPgaAaCY=GVNARC0y=E6E+bo5G=gNgag@mail.gmail.com> <CABkgnnUgXGhEm6WeVzuYs7ADAQgifkApJe0_JimYde9mK1ARhQ@mail.gmail.com> <50A747F0.2090407@gmail.com> <CABkgnnWkKy9bTyXtwubsjM5cd97xeCtPWMVnADOFq6BzWN+R9A@mail.gmail.com> <41C6A3AE-A167-483A-8F84-E2A7D35F95AC@vigilsec.com>
In-Reply-To: <41C6A3AE-A167-483A-8F84-E2A7D35F95AC@vigilsec.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-6man-uri-zoneid.all@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-6man-uri-zoneid-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 15:02:44 -0000

Russ, there are changes needed from this and other reviews, and IMHO
some of them need to go back to the WG. I wouldn't be comfortable
asserting that they are editorial.

Personally I'd be happy with Revised I-D Needed, with or without a DISCUSS.

Regards
   Brian Carpenter

On 29/11/2012 14:24, Russ Housley wrote:
> I do not see changes based on this discussion.  There should be some, right?
> 
> Russ
> 
> 
> On Nov 18, 2012, at 10:25 PM, Martin Thomson wrote:
> 
>> On 17 November 2012 00:16, Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>>> I don't quite understand that. RFC3986 section 2.1 says
>>>  pct-encoded = "%" HEXDIG HEXDIG
>>> with no restrictions on HEXDIG, so why is %01 disallowed?
>>> (I agree it would be meaningless, but that's another matter).
>> Meaningless is precisely my point.  It's unclear what is exactly the
>> right behaviour in this situation, so hedging on the vague side,
>> inadvisable as that normally is, might be safest.
>>
>>>>> s/proxy/intermediary/
>>> proxy or other intermediary?
>> Exactly.
> 
> 

From bob.hinden@gmail.com  Thu Nov 29 09:46:44 2012
Return-Path: <bob.hinden@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 3DE4921F8B47 for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 09:46:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9XhLSzcSpXSY for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 09:46:43 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6D3C821F8B40 for <gen-art@ietf.org>; Thu, 29 Nov 2012 09:46:43 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id w11so7158164bku.31 for <gen-art@ietf.org>; Thu, 29 Nov 2012 09:46:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=zEaCp+S1ug1r2fzhNeBQx8AT3jFUckCC/3SHnNQfD7k=; b=DoVtpAqXss+F01RdUkM+1REcS5YCFLCJta2dzG8IKlHCvZjbCj9zegbQaK8ZmYEPhS RINmFEx9pA4p2Wh45GPF4DHQs5YjWfKuNcutseSDbaQLEP/QfNICWb450qKC2ZbHHLqM N4UICJ6v/cYEPic9qkARjPIyfSoWRVNiefzD2Fzm4DO3SWJ6kof4xHC+oFmuNIHT164l Fr3qYzU5jKA7jzM7rqwQkPG1o5vuMISMsmSyGuExRdoyz4bzR+3rSa2reoxwmQjoTIN+ cjMbiSwsqIpvfhCgtGGsk895icslT3M8OOTqGxE4qtCxdlijGscqiNpkdr0uoUY/hp8k q31w==
Received: by 10.204.136.207 with SMTP id s15mr7042972bkt.5.1354211202316; Thu, 29 Nov 2012 09:46:42 -0800 (PST)
Received: from ?IPv6:2601:9:4080:10:e80c:74c6:f7f9:b25c? ([2601:9:4080:10:e80c:74c6:f7f9:b25c]) by mx.google.com with ESMTPS id y11sm1783775bkw.8.2012.11.29.09.46.37 (version=SSLv3 cipher=OTHER); Thu, 29 Nov 2012 09:46:41 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <50B77918.8020702@gmail.com>
Date: Thu, 29 Nov 2012 09:46:35 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7B838AB-9F8C-445C-90B8-C3C3991989C0@gmail.com>
References: <CABkgnnVo1LYt=LRbH8dPgaAaCY=GVNARC0y=E6E+bo5G=gNgag@mail.gmail.com> <CABkgnnUgXGhEm6WeVzuYs7ADAQgifkApJe0_JimYde9mK1ARhQ@mail.gmail.com> <50A747F0.2090407@gmail.com> <CABkgnnWkKy9bTyXtwubsjM5cd97xeCtPWMVnADOFq6BzWN+R9A@mail.gmail.com> <41C6A3AE-A167-483A-8F84-E2A7D35F95AC@vigilsec.com> <50B77918.8020702@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Thu, 29 Nov 2012 10:03:14 -0800
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, draft-ietf-6man-uri-zoneid.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-6man-uri-zoneid-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 17:46:44 -0000

On Nov 29, 2012, at 7:02 AM, Brian E Carpenter wrote:

> Russ, there are changes needed from this and other reviews, and IMHO
> some of them need to go back to the WG. I wouldn't be comfortable
> asserting that they are editorial.
>=20
> Personally I'd be happy with Revised I-D Needed, with or without a =
DISCUSS.

With my w.g. chair hat on, I think there have been enough changes that =
the w.g. should review it once we have a version that resolves the IESG =
discusses/comments/etc. =20

Bob


>=20
> Regards
>   Brian Carpenter
>=20
> On 29/11/2012 14:24, Russ Housley wrote:
>> I do not see changes based on this discussion.  There should be some, =
right?
>>=20
>> Russ
>>=20
>>=20
>> On Nov 18, 2012, at 10:25 PM, Martin Thomson wrote:
>>=20
>>> On 17 November 2012 00:16, Brian E Carpenter
>>> <brian.e.carpenter@gmail.com> wrote:
>>>> I don't quite understand that. RFC3986 section 2.1 says
>>>> pct-encoded =3D "%" HEXDIG HEXDIG
>>>> with no restrictions on HEXDIG, so why is %01 disallowed?
>>>> (I agree it would be meaningless, but that's another matter).
>>> Meaningless is precisely my point.  It's unclear what is exactly the
>>> right behaviour in this situation, so hedging on the vague side,
>>> inadvisable as that normally is, might be safest.
>>>=20
>>>>>> s/proxy/intermediary/
>>>> proxy or other intermediary?
>>> Exactly.
>>=20
>>=20


From mahoney@nostrum.com  Thu Nov 29 15:06:40 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B228F21F8B2F for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 15:06:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMmfNCpGw-js for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 15:06:40 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1709B21F8A9B for <gen-art@ietf.org>; Thu, 29 Nov 2012 15:06:40 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qATN6cuA025162 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 29 Nov 2012 17:06:38 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50B7EA7E.80002@nostrum.com>
Date: Thu, 29 Nov 2012 17:06:38 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Cc: Tero Kivinen <kivinen@iki.fi>
Subject: [Gen-art] Changes to the review tool
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 29 Nov 2012 23:06:40 -0000

Hi all,

The Gen-ART review tool has been updated.

Highlights of changes:

  * Review status tooltip - on the Queue pages, hover your mouse over a
    reviewer's name to see when a review was done, which version was
    reviewed, and the summary of the review.
  * Easier review editing - click the Done link of your document to be
    taken to the review page where you can modify the version, the
    status, review URL, and the review summary.
  * Withdraw document - the secretary can now withdraw a document from a
    reviewer's queue, rather than "Reject"ing it.
  * No Response - the secretary can now mark a review assignment with No
    Response if a review has not been received by the telechat date.
  * IESG status links now point to the IESG ballot.


A list of all the changes since the last version:

https://wiki.tools.ietf.org/tools/art/trac/query?status=assigned&status=closed&status=reopened&changetime=2012-11-01..2012-11-29&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=id


Thanks to Tero for maintaining and improving the tool!

Jean





From peter@akayla.com  Thu Nov 29 15:08:57 2012
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E73E321F8ADD; Thu, 29 Nov 2012 15:08:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r79CYSuQzXdh; Thu, 29 Nov 2012 15:08:57 -0800 (PST)
Received: from p3plsmtpa06-02.prod.phx3.secureserver.net (p3plsmtpa06-02.prod.phx3.secureserver.net [173.201.192.103]) by ietfa.amsl.com (Postfix) with ESMTP id 339DA21F8A9B; Thu, 29 Nov 2012 15:08:56 -0800 (PST)
Received: from spectre ([173.8.184.78]) by p3plsmtpa06-02.prod.phx3.secureserver.net with  id Vb8v1k00A1huGat01b8v5g; Thu, 29 Nov 2012 16:08:56 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org>
Date: Thu, 29 Nov 2012 15:09:00 -0800
Message-ID: <002501cdce86$84f59940$8ee0cbc0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3OhkqJKVIPVc8hSRSzOY8nvjKAQg==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 23:08:58 -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-nfsv4-federated-fs-protocol-14
Reviewer: Peter Yee
Review Date: Nov-29-2012
IETF LC End Date: Oct-22-2012
IESG Telechat date: Nov-29-2012

Summary: This draft is basically ready for publication, but has a nit that
should be fixed before publication. [Ready with nits.]

All other corrections from the -13 review were accepted and the other
changes in the current version appear reasonable.

Major issues:

Minor issues:

Nits/editorial comments:

Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1"  in
"(see" and ")" for readability.
[This is my same suggestion from the previous review.  I won't mention it
again, I promise. :-) ]


From mahoney@nostrum.com  Thu Nov 29 15:27:08 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07B2A21F8AB2 for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 15:27:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id os9JhvceTWEF for <gen-art@ietfa.amsl.com>; Thu, 29 Nov 2012 15:27:07 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4CCD321F8958 for <gen-art@ietf.org>; Thu, 29 Nov 2012 15:27:07 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qATNR5j2027305 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 29 Nov 2012 17:27:05 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50B7EF49.1090407@nostrum.com>
Date: Thu, 29 Nov 2012 17:27:05 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-11-29
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 29 Nov 2012 23:27:08 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Alexey Melnikov   2012-12-12   draft-ietf-6renum-static-problem-02

Brian Carpenter   2012-12-27   draft-hanes-dispatch-fax-capability-06

Christer Holmberg 2012-12-13   draft-ietf-tcpm-experimental-options-03 *

Dan Romascanu     2013-01-02   draft-bonica-special-purpose-03

Vijay Gurbani     2012-12-26   draft-salgueiro-vcarddav-kind-device-06

Wassim Haddad     2012-12-12   draft-ietf-6renum-enterprise-04


* on the 2012-12-20 telechat


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

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


The standard template is included below.

Thanks,

Jean

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From vkg@bell-labs.com  Fri Nov 30 06:49:29 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B87521F8A60 for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 06:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ggq3f1f8Ggo0 for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 06:49:28 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id A99CB21F8942 for <gen-art@ietf.org>; Fri, 30 Nov 2012 06:49:23 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id qAUEnD0w017417 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 30 Nov 2012 08:49:13 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qAUEnCCm032274 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 30 Nov 2012 08:49:12 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qAUEnA3N025292; Fri, 30 Nov 2012 08:49:10 -0600 (CST)
Message-ID: <50B8C7BD.6020504@bell-labs.com>
Date: Fri, 30 Nov 2012 08:50:37 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: draft-salgueiro-vcarddav-kind-device@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: Pete Resnick <presnick@qualcomm.com>, Cyrus Daboo <cyrus@daboo.name>, General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 14:49: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-salgueiro-vcarddav-kind-device-06
Reviewer: Vijay K. Gurbani
Review Date: Nov-30-2012
IETF LC End Date: Dec-26-2012
IESG Telechat date: Unknown

This document is ready as a Proposed Standard.

Major: 0
Minor: 0
Nits: 2

Nits:

1/ S1: The value "thing" sort of creeps up on you in the second
  paragraph.  Upon further reading, it becomes more apparent that
  during the WG discussions "thing" was a meta-value (or super-
  class) and that "application" and "device" appear to be sub-
  classes (or specific values) of "thing"s.

  Furthermore, rf6473 already defined "application" and that this
  particular draft is now defining "device".

  To better impart this information, I would suggest the following
  simple modification

  OLD:
  ...Working Group defined values of "individual", "org", "group", and
  "location" for the KIND property.  Additionally, [RFC6473] has
  defined a value of "application" for the KIND property to represent
  software applications.

  During working group discussion of the document that became
  [RFC6473], consideration was given to defining a more general value
  of "thing", but it was decided to split "thing" into software
  applications and hardware devices and to define only the
  "application" value at that time....

  NEW:
  ...Working Group defined values of "individual", "org", "group", and
  "location" for the KIND property.

  During working group discussion of the document that became
  [RFC6473], consideration was given to defining a more general value
  of "thing", but it was decided to split "thing" into software
  applications and hardware devices and to define only the
  "application" value at that time....

2/ S2, top of page 4: "FN" probably expands to "Full Name".  If it is
  an accepted practice to use "FN" in your domain, then you can leave
  it unexpanded.  If not, then an expansion may help the general reader
  (like me) who may think what "FN" is.  (The rest of the properties
  listed on page 4 and 5 appear to be self-explanatory).

Thanks,

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

From chuck.lever@oracle.com  Fri Nov 30 07:45:28 2012
Return-Path: <chuck.lever@oracle.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2690621F8B4D; Fri, 30 Nov 2012 07:45:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=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 nZR4fd1i8NL9; Fri, 30 Nov 2012 07:45:27 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 5D55D21F8B36; Fri, 30 Nov 2012 07:45:27 -0800 (PST)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id qAUFjGrL013266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 30 Nov 2012 15:45:17 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id qAUFjGXB020212 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Nov 2012 15:45:16 GMT
Received: from abhmt112.oracle.com (abhmt112.oracle.com [141.146.116.64]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id qAUFjFO6032269; Fri, 30 Nov 2012 09:45:15 -0600
Received: from moret.1015granger.net (/99.26.161.222) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 30 Nov 2012 07:45:15 -0800
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <002501cdce86$84f59940$8ee0cbc0$@akayla.com>
Date: Fri, 30 Nov 2012 10:45:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <08608853-52A1-443F-88CF-B550BD325B82@oracle.com>
References: <002501cdce86$84f59940$8ee0cbc0$@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1499)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-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, 30 Nov 2012 15:45:28 -0000

On Nov 29, 2012, at 6:09 PM, Peter Yee <peter@akayla.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at <
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd or AD before =
posting a
> new version of the draft.
>=20
> Document: draft-ietf-nfsv4-federated-fs-protocol-14
> Reviewer: Peter Yee
> Review Date: Nov-29-2012
> IETF LC End Date: Oct-22-2012
> IESG Telechat date: Nov-29-2012
>=20
> Summary: This draft is basically ready for publication, but has a nit =
that
> should be fixed before publication. [Ready with nits.]
>=20
> All other corrections from the -13 review were accepted and the other
> changes in the current version appear reasonable.
>=20
> Major issues:
>=20
> Minor issues:
>=20
> Nits/editorial comments:
>=20
> Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1"  =
in
> "(see" and ")" for readability.
> [This is my same suggestion from the previous review.  I won't mention =
it
> again, I promise. :-) ]

Sorry we missed this before.  I'll work with Martin to see that this is =
addressed.

--=20
Chuck Lever
chuck[dot]lever[at]oracle[dot]com





From gsalguei@cisco.com  Fri Nov 30 08:27:17 2012
Return-Path: <gsalguei@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 1F28821E8040 for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:27:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=0.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 NpZWWH4N0mRH for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:27:16 -0800 (PST)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 34D7121F8B29 for <gen-art@ietf.org>; Fri, 30 Nov 2012 08:27:16 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qAUGREU6011953 for <gen-art@ietf.org>; Fri, 30 Nov 2012 11:27:14 -0500 (EST)
Received: from dhcp-64-102-154-214.cisco.com (dhcp-64-102-154-214.cisco.com [64.102.154.214]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qAUGRCia011666; Fri, 30 Nov 2012 11:27:12 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <50B8C7BD.6020504@bell-labs.com>
Date: Fri, 30 Nov 2012 11:27:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com>
References: <50B8C7BD.6020504@bell-labs.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Fri, 30 Nov 2012 08:27:58 -0800
Cc: Pete Resnick <presnick@qualcomm.com>, draft-salgueiro-vcarddav-kind-device@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Cyrus Daboo <cyrus@daboo.name>, Gonzalo Salgueiro <gsalguei@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 16:27:17 -0000

Vijay -=20

Good to hear from you, my friend. Hope you are well.

Thanks for the detailed review. As for your two nits:

1. I'm fine with the suggested edit and will update the next version =
(after IETF LC) with the suggested changes.

2. FN is a well-known identification property for vCards and does expand =
to "Full Name". Even in RFC 6350 it doesn't appear to be expanded, so =
I'll likely continue that trend and simply add a reference section 6.2.1 =
of RFC 6350 after the usage of FN to help the uninitiated in vCards.  Is =
that OK with you?

Cheers,

Gonzalo

On Nov 30, 2012, at 9:50 AM, Vijay K. Gurbani wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-salgueiro-vcarddav-kind-device-06
> Reviewer: Vijay K. Gurbani
> Review Date: Nov-30-2012
> IETF LC End Date: Dec-26-2012
> IESG Telechat date: Unknown
>=20
> This document is ready as a Proposed Standard.
>=20
> Major: 0
> Minor: 0
> Nits: 2
>=20
> Nits:
>=20
> 1/ S1: The value "thing" sort of creeps up on you in the second
> paragraph.  Upon further reading, it becomes more apparent that
> during the WG discussions "thing" was a meta-value (or super-
> class) and that "application" and "device" appear to be sub-
> classes (or specific values) of "thing"s.
>=20
> Furthermore, rf6473 already defined "application" and that this
> particular draft is now defining "device".
>=20
> To better impart this information, I would suggest the following
> simple modification
>=20
> OLD:
> ...Working Group defined values of "individual", "org", "group", and
> "location" for the KIND property.  Additionally, [RFC6473] has
> defined a value of "application" for the KIND property to represent
> software applications.
>=20
> During working group discussion of the document that became
> [RFC6473], consideration was given to defining a more general value
> of "thing", but it was decided to split "thing" into software
> applications and hardware devices and to define only the
> "application" value at that time....
>=20
> NEW:
> ...Working Group defined values of "individual", "org", "group", and
> "location" for the KIND property.
>=20
> During working group discussion of the document that became
> [RFC6473], consideration was given to defining a more general value
> of "thing", but it was decided to split "thing" into software
> applications and hardware devices and to define only the
> "application" value at that time....
>=20
> 2/ S2, top of page 4: "FN" probably expands to "Full Name".  If it is
> an accepted practice to use "FN" in your domain, then you can leave
> it unexpanded.  If not, then an expansion may help the general reader
> (like me) who may think what "FN" is.  (The rest of the properties
> listed on page 4 and 5 appear to be self-explanatory).
>=20
> Thanks,
>=20
> - vijay
> --=20
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web:   http://ect.bell-labs.com/who/vkg/
>=20


From jclarke@cisco.com  Fri Nov 30 08:30:44 2012
Return-Path: <jclarke@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 1AC0621F8B4F for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:30:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iLB96GyyCqW4 for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:30:43 -0800 (PST)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 3216421F8B48 for <gen-art@ietf.org>; Fri, 30 Nov 2012 08:30:43 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qAUGUe9T012353; Fri, 30 Nov 2012 11:30:40 -0500 (EST)
Received: from dhcp-10-150-52-225.cisco.com (dhcp-10-150-52-225.cisco.com [10.150.52.225]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qAUGUemD015762;  Fri, 30 Nov 2012 11:30:40 -0500 (EST)
Message-ID: <50B8DF30.6000002@cisco.com>
Date: Fri, 30 Nov 2012 11:30:40 -0500
From: Joe Marcus Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Gonzalo Salgueiro <gsalguei@cisco.com>
References: <50B8C7BD.6020504@bell-labs.com> <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com>
In-Reply-To: <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 30 Nov 2012 08:31:34 -0800
Cc: Pete Resnick <presnick@qualcomm.com>, draft-salgueiro-vcarddav-kind-device@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Cyrus Daboo <cyrus@daboo.name>
Subject: Re: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 16:30:44 -0000

On 11/30/12 11:27 AM, Gonzalo Salgueiro wrote:
> Vijay - 
> 
> Good to hear from you, my friend. Hope you are well.
> 
> Thanks for the detailed review. As for your two nits:
> 
> 1. I'm fine with the suggested edit and will update the next version (after IETF LC) with the suggested changes.

++

> 
> 2. FN is a well-known identification property for vCards and does expand to "Full Name". Even in RFC 6350 it doesn't appear to be expanded, so I'll likely continue that trend and simply add a reference section 6.2.1 of RFC 6350 after the usage of FN to help the uninitiated in vCards.  Is that OK with you?

FN is a property name, so I think we should leave it as-is.  Since we
already reference 6350, and we don't annotate each property, do we need
another ref?  I think those in the vCard domain will recognize FN.
Thoughts?

Joe

> 
> Cheers,
> 
> Gonzalo
> 
> On Nov 30, 2012, at 9:50 AM, Vijay K. Gurbani wrote:
> 
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-salgueiro-vcarddav-kind-device-06
>> Reviewer: Vijay K. Gurbani
>> Review Date: Nov-30-2012
>> IETF LC End Date: Dec-26-2012
>> IESG Telechat date: Unknown
>>
>> This document is ready as a Proposed Standard.
>>
>> Major: 0
>> Minor: 0
>> Nits: 2
>>
>> Nits:
>>
>> 1/ S1: The value "thing" sort of creeps up on you in the second
>> paragraph.  Upon further reading, it becomes more apparent that
>> during the WG discussions "thing" was a meta-value (or super-
>> class) and that "application" and "device" appear to be sub-
>> classes (or specific values) of "thing"s.
>>
>> Furthermore, rf6473 already defined "application" and that this
>> particular draft is now defining "device".
>>
>> To better impart this information, I would suggest the following
>> simple modification
>>
>> OLD:
>> ...Working Group defined values of "individual", "org", "group", and
>> "location" for the KIND property.  Additionally, [RFC6473] has
>> defined a value of "application" for the KIND property to represent
>> software applications.
>>
>> During working group discussion of the document that became
>> [RFC6473], consideration was given to defining a more general value
>> of "thing", but it was decided to split "thing" into software
>> applications and hardware devices and to define only the
>> "application" value at that time....
>>
>> NEW:
>> ...Working Group defined values of "individual", "org", "group", and
>> "location" for the KIND property.
>>
>> During working group discussion of the document that became
>> [RFC6473], consideration was given to defining a more general value
>> of "thing", but it was decided to split "thing" into software
>> applications and hardware devices and to define only the
>> "application" value at that time....
>>
>> 2/ S2, top of page 4: "FN" probably expands to "Full Name".  If it is
>> an accepted practice to use "FN" in your domain, then you can leave
>> it unexpanded.  If not, then an expansion may help the general reader
>> (like me) who may think what "FN" is.  (The rest of the properties
>> listed on page 4 and 5 appear to be self-explanatory).
>>
>> Thanks,
>>
>> - vijay
>> -- 
>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
>> Web:   http://ect.bell-labs.com/who/vkg/
>>
> 
> 


-- 
Joe Marcus Clarke, CCIE #5384,         |          |
SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
Distinguished Services Engineer ..:|||||||||::|||||||||:..
Phone: +1 (919) 392-2867         c i s c o  S y s t e m s
Email: jclarke@cisco.com

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

From gsalguei@cisco.com  Fri Nov 30 08:37:40 2012
Return-Path: <gsalguei@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 1A6D621F8B64 for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:37:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level: 
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 pxMgXw1cy4Ib for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:37:39 -0800 (PST)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 4886A21F8B24 for <gen-art@ietf.org>; Fri, 30 Nov 2012 08:37:39 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qAUGbc8u013152 for <gen-art@ietf.org>; Fri, 30 Nov 2012 11:37:38 -0500 (EST)
Received: from dhcp-64-102-154-214.cisco.com (dhcp-64-102-154-214.cisco.com [64.102.154.214]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qAUGbb5Y023966; Fri, 30 Nov 2012 11:37:37 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <50B8DF30.6000002@cisco.com>
Date: Fri, 30 Nov 2012 11:37:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <29C62AF2-90EB-4293-8865-3B827B368303@cisco.com>
References: <50B8C7BD.6020504@bell-labs.com> <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com> <50B8DF30.6000002@cisco.com>
To: Joe Marcus Clarke <jclarke@cisco.com>
X-Mailer: Apple Mail (2.1283)
Cc: General Area Review Team <gen-art@ietf.org>, Gonzalo Salgueiro <gsalguei@cisco.com>, Cyrus Daboo <cyrus@daboo.name>, draft-salgueiro-vcarddav-kind-device@tools.ietf.org, Pete Resnick <presnick@qualcomm.com>
Subject: Re: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 16:37:40 -0000

On Nov 30, 2012, at 11:30 AM, Joe Marcus Clarke wrote:

> On 11/30/12 11:27 AM, Gonzalo Salgueiro wrote:
>> Vijay -=20
>>=20
>> Good to hear from you, my friend. Hope you are well.
>>=20
>> Thanks for the detailed review. As for your two nits:
>>=20
>> 1. I'm fine with the suggested edit and will update the next version =
(after IETF LC) with the suggested changes.
>=20
> ++
>=20
>>=20
>> 2. FN is a well-known identification property for vCards and does =
expand to "Full Name". Even in RFC 6350 it doesn't appear to be =
expanded, so I'll likely continue that trend and simply add a reference =
section 6.2.1 of RFC 6350 after the usage of FN to help the uninitiated =
in vCards.  Is that OK with you?
>=20
> FN is a property name, so I think we should leave it as-is.  Since we
> already reference 6350, and we don't annotate each property, do we =
need
> another ref?  I think those in the vCard domain will recognize FN.
> Thoughts?

I'm certainly OK without the specific reference to FN (as that is what =
is there now). It was suggested as an aid for casual readers since Vijay =
mentioned that FN was the only property that wasn't immediately =
understood.  I'm good either way.

Cheers,

Gonzalo

>=20
> Joe
>=20
>>=20
>> Cheers,
>>=20
>> Gonzalo
>>=20
>> On Nov 30, 2012, at 9:50 AM, Vijay K. Gurbani wrote:
>>=20
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>=20
>>> Please resolve these comments along with any other Last Call =
comments
>>> you may receive.
>>>=20
>>> Document: draft-salgueiro-vcarddav-kind-device-06
>>> Reviewer: Vijay K. Gurbani
>>> Review Date: Nov-30-2012
>>> IETF LC End Date: Dec-26-2012
>>> IESG Telechat date: Unknown
>>>=20
>>> This document is ready as a Proposed Standard.
>>>=20
>>> Major: 0
>>> Minor: 0
>>> Nits: 2
>>>=20
>>> Nits:
>>>=20
>>> 1/ S1: The value "thing" sort of creeps up on you in the second
>>> paragraph.  Upon further reading, it becomes more apparent that
>>> during the WG discussions "thing" was a meta-value (or super-
>>> class) and that "application" and "device" appear to be sub-
>>> classes (or specific values) of "thing"s.
>>>=20
>>> Furthermore, rf6473 already defined "application" and that this
>>> particular draft is now defining "device".
>>>=20
>>> To better impart this information, I would suggest the following
>>> simple modification
>>>=20
>>> OLD:
>>> ...Working Group defined values of "individual", "org", "group", and
>>> "location" for the KIND property.  Additionally, [RFC6473] has
>>> defined a value of "application" for the KIND property to represent
>>> software applications.
>>>=20
>>> During working group discussion of the document that became
>>> [RFC6473], consideration was given to defining a more general value
>>> of "thing", but it was decided to split "thing" into software
>>> applications and hardware devices and to define only the
>>> "application" value at that time....
>>>=20
>>> NEW:
>>> ...Working Group defined values of "individual", "org", "group", and
>>> "location" for the KIND property.
>>>=20
>>> During working group discussion of the document that became
>>> [RFC6473], consideration was given to defining a more general value
>>> of "thing", but it was decided to split "thing" into software
>>> applications and hardware devices and to define only the
>>> "application" value at that time....
>>>=20
>>> 2/ S2, top of page 4: "FN" probably expands to "Full Name".  If it =
is
>>> an accepted practice to use "FN" in your domain, then you can leave
>>> it unexpanded.  If not, then an expansion may help the general =
reader
>>> (like me) who may think what "FN" is.  (The rest of the properties
>>> listed on page 4 and 5 appear to be self-explanatory).
>>>=20
>>> Thanks,
>>>=20
>>> - vijay
>>> --=20
>>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>>> Email: vkg@{bell-labs.com,acm.org} / =
vijay.gurbani@alcatel-lucent.com
>>> Web:   http://ect.bell-labs.com/who/vkg/
>>>=20
>>=20
>>=20
>=20
>=20
> --=20
> Joe Marcus Clarke, CCIE #5384,         |          |
> SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
> Distinguished Services Engineer ..:|||||||||::|||||||||:..
> Phone: +1 (919) 392-2867         c i s c o  S y s t e m s
> Email: jclarke@cisco.com
>=20
> =
--------------------------------------------------------------------------=
--
>=20


From vkg@bell-labs.com  Fri Nov 30 08:38:58 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ABF121F8B64 for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:38:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nu7+qWs1HbXx for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:38:57 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 71F2421F8B4F for <gen-art@ietf.org>; Fri, 30 Nov 2012 08:38:57 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id qAUGckpC011163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 30 Nov 2012 10:38:46 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qAUGckXj004827 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 30 Nov 2012 10:38:46 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qAUGcjaR021771; Fri, 30 Nov 2012 10:38:46 -0600 (CST)
Message-ID: <50B8E16D.2050700@bell-labs.com>
Date: Fri, 30 Nov 2012 10:40:13 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Gonzalo Salgueiro <gsalguei@cisco.com>
References: <50B8C7BD.6020504@bell-labs.com> <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com>
In-Reply-To: <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: Pete Resnick <presnick@qualcomm.com>, draft-salgueiro-vcarddav-kind-device@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Cyrus Daboo <cyrus@daboo.name>
Subject: Re: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 16:38:58 -0000

Gonzalo: Please see inline.

On 11/30/2012 10:27 AM, Gonzalo Salgueiro wrote:
> 1. I'm fine with the suggested edit and will update the next version
> (after IETF LC) with the suggested changes.
>
> 2. FN is a well-known identification property for vCards and does
> expand to "Full Name". Even in RFC 6350 it doesn't appear to be
> expanded, so I'll likely continue that trend and simply add a
> reference section 6.2.1 of RFC 6350 after the usage of FN to help the
> uninitiated in vCards.  Is that OK with you?

That sounds good.  Thanks for attending to my comments.

Cheers,

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

From jclarke@cisco.com  Fri Nov 30 08:41:30 2012
Return-Path: <jclarke@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 146CB21F87FF for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:41:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 7mex9npTtdnO for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:41:29 -0800 (PST)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id CEB9621F85CE for <gen-art@ietf.org>; Fri, 30 Nov 2012 08:41:28 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qAUGfOEQ013594; Fri, 30 Nov 2012 11:41:24 -0500 (EST)
Received: from dhcp-10-150-52-225.cisco.com (dhcp-10-150-52-225.cisco.com [10.150.52.225]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qAUGfOFQ028221;  Fri, 30 Nov 2012 11:41:24 -0500 (EST)
Message-ID: <50B8E1B4.80209@cisco.com>
Date: Fri, 30 Nov 2012 11:41:24 -0500
From: Joe Marcus Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Peter Saint-Andre <psaintan@cisco.com>
References: <50B8C7BD.6020504@bell-labs.com> <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com> <CCCC65B5-406D-4DD5-BBC2-89C24C2FD5FC@cisco.com>
In-Reply-To: <CCCC65B5-406D-4DD5-BBC2-89C24C2FD5FC@cisco.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, Gonzalo Salgueiro <gsalguei@cisco.com>, Cyrus Daboo <cyrus@daboo.name>, draft-salgueiro-vcarddav-kind-device@tools.ietf.org, Pete Resnick <presnick@qualcomm.com>
Subject: Re: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 16:41:30 -0000

On 11/30/12 11:37 AM, Peter Saint-Andre wrote:
> Hi Vijay and Gonzalo,
> 
> Agreed, that change in the introduction makes sense.
> 
> As to FN, how about this?
> 
> OLD
>    o  The device itself (e.g., the FN property might represent the 
>       hostname of a computing device, the URL property might represent a
>       website that contains details on where to find documentation or
>       get further information about the device, the KEY property might
>       represent a digital certificate that was provisioned into the 
>       device at the time of manufacture [IEEE.802.1AR], or a public key 
>       certificate previously provisioned into the device, and the ADR,
>       GEO, and TZ properties might represent the physical address,
>       geographical location, and timezone where the device is deployed).
> 
> NEW
>    o  The device itself. For example, the FN ("full name") property
>        ([RFC6250, section 2.1) might represent the hostname of a computing
>        device, the URL property might represent a website that contains
>        details on where to find documentation or get further information
>        about the device, the KEY property might represent a digital
>        certificate that was provisioned into the device at the time of
>         manufacture [IEEE.802.1AR], or a public key certificate previously
>        provisioned into the device, and the ADR, GEO, and TZ properties
>        might represent the physical address, geographical location, and
>        timezone where the device is deployed.

While I think you mean 6350 :-) I wonder do we need this reference?  We
don't do the same for ADR, GEO, and TZ below.  I don't mind the
parenthetical expansion.  Would that not be sufficient?

Joe

> 
> Peter
> 
> On Nov 30, 2012, at 9:27 AM, Gonzalo Salgueiro wrote:
> 
>> Vijay - 
>>
>> Good to hear from you, my friend. Hope you are well.
>>
>> Thanks for the detailed review. As for your two nits:
>>
>> 1. I'm fine with the suggested edit and will update the next version (after IETF LC) with the suggested changes.
>>
>> 2. FN is a well-known identification property for vCards and does expand to "Full Name". Even in RFC 6350 it doesn't appear to be expanded, so I'll likely continue that trend and simply add a reference section 6.2.1 of RFC 6350 after the usage of FN to help the uninitiated in vCards.  Is that OK with you?
>>
>> Cheers,
>>
>> Gonzalo
>>
>> On Nov 30, 2012, at 9:50 AM, Vijay K. Gurbani wrote:
>>
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>> Please resolve these comments along with any other Last Call comments
>>> you may receive.
>>>
>>> Document: draft-salgueiro-vcarddav-kind-device-06
>>> Reviewer: Vijay K. Gurbani
>>> Review Date: Nov-30-2012
>>> IETF LC End Date: Dec-26-2012
>>> IESG Telechat date: Unknown
>>>
>>> This document is ready as a Proposed Standard.
>>>
>>> Major: 0
>>> Minor: 0
>>> Nits: 2
>>>
>>> Nits:
>>>
>>> 1/ S1: The value "thing" sort of creeps up on you in the second
>>> paragraph.  Upon further reading, it becomes more apparent that
>>> during the WG discussions "thing" was a meta-value (or super-
>>> class) and that "application" and "device" appear to be sub-
>>> classes (or specific values) of "thing"s.
>>>
>>> Furthermore, rf6473 already defined "application" and that this
>>> particular draft is now defining "device".
>>>
>>> To better impart this information, I would suggest the following
>>> simple modification
>>>
>>> OLD:
>>> ...Working Group defined values of "individual", "org", "group", and
>>> "location" for the KIND property.  Additionally, [RFC6473] has
>>> defined a value of "application" for the KIND property to represent
>>> software applications.
>>>
>>> During working group discussion of the document that became
>>> [RFC6473], consideration was given to defining a more general value
>>> of "thing", but it was decided to split "thing" into software
>>> applications and hardware devices and to define only the
>>> "application" value at that time....
>>>
>>> NEW:
>>> ...Working Group defined values of "individual", "org", "group", and
>>> "location" for the KIND property.
>>>
>>> During working group discussion of the document that became
>>> [RFC6473], consideration was given to defining a more general value
>>> of "thing", but it was decided to split "thing" into software
>>> applications and hardware devices and to define only the
>>> "application" value at that time....
>>>
>>> 2/ S2, top of page 4: "FN" probably expands to "Full Name".  If it is
>>> an accepted practice to use "FN" in your domain, then you can leave
>>> it unexpanded.  If not, then an expansion may help the general reader
>>> (like me) who may think what "FN" is.  (The rest of the properties
>>> listed on page 4 and 5 appear to be self-explanatory).
>>>
>>> Thanks,
>>>
>>> - vijay
>>> -- 
>>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>>> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
>>> Web:   http://ect.bell-labs.com/who/vkg/
>>>
>>
> 
> 


-- 
Joe Marcus Clarke, CCIE #5384,         |          |
SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
Distinguished Services Engineer ..:|||||||||::|||||||||:..
Phone: +1 (919) 392-2867         c i s c o  S y s t e m s
Email: jclarke@cisco.com

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

From psaintan@cisco.com  Fri Nov 30 08:37:08 2012
Return-Path: <psaintan@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 A90CF21F8A43 for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:37:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e10MQXdLFagd for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:37:07 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC5121F8B24 for <gen-art@ietf.org>; Fri, 30 Nov 2012 08:37:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5031; q=dns/txt; s=iport; t=1354293427; x=1355503027; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=tsL7JoM7o2i/bEW+n5IXcy3N//Mj6xjhdG5Hl8ZPEtc=; b=jOK3UftboYbjl+L4aUboan20xowrF5VpN7rJl1OMsvToILkk54dEy/t6 UstsWHSIu1lQhOBnzZQmiyMiVsttmzZjFyhAndA8aCbBRvCc+L49mr2+E Prk7jWrW2H210e80vLsGVrbEXpKFpw4lTJNo1r/bsna7gz+HLP2Zix6J7 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,6911"; a="10044792"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 30 Nov 2012 16:37:04 +0000
Received: from [10.129.24.67] ([10.129.24.67]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id qAUGb2Bm001747; Fri, 30 Nov 2012 16:37:03 GMT
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Peter Saint-Andre <psaintan@cisco.com>
In-Reply-To: <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com>
Date: Fri, 30 Nov 2012 09:37:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CCCC65B5-406D-4DD5-BBC2-89C24C2FD5FC@cisco.com>
References: <50B8C7BD.6020504@bell-labs.com> <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Fri, 30 Nov 2012 08:51:10 -0800
Cc: Pete Resnick <presnick@qualcomm.com>, draft-salgueiro-vcarddav-kind-device@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Cyrus Daboo <cyrus@daboo.name>
Subject: Re: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 16:46:19 -0000

Hi Vijay and Gonzalo,

Agreed, that change in the introduction makes sense.

As to FN, how about this?

OLD
   o  The device itself (e.g., the FN property might represent the=20
      hostname of a computing device, the URL property might represent a
      website that contains details on where to find documentation or
      get further information about the device, the KEY property might
      represent a digital certificate that was provisioned into the=20
      device at the time of manufacture [IEEE.802.1AR], or a public key=20=

      certificate previously provisioned into the device, and the ADR,
      GEO, and TZ properties might represent the physical address,
      geographical location, and timezone where the device is deployed).

NEW
   o  The device itself. For example, the FN ("full name") property
       ([RFC6250, section 2.1) might represent the hostname of a =
computing
       device, the URL property might represent a website that contains
       details on where to find documentation or get further information
       about the device, the KEY property might represent a digital
       certificate that was provisioned into the device at the time of
        manufacture [IEEE.802.1AR], or a public key certificate =
previously
       provisioned into the device, and the ADR, GEO, and TZ properties
       might represent the physical address, geographical location, and
       timezone where the device is deployed.

Peter

On Nov 30, 2012, at 9:27 AM, Gonzalo Salgueiro wrote:

> Vijay -=20
>=20
> Good to hear from you, my friend. Hope you are well.
>=20
> Thanks for the detailed review. As for your two nits:
>=20
> 1. I'm fine with the suggested edit and will update the next version =
(after IETF LC) with the suggested changes.
>=20
> 2. FN is a well-known identification property for vCards and does =
expand to "Full Name". Even in RFC 6350 it doesn't appear to be =
expanded, so I'll likely continue that trend and simply add a reference =
section 6.2.1 of RFC 6350 after the usage of FN to help the uninitiated =
in vCards.  Is that OK with you?
>=20
> Cheers,
>=20
> Gonzalo
>=20
> On Nov 30, 2012, at 9:50 AM, Vijay K. Gurbani wrote:
>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document: draft-salgueiro-vcarddav-kind-device-06
>> Reviewer: Vijay K. Gurbani
>> Review Date: Nov-30-2012
>> IETF LC End Date: Dec-26-2012
>> IESG Telechat date: Unknown
>>=20
>> This document is ready as a Proposed Standard.
>>=20
>> Major: 0
>> Minor: 0
>> Nits: 2
>>=20
>> Nits:
>>=20
>> 1/ S1: The value "thing" sort of creeps up on you in the second
>> paragraph.  Upon further reading, it becomes more apparent that
>> during the WG discussions "thing" was a meta-value (or super-
>> class) and that "application" and "device" appear to be sub-
>> classes (or specific values) of "thing"s.
>>=20
>> Furthermore, rf6473 already defined "application" and that this
>> particular draft is now defining "device".
>>=20
>> To better impart this information, I would suggest the following
>> simple modification
>>=20
>> OLD:
>> ...Working Group defined values of "individual", "org", "group", and
>> "location" for the KIND property.  Additionally, [RFC6473] has
>> defined a value of "application" for the KIND property to represent
>> software applications.
>>=20
>> During working group discussion of the document that became
>> [RFC6473], consideration was given to defining a more general value
>> of "thing", but it was decided to split "thing" into software
>> applications and hardware devices and to define only the
>> "application" value at that time....
>>=20
>> NEW:
>> ...Working Group defined values of "individual", "org", "group", and
>> "location" for the KIND property.
>>=20
>> During working group discussion of the document that became
>> [RFC6473], consideration was given to defining a more general value
>> of "thing", but it was decided to split "thing" into software
>> applications and hardware devices and to define only the
>> "application" value at that time....
>>=20
>> 2/ S2, top of page 4: "FN" probably expands to "Full Name".  If it is
>> an accepted practice to use "FN" in your domain, then you can leave
>> it unexpanded.  If not, then an expansion may help the general reader
>> (like me) who may think what "FN" is.  (The rest of the properties
>> listed on page 4 and 5 appear to be self-explanatory).
>>=20
>> Thanks,
>>=20
>> - vijay
>> --=20
>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
>> Web:   http://ect.bell-labs.com/who/vkg/
>>=20
>=20


From psaintan@cisco.com  Fri Nov 30 08:49:11 2012
Return-Path: <psaintan@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 246E921F8B62 for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:49:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.511
X-Spam-Level: 
X-Spam-Status: No, score=-10.511 tagged_above=-999 required=5 tests=[AWL=0.089, 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 E-U-K-76VqLd for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:49:10 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 850EE21F8B48 for <gen-art@ietf.org>; Fri, 30 Nov 2012 08:49:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6138; q=dns/txt; s=iport; t=1354294149; x=1355503749; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=CF51/S8SyuyY2dY5U/zabFjLRXVAxIWPbAwfqVHzIxs=; b=XkSd1Isez0i+z/04+/u5b6Y057wZvG5rA6D5HziT2zaJT7pfQYOZ8XIz ma0noKpmc0rhptYbA8XJtoM2Y0q712trZUK35GeyrrP6q1vHLCzaDlX9O xgmHhGd3i1Go9+jDQ3/w+L4jjKp1WSyQyRGKgh+HQr9OKOrR9sTjcnPhe k=;
X-IronPort-AV: E=McAfee;i="5400,1158,6911"; a="78706835"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 30 Nov 2012 16:49:08 +0000
Received: from [10.129.24.67] ([10.129.24.67]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qAUGn72v009774; Fri, 30 Nov 2012 16:49:07 GMT
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Peter Saint-Andre <psaintan@cisco.com>
In-Reply-To: <50B8E1B4.80209@cisco.com>
Date: Fri, 30 Nov 2012 09:49:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FF960117-994A-461D-A7B7-046E81D6CD09@cisco.com>
References: <50B8C7BD.6020504@bell-labs.com> <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com> <CCCC65B5-406D-4DD5-BBC2-89C24C2FD5FC@cisco.com> <50B8E1B4.80209@cisco.com>
To: Joe Marcus Clarke <jclarke@cisco.com>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Fri, 30 Nov 2012 08:51:10 -0800
Cc: General Area Review Team <gen-art@ietf.org>, Gonzalo Salgueiro <gsalguei@cisco.com>, Cyrus Daboo <cyrus@daboo.name>, draft-salgueiro-vcarddav-kind-device@tools.ietf.org, Pete Resnick <presnick@qualcomm.com>
Subject: Re: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 16:49:11 -0000

I think only the expansion is fine. And yes, 6350. Typing too fast. :)

On Nov 30, 2012, at 9:41 AM, Joe Marcus Clarke wrote:

> On 11/30/12 11:37 AM, Peter Saint-Andre wrote:
>> Hi Vijay and Gonzalo,
>>=20
>> Agreed, that change in the introduction makes sense.
>>=20
>> As to FN, how about this?
>>=20
>> OLD
>>   o  The device itself (e.g., the FN property might represent the=20
>>      hostname of a computing device, the URL property might represent =
a
>>      website that contains details on where to find documentation or
>>      get further information about the device, the KEY property might
>>      represent a digital certificate that was provisioned into the=20
>>      device at the time of manufacture [IEEE.802.1AR], or a public =
key=20
>>      certificate previously provisioned into the device, and the ADR,
>>      GEO, and TZ properties might represent the physical address,
>>      geographical location, and timezone where the device is =
deployed).
>>=20
>> NEW
>>   o  The device itself. For example, the FN ("full name") property
>>       ([RFC6250, section 2.1) might represent the hostname of a =
computing
>>       device, the URL property might represent a website that =
contains
>>       details on where to find documentation or get further =
information
>>       about the device, the KEY property might represent a digital
>>       certificate that was provisioned into the device at the time of
>>        manufacture [IEEE.802.1AR], or a public key certificate =
previously
>>       provisioned into the device, and the ADR, GEO, and TZ =
properties
>>       might represent the physical address, geographical location, =
and
>>       timezone where the device is deployed.
>=20
> While I think you mean 6350 :-) I wonder do we need this reference?  =
We
> don't do the same for ADR, GEO, and TZ below.  I don't mind the
> parenthetical expansion.  Would that not be sufficient?
>=20
> Joe
>=20
>>=20
>> Peter
>>=20
>> On Nov 30, 2012, at 9:27 AM, Gonzalo Salgueiro wrote:
>>=20
>>> Vijay -=20
>>>=20
>>> Good to hear from you, my friend. Hope you are well.
>>>=20
>>> Thanks for the detailed review. As for your two nits:
>>>=20
>>> 1. I'm fine with the suggested edit and will update the next version =
(after IETF LC) with the suggested changes.
>>>=20
>>> 2. FN is a well-known identification property for vCards and does =
expand to "Full Name". Even in RFC 6350 it doesn't appear to be =
expanded, so I'll likely continue that trend and simply add a reference =
section 6.2.1 of RFC 6350 after the usage of FN to help the uninitiated =
in vCards.  Is that OK with you?
>>>=20
>>> Cheers,
>>>=20
>>> Gonzalo
>>>=20
>>> On Nov 30, 2012, at 9:50 AM, Vijay K. Gurbani wrote:
>>>=20
>>>> I am the assigned Gen-ART reviewer for this draft. For background =
on
>>>> Gen-ART, please see the FAQ at
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>=20
>>>> Please resolve these comments along with any other Last Call =
comments
>>>> you may receive.
>>>>=20
>>>> Document: draft-salgueiro-vcarddav-kind-device-06
>>>> Reviewer: Vijay K. Gurbani
>>>> Review Date: Nov-30-2012
>>>> IETF LC End Date: Dec-26-2012
>>>> IESG Telechat date: Unknown
>>>>=20
>>>> This document is ready as a Proposed Standard.
>>>>=20
>>>> Major: 0
>>>> Minor: 0
>>>> Nits: 2
>>>>=20
>>>> Nits:
>>>>=20
>>>> 1/ S1: The value "thing" sort of creeps up on you in the second
>>>> paragraph.  Upon further reading, it becomes more apparent that
>>>> during the WG discussions "thing" was a meta-value (or super-
>>>> class) and that "application" and "device" appear to be sub-
>>>> classes (or specific values) of "thing"s.
>>>>=20
>>>> Furthermore, rf6473 already defined "application" and that this
>>>> particular draft is now defining "device".
>>>>=20
>>>> To better impart this information, I would suggest the following
>>>> simple modification
>>>>=20
>>>> OLD:
>>>> ...Working Group defined values of "individual", "org", "group", =
and
>>>> "location" for the KIND property.  Additionally, [RFC6473] has
>>>> defined a value of "application" for the KIND property to represent
>>>> software applications.
>>>>=20
>>>> During working group discussion of the document that became
>>>> [RFC6473], consideration was given to defining a more general value
>>>> of "thing", but it was decided to split "thing" into software
>>>> applications and hardware devices and to define only the
>>>> "application" value at that time....
>>>>=20
>>>> NEW:
>>>> ...Working Group defined values of "individual", "org", "group", =
and
>>>> "location" for the KIND property.
>>>>=20
>>>> During working group discussion of the document that became
>>>> [RFC6473], consideration was given to defining a more general value
>>>> of "thing", but it was decided to split "thing" into software
>>>> applications and hardware devices and to define only the
>>>> "application" value at that time....
>>>>=20
>>>> 2/ S2, top of page 4: "FN" probably expands to "Full Name".  If it =
is
>>>> an accepted practice to use "FN" in your domain, then you can leave
>>>> it unexpanded.  If not, then an expansion may help the general =
reader
>>>> (like me) who may think what "FN" is.  (The rest of the properties
>>>> listed on page 4 and 5 appear to be self-explanatory).
>>>>=20
>>>> Thanks,
>>>>=20
>>>> - vijay
>>>> --=20
>>>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>>>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>>>> Email: vkg@{bell-labs.com,acm.org} / =
vijay.gurbani@alcatel-lucent.com
>>>> Web:   http://ect.bell-labs.com/who/vkg/
>>>>=20
>>>=20
>>=20
>>=20
>=20
>=20
> --=20
> Joe Marcus Clarke, CCIE #5384,         |          |
> SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
> Distinguished Services Engineer ..:|||||||||::|||||||||:..
> Phone: +1 (919) 392-2867         c i s c o  S y s t e m s
> Email: jclarke@cisco.com
>=20
> =
--------------------------------------------------------------------------=
--


From jclarke@cisco.com  Fri Nov 30 08:55:08 2012
Return-Path: <jclarke@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 3D80E21F8B5A for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:55:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nlF3jiepKnhM for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 08:55:07 -0800 (PST)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB3321F8B56 for <gen-art@ietf.org>; Fri, 30 Nov 2012 08:55:07 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qAUGsv9v015059; Fri, 30 Nov 2012 11:54:57 -0500 (EST)
Received: from dhcp-10-150-52-225.cisco.com (dhcp-10-150-52-225.cisco.com [10.150.52.225]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qAUGsv6N013224;  Fri, 30 Nov 2012 11:54:57 -0500 (EST)
Message-ID: <50B8E4E1.3010904@cisco.com>
Date: Fri, 30 Nov 2012 11:54:57 -0500
From: Joe Marcus Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Peter Saint-Andre <psaintan@cisco.com>
References: <50B8C7BD.6020504@bell-labs.com> <FDC22165-43F3-4FE4-A385-59BCE86FB1CF@cisco.com> <CCCC65B5-406D-4DD5-BBC2-89C24C2FD5FC@cisco.com> <50B8E1B4.80209@cisco.com> <FF960117-994A-461D-A7B7-046E81D6CD09@cisco.com>
In-Reply-To: <FF960117-994A-461D-A7B7-046E81D6CD09@cisco.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, Gonzalo Salgueiro <gsalguei@cisco.com>, Cyrus Daboo <cyrus@daboo.name>, draft-salgueiro-vcarddav-kind-device@tools.ietf.org, Pete Resnick <presnick@qualcomm.com>
Subject: Re: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 16:55:08 -0000

On 11/30/12 11:49 AM, Peter Saint-Andre wrote:
> I think only the expansion is fine. And yes, 6350. Typing too fast. :)

Cool.  So:

OLD
   o  The device itself (e.g., the FN property might represent the
      hostname of a computing device, the URL property might represent a
      website that contains details on where to find documentation or
      get further information about the device, the KEY property might
      represent a digital certificate that was provisioned into the
      device at the time of manufacture [IEEE.802.1AR], or a public key
      certificate previously provisioned into the device, and the ADR,
      GEO, and TZ properties might represent the physical address,
      geographical location, and timezone where the device is deployed).

NEW
   o  The device itself. For example, the FN ("full name") property
       might represent the hostname of a computing
       device, the URL property might represent a website that contains
       details on where to find documentation or get further information
       about the device, the KEY property might represent a digital
       certificate that was provisioned into the device at the time of
        manufacture [IEEE.802.1AR], or a public key certificate
previously
       provisioned into the device, and the ADR, GEO, and TZ properties
       might represent the physical address, geographical location, and
       timezone where the device is deployed.

Joe

> 
> On Nov 30, 2012, at 9:41 AM, Joe Marcus Clarke wrote:
> 
>> On 11/30/12 11:37 AM, Peter Saint-Andre wrote:
>>> Hi Vijay and Gonzalo,
>>>
>>> Agreed, that change in the introduction makes sense.
>>>
>>> As to FN, how about this?
>>>
>>> OLD
>>>   o  The device itself (e.g., the FN property might represent the 
>>>      hostname of a computing device, the URL property might represent a
>>>      website that contains details on where to find documentation or
>>>      get further information about the device, the KEY property might
>>>      represent a digital certificate that was provisioned into the 
>>>      device at the time of manufacture [IEEE.802.1AR], or a public key 
>>>      certificate previously provisioned into the device, and the ADR,
>>>      GEO, and TZ properties might represent the physical address,
>>>      geographical location, and timezone where the device is deployed).
>>>
>>> NEW
>>>   o  The device itself. For example, the FN ("full name") property
>>>       ([RFC6250, section 2.1) might represent the hostname of a computing
>>>       device, the URL property might represent a website that contains
>>>       details on where to find documentation or get further information
>>>       about the device, the KEY property might represent a digital
>>>       certificate that was provisioned into the device at the time of
>>>        manufacture [IEEE.802.1AR], or a public key certificate previously
>>>       provisioned into the device, and the ADR, GEO, and TZ properties
>>>       might represent the physical address, geographical location, and
>>>       timezone where the device is deployed.
>>
>> While I think you mean 6350 :-) I wonder do we need this reference?  We
>> don't do the same for ADR, GEO, and TZ below.  I don't mind the
>> parenthetical expansion.  Would that not be sufficient?
>>
>> Joe
>>
>>>
>>> Peter
>>>
>>> On Nov 30, 2012, at 9:27 AM, Gonzalo Salgueiro wrote:
>>>
>>>> Vijay - 
>>>>
>>>> Good to hear from you, my friend. Hope you are well.
>>>>
>>>> Thanks for the detailed review. As for your two nits:
>>>>
>>>> 1. I'm fine with the suggested edit and will update the next version (after IETF LC) with the suggested changes.
>>>>
>>>> 2. FN is a well-known identification property for vCards and does expand to "Full Name". Even in RFC 6350 it doesn't appear to be expanded, so I'll likely continue that trend and simply add a reference section 6.2.1 of RFC 6350 after the usage of FN to help the uninitiated in vCards.  Is that OK with you?
>>>>
>>>> Cheers,
>>>>
>>>> Gonzalo
>>>>
>>>> On Nov 30, 2012, at 9:50 AM, Vijay K. Gurbani wrote:
>>>>
>>>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>>>> Gen-ART, please see the FAQ at
>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>>
>>>>> Please resolve these comments along with any other Last Call comments
>>>>> you may receive.
>>>>>
>>>>> Document: draft-salgueiro-vcarddav-kind-device-06
>>>>> Reviewer: Vijay K. Gurbani
>>>>> Review Date: Nov-30-2012
>>>>> IETF LC End Date: Dec-26-2012
>>>>> IESG Telechat date: Unknown
>>>>>
>>>>> This document is ready as a Proposed Standard.
>>>>>
>>>>> Major: 0
>>>>> Minor: 0
>>>>> Nits: 2
>>>>>
>>>>> Nits:
>>>>>
>>>>> 1/ S1: The value "thing" sort of creeps up on you in the second
>>>>> paragraph.  Upon further reading, it becomes more apparent that
>>>>> during the WG discussions "thing" was a meta-value (or super-
>>>>> class) and that "application" and "device" appear to be sub-
>>>>> classes (or specific values) of "thing"s.
>>>>>
>>>>> Furthermore, rf6473 already defined "application" and that this
>>>>> particular draft is now defining "device".
>>>>>
>>>>> To better impart this information, I would suggest the following
>>>>> simple modification
>>>>>
>>>>> OLD:
>>>>> ...Working Group defined values of "individual", "org", "group", and
>>>>> "location" for the KIND property.  Additionally, [RFC6473] has
>>>>> defined a value of "application" for the KIND property to represent
>>>>> software applications.
>>>>>
>>>>> During working group discussion of the document that became
>>>>> [RFC6473], consideration was given to defining a more general value
>>>>> of "thing", but it was decided to split "thing" into software
>>>>> applications and hardware devices and to define only the
>>>>> "application" value at that time....
>>>>>
>>>>> NEW:
>>>>> ...Working Group defined values of "individual", "org", "group", and
>>>>> "location" for the KIND property.
>>>>>
>>>>> During working group discussion of the document that became
>>>>> [RFC6473], consideration was given to defining a more general value
>>>>> of "thing", but it was decided to split "thing" into software
>>>>> applications and hardware devices and to define only the
>>>>> "application" value at that time....
>>>>>
>>>>> 2/ S2, top of page 4: "FN" probably expands to "Full Name".  If it is
>>>>> an accepted practice to use "FN" in your domain, then you can leave
>>>>> it unexpanded.  If not, then an expansion may help the general reader
>>>>> (like me) who may think what "FN" is.  (The rest of the properties
>>>>> listed on page 4 and 5 appear to be self-explanatory).
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - vijay
>>>>> -- 
>>>>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>>>>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>>>>> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
>>>>> Web:   http://ect.bell-labs.com/who/vkg/
>>>>>
>>>>
>>>
>>>
>>
>>
>> -- 
>> Joe Marcus Clarke, CCIE #5384,         |          |
>> SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
>> Distinguished Services Engineer ..:|||||||||::|||||||||:..
>> Phone: +1 (919) 392-2867         c i s c o  S y s t e m s
>> Email: jclarke@cisco.com
>>
>> ----------------------------------------------------------------------------
> 
> 


-- 
Joe Marcus Clarke, CCIE #5384,         |          |
SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
Distinguished Services Engineer ..:|||||||||::|||||||||:..
Phone: +1 (919) 392-2867         c i s c o  S y s t e m s
Email: jclarke@cisco.com

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

From mjethanandani@gmail.com  Fri Nov 30 09:03:20 2012
Return-Path: <mjethanandani@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 0D8FB21F8B91; Fri, 30 Nov 2012 09:03:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=1.299,  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 D+6WEfo7p65A; Fri, 30 Nov 2012 09:03:19 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 31E1121F8B67; Fri, 30 Nov 2012 09:03:19 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so287371dae.31 for <multiple recipients>; Fri, 30 Nov 2012 09:03:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=6ktjHCgE6fHmvkCp91eEKkKq/y9lvt3L9CvqJFkkLDA=; b=suvHF2VUbl4aOCMeiaGD/XWXNn8UTnyzFA7r0CflY2EJ3uDM+ctJKy/j04aSpQpwrg tuEan8Dh5SEIOSn/nA7Eh+NuuN2E7uE1WqV1mI+Ybw8LRkFW9x2i00zAReoSNHAN+9+2 EyRyhIYZdG5UdKSsUX2I6KudnRODl5jElAVdHDJ1ax5hCXIw8/iFInik+zbtyFTds1tp PPNQUIHEgyeDc7eR7+W1Q3bAKRq1lfKXUKPmedRLk3p7DM7SET467eDjcrFMkJNuIp4A 4EbG4802d8ySNiM9Oy6rTZtE8C46x6+7pdMSDkWgOnbb6WVoDXEfcDygVo+cSpkJ9ceS 6koQ==
Received: by 10.66.79.133 with SMTP id j5mr4675167pax.51.1354294998955; Fri, 30 Nov 2012 09:03:18 -0800 (PST)
Received: from [192.168.1.123] (c-24-6-180-144.hsd1.ca.comcast.net. [24.6.180.144]) by mx.google.com with ESMTPS id a8sm3182035paz.18.2012.11.30.09.03.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 30 Nov 2012 09:03:18 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-4-178157723
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <F60EDDFC-0612-4636-AFC7-3D7FD9052D74@gmail.com>
Date: Fri, 30 Nov 2012 09:03:15 -0800
Message-Id: <7B7C06EA-E5EB-4FD6-ADE6-1A8E38B11405@gmail.com>
References: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com> <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com> <3B3FEC40-3D96-4F77-A628-E80DFAEB2278@nostrum.com> <F60EDDFC-0612-4636-AFC7-3D7FD9052D74@gmail.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1085)
Cc: draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-karp-routing-tcp-analysis-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: Fri, 30 Nov 2012 17:03:20 -0000

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

Ben,

See inline. If you are ok with these changes, I will go ahead and submit =
an updated version of the draft.

On Nov 25, 2012, at 5:56 PM, Mahesh Jethanandani wrote:

> Further trimming it to sections that require a response.
>=20
> On Nov 21, 2012, at 3:12 PM, Ben Campbell wrote:
>=20
>>=20
>>>>=20
>>>> *** Minor issues *** :
>>>>=20
>>>> -- section 2.2, last paragraph:
>>>>=20
>>>> The IKE mention lacks context. Do you mean to suggest IKE with =
IPSec? I assume so, but there's been no mention of IPSec so far.
>>>=20
>>> No. It implies the use of IKEv2 protocol for performing mutual =
authentication and establishing SA. There is no suggestion of using IKE =
with IPSec.
>>>=20
>>> How about this?
>>>=20
>>> For point-to-point key management IKEv2[RFC5996] protocol provides =
...
>>=20
>> 5996 describes IKEv2 as a component of IPSec, and a key-management =
mechanism for ESP and AH SAs. Now, I won't claim to be an IKE expert by =
any extent, but I think that if you mean to use IKE _without_ IPSec it =
would be good to add a sentence or two pointing that out. Or is there =
some other reference that could be used that describes using IKEv2 for =
non-IPSec SAs?
>=20
> Added this sentence.
>=20
> Although IKEv2 is discussed as a component of IPsec, KMP can use just =
the mutual authentication and SA establishment portion of IKEv2.

This statement has been further modified to:

For point-to-point key management IKEv2 [RFC5996] provides for
 automated key exchange under a SA and can be used for a comprehensive
 Key Management Protocol (KMP) solution for routers.  IKEv2 can be used
 for both IPsec SAs [RFC4301] and other types of SAs. For example,=20
 Fibre Channel SAs  [RFC4595] are currently negotiated with IKEv2. Using
 IKEv2 to negotiate TCP-AO is a possible option.


>=20
>>=20
>>>=20
>>>>=20
>>>> *** Nits/editorial comments ***:
>>>>=20
>>>> -- IDNits indicates some unused and obsoleted references. Please =
check.
>>>=20
>>> Found one unused reference and have removed it.
>>=20
>> Seems like there were more than one. =46rom IDNits:
>>=20
>>  =3D=3D Missing Reference: 'IRR' is mentioned on line 92, but not =
defined
>>=20
>>  =3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit
>>     reference was found in the text
>>=20
>>  =3D=3D Unused Reference: 'RFC3547' is defined on line 588, but no =
explicit
>>     reference was found in the text
>>=20
>>  ** Obsolete normative reference: RFC 2385 (Obsoleted by RFC 5925)
>>=20
>>  -- Obsolete informational reference (is this intentional?): RFC 2409
>>     (Obsoleted by RFC 4306)
>>=20
>>  -- Obsolete informational reference (is this intentional?): RFC 3547
>>     (Obsoleted by RFC 6407)
>=20
> I have removed these unused references.
>=20
>>=20
>>>>=20
>>>> -- section 4, 2nd paragraph: "In addition Improving TCP=92s =
Robustness to Blind In-Window Attacks."
>>>>=20
>>>> sentence fragment.
>>>=20
>>> Changed it to say:
>>>=20
>>> In addition, the recommendations in Improving TCP's Robustness to =
Blind In-Window Attacks
>>>=20
>>=20
>> Am I correct in assuming this merges with the following sentence? =
Otherwise, it's still a fragment.
>>=20
>=20
> Changed it to:
>=20
> In addition, the recommendations in RFC 5961 should also be followed =
...

Mahesh Jethanandani
mjethanandani@gmail.com




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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Ben,<div><br></div><div>See inline. If you are ok with these changes, =
I will go ahead and submit an updated version of the =
draft.<div><br><div><div>On Nov 25, 2012, at 5:56 PM, Mahesh =
Jethanandani wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Further trimming it to sections =
that require a response.<div><br><div><div>On Nov 21, 2012, at 3:12 PM, =
Ben Campbell wrote:</div><br><blockquote =
type=3D"cite"><div><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">*** Minor issues *** =
:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- section 2.2, last =
paragraph:<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">The IKE mention lacks context. =
Do you mean to suggest IKE with IPSec? I assume so, but there's been no =
mention of IPSec so far.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">No. It implies =
the use of IKEv2 protocol for performing mutual authentication and =
establishing SA. There is no suggestion of using IKE with =
IPSec.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">How about =
this?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">For =
point-to-point key management IKEv2[RFC5996] protocol provides =
...<br></blockquote><br>5996 describes IKEv2 as a component of IPSec, =
and a key-management mechanism for ESP and AH SAs. Now, I won't claim to =
be an IKE expert by any extent, but I think that if you mean to use IKE =
_without_ IPSec it would be good to add a sentence or two pointing that =
out. Or is there some other reference that could be used that describes =
using IKEv2 for non-IPSec =
SAs?<br></div></blockquote><div><br></div>Added this =
sentence.</div><div><br></div><div><i>Although IKEv2 is discussed as a =
component of IPsec, KMP can use just the mutual authentication and SA =
establishment portion of =
IKEv2.</i></div></div></div></blockquote><div><br></div>This statement =
has been further modified to:</div><div><br></div><div><i>For =
point-to-point key management IKEv2 [RFC5996] provides =
for</i><div><i>&nbsp;automated key exchange under a SA and can be used =
for a comprehensive</i></div><div><i>&nbsp;Key Management Protocol (KMP) =
solution for routers. &nbsp;IKEv2 can be used</i></div><div><i>&nbsp;for =
both IPsec SAs [RFC4301] and other types of SAs. For =
example,&nbsp;</i></div><div><i>&nbsp;Fibre Channel&nbsp;SAs =
&nbsp;[RFC4595] are currently negotiated with IKEv2. =
Using</i></div><div><i>&nbsp;IKEv2 to negotiate TCP-AO is a possible =
option.</i></div></div><div><br></div><div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><div><br><blockquote type=3D"cite"><div><br><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">*** Nits/editorial comments =
***:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- IDNits indicates some unused =
and obsoleted references. Please =
check.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Found one =
unused reference and have removed it.<br></blockquote><br>Seems like =
there were more than one. =46rom IDNits:<br><br> &nbsp;=3D=3D Missing =
Reference: 'IRR' is mentioned on line 92, but not defined<br><br> =
&nbsp;=3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit<br> &nbsp;&nbsp;&nbsp;&nbsp;reference was found in the =
text<br><br> &nbsp;=3D=3D Unused Reference: 'RFC3547' is defined on line =
588, but no explicit<br> &nbsp;&nbsp;&nbsp;&nbsp;reference was found in =
the text<br><br> &nbsp;** Obsolete normative reference: RFC 2385 =
(Obsoleted by RFC 5925)<br><br> &nbsp;-- Obsolete informational =
reference (is this intentional?): RFC 2409<br> =
&nbsp;&nbsp;&nbsp;&nbsp;(Obsoleted by RFC 4306)<br><br> &nbsp;-- =
Obsolete informational reference (is this intentional?): RFC 3547<br> =
&nbsp;&nbsp;&nbsp;&nbsp;(Obsoleted by RFC =
6407)<br></div></blockquote><div><br></div>I have removed these unused =
references.</div><div><br><blockquote type=3D"cite"><div><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- section 4, 2nd paragraph: "In =
addition Improving TCP=92s Robustness to Blind In-Window =
Attacks."<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">sentence =
fragment.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Changed it to =
say:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">In addition, =
the recommendations in Improving TCP's Robustness to Blind In-Window =
Attacks<br></blockquote><blockquote type=3D"cite"><br></blockquote><br>Am =
I correct in assuming this merges with the following sentence? =
Otherwise, it's still a =
fragment.<br><br></div></blockquote><br></div><div>Changed it =
to:</div><div><br></div><div><i>In addition, the recommendations in RFC =
5961 should also be followed =
...</i></div></div></div></blockquote></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>Mahesh =
Jethanandani</div><div><a =
href=3D"mailto:mjethanandani@gmail.com">mjethanandani@gmail.com</a></div><=
div><br></div></span><br class=3D"Apple-interchange-newline">
</div>
<br></div></div></body></html>=

--Apple-Mail-4-178157723--

From vkg@bell-labs.com  Fri Nov 30 09:16:05 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 680E221F8965 for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 09:16:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.599
X-Spam-Level: 
X-Spam-Status: No, score=-108.599 tagged_above=-999 required=5 tests=[AWL=2.000, 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 kqcVJkscy7Ty for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 09:16:04 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE0A21F88C7 for <gen-art@ietf.org>; Fri, 30 Nov 2012 09:16:02 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id qAUHFsQN016518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 30 Nov 2012 11:15:55 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qAUHFscs015714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 30 Nov 2012 11:15:54 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qAUHFrJZ019869; Fri, 30 Nov 2012 11:15:54 -0600 (CST)
Message-ID: <50B8EA20.9080408@bell-labs.com>
Date: Fri, 30 Nov 2012 11:17:20 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <50B8C7BD.6020504@bell-labs.com> <50B8E915.4060600@qti.qualcomm.com>
In-Reply-To: <50B8E915.4060600@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: Cyrus Daboo <cyrus@daboo.name>, draft-salgueiro-vcarddav-kind-device@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 17:16:05 -0000

On 11/30/2012 11:12 AM, Pete Resnick wrote:
[...]
> Do I understand correctly that you simply want to delete the sentence,
> "Additionally, [RFC6473] has defined a value of "application" for the
> KIND property to represent software applications."?

Pete: Yes.

> I can put the two changes (this one, and the one suggest by PSA as
> edited by Joe) in the RFC Editor notes of the tracker for the moment.
> Who know, maybe a miracle will occur and these will be the only changes
> between Last Call and IESG Evaluation. :-)

Thanks,

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

From presnick@qti.qualcomm.com  Fri Nov 30 09:12:59 2012
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 404C421F88C7 for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 09:12:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, 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 K0rDMpIwBu0s for <gen-art@ietfa.amsl.com>; Fri, 30 Nov 2012 09:12:57 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB6C21F8965 for <gen-art@ietf.org>; Fri, 30 Nov 2012 09:12:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1354294618; x=1385830618; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=rvf/nbDys1jELPyzYSNdJ2ZzwuqInWT9i7rM+G/TvbE=; b=D3hqxVAiEpInq45L4yznsLs++wWBzrT9ytcwRuiytZ9aTZi0PP8BKKDr IBhChen6VHi7Xd2E4GYmy/MLmW29ezn1vZVFJeonPmWZZEgjfe+v3mHaI c2z+hrOqCKNw2KWcHWSTKqacBlfG1IW1mzWqn0ZHetRSBXwQwapwJ6BVK s=;
X-IronPort-AV: E=McAfee;i="5400,1158,6911"; a="9875979"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth01.qualcomm.com with ESMTP; 30 Nov 2012 08:56:57 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6911"; a="376872747"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 30 Nov 2012 09:12:56 -0800
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 30 Nov 2012 09:12:56 -0800
Message-ID: <50B8E915.4060600@qti.qualcomm.com>
Date: Fri, 30 Nov 2012 11:12:53 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
References: <50B8C7BD.6020504@bell-labs.com>
In-Reply-To: <50B8C7BD.6020504@bell-labs.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
X-Mailman-Approved-At: Fri, 30 Nov 2012 09:23:03 -0800
Cc: Cyrus Daboo <cyrus@daboo.name>, draft-salgueiro-vcarddav-kind-device@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-salgueiro-vcarddav-kind-device-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, 30 Nov 2012 17:12:59 -0000

On 11/30/12 8:50 AM, Vijay K. Gurbani wrote:

> OLD:
>  ...Working Group defined values of "individual", "org", "group", and
>  "location" for the KIND property.  Additionally, [RFC6473] has
>  defined a value of "application" for the KIND property to represent
>  software applications.
>
>  During working group discussion of the document that became
>  [RFC6473], consideration was given to defining a more general value
>  of "thing", but it was decided to split "thing" into software
>  applications and hardware devices and to define only the
>  "application" value at that time....
>
>  NEW:
>  ...Working Group defined values of "individual", "org", "group", and
>  "location" for the KIND property.
>
>  During working group discussion of the document that became
>  [RFC6473], consideration was given to defining a more general value
>  of "thing", but it was decided to split "thing" into software
>  applications and hardware devices and to define only the
>  "application" value at that time....

Do I understand correctly that you simply want to delete the sentence, 
"Additionally, [RFC6473] has defined a value of "application" for the 
KIND property to represent software applications."?

I can put the two changes (this one, and the one suggest by PSA as 
edited by Joe) in the RFC Editor notes of the tracker for the moment. 
Who know, maybe a miracle will occur and these will be the only changes 
between Last Call and IESG Evaluation. :-)

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

