
From Johannes.Merkle@secunet.com  Tue Jul  2 05:24:00 2013
Return-Path: <Johannes.Merkle@secunet.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB7C711E8106; Tue,  2 Jul 2013 05:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F95jR3mT7OOr; Tue,  2 Jul 2013 05:23:56 -0700 (PDT)
Received: from a.mx.secunet.com (a.mx.secunet.com [195.81.216.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8794411E80A2; Tue,  2 Jul 2013 05:23:56 -0700 (PDT)
Received: from localhost (alg1 [127.0.0.1]) by a.mx.secunet.com (Postfix) with ESMTP id 479D81A0084; Tue,  2 Jul 2013 14:23:54 +0200 (CEST)
X-Virus-Scanned: by secunet
Received: from a.mx.secunet.com ([127.0.0.1]) by localhost (a.mx.secunet.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HEfdQQ3hfsdN; Tue,  2 Jul 2013 14:23:51 +0200 (CEST)
Received: from mail-srv1.secumail.de (unknown [10.53.40.200]) by a.mx.secunet.com (Postfix) with ESMTP id EB0C01A0085; Tue,  2 Jul 2013 14:23:51 +0200 (CEST)
Received: from [10.208.1.73] ([10.208.1.73]) by mail-srv1.secumail.de with Microsoft SMTPSVC(6.0.3790.4675); Tue, 2 Jul 2013 14:23:51 +0200
Message-ID: <51D2C656.3080608@secunet.com>
Date: Tue, 02 Jul 2013 14:23:50 +0200
From: Johannes Merkle <johannes.merkle@secunet.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
References: <048001ce755d$505996e0$f10cc4a0$@gmail.com>
In-Reply-To: <048001ce755d$505996e0$f10cc4a0$@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 02 Jul 2013 12:23:52.0016 (UTC) FILETIME=[031BAD00:01CE771F]
Cc: gen-art@ietf.org, ietf@ietf.org, draft-merkle-tls-brainpool.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-merkle-tls-brainpool-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, 02 Jul 2013 12:24:00 -0000

a new version addressing your review is on its way.

Johannes


Roni Even schrieb am 30.06.2013 08:44:
> 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-merkle-tls-brainpool-02
> 
> Reviewer: Roni Even
> 
> Review Date:2013𤖭0
> 
> IETF LC End Date: 2013-7�23
> 
> IESG Telechat date:
> 
>  
> 
> Summary: This draft is almost ready for publication as Standard track RFC.
> 
>  
> 
>  
> 
> Major issues:
> 
>  
> 
> Minor issues:
> 
>  
> 
> In section 1 you reference TLS 1.0 and 1.1 usage based on RFC 4492. What about TLS 1.2 usage specified in RFC5246 A.7
> 
>  
> 
>  
> 
>  
> 
> Nits/editorial comments:
> 
>  1. In section 3 the  registry name is EC Named Curve
>  2. In section 3 change 搒uitability� to 搒uitable�
> 
>  
> 


-- 

Mit freundlichen Gren,
Dr. Johannes Merkle
Principal Beratung, Elektronische Identit鋞en
Public Sector
secunet Security Networks AG
Mergenthaler Allee 77
65760 Eschborn
Germany
Telefon +49 201 54 54-3091
Telefax +49 201 54 54-1325
Mobil   +49 175 2224439
johannes.merkle@secunet.com
www.secunet.com

From Francis.Dupont@fdupont.fr  Tue Jul  2 10:37:27 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD48321F9B7F for <gen-art@ietfa.amsl.com>; Tue,  2 Jul 2013 10:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J9Gv+4eMe2bZ for <gen-art@ietfa.amsl.com>; Tue,  2 Jul 2013 10:37:27 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 2A25321F9B7E for <gen-art@ietf.org>; Tue,  2 Jul 2013 10:37:27 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r62HbPKL002198; Tue, 2 Jul 2013 19:37:25 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201307021737.r62HbPKL002198@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: curtis@ipv6.occnc.com
In-reply-to: Your message of Thu, 27 Jun 2013 14:02:51 EDT. <201306271802.r5RI2qOw096500@gateway1.orleans.occnc.com> 
Date: Tue, 02 Jul 2013 19:37:25 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: gen-art@ietf.org, draft-ietf-rtgwg-cl-requirement.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-rtgwg-cl-requirement-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2013 17:37:28 -0000

 In your previous mail you wrote:

>  > Minor issues: None
>  
>  OK.  Thanks but it appears the document is headed back to another WGLC
>  due to other comments, mostly due to the RtgDir review comments.

=> yes, I saw that.

>  > Nits/editorial comments:
>  >  - ToC page 3 and 7 page 12: Acknowledgements -> Acknowledgments
>  
>  It appears that both spellings are acceptable according to my spell
>  checker.  I will leave as is unless there is continued objection.

=> Acknowledgements is UK English, Acknowledgments is US English.
The usage is more for US English but anyway it is something for
the RFC Editor...

>  >  - 3 page 5 (component link): the term NPO is used before being defined
>  >  
>  >  - 3 page 5 (component link): expand the WDM abbrev -- not well known
>  >   according tothe RFC Editor list:
>  >   http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
>  >  
>  >  - 3 page 5 (flow identification): same for the PW abbrev
>  
>  A last call comment from our AD is to expand all acronyms before use.
>  The SecDir comments also requested this.

=> not a bad policy anyway even the official one makes this optional
for well known acronyms (the acronyms with a star in the list, e.g.,
it is not really required to expand TCP/IP :-).

>  I will also do a full spell check and see what else the spell checker
>  find.  (I am using International Ispell Version 3.3.02 12 Jun 2005
>  with English and American English dictionary files).

=> I use the same but by default with only the American English one
(even I have the UK and of course the French (from France) dicts too).

Thanks

Francis.Dupont@fdupont.fr

From tterribe@xiph.org  Tue Jul  2 11:00:40 2013
Return-Path: <tterribe@xiph.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 E30AC21F9B07 for <gen-art@ietfa.amsl.com>; Tue,  2 Jul 2013 11:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VZ24yvs3fvqO for <gen-art@ietfa.amsl.com>; Tue,  2 Jul 2013 11:00:23 -0700 (PDT)
Received: from smtp.mozilla.org (mx2.corp.phx1.mozilla.com [63.245.216.70]) by ietfa.amsl.com (Postfix) with ESMTP id 6913921F9BCB for <gen-art@ietf.org>; Tue,  2 Jul 2013 11:00:23 -0700 (PDT)
Received: from [10.250.6.54] (unknown [63.245.220.240]) (Authenticated sender: tterriberry@mozilla.com) by mx2.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id 223B9F22FA;  Tue,  2 Jul 2013 11:00:23 -0700 (PDT)
Message-ID: <51D31536.1080300@xiph.org>
Date: Tue, 02 Jul 2013 11:00:22 -0700
From: "Timothy B. Terriberry" <tterribe@xiph.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 SeaMonkey/2.16.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  draft-ietf-avtcore-avp-codecs.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
References: <51C3D88D.5090500@gmail.com>
In-Reply-To: <51C3D88D.5090500@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 02 Jul 2013 13:08:16 -0700
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-avtcore-avp-codecs-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2013 18:00:41 -0000

Brian E Carpenter wrote:
> According to normal practice, the abstract should also specifically mention RFC 3551:
>
> "This document updates the RTP/AVP profile (RFC 3551)..."

Thanks Brian, done.

From Francis.Dupont@fdupont.fr  Tue Jul  2 14:36:17 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C738411E80E4 for <gen-art@ietfa.amsl.com>; Tue,  2 Jul 2013 14:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ki7Qu6SlrQ8X for <gen-art@ietfa.amsl.com>; Tue,  2 Jul 2013 14:36:17 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 1626E11E80E0 for <gen-art@ietf.org>; Tue,  2 Jul 2013 14:36:16 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r62LaFLJ017480; Tue, 2 Jul 2013 23:36:15 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201307022136.r62LaFLJ017480@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Varun Singh <varun@comnet.tkk.fi>
In-reply-to: Your message of Fri, 28 Jun 2013 01:52:41 +0300. <0871C7A1-0F51-4A1B-B025-80782DACC372@comnet.tkk.fi> 
Date: Tue, 02 Jul 2013 23:36:15 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: gen-art@ietf.org, draft-ietf-xrblock-rtcp-xr-discard-rle-metrics.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-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: Tue, 02 Jul 2013 21:36:17 -0000

 In your previous mail you wrote:

>  > - 1 page 3: take benefit of the first "Extended Reports" to introduce
>  > the XR abbrev
>  
>  It is in the title, but I've expanded it at first occurrence in text.

=> the convention is to consider the title and the abstract as other
independent parts of the document.

>  > - 1 page 3: playout > play out (according to my spell checker)
>  
>  In multimedia we often use: playout buffer, playout delay.
>  But in this case playout is acting more as a verb instead of a noun.
>  Anyone else have an opinion about this?

=> I agree it is a common term: this is why I added "according to
my spell checker"... BTW this should typically be handled by the
RFC Editor.

Thanks

Francis.Dupont@fdupont.fr

From gonzalo.camarillo@ericsson.com  Thu Jul  4 23:00:06 2013
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C775921F9BD0 for <gen-art@ietfa.amsl.com>; Thu,  4 Jul 2013 23:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.611
X-Spam-Level: 
X-Spam-Status: No, score=-105.611 tagged_above=-999 required=5 tests=[AWL=0.638, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtqtDXaddBU3 for <gen-art@ietfa.amsl.com>; Thu,  4 Jul 2013 22:59:58 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id CEF2F21F9BDB for <gen-art@ietf.org>; Thu,  4 Jul 2013 22:59:56 -0700 (PDT)
X-AuditID: c1b4fb25-b7f826d000001766-0e-51d660db6dbd
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 7C.ED.05990.BD066D15; Fri,  5 Jul 2013 07:59:55 +0200 (CEST)
Received: from [131.160.126.156] (153.88.183.148) by smtp.internal.ericsson.com (153.88.183.41) with Microsoft SMTP Server id 14.2.328.9; Fri, 5 Jul 2013 07:59:55 +0200
Message-ID: <51D660DA.4030903@ericsson.com>
Date: Fri, 5 Jul 2013 08:59:54 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@fdupont.fr>
References: <201307022136.r62LaFLJ017480@givry.fdupont.fr>
In-Reply-To: <201307022136.r62LaFLJ017480@givry.fdupont.fr>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUyM+Jvre7thGuBBg9/6FpM39HPZvFo2k5W i6uvPrNYzDjB4cDicXbZVCaPd1P/sHosWfKTyePL5c9sASxRXDYpqTmZZalF+nYJXBmLPpxn L7jIXrFh/0LGBsZHrF2MnBwSAiYSu1+1M0HYYhIX7q1n62Lk4hASOMwosW/dflYIZw2jxI8/ J5hBqngFtCUuLDvGDmKzCKhI3D54ixHEZhOwkNhy6z4LiC0qECXR2jsVql5Q4uTMJ2BxEQE9 iXdXD7KDDGUWaGCUuLrqFpDDwSEs4COxa64/SI2QgJXE3vVH2EBsTgFriTW3njBDXCcpseVF O9heZqA5U662MELY8hLb385hhujVllj+rIVlAqPQLCSrZyFpmYWkZQEj8ypG9tzEzJz0cqNN jMCQPrjlt+oOxjvnRA4xSnOwKInzbtY7EygkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBMUJF oHPK69KYzg2BK9V+1Rfrbv7v6aj4TXyZXI+5QcCFp1ZVb9kXq1dYLvUJ7Wx4aeYrJ2TSuW7a +rhlxx/aub00evGQo8P+76dzNyQmbNnjWbLvUsfUo4WLn0/VE5e63Tvh3A3VKRvn8KlpiTy1 7dTZtuvK7ZkeO8VjQgx/SKz+ZvH419wbr5VYijMSDbWYi4oTAbdgNlA3AgAA
Cc: gen-art@ietf.org, Varun Singh <varun@comnet.tkk.fi>, draft-ietf-xrblock-rtcp-xr-discard-rle-metrics.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-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, 05 Jul 2013 06:00:07 -0000

Authors,

could you please revise the draft in order to address the comments you
have received?

Thanks,

Gonzalo

On 03/07/2013 12:36 AM, Francis Dupont wrote:
>  In your previous mail you wrote:
> 
>>  > - 1 page 3: take benefit of the first "Extended Reports" to introduce
>>  > the XR abbrev
>>  
>>  It is in the title, but I've expanded it at first occurrence in text.
> 
> => the convention is to consider the title and the abstract as other
> independent parts of the document.
> 
>>  > - 1 page 3: playout > play out (according to my spell checker)
>>  
>>  In multimedia we often use: playout buffer, playout delay.
>>  But in this case playout is acting more as a verb instead of a noun.
>>  Anyone else have an opinion about this?
> 
> => I agree it is a common term: this is why I added "according to
> my spell checker"... BTW this should typically be handled by the
> RFC Editor.
> 
> Thanks
> 
> Francis.Dupont@fdupont.fr
> 


From peter@akayla.com  Fri Jul  5 15:35:02 2013
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 1F22921F99D9 for <gen-art@ietfa.amsl.com>; Fri,  5 Jul 2013 15:35:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OW9F75LVivRK for <gen-art@ietfa.amsl.com>; Fri,  5 Jul 2013 15:34:57 -0700 (PDT)
Received: from m1plsmtpa01-06.prod.mesa1.secureserver.net (m1plsmtpa01-06.prod.mesa1.secureserver.net [64.202.165.34]) by ietfa.amsl.com (Postfix) with ESMTP id A47F521F8497 for <gen-art@ietf.org>; Fri,  5 Jul 2013 15:34:19 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by m1plsmtpa01-06.prod.mesa1.secureserver.net with  id wmaF1l0031huGat01maFq4; Fri, 05 Jul 2013 15:34:16 -0700
From: "Peter Yee" <peter@akayla.com>
To: <gen-art@ietf.org>
Date: Fri, 5 Jul 2013 15:34:21 -0700
Message-ID: <024c01ce79cf$cbbf34e0$633d9ea0$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_024D_01CE7995.1F605CE0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac55z1JueRlwwZiZRLyKtPNChAnSTg==
Content-Language: en-us
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-07-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, 05 Jul 2013 22:35:02 -0000

This is a multipart message in MIME format.

------=_NextPart_000_024D_01CE7995.1F605CE0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 

The following reviewers have assignments:

 

Reviewer          LC end       Draft

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

Ben Campbell      2013-07-18  draft-ietf-jcardcal-jcard-04

 

Brian Carpenter   2013-07-15  draft-ietf-lisp-deployment-08

 

David Black       2013-07-18  draft-ietf-trill-directory-framework

 

Elwyn Davies      2013-07-17  draft-ietf-dhc-dhcpv6-failover-requirements-06

 

Wassim Haddad     2013-07-31   draft-housley-ltans-oids-00

 

Contact me if you have any issues with the assignments.  I tried to follow
Jean's directions!

 

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,

 

Peter

 

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

 

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:

 

_______________________________________________

Gen-art mailing list

Gen-art@ietf.org

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

 


------=_NextPart_000_024D_01CE7995.1F605CE0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>The following reviewers have =
assignments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Reviewer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LC =
end&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Draft<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
--<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span style=3D'font-family:"Courier =
New"'>Ben Campbell&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-07-18&nbsp; =
draft-ietf-jcardcal-jcard-04<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span style=3D'font-family:"Courier =
New"'>Brian Carpenter&nbsp;&nbsp; 2013-07-15&nbsp; =
draft-ietf-lisp-deployment-08<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span style=3D'font-family:"Courier =
New"'>David Black &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2013-07-18&nbsp; =
draft-ietf-trill-directory-framework<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-family:"Courier New"'>Elwyn Davies =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2013-07-17&nbsp; =
draft-ietf-dhc-dhcpv6-failover-requirements-06<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-family:"Courier New"'>Wassim =
Haddad&nbsp;&nbsp;&nbsp;&nbsp; 2013-07-31&nbsp;&nbsp; =
draft-housley-ltans-oids-00<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span style=3D'font-family:"Courier =
New"'>Contact me if you have any issues with the assignments.&nbsp; I =
tried to follow Jean&#8217;s directions!<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>I have =
made the assignments in the review tool:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>http://art.tools.ietf.org/tools/art/genart/<o:p></o:p></span></p><p=
 class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>And the assignments are captured in =
the spreadsheets:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>http://wiki.tools.ietf.org/dav/genart/gen-art.html<o:p></o:p></span=
></p><p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>The standard template is included =
below.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Thanks,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Peter<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<o:=
p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Please =
resolve these comments along with any other Last Call comments you may =
receive.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Document:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Reviewer:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Review =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IETF LC End =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IESG Telechat date: (if =
known)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Summary:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Nits/editorial comments:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>_______________________________________________<o:p></o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Gen-art mailing list<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Gen-art@ietf.org<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>https://www.ietf.org/mailman/listinfo/gen-art<o:p></o:p></span></p>=
<p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_024D_01CE7995.1F605CE0--


From peter@akayla.com  Fri Jul  5 16:12:34 2013
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 622DF21F9DEF for <gen-art@ietfa.amsl.com>; Fri,  5 Jul 2013 16:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.732
X-Spam-Level: 
X-Spam-Status: No, score=-1.732 tagged_above=-999 required=5 tests=[AWL=0.866,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JNcrfPtehYP8 for <gen-art@ietfa.amsl.com>; Fri,  5 Jul 2013 16:12:29 -0700 (PDT)
Received: from p3plsmtpa07-08.prod.phx3.secureserver.net (p3plsmtpa07-08.prod.phx3.secureserver.net [173.201.192.237]) by ietfa.amsl.com (Postfix) with ESMTP id 87BA221F962D for <gen-art@ietf.org>; Fri,  5 Jul 2013 16:12:29 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-08.prod.phx3.secureserver.net with  id wnCU1l0011huGat01nCUNz; Fri, 05 Jul 2013 16:12:28 -0700
From: "Peter Yee" <peter@akayla.com>
To: <gen-art@ietf.org>
Date: Fri, 5 Jul 2013 16:12:34 -0700
Message-ID: <026801ce79d5$225c91d0$6715b570$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0269_01CE799A.76002AD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac550z9ZgMA6+nqBRJOTgIcWFWIISg==
Content-Language: en-us
Subject: [Gen-art] Assignments for the 2013-07-11 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: Fri, 05 Jul 2013 23:12:34 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0269_01CE799A.76002AD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 

This is an update from last week's list.

 

The following reviewers have assignments:

 

Reviewer               LC end     Draft

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

Ben Campbell           2013-06-25     draft-thornburgh-adobe-rtmfp-09 *

 

Joel Halpern           2013-06-19
draft-ietf-ospf-manet-single-hop-mdr-03 **

 

Joel Halpern           2013-07-01     draft-ietf-straw-b2bua-taxonomy-02 **

 

Kathleen Moriarty      2013-06-28
draft-ietf-ipfix-protocol-rfc5101bis-08 **

 

Peter Yee              2013-06-27     draft-ietf-appsawg-rfc5451bis-09 *

 

Suresh Krishnan        2013-01-21     draft-ietf-lisp-mib-11 * (Reassigned
from Miguel Garcia)

 

Wassim Haddad          2013-06-27     draft-ietf-l2vpn-pbb-vpls-pe-model-07

 

* Earlier draft reviewed

** Already reviewed

 

 

 

I have made the assignments in the review tool:

 <http://art.tools.ietf.org/tools/art/genart/>
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.html

 <http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.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/>
http://wiki.tools.ietf.org/area/gen/trac/wiki/

 

Peter

 

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

 

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

 

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

 

Document:

Reviewer:

Review Date:

IETF LC End Date:

IESG Telechat date: (if known)

 

Summary:

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

_______________________________________________

Gen-art mailing list

 <mailto:Gen-art@ietf.org> Gen-art@ietf.org

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


------=_NextPart_000_0269_01CE799A.76002AD0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>This is an update from last =
week&#8217;s list.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>The =
following reviewers have assignments:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>Reviewer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; LC end&nbsp;&nbsp;&nbsp;&nbsp; =
Draft<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
-----------------<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Ben =
Campbell&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2013-06-25 &nbsp;&nbsp;&nbsp;&nbsp;draft-thornburgh-adobe-rtmfp-09 =
*<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Joel =
Halpern&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2013-06-19 =
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-ospf-manet-single-hop-mdr-03 =
**<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Joel =
Halpern&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2013-07-01 &nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-straw-b2bua-taxonomy-02 =
**<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Kathleen =
Moriarty&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-06-28 =
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-ipfix-protocol-rfc5101bis-08 =
**<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Peter =
Yee&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; 2013-06-27 =
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-appsawg-rfc5451bis-0<span =
style=3D'color:#1F497D'>9</span> *<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Suresh =
Krishnan&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-01-21 =
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-lisp-mib-11 * (Reassigned from Miguel =
Garcia)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Wassim =
Haddad&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2013-06-27 =
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-l2vpn-pbb-vpls-pe-model-07<o:p></o:p><=
/span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>* Earlier =
draft reviewed<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>** Already =
reviewed<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>I have =
made the assignments in the review tool:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'><a =
href=3D"http://art.tools.ietf.org/tools/art/genart/"><span =
style=3D'color:windowtext;text-decoration:none'>http://art.tools.ietf.org=
/tools/art/genart/</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>And the assignments are captured in =
the spreadsheets:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><a =
href=3D"http://wiki.tools.ietf.org/dav/genart/gen-art.html"><span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/dav/genart/gen-art.html</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'><a =
href=3D"http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html"><=
span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/dav/genart/gen-art-by-reviewer.html</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>For your convenience, the review =
boilerplate template is included below.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Note that reviews should ideally be =
posted to the gen-art mailing list by COB on =
Tuesday:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/"><span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/area/gen/trac/wiki/</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Peter<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>-------------------------------------------------------------------=
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt; <a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"><span =
style=3D'color:windowtext;text-decoration:none'>http://wiki.tools.ietf.or=
g/area/gen/trac/wiki/GenArtfaq</span></a>&gt;.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Please wait for direction from your =
document shepherd or AD before posting a new version of the =
draft.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Document:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>Reviewer:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Review =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IETF LC End =
Date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>IESG Telechat date: (if =
known)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Summary:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Nits/editorial comments:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New"'>_______________________________________________<o:p></o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'>Gen-art mailing list<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'><a =
href=3D"mailto:Gen-art@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>Gen-art@ietf.org</span></=
a><o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><a =
href=3D"https://www.ietf.org/mailman/listinfo/gen-art"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/gen-art</span></a><o:p></o:p></span></p></div></body></html>
------=_NextPart_000_0269_01CE799A.76002AD0--


From elwynd@dial.pipex.com  Sat Jul  6 06:05:30 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D15021F9A5E for <gen-art@ietfa.amsl.com>; Sat,  6 Jul 2013 06:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.599
X-Spam-Level: 
X-Spam-Status: No, score=-97.599 tagged_above=-999 required=5 tests=[AWL=5.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k1dVYGtGUENM for <gen-art@ietfa.amsl.com>; Sat,  6 Jul 2013 06:05:29 -0700 (PDT)
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 43A7F21F9798 for <gen-art@ietf.org>; Sat,  6 Jul 2013 06:05:29 -0700 (PDT)
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 1UvSB0-0008N1-PY; Sat, 06 Jul 2013 14:05:26 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Sat, 06 Jul 2013 14:01:37 +0100
Message-Id: <1373115697.4524.42154.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: draft-ietf-dhc-dhcpv6-failover-requirements.all@tools.ietf.org
Subject: [Gen-art] Gen-art LC review: draft-ietf-dhc-dhcpv6-failover-requirements-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: Sat, 06 Jul 2013 13:05:30 -0000

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

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

Document: draft-ietf-dhc-dhcpv6-failover-requirements-06.txt
Reviewer: Elwyn Davies
Review Date: 6 July 2013
IETF LC End Date: 17 July 2013
IESG Telechat date: (if known) -

Summary: Almost ready.  There are a few very minor issues and a fair
number of editorial nits to fix but generally in good shape.

Major issues:
None

Minor issues:
s1, Introduction of Primary/Secondary terminology: The introduction
talks about multiple servers (i.e., potentially > 2) but then in the
last sentence of para 1 introduces primary and secondary servers.  The
initial impression this gives is that the number of servers has now been
reduced to <= 2.  Having read through the rest of the document I can see
how I am supposed to interpret the last sentence of para 1, but things
would be much clearer if an extra sentence or three describing the
chosen model (and its intended extension) was added just before this
last sentence.  Maybe something like:
   The failover model, to which these requirements apply, will initially
   be a pairwise "hot standby" model (see Section 4.1) with a primary 
   server used in normal operation switching over to a backup secondary 
   server in the event of failure.  Optionally, a secondary server may 
   provide failover service for multiple primary servers.  However the 
   requirements will not preclude a future load-balancing extension 
   where there is a symmetric failover relationship. 

s7: Related to the previous comment, perhaps it should be made explicit
that the resulting protocol is "load-balancing friendly" to avoid rework
if at all possible.  Since both v4 and v6 load-balancing and v4 failover
with load-balancing are in progress, it should be known how to avoid
pitfalls by the time the v6 failover protocol is designed!

s7, item 4, last sentence: 
"Long-lived connections must not be disturbed."
I don't believe the DHCPv6 server or the failover protocol can either
know that an address is in use for long lived connections or guarantee
that they won't be disturbed beyond what is said earlier in this item.
Presumably what is meant is something like: "Lease stability has the aim
of avoiding disturbance to long-lived connections."

s7, item 6:  Maybe irrelevant thought: Presumably you could build a
failover system using a shared, reliable database and a minimalistic
version of the failover protocol instead of using lazy updates.  Should
this be explicitly an option?

s7, last para: "Despite the lack of standardization of DHCPv4
failover...": It appears that work is in progress on this
(http://tools.ietf.org/html/draft-ietf-dhc-failover-12)... so what is
meant here?

Nits/editorial comments:

Global: s/i.e./i.e.,/
Global: s/e.g./e.g.,/

Abstract: s/any way/any way that/

s2: Expoand acronyms CPR, IA - even though IA is defined in RFC 3315, it
would help readability to repeat the expansion.

s2, lease: Should this mention something about length of time for which
the lease will be valid?

s3.1.1: Expand PXE acronym.

s3.1.1, para 1:
OLD
   Address and possibly other
   configuration parameters are used during boot process and are
   discarded afterwards. 
NEW:
   The address and possibly other
   configuration parameters are used during the boot process and are
   discarded thereafter. 

s3.1.1, para 2: s/distinct preference set/a distinct preference set/

s3.1.2, para 2:
OLD:
   There are several well documented approaches how such deployment
   works. 
NEW:
   There are several well-documented approaches showing how such a deployment
   could work.

s3.1.3, para 2:
OLD:
   It is also essential to use only databases that are really
   distributed and do not have single point of failure themselves.
NEW:
   It is also essential to use only a database system that provides 
   equivalent reliability and failover capability. 

s4: This paragraph implies that the document defines a protocol contrary
to its expressed intention and reality.
OLD:
   These scenarios may be inside or
   outside of scope for DHCPv6 failover protocol as defined by this
   document.  They are enumerated here to provide a common basis for
   discussion.
NEW:
   These scenarios may be in or
   out of scope for the DHCPv6 failover model to which this 
   document's requirements apply; they are enumerated here to provide a 
   common basis for discussion.   

s5, para 2: s/General failover concept/The general failover concept/, 
s/in case of the primary server/in case of a primary server/,
s/In case of just/In the case of just/,
s/Had there be more than two partners/Were there more than two partners/
(subjunctive!)

s5, para 2:
OLD:
   there would be a third states in between (some
   partners updated their state, but some didn't).
NEW:
   there would be intermediate, inconsistent states where some partners
   had updated their state and some had not.

s4.1: s/Only one of partners/Only one of the partners/

s4.6, para 2: s/every time IPv6 address changes/every time an IPv6
address changes/

s4.6, para 3: s/having stable address/having a stable address/

s5.1, last sentence:  This seems to imply that *this section* states
whether the failure mode is in or out of scope for the protocol.  It
doesn't - that is postponed to s7.  Either remove this sentence or
redraft to refer to s7.

s5.1.2, para 2: s/is that partner also detected/is that the partner also
detected/

s5.2: s/synchronization methods/synchronization method/,
s/familiarity with distributed database/familiarity with distributed database technology/

s5.2.1, para 1: s/response from partner/response from its partner/

s5.2.1, para 2: 'large' is an over-generalization. Maybe:
s/a large performance penalty/typically a significant performance penalty/

s5.2.1, para 3:
OLD:
Due to advent of SSD disks or battery backed ram disks technology,
NEW:
Due to the advent of fast SSD (solid state disk) and battery-backed RAM 
(random access memory) disk technology,

s5.2.2, para 2: s/if server crashes/if the server crashes/

s7, item 4: s/should pose/should have/


From peter@akayla.com  Sun Jul  7 20:21:44 2013
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 B768C21F9DE6; Sun,  7 Jul 2013 20:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g+CcFJkQMRwp; Sun,  7 Jul 2013 20:21:40 -0700 (PDT)
Received: from p3plsmtpa11-03.prod.phx3.secureserver.net (p3plsmtpa11-03.prod.phx3.secureserver.net [68.178.252.104]) by ietfa.amsl.com (Postfix) with ESMTP id AE01821F8D0D; Sun,  7 Jul 2013 20:21:39 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa11-03.prod.phx3.secureserver.net with  id xfMd1l0011huGat01fMdwi; Sun, 07 Jul 2013 20:21:38 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-jabley-dnsext-eui48-eui64-rrtypes.all@tools.ietf.org>
Date: Sun, 7 Jul 2013 20:21:36 -0700
Message-ID: <02fe01ce7b8a$41f2af50$c5d80df0$@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: Ac57iWpUND76SWuaRiWlOdeUt9Gl4g==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-jabley-dnsext-eui48-eui64-rrtypes-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, 08 Jul 2013 03:21:44 -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-jabley-dnsext-eui48-eui64-rrtypes-05
Reviewer: Peter Yee
Review Date: July-07-2013
IETF LC End Date: July-17-2013
IESG Telechat date: August-15-2013

Summary: This draft is basically ready for publication as an Informational
RFC, but has nits that should be fixed before publication. [Ready with nits]

This draft defines DNS Resources Record Types for encoding IEEE 802 EUI-48
and EUI-64 addresses.  Potential privacy issues with this scheme have been
soundly beaten to death with extreme prejudice.

Major issues:

Minor issues:

Nits:

Page 1, Abstract, 1st paragraph: After "e.g.", append a comma and delete an
extraneous space before "Ethernet".

Page 3, Introduction, 1st paragraph, 2nd sentence: change "This" to "These"
and change "specification defines" to "specifications define". 

Page 3, Introduction, 2nd paragraph: append a comma after "e.g.".

		-Peter Yee




From peter@akayla.com  Sun Jul  7 22:39:04 2013
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 5C7E611E8186; Sun,  7 Jul 2013 22:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level: 
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[AWL=0.520,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ab0b1qYJB-0x; Sun,  7 Jul 2013 22:38:59 -0700 (PDT)
Received: from p3plsmtpa09-07.prod.phx3.secureserver.net (p3plsmtpa09-07.prod.phx3.secureserver.net [173.201.193.236]) by ietfa.amsl.com (Postfix) with ESMTP id 426A011E8189; Sun,  7 Jul 2013 22:38:59 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-07.prod.phx3.secureserver.net with  id xheu1l0041huGat01heuhU; Sun, 07 Jul 2013 22:38:55 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org>
Date: Sun, 7 Jul 2013 22:38:53 -0700
Message-ID: <030301ce7b9d$6f821100$4e863300$@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: Ac57nWUOX1k3nDvKSfOr8IcedY5lqw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-appsawg-rfc5451bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2013 05:39: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-appsawg-rfc5451bis-09
Reviewer: Peter Yee
Review Date: July-01-2013
IETF LC End Date: June-27-2013
IESG Telechat date: July-11-2013

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

This draft defines a message header for conveying message authentication
outcomes from various, existing email authentication standards.  The draft
is well-written with numerous worked out examples.

Major issues:

Minor issues:

Nits:

Page 4, Introduction, 5th paragraph: append a comma after "published".

Page 5, 2nd paragraph after bullet item, 1st sentence: change "pre-standards
DomainKeys defined" to "pre-standard DomainKeys-defined".

Page 6, 2nd paragraph, last sentence: change "their data center" to "its
data center".

Page 6, section 1.3, 2nd sentence: change "encapsualted" to "encapsulated".

Page 7, section 1.5.2, 1st paragraph after bullet points, 2nd sentence: add
commas after "agents" and "authorization)".  Also change "ensures" to
"ensure".

Page 14, section 2.5, 4th sentence: insert ", but" between "document" and
"intended".

Page 17, Section 2.5.5: amend "Authorhized" to "Authorized".

Page 19, 2nd full paragraph, 2nd sentence: "finite" is probably not the best
word to use here.  Perhaps "not unduly taxing to the DNS infrastructure"
would work better?

Page 19, section 4, title: change "A" to "a".

Page 19, section 4, 1st paragraph, second sentence: change "THe" to "The".

Page 20, 2nd full paragraph, 1st sentence: append a comma after "applied".

Page 20, 5th full paragraph, 3rd sentence: insert "placement" between "This"
and "allows".

Page 20, 5th full paragraph, 3rd sentence: regarding whether the field can
be "trusted": why would the MUA check the field in any other location than
prior to the top-most trace field?  If the location is the source of
trustedness, then the MUA shouldn't be checking it anywhere else, right?

Page 22, first full paragraph, 1st sentence: replace "which" with "that".

Page 22, 3rd full paragraph: "this" is an ambiguous reference.  Maybe use
"these topics" or "these issues" if you mean everything in the section?

Page 23, 1st paragraph, last sentence: for clarity, consider inserting "the
header field originating from" between "removing" and "all".

Page 23, 4th paragraph:  as the MTA (implied to be an MTA within the ADMD)
is not the end consumer of the information and the MUA might understand a
later version of the header, shouldn't the decision to remove (or
essentially ignore) the header be made by the MUA?

Page 31, section 8.4, 2nd sentence: change "need" to "needs".

Page 32, section 8.6, 3rd sentence: regarding keeping the list "current",
how about using a new RRType in the DNS?

Page 39, section C.4: the "Received" header would make it look like the
message is going from example.net to example.com, but the "To" and "From"
headers show the opposite to be the case.

Page 39, section C.4: the same issue strikes the paragraph immediately
following Example 4.  The "sending DNS" name is what appears for the
authserv-id, not the "receiving DNS" name.  A simple swap of the "To" and
"From" header values would rectify the situation.

Page 43, 2nd paragraph, 2nd sentence: change "that" to "whom".

Page 44, item 1, 2nd sentence: delete the "s" in "rejections".

Page 44, item 3, 1st sentence: append a comma after "header".

Page 45, item 5, 3rd sentence: change "vs" to "vs."  and append a comma
after "intertia".

		-Peter Yee


From superuser@gmail.com  Mon Jul  8 00:13:41 2013
Return-Path: <superuser@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAC6211E81A0; Mon,  8 Jul 2013 00:13:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mkNGWYoQ+h3P; Mon,  8 Jul 2013 00:13:39 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5F26211E8190; Mon,  8 Jul 2013 00:13:25 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id k10so8693106wiv.1 for <multiple recipients>; Mon, 08 Jul 2013 00:13:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZcE4bJTzebcoiwEnzGGJbNUKkOpj+7W7H1+EBVJJ6g0=; b=wJGWX9MZe/jq/yRx0sOU6PGTHg/cApHByCbCNKPa6c4rKb2/InqbKluO5rN8WO+0AX L2uVGcXX/Ww+HzLzwZapzU21smF+XSvf740RhypiNncsQvHohVdLAMXdtnH3nhwZl7cq ZyyVnO67Cy7wEbeYAN58t0WBtLZDFRhrI5UrmipeGQHQcmK1SqW3NGovy3jMzLIOGtU6 ltMkNTvCVQiR2LJD07mrsfQuDnf7+1oUkpu24yVR0kjFF56f7xyqjRiUnK30yzcLXl2s V4pZmuZfMoY/77HtEBRK9Ffjh0fd/PWoiVwyV7zA+bV7nWQQt2pd0n1kLQckuHBiE04U 2nHg==
MIME-Version: 1.0
X-Received: by 10.194.239.225 with SMTP id vv1mr11458954wjc.63.1373267603336;  Mon, 08 Jul 2013 00:13:23 -0700 (PDT)
Received: by 10.180.90.16 with HTTP; Mon, 8 Jul 2013 00:13:23 -0700 (PDT)
In-Reply-To: <030301ce7b9d$6f821100$4e863300$@akayla.com>
References: <030301ce7b9d$6f821100$4e863300$@akayla.com>
Date: Mon, 8 Jul 2013 00:13:23 -0700
Message-ID: <CAL0qLwbaGGJ_indZfn4QZjLoRwNyQw4K5DB0QN3L4Ju0L_oAMQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Peter Yee <peter@akayla.com>
Content-Type: multipart/alternative; boundary=089e01493384adb7d504e0fac7f3
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org, ietf <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-appsawg-rfc5451bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2013 07:13:41 -0000

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

Hi Peter, thanks for the review.  Comments inline:

On Sun, Jul 7, 2013 at 10:38 PM, Peter Yee <peter@akayla.com> wrote:

> Page 5, 2nd paragraph after bullet item, 1st sentence: change
> "pre-standards
> DomainKeys defined" to "pre-standard DomainKeys-defined".
>

This doesn't seem to work.  The sentence is basically "SPF defined X and
DomainKeys defined Y."  "defined" is a verb, not an adjective, so I don't
think the hyphen is appropriate.


>
> Page 20, 5th full paragraph, 3rd sentence: regarding whether the field can
> be "trusted": why would the MUA check the field in any other location than
> prior to the top-most trace field?  If the location is the source of
> trustedness, then the MUA shouldn't be checking it anywhere else, right?
>

At the time the work on RFC5451 was originally done, here were some
implementations of a plugin API that were not able to prepend trace header
fields, and could only append them.  Moreover, an MUA or other agent might
be configured to trust A-R fields added in more than one place (e.g., a
trusted filter), so trusting only the top-most one would limit that
possibility.


>
> Page 23, 4th paragraph:  as the MTA (implied to be an MTA within the ADMD)
> is not the end consumer of the information and the MUA might understand a
> later version of the header, shouldn't the decision to remove (or
> essentially ignore) the header be made by the MUA?
>

Good point.  I'll add a note about this.


>
> Page 32, section 8.6, 3rd sentence: regarding keeping the list "current",
> how about using a new RRType in the DNS?
>

That's certainly one option to solve that problem. However, I'd prefer not
to suggest new mechanisms that haven't been deployed yet.

I'll post the rest in a -10 revision after the telechat, or if directed to
do so sooner.

Thanks again,
-MSK

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

<div dir=3D"ltr">Hi Peter, thanks for the review.=A0 Comments inline:<br><d=
iv class=3D"gmail_extra"><br>On Sun, Jul 7, 2013 at 10:38 PM, Peter Yee <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:peter@akayla.com" target=3D"_blank">pe=
ter@akayla.com</a>&gt;</span> wrote:<br>
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Page 5, 2nd parag=
raph after bullet item, 1st sentence: change &quot;pre-standards<br>
DomainKeys defined&quot; to &quot;pre-standard DomainKeys-defined&quot;.<br=
></blockquote><div><br></div><div>This doesn&#39;t seem to work.=A0 The sen=
tence is basically &quot;SPF defined X and DomainKeys defined Y.&quot;=A0 &=
quot;defined&quot; is a verb, not an adjective, so I don&#39;t think the hy=
phen is appropriate.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
Page 20, 5th full paragraph, 3rd sentence: regarding whether the field can<=
br>
be &quot;trusted&quot;: why would the MUA check the field in any other loca=
tion than<br>
prior to the top-most trace field? =A0If the location is the source of<br>
trustedness, then the MUA shouldn&#39;t be checking it anywhere else, right=
?<br></blockquote><div><br></div><div>At the time the work on RFC5451 was o=
riginally done, here were some implementations of a plugin API that were no=
t able to prepend trace header fields, and could only append them.=A0 Moreo=
ver, an MUA or other agent might be configured to trust A-R fields added in=
 more than one place (e.g., a trusted filter), so trusting only the top-mos=
t one would limit that possibility.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
Page 23, 4th paragraph: =A0as the MTA (implied to be an MTA within the ADMD=
)<br>
is not the end consumer of the information and the MUA might understand a<b=
r>
later version of the header, shouldn&#39;t the decision to remove (or<br>
essentially ignore) the header be made by the MUA?<br></blockquote><div><br=
></div><div>Good point.=A0 I&#39;ll add a note about this.<br>=A0<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">

<br>
Page 32, section 8.6, 3rd sentence: regarding keeping the list &quot;curren=
t&quot;,<br>
how about using a new RRType in the DNS?<br></blockquote><div><br></div><di=
v>That&#39;s certainly one option to solve that problem. However, I&#39;d p=
refer not to suggest new mechanisms that haven&#39;t been deployed yet. <br=
>
<br></div><div>I&#39;ll post the rest in a -10 revision after the telechat,=
 or if directed to do so sooner.<br><br></div><div>Thanks again,<br></div><=
div>-MSK<br></div></div></div></div>

--089e01493384adb7d504e0fac7f3--

From peter@akayla.com  Mon Jul  8 00:22:09 2013
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 058D811E81A9; Mon,  8 Jul 2013 00:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.165
X-Spam-Level: 
X-Spam-Status: No, score=-2.165 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ZsZUeR-O73O; Mon,  8 Jul 2013 00:22:03 -0700 (PDT)
Received: from p3plsmtpa11-09.prod.phx3.secureserver.net (p3plsmtpa11-09.prod.phx3.secureserver.net [68.178.252.110]) by ietfa.amsl.com (Postfix) with ESMTP id E7DC611E81AB; Mon,  8 Jul 2013 00:21:49 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa11-09.prod.phx3.secureserver.net with  id xjMi1l0081huGat01jMiqJ; Mon, 08 Jul 2013 00:21:44 -0700
From: "Peter Yee" <peter@akayla.com>
To: "'Murray S. Kucherawy'" <superuser@gmail.com>
References: <030301ce7b9d$6f821100$4e863300$@akayla.com> <CAL0qLwbaGGJ_indZfn4QZjLoRwNyQw4K5DB0QN3L4Ju0L_oAMQ@mail.gmail.com>
In-Reply-To: <CAL0qLwbaGGJ_indZfn4QZjLoRwNyQw4K5DB0QN3L4Ju0L_oAMQ@mail.gmail.com>
Date: Mon, 8 Jul 2013 00:21:42 -0700
Message-ID: <030801ce7bab$cca088e0$65e19aa0$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0309_01CE7B71.2042C250"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFQvfcxhikEpypLQc81LDoJCpyLfwHKw+5rmkeDluA=
Content-Language: en-us
Cc: 'General Area Review Team' <gen-art@ietf.org>, draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org, 'ietf' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-appsawg-rfc5451bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2013 07:22:09 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0309_01CE7B71.2042C250
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Murray,

                Quick response!  My replies are found below.

 

                Thanks.

 

                                -Peter

 

From: Murray S. Kucherawy [mailto:superuser@gmail.com] 
Sent: Monday, July 08, 2013 12:13 AM
To: Peter Yee
Cc: draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org; General Area Review
Team; ietf
Subject: Re: Gen-ART Telechat review of draft-ietf-appsawg-rfc5451bis-09

 

Hi Peter, thanks for the review.  Comments inline:


On Sun, Jul 7, 2013 at 10:38 PM, Peter Yee <peter@akayla.com> wrote:

Page 5, 2nd paragraph after bullet item, 1st sentence: change "pre-standards
DomainKeys defined" to "pre-standard DomainKeys-defined".

 

This doesn't seem to work.  The sentence is basically "SPF defined X and
DomainKeys defined Y."  "defined" is a verb, not an adjective, so I don't
think the hyphen is appropriate.

 

Hmm.  Yup, I misread that.  Just ignore the hyphen part of the comment.
 

Page 20, 5th full paragraph, 3rd sentence: regarding whether the field can
be "trusted": why would the MUA check the field in any other location than
prior to the top-most trace field?  If the location is the source of
trustedness, then the MUA shouldn't be checking it anywhere else, right?

 

Page 32, section 8.6, 3rd sentence: regarding keeping the list "current",
how about using a new RRType in the DNS?

 

That's certainly one option to solve that problem. However, I'd prefer not
to suggest new mechanisms that haven't been deployed yet. 

Fair enough.

I'll post the rest in a -10 revision after the telechat, or if directed to
do so sooner.

Thanks again,

-MSK


------=_NextPart_000_0309_01CE7B71.2042C250
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Murray,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Quick response! &nbsp;My replies are found =
below.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Thanks.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-Peter<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Murray S. Kucherawy [mailto:superuser@gmail.com] <br><b>Sent:</b> =
Monday, July 08, 2013 12:13 AM<br><b>To:</b> Peter Yee<br><b>Cc:</b> =
draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org; General Area Review =
Team; ietf<br><b>Subject:</b> Re: Gen-ART Telechat review of =
draft-ietf-appsawg-rfc5451bis-09<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Hi =
Peter, thanks for the review.&nbsp; Comments =
inline:<o:p></o:p></p><div><p class=3DMsoNormal><br>On Sun, Jul 7, 2013 =
at 10:38 PM, Peter Yee &lt;<a href=3D"mailto:peter@akayla.com" =
target=3D"_blank">peter@akayla.com</a>&gt; =
wrote:<o:p></o:p></p><div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><p class=3DMsoNormal>Page 5, =
2nd paragraph after bullet item, 1st sentence: change =
&quot;pre-standards<br>DomainKeys defined&quot; to &quot;pre-standard =
DomainKeys-defined&quot;.<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>This doesn't seem to work.&nbsp; The sentence is =
basically &quot;SPF defined X and DomainKeys defined Y.&quot;&nbsp; =
&quot;defined&quot; is a verb, not an adjective, so I don't think the =
hyphen is appropriate.<span =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hmm.&nbsp; Yup, I misread that.&nbsp; Just ignore the hyphen part of =
the comment.</span><br>&nbsp;<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><p class=3DMsoNormal>Page 20, =
5th full paragraph, 3rd sentence: regarding whether the field can<br>be =
&quot;trusted&quot;: why would the MUA check the field in any other =
location than<br>prior to the top-most trace field? &nbsp;If the =
location is the source of<br>trustedness, then the MUA shouldn't be =
checking it anywhere else, right?<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><p class=3DMsoNormal>Page 32, =
section 8.6, 3rd sentence: regarding keeping the list =
&quot;current&quot;,<br>how about using a new RRType in the =
DNS?<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>That's certainly one option to solve that =
problem. However, I'd prefer not to suggest new mechanisms that haven't =
been deployed yet. <o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Fair enough.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>I'll post the rest in a -10 revision =
after the telechat, or if directed to do so =
sooner.<o:p></o:p></p></div><div><p class=3DMsoNormal>Thanks =
again,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>-MSK<o:p></o:p></p></div></div></div></div></div></body=
></html>
------=_NextPart_000_0309_01CE7B71.2042C250--


From david.black@emc.com  Mon Jul  8 13:44:31 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B91621F9E18; Mon,  8 Jul 2013 13:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYiHA9L0gMKd; Mon,  8 Jul 2013 13:44:26 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 798DA21F9E0D; Mon,  8 Jul 2013 13:44:24 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r68KhwW7016168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Jul 2013 16:44:07 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 8 Jul 2013 16:43:43 -0400
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r68Khg2q012722; Mon, 8 Jul 2013 16:43:43 -0400
Received: from mxhub40.corp.emc.com (128.222.70.107) by mxhub12.corp.emc.com (10.254.92.107) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 8 Jul 2013 16:43:42 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub40.corp.emc.com ([128.222.70.107]) with mapi; Mon, 8 Jul 2013 16:43:42 -0400
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "stefan.winter@restena.lu" <stefan.winter@restena.lu>, "jsalowey@cisco.com" <jsalowey@cisco.com>, General Area Review Team <gen-art@ietf.org>
Date: Mon, 8 Jul 2013 16:43:41 -0400
Thread-Topic: Gen-ART review of draft-ietf-abfab-eapapplicability-04
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgQTfgIg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712983F2C87@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-abfab-eapapplicability-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2013 20:44:31 -0000

The -04 version of this draft resolves the minor issue noted in
the Gen-ART review of the -03 version.

There is a remaining editorial nit, in that the one use of
"non-network" in the -04 version would benefit from clarification.
I suggest the following text change to the start of the paragraph
that's split across pages 3 and 4 (change is to last line of excerpt):

OLD
   Operators need to carefully consider the security implications before
   relaxing these requirements.  One potentially serious attack exists
   when channel binding is not required and EAP authentication is
   introduced into an existing non-network service.

NEW
   Operators need to carefully consider the security implications before
   relaxing these requirements.  One potentially serious attack exists
   when channel binding is not required and EAP authentication is
   introduced into an existing service other than network access.
=09
Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Monday, June 17, 2013 10:39 PM
> To: stefan.winter@restena.lu; jsalowey@cisco.com; General Area Review Tea=
m
> Cc: ietf@ietf.org; abfab@ietf.org; Black, David
> Subject: Gen-ART review of draft-ietf-abfab-eapapplicability-03
>=20
> 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-abfab-eapapplicability-03
> Reviewer: David L. Black
> Review Date: June 17, 2003
> IETF LC End Date: June 17, 2003
>=20
> Summary:
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> This draft updates the applicability statement for EAP to include usage
> for application layer access via EAP over GSSAPI.  Additional security
> requirements are introduced for environments in which EAP is used for
> that purpose.
>=20
> I found one open issue, which is minor, and may be editorial
>=20
> Major issues: None
>=20
> Minor issues: One
>=20
> The next to last paragraph on p.3 begins with this sentence:
>=20
>    For these reasons, channel binding MUST be implemented by peers, EAP
>    servers and AAA servers in environments where EAP authentication is
>    used to access application layer services.
>=20
> It appear that this "MUST" requirement applies to all uses of EAP,
> including network access authentication, not just application layer acces=
s
> authentication.  If so, that's not immediately obvious from the text, and
> an additional sentence should be added to make this clearer.  If not,
> the above sentence needs to exclude network access authentication from
> that requirement.
>=20
> Nits/editorial comments:
>=20
> The same paragraph (p.3) continues with:
>=20
>    In addition, channel
>    binding MUST default to being required by peers for non-network
>    authentication.  If the EAP server is aware that authentication is
>    for something other than a network service, it too MUST default to
>    requiring channel binding.
>=20
> What is meant by "non-network authentication" and "other than a network
> service"?  If those mean "other than for network access authentication"
> as the term "network access authentication" is used in section 1 and
> RFC 3748, that meaning should be clarified.
>=20
> idnits 2.12.17 generated this comment:
>=20
>   -- The document seems to lack a disclaimer for pre-RFC5378 work, but ma=
y
>      have content which was first submitted before 10 November 2008.  If =
you
>      have contacted all the original authors and they are all willing to =
grant
>      the BCP78 rights to the IETF Trust, then this is fine, and you can i=
gnore
>      this comment.  If not, you may need to add the pre-RFC5378 disclaime=
r.
>      (See the Legal Provisions document at
>      http://trustee.ietf.org/license-info for more information.)
>=20
> idnits appears to be confused ;-).  The -00 version of this draft is from
> 2012,
> and this draft does not contain sufficient material from RFC 3748 that wo=
uld
> raise that concern, so this comment should be ok to ignore.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From ben@nostrum.com  Tue Jul  9 12:58:55 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207D321F9D80; Tue,  9 Jul 2013 12:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ezttndz4pXIg; Tue,  9 Jul 2013 12:58:54 -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 C17D521F9CAD; Tue,  9 Jul 2013 12:58:53 -0700 (PDT)
Received: from [10.0.1.12] (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 r69JwpgG051378 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Jul 2013 14:58:52 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Jul 2013 14:58:51 -0500
Message-Id: <AE51780A-646A-4C82-9DAD-8557B06C75A5@nostrum.com>
To: "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review of draft-thornburgh-adobe-rtmfp-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2013 19:58: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>.
=20
Please wait for direction from your document shepherd or AD before =
posting a new version of the draft.
=20
Document: draft-thornburgh-adobe-rtmfp-09
Reviewer: Ben Campbell
Review Date: 2013-07-09
IESG Telechat date: 2013-07-11
=20
Summary: This draft is essentially ready for publication as an =
informational RFC. There is one issue from my previous review and =
related discussion that I think is almost, but not completely handled. =
All other concerns from my previous review have been addressed in this =
version.
=20
Major issues:
=20
There has been a fair amount of discussion about how this protocol =
requires a crypto profile to interoperate, and no such profiles are =
included, or otherwise widely published. If this were a standards track =
draft, I would argue for at least one mandatory-to-implement profile to =
be included or referenced. But since this is intended as an =
informational RFC that simply describes what certain products are doing, =
that's probably okay.  Furthermore, the author added a paragraph to the =
introduction specifically calling out the issue, which I applaud.=20

But I'd like to see that paragraph go a bit further, and explicitly =
mention any such profile needed to interoperate with the commercial =
products mentioned in the 2nd paragraph of section 1 has not been made =
available at the time of RFC publication, and that implementors should =
investigate the availability of such a profile prior to implementing =
this protocol for the purposes of interoperating with those products.

Minor issues:

None.

Nits/editorial comments:

None.=

From vishwas.manral@hp.com  Tue Jul  9 15:00:06 2013
Return-Path: <vishwas.manral@hp.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A42C11E818F for <gen-art@ietfa.amsl.com>; Tue,  9 Jul 2013 15:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtO2X-j9VPVY for <gen-art@ietfa.amsl.com>; Tue,  9 Jul 2013 14:59:52 -0700 (PDT)
Received: from g6t0186.atlanta.hp.com (g6t0186.atlanta.hp.com [15.193.32.63]) by ietfa.amsl.com (Postfix) with ESMTP id EE34A11E8195 for <gen-art@ietf.org>; Tue,  9 Jul 2013 14:58:55 -0700 (PDT)
Received: from G6W4001.americas.hpqcorp.net (g6w4001.atlanta.hp.com [16.205.80.210]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g6t0186.atlanta.hp.com (Postfix) with ESMTPS id F16932C4B2; Tue,  9 Jul 2013 21:58:54 +0000 (UTC)
Received: from G5W5499.americas.hpqcorp.net (16.201.144.179) by G6W4001.americas.hpqcorp.net (16.205.80.210) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 9 Jul 2013 21:58:05 +0000
Received: from G5W2732.americas.hpqcorp.net ([169.254.4.124]) by G5W5499.americas.hpqcorp.net ([16.201.144.179]) with mapi id 14.03.0123.003; Tue, 9 Jul 2013 21:58:06 +0000
From: "Manral, Vishwas" <vishwas.manral@hp.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, "draft-ietf-ipsecme-ad-vpn-problem.all@tools.ietf.org" <draft-ietf-ipsecme-ad-vpn-problem.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat review of draft-ietf-ipsecme-ad-vpn-problem-07.txt
Thread-Index: AQHOcQ84fjwvVmfREk63wI1zJUppw5lc9xew
Date: Tue, 9 Jul 2013 21:58:04 +0000
Message-ID: <5A9E892C56FD5842856290BDA06E12A00B7338F7@G5W2732.americas.hpqcorp.net>
References: <51C89A1D.10404@ericsson.com>
In-Reply-To: <51C89A1D.10404@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [16.201.12.21]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 09 Jul 2013 15:02:16 -0700
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-ipsecme-ad-vpn-problem-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2013 22:00:09 -0000

Hi Suresh,

Good comments.

* Section 2.3

The following sentence is a bit confusing. How does a mobile user
connect to a new gateway without reinitiating a connection? Can you
please clarify or reword.

"The mobile user ought to be able to discover and then connect to the
current most efficient gateway without having to reinitiate the connection.=
"
VM> The idea here is that the connection doesn't get reinitiated and is nev=
er down, we move the connection between 2 IPsec gateways. I have changed th=
e text as I see where you are coming from.

VM> A mobile user roaming on the Internet may connect to a gateway, which b=
ecause of roaming is no longer the most efficient gateway to use (reasons c=
ould be cost/ efficiency/ latency or some other factor). The mobile user ou=
ght to be able to discover and then connect to the current most efficient g=
ateway in a seamless way          without having to bring down the connecti=
on.

* Section 4.1. Requirement 5

Shouldn't there be a requirement here that states what kind of damage is
allowed and prohibited in case a hub node is compromised?
VM> The Hub is the central point in my view, which leads to the single poin=
t of failure. I think the solution will allow for multiple hubs (HP DVPN so=
lution already does) and it uses AES-256 encryption etc. I think these howe=
ver are elements of the implementation, not requirements.=20

VM> I added the following as a requirement:
     There ADVPN solution SHOULD take care of now letting the Hub to be a s=
ingle point of failure

* Section 4.1. Requirement 12

It is unclear what this requirement means. Is the requirement for the
solution to integrate with multicast routing protocols to come up with a
different (and optimized) multicast ADVPN topology or to simply allow
the advpn to carry (flattened out) multicast traffic?
VM> General solutions uses Multiple unicast as broadcast and that does not =
scale. What we are mentioning here is that the solution for traffic does no=
t scale. The document that's why says:

VM>       The ADVPN solution SHOULD be able to scale for multicast traffic.

* Section 4.1. Requirement 14

Are there any special requirements that L3VPN poses on top of what is
required for carrying generic IP traffic? If so, can you elaborate here.
VM> No there are no special requirements. We got the comment from Lou Berge=
r who felt we should explicitly state the same as the solution will be used=
 in L3VPN use cases too. This is so that we do not exclude a use case when =
thinking of the solution.

Thanks,
Vishwas



From mthornbu@adobe.com  Tue Jul  9 15:09:44 2013
Return-Path: <mthornbu@adobe.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 911E211E817C; Tue,  9 Jul 2013 15:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vU+9n1ttO6uJ; Tue,  9 Jul 2013 15:09:37 -0700 (PDT)
Received: from exprod6og111.obsmtp.com (exprod6og111.obsmtp.com [64.18.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB9D11E8175; Tue,  9 Jul 2013 15:09:35 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob111.postini.com ([64.18.5.12]) with SMTP ID DSNKUdyKFSXa5o+m18yy7oGztmueyi6/2Sjt@postini.com; Tue, 09 Jul 2013 15:09:36 PDT
Received: from inner-relay-1.corp.adobe.com (inner-relay-1.corp.adobe.com [153.32.1.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r69M9NAI008831; Tue, 9 Jul 2013 15:09:23 -0700 (PDT)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r69M2g6I018016; Tue, 9 Jul 2013 15:09:21 -0700 (PDT)
Received: from nambx08.corp.adobe.com ([10.8.189.94]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Tue, 9 Jul 2013 15:03:24 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: Ben Campbell <ben@nostrum.com>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>
Date: Tue, 9 Jul 2013 15:03:23 -0700
Thread-Topic: Gen-ART Telechat Review of draft-thornburgh-adobe-rtmfp-09
Thread-Index: Ac583sYXYAi/c8CwRiingf+U1YZ89QADR/hA
Message-ID: <D9D602D39A98E34D9C43E965BEC74398261AB600@nambx08.corp.adobe.com>
References: <AE51780A-646A-4C82-9DAD-8557B06C75A5@nostrum.com>
In-Reply-To: <AE51780A-646A-4C82-9DAD-8557B06C75A5@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-thornburgh-adobe-rtmfp-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2013 22:09:44 -0000

hi Ben.

your "like to see" is entirely reasonable, and the following text will be i=
n the next revision once my AD or Document Shepherd directs me to post it:

   Note to implementers: at the time of writing, the Cryptography
   Profile used by the above mentioned Adobe products is not publicly
   described by Adobe.  Implementers should investigate the availability
   of documentation of that Cryptography Profile prior to implementing
   RTMFP for the purpose of interoperation with the above mentioned
   Adobe products.

thank you.

-michael thornburgh


> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Tuesday, July 09, 2013 12:59 PM
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-=
ART, please see the FAQ at <
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd or AD before postin=
g a new version of the draft.
>=20
> Document: draft-thornburgh-adobe-rtmfp-09
> Reviewer: Ben Campbell
> Review Date: 2013-07-09
> IESG Telechat date: 2013-07-11
>=20
> Summary: This draft is essentially ready for publication as an informatio=
nal RFC. There is one issue
> from my previous review and related discussion that I think is almost, bu=
t not completely handled. All
> other concerns from my previous review have been addressed in this versio=
n.
>=20
> Major issues:
>=20
> There has been a fair amount of discussion about how this protocol requir=
es a crypto profile to
> interoperate, and no such profiles are included, or otherwise widely publ=
ished. If this were a
> standards track draft, I would argue for at least one mandatory-to-implem=
ent profile to be included or
> referenced. But since this is intended as an informational RFC that simpl=
y describes what certain
> products are doing, that's probably okay.  Furthermore, the author added =
a paragraph to the
> introduction specifically calling out the issue, which I applaud.
>=20
> But I'd like to see that paragraph go a bit further, and explicitly menti=
on any such profile needed to
> interoperate with the commercial products mentioned in the 2nd paragraph =
of section 1 has not been
> made available at the time of RFC publication, and that implementors shou=
ld investigate the
> availability of such a profile prior to implementing this protocol for th=
e purposes of interoperating
> with those products.
>=20
> Minor issues:
>=20
> None.
>=20
> Nits/editorial comments:
>=20
> None.

From ben@nostrum.com  Tue Jul  9 15:12:19 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E302B21E804D; Tue,  9 Jul 2013 15:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.373
X-Spam-Level: 
X-Spam-Status: No, score=-101.373 tagged_above=-999 required=5 tests=[AWL=-1.228, BAYES_00=-2.599, FRT_ADOBE2=2.455, SPF_PASS=-0.001,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hF4kldosMtVO; Tue,  9 Jul 2013 15:12:19 -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 2F75E21F9C8D; Tue,  9 Jul 2013 15:12:19 -0700 (PDT)
Received: from [10.0.1.12] (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 r69MCAAT065769 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Jul 2013 17:12:10 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC74398261AB600@nambx08.corp.adobe.com>
Date: Tue, 9 Jul 2013 17:12:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <579008D9-8C34-439B-BEE0-BF73EF25636B@nostrum.com>
References: <AE51780A-646A-4C82-9DAD-8557B06C75A5@nostrum.com> <D9D602D39A98E34D9C43E965BEC74398261AB600@nambx08.corp.adobe.com>
To: Michael Thornburgh <mthornbu@adobe.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, "draft-thornburgh-adobe-rtmfp.all@tools.ietf.org" <draft-thornburgh-adobe-rtmfp.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-thornburgh-adobe-rtmfp-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2013 22:12:20 -0000

Thanks Michael, that note would completely resolve my concern, and =
change my review summary to "ready for publication".

Ben.

On Jul 9, 2013, at 5:03 PM, Michael Thornburgh <mthornbu@adobe.com> =
wrote:

> hi Ben.
>=20
> your "like to see" is entirely reasonable, and the following text will =
be in the next revision once my AD or Document Shepherd directs me to =
post it:
>=20
>   Note to implementers: at the time of writing, the Cryptography
>   Profile used by the above mentioned Adobe products is not publicly
>   described by Adobe.  Implementers should investigate the =
availability
>   of documentation of that Cryptography Profile prior to implementing
>   RTMFP for the purpose of interoperation with the above mentioned
>   Adobe products.
>=20
> thank you.
>=20
> -michael thornburgh
>=20
>=20
>> From: Ben Campbell [mailto:ben@nostrum.com]
>> Sent: Tuesday, July 09, 2013 12:59 PM
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at <
>> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please wait for direction from your document shepherd or AD before =
posting a new version of the draft.
>>=20
>> Document: draft-thornburgh-adobe-rtmfp-09
>> Reviewer: Ben Campbell
>> Review Date: 2013-07-09
>> IESG Telechat date: 2013-07-11
>>=20
>> Summary: This draft is essentially ready for publication as an =
informational RFC. There is one issue
>> from my previous review and related discussion that I think is =
almost, but not completely handled. All
>> other concerns from my previous review have been addressed in this =
version.
>>=20
>> Major issues:
>>=20
>> There has been a fair amount of discussion about how this protocol =
requires a crypto profile to
>> interoperate, and no such profiles are included, or otherwise widely =
published. If this were a
>> standards track draft, I would argue for at least one =
mandatory-to-implement profile to be included or
>> referenced. But since this is intended as an informational RFC that =
simply describes what certain
>> products are doing, that's probably okay.  Furthermore, the author =
added a paragraph to the
>> introduction specifically calling out the issue, which I applaud.
>>=20
>> But I'd like to see that paragraph go a bit further, and explicitly =
mention any such profile needed to
>> interoperate with the commercial products mentioned in the 2nd =
paragraph of section 1 has not been
>> made available at the time of RFC publication, and that implementors =
should investigate the
>> availability of such a profile prior to implementing this protocol =
for the purposes of interoperating
>> with those products.
>>=20
>> Minor issues:
>>=20
>> None.
>>=20
>> Nits/editorial comments:
>>=20
>> None.


From brian.e.carpenter@gmail.com  Tue Jul  9 21:18:40 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B554721F9BBB for <gen-art@ietfa.amsl.com>; Tue,  9 Jul 2013 21:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.461
X-Spam-Level: 
X-Spam-Status: No, score=-102.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C5EFDp0Ekzfs for <gen-art@ietfa.amsl.com>; Tue,  9 Jul 2013 21:18:40 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3034F21F9BB9 for <gen-art@ietf.org>; Tue,  9 Jul 2013 21:18:40 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id 4so5956729pdd.34 for <gen-art@ietf.org>; Tue, 09 Jul 2013 21:18:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=w4lQtJbDu+mI+D6EgIVeq13AZChdm03jG3sJlPpq7hM=; b=IVsoSTR8IHwbE1XpLgZ3vhjGIW7wJVJ26Ci0tb7Y6G45Iv9zvCu3ErFpytvYtoBPA4 4cJND7j0k7GVPFXuATuMVqmxjExNg7y85Irzp5NWnVPjhE2Ntrm1SRKRcqgDxMmeQcs5 BzaJZlzGasUBJlMqoM+vVoUi9wJxIfdrdBnXMN/W/21vh61nICLfpTacXFC7eI8HLpMi njUgkNCKIdt1R2dd1AA+oiYHJVoOsreqIK1MaRPHmTCCF/CBqdc4/Vg+l6+GKXPulV1j Vy5FxzaYokRKFMfk2bZIQiabT6x+ltdGZ1FghbBtoCOzqz5aoaWZQG0nG1pivp9cnNdV ze6Q==
X-Received: by 10.67.3.35 with SMTP id bt3mr15962871pad.41.1373429919912; Tue, 09 Jul 2013 21:18:39 -0700 (PDT)
Received: from [192.168.178.23] (211.192.69.111.dynamic.snap.net.nz. [111.69.192.211]) by mx.google.com with ESMTPSA id z19sm33648300paf.12.2013.07.09.21.18.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 21:18:39 -0700 (PDT)
Message-ID: <51DCE0A1.90807@gmail.com>
Date: Wed, 10 Jul 2013 16:18:41 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-lisp-deployment.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART LC review of draft-ietf-lisp-deployment-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, 10 Jul 2013 04:18:40 -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-lisp-deployment-09.txt
Reviewer: Brian Carpenter
Review Date: 2013-07-10
IETF LC End Date: 2013-07-15
IESG Telechat date:

Summary:  Almost ready
--------

Comments:
---------

I was assigned to review -08, but -09 came out during Last Call.

Issues:
-------

The draft states in its Introduction that it "is expected to evolve as LISP
deployment progresses, and the described scenarios are better understood or
new scenarios are discovered." The desire to freeze a version of the draft
as an RFC is understandable, but shouldn't the title and Abstract clearly
indicate that it's a snapshot (and genuinely a request for comments)?

In general the draft is clear and well written. If you believe that there
are sufficient incentives for Tier 3 providers and large sites to deploy
an experimental protocol such as LISP, the discussion is useful. However,
I am disappointed by the limited discussion of scalability. In particular,
the incentives to deploy P-ITRs and to announce routes to them will become
a critical issue at the half-way stage between early transition (LISP is a
minority solution) and late transition (LISP is the majority solution).
According to RFC 6832, P-ITRs scale either because "aggregate routes might
be selectively announced" or because "the same address might be announced
by multiple Proxy-ITRs in order to share the traffic." I really expected
the deployment draft to discuss this issue in more detail. As I believe
has been said before, these issues are very similar to the issues facing
the operators of a 6to4 forward or return relay. We have experimental
evidence there that altruism doesn't work and the incentives to "donate"
connectivity are insufficient. The analogy isn't perfect, but the underlying
question is similar - what is the incentive for a particular operator to
offer P-ITR service for a particular bunch of EID prefixes, when the
clientele might be up to half the Internet, depending on who chooses to
propagate the routes?

The Security Considerations are minimal. I wonder if draft-ietf-lisp-threats
identifies threats for each scenario described in draft-ietf-lisp-deployment?
If not, the statement "Security implications of LISP deployments are to be
discussed in separate documents." is rather optimistic.


From jari.arkko@piuha.net  Wed Jul 10 09:53:51 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B32111E80AE for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 09:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OibiPMBJ7zGJ for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 09:53:43 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 36A9E21F9FE2 for <gen-art@ietf.org>; Wed, 10 Jul 2013 09:53:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 455642CC48 for <gen-art@ietf.org>; Wed, 10 Jul 2013 19:53:28 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pKgZdkxDCrjg for <gen-art@ietf.org>; Wed, 10 Jul 2013 19:53:27 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id A774E2CC3C for <gen-art@ietf.org>; Wed, 10 Jul 2013 19:53:27 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net>
Date: Wed, 10 Jul 2013 19:53:26 +0300
To: "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Subject: [Gen-art] Timing of reviews: conclusion
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 10 Jul 2013 16:53:51 -0000

I wanted to conclude our earlier discussion on the timing of directorate =
reviews. Overall I read the thread as cautiously positive for =
experimenting if this helps or not. But we need to take care of a =
multiple issues:

- Figure out the best way for the reviewers to be able to send mail to =
WG lists
- Limit the time/scope of the experiment in order to find out what the =
real effect is on, e.g., reviewer workload
- Determine whether to review at WG time, IETF last call time, and IESG =
review time. Right now we are doing the last two.
- Determine how to start the review, and what the timing is.
- Carefully select review timing and documents so that they are ready =
for an external review
- Shield reviewers from being shouted down by a large group of WG =
participants

The suggestions for resolving these items is:

- We can start the effort by having the WG chairs able to ask for this =
service. The team can then throttle the requests to a level they see =
they can handle.
- Start the experiment now and review in six months, determine success =
based on interviewing participating reviewers and WG chairs
- Perform reviews after the WGLC (in parallel with AD reviews)
- Review documents while they are in the working group, and attempt to =
have the same person do a review of the new version that is entering the =
IESG telechat (similar to what we are doing now, but replacing IETF last =
call review with WGLC review)
- Require working group chairs to mediate and monitor discussions =
between the reviewer and the working group
- Whitelisting might be a feasible solution for making the reviewers =
able to post to the WG list. Or is there something else that we could =
do? Rely on the WG chairs approving posts?

Comments?

Jari


From brian.e.carpenter@gmail.com  Wed Jul 10 13:11:58 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FEA921F9E7D for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 13:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.475
X-Spam-Level: 
X-Spam-Status: No, score=-102.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MxxB2R5bjXpj for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 13:11:57 -0700 (PDT)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id CD12521F9E77 for <gen-art@ietf.org>; Wed, 10 Jul 2013 13:11:57 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id q10so6752001pdj.10 for <gen-art@ietf.org>; Wed, 10 Jul 2013 13:11:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=6rBwCytUJfJby9zYYkR73xl//3h3ccha4ZBA1rb+ObQ=; b=Ft2K7vgvd1O6b6OuJ6dlbuIx5GlbenytTcqbCrGWV3qwCMLEUQJDaRLzmDMHmGQnAD g/m+2FDt4PJvIap2yuqji6PbH68LNoenOrb7ZDYMliLZQvC2S1ChfHmRa9uEwT09ZUUn 8TrOS7PAu2BZLbY5BRpFh+ggiHZYuee8O06lJnsXiW7PRQNDMntkMD2sBNxveKr1eL8X yXliBxApDQQ60EuKvs37cU78QdiMRsPfrZEKY4GJ9nsaKVI8vES0SLCFVpmUcVynWk9e 1By7V6X7gW3qSt8rCdnnbZvgSsP1D5NPk531bgZTznohb4E9tbspOEH/FkBGbX072HyK 4iRA==
X-Received: by 10.68.101.226 with SMTP id fj2mr32606375pbb.6.1373487116339; Wed, 10 Jul 2013 13:11:56 -0700 (PDT)
Received: from [192.168.178.23] (150.199.69.111.dynamic.snap.net.nz. [111.69.199.150]) by mx.google.com with ESMTPSA id ot4sm37852654pac.17.2013.07.10.13.11.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 13:11:55 -0700 (PDT)
Message-ID: <51DDC010.7020408@gmail.com>
Date: Thu, 11 Jul 2013 08:12:00 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net>
In-Reply-To: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Timing of reviews: conclusion
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 10 Jul 2013 20:11:58 -0000

Hi Jari,

Personally, I'm willing to try this. I was just wondering what our
"standard" template would be for this. Something like this perhaps:

The WG Chairs requested a Gen-ART review 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 Area Director comments
you may receive.

Document: draft-ietf-foobar...
Reviewer: Brian Carpenter
Review Date: 2013-07-10
IETF LC End Date: TBD
IESG Telechat date: TBD

Summary:  Needs work...

Also: we would need to update the GenART FAQ slightly. The answer
to "Q: Why is my document being reviewed?" needs changing.

Regards
   Brian

On 11/07/2013 04:53, Jari Arkko wrote:
> I wanted to conclude our earlier discussion on the timing of directorate reviews. Overall I read the thread as cautiously positive for experimenting if this helps or not. But we need to take care of a multiple issues:
> 
> - Figure out the best way for the reviewers to be able to send mail to WG lists
> - Limit the time/scope of the experiment in order to find out what the real effect is on, e.g., reviewer workload
> - Determine whether to review at WG time, IETF last call time, and IESG review time. Right now we are doing the last two.
> - Determine how to start the review, and what the timing is.
> - Carefully select review timing and documents so that they are ready for an external review
> - Shield reviewers from being shouted down by a large group of WG participants
> 
> The suggestions for resolving these items is:
> 
> - We can start the effort by having the WG chairs able to ask for this service. The team can then throttle the requests to a level they see they can handle.
> - Start the experiment now and review in six months, determine success based on interviewing participating reviewers and WG chairs
> - Perform reviews after the WGLC (in parallel with AD reviews)
> - Review documents while they are in the working group, and attempt to have the same person do a review of the new version that is entering the IESG telechat (similar to what we are doing now, but replacing IETF last call review with WGLC review)
> - Require working group chairs to mediate and monitor discussions between the reviewer and the working group
> - Whitelisting might be a feasible solution for making the reviewers able to post to the WG list. Or is there something else that we could do? Rely on the WG chairs approving posts?
> 
> Comments?
> 
> Jari
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
> 

From jari.arkko@piuha.net  Wed Jul 10 13:23:43 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F5EC21F9D7E for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 13:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id osN9q4zynnPk for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 13:23:38 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id F186521F9D5A for <gen-art@ietf.org>; Wed, 10 Jul 2013 13:23:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 63A122CC48; Wed, 10 Jul 2013 23:23:25 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VRUGaVZxlzRP; Wed, 10 Jul 2013 23:23:25 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id CDDE72CC3C; Wed, 10 Jul 2013 23:23:24 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51DDC010.7020408@gmail.com>
Date: Wed, 10 Jul 2013 23:23:24 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <B980ED9D-54DD-49CD-B394-1EB109EE8980@piuha.net>
References: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net> <51DDC010.7020408@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Timing of reviews: conclusion
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 10 Jul 2013 20:23:43 -0000

Brian:

Good points. And I like the template. Thanks.

Jari



From jari.arkko@piuha.net  Wed Jul 10 13:25:04 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22FBC21F9D5A; Wed, 10 Jul 2013 13:25:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VbZ9H68gVp-8; Wed, 10 Jul 2013 13:24:59 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id AAE3021F9DAA; Wed, 10 Jul 2013 13:24:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 04B9F2CC48; Wed, 10 Jul 2013 23:24:41 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lplK58zgVFGC; Wed, 10 Jul 2013 23:24:40 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 6746C2CC3C; Wed, 10 Jul 2013 23:24:40 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <030301ce7b9d$6f821100$4e863300$@akayla.com>
Date: Wed, 10 Jul 2013 23:24:40 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D189071-3175-4D21-8B64-7F59FB259EF9@piuha.net>
References: <030301ce7b9d$6f821100$4e863300$@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org, draft-ietf-appsawg-rfc5451bis.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-appsawg-rfc5451bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2013 20:25:04 -0000

Peter,

Thank you very much for your detailed review. And Murray, thanks for =
taking into account the comments. FWIW, I plan to ballot No-Objection =
for this draft based on the Gen-ART review (and my own far less detailed =
review).

Jari


From jari.arkko@piuha.net  Wed Jul 10 14:24:13 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DE0221F9CCA for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 14:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kb15bJ1+z3gN for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 14:24:07 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 214A921F9DB2 for <gen-art@ietf.org>; Wed, 10 Jul 2013 14:24:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2783E2CC61; Thu, 11 Jul 2013 00:24:01 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CIvuQ4sRq37G; Thu, 11 Jul 2013 00:24:00 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 504892CC48; Thu, 11 Jul 2013 00:24:00 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 11 Jul 2013 00:23:59 +0300
Message-Id: <B86D52BC-5F5F-4B1F-8C10-9C59068CB8F5@piuha.net>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-lisp-mib@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-lisp-mib-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2013 21:24:13 -0000

Miguel,

This draft is finally in IESG plate after you had reviewed it in =
January. Thank you for the review! I'm planning to ballot a =
No-Objection. I also noticed that for the IESG review it had been =
reassigned to Suresh. Suresh, any objections - have you reviewed this =
version?

Jari


From suresh.krishnan@ericsson.com  Wed Jul 10 15:47:24 2013
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 583A311E8135 for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 15:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id byv5xFP-8eGK for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 15:47:18 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id DE3A611E8141 for <gen-art@ietf.org>; Wed, 10 Jul 2013 15:47:17 -0700 (PDT)
X-AuditID: c618062d-b7fc36d0000032ea-9d-51dde4757038
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id B3.A3.13034.574EDD15; Thu, 11 Jul 2013 00:47:17 +0200 (CEST)
Received: from [142.133.112.97] (147.117.188.135) by smtps-am.internal.ericsson.com (147.117.188.78) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 10 Jul 2013 18:47:17 -0400
Message-ID: <51DDE3DA.7010003@ericsson.com>
Date: Wed, 10 Jul 2013 18:44:42 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <B86D52BC-5F5F-4B1F-8C10-9C59068CB8F5@piuha.net>
In-Reply-To: <B86D52BC-5F5F-4B1F-8C10-9C59068CB8F5@piuha.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [147.117.188.135]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGLMWRmVeSWpSXmKPExsUyuXSPn27pk7uBBpcuyVvMXLCL0eLqq88s FjP2rWBzYPZYsuQnk8fWJdPZPL5c/swWwBzFZZOSmpNZllqkb5fAlbHm4Cz2gg+sFT9nf2Rv YNzJ0sXIwSEhYCIxc7ViFyMnkCkmceHeerYuRi4OIYGjjBIn1i5ngXB2MEqsWLyPBaSKV0Bb 4kLXRzYQm0VAVeLwvj4wmw1o0Iadn5lAbFGBMIkPy5YwQdQLSpyc+QSsVwSofu7RNawgQ5kF JjBK/Pz8AuwKYQF7iVW7TEFqhARsJPad+8gMYnMK2ErMfvSMHeI6SYktL9rBbGYBPYkpV1sY IWx5ie1v5zBD9GpKbF3znRXiMWWJHTMSJzAKz0JyxSwk3bOQdC9gZF7FyFFanFqWm25ksIkR GNbHJNh0dzDueWl5iFGag0VJnHeV3plAIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYzR/RXF +S9Sunn/Bp94u/FMdXfDxnnhMgY75iiVFc7hD7loyyIV+pgnxS/nxgn15NQdYvz/3M/lBRZz ah9zyZdc6Lr0nOXFzGchj7l3no/VccuL4/nE4hmgVBGj8TL7q/Ml6QOWHfbT10RoTpIzd8o9 MSPgx2vDV58DX03dLj31+cGJBi6e/5VYijMSDbWYi4oTAer1OCM5AgAA
Cc: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-lisp-mib@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-lisp-mib-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2013 22:47:24 -0000

Hi Jari,
  I went through the draft and it looks OK. I just had one minor issue
with some example math in the draft.

The following math in the Example 3 of lispMapCacheEntry is wrong and
needs to get fixed.

11 - (2 + 1 + 1 + 1 + 1 + 1 + 4) = 1

I don't think that this should hold the draft up as it is only an
example, but it certainly did throw me off when I read it.

Thanks
Suresh

On 07/10/2013 05:23 PM, Jari Arkko wrote:
> Miguel,
> 
> This draft is finally in IESG plate after you had reviewed it in January. Thank you for the review! I'm planning to ballot a No-Objection. I also noticed that for the IESG review it had been reassigned to Suresh. Suresh, any objections - have you reviewed this version?
> 
> Jari
> 


From jari.arkko@piuha.net  Wed Jul 10 16:04:53 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 715E321F9CE6 for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 16:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KfUUbV1--Ff3 for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 16:04:48 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id E132411E8135 for <gen-art@ietf.org>; Wed, 10 Jul 2013 16:04:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8BABA2CC61; Thu, 11 Jul 2013 02:04:44 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XXGXUGXQkCvu; Thu, 11 Jul 2013 02:04:44 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id B6A4F2CC48; Thu, 11 Jul 2013 02:04:43 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51DDE3DA.7010003@ericsson.com>
Date: Thu, 11 Jul 2013 02:04:43 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F207A77-7BC8-44B7-8910-66C617E9F0D1@piuha.net>
References: <B86D52BC-5F5F-4B1F-8C10-9C59068CB8F5@piuha.net> <51DDE3DA.7010003@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-lisp-mib@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-lisp-mib-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2013 23:04:53 -0000

Thanks for your review, Suresh. Authors, can you fix the example? =
Thanks.

Jari

On Jul 11, 2013, at 1:44 AM, Suresh Krishnan =
<suresh.krishnan@ericsson.com> wrote:

> Hi Jari,
>  I went through the draft and it looks OK. I just had one minor issue
> with some example math in the draft.
>=20
> The following math in the Example 3 of lispMapCacheEntry is wrong and
> needs to get fixed.
>=20
> 11 - (2 + 1 + 1 + 1 + 1 + 1 + 4) =3D 1
>=20
> I don't think that this should hold the draft up as it is only an
> example, but it certainly did throw me off when I read it.
>=20
> Thanks
> Suresh
>=20
> On 07/10/2013 05:23 PM, Jari Arkko wrote:
>> Miguel,
>>=20
>> This draft is finally in IESG plate after you had reviewed it in =
January. Thank you for the review! I'm planning to ballot a =
No-Objection. I also noticed that for the IESG review it had been =
reassigned to Suresh. Suresh, any objections - have you reviewed this =
version?
>>=20
>> Jari
>>=20
>=20


From jari.arkko@piuha.net  Wed Jul 10 16:46:18 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 293BC11E8107 for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 16:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCAcF9k5Ib2i for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 16:46:13 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 22D5E21F8825 for <gen-art@ietf.org>; Wed, 10 Jul 2013 16:45:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 64BB62CC61; Thu, 11 Jul 2013 02:45:40 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vPzZAui71RLO; Thu, 11 Jul 2013 02:45:40 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 97B062CC48; Thu, 11 Jul 2013 02:45:39 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <ED495B2B0CBE86418E03429D7AC236C40FD98512@xmb-rcd-x09.cisco.com>
Date: Thu, 11 Jul 2013 02:45:39 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <D8B6A473-9DC5-4B3B-A7D2-349AA5F7CAF8@piuha.net>
References: <B86D52BC-5F5F-4B1F-8C10-9C59068CB8F5@piuha.net> <51DDE3DA.7010003@ericsson.com> <7F207A77-7BC8-44B7-8910-66C617E9F0D1@piuha.net> <ED495B2B0CBE86418E03429D7AC236C40FD98512@xmb-rcd-x09.cisco.com>
To: Gregg Schudel (gschudel) <gschudel@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-lisp-mib@tools.ietf.org" <draft-ietf-lisp-mib@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-lisp-mib-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2013 23:46:18 -0000

> 
> I'll correct this.
> 

thanks!

Jari



From gschudel@cisco.com  Wed Jul 10 16:43:33 2013
Return-Path: <gschudel@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 6575711E8158 for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 16:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jFnG4eCKa3VL for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 16:43:27 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id AC4D511E813D for <gen-art@ietf.org>; Wed, 10 Jul 2013 16:43:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1283; q=dns/txt; s=iport; t=1373499805; x=1374709405; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=qO6G6a5HyVEUWcpIEbsIyEBMt5z4dnd4npLa08sgyXA=; b=gGNVhSOHTDs1+qS0L4EqL4weHnfUDmA3p1WqoDXKKKUg4l30JQW3qaTq 6aFhVwBGnf7HLOVtJYm1U7EQ7zB+J5YMEi58a3MgQCShyf0Ehk52mBnjW OlW0CLEnm9/37XbWGd2bf/fNV62GLZRaDWB3bx9NEwrFVeAlIIYyU3pD4 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFALLw3VGtJXHA/2dsb2JhbABXA4MJMk3BJ4EOFnSCIwEBAQECAW8KBQsCAQgYCiQyJQIEAQ0FCIgBBgy3XI4hgQ8CIRACBRGCeGwDqSSDEYFxNw
X-IronPort-AV: E=Sophos;i="4.87,1039,1363132800"; d="scan'208";a="233332459"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-8.cisco.com with ESMTP; 10 Jul 2013 23:43:22 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6ANhMLa027557 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 10 Jul 2013 23:43:22 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Wed, 10 Jul 2013 18:43:22 -0500
From: "Gregg Schudel (gschudel)" <gschudel@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: [Gen-art] Gen-ART review of draft-ietf-lisp-mib-08  
Thread-Index: AQHOfcHkbcnoEinX7Um5n9MFPZ0V0Zle5tOA
Date: Wed, 10 Jul 2013 23:43:21 +0000
Message-ID: <ED495B2B0CBE86418E03429D7AC236C40FD98512@xmb-rcd-x09.cisco.com>
References: <B86D52BC-5F5F-4B1F-8C10-9C59068CB8F5@piuha.net> <51DDE3DA.7010003@ericsson.com> <7F207A77-7BC8-44B7-8910-66C617E9F0D1@piuha.net>
In-Reply-To: <7F207A77-7BC8-44B7-8910-66C617E9F0D1@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.67.31]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <B08872C566F67D438222A15A0BCB4FC6@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 10 Jul 2013 19:57:01 -0700
Cc: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-lisp-mib@tools.ietf.org" <draft-ietf-lisp-mib@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-lisp-mib-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2013 23:43:33 -0000

On Jul 10, 2013, at 4:04 PM, Jari Arkko <jari.arkko@piuha.net>
 wrote:

> Thanks for your review, Suresh. Authors, can you fix the example? Thanks.
>=20
> Jari
>=20
> On Jul 11, 2013, at 1:44 AM, Suresh Krishnan <suresh.krishnan@ericsson.co=
m> wrote:
>=20
>> Hi Jari,
>> I went through the draft and it looks OK. I just had one minor issue
>> with some example math in the draft.
>>=20
>> The following math in the Example 3 of lispMapCacheEntry is wrong and
>> needs to get fixed.
>>=20
>> 11 - (2 + 1 + 1 + 1 + 1 + 1 + 4) =3D 1
>>=20
>> I don't think that this should hold the draft up as it is only an
>> example, but it certainly did throw me off when I read it.
>>=20


[gs] embarrassing=85 sorry! there was one-too-many "+ 1" in there.
I'll correct this.

Thank you!



Best regards,
Gregg

--------------------------------------------------------------------
.:|:.:|:. | gregg schudel (ccie#9591) LISP technical marketing engr
  cisco   | mobile: +1 571 332 2222   email: gschudel@cisco.com
--------------------------------------------------------------------
cisco corporate legal statement:=20
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
--------------------------------------------------------------------






From jari.arkko@piuha.net  Wed Jul 10 23:51:18 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEF7821F99F4 for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 23:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iU3LxH4fHrie for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 23:51:14 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB9221F8F00 for <gen-art@ietf.org>; Wed, 10 Jul 2013 23:51:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7F2642CC48; Thu, 11 Jul 2013 09:51:12 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pveiR2S_ynKQ; Thu, 11 Jul 2013 09:51:11 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7F9E62CC3C; Thu, 11 Jul 2013 09:51:10 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51B366F7.5040603@joelhalpern.com>
Date: Thu, 11 Jul 2013 09:51:09 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <08C67BF5-1625-4481-9720-329CEE246292@piuha.net>
References: <51B115F1.7010901@nostrum.com> <51B366F7.5040603@joelhalpern.com>
To: Joel M. Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Review: draft-ietf-ospf-manet-single-hop-mdr-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: Thu, 11 Jul 2013 06:51:19 -0000

Joel: thank you very much for your review. This review has helped me =
decide what to do in the IESG review - I plan to ballot No-Objection for =
this draft.

Jari

On Jun 8, 2013, at 8:16 PM, Joel M. Halpern <jmh@joelhalpern.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-ietf-ospf-manet-single-hop-mdr-03.txt
>=20
> Reviewer: Joel M. Halpern
> Review Date: 8-June-2013
> IETF LC End Date: 19-June-2013
> IESG Telechat date: N/A
>=20
> Summary: This document is ready for publication as an Experimental =
RFC.
>=20
> Major issues: N/A
>=20
> Minor issues: N/A
>=20
> Nits/editorial comments: N/A
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Jul 10 23:54:55 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB9C21F9E44 for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 23:54:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ul8kAvfIoQS2 for <gen-art@ietfa.amsl.com>; Wed, 10 Jul 2013 23:54:51 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 228B421F9E45 for <gen-art@ietf.org>; Wed, 10 Jul 2013 23:54:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 621712CC48; Thu, 11 Jul 2013 09:54:37 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79iH9SCwSKNs; Thu, 11 Jul 2013 09:54:36 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id A0A6E2CC3C; Thu, 11 Jul 2013 09:54:35 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51C46746.1080802@joelhalpern.com>
Date: Thu, 11 Jul 2013 09:54:34 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <3CBCF9D8-FC32-4F72-A9AB-A5068036DD8B@piuha.net>
References: <019c01ce6e01$105176c0$30f46440$@akayla.com> <51C46746.1080802@joelhalpern.com>
To: Joel M. Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] review: draft-ietf-straw-b2bua-taxonomy-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jul 2013 06:54:55 -0000

Joel: Thanks for reviewing this draft as well. I plan to ballot =
no-objection for this draft as well.

Jari

On Jun 21, 2013, at 5:46 PM, Joel M. Halpern <jmh@joelhalpern.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-ietf-straw-b2bua-taxonomy-02
>    A Taxonomy of Session Initiation Protocol (SIP)
>        Back-to-Back User Agents
> Reviewer: Joel M. Halpern
> Review Date: 21-June-2013
> IETF LC End Date: 01-July-2013
> IESG Telechat date: N/A
>=20
> Summary: This document is ready for publication as an Informational =
RFC.
>=20
> Major issues: N/A
>=20
> Minor issues: N/A
>=20
> Nits/editorial comments: N/A
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From dromasca@avaya.com  Thu Jul 11 02:11:20 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FA1621F9D80 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 02:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.369
X-Spam-Level: 
X-Spam-Status: No, score=-103.369 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AN-pdK9O4DVr for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 02:11:15 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id C86B821F9AB7 for <gen-art@ietf.org>; Thu, 11 Jul 2013 02:11:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAAH/ZlHGmAcV/2dsb2JhbABQgmUhNsFIgQcWdIIfAQEBAQMBAQEPKDQXBAIBCA0EBAEBCxQJBycLFAkIAgQBEggTB4dyAQugPJ0MF41fBYEBJhIGglphA5M2iXOKaIMLgWsIFx4
X-IronPort-AV: E=Sophos;i="4.87,456,1363147200"; d="scan'208";a="19100596"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 11 Jul 2013 05:11:02 -0400
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 11 Jul 2013 05:09:16 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0328.009; Thu, 11 Jul 2013 05:11:01 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Jari Arkko <jari.arkko@piuha.net>, "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Timing of reviews: conclusion
Thread-Index: AQHOfY4Yy+yJNMY/TUKuNJPJgWGuZplfLNpg
Date: Thu, 11 Jul 2013 09:11:00 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA12868FF5@AZ-FFEXMB04.global.avaya.com>
References: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net>
In-Reply-To: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Gen-art] Timing of reviews: conclusion
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 11 Jul 2013 09:11:20 -0000

I am also in favor of the experiment and willing to participate. Besides th=
e changes pointed to by Brian we may also need to make some adjustments to =
the Gen-ART tools (new column in the table at http://art.tools.ietf.org/too=
ls/art/genart/index.cgi/t=3D3634/fullqueue to mark the WG review due date) =
and the process used by the secretary (separate mail for WG early review?).=
=20

Regards,

Dan






> -----Original Message-----
> From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On
> Behalf Of Jari Arkko
> Sent: Wednesday, July 10, 2013 7:53 PM
> To: <gen-art@ietf.org> Team
> Subject: [Gen-art] Timing of reviews: conclusion
>=20
> I wanted to conclude our earlier discussion on the timing of directorate
> reviews. Overall I read the thread as cautiously positive for
> experimenting if this helps or not. But we need to take care of a
> multiple issues:
>=20
> - Figure out the best way for the reviewers to be able to send mail to
> WG lists
> - Limit the time/scope of the experiment in order to find out what the
> real effect is on, e.g., reviewer workload
> - Determine whether to review at WG time, IETF last call time, and IESG
> review time. Right now we are doing the last two.
> - Determine how to start the review, and what the timing is.
> - Carefully select review timing and documents so that they are ready
> for an external review
> - Shield reviewers from being shouted down by a large group of WG
> participants
>=20
> The suggestions for resolving these items is:
>=20
> - We can start the effort by having the WG chairs able to ask for this
> service. The team can then throttle the requests to a level they see
> they can handle.
> - Start the experiment now and review in six months, determine success
> based on interviewing participating reviewers and WG chairs
> - Perform reviews after the WGLC (in parallel with AD reviews)
> - Review documents while they are in the working group, and attempt to
> have the same person do a review of the new version that is entering the
> IESG telechat (similar to what we are doing now, but replacing IETF last
> call review with WGLC review)
> - Require working group chairs to mediate and monitor discussions
> between the reviewer and the working group
> - Whitelisting might be a feasible solution for making the reviewers
> able to post to the WG list. Or is there something else that we could
> do? Rely on the WG chairs approving posts?
>=20
> Comments?
>=20
> Jari
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

From lojakab@cisco.com  Thu Jul 11 05:48:52 2013
Return-Path: <lojakab@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 C25EA11E8133 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 05:48:52 -0700 (PDT)
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, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o99jnlS+B3Z9 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 05:48:48 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id CCF2411E8127 for <gen-art@ietf.org>; Thu, 11 Jul 2013 05:48:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4866; q=dns/txt; s=iport; t=1373546927; x=1374756527; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=vtDRICeIs/OOkUPIL8vbqFV3QmAC3W4XjZYhSfHVQBM=; b=UKv+ENnUtwzxFVfwPlNCIK6xdpkVZFyVa8+deq22FDuMyCV2APBksvyv SZR7LNro+kfCUAj7XQF0xI1pd8z5oYRvuHGLZYA9lHU0SNwSbMNinC/nS OhnpK4FnDDbE0wFuvxMBZBF/GK0uspvON9m/qgiAIhDk/GYsqGK8nzL+Q 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAJid3lGtJV2a/2dsb2JhbABagwkyTYMGvkqBBhZ0giMBAQEDASMVOgIEARALFAQCAgUWCwICCQMCAQIBRQYNAQcBAReHbgYMpXaRPoEmjQOBOAeCVoEfA4khimKDV4EphHqLJ4MUgWVA
X-IronPort-AV: E=Sophos;i="4.87,1043,1363132800"; d="scan'208";a="233542776"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-8.cisco.com with ESMTP; 11 Jul 2013 12:48:46 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6BCmjRG002345 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 11 Jul 2013 12:48:45 GMT
Received: from [10.21.126.80] (10.21.126.80) by xhc-rcd-x03.cisco.com (173.37.183.77) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 11 Jul 2013 07:48:43 -0500
Message-ID: <51DEA9A5.2040405@cisco.com>
Date: Thu, 11 Jul 2013 15:48:37 +0300
From: Lori Jakab <lojakab@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <51DCE0A1.90807@gmail.com>
In-Reply-To: <51DCE0A1.90807@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.21.126.80]
X-Mailman-Approved-At: Thu, 11 Jul 2013 06:23:41 -0700
Cc: draft-ietf-lisp-deployment.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-lisp-deployment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jul 2013 12:48:52 -0000

Hi Brian,

Thank you for reviewing.  Please find replies to you comments inline.

On 7/10/13 7:18 AM, Brian E Carpenter 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-lisp-deployment-09.txt
> Reviewer: Brian Carpenter
> Review Date: 2013-07-10
> IETF LC End Date: 2013-07-15
> IESG Telechat date:
>
> Summary:  Almost ready
> --------
>
> Comments:
> ---------
>
> I was assigned to review -08, but -09 came out during Last Call.
>
> Issues:
> -------
>
> The draft states in its Introduction that it "is expected to evolve as LISP
> deployment progresses, and the described scenarios are better understood or
> new scenarios are discovered." The desire to freeze a version of the draft
> as an RFC is understandable, but shouldn't the title and Abstract clearly
> indicate that it's a snapshot (and genuinely a request for comments)?

I'm not sure a change in the title is warranted (please suggest a new 
title if you think it is), but I agree the Abstract should be reworded.  
How about this new text replacing the old one:

    This document is a snapshot of different Locator/Identifier
    Separation Protocol (LISP) deployment scenarios.  It discusses the
    placement of new network elements introduced by the protocol,
    representing the thinking of the authors as of Summer 2013.  LISP
    deployment scenarios may have evolved since. This memo represents
    one stable point in that evolution of understanding.


>
> In general the draft is clear and well written. If you believe that there
> are sufficient incentives for Tier 3 providers and large sites to deploy
> an experimental protocol such as LISP, the discussion is useful. However,
> I am disappointed by the limited discussion of scalability. In particular,
> the incentives to deploy P-ITRs and to announce routes to them will become
> a critical issue at the half-way stage between early transition (LISP is a
> minority solution) and late transition (LISP is the majority solution).
> According to RFC 6832, P-ITRs scale either because "aggregate routes might
> be selectively announced" or because "the same address might be announced
> by multiple Proxy-ITRs in order to share the traffic." I really expected
> the deployment draft to discuss this issue in more detail. As I believe
> has been said before, these issues are very similar to the issues facing
> the operators of a 6to4 forward or return relay. We have experimental
> evidence there that altruism doesn't work and the incentives to "donate"
> connectivity are insufficient. The analogy isn't perfect, but the underlying
> question is similar - what is the incentive for a particular operator to
> offer P-ITR service for a particular bunch of EID prefixes, when the
> clientele might be up to half the Internet, depending on who chooses to
> propagate the routes?

I was hoping we addressed these concerns in Section 5.3, Proxy-ITR Route 
Distribution (PITR-RD).  I agree that altruism doesn't work, that's why 
the PITR-RD scenario is based on business relationships between 
different providers.  When someone registers a domain name, he/she pays 
an annual fee that should cover the operating expenses for publishing 
the domain in the global DNS.  The situation is similar with several 
other registration services.  When someone contacts a mapping service 
provider (MSR), to get their prefix registered in the LISP mapping 
system, they get the option of signing up for PITR services as well, for 
an extra fee.  These services may be offered by the MSP themselves, but 
it is expected that specialized P-ITR service providers (PSPs) will do 
it.  If they don't sign up, they become responsible for getting non-LISP 
traffic to their EIDs (using the LISP+BGP scenario).

Additionally, Tier 1 ISPs may offer P-ITR services to non-subscribers in 
strategic places just to attract more traffic from competitors, thus 
more revenue.

Should we add anything to this section to resolve the comment?

>
> The Security Considerations are minimal. I wonder if draft-ietf-lisp-threats
> identifies threats for each scenario described in draft-ietf-lisp-deployment?
> If not, the statement "Security implications of LISP deployments are to be
> discussed in separate documents." is rather optimistic.
>

draft-ietf-lisp-threats discusses general LISP deployment security 
issues, without analyzing all scenarios described in 
draft-ietf-lisp-deployment.  I'm not sure such an iterative approach is 
necessary, unless scenario specific threats are discovered.

Best regards,
-Lori

From jari.arkko@piuha.net  Thu Jul 11 08:23:38 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C8B321F9D04 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 08:23:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3-AX-lE7w3P for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 08:23:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 1444E21F9D02 for <gen-art@ietf.org>; Thu, 11 Jul 2013 08:23:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7F8682CC53; Thu, 11 Jul 2013 18:23:13 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNJlu2OywfZM; Thu, 11 Jul 2013 18:23:11 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 5F5322CC48; Thu, 11 Jul 2013 18:23:11 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA12868FF5@AZ-FFEXMB04.global.avaya.com>
Date: Thu, 11 Jul 2013 18:23:11 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <959762B0-8152-4475-9B64-93A6F5C2DAB8@piuha.net>
References: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net> <9904FB1B0159DA42B0B887B7FA8119CA12868FF5@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1508)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] Timing of reviews: conclusion
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 11 Jul 2013 15:23:38 -0000

> I am also in favor of the experiment and willing to participate. =
Besides the changes pointed to by Brian we may also need to make some =
adjustments to the Gen-ART tools (new column in the table at =
http://art.tools.ietf.org/tools/art/genart/index.cgi/t=3D3634/fullqueue =
to mark the WG review due date) and the process used by the secretary =
(separate mail for WG early review?).=20

That's a good point. Thanks.

Jari



From rjsparks@nostrum.com  Thu Jul 11 11:46:36 2013
Return-Path: <rjsparks@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 21F2A21F9F08 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 11:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0hOZIPwNNVj3 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 11:46:35 -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 6DCD221F9A70 for <gen-art@ietf.org>; Thu, 11 Jul 2013 11:46:35 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6BIkW2i072247 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <gen-art@ietf.org>; Thu, 11 Jul 2013 13:46:34 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <51DEFD83.7030403@nostrum.com>
Date: Thu, 11 Jul 2013 13:46:27 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: gen-art@ietf.org
References: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net> <9904FB1B0159DA42B0B887B7FA8119CA12868FF5@AZ-FFEXMB04.global.avaya.com> <959762B0-8152-4475-9B64-93A6F5C2DAB8@piuha.net>
In-Reply-To: <959762B0-8152-4475-9B64-93A6F5C2DAB8@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: Re: [Gen-art] Timing of reviews: conclusion
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 11 Jul 2013 18:46:36 -0000

I would like start discussing a more general way to track reviews when 
they are needed. Dan's new-column tweak to the existing tool makes me a 
little nervous in the long run - the column won't apply to all 
documents, and other types will come in making new columns leading to a 
painfully sparse matrix.

Rather, I would like to work towards a system where we can request 
reviews on a document at any time, for any reason.

Instead of scraping last calls to identify documents that need review, 
we can make the parts of the system that issue last calls automatically 
make a review request, and that request can tailor the data we need to 
track for that particular review (like any constraining dates such as WG 
LC or IETF LC completion).

RjS

On 7/11/13 10:23 AM, Jari Arkko wrote:
>> I am also in favor of the experiment and willing to participate. Besides the changes pointed to by Brian we may also need to make some adjustments to the Gen-ART tools (new column in the table at http://art.tools.ietf.org/tools/art/genart/index.cgi/t=3634/fullqueue to mark the WG review due date) and the process used by the secretary (separate mail for WG early review?).
> That's a good point. Thanks.
>
> Jari
>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From mahoney@nostrum.com  Thu Jul 11 11:49:13 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C226B21F9FF4 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 11:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hvy+xSFE213n for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 11:49:13 -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 25C0121F9FED for <gen-art@ietf.org>; Thu, 11 Jul 2013 11:49:13 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6BIn62p072465 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 11 Jul 2013 13:49:12 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51DEFE1D.500@nostrum.com>
Date: Thu, 11 Jul 2013 13:49:01 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: gen-art@ietf.org
References: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net> <9904FB1B0159DA42B0B887B7FA8119CA12868FF5@AZ-FFEXMB04.global.avaya.com> <959762B0-8152-4475-9B64-93A6F5C2DAB8@piuha.net>
In-Reply-To: <959762B0-8152-4475-9B64-93A6F5C2DAB8@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: Re: [Gen-art] Timing of reviews: conclusion
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 11 Jul 2013 18:49:13 -0000

I'm also willing to help with the experiment, but I suggest that the 
review tool be updated later, after we have a better idea of the new 
requirements. Updating the review tool would probably require updating 
datatracker also.

I can easily capture early review assignments in the spreadsheets for now.

Jean


On 7/11/13 10:23 AM, Jari Arkko wrote:
>> I am also in favor of the experiment and willing to participate. Besides the changes pointed to by Brian we may also need to make some adjustments to the Gen-ART tools (new column in the table at http://art.tools.ietf.org/tools/art/genart/index.cgi/t=3634/fullqueue to mark the WG review due date) and the process used by the secretary (separate mail for WG early review?).
> That's a good point. Thanks.
>
> Jari
>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From brian.e.carpenter@gmail.com  Thu Jul 11 13:03:59 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBE7A21F9E63 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 13:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level: 
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x4ScuSzQa2l8 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 13:03:59 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 0357C21F9D59 for <gen-art@ietf.org>; Thu, 11 Jul 2013 13:03:58 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx10so8213268pab.13 for <gen-art@ietf.org>; Thu, 11 Jul 2013 13:03:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hmtkflECQEp/eMIXEpTsjydpWlPmJzudb3ktlcGYwKs=; b=genCRfwbAV1YjGb0Njp9Sh3ki6IFaqMh5rWaoRW/rErCGt7yTFO0LCyWhg6w6rURNp qX3PT/DbM03/Vlo7SSDj2igQLY3G3gvYGKwfjnybDW26qBov5HGk2DGmM7agcxScKSlj MIWvM+MAkhhvnpkQBoZh+i6WcvXr8g9v+Zcjt8eGSWfACDspQmyvd2z96UiZviJMosda UF6Vf2irWruECgmCmGsAzd1iXR+lAwLlbMKmPWFl3/FcQiLz6XgrbG9VtxAeaPyXMLjt W+cuqWZ/YpwaHi9gFCs7mkWD7fX38xVwMwa9bOxskWyuozZtzV5PnIAI9Yz5blQDyjCr ftcw==
X-Received: by 10.68.88.36 with SMTP id bd4mr38392437pbb.178.1373573035643; Thu, 11 Jul 2013 13:03:55 -0700 (PDT)
Received: from [192.168.178.23] (124.199.69.111.dynamic.snap.net.nz. [111.69.199.124]) by mx.google.com with ESMTPSA id x8sm41258644pbb.39.2013.07.11.13.03.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 13:03:55 -0700 (PDT)
Message-ID: <51DF0FAD.1010604@gmail.com>
Date: Fri, 12 Jul 2013 08:03:57 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net>	<9904FB1B0159DA42B0B887B7FA8119CA12868FF5@AZ-FFEXMB04.global.avaya.com>	<959762B0-8152-4475-9B64-93A6F5C2DAB8@piuha.net> <51DEFE1D.500@nostrum.com>
In-Reply-To: <51DEFE1D.500@nostrum.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Timing of reviews: conclusion
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 11 Jul 2013 20:03:59 -0000

On 12/07/2013 06:49, A. Jean Mahoney wrote:
> I'm also willing to help with the experiment, but I suggest that the
> review tool be updated later, after we have a better idea of the new
> requirements. Updating the review tool would probably require updating
> datatracker also.

Yes. The following is not a complaint, since the review tool is a
much-appreciated volunteer effort, but IMHO it would be better
if we submitted our reviews via the review tool, which could then
send them on as email automatically. At the moment I usually forget
to enter the review URL into the tool until some days or weeks later!

(People who've used EDAS know what I mean.)

It would also make sense for reviewers to be remembered by the tracker,
so that they can get status updates automatically.

Since the tracker already knows who is interested in each draft,
integrating the two would make a lot of sense.

   Brian

> 
> I can easily capture early review assignments in the spreadsheets for now.
> 
> Jean
> 
> 
> On 7/11/13 10:23 AM, Jari Arkko wrote:
>>> I am also in favor of the experiment and willing to participate.
>>> Besides the changes pointed to by Brian we may also need to make some
>>> adjustments to the Gen-ART tools (new column in the table at
>>> http://art.tools.ietf.org/tools/art/genart/index.cgi/t=3634/fullqueue
>>> to mark the WG review due date) and the process used by the secretary
>>> (separate mail for WG early review?).
>> That's a good point. Thanks.
>>
>> Jari
>>
>>
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
> 

From brian.e.carpenter@gmail.com  Thu Jul 11 13:17:02 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6707021E8054 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 13:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.204
X-Spam-Level: 
X-Spam-Status: No, score=-102.204 tagged_above=-999 required=5 tests=[AWL=-0.205, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rYvgN1n1pgmo for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 13:17:01 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id A439521E8055 for <gen-art@ietf.org>; Thu, 11 Jul 2013 13:17:01 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id tj12so8162978pac.40 for <gen-art@ietf.org>; Thu, 11 Jul 2013 13:17:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=0774XMVTYvnKkBlc9+XprsrCQicvkOxcYS2UmZWjP9U=; b=tUbH3Vl/NbTaU92IU5EThzr2/wAwnORy6+y95cespu3kgB9CLc+jcOdSJhF8lI+Kdu sgZlya8Bmj2FoAAjTGEtug9sHHCcmEnacKdXChi144XvoAst/GGAZPEYrb2IX8Ia836x JbUTq5IsJJ2Z/3l6I3eu9erESRK9yirBCfGN21BHlCufdxrQhgWCRI3r8VToYleCAt7D h9jceHhGSSyPysw9q0wFob5I4Vf/JUaek2EfevkzhNLRGSg6qkstGBJu7N+rsOcBjF6S HUWKz5bTJh/BvNJcJ7WX+gn4pMtkfUaFnJn1YlSU2UTH0gjdZXV3Di70yE212YhKprQk 33aQ==
X-Received: by 10.68.235.9 with SMTP id ui9mr29160571pbc.85.1373573819693; Thu, 11 Jul 2013 13:16:59 -0700 (PDT)
Received: from [192.168.178.23] (124.199.69.111.dynamic.snap.net.nz. [111.69.199.124]) by mx.google.com with ESMTPSA id y6sm41320822pbl.23.2013.07.11.13.16.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 13:16:59 -0700 (PDT)
Message-ID: <51DF12C1.2080506@gmail.com>
Date: Fri, 12 Jul 2013 08:17:05 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Lori Jakab <lojakab@cisco.com>
References: <51DCE0A1.90807@gmail.com> <51DEA9A5.2040405@cisco.com>
In-Reply-To: <51DEA9A5.2040405@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-lisp-deployment.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-lisp-deployment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jul 2013 20:17:02 -0000

Hi Lori, see in line.

On 12/07/2013 00:48, Lori Jakab wrote:
> Hi Brian,
> 
> Thank you for reviewing.  Please find replies to you comments inline.
> 
> On 7/10/13 7:18 AM, Brian E Carpenter 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-lisp-deployment-09.txt
>> Reviewer: Brian Carpenter
>> Review Date: 2013-07-10
>> IETF LC End Date: 2013-07-15
>> IESG Telechat date:
>>
>> Summary:  Almost ready
>> --------
>>
>> Comments:
>> ---------
>>
>> I was assigned to review -08, but -09 came out during Last Call.
>>
>> Issues:
>> -------
>>
>> The draft states in its Introduction that it "is expected to evolve as
>> LISP
>> deployment progresses, and the described scenarios are better
>> understood or
>> new scenarios are discovered." The desire to freeze a version of the
>> draft
>> as an RFC is understandable, but shouldn't the title and Abstract clearly
>> indicate that it's a snapshot (and genuinely a request for comments)?
> 
> I'm not sure a change in the title is warranted (please suggest a new
> title if you think it is), but I agree the Abstract should be reworded. 
> How about this new text replacing the old one:
> 
>    This document is a snapshot of different Locator/Identifier
>    Separation Protocol (LISP) deployment scenarios.  It discusses the
>    placement of new network elements introduced by the protocol,
>    representing the thinking of the authors as of Summer 2013.  LISP
>    deployment scenarios may have evolved since. This memo represents
>    one stable point in that evolution of understanding.

That's good. I don't feel strongly about the title.

> 
> 
>>
>> In general the draft is clear and well written. If you believe that there
>> are sufficient incentives for Tier 3 providers and large sites to deploy
>> an experimental protocol such as LISP, the discussion is useful. However,
>> I am disappointed by the limited discussion of scalability. In
>> particular,
>> the incentives to deploy P-ITRs and to announce routes to them will
>> become
>> a critical issue at the half-way stage between early transition (LISP
>> is a
>> minority solution) and late transition (LISP is the majority solution).
>> According to RFC 6832, P-ITRs scale either because "aggregate routes
>> might
>> be selectively announced" or because "the same address might be announced
>> by multiple Proxy-ITRs in order to share the traffic." I really expected
>> the deployment draft to discuss this issue in more detail. As I believe
>> has been said before, these issues are very similar to the issues facing
>> the operators of a 6to4 forward or return relay. We have experimental
>> evidence there that altruism doesn't work and the incentives to "donate"
>> connectivity are insufficient. The analogy isn't perfect, but the
>> underlying
>> question is similar - what is the incentive for a particular operator to
>> offer P-ITR service for a particular bunch of EID prefixes, when the
>> clientele might be up to half the Internet, depending on who chooses to
>> propagate the routes?
> 
> I was hoping we addressed these concerns in Section 5.3, Proxy-ITR Route
> Distribution (PITR-RD).  I agree that altruism doesn't work, that's why
> the PITR-RD scenario is based on business relationships between
> different providers.  When someone registers a domain name, he/she pays
> an annual fee that should cover the operating expenses for publishing
> the domain in the global DNS.  The situation is similar with several
> other registration services.  When someone contacts a mapping service
> provider (MSR), to get their prefix registered in the LISP mapping
> system, they get the option of signing up for PITR services as well, for
> an extra fee.  These services may be offered by the MSP themselves, but
> it is expected that specialized P-ITR service providers (PSPs) will do
> it.  If they don't sign up, they become responsible for getting non-LISP
> traffic to their EIDs (using the LISP+BGP scenario).
> 
> Additionally, Tier 1 ISPs may offer P-ITR services to non-subscribers in
> strategic places just to attract more traffic from competitors, thus
> more revenue.
> 
> Should we add anything to this section to resolve the comment?

The explanation you have just written is quite informative. We're a bit
shy in the IETF about discussing incentives, but I think your explanation
would fit nicely into the draft. (I'm embarassed that we didn't
get this right for 6to4.)

>> The Security Considerations are minimal. I wonder if
>> draft-ietf-lisp-threats
>> identifies threats for each scenario described in
>> draft-ietf-lisp-deployment?
>> If not, the statement "Security implications of LISP deployments are
>> to be
>> discussed in separate documents." is rather optimistic.
>>
> 
> draft-ietf-lisp-threats discusses general LISP deployment security
> issues, without analyzing all scenarios described in
> draft-ietf-lisp-deployment.  I'm not sure such an iterative approach is
> necessary, unless scenario specific threats are discovered.


I expect you will be getting a Security Area review, so maybe
you'd better go by that.

    Brian

> 
> Best regards,
> -Lori
> 

From mahoney@nostrum.com  Thu Jul 11 15:05:34 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E219411E81B6 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 15:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AmACYzXmik78 for <gen-art@ietfa.amsl.com>; Thu, 11 Jul 2013 15:05:34 -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 5756E11E81A0 for <gen-art@ietf.org>; Thu, 11 Jul 2013 15:05:34 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6BM5NFP093636 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 11 Jul 2013 17:05:27 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51DF2C1E.4040902@nostrum.com>
Date: Thu, 11 Jul 2013 17:05:18 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-07-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jul 2013 22:05:35 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------

Francis Dupont    2013-07-25   draft-ietf-emu-crypto-bind-04


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 dromasca@avaya.com  Fri Jul 12 02:35:14 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9F3621F9C70 for <gen-art@ietfa.amsl.com>; Fri, 12 Jul 2013 02:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.845
X-Spam-Level: 
X-Spam-Status: No, score=-102.845 tagged_above=-999 required=5 tests=[AWL=-0.246, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFbeE03Sgzkl for <gen-art@ietfa.amsl.com>; Fri, 12 Jul 2013 02:35:09 -0700 (PDT)
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 3861921F9C7D for <gen-art@ietf.org>; Fri, 12 Jul 2013 02:35:09 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjYJAGzM31HGmAcV/2dsb2JhbABagmUhNE+tVJN9gQYWdIIjAQEBAQMBAQEPKDQLDAQCAQgNBAQBAQEKFAkHJwsUCQgCBAENBQgah20BC5pum3IXjh8QgQExBwaDA2wDniOLB4MRgXE3
X-IronPort-AV: E=Sophos;i="4.89,652,1367985600"; d="scan'208";a="19809649"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 12 Jul 2013 05:35:08 -0400
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 12 Jul 2013 05:33:18 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Fri, 12 Jul 2013 05:35:05 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "A. Jean Mahoney" <mahoney@nostrum.com>
Thread-Topic: [Gen-art] Timing of reviews: conclusion
Thread-Index: AQHOfkqR+TyYzb83v0auY/hSbpy9q5lgFRaAgAAU8ICAAJ+EoA==
Date: Fri, 12 Jul 2013 09:35:05 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA1286B27A@AZ-FFEXMB04.global.avaya.com>
References: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net> <9904FB1B0159DA42B0B887B7FA8119CA12868FF5@AZ-FFEXMB04.global.avaya.com> <959762B0-8152-4475-9B64-93A6F5C2DAB8@piuha.net>	<51DEFE1D.500@nostrum.com> <51DF0FAD.1010604@gmail.com>
In-Reply-To: <51DF0FAD.1010604@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Timing of reviews: conclusion
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 12 Jul 2013 09:35:14 -0000

+1



> -----Original Message-----
> From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On
> Behalf Of Brian E Carpenter
> Sent: Thursday, July 11, 2013 11:04 PM
> To: A. Jean Mahoney
> Cc: gen-art@ietf.org
> Subject: Re: [Gen-art] Timing of reviews: conclusion
>=20
> On 12/07/2013 06:49, A. Jean Mahoney wrote:
> > I'm also willing to help with the experiment, but I suggest that the
> > review tool be updated later, after we have a better idea of the new
> > requirements. Updating the review tool would probably require updating
> > datatracker also.
>=20
> Yes. The following is not a complaint, since the review tool is a much-
> appreciated volunteer effort, but IMHO it would be better if we
> submitted our reviews via the review tool, which could then send them on
> as email automatically. At the moment I usually forget to enter the
> review URL into the tool until some days or weeks later!
>=20
> (People who've used EDAS know what I mean.)
>=20
> It would also make sense for reviewers to be remembered by the tracker,
> so that they can get status updates automatically.
>=20
> Since the tracker already knows who is interested in each draft,
> integrating the two would make a lot of sense.
>=20
>    Brian
>=20
> >
> > I can easily capture early review assignments in the spreadsheets for
> now.
> >
> > Jean
> >
> >
> > On 7/11/13 10:23 AM, Jari Arkko wrote:
> >>> I am also in favor of the experiment and willing to participate.
> >>> Besides the changes pointed to by Brian we may also need to make
> >>> some adjustments to the Gen-ART tools (new column in the table at
> >>> http://art.tools.ietf.org/tools/art/genart/index.cgi/t=3D3634/fullque=
u
> >>> e to mark the WG review due date) and the process used by the
> >>> secretary (separate mail for WG early review?).
> >> That's a good point. Thanks.
> >>
> >> Jari
> >>
> >>
> >> _______________________________________________
> >> Gen-art mailing list
> >> Gen-art@ietf.org
> >> https://www.ietf.org/mailman/listinfo/gen-art
> >
> > _______________________________________________
> > Gen-art mailing list
> > Gen-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/gen-art
> >
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

From mahoney@nostrum.com  Fri Jul 12 07:19:38 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0212A11E8108 for <gen-art@ietfa.amsl.com>; Fri, 12 Jul 2013 07:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RabhzPq6trJl for <gen-art@ietfa.amsl.com>; Fri, 12 Jul 2013 07:19:37 -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 DC29C11E810C for <gen-art@ietf.org>; Fri, 12 Jul 2013 07:19:34 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6CEJYmM006191 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 12 Jul 2013 09:19:34 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51E01071.9090907@nostrum.com>
Date: Fri, 12 Jul 2013 09:19:29 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2013-07-18 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: Fri, 12 Jul 2013 14:19:38 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft
------------------------------------------------------------------------------------
Alexey Melnikov        2013-07-03   draft-ietf-multimob-pmipv6-ropt-07

Ben Campbell           2013-07-18   draft-ietf-jcardcal-jcard-04

David Black            2013-06-17   draft-ietf-abfab-eapapplicability-05 *

Elwyn Davies           2013-06-18   draft-ietf-payload-vp8-09 *

Francis Dupont         2013-07-01   draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-06 *

* 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 david.black@emc.com  Fri Jul 12 08:04:41 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 534A511E810E; Fri, 12 Jul 2013 08:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.477
X-Spam-Level: 
X-Spam-Status: No, score=-102.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EFaD0y+EAbNI; Fri, 12 Jul 2013 08:04:37 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1381811E811A; Fri, 12 Jul 2013 08:04:32 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6CF4Cqn004158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Jul 2013 11:04:13 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 12 Jul 2013 11:04:04 -0400
Received: from mxhub17.corp.emc.com (mxhub17.corp.emc.com [10.254.93.46]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6CF43ka003859; Fri, 12 Jul 2013 11:04:03 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub17.corp.emc.com ([10.254.93.46]) with mapi; Fri, 12 Jul 2013 11:04:03 -0400
From: "Black, David" <david.black@emc.com>
To: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, "jsalowey@cisco.com" <jsalowey@cisco.com>, General Area Review Team <gen-art@ietf.org>
Date: Fri, 12 Jul 2013 11:04:01 -0400
Thread-Topic: Gen-ART review of draft-ietf-abfab-eapapplicability-05
Thread-Index: Ac5rzQ3h5Vr98eb9RParuraCHgwUcgQTfgIgAL1zdeA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712983F32EC@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712983F2C87@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712983F2C87@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-abfab-eapapplicability-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, 12 Jul 2013 15:04:41 -0000

And the -05 version includes the text to address that editorial nit - it's
ready for publication as a Proposed Standard RFC.  Many thanks to the autho=
rs
for productively addressing the review comments.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Monday, July 08, 2013 4:44 PM
> To: Black, David; stefan.winter@restena.lu; jsalowey@cisco.com; General A=
rea
> Review Team
> Cc: ietf@ietf.org; abfab@ietf.org
> Subject: Gen-ART review of draft-ietf-abfab-eapapplicability-04
>=20
> The -04 version of this draft resolves the minor issue noted in
> the Gen-ART review of the -03 version.
>=20
> There is a remaining editorial nit, in that the one use of
> "non-network" in the -04 version would benefit from clarification.
> I suggest the following text change to the start of the paragraph
> that's split across pages 3 and 4 (change is to last line of excerpt):
>=20
> OLD
>    Operators need to carefully consider the security implications before
>    relaxing these requirements.  One potentially serious attack exists
>    when channel binding is not required and EAP authentication is
>    introduced into an existing non-network service.
>=20
> NEW
>    Operators need to carefully consider the security implications before
>    relaxing these requirements.  One potentially serious attack exists
>    when channel binding is not required and EAP authentication is
>    introduced into an existing service other than network access.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Monday, June 17, 2013 10:39 PM
> > To: stefan.winter@restena.lu; jsalowey@cisco.com; General Area Review T=
eam
> > Cc: ietf@ietf.org; abfab@ietf.org; Black, David
> > Subject: Gen-ART review of draft-ietf-abfab-eapapplicability-03
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-abfab-eapapplicability-03
> > Reviewer: David L. Black
> > Review Date: June 17, 2003
> > IETF LC End Date: June 17, 2003
> >
> > Summary:
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > This draft updates the applicability statement for EAP to include usage
> > for application layer access via EAP over GSSAPI.  Additional security
> > requirements are introduced for environments in which EAP is used for
> > that purpose.
> >
> > I found one open issue, which is minor, and may be editorial
> >
> > Major issues: None
> >
> > Minor issues: One
> >
> > The next to last paragraph on p.3 begins with this sentence:
> >
> >    For these reasons, channel binding MUST be implemented by peers, EAP
> >    servers and AAA servers in environments where EAP authentication is
> >    used to access application layer services.
> >
> > It appear that this "MUST" requirement applies to all uses of EAP,
> > including network access authentication, not just application layer acc=
ess
> > authentication.  If so, that's not immediately obvious from the text, a=
nd
> > an additional sentence should be added to make this clearer.  If not,
> > the above sentence needs to exclude network access authentication from
> > that requirement.
> >
> > Nits/editorial comments:
> >
> > The same paragraph (p.3) continues with:
> >
> >    In addition, channel
> >    binding MUST default to being required by peers for non-network
> >    authentication.  If the EAP server is aware that authentication is
> >    for something other than a network service, it too MUST default to
> >    requiring channel binding.
> >
> > What is meant by "non-network authentication" and "other than a network
> > service"?  If those mean "other than for network access authentication"
> > as the term "network access authentication" is used in section 1 and
> > RFC 3748, that meaning should be clarified.
> >
> > idnits 2.12.17 generated this comment:
> >
> >   -- The document seems to lack a disclaimer for pre-RFC5378 work, but =
may
> >      have content which was first submitted before 10 November 2008.  I=
f you
> >      have contacted all the original authors and they are all willing t=
o
> grant
> >      the BCP78 rights to the IETF Trust, then this is fine, and you can
> ignore
> >      this comment.  If not, you may need to add the pre-RFC5378 disclai=
mer.
> >      (See the Legal Provisions document at
> >      http://trustee.ietf.org/license-info for more information.)
> >
> > idnits appears to be confused ;-).  The -00 version of this draft is fr=
om
> > 2012,
> > and this draft does not contain sufficient material from RFC 3748 that =
would
> > raise that concern, so this comment should be ok to ignore.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From elwynd@dial.pipex.com  Fri Jul 12 08:35:47 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B054611E814D for <gen-art@ietfa.amsl.com>; Fri, 12 Jul 2013 08:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.099
X-Spam-Level: 
X-Spam-Status: No, score=-100.099 tagged_above=-999 required=5 tests=[AWL=2.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MFhh6gI3FBVV for <gen-art@ietfa.amsl.com>; Fri, 12 Jul 2013 08:35:47 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 31BE521F9E15 for <gen-art@ietf.org>; Fri, 12 Jul 2013 08:35:47 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1UxfNl-0004lT-0j; Fri, 12 Jul 2013 16:35:41 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Fri, 12 Jul 2013 16:30:41 +0100
Message-Id: <1373643041.4524.48488.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-ACL-Warn: Blacklisted URL in message. (ietf.org) in. See http://lookup.uribl.com.
Cc: draft-ietf-payload-vp8.all@tools.ietf.org
Subject: [Gen-art] Gen-art Telechat review of draft-ietf-payload-vp8-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jul 2013 15:35: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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-payload-vp8-08
Reviewer: Elwyn Davies
Review Date: 12 July 2013
IETF LC End Date: 18 June 2013 
IESG Telechat date: (if known) 18 July 2013

Summary: Essentially ready.  The nits from the last call review have
mostly been fixed - thanks. The issues with the references section have
only ben partly dealt with and there are still a mixture of bytes and
octets.  There is a rather awkquard downref to the VP8 coded data format
RFC 6386 - take advice from your AD on this one (he may already have
given it).
  
Major issues:

Minor issues:

Nits/editorial comments:
General: Consistent use of octets instead of bytes.

s10:  Are all of the refs normative?  If so change the section title.
The only one which I am dubious about is RFC 4566 (and there is  6386 -
see next comment).

s10:  idnits complains that RFC 3984 is not referenced (sorry the LC
review said 3894), and RFC 6386 is a downref (you had better ask your AD
about this downref - it is fairly fundamental!)


From martin.thomson@gmail.com  Fri Jul 12 09:14:09 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C9CB21F9E33 for <gen-art@ietfa.amsl.com>; Fri, 12 Jul 2013 09:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.315
X-Spam-Level: 
X-Spam-Status: No, score=-2.315 tagged_above=-999 required=5 tests=[AWL=0.285,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ciZaA4Zsek0w for <gen-art@ietfa.amsl.com>; Fri, 12 Jul 2013 09:14:09 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 084C621F9E71 for <gen-art@ietf.org>; Fri, 12 Jul 2013 09:14:08 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id z11so8177124wgg.34 for <gen-art@ietf.org>; Fri, 12 Jul 2013 09:14:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CISMc+3VmQ8AeI5CbqGyI99FGm6YN5xP/NBcIcB5SVQ=; b=z8L3rUmLJxseAuwRsJrxKI6rbpMUw8/hkZup+TJODteFFlZ2BgT2ENwawpHrwcAaEy zM3zG52G15ts5nv/yZf4zPUGMjO9AY86IPqu0rN3VByZdzTvPeOxeV6unECQCpAdNYkn FvsdDXwGwyXgaSj+eGtkbNXMqKFReDdV+wdre88yteyhORBTXo84hBx9D+0c8eamSVR2 +pfNJq6/YMLkElrqTET+cb4glStTpoRHf1jnS0jnMdGVsignCOluvooLeUWLFzp3PPVJ /tAHypUsAe8Ykq/wr9GYo3NqlfmsKMF1F9kNZXJxoGZx4b0Rvm8LoOrlTmOQG81vUmeG +Blg==
MIME-Version: 1.0
X-Received: by 10.194.77.99 with SMTP id r3mr24653406wjw.5.1373645648079; Fri, 12 Jul 2013 09:14:08 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Fri, 12 Jul 2013 09:14:08 -0700 (PDT)
In-Reply-To: <51DF0FAD.1010604@gmail.com>
References: <543A2FC3-DED1-41AD-AA13-E481DBF3359E@piuha.net> <9904FB1B0159DA42B0B887B7FA8119CA12868FF5@AZ-FFEXMB04.global.avaya.com> <959762B0-8152-4475-9B64-93A6F5C2DAB8@piuha.net> <51DEFE1D.500@nostrum.com> <51DF0FAD.1010604@gmail.com>
Date: Fri, 12 Jul 2013 09:14:08 -0700
Message-ID: <CABkgnnU5GGLcdexuyo_UvXhRJ-FfJACdVvv_t5JL06_S9yLHFA@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: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Timing of reviews: conclusion
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 12 Jul 2013 16:14:09 -0000

On 11 July 2013 13:03, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> but IMHO it would be better
> if we submitted our reviews via the review tool, which could then
> send them on as email automatically.

I have all the same problems as Brian.  And this might also make
access control easier, such that reviews could be sent to WG lists
without requiring sign-up (though on reflection, that's a little
optimistic).

From jari.arkko@piuha.net  Mon Jul 15 23:12:32 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7628021F8756 for <gen-art@ietfa.amsl.com>; Mon, 15 Jul 2013 23:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Pe8X3czLyLZ for <gen-art@ietfa.amsl.com>; Mon, 15 Jul 2013 23:12:14 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 16EB821E81A8 for <gen-art@ietf.org>; Mon, 15 Jul 2013 23:12:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A989B2CC53; Tue, 16 Jul 2013 09:12:09 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zhh0-ouUCa-3; Tue, 16 Jul 2013 09:12:09 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 3815F2CC3C; Tue, 16 Jul 2013 09:12:08 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <1373643041.4524.48488.camel@mightyatom>
Date: Tue, 16 Jul 2013 08:12:07 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <08F34797-430C-415D-BC16-1AE06FCC1996@piuha.net>
References: <1373643041.4524.48488.camel@mightyatom>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1508)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-payload-vp8.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art Telechat review of draft-ietf-payload-vp8-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 06:12:32 -0000

Elwyn, many thanks for your review! I have raised the =
normative/informative question in my IESG review as an issue.

Jari

On Jul 12, 2013, at 5:30 PM, Elwyn Davies <elwynd@dial.pipex.com> wrote:

> s10:  Are all of the refs normative?  If so change the section title.
> The only one which I am dubious about is RFC 4566 (and there is  6386 =
-
> see next comment).


From jari.arkko@piuha.net  Mon Jul 15 23:24:14 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FBFA21F9DBE; Mon, 15 Jul 2013 23:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UEABjIvSuYk0; Mon, 15 Jul 2013 23:24:09 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 02F0921F9D09; Mon, 15 Jul 2013 23:24:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4ED882CC53; Tue, 16 Jul 2013 09:24:08 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cufW7r3I3BaK; Tue, 16 Jul 2013 09:24:07 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id E5A002CC3C; Tue, 16 Jul 2013 09:24:05 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712983F32EC@MX15A.corp.emc.com>
Date: Tue, 16 Jul 2013 08:24:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6356DA73-32CE-4B32-B760-48AED3B04120@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE71298265158@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712983F2C87@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712983F32EC@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Cc: "stefan.winter@restena.lu" <stefan.winter@restena.lu>, General Area Review Team <gen-art@ietf.org>, "jsalowey@cisco.com" <jsalowey@cisco.com>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-abfab-eapapplicability-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 06:24:14 -0000

> And the -05 version includes the text to address that editorial nit - =
it's
> ready for publication as a Proposed Standard RFC.  Many thanks to the =
authors
> for productively addressing the review comments.

And many thanks to you, David, for your review. Based on this review and =
my own review of this document, I have balloted Yes on the document.=20

Jari


From jari.arkko@piuha.net  Mon Jul 15 23:29:31 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D50821F9BA2 for <gen-art@ietfa.amsl.com>; Mon, 15 Jul 2013 23:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5df4bFCw7NT for <gen-art@ietfa.amsl.com>; Mon, 15 Jul 2013 23:29:26 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 056DE21F9B94 for <gen-art@ietf.org>; Mon, 15 Jul 2013 23:29:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4FCEE2CC53; Tue, 16 Jul 2013 09:29:25 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OFzMppADLJz5; Tue, 16 Jul 2013 09:29:24 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id DFC452CC3C; Tue, 16 Jul 2013 09:29:23 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201306271628.r5RGS2N1050704@givry.fdupont.fr>
Date: Tue, 16 Jul 2013 08:29:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <993CCE3E-8067-4FFC-AA46-1FB9FFC41F5A@piuha.net>
References: <201306271628.r5RGS2N1050704@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org, draft-ietf-xrblock-rtcp-xr-discard-rle-metrics.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-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: Tue, 16 Jul 2013 06:29:31 -0000

Francis: Thank you very much for your review. I'm basing my IESG =
recommendation on this review.

Jari


From jari.arkko@piuha.net  Tue Jul 16 00:36:51 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF1E11E8233 for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 00:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Rbfu7Vy7cZ9 for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 00:36:47 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9518A11E8257 for <gen-art@ietf.org>; Tue, 16 Jul 2013 00:36:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E0C252CC53; Tue, 16 Jul 2013 10:36:40 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q0tAsVBeniVb; Tue, 16 Jul 2013 10:36:39 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 93C6B2CC3C; Tue, 16 Jul 2013 10:36:38 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <1373115697.4524.42154.camel@mightyatom>
Date: Tue, 16 Jul 2013 09:36:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B3ED28F-E27B-4B16-B73E-8070B830D437@piuha.net>
References: <1373115697.4524.42154.camel@mightyatom>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1508)
Cc: draft-ietf-dhc-dhcpv6-failover-requirements.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art LC review: draft-ietf-dhc-dhcpv6-failover-requirements-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 07:36:51 -0000

Thank you for your review, Elwyn. Do the authors have any thoughts on =
the issues that Elwyn raises here?

Jari

On Jul 6, 2013, at 3:01 PM, Elwyn Davies <elwynd@dial.pipex.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 resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-dhc-dhcpv6-failover-requirements-06.txt
> Reviewer: Elwyn Davies
> Review Date: 6 July 2013
> IETF LC End Date: 17 July 2013
> IESG Telechat date: (if known) -
>=20
> Summary: Almost ready.  There are a few very minor issues and a fair
> number of editorial nits to fix but generally in good shape.
>=20
> Major issues:
> None
>=20
> Minor issues:
> s1, Introduction of Primary/Secondary terminology: The introduction
> talks about multiple servers (i.e., potentially > 2) but then in the
> last sentence of para 1 introduces primary and secondary servers.  The
> initial impression this gives is that the number of servers has now =
been
> reduced to <=3D 2.  Having read through the rest of the document I can =
see
> how I am supposed to interpret the last sentence of para 1, but things
> would be much clearer if an extra sentence or three describing the
> chosen model (and its intended extension) was added just before this
> last sentence.  Maybe something like:
>   The failover model, to which these requirements apply, will =
initially
>   be a pairwise "hot standby" model (see Section 4.1) with a primary=20=

>   server used in normal operation switching over to a backup secondary=20=

>   server in the event of failure.  Optionally, a secondary server may=20=

>   provide failover service for multiple primary servers.  However the=20=

>   requirements will not preclude a future load-balancing extension=20
>   where there is a symmetric failover relationship.=20
>=20
> s7: Related to the previous comment, perhaps it should be made =
explicit
> that the resulting protocol is "load-balancing friendly" to avoid =
rework
> if at all possible.  Since both v4 and v6 load-balancing and v4 =
failover
> with load-balancing are in progress, it should be known how to avoid
> pitfalls by the time the v6 failover protocol is designed!
>=20
> s7, item 4, last sentence:=20
> "Long-lived connections must not be disturbed."
> I don't believe the DHCPv6 server or the failover protocol can either
> know that an address is in use for long lived connections or guarantee
> that they won't be disturbed beyond what is said earlier in this item.
> Presumably what is meant is something like: "Lease stability has the =
aim
> of avoiding disturbance to long-lived connections."
>=20
> s7, item 6:  Maybe irrelevant thought: Presumably you could build a
> failover system using a shared, reliable database and a minimalistic
> version of the failover protocol instead of using lazy updates.  =
Should
> this be explicitly an option?
>=20
> s7, last para: "Despite the lack of standardization of DHCPv4
> failover...": It appears that work is in progress on this
> (http://tools.ietf.org/html/draft-ietf-dhc-failover-12)... so what is
> meant here?
>=20
> Nits/editorial comments:
>=20
> Global: s/i.e./i.e.,/
> Global: s/e.g./e.g.,/
>=20
> Abstract: s/any way/any way that/
>=20
> s2: Expoand acronyms CPR, IA - even though IA is defined in RFC 3315, =
it
> would help readability to repeat the expansion.
>=20
> s2, lease: Should this mention something about length of time for =
which
> the lease will be valid?
>=20
> s3.1.1: Expand PXE acronym.
>=20
> s3.1.1, para 1:
> OLD
>   Address and possibly other
>   configuration parameters are used during boot process and are
>   discarded afterwards.=20
> NEW:
>   The address and possibly other
>   configuration parameters are used during the boot process and are
>   discarded thereafter.=20
>=20
> s3.1.1, para 2: s/distinct preference set/a distinct preference set/
>=20
> s3.1.2, para 2:
> OLD:
>   There are several well documented approaches how such deployment
>   works.=20
> NEW:
>   There are several well-documented approaches showing how such a =
deployment
>   could work.
>=20
> s3.1.3, para 2:
> OLD:
>   It is also essential to use only databases that are really
>   distributed and do not have single point of failure themselves.
> NEW:
>   It is also essential to use only a database system that provides=20
>   equivalent reliability and failover capability.=20
>=20
> s4: This paragraph implies that the document defines a protocol =
contrary
> to its expressed intention and reality.
> OLD:
>   These scenarios may be inside or
>   outside of scope for DHCPv6 failover protocol as defined by this
>   document.  They are enumerated here to provide a common basis for
>   discussion.
> NEW:
>   These scenarios may be in or
>   out of scope for the DHCPv6 failover model to which this=20
>   document's requirements apply; they are enumerated here to provide a=20=

>   common basis for discussion.  =20
>=20
> s5, para 2: s/General failover concept/The general failover concept/,=20=

> s/in case of the primary server/in case of a primary server/,
> s/In case of just/In the case of just/,
> s/Had there be more than two partners/Were there more than two =
partners/
> (subjunctive!)
>=20
> s5, para 2:
> OLD:
>   there would be a third states in between (some
>   partners updated their state, but some didn't).
> NEW:
>   there would be intermediate, inconsistent states where some partners
>   had updated their state and some had not.
>=20
> s4.1: s/Only one of partners/Only one of the partners/
>=20
> s4.6, para 2: s/every time IPv6 address changes/every time an IPv6
> address changes/
>=20
> s4.6, para 3: s/having stable address/having a stable address/
>=20
> s5.1, last sentence:  This seems to imply that *this section* states
> whether the failure mode is in or out of scope for the protocol.  It
> doesn't - that is postponed to s7.  Either remove this sentence or
> redraft to refer to s7.
>=20
> s5.1.2, para 2: s/is that partner also detected/is that the partner =
also
> detected/
>=20
> s5.2: s/synchronization methods/synchronization method/,
> s/familiarity with distributed database/familiarity with distributed =
database technology/
>=20
> s5.2.1, para 1: s/response from partner/response from its partner/
>=20
> s5.2.1, para 2: 'large' is an over-generalization. Maybe:
> s/a large performance penalty/typically a significant performance =
penalty/
>=20
> s5.2.1, para 3:
> OLD:
> Due to advent of SSD disks or battery backed ram disks technology,
> NEW:
> Due to the advent of fast SSD (solid state disk) and battery-backed =
RAM=20
> (random access memory) disk technology,
>=20
> s5.2.2, para 2: s/if server crashes/if the server crashes/
>=20
> s7, item 4: s/should pose/should have/
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From alexey.melnikov@isode.com  Tue Jul 16 03:16:56 2013
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79C1811E8276 for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 03:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.671
X-Spam-Level: 
X-Spam-Status: No, score=-102.671 tagged_above=-999 required=5 tests=[AWL=-0.073, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FeBIhTIDHjUp for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 03:16:55 -0700 (PDT)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6928121E81DF for <gen-art@ietf.org>; Tue, 16 Jul 2013 03:16:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1373969807; d=isode.com; s=selector; i=@isode.com; bh=UhmvCFExXaoVoaHR7eiSK6S6PGXj3U+AMyo+JFqpAY8=; 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=pjvS9Jl3/wHQfYu5J0/ZN8Q0u3bP0U/W75s7o/xd1KAstPyp0gFnzO3e6XJ8OJ8Imh1RTQ L4VXsR9aNSWkgASVqVrek66ri9A0hHa0V5bcCSZVwhQwGevRSW4vgAqez2u5rwUSsF7Fr0 vbkS/UK3ALFS5PVhEv9YZrxNFOXy+Es=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UeUdjQBjM3Qv@waldorf.isode.com>; Tue, 16 Jul 2013 11:16:47 +0100
Message-ID: <51E51DA9.8000005@isode.com>
Date: Tue, 16 Jul 2013 11:17:13 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: draft-ietf-multimob-pmipv6-ropt.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------000607020007020501030504"
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-Art review of draft-ietf-multimob-pmipv6-ropt-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 10:16:56 -0000

This is a multi-part message in MIME format.
--------------000607020007020501030504
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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

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

Document: draft-ietf-multimob-pmipv6-ropt-07.txt

Reviewer: Alexey Melnikov

Review Date: 16 July 2013

IETF LC End Date: 3 July 2013

IESG Telechat date: 18 July 2013

Summary: Ready for publication as an Experimental RFC with some nits


Major issues: None

Minor issues:



In 5.1.2:

Dynamic IP Multicast Selector Mode Flag:

       This field indicates the subscription via MTMA/direct routing
       mode.  If the (M) flag value is set to a value of (1), it is an
       indication that the IP multicast traffic associated to the
       multicast group(s) identified by the Multicast Address Record(s)
       in this mobility option SHOULD be routed locally (subscription via
       direct routing mode).  If the (M) flag value is set to a value of
       (0), it is an indication that IP multicast traffic associated to
       the multicast group(s) identified by the Multicast Address Record
       in this mobility option(s) SHOULD be routed to the home network,
       via the MTMA (subscription via MTMA mode).  All other IP traffic
       associated with the mobile node SHOULD be managed according to a
       default policy configured at the PMIPv6 multicast domain.

The last sentence: I don't think you should use RFC 2119 SHOULD here.
I think you are saying that this document doesn't affect all other IP
traffic. So just use "is managed" instead of "SHOULD be managed".


Is IANA Considerations section clear to IANA? I suggest you add at least 
the URI for the IANA registry.
Is IANA registration policy compatible with the type of document 
(Experimental)? I can't check that, as I don't know which registry you 
are talking about.


Nits/editorial comments:


In 3.3: acronyms PBU and PBA need to be expanded on first use. They are 
expanded further down in the document.



--------------000607020007020501030504
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=ISO-8859-1">
    <meta name="Generator" content="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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
  </head>
  <body lang="EN-US" link="blue" text="#000000" vlink="purple"
    bgcolor="#FFFFFF">
    <div class="WordSection1"><span style="font-family:&quot;Courier
        New&quot;">I am the assigned Gen-ART reviewer for this draft.
        For background on Gen-ART, please see the FAQ at<o:p></o:p></span><span
        style="font-family:&quot;Courier New&quot;"><o:p> </o:p><a class="moz-txt-link-rfc2396E" href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.<o:p></o:p></span><span
        style="font-family:&quot;Courier New&quot;"><o:p><br>
          <br>
        </o:p>Please resolve these comments along with any other Last
        Call comments you may receive.<o:p></o:p></span>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;"><o:p>&nbsp;</o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;">Document:</span>
        draft-ietf-multimob-pmipv6-ropt-07.txt</p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;">Reviewer: Alexey Melnikov<o:p></o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;">Review Date: 16 July 2013<o:p></o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;">IETF LC End Date: 3 July 2013<o:p></o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;">IESG Telechat date: 18 July 2013</span><span
          style="color: rgb(0, 0, 0); font-family: arial, helvetica,
          clean, sans-serif; font-size: 13px; font-style: normal;
          font-variant: normal; font-weight: normal; letter-spacing:
          normal; line-height: 16px; orphans: auto; text-align: start;
          text-indent: 0px; text-transform: none; white-space: normal;
          widows: auto; word-spacing: 0px; -webkit-text-stroke-width:
          0px; background-color: rgb(237, 245, 255); display: inline
          !important; float: none;"></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;"><o:p>&nbsp;</o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;">Summary: Ready for publication as an Experimental
          RFC with some nits<o:p></o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;"><o:p><br>
          </o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;">Major issues: None<o:p></o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;"><o:p>&nbsp;</o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;">Minor issues:<br>
        </span></p>
      <p class="MsoPlainText"><br>
        <br>
        In 5.1.2:<br>
        <br>
        Dynamic IP Multicast Selector Mode Flag:<br>
        <br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This field indicates the subscription via MTMA/direct
        routing<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mode.&nbsp; If the (M) flag value is set to a value of (1), it
        is an<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indication that the IP multicast traffic associated to the<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast group(s) identified by the Multicast Address
        Record(s)<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in this mobility option SHOULD be routed locally
        (subscription via<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; direct routing mode).&nbsp; If the (M) flag value is set to a
        value of<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0), it is an indication that IP multicast traffic
        associated to<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the multicast group(s) identified by the Multicast Address
        Record<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in this mobility option(s) SHOULD be routed to the home
        network,<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; via the MTMA (subscription via MTMA mode).&nbsp; All other IP
        traffic<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; associated with the mobile node SHOULD be managed
        according to a<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default policy configured at the PMIPv6 multicast domain.<br>
        <br>
        The last sentence: I don't think you should use RFC 2119 SHOULD
        here.<br>
        I think you are saying that this document doesn't affect all
        other IP<br>
        traffic. So just use "is managed" instead of "SHOULD be
        managed".<br>
        <br>
        <br>
        Is IANA Considerations section clear to IANA? I suggest you add
        at least the URI for the IANA registry.<br>
        Is IANA registration policy compatible with the type of document
        (Experimental)? I can't check that, as I don't know which
        registry you are talking about.<br>
        <br>
        <br>
        <span style="font-family:&quot;Courier New&quot;"><o:p></o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;"><o:p>&nbsp;</o:p></span></p>
      <p class="MsoPlainText"><span style="font-family:&quot;Courier
          New&quot;">Nits/editorial comments:<br>
        </span></p>
      <p class="MsoPlainText"><br>
      </p>
      <p class="MsoPlainText">In 3.3: acronyms PBU and PBA need to be
        expanded on first use. They are expanded further down in the
        document.</p>
      <p class="MsoPlainText"><br>
        <span style="font-family:&quot;Courier New&quot;"><o:p></o:p></span></p>
    </div>
  </body>
</html>

--------------000607020007020501030504--

From alexey.melnikov@isode.com  Tue Jul 16 03:28:20 2013
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0418911E8294 for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 03:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.667
X-Spam-Level: 
X-Spam-Status: No, score=-102.667 tagged_above=-999 required=5 tests=[AWL=-0.068, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bKDlEDTUt6W4 for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 03:28:19 -0700 (PDT)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4D81711E80A5 for <gen-art@ietf.org>; Tue, 16 Jul 2013 03:28:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1373970498; d=isode.com; s=selector; i=@isode.com; bh=fZKmTWVpL74+aEboQNZDowis1QE9Xd/TPzuU7WxnGLA=; 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=HSS9Y/34Wy/gsOpxOR2lOUBGgLmElN0rFlvA2zO/uXW51SB7WAiKogq1TtjjYKllPwEEFU HMyLrV8C+A+EO5aKlDItEBhiz8PwpqndXwrjiRo0c2NloNy6IjOMcPYcnr75nQ86smxF09 pw5Avw2QEYM29cRCOZM3Sbvuqls0+7c=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UeUgOwBjM4tE@waldorf.isode.com>; Tue, 16 Jul 2013 11:28:18 +0100
Message-ID: <51E52056.6070501@isode.com>
Date: Tue, 16 Jul 2013 11:28:38 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: draft-ietf-pce-gmpls-aps-req.all@tools.ietf.org
References: <51B05EE4.1010405@isode.com>
In-Reply-To: <51B05EE4.1010405@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-pce-gmpls-aps-req-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 10:28:20 -0000

Sorry for the confusion with my earlier email, I corrected the subject 
for my review.

On 06/06/2013 11:05, Alexey Melnikov wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document:  draft-ietf-pce-gmpls-aps-req-07
> Reviewer: Alexey Melnikov
> Review Date: 2013-06-06
> IETF LC End Date: 2013-06-07
> IESG Telechat date: (if known)
>
> Summary: This draft is ready for publication as an informational RFC.
>
> Major issues: None.
>
> Minor issues: None.
>
> Nits/editorial comments:
>
> I might have missed that, but I think the first mention of ERO
> needs expansion of the acronym and a reference.


From kkinnear@cisco.com  Tue Jul 16 07:38:11 2013
Return-Path: <kkinnear@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 4263121F9DAB for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 07:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6EgyAt5gnZ2Z for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 07:38:06 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 166B121E808E for <gen-art@ietf.org>; Tue, 16 Jul 2013 07:38:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9892; q=dns/txt; s=iport; t=1373985486; x=1375195086; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=MGYIweWM/Uyv1sIEtSFZ46otSNrLI7N8MeBTr0JjwYY=; b=doVYa892oAGljxl/0UPdDcZip7CZ5qjEBQqOvMHKhSpXMIyXJQOwtJgj Oc9+l8Jjp7mmqAx3OERR1wOLilYV173lcEI1KdA5MLUQoWyPdNhP6P1Jp JFS1/hEQxXRJWzLF9ZCxPtigSR+brAUlHlsccLGF8n1v9c2zuKSFSAGiz E=;
X-IronPort-AV: E=Sophos;i="4.89,677,1367971200"; d="scan'208";a="235537546"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-4.cisco.com with ESMTP; 16 Jul 2013 14:38:06 +0000
Received: from printer-xerox-test-5735.cisco.com (printer-xerox-test-5735.cisco.com [161.44.65.115]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6GEc4b1020873;  Tue, 16 Jul 2013 14:38:04 GMT
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <7B3ED28F-E27B-4B16-B73E-8070B830D437@piuha.net>
Date: Tue, 16 Jul 2013 10:38:05 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <130E5C09-1C4D-4EF1-AE09-95E3F9D29F63@cisco.com>
References: <1373115697.4524.42154.camel@mightyatom> <7B3ED28F-E27B-4B16-B73E-8070B830D437@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>, Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Tue, 16 Jul 2013 07:41:49 -0700
Cc: draft-ietf-dhc-dhcpv6-failover-requirements.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [Gen-art] Gen-art LC review: draft-ietf-dhc-dhcpv6-failover-requirements-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 14:38:11 -0000

Jari, Elwyn,

Elwyn -- thank you for the thoughtful review.  My comments
are indented below...

On Jul 16, 2013, at 3:36 AM, Jari Arkko wrote:

> Thank you for your review, Elwyn. Do the authors have any thoughts on =
the issues that Elwyn raises here?
>=20
> Jari
>=20
> On Jul 6, 2013, at 3:01 PM, Elwyn Davies <elwynd@dial.pipex.com> =
wrote:
>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document: draft-ietf-dhc-dhcpv6-failover-requirements-06.txt
>> Reviewer: Elwyn Davies
>> Review Date: 6 July 2013
>> IETF LC End Date: 17 July 2013
>> IESG Telechat date: (if known) -
>>=20
>> Summary: Almost ready.  There are a few very minor issues and a fair
>> number of editorial nits to fix but generally in good shape.
>>=20
>> Major issues:
>> None
>>=20
>> Minor issues:
>> s1, Introduction of Primary/Secondary terminology: The introduction
>> talks about multiple servers (i.e., potentially > 2) but then in the
>> last sentence of para 1 introduces primary and secondary servers.  =
The
>> initial impression this gives is that the number of servers has now =
been
>> reduced to <=3D 2.  Having read through the rest of the document I =
can see
>> how I am supposed to interpret the last sentence of para 1, but =
things
>> would be much clearer if an extra sentence or three describing the
>> chosen model (and its intended extension) was added just before this
>> last sentence.  Maybe something like:
>>  The failover model, to which these requirements apply, will =
initially
>>  be a pairwise "hot standby" model (see Section 4.1) with a primary=20=

>>  server used in normal operation switching over to a backup secondary=20=

>>  server in the event of failure.  Optionally, a secondary server may=20=

>>  provide failover service for multiple primary servers.  However the=20=

>>  requirements will not preclude a future load-balancing extension=20
>>  where there is a symmetric failover relationship.=20

	Yes, this is a fine idea.  Thanks for the sentence.
>>=20
>> s7: Related to the previous comment, perhaps it should be made =
explicit
>> that the resulting protocol is "load-balancing friendly" to avoid =
rework
>> if at all possible.  Since both v4 and v6 load-balancing and v4 =
failover
>> with load-balancing are in progress, it should be known how to avoid
>> pitfalls by the time the v6 failover protocol is designed!

	Sure, we'll put something in to deal with that.
>>=20
>> s7, item 4, last sentence:=20
>> "Long-lived connections must not be disturbed."
>> I don't believe the DHCPv6 server or the failover protocol can either
>> know that an address is in use for long lived connections or =
guarantee
>> that they won't be disturbed beyond what is said earlier in this =
item.
>> Presumably what is meant is something like: "Lease stability has the =
aim
>> of avoiding disturbance to long-lived connections."

	Yes, we'll reword this as you suggest.
>>=20
>> s7, item 6:  Maybe irrelevant thought: Presumably you could build a
>> failover system using a shared, reliable database and a minimalistic
>> version of the failover protocol instead of using lazy updates.  =
Should
>> this be explicitly an option?

	Well, this thought is explored in Section 3.1.3, but under
	the overall heading of "Alternatives to Failover".  Is this
	an alternative *to* failover, or an option *for* failover=20
	(as you suggest might be appropriate)?  Hard to say.=20
=20
	I suppose that our design draft, already about to go to
	last call, influenced our thinking to some degree when we
	wrote this.  I don't think the document would be substantively
	better were we to change it so that a distributed database
	solution is an option as opposed to an alternative.  So,
	to be clear, I don't think changing this is a good idea.

>>=20
>> s7, last para: "Despite the lack of standardization of DHCPv4
>> failover...": It appears that work is in progress on this
>> (http://tools.ietf.org/html/draft-ietf-dhc-failover-12)... so what is
>> meant here?

	The work in progress ended years ago.  Many years ago.
	The document which you reference is ~132 pages long, and
	has requirements, design, and protocol all in one
	document.  It was essentially too big and complicated to
	be digested by the IETF.  We could not even get the AD at
	the time to review the entire document.  In part this was
	because the problem was important to solve in an
	intra-vendor way, but inter-vendor capable failover was
	not important in the real world (i.e., nobody really
	cared to pay extra for failover that worked across two
	vendors servers).

	The experience gained during the v4 failover effort is
	the reason the v6 failover effort (of which the document
	under discussion is a part) has been split into three
	separate pieces: requirements, design, and (if sufficient
	interest exists), protocol.  The hope is that these
	pieces will be individually digestible where the v4
	effort was not.

	That said, the v6 failover design draft is already 50
	pages, and it hasn't yet undergone WG last call, though
	it is very close to that point. =20

	Plus, it is possible that we will end with the design
	document, since that will have the basics of how you
	build a v6 failover capability.  The protocol document is
	only really interesting if you want to have an
	inter-vendor failover capability.  We don't yet know how
	that will play out, though we certainly expect to give
	it a try.
>>=20
>> Nits/editorial comments:

	Thank you for catching these.  We will make all of these
	changes.

	Thanks again for your review!

	Regards -- Kim

>>=20
>> Global: s/i.e./i.e.,/
>> Global: s/e.g./e.g.,/
>>=20
>> Abstract: s/any way/any way that/
>>=20
>> s2: Expoand acronyms CPR, IA - even though IA is defined in RFC 3315, =
it
>> would help readability to repeat the expansion.
>>=20
>> s2, lease: Should this mention something about length of time for =
which
>> the lease will be valid?
>>=20
>> s3.1.1: Expand PXE acronym.
>>=20
>> s3.1.1, para 1:
>> OLD
>>  Address and possibly other
>>  configuration parameters are used during boot process and are
>>  discarded afterwards.=20
>> NEW:
>>  The address and possibly other
>>  configuration parameters are used during the boot process and are
>>  discarded thereafter.=20
>>=20
>> s3.1.1, para 2: s/distinct preference set/a distinct preference set/
>>=20
>> s3.1.2, para 2:
>> OLD:
>>  There are several well documented approaches how such deployment
>>  works.=20
>> NEW:
>>  There are several well-documented approaches showing how such a =
deployment
>>  could work.
>>=20
>> s3.1.3, para 2:
>> OLD:
>>  It is also essential to use only databases that are really
>>  distributed and do not have single point of failure themselves.
>> NEW:
>>  It is also essential to use only a database system that provides=20
>>  equivalent reliability and failover capability.=20
>>=20
>> s4: This paragraph implies that the document defines a protocol =
contrary
>> to its expressed intention and reality.
>> OLD:
>>  These scenarios may be inside or
>>  outside of scope for DHCPv6 failover protocol as defined by this
>>  document.  They are enumerated here to provide a common basis for
>>  discussion.
>> NEW:
>>  These scenarios may be in or
>>  out of scope for the DHCPv6 failover model to which this=20
>>  document's requirements apply; they are enumerated here to provide a=20=

>>  common basis for discussion.  =20
>>=20
>> s5, para 2: s/General failover concept/The general failover concept/,=20=

>> s/in case of the primary server/in case of a primary server/,
>> s/In case of just/In the case of just/,
>> s/Had there be more than two partners/Were there more than two =
partners/
>> (subjunctive!)
>>=20
>> s5, para 2:
>> OLD:
>>  there would be a third states in between (some
>>  partners updated their state, but some didn't).
>> NEW:
>>  there would be intermediate, inconsistent states where some partners
>>  had updated their state and some had not.
>>=20
>> s4.1: s/Only one of partners/Only one of the partners/
>>=20
>> s4.6, para 2: s/every time IPv6 address changes/every time an IPv6
>> address changes/
>>=20
>> s4.6, para 3: s/having stable address/having a stable address/
>>=20
>> s5.1, last sentence:  This seems to imply that *this section* states
>> whether the failure mode is in or out of scope for the protocol.  It
>> doesn't - that is postponed to s7.  Either remove this sentence or
>> redraft to refer to s7.
>>=20
>> s5.1.2, para 2: s/is that partner also detected/is that the partner =
also
>> detected/
>>=20
>> s5.2: s/synchronization methods/synchronization method/,
>> s/familiarity with distributed database/familiarity with distributed =
database technology/
>>=20
>> s5.2.1, para 1: s/response from partner/response from its partner/
>>=20
>> s5.2.1, para 2: 'large' is an over-generalization. Maybe:
>> s/a large performance penalty/typically a significant performance =
penalty/
>>=20
>> s5.2.1, para 3:
>> OLD:
>> Due to advent of SSD disks or battery backed ram disks technology,
>> NEW:
>> Due to the advent of fast SSD (solid state disk) and battery-backed =
RAM=20
>> (random access memory) disk technology,
>>=20
>> s5.2.2, para 2: s/if server crashes/if the server crashes/
>>=20
>> s7, item 4: s/should pose/should have/
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20


From cjbc@it.uc3m.es  Tue Jul 16 11:42:34 2013
Return-Path: <cjbc@it.uc3m.es>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C20A21F9A3B for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 11:42:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.179
X-Spam-Level: 
X-Spam-Status: No, score=-6.179 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wCoO0p+cznqu for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 11:42:22 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by ietfa.amsl.com (Postfix) with ESMTP id 3FDDB21E8054 for <gen-art@ietf.org>; Tue, 16 Jul 2013 11:42:21 -0700 (PDT)
Received: from smtp01.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id F16DACC4948; Tue, 16 Jul 2013 20:42:20 +0200 (CEST)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [10.3.251.252] (interdigital.vlan431.asr1.yyz1.gblx.net [208.49.79.242]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp01.uc3m.es) by smtp01.uc3m.es (Postfix) with ESMTPSA id 4B433CC5B0D; Tue, 16 Jul 2013 20:42:20 +0200 (CEST)
Message-ID: <1374000138.7044.90.camel@acorde.it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Tue, 16 Jul 2013 20:42:18 +0200
In-Reply-To: <51E51DA9.8000005@isode.com>
References: <51E51DA9.8000005@isode.com>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.4.4-3 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.0.0.1014-20020.001
Cc: gen-art@ietf.org, draft-ietf-multimob-pmipv6-ropt.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-multimob-pmipv6-ropt-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cjbc@it.uc3m.es
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 16 Jul 2013 18:42:34 -0000

Hi Alexey,

Thanks a lot for the review. Please see below some comments inline.

On Tue, 2013-07-16 at 11:17 +0100, Alexey Melnikov wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please resolve these comments along with any other Last Call comments
> you may receive. 
> 
>  
> 
> Document: draft-ietf-multimob-pmipv6-ropt-07.txt
> 
> Reviewer: Alexey Melnikov
> 
> Review Date: 16 July 2013
> 
> IETF LC End Date: 3 July 2013
> 
> IESG Telechat date: 18 July 2013
> 
>  
> 
> Summary: Ready for publication as an Experimental RFC with some nits
> 
> 
> Major issues: None
> 
>  
> 
> Minor issues:
> 
> 
> 
> 
> In 5.1.2:
> 
> Dynamic IP Multicast Selector Mode Flag:
> 
>       This field indicates the subscription via MTMA/direct routing
>       mode.  If the (M) flag value is set to a value of (1), it is an
>       indication that the IP multicast traffic associated to the
>       multicast group(s) identified by the Multicast Address Record(s)
>       in this mobility option SHOULD be routed locally (subscription
> via
>       direct routing mode).  If the (M) flag value is set to a value
> of
>       (0), it is an indication that IP multicast traffic associated to
>       the multicast group(s) identified by the Multicast Address
> Record
>       in this mobility option(s) SHOULD be routed to the home network,
>       via the MTMA (subscription via MTMA mode).  All other IP traffic
>       associated with the mobile node SHOULD be managed according to a
>       default policy configured at the PMIPv6 multicast domain.
> 
> The last sentence: I don't think you should use RFC 2119 SHOULD here.
> I think you are saying that this document doesn't affect all other IP
> traffic. So just use "is managed" instead of "SHOULD be managed".
> 
OK, updated in version -08 (to be submitted once we get all the
comments).

> 
> Is IANA Considerations section clear to IANA? I suggest you add at
> least the URI for the IANA registry.
> Is IANA registration policy compatible with the type of document
> (Experimental)? I can't check that, as I don't know which registry you
> are talking about.
> 
The IANA has not complained about it, but we will update the text in -08
so it reads like this:

9.  IANA Considerations

   This document defines a new mobility option, the Dynamic IP Multicast
   Selector, which has been assigned the Type TBD by IANA.  The Type
   value for these options has been assigned from the same numbering
   space as allocated for the other mobility options, as defined in
   [RFC6275]: http://www.iana.org/assignments/mobility-parameters/
   mobility-parameters.xhtml.
> 
>  
> 
> Nits/editorial comments:
> 
> 
> 
> In 3.3: acronyms PBU and PBA need to be expanded on first use. They
> are expanded further down in the document.

Fixed in -08, thanks.

Thanks again for the review,

Carlos
> 
> 



From ben@nostrum.com  Tue Jul 16 15:27:33 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3148921F91B7; Tue, 16 Jul 2013 15:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E7XvFlbvVhe5; Tue, 16 Jul 2013 15:27:32 -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 7566921F9011; Tue, 16 Jul 2013 15:27:32 -0700 (PDT)
Received: from [10.0.1.12] (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 r6GMRV0X020855 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Jul 2013 17:27:31 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 16 Jul 2013 17:27:31 -0500
Message-Id: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com>
To: draft-ietf-jcardcal-jcard.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC/Telechat Review of draft-ietf-jcardcal-jcard-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 22:27:33 -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-jcardcal-jcard-04
Reviewer:  Ben Campbell
Review Date:  2013-07-16
IETF LC End Date: 2013-07-18
IESG Telechat date: 2013-07-18

Note: This draft is on the IESG Telechat agenda on the same date as it =
completes IETF Last Call. Therefore, this review serves both purposes.

Summary: This draft is almost ready for publication as a proposed =
standard. There are a few minor issues and editorial nits that should be =
considered prior to publication.

Major issues:

-- None

Minor issues:

-- Section 1, design considerations:

You mention that the semantic results should survive round-tripping, but =
the order of fields might not. I gather there are other changes that =
might occur from the literal text, right? (e.g. Case changes, some =
optional parameter usage). If so, it might be worth clarifying that.

-- 3.1, 2nd paragraph:

I assume the removal of escaping means that one renders the escaped =
text, not simply removes it, right? Is that as simple as removing the =
escape characters in vCards? I assume this doesn't apply to any =
content-specific escaping inside vCard fields, e.g. URI escaping, right? =
If so, it might be worth mentioning.

-- 3.2.1.1:

What happens for future versions of vCard? Do you simply use the new =
version number, or would we need a new version of this spec? I suspect =
the latter. If true, it might be worth mentioning that, or somewhere =
early in the draft mention that this spec is for vCard 4.0 only.

-- sections 3.4.3 and 3.4.4:

Is the included ABNF a quotation of that in the referenced RFCs, or is =
it new and authoritative? If the former, it would be helpful to mention =
that in the text. (I note you did say that about the ABNF in the =
appendix).

-- 3.4.11:

If RFC6350 says that use of the timezone offset is NOT RECOMMENDED, can =
you elaborate on why it's included here? (I can guess it's because =
people may still use it in vCards since it was a "MUST NOT", but it =
would be good to say something to that effect in the text.)

Nits/editorial comments:

-- Section 1, paragraph 1:

Please expand JSON on first mention.

-- Section 1, paragraph 3:

This paragraph seems redundant to paragraph 1.

-- 1, paragraph 7: " Preserve the semantics of the vCard data."

Imperative form sentence is confusing in context, and inconsistent with =
surrounding text.

-- 1, paragraph 8:

Sentence Fragment.

-- 3.2, Last Paragraph: "... for a parser check the data type..."

Missing "to"?

-- 3.2.1.2, last paragraph before example:

Should the "iCalendar" reference be "vCard" instead?

-- 3.2.1.3, Last Paragraph:

RFCTODO? I gather in the IANA section, that may be a placeholder for =
"this RFC", but that doesn't seem to fit here.

-- 3.3.2: "Example 1:"

Other examples are not numbered.

-- 5:

More occurrences of RFCTODO









From ben@nostrum.com  Tue Jul 16 15:51:47 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C451B21F9AA3; Tue, 16 Jul 2013 15:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ioqTdRRbvSqz; Tue, 16 Jul 2013 15:51:47 -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 B8DBB21F9A98; Tue, 16 Jul 2013 15:51:46 -0700 (PDT)
Received: from [10.0.1.12] (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 r6GMpjYJ023427 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Jul 2013 17:51:46 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 16 Jul 2013 17:51:45 -0500
Message-Id: <15C587F4-4A93-4EAC-A241-D0E5E8FF5F3B@nostrum.com>
To: draft-yusef-dispatch-ccmp-indication.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-yusef-dispatch-ccmp-indication-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 22:51: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-yusef-dispatch-ccmp-indication-04
Reviewer: Ben Campbell=09
Review Date: 2013-07-16
IETF LC End Date: 2013-07-16

Summary: This draft is almost ready for publication as a proposed =
standard, but I think there are some clarifications needed first.

Major issues:

-- None

Minor issues:

-- Abstract:

Is the abstract current? It says you will discuss pros and cons of a few =
options, and recommend two. I guess you did recommend two, but the =
others have been relegated to the appendix. There are no pros and cons =
listed for the two recommended choices, which seems rather odd.=20

It also mentions that these are mechanisms to be used by SIP clients. =
That's not repeated in the introduction. Is this entire draft intended =
exclusively for SIP clients?

-- 2.

It would be helpful to give more guidance on when one would use one =
method over the other. 2.1 mentions that it might be an "easier way for =
a UA that is not interested in the URI". I'm not sure what it means for =
a UA to be interested or not interested in a URI--maybe you mean "A UA =
that does not otherwise need to parse the URI"?

-- 2.1:=20

I assume this section is intended to be SIP specific. It would help to =
say that somewhere, and include a 3261 citation for Call-Info. There are =
hints that the entire draft is SIP specific in the abstract, but that =
doesn't get repeated elsewhere. (In fact, the only non-abstract citation =
to 3261 is in the IANA considerations.)

Also, the section seems underspecified. It says the ccmp value can go in =
any INVITE, INVITE response, or OPTIONS response. It would help to =
describe how UAs would actually use it. Simply naming the actors would =
help; as it is, they are obscured by the passive voice in "... can be =
used...", and the reader is left to infer the intent based on his =
knowledge of SIP.

--2.2:

I assume this section is _not_ necessarily SIP specific. If that's the =
intent, it would be helpful to say so.

-- Appendices:

There's more detail and discussion around the discarded methods than the =
recommended ones in sections 2.X. It would be helpful to have those =
sections have at least this much explanation.

-- section 3:

You say this draft introduces no additional security considerations. =
Statements like that turn out false more often than not. For example, is =
there no security consideration created by having a SIP UA identify =
itself as a conference focus in an INVITE? (Even if the answer is no, =
it's helpful to have text along the line of "we thought about this and =
decided it was not a consideration due <reasons>"

Further, you say "... beyond those applicable to the mechanisms =
described within". The mechanisms in sections 2.X are "described =
within". I assume those aren't the ones you mean here.


Nits/editorial comments:

-- Abstract:

The abstract should not contain citations. It will be published in =
multiple places without the rest of the document, orphaning the =
citations.=

From jari.arkko@piuha.net  Tue Jul 16 22:01:43 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2F021F9A99 for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 22:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P6cnaokz+7su for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 22:01:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 1634221F9A2E for <gen-art@ietf.org>; Tue, 16 Jul 2013 22:01:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9C76B2CC5D; Wed, 17 Jul 2013 08:01:31 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id foz2k0LKGpgB; Wed, 17 Jul 2013 08:01:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D1A942CC3C; Wed, 17 Jul 2013 08:01:29 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com>
Date: Wed, 17 Jul 2013 07:01:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6766AC36-3860-4CBF-9FE3-22551D69D519@piuha.net>
References: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1508)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, draft-ietf-jcardcal-jcard.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC/Telechat Review of draft-ietf-jcardcal-jcard-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2013 05:01:43 -0000

Many thanks for your review, Ben! These reviews are very helpful for me =
to form an opinion about the draft in the IESG telechat. Authors, do you =
have thoughts on the issues that Ben raises here?

Jari

On Jul 17, 2013, at 12:27 AM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document:  draft-ietf-jcardcal-jcard-04
> Reviewer:  Ben Campbell
> Review Date:  2013-07-16
> IETF LC End Date: 2013-07-18
> IESG Telechat date: 2013-07-18
>=20
> Note: This draft is on the IESG Telechat agenda on the same date as it =
completes IETF Last Call. Therefore, this review serves both purposes.
>=20
> Summary: This draft is almost ready for publication as a proposed =
standard. There are a few minor issues and editorial nits that should be =
considered prior to publication.
>=20
> Major issues:
>=20
> -- None
>=20
> Minor issues:
>=20
> -- Section 1, design considerations:
>=20
> You mention that the semantic results should survive round-tripping, =
but the order of fields might not. I gather there are other changes that =
might occur from the literal text, right? (e.g. Case changes, some =
optional parameter usage). If so, it might be worth clarifying that.
>=20
> -- 3.1, 2nd paragraph:
>=20
> I assume the removal of escaping means that one renders the escaped =
text, not simply removes it, right? Is that as simple as removing the =
escape characters in vCards? I assume this doesn't apply to any =
content-specific escaping inside vCard fields, e.g. URI escaping, right? =
If so, it might be worth mentioning.
>=20
> -- 3.2.1.1:
>=20
> What happens for future versions of vCard? Do you simply use the new =
version number, or would we need a new version of this spec? I suspect =
the latter. If true, it might be worth mentioning that, or somewhere =
early in the draft mention that this spec is for vCard 4.0 only.
>=20
> -- sections 3.4.3 and 3.4.4:
>=20
> Is the included ABNF a quotation of that in the referenced RFCs, or is =
it new and authoritative? If the former, it would be helpful to mention =
that in the text. (I note you did say that about the ABNF in the =
appendix).
>=20
> -- 3.4.11:
>=20
> If RFC6350 says that use of the timezone offset is NOT RECOMMENDED, =
can you elaborate on why it's included here? (I can guess it's because =
people may still use it in vCards since it was a "MUST NOT", but it =
would be good to say something to that effect in the text.)
>=20
> Nits/editorial comments:
>=20
> -- Section 1, paragraph 1:
>=20
> Please expand JSON on first mention.
>=20
> -- Section 1, paragraph 3:
>=20
> This paragraph seems redundant to paragraph 1.
>=20
> -- 1, paragraph 7: " Preserve the semantics of the vCard data."
>=20
> Imperative form sentence is confusing in context, and inconsistent =
with surrounding text.
>=20
> -- 1, paragraph 8:
>=20
> Sentence Fragment.
>=20
> -- 3.2, Last Paragraph: "... for a parser check the data type..."
>=20
> Missing "to"?
>=20
> -- 3.2.1.2, last paragraph before example:
>=20
> Should the "iCalendar" reference be "vCard" instead?
>=20
> -- 3.2.1.3, Last Paragraph:
>=20
> RFCTODO? I gather in the IANA section, that may be a placeholder for =
"this RFC", but that doesn't seem to fit here.
>=20
> -- 3.3.2: "Example 1:"
>=20
> Other examples are not numbered.
>=20
> -- 5:
>=20
> More occurrences of RFCTODO
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From elwynd@dial.pipex.com  Wed Jul 17 07:42:29 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 177A221F9DFB for <gen-art@ietfa.amsl.com>; Wed, 17 Jul 2013 07:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.599
X-Spam-Level: 
X-Spam-Status: No, score=-100.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HcVkClxrfczy for <gen-art@ietfa.amsl.com>; Wed, 17 Jul 2013 07:42:28 -0700 (PDT)
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 0421E21F9E47 for <gen-art@ietf.org>; Wed, 17 Jul 2013 07:42:27 -0700 (PDT)
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 1UzSvm-0005s8-VE; Wed, 17 Jul 2013 15:42:20 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <130E5C09-1C4D-4EF1-AE09-95E3F9D29F63@cisco.com>
References: <1373115697.4524.42154.camel@mightyatom> <7B3ED28F-E27B-4B16-B73E-8070B830D437@piuha.net> <130E5C09-1C4D-4EF1-AE09-95E3F9D29F63@cisco.com>
Content-Type: text/plain
Date: Wed, 17 Jul 2013 15:41:38 +0100
Message-Id: <1374072098.4524.48650.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: draft-ietf-dhc-dhcpv6-failover-requirements.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art LC review: draft-ietf-dhc-dhcpv6-failover-requirements-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2013 14:42:29 -0000

Hi, Kim.

Thanks for the reponses.

Looks like we are pretty well agreed. Just these two points: 

On s7, item 6: Just a thought so I'll consider it irrelevant.

On the last para of 7, I clearly failed to notice the date on the draft
for DHCPv4 failover protocol! [The hazards of an infinite archive for
I-Ds!]  So I understand why this probably isn't  going to go all the way
to an inter-operable protocol for either v4 or v6.  Perhaps it might be
worth adding in a few words to explain this (and improve an editorial
nit I missed):
OLD:
   Despite the lack of standardization of DHCPv4 failover, the
   coexistence of DHCPv4 and DHCPv6 failover may be taken into
   consideration.  In particular, certain features that are common for
   both IPv4 and IPv6, like DNS Update mechanism should be taken into
   consideration. 
NEW:
   Although progress on a standardized inter-operable DHCPv4 failover
   protocol has stalled, vendor-specific DHCPv4 failover protocols 
   have been deployed that meet these requirements to a large extent.
   Accordingly it would be appropriate to take into account the likely 
   coexistence of DHCPv4 and DHCPv6 failover solutions.  In particular, 
   certain features that are common to both IPv4 and IPv6 
   implementations, such as any DNS Update mechanism, should be taken into
   consideration to ensure compatible operation.

Regards,
Elwyn

On Tue, 2013-07-16 at 10:38 -0400, Kim Kinnear wrote:
> Jari, Elwyn,
> 
> Elwyn -- thank you for the thoughtful review.  My comments
> are indented below...
> 
> On Jul 16, 2013, at 3:36 AM, Jari Arkko wrote:
> 
> > Thank you for your review, Elwyn. Do the authors have any thoughts on the issues that Elwyn raises here?
> > 
> > Jari
> > 
> > On Jul 6, 2013, at 3:01 PM, Elwyn Davies <elwynd@dial.pipex.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-dhc-dhcpv6-failover-requirements-06.txt
> >> Reviewer: Elwyn Davies
> >> Review Date: 6 July 2013
> >> IETF LC End Date: 17 July 2013
> >> IESG Telechat date: (if known) -
> >> 
> >> Summary: Almost ready.  There are a few very minor issues and a fair
> >> number of editorial nits to fix but generally in good shape.
> >> 
> >> Major issues:
> >> None
> >> 
> >> Minor issues:
> >> s1, Introduction of Primary/Secondary terminology: The introduction
> >> talks about multiple servers (i.e., potentially > 2) but then in the
> >> last sentence of para 1 introduces primary and secondary servers.  The
> >> initial impression this gives is that the number of servers has now been
> >> reduced to <= 2.  Having read through the rest of the document I can see
> >> how I am supposed to interpret the last sentence of para 1, but things
> >> would be much clearer if an extra sentence or three describing the
> >> chosen model (and its intended extension) was added just before this
> >> last sentence.  Maybe something like:
> >>  The failover model, to which these requirements apply, will initially
> >>  be a pairwise "hot standby" model (see Section 4.1) with a primary 
> >>  server used in normal operation switching over to a backup secondary 
> >>  server in the event of failure.  Optionally, a secondary server may 
> >>  provide failover service for multiple primary servers.  However the 
> >>  requirements will not preclude a future load-balancing extension 
> >>  where there is a symmetric failover relationship. 
> 
> 	Yes, this is a fine idea.  Thanks for the sentence.
> >> 
> >> s7: Related to the previous comment, perhaps it should be made explicit
> >> that the resulting protocol is "load-balancing friendly" to avoid rework
> >> if at all possible.  Since both v4 and v6 load-balancing and v4 failover
> >> with load-balancing are in progress, it should be known how to avoid
> >> pitfalls by the time the v6 failover protocol is designed!
> 
> 	Sure, we'll put something in to deal with that.
> >> 
> >> s7, item 4, last sentence: 
> >> "Long-lived connections must not be disturbed."
> >> I don't believe the DHCPv6 server or the failover protocol can either
> >> know that an address is in use for long lived connections or guarantee
> >> that they won't be disturbed beyond what is said earlier in this item.
> >> Presumably what is meant is something like: "Lease stability has the aim
> >> of avoiding disturbance to long-lived connections."
> 
> 	Yes, we'll reword this as you suggest.
> >> 
> >> s7, item 6:  Maybe irrelevant thought: Presumably you could build a
> >> failover system using a shared, reliable database and a minimalistic
> >> version of the failover protocol instead of using lazy updates.  Should
> >> this be explicitly an option?
> 
> 	Well, this thought is explored in Section 3.1.3, but under
> 	the overall heading of "Alternatives to Failover".  Is this
> 	an alternative *to* failover, or an option *for* failover 
> 	(as you suggest might be appropriate)?  Hard to say. 
>  
> 	I suppose that our design draft, already about to go to
> 	last call, influenced our thinking to some degree when we
> 	wrote this.  I don't think the document would be substantively
> 	better were we to change it so that a distributed database
> 	solution is an option as opposed to an alternative.  So,
> 	to be clear, I don't think changing this is a good idea.
> 
> >> 
> >> s7, last para: "Despite the lack of standardization of DHCPv4
> >> failover...": It appears that work is in progress on this
> >> (http://tools.ietf.org/html/draft-ietf-dhc-failover-12)... so what is
> >> meant here?
> 
> 	The work in progress ended years ago.  Many years ago.
> 	The document which you reference is ~132 pages long, and
> 	has requirements, design, and protocol all in one
> 	document.  It was essentially too big and complicated to
> 	be digested by the IETF.  We could not even get the AD at
> 	the time to review the entire document.  In part this was
> 	because the problem was important to solve in an
> 	intra-vendor way, but inter-vendor capable failover was
> 	not important in the real world (i.e., nobody really
> 	cared to pay extra for failover that worked across two
> 	vendors servers).
> 
> 	The experience gained during the v4 failover effort is
> 	the reason the v6 failover effort (of which the document
> 	under discussion is a part) has been split into three
> 	separate pieces: requirements, design, and (if sufficient
> 	interest exists), protocol.  The hope is that these
> 	pieces will be individually digestible where the v4
> 	effort was not.
> 
> 	That said, the v6 failover design draft is already 50
> 	pages, and it hasn't yet undergone WG last call, though
> 	it is very close to that point.  
> 
> 	Plus, it is possible that we will end with the design
> 	document, since that will have the basics of how you
> 	build a v6 failover capability.  The protocol document is
> 	only really interesting if you want to have an
> 	inter-vendor failover capability.  We don't yet know how
> 	that will play out, though we certainly expect to give
> 	it a try.
> >> 
> >> Nits/editorial comments:
> 
> 	Thank you for catching these.  We will make all of these
> 	changes.
> 
> 	Thanks again for your review!
> 
> 	Regards -- Kim
> 
> >> 
> >> Global: s/i.e./i.e.,/
> >> Global: s/e.g./e.g.,/
> >> 
> >> Abstract: s/any way/any way that/
> >> 
> >> s2: Expoand acronyms CPR, IA - even though IA is defined in RFC 3315, it
> >> would help readability to repeat the expansion.
> >> 
> >> s2, lease: Should this mention something about length of time for which
> >> the lease will be valid?
> >> 
> >> s3.1.1: Expand PXE acronym.
> >> 
> >> s3.1.1, para 1:
> >> OLD
> >>  Address and possibly other
> >>  configuration parameters are used during boot process and are
> >>  discarded afterwards. 
> >> NEW:
> >>  The address and possibly other
> >>  configuration parameters are used during the boot process and are
> >>  discarded thereafter. 
> >> 
> >> s3.1.1, para 2: s/distinct preference set/a distinct preference set/
> >> 
> >> s3.1.2, para 2:
> >> OLD:
> >>  There are several well documented approaches how such deployment
> >>  works. 
> >> NEW:
> >>  There are several well-documented approaches showing how such a deployment
> >>  could work.
> >> 
> >> s3.1.3, para 2:
> >> OLD:
> >>  It is also essential to use only databases that are really
> >>  distributed and do not have single point of failure themselves.
> >> NEW:
> >>  It is also essential to use only a database system that provides 
> >>  equivalent reliability and failover capability. 
> >> 
> >> s4: This paragraph implies that the document defines a protocol contrary
> >> to its expressed intention and reality.
> >> OLD:
> >>  These scenarios may be inside or
> >>  outside of scope for DHCPv6 failover protocol as defined by this
> >>  document.  They are enumerated here to provide a common basis for
> >>  discussion.
> >> NEW:
> >>  These scenarios may be in or
> >>  out of scope for the DHCPv6 failover model to which this 
> >>  document's requirements apply; they are enumerated here to provide a 
> >>  common basis for discussion.   
> >> 
> >> s5, para 2: s/General failover concept/The general failover concept/, 
> >> s/in case of the primary server/in case of a primary server/,
> >> s/In case of just/In the case of just/,
> >> s/Had there be more than two partners/Were there more than two partners/
> >> (subjunctive!)
> >> 
> >> s5, para 2:
> >> OLD:
> >>  there would be a third states in between (some
> >>  partners updated their state, but some didn't).
> >> NEW:
> >>  there would be intermediate, inconsistent states where some partners
> >>  had updated their state and some had not.
> >> 
> >> s4.1: s/Only one of partners/Only one of the partners/
> >> 
> >> s4.6, para 2: s/every time IPv6 address changes/every time an IPv6
> >> address changes/
> >> 
> >> s4.6, para 3: s/having stable address/having a stable address/
> >> 
> >> s5.1, last sentence:  This seems to imply that *this section* states
> >> whether the failure mode is in or out of scope for the protocol.  It
> >> doesn't - that is postponed to s7.  Either remove this sentence or
> >> redraft to refer to s7.
> >> 
> >> s5.1.2, para 2: s/is that partner also detected/is that the partner also
> >> detected/
> >> 
> >> s5.2: s/synchronization methods/synchronization method/,
> >> s/familiarity with distributed database/familiarity with distributed database technology/
> >> 
> >> s5.2.1, para 1: s/response from partner/response from its partner/
> >> 
> >> s5.2.1, para 2: 'large' is an over-generalization. Maybe:
> >> s/a large performance penalty/typically a significant performance penalty/
> >> 
> >> s5.2.1, para 3:
> >> OLD:
> >> Due to advent of SSD disks or battery backed ram disks technology,
> >> NEW:
> >> Due to the advent of fast SSD (solid state disk) and battery-backed RAM 
> >> (random access memory) disk technology,
> >> 
> >> s5.2.2, para 2: s/if server crashes/if the server crashes/
> >> 
> >> s7, item 4: s/should pose/should have/
> >> 
> >> _______________________________________________
> >> Gen-art mailing list
> >> Gen-art@ietf.org
> >> https://www.ietf.org/mailman/listinfo/gen-art
> > 
> 


From kkinnear@cisco.com  Wed Jul 17 08:38:20 2013
Return-Path: <kkinnear@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 AC96821F90FB for <gen-art@ietfa.amsl.com>; Wed, 17 Jul 2013 08:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vOCOxs3KfHZO for <gen-art@ietfa.amsl.com>; Wed, 17 Jul 2013 08:38:16 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 03E7A21F8FD8 for <gen-art@ietf.org>; Wed, 17 Jul 2013 08:38:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12211; q=dns/txt; s=iport; t=1374075496; x=1375285096; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Mtk/TJ4q1DqJ9MYRZ6jFZHBNCga/dZNx1nrfHRVtvZk=; b=Aw1Gnr37bZd7McQzjEgWeTyUuPYy+sTBNpqECpvaD7LqQCpLiEgyh97a lt5eWHvaeZyKejJReSc8wObCu3pYS3fyl+j3+XhbIeb/Y4JAA826VcYc0 3jOeY4dPm4y13FB3Z7V6k7eX6KSt60l9BeJiRHrW1xxyIGKKOCvl0dwYB I=;
X-IronPort-AV: E=Sophos;i="4.89,685,1367971200"; d="scan'208";a="235984327"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-5.cisco.com with ESMTP; 17 Jul 2013 15:38:15 +0000
Received: from [10.131.32.109] ([10.131.32.109]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6HFcE10000994;  Wed, 17 Jul 2013 15:38:15 GMT
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <1374072098.4524.48650.camel@mightyatom>
Date: Wed, 17 Jul 2013 11:38:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC80BF12-992E-4245-8C38-4F425EFD820A@cisco.com>
References: <1373115697.4524.42154.camel@mightyatom> <7B3ED28F-E27B-4B16-B73E-8070B830D437@piuha.net> <130E5C09-1C4D-4EF1-AE09-95E3F9D29F63@cisco.com> <1374072098.4524.48650.camel@mightyatom>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1278)
Cc: draft-ietf-dhc-dhcpv6-failover-requirements.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [Gen-art] Gen-art LC review: draft-ietf-dhc-dhcpv6-failover-requirements-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2013 15:38:20 -0000

Elwyn,

I love the "NEW" paragraph below.  We'll be sure to
use that. =20

Thanks!

Kim

On Jul 17, 2013, at 10:41 AM, Elwyn Davies wrote:

> Hi, Kim.
>=20
> Thanks for the reponses.
>=20
> Looks like we are pretty well agreed. Just these two points:=20
>=20
> On s7, item 6: Just a thought so I'll consider it irrelevant.
>=20
> On the last para of 7, I clearly failed to notice the date on the =
draft
> for DHCPv4 failover protocol! [The hazards of an infinite archive for
> I-Ds!]  So I understand why this probably isn't  going to go all the =
way
> to an inter-operable protocol for either v4 or v6.  Perhaps it might =
be
> worth adding in a few words to explain this (and improve an editorial
> nit I missed):
> OLD:
>   Despite the lack of standardization of DHCPv4 failover, the
>   coexistence of DHCPv4 and DHCPv6 failover may be taken into
>   consideration.  In particular, certain features that are common for
>   both IPv4 and IPv6, like DNS Update mechanism should be taken into
>   consideration.=20
> NEW:
>   Although progress on a standardized inter-operable DHCPv4 failover
>   protocol has stalled, vendor-specific DHCPv4 failover protocols=20
>   have been deployed that meet these requirements to a large extent.
>   Accordingly it would be appropriate to take into account the likely=20=

>   coexistence of DHCPv4 and DHCPv6 failover solutions.  In particular,=20=

>   certain features that are common to both IPv4 and IPv6=20
>   implementations, such as any DNS Update mechanism, should be taken =
into
>   consideration to ensure compatible operation.
>=20
> Regards,
> Elwyn
>=20
> On Tue, 2013-07-16 at 10:38 -0400, Kim Kinnear wrote:
>> Jari, Elwyn,
>>=20
>> Elwyn -- thank you for the thoughtful review.  My comments
>> are indented below...
>>=20
>> On Jul 16, 2013, at 3:36 AM, Jari Arkko wrote:
>>=20
>>> Thank you for your review, Elwyn. Do the authors have any thoughts =
on the issues that Elwyn raises here?
>>>=20
>>> Jari
>>>=20
>>> On Jul 6, 2013, at 3:01 PM, Elwyn Davies <elwynd@dial.pipex.com> =
wrote:
>>>=20
>>>> I am the assigned Gen-ART reviewer for this draft. For background =
on
>>>> Gen-ART, please see the FAQ at
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>=20
>>>> Please resolve these comments along with any other Last Call =
comments
>>>> you may receive.
>>>>=20
>>>> Document: draft-ietf-dhc-dhcpv6-failover-requirements-06.txt
>>>> Reviewer: Elwyn Davies
>>>> Review Date: 6 July 2013
>>>> IETF LC End Date: 17 July 2013
>>>> IESG Telechat date: (if known) -
>>>>=20
>>>> Summary: Almost ready.  There are a few very minor issues and a =
fair
>>>> number of editorial nits to fix but generally in good shape.
>>>>=20
>>>> Major issues:
>>>> None
>>>>=20
>>>> Minor issues:
>>>> s1, Introduction of Primary/Secondary terminology: The introduction
>>>> talks about multiple servers (i.e., potentially > 2) but then in =
the
>>>> last sentence of para 1 introduces primary and secondary servers.  =
The
>>>> initial impression this gives is that the number of servers has now =
been
>>>> reduced to <=3D 2.  Having read through the rest of the document I =
can see
>>>> how I am supposed to interpret the last sentence of para 1, but =
things
>>>> would be much clearer if an extra sentence or three describing the
>>>> chosen model (and its intended extension) was added just before =
this
>>>> last sentence.  Maybe something like:
>>>> The failover model, to which these requirements apply, will =
initially
>>>> be a pairwise "hot standby" model (see Section 4.1) with a primary=20=

>>>> server used in normal operation switching over to a backup =
secondary=20
>>>> server in the event of failure.  Optionally, a secondary server may=20=

>>>> provide failover service for multiple primary servers.  However the=20=

>>>> requirements will not preclude a future load-balancing extension=20
>>>> where there is a symmetric failover relationship.=20
>>=20
>> 	Yes, this is a fine idea.  Thanks for the sentence.
>>>>=20
>>>> s7: Related to the previous comment, perhaps it should be made =
explicit
>>>> that the resulting protocol is "load-balancing friendly" to avoid =
rework
>>>> if at all possible.  Since both v4 and v6 load-balancing and v4 =
failover
>>>> with load-balancing are in progress, it should be known how to =
avoid
>>>> pitfalls by the time the v6 failover protocol is designed!
>>=20
>> 	Sure, we'll put something in to deal with that.
>>>>=20
>>>> s7, item 4, last sentence:=20
>>>> "Long-lived connections must not be disturbed."
>>>> I don't believe the DHCPv6 server or the failover protocol can =
either
>>>> know that an address is in use for long lived connections or =
guarantee
>>>> that they won't be disturbed beyond what is said earlier in this =
item.
>>>> Presumably what is meant is something like: "Lease stability has =
the aim
>>>> of avoiding disturbance to long-lived connections."
>>=20
>> 	Yes, we'll reword this as you suggest.
>>>>=20
>>>> s7, item 6:  Maybe irrelevant thought: Presumably you could build a
>>>> failover system using a shared, reliable database and a =
minimalistic
>>>> version of the failover protocol instead of using lazy updates.  =
Should
>>>> this be explicitly an option?
>>=20
>> 	Well, this thought is explored in Section 3.1.3, but under
>> 	the overall heading of "Alternatives to Failover".  Is this
>> 	an alternative *to* failover, or an option *for* failover=20
>> 	(as you suggest might be appropriate)?  Hard to say.=20
>>=20
>> 	I suppose that our design draft, already about to go to
>> 	last call, influenced our thinking to some degree when we
>> 	wrote this.  I don't think the document would be substantively
>> 	better were we to change it so that a distributed database
>> 	solution is an option as opposed to an alternative.  So,
>> 	to be clear, I don't think changing this is a good idea.
>>=20
>>>>=20
>>>> s7, last para: "Despite the lack of standardization of DHCPv4
>>>> failover...": It appears that work is in progress on this
>>>> (http://tools.ietf.org/html/draft-ietf-dhc-failover-12)... so what =
is
>>>> meant here?
>>=20
>> 	The work in progress ended years ago.  Many years ago.
>> 	The document which you reference is ~132 pages long, and
>> 	has requirements, design, and protocol all in one
>> 	document.  It was essentially too big and complicated to
>> 	be digested by the IETF.  We could not even get the AD at
>> 	the time to review the entire document.  In part this was
>> 	because the problem was important to solve in an
>> 	intra-vendor way, but inter-vendor capable failover was
>> 	not important in the real world (i.e., nobody really
>> 	cared to pay extra for failover that worked across two
>> 	vendors servers).
>>=20
>> 	The experience gained during the v4 failover effort is
>> 	the reason the v6 failover effort (of which the document
>> 	under discussion is a part) has been split into three
>> 	separate pieces: requirements, design, and (if sufficient
>> 	interest exists), protocol.  The hope is that these
>> 	pieces will be individually digestible where the v4
>> 	effort was not.
>>=20
>> 	That said, the v6 failover design draft is already 50
>> 	pages, and it hasn't yet undergone WG last call, though
>> 	it is very close to that point. =20
>>=20
>> 	Plus, it is possible that we will end with the design
>> 	document, since that will have the basics of how you
>> 	build a v6 failover capability.  The protocol document is
>> 	only really interesting if you want to have an
>> 	inter-vendor failover capability.  We don't yet know how
>> 	that will play out, though we certainly expect to give
>> 	it a try.
>>>>=20
>>>> Nits/editorial comments:
>>=20
>> 	Thank you for catching these.  We will make all of these
>> 	changes.
>>=20
>> 	Thanks again for your review!
>>=20
>> 	Regards -- Kim
>>=20
>>>>=20
>>>> Global: s/i.e./i.e.,/
>>>> Global: s/e.g./e.g.,/
>>>>=20
>>>> Abstract: s/any way/any way that/
>>>>=20
>>>> s2: Expoand acronyms CPR, IA - even though IA is defined in RFC =
3315, it
>>>> would help readability to repeat the expansion.
>>>>=20
>>>> s2, lease: Should this mention something about length of time for =
which
>>>> the lease will be valid?
>>>>=20
>>>> s3.1.1: Expand PXE acronym.
>>>>=20
>>>> s3.1.1, para 1:
>>>> OLD
>>>> Address and possibly other
>>>> configuration parameters are used during boot process and are
>>>> discarded afterwards.=20
>>>> NEW:
>>>> The address and possibly other
>>>> configuration parameters are used during the boot process and are
>>>> discarded thereafter.=20
>>>>=20
>>>> s3.1.1, para 2: s/distinct preference set/a distinct preference =
set/
>>>>=20
>>>> s3.1.2, para 2:
>>>> OLD:
>>>> There are several well documented approaches how such deployment
>>>> works.=20
>>>> NEW:
>>>> There are several well-documented approaches showing how such a =
deployment
>>>> could work.
>>>>=20
>>>> s3.1.3, para 2:
>>>> OLD:
>>>> It is also essential to use only databases that are really
>>>> distributed and do not have single point of failure themselves.
>>>> NEW:
>>>> It is also essential to use only a database system that provides=20
>>>> equivalent reliability and failover capability.=20
>>>>=20
>>>> s4: This paragraph implies that the document defines a protocol =
contrary
>>>> to its expressed intention and reality.
>>>> OLD:
>>>> These scenarios may be inside or
>>>> outside of scope for DHCPv6 failover protocol as defined by this
>>>> document.  They are enumerated here to provide a common basis for
>>>> discussion.
>>>> NEW:
>>>> These scenarios may be in or
>>>> out of scope for the DHCPv6 failover model to which this=20
>>>> document's requirements apply; they are enumerated here to provide =
a=20
>>>> common basis for discussion.  =20
>>>>=20
>>>> s5, para 2: s/General failover concept/The general failover =
concept/,=20
>>>> s/in case of the primary server/in case of a primary server/,
>>>> s/In case of just/In the case of just/,
>>>> s/Had there be more than two partners/Were there more than two =
partners/
>>>> (subjunctive!)
>>>>=20
>>>> s5, para 2:
>>>> OLD:
>>>> there would be a third states in between (some
>>>> partners updated their state, but some didn't).
>>>> NEW:
>>>> there would be intermediate, inconsistent states where some =
partners
>>>> had updated their state and some had not.
>>>>=20
>>>> s4.1: s/Only one of partners/Only one of the partners/
>>>>=20
>>>> s4.6, para 2: s/every time IPv6 address changes/every time an IPv6
>>>> address changes/
>>>>=20
>>>> s4.6, para 3: s/having stable address/having a stable address/
>>>>=20
>>>> s5.1, last sentence:  This seems to imply that *this section* =
states
>>>> whether the failure mode is in or out of scope for the protocol.  =
It
>>>> doesn't - that is postponed to s7.  Either remove this sentence or
>>>> redraft to refer to s7.
>>>>=20
>>>> s5.1.2, para 2: s/is that partner also detected/is that the partner =
also
>>>> detected/
>>>>=20
>>>> s5.2: s/synchronization methods/synchronization method/,
>>>> s/familiarity with distributed database/familiarity with =
distributed database technology/
>>>>=20
>>>> s5.2.1, para 1: s/response from partner/response from its partner/
>>>>=20
>>>> s5.2.1, para 2: 'large' is an over-generalization. Maybe:
>>>> s/a large performance penalty/typically a significant performance =
penalty/
>>>>=20
>>>> s5.2.1, para 3:
>>>> OLD:
>>>> Due to advent of SSD disks or battery backed ram disks technology,
>>>> NEW:
>>>> Due to the advent of fast SSD (solid state disk) and battery-backed =
RAM=20
>>>> (random access memory) disk technology,
>>>>=20
>>>> s5.2.2, para 2: s/if server crashes/if the server crashes/
>>>>=20
>>>> s7, item 4: s/should pose/should have/
>>>>=20
>>>> _______________________________________________
>>>> Gen-art mailing list
>>>> Gen-art@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/gen-art
>>>=20
>>=20
>=20


From lojakab@cisco.com  Wed Jul 17 10:53:57 2013
Return-Path: <lojakab@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 A9A3F21F9F3A for <gen-art@ietfa.amsl.com>; Wed, 17 Jul 2013 10:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.199
X-Spam-Level: 
X-Spam-Status: No, score=-10.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pXjj4bAbcSZt for <gen-art@ietfa.amsl.com>; Wed, 17 Jul 2013 10:53:52 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 25ADC21F9F1F for <gen-art@ietf.org>; Wed, 17 Jul 2013 10:53:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5800; q=dns/txt; s=iport; t=1374083629; x=1375293229; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=WzPVevQulRoSQi+6JCKyawHPTMpYNWYhNvne9E5qfRY=; b=ienqEwTFmbFdEWcsq2QRWTyFarXga91fVqO+Swdk3SUy3ULcwzkD6Gi4 DyaALELPyebvEhX0AHPoPWE0ZL7zdxNLNDCfD5X0ve43B0zg3nKvThgu4 e2I3HgUAs/WVwlmzymfurmDZmfOTYpbrIG2mqjNzRo0FNSQtkqVpHRy+X k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAATZ5lGtJXG8/2dsb2JhbABagwY0UIMGv1CBERZ0giMBAQEEIxU6AgQBEAsUBAICBRYLAgIJAwIBAgFFBg0BBwEBF4d1DKQNkU+BKI0agTgHglqBIQOJIYpkg1eBKYR6iyqDFYFlQA
X-IronPort-AV: E=Sophos;i="4.89,686,1367971200"; d="scan'208";a="235848512"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 17 Jul 2013 17:53:43 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r6HHrhM9018538 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Jul 2013 17:53:43 GMT
Received: from [10.21.77.94] (10.21.77.94) by xhc-rcd-x14.cisco.com (173.37.183.88) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 17 Jul 2013 12:53:41 -0500
Message-ID: <51E6DA1E.9070207@cisco.com>
Date: Wed, 17 Jul 2013 20:53:34 +0300
From: Lori Jakab <lojakab@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <51DCE0A1.90807@gmail.com> <51DEA9A5.2040405@cisco.com> <51DF12C1.2080506@gmail.com>
In-Reply-To: <51DF12C1.2080506@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.21.77.94]
Cc: draft-ietf-lisp-deployment.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-lisp-deployment-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, 17 Jul 2013 17:53:57 -0000

Hi Brian,

Should we post a new revision of the draft now, with the below changes, 
or should we wait for the security review first?

-Lori

On 7/11/13 11:17 PM, Brian E Carpenter wrote:
> Hi Lori, see in line.
>
> On 12/07/2013 00:48, Lori Jakab wrote:
>> Hi Brian,
>>
>> Thank you for reviewing.  Please find replies to you comments inline.
>>
>> On 7/10/13 7:18 AM, Brian E Carpenter 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-lisp-deployment-09.txt
>>> Reviewer: Brian Carpenter
>>> Review Date: 2013-07-10
>>> IETF LC End Date: 2013-07-15
>>> IESG Telechat date:
>>>
>>> Summary:  Almost ready
>>> --------
>>>
>>> Comments:
>>> ---------
>>>
>>> I was assigned to review -08, but -09 came out during Last Call.
>>>
>>> Issues:
>>> -------
>>>
>>> The draft states in its Introduction that it "is expected to evolve as
>>> LISP
>>> deployment progresses, and the described scenarios are better
>>> understood or
>>> new scenarios are discovered." The desire to freeze a version of the
>>> draft
>>> as an RFC is understandable, but shouldn't the title and Abstract clearly
>>> indicate that it's a snapshot (and genuinely a request for comments)?
>> I'm not sure a change in the title is warranted (please suggest a new
>> title if you think it is), but I agree the Abstract should be reworded.
>> How about this new text replacing the old one:
>>
>>     This document is a snapshot of different Locator/Identifier
>>     Separation Protocol (LISP) deployment scenarios.  It discusses the
>>     placement of new network elements introduced by the protocol,
>>     representing the thinking of the authors as of Summer 2013.  LISP
>>     deployment scenarios may have evolved since. This memo represents
>>     one stable point in that evolution of understanding.
> That's good. I don't feel strongly about the title.
>
>>
>>> In general the draft is clear and well written. If you believe that there
>>> are sufficient incentives for Tier 3 providers and large sites to deploy
>>> an experimental protocol such as LISP, the discussion is useful. However,
>>> I am disappointed by the limited discussion of scalability. In
>>> particular,
>>> the incentives to deploy P-ITRs and to announce routes to them will
>>> become
>>> a critical issue at the half-way stage between early transition (LISP
>>> is a
>>> minority solution) and late transition (LISP is the majority solution).
>>> According to RFC 6832, P-ITRs scale either because "aggregate routes
>>> might
>>> be selectively announced" or because "the same address might be announced
>>> by multiple Proxy-ITRs in order to share the traffic." I really expected
>>> the deployment draft to discuss this issue in more detail. As I believe
>>> has been said before, these issues are very similar to the issues facing
>>> the operators of a 6to4 forward or return relay. We have experimental
>>> evidence there that altruism doesn't work and the incentives to "donate"
>>> connectivity are insufficient. The analogy isn't perfect, but the
>>> underlying
>>> question is similar - what is the incentive for a particular operator to
>>> offer P-ITR service for a particular bunch of EID prefixes, when the
>>> clientele might be up to half the Internet, depending on who chooses to
>>> propagate the routes?
>> I was hoping we addressed these concerns in Section 5.3, Proxy-ITR Route
>> Distribution (PITR-RD).  I agree that altruism doesn't work, that's why
>> the PITR-RD scenario is based on business relationships between
>> different providers.  When someone registers a domain name, he/she pays
>> an annual fee that should cover the operating expenses for publishing
>> the domain in the global DNS.  The situation is similar with several
>> other registration services.  When someone contacts a mapping service
>> provider (MSR), to get their prefix registered in the LISP mapping
>> system, they get the option of signing up for PITR services as well, for
>> an extra fee.  These services may be offered by the MSP themselves, but
>> it is expected that specialized P-ITR service providers (PSPs) will do
>> it.  If they don't sign up, they become responsible for getting non-LISP
>> traffic to their EIDs (using the LISP+BGP scenario).
>>
>> Additionally, Tier 1 ISPs may offer P-ITR services to non-subscribers in
>> strategic places just to attract more traffic from competitors, thus
>> more revenue.
>>
>> Should we add anything to this section to resolve the comment?
> The explanation you have just written is quite informative. We're a bit
> shy in the IETF about discussing incentives, but I think your explanation
> would fit nicely into the draft. (I'm embarassed that we didn't
> get this right for 6to4.)
>
>>> The Security Considerations are minimal. I wonder if
>>> draft-ietf-lisp-threats
>>> identifies threats for each scenario described in
>>> draft-ietf-lisp-deployment?
>>> If not, the statement "Security implications of LISP deployments are
>>> to be
>>> discussed in separate documents." is rather optimistic.
>>>
>> draft-ietf-lisp-threats discusses general LISP deployment security
>> issues, without analyzing all scenarios described in
>> draft-ietf-lisp-deployment.  I'm not sure such an iterative approach is
>> necessary, unless scenario specific threats are discovered.
>
> I expect you will be getting a Security Area review, so maybe
> you'd better go by that.
>
>      Brian
>
>> Best regards,
>> -Lori
>>


From brian@innovationslab.net  Wed Jul 17 11:15:46 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9206321F9C82 for <gen-art@ietfa.amsl.com>; Wed, 17 Jul 2013 11:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I+VVZebEJTup for <gen-art@ietfa.amsl.com>; Wed, 17 Jul 2013 11:15:41 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 9441B21F9D01 for <gen-art@ietf.org>; Wed, 17 Jul 2013 11:15:41 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id CD85D88129; Wed, 17 Jul 2013 11:15:40 -0700 (PDT)
Received: from clemson.local (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 14C04130003; Wed, 17 Jul 2013 11:15:39 -0700 (PDT)
Message-ID: <51E6DF5A.8010103@innovationslab.net>
Date: Wed, 17 Jul 2013 14:15:54 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Lori Jakab <lojakab@cisco.com>
References: <51DCE0A1.90807@gmail.com> <51DEA9A5.2040405@cisco.com> <51DF12C1.2080506@gmail.com> <51E6DA1E.9070207@cisco.com>
In-Reply-To: <51E6DA1E.9070207@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-lisp-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-lisp-deployment-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, 17 Jul 2013 18:15:46 -0000

I would suggest waiting for the secdir review and generate a single 
update based on all reviews.

Regards,
Brian H.

On 7/17/13 1:53 PM, Lori Jakab wrote:
> Hi Brian,
>
> Should we post a new revision of the draft now, with the below changes,
> or should we wait for the security review first?
>
> -Lori
>
> On 7/11/13 11:17 PM, Brian E Carpenter wrote:
>> Hi Lori, see in line.
>>
>> On 12/07/2013 00:48, Lori Jakab wrote:
>>> Hi Brian,
>>>
>>> Thank you for reviewing.  Please find replies to you comments inline.
>>>
>>> On 7/10/13 7:18 AM, Brian E Carpenter 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-lisp-deployment-09.txt
>>>> Reviewer: Brian Carpenter
>>>> Review Date: 2013-07-10
>>>> IETF LC End Date: 2013-07-15
>>>> IESG Telechat date:
>>>>
>>>> Summary:  Almost ready
>>>> --------
>>>>
>>>> Comments:
>>>> ---------
>>>>
>>>> I was assigned to review -08, but -09 came out during Last Call.
>>>>
>>>> Issues:
>>>> -------
>>>>
>>>> The draft states in its Introduction that it "is expected to evolve as
>>>> LISP
>>>> deployment progresses, and the described scenarios are better
>>>> understood or
>>>> new scenarios are discovered." The desire to freeze a version of the
>>>> draft
>>>> as an RFC is understandable, but shouldn't the title and Abstract
>>>> clearly
>>>> indicate that it's a snapshot (and genuinely a request for comments)?
>>> I'm not sure a change in the title is warranted (please suggest a new
>>> title if you think it is), but I agree the Abstract should be reworded.
>>> How about this new text replacing the old one:
>>>
>>>     This document is a snapshot of different Locator/Identifier
>>>     Separation Protocol (LISP) deployment scenarios.  It discusses the
>>>     placement of new network elements introduced by the protocol,
>>>     representing the thinking of the authors as of Summer 2013.  LISP
>>>     deployment scenarios may have evolved since. This memo represents
>>>     one stable point in that evolution of understanding.
>> That's good. I don't feel strongly about the title.
>>
>>>
>>>> In general the draft is clear and well written. If you believe that
>>>> there
>>>> are sufficient incentives for Tier 3 providers and large sites to
>>>> deploy
>>>> an experimental protocol such as LISP, the discussion is useful.
>>>> However,
>>>> I am disappointed by the limited discussion of scalability. In
>>>> particular,
>>>> the incentives to deploy P-ITRs and to announce routes to them will
>>>> become
>>>> a critical issue at the half-way stage between early transition (LISP
>>>> is a
>>>> minority solution) and late transition (LISP is the majority solution).
>>>> According to RFC 6832, P-ITRs scale either because "aggregate routes
>>>> might
>>>> be selectively announced" or because "the same address might be
>>>> announced
>>>> by multiple Proxy-ITRs in order to share the traffic." I really
>>>> expected
>>>> the deployment draft to discuss this issue in more detail. As I believe
>>>> has been said before, these issues are very similar to the issues
>>>> facing
>>>> the operators of a 6to4 forward or return relay. We have experimental
>>>> evidence there that altruism doesn't work and the incentives to
>>>> "donate"
>>>> connectivity are insufficient. The analogy isn't perfect, but the
>>>> underlying
>>>> question is similar - what is the incentive for a particular
>>>> operator to
>>>> offer P-ITR service for a particular bunch of EID prefixes, when the
>>>> clientele might be up to half the Internet, depending on who chooses to
>>>> propagate the routes?
>>> I was hoping we addressed these concerns in Section 5.3, Proxy-ITR Route
>>> Distribution (PITR-RD).  I agree that altruism doesn't work, that's why
>>> the PITR-RD scenario is based on business relationships between
>>> different providers.  When someone registers a domain name, he/she pays
>>> an annual fee that should cover the operating expenses for publishing
>>> the domain in the global DNS.  The situation is similar with several
>>> other registration services.  When someone contacts a mapping service
>>> provider (MSR), to get their prefix registered in the LISP mapping
>>> system, they get the option of signing up for PITR services as well, for
>>> an extra fee.  These services may be offered by the MSP themselves, but
>>> it is expected that specialized P-ITR service providers (PSPs) will do
>>> it.  If they don't sign up, they become responsible for getting non-LISP
>>> traffic to their EIDs (using the LISP+BGP scenario).
>>>
>>> Additionally, Tier 1 ISPs may offer P-ITR services to non-subscribers in
>>> strategic places just to attract more traffic from competitors, thus
>>> more revenue.
>>>
>>> Should we add anything to this section to resolve the comment?
>> The explanation you have just written is quite informative. We're a bit
>> shy in the IETF about discussing incentives, but I think your explanation
>> would fit nicely into the draft. (I'm embarassed that we didn't
>> get this right for 6to4.)
>>
>>>> The Security Considerations are minimal. I wonder if
>>>> draft-ietf-lisp-threats
>>>> identifies threats for each scenario described in
>>>> draft-ietf-lisp-deployment?
>>>> If not, the statement "Security implications of LISP deployments are
>>>> to be
>>>> discussed in separate documents." is rather optimistic.
>>>>
>>> draft-ietf-lisp-threats discusses general LISP deployment security
>>> issues, without analyzing all scenarios described in
>>> draft-ietf-lisp-deployment.  I'm not sure such an iterative approach is
>>> necessary, unless scenario specific threats are discovered.
>>
>> I expect you will be getting a Security Area review, so maybe
>> you'd better go by that.
>>
>>      Brian
>>
>>> Best regards,
>>> -Lori
>>>


From elwynd@dial.pipex.com  Wed Jul 17 14:55:53 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F121A21F9D4F for <gen-art@ietfa.amsl.com>; Wed, 17 Jul 2013 14:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.932
X-Spam-Level: 
X-Spam-Status: No, score=-100.932 tagged_above=-999 required=5 tests=[AWL=1.667, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QfRBB81E5T5u for <gen-art@ietfa.amsl.com>; Wed, 17 Jul 2013 14:55:40 -0700 (PDT)
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 30E9421F9E6A for <gen-art@ietf.org>; Wed, 17 Jul 2013 14:55:40 -0700 (PDT)
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 1UzZh5-00051M-NQ; Wed, 17 Jul 2013 22:55:36 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <BC80BF12-992E-4245-8C38-4F425EFD820A@cisco.com>
References: <1373115697.4524.42154.camel@mightyatom> <7B3ED28F-E27B-4B16-B73E-8070B830D437@piuha.net> <130E5C09-1C4D-4EF1-AE09-95E3F9D29F63@cisco.com> <1374072098.4524.48650.camel@mightyatom> <BC80BF12-992E-4245-8C38-4F425EFD820A@cisco.com>
Content-Type: text/plain
Date: Wed, 17 Jul 2013 22:54:54 +0100
Message-Id: <1374098094.4524.49064.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: draft-ietf-dhc-dhcpv6-failover-requirements.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art LC review: draft-ietf-dhc-dhcpv6-failover-requirements-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2013 21:55:53 -0000

:-)

On Wed, 2013-07-17 at 11:38 -0400, Kim Kinnear wrote:
> Elwyn,
> 
> I love the "NEW" paragraph below.  We'll be sure to
> use that.  
> 
> Thanks!
> 
> Kim
> 
> On Jul 17, 2013, at 10:41 AM, Elwyn Davies wrote:
> 
> > Hi, Kim.
> > 
> > Thanks for the reponses.
> > 
> > Looks like we are pretty well agreed. Just these two points: 
> > 
> > On s7, item 6: Just a thought so I'll consider it irrelevant.
> > 
> > On the last para of 7, I clearly failed to notice the date on the draft
> > for DHCPv4 failover protocol! [The hazards of an infinite archive for
> > I-Ds!]  So I understand why this probably isn't  going to go all the way
> > to an inter-operable protocol for either v4 or v6.  Perhaps it might be
> > worth adding in a few words to explain this (and improve an editorial
> > nit I missed):
> > OLD:
> >   Despite the lack of standardization of DHCPv4 failover, the
> >   coexistence of DHCPv4 and DHCPv6 failover may be taken into
> >   consideration.  In particular, certain features that are common for
> >   both IPv4 and IPv6, like DNS Update mechanism should be taken into
> >   consideration. 
> > NEW:
> >   Although progress on a standardized inter-operable DHCPv4 failover
> >   protocol has stalled, vendor-specific DHCPv4 failover protocols 
> >   have been deployed that meet these requirements to a large extent.
> >   Accordingly it would be appropriate to take into account the likely 
> >   coexistence of DHCPv4 and DHCPv6 failover solutions.  In particular, 
> >   certain features that are common to both IPv4 and IPv6 
> >   implementations, such as any DNS Update mechanism, should be taken into
> >   consideration to ensure compatible operation.
> > 
> > Regards,
> > Elwyn
> > 
> > On Tue, 2013-07-16 at 10:38 -0400, Kim Kinnear wrote:
> >> Jari, Elwyn,
> >> 
> >> Elwyn -- thank you for the thoughtful review.  My comments
> >> are indented below...
> >> 
> >> On Jul 16, 2013, at 3:36 AM, Jari Arkko wrote:
> >> 
> >>> Thank you for your review, Elwyn. Do the authors have any thoughts on the issues that Elwyn raises here?
> >>> 
> >>> Jari
> >>> 
> >>> On Jul 6, 2013, at 3:01 PM, Elwyn Davies <elwynd@dial.pipex.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-dhc-dhcpv6-failover-requirements-06.txt
> >>>> Reviewer: Elwyn Davies
> >>>> Review Date: 6 July 2013
> >>>> IETF LC End Date: 17 July 2013
> >>>> IESG Telechat date: (if known) -
> >>>> 
> >>>> Summary: Almost ready.  There are a few very minor issues and a fair
> >>>> number of editorial nits to fix but generally in good shape.
> >>>> 
> >>>> Major issues:
> >>>> None
> >>>> 
> >>>> Minor issues:
> >>>> s1, Introduction of Primary/Secondary terminology: The introduction
> >>>> talks about multiple servers (i.e., potentially > 2) but then in the
> >>>> last sentence of para 1 introduces primary and secondary servers.  The
> >>>> initial impression this gives is that the number of servers has now been
> >>>> reduced to <= 2.  Having read through the rest of the document I can see
> >>>> how I am supposed to interpret the last sentence of para 1, but things
> >>>> would be much clearer if an extra sentence or three describing the
> >>>> chosen model (and its intended extension) was added just before this
> >>>> last sentence.  Maybe something like:
> >>>> The failover model, to which these requirements apply, will initially
> >>>> be a pairwise "hot standby" model (see Section 4.1) with a primary 
> >>>> server used in normal operation switching over to a backup secondary 
> >>>> server in the event of failure.  Optionally, a secondary server may 
> >>>> provide failover service for multiple primary servers.  However the 
> >>>> requirements will not preclude a future load-balancing extension 
> >>>> where there is a symmetric failover relationship. 
> >> 
> >> 	Yes, this is a fine idea.  Thanks for the sentence.
> >>>> 
> >>>> s7: Related to the previous comment, perhaps it should be made explicit
> >>>> that the resulting protocol is "load-balancing friendly" to avoid rework
> >>>> if at all possible.  Since both v4 and v6 load-balancing and v4 failover
> >>>> with load-balancing are in progress, it should be known how to avoid
> >>>> pitfalls by the time the v6 failover protocol is designed!
> >> 
> >> 	Sure, we'll put something in to deal with that.
> >>>> 
> >>>> s7, item 4, last sentence: 
> >>>> "Long-lived connections must not be disturbed."
> >>>> I don't believe the DHCPv6 server or the failover protocol can either
> >>>> know that an address is in use for long lived connections or guarantee
> >>>> that they won't be disturbed beyond what is said earlier in this item.
> >>>> Presumably what is meant is something like: "Lease stability has the aim
> >>>> of avoiding disturbance to long-lived connections."
> >> 
> >> 	Yes, we'll reword this as you suggest.
> >>>> 
> >>>> s7, item 6:  Maybe irrelevant thought: Presumably you could build a
> >>>> failover system using a shared, reliable database and a minimalistic
> >>>> version of the failover protocol instead of using lazy updates.  Should
> >>>> this be explicitly an option?
> >> 
> >> 	Well, this thought is explored in Section 3.1.3, but under
> >> 	the overall heading of "Alternatives to Failover".  Is this
> >> 	an alternative *to* failover, or an option *for* failover 
> >> 	(as you suggest might be appropriate)?  Hard to say. 
> >> 
> >> 	I suppose that our design draft, already about to go to
> >> 	last call, influenced our thinking to some degree when we
> >> 	wrote this.  I don't think the document would be substantively
> >> 	better were we to change it so that a distributed database
> >> 	solution is an option as opposed to an alternative.  So,
> >> 	to be clear, I don't think changing this is a good idea.
> >> 
> >>>> 
> >>>> s7, last para: "Despite the lack of standardization of DHCPv4
> >>>> failover...": It appears that work is in progress on this
> >>>> (http://tools.ietf.org/html/draft-ietf-dhc-failover-12)... so what is
> >>>> meant here?
> >> 
> >> 	The work in progress ended years ago.  Many years ago.
> >> 	The document which you reference is ~132 pages long, and
> >> 	has requirements, design, and protocol all in one
> >> 	document.  It was essentially too big and complicated to
> >> 	be digested by the IETF.  We could not even get the AD at
> >> 	the time to review the entire document.  In part this was
> >> 	because the problem was important to solve in an
> >> 	intra-vendor way, but inter-vendor capable failover was
> >> 	not important in the real world (i.e., nobody really
> >> 	cared to pay extra for failover that worked across two
> >> 	vendors servers).
> >> 
> >> 	The experience gained during the v4 failover effort is
> >> 	the reason the v6 failover effort (of which the document
> >> 	under discussion is a part) has been split into three
> >> 	separate pieces: requirements, design, and (if sufficient
> >> 	interest exists), protocol.  The hope is that these
> >> 	pieces will be individually digestible where the v4
> >> 	effort was not.
> >> 
> >> 	That said, the v6 failover design draft is already 50
> >> 	pages, and it hasn't yet undergone WG last call, though
> >> 	it is very close to that point.  
> >> 
> >> 	Plus, it is possible that we will end with the design
> >> 	document, since that will have the basics of how you
> >> 	build a v6 failover capability.  The protocol document is
> >> 	only really interesting if you want to have an
> >> 	inter-vendor failover capability.  We don't yet know how
> >> 	that will play out, though we certainly expect to give
> >> 	it a try.
> >>>> 
> >>>> Nits/editorial comments:
> >> 
> >> 	Thank you for catching these.  We will make all of these
> >> 	changes.
> >> 
> >> 	Thanks again for your review!
> >> 
> >> 	Regards -- Kim
> >> 
> >>>> 
> >>>> Global: s/i.e./i.e.,/
> >>>> Global: s/e.g./e.g.,/
> >>>> 
> >>>> Abstract: s/any way/any way that/
> >>>> 
> >>>> s2: Expoand acronyms CPR, IA - even though IA is defined in RFC 3315, it
> >>>> would help readability to repeat the expansion.
> >>>> 
> >>>> s2, lease: Should this mention something about length of time for which
> >>>> the lease will be valid?
> >>>> 
> >>>> s3.1.1: Expand PXE acronym.
> >>>> 
> >>>> s3.1.1, para 1:
> >>>> OLD
> >>>> Address and possibly other
> >>>> configuration parameters are used during boot process and are
> >>>> discarded afterwards. 
> >>>> NEW:
> >>>> The address and possibly other
> >>>> configuration parameters are used during the boot process and are
> >>>> discarded thereafter. 
> >>>> 
> >>>> s3.1.1, para 2: s/distinct preference set/a distinct preference set/
> >>>> 
> >>>> s3.1.2, para 2:
> >>>> OLD:
> >>>> There are several well documented approaches how such deployment
> >>>> works. 
> >>>> NEW:
> >>>> There are several well-documented approaches showing how such a deployment
> >>>> could work.
> >>>> 
> >>>> s3.1.3, para 2:
> >>>> OLD:
> >>>> It is also essential to use only databases that are really
> >>>> distributed and do not have single point of failure themselves.
> >>>> NEW:
> >>>> It is also essential to use only a database system that provides 
> >>>> equivalent reliability and failover capability. 
> >>>> 
> >>>> s4: This paragraph implies that the document defines a protocol contrary
> >>>> to its expressed intention and reality.
> >>>> OLD:
> >>>> These scenarios may be inside or
> >>>> outside of scope for DHCPv6 failover protocol as defined by this
> >>>> document.  They are enumerated here to provide a common basis for
> >>>> discussion.
> >>>> NEW:
> >>>> These scenarios may be in or
> >>>> out of scope for the DHCPv6 failover model to which this 
> >>>> document's requirements apply; they are enumerated here to provide a 
> >>>> common basis for discussion.   
> >>>> 
> >>>> s5, para 2: s/General failover concept/The general failover concept/, 
> >>>> s/in case of the primary server/in case of a primary server/,
> >>>> s/In case of just/In the case of just/,
> >>>> s/Had there be more than two partners/Were there more than two partners/
> >>>> (subjunctive!)
> >>>> 
> >>>> s5, para 2:
> >>>> OLD:
> >>>> there would be a third states in between (some
> >>>> partners updated their state, but some didn't).
> >>>> NEW:
> >>>> there would be intermediate, inconsistent states where some partners
> >>>> had updated their state and some had not.
> >>>> 
> >>>> s4.1: s/Only one of partners/Only one of the partners/
> >>>> 
> >>>> s4.6, para 2: s/every time IPv6 address changes/every time an IPv6
> >>>> address changes/
> >>>> 
> >>>> s4.6, para 3: s/having stable address/having a stable address/
> >>>> 
> >>>> s5.1, last sentence:  This seems to imply that *this section* states
> >>>> whether the failure mode is in or out of scope for the protocol.  It
> >>>> doesn't - that is postponed to s7.  Either remove this sentence or
> >>>> redraft to refer to s7.
> >>>> 
> >>>> s5.1.2, para 2: s/is that partner also detected/is that the partner also
> >>>> detected/
> >>>> 
> >>>> s5.2: s/synchronization methods/synchronization method/,
> >>>> s/familiarity with distributed database/familiarity with distributed database technology/
> >>>> 
> >>>> s5.2.1, para 1: s/response from partner/response from its partner/
> >>>> 
> >>>> s5.2.1, para 2: 'large' is an over-generalization. Maybe:
> >>>> s/a large performance penalty/typically a significant performance penalty/
> >>>> 
> >>>> s5.2.1, para 3:
> >>>> OLD:
> >>>> Due to advent of SSD disks or battery backed ram disks technology,
> >>>> NEW:
> >>>> Due to the advent of fast SSD (solid state disk) and battery-backed RAM 
> >>>> (random access memory) disk technology,
> >>>> 
> >>>> s5.2.2, para 2: s/if server crashes/if the server crashes/
> >>>> 
> >>>> s7, item 4: s/should pose/should have/
> >>>> 
> >>>> _______________________________________________
> >>>> Gen-art mailing list
> >>>> Gen-art@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/gen-art
> >>> 
> >> 
> > 
> 


From david.black@emc.com  Wed Jul 17 16:55:08 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 427AE21F88D2; Wed, 17 Jul 2013 16:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.196
X-Spam-Level: 
X-Spam-Status: No, score=-102.196 tagged_above=-999 required=5 tests=[AWL=-0.197, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehLTLOl-G-SI; Wed, 17 Jul 2013 16:54:52 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6612C21F99C3; Wed, 17 Jul 2013 16:54:48 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6HNsf66028956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jul 2013 19:54:41 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 17 Jul 2013 19:54:30 -0400
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6HNsTmm024844; Wed, 17 Jul 2013 19:54:29 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Wed, 17 Jul 2013 19:54:28 -0400
From: "Black, David" <david.black@emc.com>
To: "ldunbar@huawei.com" <ldunbar@huawei.com>, Donald Eastlake <d3e3e3@gmail.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>, General Area Review Team <gen-art@ietf.org>
Date: Wed, 17 Jul 2013 19:54:27 -0400
Thread-Topic: Gen-ART review of draft-ietf-trill-directory-framework-05
Thread-Index: Ac6DSPiBG6FbLQSdQg+o47Dp8whwIw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712984AC753@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: Ted Lemon <Ted.Lemon@nominum.com>, "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-trill-directory-framework-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2013 23:55:09 -0000

Document: draft-ietf-trill-directory-framework-05
Reviewer: David L. Black
Review Date: July 17, 2013
IETF LC End Date: July 18, 2013

Summary:
This draft is on the right track but has open issues, described in the revi=
ew.

This draft describes a framework for using directory servers to provide
address mappings (address -> destination RBridge) to TRILL Rbridges as an
alternative to data plane learning and use of the TRILL ESADI protocol.

The draft's generally well written and clear.  I found a couple of minor
issues.

Major issues: None.

Minor issues:

[1] The last bullet in Section 3.1 says:

       - In an environment where VMs migrate, there is a higher chance
         of cached information becoming invalid, causing traffic to be
         black-holed by the ingress RBridge, that is, persistently sent
         to the wrong egress RBridge. If VMs do not flood gratuitous
         ARP/ND or VDP [802.1Qbg] messages upon arriving at new
         locations, the ingress nodes might not have MAC entries for the
         MAC of the newly arrived VMs, causing unknown address flooding.

This is incorrect in multiple ways and should just be removed:

- Persistent black-holing is rare in practice because all common
	VM migration implementations issue the gratuitous messages.
- VMs don't send the gratuitous messages, hypervisors do.
- VDP is not flooded.  The receiver's always a bridge.
- At least one common VM migration implementation actually uses a gratuitou=
s
	RARP, not ARP.
- Flooding is done by the bridges and Rbridges, not the VMs.

[2] There are some unfortunate notation problems in Section 5.1 that carry
into the following sections, based on the logical data structure:

   [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
   interested RBridges}]

- The first open curly brace ('{') is unmatched.
- Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
	none of which appear in that structure.

Nits/editorial comments:

Section 1 - item 1 in the numbered list does not explain why it makes
a directory approach attractive.  This should be added, as it is
present for the other three items .

Section 2 - Say that IS-IS is a routing protocol.
The definition of Station should say that the node or virtual node
is on a network.  Also, please define or explain "virtual node".

Section 3.2 - Add the number of entries to be learned to scenario #1
in order to parallel the scenario # 2 discussion.

Section 4 - remove "(distributed model)" from first paragraph,
as it's not explained.

Section 5.3, top of p.13:

   therefore, there needs to be some mechanism by which RBridges that
   have pulled information that has not expired can be informed when
   that information changes or the like.

"or the like" is vague.  I suggest "or becomes invalid for other
 reasons".

idnits 2.12.17 didn't find any nits that need attention.

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


From tomasz.mrugalski@gmail.com  Thu Jul 18 10:34:40 2013
Return-Path: <tomasz.mrugalski@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 0A7B011E818B for <gen-art@ietfa.amsl.com>; Thu, 18 Jul 2013 10:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[AWL=0.163,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ln5ybURDzOpc for <gen-art@ietfa.amsl.com>; Thu, 18 Jul 2013 10:34:39 -0700 (PDT)
Received: from mail-bk0-x233.google.com (mail-bk0-x233.google.com [IPv6:2a00:1450:4008:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id E25D521E8146 for <gen-art@ietf.org>; Thu, 18 Jul 2013 10:34:38 -0700 (PDT)
Received: by mail-bk0-f51.google.com with SMTP id ji1so1289275bkc.24 for <gen-art@ietf.org>; Thu, 18 Jul 2013 10:34:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:x-tagtoolbar-keys :content-type:content-transfer-encoding; bh=LOc9MLPoutg+Eqdsq6jmDyrtzoopMiOkgnMtAXcMlJE=; b=qxjD72RlLUaSXFglWJCPl6YhbPyZNgFS0nhtn1AUceZgwDpnTtjR+K+FjemJOzYp9Z SR6/jfzFzBYtyg1MmwqvPGQENoo0WW0QI5We9fce3e/5L+lH+Dwj/PxiRk6FNFaX/VQq FpglxoE70HFapHzBZJejIxc61QRf5dgyAYEXCDIW67hYY3VoUVA0/Is6A3vLm2aS4du/ tYCMO7UPXK/8Bx3xhirG0LJKmE1rKIQwKxJifuDTC/9kL3M5umNPJgwsqjLtJWd+srmY DiDlZwsha3MUDcbbjGE2oRUBHMHQtxPmu7F1fCFiJaNujHlU8DMamcUOt4jh7m0AjQru OX0g==
X-Received: by 10.205.116.1 with SMTP id fg1mr1913947bkc.169.1374168876836; Thu, 18 Jul 2013 10:34:36 -0700 (PDT)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id kz11sm3624896bkb.11.2013.07.18.10.34.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Jul 2013 10:34:35 -0700 (PDT)
Message-ID: <51E82726.7040502@gmail.com>
Date: Thu, 18 Jul 2013 19:34:30 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Elwyn Davies <elwynd@dial.pipex.com>
References: <1373115697.4524.42154.camel@mightyatom> <7B3ED28F-E27B-4B16-B73E-8070B830D437@piuha.net> <130E5C09-1C4D-4EF1-AE09-95E3F9D29F63@cisco.com> <1374072098.4524.48650.camel@mightyatom>
In-Reply-To: <1374072098.4524.48650.camel@mightyatom>
X-Enigmail-Version: 1.4.6
X-TagToolbar-Keys: D20130718193430907
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 18 Jul 2013 10:38:45 -0700
Cc: draft-ietf-dhc-dhcpv6-failover-requirements.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [Gen-art] Gen-art LC review: draft-ietf-dhc-dhcpv6-failover-requirements-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 17:34:40 -0000

On 17.07.2013 16:41, Elwyn Davies wrote:
> On s7, item 6: Just a thought so I'll consider it irrelevant.
> 
> On the last para of 7, I clearly failed to notice the date on the draft
> for DHCPv4 failover protocol! [The hazards of an infinite archive for
> I-Ds!]  So I understand why this probably isn't  going to go all the way
> to an inter-operable protocol for either v4 or v6.  Perhaps it might be
> worth adding in a few words to explain this (and improve an editorial
> nit I missed):
> OLD:
>    Despite the lack of standardization of DHCPv4 failover, the
>    coexistence of DHCPv4 and DHCPv6 failover may be taken into
>    consideration.  In particular, certain features that are common for
>    both IPv4 and IPv6, like DNS Update mechanism should be taken into
>    consideration. 
> NEW:
>    Although progress on a standardized inter-operable DHCPv4 failover
>    protocol has stalled, vendor-specific DHCPv4 failover protocols 
>    have been deployed that meet these requirements to a large extent.
>    Accordingly it would be appropriate to take into account the likely 
>    coexistence of DHCPv4 and DHCPv6 failover solutions.  In particular, 
>    certain features that are common to both IPv4 and IPv6 
>    implementations, such as any DNS Update mechanism, should be taken into
>    consideration to ensure compatible operation.
Hi Elwyn,

Thanks a lot for your thorough review and comments. The submission tool
is now closed, so I have put an unpublished -07 version here:
https://github.com/tomaszmrugalski/ietf-dhcpv6-fo/
We will upload it to IETF once the submission tool reopens.

I hope I didn't miss any comments. Please let me know if I did.

Tomek


From mahoney@nostrum.com  Thu Jul 18 15:52:44 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C75A11E8233 for <gen-art@ietfa.amsl.com>; Thu, 18 Jul 2013 15:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kblI0GrFcMHO for <gen-art@ietfa.amsl.com>; Thu, 18 Jul 2013 15:52:43 -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 C736911E8204 for <gen-art@ietf.org>; Thu, 18 Jul 2013 15:52:43 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6IMqdag048389 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 18 Jul 2013 17:52:40 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51E871B2.3070003@nostrum.com>
Date: Thu, 18 Jul 2013 17:52:34 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-07-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 22:52:44 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Joel Halpern      2013-07-29   draft-ietf-weirds-using-http-07

Kathleen Moriarty 2013-07-29   draft-ietf-weirds-rdap-sec-04

Martin Thomson    2013-08-13   draft-bormann-cbor-04

Meral Shirazipour 2013-07-30   draft-ietf-emu-eap-tunnel-method-07

Peter McCann      2013-07-31   draft-ietf-mpls-retire-ach-tlv-02

Peter Yee         2013-07-31   draft-ietf-geopriv-res-gw-lis-discovery-05


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  Thu Jul 18 16:34:50 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2490711E8236 for <gen-art@ietfa.amsl.com>; Thu, 18 Jul 2013 16:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h4ZRNAM1NxXW for <gen-art@ietfa.amsl.com>; Thu, 18 Jul 2013 16:34:45 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0557C11E80DC for <gen-art@ietf.org>; Thu, 18 Jul 2013 16:34:44 -0700 (PDT)
X-AuditID: c618062d-b7fc36d0000032ea-9f-51e87b8da2e9
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 7B.18.13034.D8B78E15; Fri, 19 Jul 2013 01:34:38 +0200 (CEST)
Received: from EUSAAMB104.ericsson.se ([147.117.188.121]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0328.009; Thu, 18 Jul 2013 19:34:37 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ivov-grouptextchat-purpose.all@tools.ietf.org" <draft-ivov-grouptextchat-purpose.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ivov-grouptextchat-purpose-03
Thread-Index: Ac6EDwUJuEqMgjbGRNuTIxPIDRxe/g==
Date: Thu, 18 Jul 2013 23:34:37 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A5B954C@eusaamb104.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A5B954Ceusaamb104ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyuXRPlG5f9YtAg+OPuC26J65ksbj66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJXx8vlPxoI1yhUTFy9ibGDcLt/FyMkhIWAi sWzpLmYIW0ziwr31bF2MXBxCAkcZJe4fms0O4SxnlJjTv5odpIpNwEJi++/nrCC2iMAsRonD 67xAbGEBD4lFOw9CxX0ldk48DWXrSWx5fB9sA4uAqsTsB4uBbA4OXgFviYOTrUDCjECLv59a wwRiMwuIS9x6Mp8J4iABiSV7zkMdJyrx8vE/VghbWWLJk/0sEPX5EvNOPQCr5xUQlDg58wnL BEahWUhGzUJSNgtJGURcR2LB7k9sELa2xLKFr5lh7DMHHjMhiy9gZF/FyFFanFqWm25ksIkR GA3HJNh0dzDueWl5iFGag0VJnHeV3plAIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYwFDowi PyRl+Uzf14grzLyltXNd0Fr9Dh6moOqEp1/NW059V4rLbCopfPn91/NbbW0XPxyp17jH/3pZ tLi7IWtMvGH6oTzZy3uY79QFvQqZO9MzfuqsqeUvdk+Nq/HX2vJjf66MrneQ8U1Nxsazf8RS xbJeTbznOuf64aOZpv7Pan7O4I27b6jEUpyRaKjFXFScCACkDuZPVAIAAA==
Subject: [Gen-art] Gen-ART Last Call review of draft-ivov-grouptextchat-purpose-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 23:34:50 -0000

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

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

Please resolve any other Last Call comments you may receive.

Document: draft-ivov-grouptextchat-purpose-03
Reviewer: Meral Shirazipour
Review Date: 2013-07-18
IETF LC End Date: 2013-07-22
IESG Telechat date: NA



Summary:
This draft is ready to be published as Informational  RFC.


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


--_000_ABCAA4EF18F17B4FB619EA93DEF7939A5B954Ceusaamb104ericsso_
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;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> &nbsp;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve any other Last Call comments you may =
receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ivov-grouptextchat-purpose-03<o:p></=
o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-07-18<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-07-22<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"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is ready to be published as Informational=
&nbsp; RFC.<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></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>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A5B954Ceusaamb104ericsso_--

From d3e3e3@gmail.com  Fri Jul 19 04:55:56 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D18011E810A; Fri, 19 Jul 2013 04:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.213
X-Spam-Level: 
X-Spam-Status: No, score=-102.213 tagged_above=-999 required=5 tests=[AWL=-0.212, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qB2ElY8Hu89r; Fri, 19 Jul 2013 04:55:56 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id AB7B711E8105; Fri, 19 Jul 2013 04:55:55 -0700 (PDT)
Received: by mail-ob0-f179.google.com with SMTP id xk17so5205360obc.10 for <multiple recipients>; Fri, 19 Jul 2013 04:55:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=bQ0MKVmTCbs+qZBoTSi99ilGf9pNCdODN9AolNIvgCU=; b=Y9NipZB+WAFWl2zEk7WBUSv6OHY2c9p0SLKvTcKFOiQYSCB7m+FvzTLkXkylakfuAw jg00W1h7JKMCJsKsuCTGf24BXrxPZY9x21c8iAzQyqCiaZ1Ffj6P9TexveLwB+msGCVH tOv9Lol+mzdiA/1T7beOHDoTbTTpvNKrmiG4LSavPKiwF0gOz+uLQ48aJ9Mfs8Ptx/pF bHu7JS57ZIJuTMP+dXTERseUqogRHNvIh89JCW5qNROP8V4Y2PSsQO+ChTO1NKKbcbrt MFj52L0TgqjlsiRS37EanE2QtnQDFGmXaBWiIE5RLe5jg3vO4QDQw5MqhZpq+k5BTcWH p6Jg==
X-Received: by 10.60.42.101 with SMTP id n5mr17617516oel.4.1374234955231; Fri, 19 Jul 2013 04:55:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.73.106 with HTTP; Fri, 19 Jul 2013 04:55:35 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712984AC753@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712984AC753@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 19 Jul 2013 07:55:35 -0400
Message-ID: <CAF4+nEEdg27WfotYaV0OzTgzN=_pnCxwbvm=JatizsHGJDkw9w@mail.gmail.com>
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ldunbar@huawei.com" <ldunbar@huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, Ted Lemon <Ted.Lemon@nominum.com>, "trill@ietf.org" <trill@ietf.org>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-directory-framework-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, 19 Jul 2013 11:55:56 -0000

Hi David,

Thanks for the review. See responses below.

On Wed, Jul 17, 2013 at 7:54 PM, Black, David <david.black@emc.com> wrote:
> Document: draft-ietf-trill-directory-framework-05
> Reviewer: David L. Black
> Review Date: July 17, 2013
> IETF LC End Date: July 18, 2013
>
> Summary:
> This draft is on the right track but has open issues, described in the review.
>
> This draft describes a framework for using directory servers to provide
> address mappings (address -> destination RBridge) to TRILL Rbridges as an
> alternative to data plane learning and use of the TRILL ESADI protocol.
>
> The draft's generally well written and clear.  I found a couple of minor
> issues.

Thanks.

> Major issues: None.
>
> Minor issues:
>
> [1] The last bullet in Section 3.1 says:
>
>        - In an environment where VMs migrate, there is a higher chance
>          of cached information becoming invalid, causing traffic to be
>          black-holed by the ingress RBridge, that is, persistently sent
>          to the wrong egress RBridge. If VMs do not flood gratuitous
>          ARP/ND or VDP [802.1Qbg] messages upon arriving at new
>          locations, the ingress nodes might not have MAC entries for the
>          MAC of the newly arrived VMs, causing unknown address flooding.
>
> This is incorrect in multiple ways and should just be removed:

OK.

> - Persistent black-holing is rare in practice because all common
>         VM migration implementations issue the gratuitous messages.
> - VMs don't send the gratuitous messages, hypervisors do.
> - VDP is not flooded.  The receiver's always a bridge.
> - At least one common VM migration implementation actually uses a gratuitous
>         RARP, not ARP.
> - Flooding is done by the bridges and Rbridges, not the VMs.
>
> [2] There are some unfortunate notation problems in Section 5.1 that carry
> into the following sections, based on the logical data structure:
>
>    [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
>    interested RBridges}]
>
> - The first open curly brace ('{') is unmatched.
> - Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
>         none of which appear in that structure.

We'll try to clean that up.

> Nits/editorial comments:
>
> Section 1 - item 1 in the numbered list does not explain why it makes
> a directory approach attractive.  This should be added, as it is
> present for the other three items .

I suggest combining point 1 with the material just before the table
and re-numbering points 2-4 to be 1-3.

> Section 2 - Say that IS-IS is a routing protocol.
> The definition of Station should say that the node or virtual node
> is on a network.  Also, please define or explain "virtual node".

OK on the first two points. On "virtual node", that is only used in
the definition of "station" which is different from the definition of
"end station". However, looking through the document, there was only
one instance of "station" without "end" before it and that instance
was talking about end stations. So I propose to remove the definition
of "station" and to insert "end" before the one occurrence of
"station" in the body of the document not already preceded by "end".

> Section 3.2 - Add the number of entries to be learned to scenario #1
> in order to parallel the scenario # 2 discussion.

OK.

> Section 4 - remove "(distributed model)" from first paragraph,
> as it's not explained.

OK.

> Section 5.3, top of p.13:
>
>    therefore, there needs to be some mechanism by which RBridges that
>    have pulled information that has not expired can be informed when
>    that information changes or the like.
>
> "or the like" is vague.  I suggest "or becomes invalid for other
>  reasons".

OK.

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

> idnits 2.12.17 didn't find any nits that need attention.
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------

From david.black@emc.com  Fri Jul 19 06:16:49 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D108D11E812A; Fri, 19 Jul 2013 06:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hriDw+FOmXDG; Fri, 19 Jul 2013 06:16:44 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id EC15F11E8117; Fri, 19 Jul 2013 06:16:43 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6JDGN9i015225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jul 2013 09:16:24 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Fri, 19 Jul 2013 09:16:03 -0400
Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6JDG2bh015134; Fri, 19 Jul 2013 09:16:02 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub31.corp.emc.com ([128.222.70.171]) with mapi; Fri, 19 Jul 2013 09:16:02 -0400
From: "Black, David" <david.black@emc.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 19 Jul 2013 09:16:00 -0400
Thread-Topic: Gen-ART review of draft-ietf-trill-directory-framework-05
Thread-Index: Ac6EdvpzYre5W29/SUuNLTq5/fBXxwACvX6w
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712984AC9E9@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712984AC753@MX15A.corp.emc.com> <CAF4+nEEdg27WfotYaV0OzTgzN=_pnCxwbvm=JatizsHGJDkw9w@mail.gmail.com>
In-Reply-To: <CAF4+nEEdg27WfotYaV0OzTgzN=_pnCxwbvm=JatizsHGJDkw9w@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: "ldunbar@huawei.com" <ldunbar@huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, Ted Lemon <Ted.Lemon@nominum.com>, "trill@ietf.org" <trill@ietf.org>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-directory-framework-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, 19 Jul 2013 13:16:50 -0000

Hi Donald,

All of your responses are fine with me.

Thanks,
--David

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Friday, July 19, 2013 7:56 AM
> To: Black, David
> Cc: ldunbar@huawei.com; Radia@alum.mit.edu; igor@yahoo-inc.com; General A=
rea
> Review Team; trill@ietf.org; ietf@ietf.org; Ted Lemon
> Subject: Re: Gen-ART review of draft-ietf-trill-directory-framework-05
>=20
> Hi David,
>=20
> Thanks for the review. See responses below.
>=20
> On Wed, Jul 17, 2013 at 7:54 PM, Black, David <david.black@emc.com> wrote=
:
> > Document: draft-ietf-trill-directory-framework-05
> > Reviewer: David L. Black
> > Review Date: July 17, 2013
> > IETF LC End Date: July 18, 2013
> >
> > Summary:
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > This draft describes a framework for using directory servers to provide
> > address mappings (address -> destination RBridge) to TRILL Rbridges as =
an
> > alternative to data plane learning and use of the TRILL ESADI protocol.
> >
> > The draft's generally well written and clear.  I found a couple of mino=
r
> > issues.
>=20
> Thanks.
>=20
> > Major issues: None.
> >
> > Minor issues:
> >
> > [1] The last bullet in Section 3.1 says:
> >
> >        - In an environment where VMs migrate, there is a higher chance
> >          of cached information becoming invalid, causing traffic to be
> >          black-holed by the ingress RBridge, that is, persistently sent
> >          to the wrong egress RBridge. If VMs do not flood gratuitous
> >          ARP/ND or VDP [802.1Qbg] messages upon arriving at new
> >          locations, the ingress nodes might not have MAC entries for th=
e
> >          MAC of the newly arrived VMs, causing unknown address flooding=
.
> >
> > This is incorrect in multiple ways and should just be removed:
>=20
> OK.
>=20
> > - Persistent black-holing is rare in practice because all common
> >         VM migration implementations issue the gratuitous messages.
> > - VMs don't send the gratuitous messages, hypervisors do.
> > - VDP is not flooded.  The receiver's always a bridge.
> > - At least one common VM migration implementation actually uses a gratu=
itous
> >         RARP, not ARP.
> > - Flooding is done by the bridges and Rbridges, not the VMs.
> >
> > [2] There are some unfortunate notation problems in Section 5.1 that ca=
rry
> > into the following sections, based on the logical data structure:
> >
> >    [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
> >    interested RBridges}]
> >
> > - The first open curly brace ('{') is unmatched.
> > - Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
> >         none of which appear in that structure.
>=20
> We'll try to clean that up.
>=20
> > Nits/editorial comments:
> >
> > Section 1 - item 1 in the numbered list does not explain why it makes
> > a directory approach attractive.  This should be added, as it is
> > present for the other three items .
>=20
> I suggest combining point 1 with the material just before the table
> and re-numbering points 2-4 to be 1-3.
>=20
> > Section 2 - Say that IS-IS is a routing protocol.
> > The definition of Station should say that the node or virtual node
> > is on a network.  Also, please define or explain "virtual node".
>=20
> OK on the first two points. On "virtual node", that is only used in
> the definition of "station" which is different from the definition of
> "end station". However, looking through the document, there was only
> one instance of "station" without "end" before it and that instance
> was talking about end stations. So I propose to remove the definition
> of "station" and to insert "end" before the one occurrence of
> "station" in the body of the document not already preceded by "end".
>=20
> > Section 3.2 - Add the number of entries to be learned to scenario #1
> > in order to parallel the scenario # 2 discussion.
>=20
> OK.
>=20
> > Section 4 - remove "(distributed model)" from first paragraph,
> > as it's not explained.
>=20
> OK.
>=20
> > Section 5.3, top of p.13:
> >
> >    therefore, there needs to be some mechanism by which RBridges that
> >    have pulled information that has not expired can be informed when
> >    that information changes or the like.
> >
> > "or the like" is vague.  I suggest "or becomes invalid for other
> >  reasons".
>=20
> OK.
>=20
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>=20
> > idnits 2.12.17 didn't find any nits that need attention.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > david.black@emc.com        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From jmh@joelhalpern.com  Fri Jul 19 09:17:52 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 001D811E8145 for <gen-art@ietfa.amsl.com>; Fri, 19 Jul 2013 09:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vy+C-61p3NPC for <gen-art@ietfa.amsl.com>; Fri, 19 Jul 2013 09:17:47 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 1996321E80FA for <gen-art@ietf.org>; Fri, 19 Jul 2013 09:17:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 02ED31BDBBAA; Fri, 19 Jul 2013 09:17:28 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-134-244.clppva.east.verizon.net [70.106.134.244]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 77A571BDBA67; Fri, 19 Jul 2013 09:17:27 -0700 (PDT)
Message-ID: <51E96693.4060605@joelhalpern.com>
Date: Fri, 19 Jul 2013 12:17:23 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <51E871B2.3070003@nostrum.com>
In-Reply-To: <51E871B2.3070003@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]  review: draft-ietf-weirds-using-http-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 16:17:52 -0000

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

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

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

Document: draft-ietf-weirds-using-http-07
     HTTP usage in the Registration Data Access Protocol (RDAP)
Reviewer: Joel M. Halpern
Review Date: 19-July-2013
IETF LC End Date: 29-July-2013
IESG Telechat date: 15-Aug-2013

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

Major issues:

Minor issues:

Nits/editorial comments:

From elwynd@dial.pipex.com  Mon Jul 22 03:37:46 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0C6921E80EF for <gen-art@ietfa.amsl.com>; Mon, 22 Jul 2013 03:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.312
X-Spam-Level: 
X-Spam-Status: No, score=-101.312 tagged_above=-999 required=5 tests=[AWL=1.288, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VobMScJQvyZt for <gen-art@ietfa.amsl.com>; Mon, 22 Jul 2013 03:37:27 -0700 (PDT)
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 146BE21E804E for <gen-art@ietf.org>; Mon, 22 Jul 2013 03:23:25 -0700 (PDT)
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 1V1DGn-00084C-8U; Mon, 22 Jul 2013 11:23:18 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
In-Reply-To: <51E82726.7040502@gmail.com>
References: <1373115697.4524.42154.camel@mightyatom> <7B3ED28F-E27B-4B16-B73E-8070B830D437@piuha.net> <130E5C09-1C4D-4EF1-AE09-95E3F9D29F63@cisco.com> <1374072098.4524.48650.camel@mightyatom> <51E82726.7040502@gmail.com>
Content-Type: text/plain
Date: Mon, 22 Jul 2013 11:21:59 +0100
Message-Id: <1374488519.4524.56112.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: draft-ietf-dhc-dhcpv6-failover-requirements.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [Gen-art] Gen-art LC review: draft-ietf-dhc-dhcpv6-failover-requirements-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, 22 Jul 2013 10:37:46 -0000

Hi, Tomak and Kim.

I had a quick look through -07 and it appeared to have fixed all my
quibbles.

I see the draft has now been approved - so hopefully it will progress to
RFC RSN!

Regards,
Elwyn


On Thu, 2013-07-18 at 19:34 +0200, Tomek Mrugalski wrote:
> On 17.07.2013 16:41, Elwyn Davies wrote:
> > On s7, item 6: Just a thought so I'll consider it irrelevant.
> > 
> > On the last para of 7, I clearly failed to notice the date on the draft
> > for DHCPv4 failover protocol! [The hazards of an infinite archive for
> > I-Ds!]  So I understand why this probably isn't  going to go all the way
> > to an inter-operable protocol for either v4 or v6.  Perhaps it might be
> > worth adding in a few words to explain this (and improve an editorial
> > nit I missed):
> > OLD:
> >    Despite the lack of standardization of DHCPv4 failover, the
> >    coexistence of DHCPv4 and DHCPv6 failover may be taken into
> >    consideration.  In particular, certain features that are common for
> >    both IPv4 and IPv6, like DNS Update mechanism should be taken into
> >    consideration. 
> > NEW:
> >    Although progress on a standardized inter-operable DHCPv4 failover
> >    protocol has stalled, vendor-specific DHCPv4 failover protocols 
> >    have been deployed that meet these requirements to a large extent.
> >    Accordingly it would be appropriate to take into account the likely 
> >    coexistence of DHCPv4 and DHCPv6 failover solutions.  In particular, 
> >    certain features that are common to both IPv4 and IPv6 
> >    implementations, such as any DNS Update mechanism, should be taken into
> >    consideration to ensure compatible operation.
> Hi Elwyn,
> 
> Thanks a lot for your thorough review and comments. The submission tool
> is now closed, so I have put an unpublished -07 version here:
> https://github.com/tomaszmrugalski/ietf-dhcpv6-fo/
> We will upload it to IETF once the submission tool reopens.
> 
> I hope I didn't miss any comments. Please let me know if I did.
> 
> Tomek
> 


From kewisch@gmail.com  Mon Jul 22 04:55:30 2013
Return-Path: <kewisch@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 C855B21E8064; Mon, 22 Jul 2013 04:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x+cbDWmCKXYb; Mon, 22 Jul 2013 04:55:29 -0700 (PDT)
Received: from mail-bk0-x22d.google.com (mail-bk0-x22d.google.com [IPv6:2a00:1450:4008:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 25B7D21E8056; Mon, 22 Jul 2013 04:55:27 -0700 (PDT)
Received: by mail-bk0-f45.google.com with SMTP id je9so2450445bkc.18 for <multiple recipients>; Mon, 22 Jul 2013 04:55:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=PZaHTgAq9MYzJSbmvadviiQu/6RvvxuUoJgoVz0svHI=; b=ezRR0lZMQMdvg/75ZI7FihrSUhgITCVlqk+z4l25vzO/MC6Tt5SB0IsWkpQAq430nw dvc5TMa30qb2u857IhJHE2O/3gungbZUi63ivNJcgcmUJ3+atBlhZZSHhaAwFRkY+l8/ qKzaL4rkjPIDW1Mt3/IXyCrTetnP+Wl+PIi2ruqV8yxczH9C6vezqVIb83IQMCTnIQ0k N6Zw8a5KjhBJQNoeVwgA59MM1Ekun9cw2UjesvsVUhGi8UdHVIoT3Opi0NxlJCWHytVt HrHA4Z+Juixqy45sTdc5MJ4IXEqW1aA1NcxwjAgzZjseKMRJO3MIq98T7ZgJ+E2C+mU3 EX5g==
X-Received: by 10.204.231.137 with SMTP id jq9mr3927043bkb.150.1374494127029;  Mon, 22 Jul 2013 04:55:27 -0700 (PDT)
Received: from oskar.lan (f054118207.adsl.alicedsl.de. [78.54.118.207]) by mx.google.com with ESMTPSA id eu16sm6805174bkc.0.2013.07.22.04.55.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Jul 2013 04:55:26 -0700 (PDT)
Message-ID: <51ED1DAD.90904@gmail.com>
Date: Mon, 22 Jul 2013 13:55:25 +0200
From: Philipp Kewisch <kewisch@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>,  draft-ietf-jcardcal-jcard.all@tools.ietf.org
References: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com>
In-Reply-To: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com>
Content-Type: multipart/alternative; boundary="------------070106020800040203080502"
X-Mailman-Approved-At: Mon, 22 Jul 2013 04:59:06 -0700
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>, "jcardcal@ietf.org" <jcardcal@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat Review of draft-ietf-jcardcal-jcard-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2013 11:55:31 -0000

This is a multi-part message in MIME format.
--------------070106020800040203080502
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


On 7/17/13 12:27 AM, Ben Campbell wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document:  draft-ietf-jcardcal-jcard-04
> Reviewer:  Ben Campbell
> Review Date:  2013-07-16
> IETF LC End Date: 2013-07-18
> IESG Telechat date: 2013-07-18
>
> Note: This draft is on the IESG Telechat agenda on the same date as it completes IETF Last Call. Therefore, this review serves both purposes.
>
> Summary: This draft is almost ready for publication as a proposed standard. There are a few minor issues and editorial nits that should be considered prior to publication.
>
> Major issues:
>
> -- None
>
> Minor issues:
>
> -- Section 1, design considerations:
>
> You mention that the semantic results should survive round-tripping, but the order of fields might not. I gather there are other changes that might occur from the literal text, right? (e.g. Case changes, some optional parameter usage). If so, it might be worth clarifying that.
Yes, thanks. I've added the case changes since even though upper-case is 
RECOMMENDED in rfc6350, it is indeed information that is lost. Could you 
elaborate which optional parameters you mean? If you mean the GROUP 
parameter, this parameter is to be removed when converting back into 
vCard, so there is no change to the original group construct.

I neither found nor recall any other examples where it would be 
necessary to add anything.

>
> -- 3.1, 2nd paragraph:
>
> I assume the removal of escaping means that one renders the escaped text, not simply removes it, right? Is that as simple as removing the escape characters in vCards? I assume this doesn't apply to any content-specific escaping inside vCard fields, e.g. URI escaping, right? If so, it might be worth mentioning.
I agree "removed" isn't the best word, I wasn't really happy with the 
alternatives though, maybe "unescape" will work out (not sure if that is 
a real word?). If not, then I'd go with your "render", although to me 
that always suggests it is actually displayed. I'm happy for more 
suggestions though:

OLD:
           When converting from vCard to jCard, lines MUST be unfolded 
first.
           Afterwards, vCard escaping MUST be removed.  The only 
escaping that
           may be applied is any escaping mandated by JSON (e.g., for 
control
           characters).

           The reverse order applies when converting from jCard to 
vCard. First,
           JSON escaping MUST be removed. Afterwards, vCard escaping MUST be
           applied. Finally, long lines SHOULD be folded as described in 
[RFC6350].

NEW:

           When converting from vCard to jCard, lines MUST be unfolded 
first.
           Afterwards, vCard escaping MUST be unescaped. The only 
escaping that
           may be applied is any escaping mandated by JSON (e.g., for 
control
           characters) and any content-specific escaping inside vCard 
values,
           e.g. URI escaping.

           The reverse order applies when converting from jCard to 
vCard. First,
           JSON escaping MUST be unescaped. Afterwards, vCard escaping 
MUST be
           applied. Finally, long lines SHOULD be folded as described in 
[RFC6350].
> -- 3.2.1.1:
>
> What happens for future versions of vCard? Do you simply use the new version number, or would we need a new version of this spec? I suspect the latter. If true, it might be worth mentioning that, or somewhere early in the draft mention that this spec is for vCard 4.0 only.
I'd love to hear from the WG here, but given vCard 5.0 can at least in 
theory be completely different, I think the correct thing to do would be 
to restrict this jCard document to 4.x and when 5.x comes around create 
a revision of the document. Of course the text could be changed so that 
its "valid until revised by another document", in case the changes in 
5.x are minor enough that no change in jCard is needed.

In any case, there should be a text change that any 4.x revision is 
allowed. For example, I recently read a suggestion for signed vCards 
that might use a version "4.0s".
> -- sections 3.4.3 and 3.4.4:
>
> Is the included ABNF a quotation of that in the referenced RFCs, or is it new and authoritative? If the former, it would be helpful to mention that in the text. (I note you did say that about the ABNF in the appendix).
The ISO specs don't provide a direct BNF for any of their constructs. 
Instead they show examples in the form:
Basic format: YYYYMMDD Example: 19850412
Extended format: YYYY-MM-DD Example: 1985-04-12

The ABNF in jCard mimics this format, so it is not new, but given it 
matches I guess we could say its authoritative. Unless someone tells me 
otherwise (I'm still a bit uncertain when something can be called 
authoritative), I'll change it by changing the hangText "ABNF Schema:" 
to "ABNF Schema (authoritative):" in both sections.

> -- 3.4.11:
>
> If RFC6350 says that use of the timezone offset is NOT RECOMMENDED, can you elaborate on why it's included here? (I can guess it's because people may still use it in vCards since it was a "MUST NOT", but it would be good to say something to that effect in the text.)
There is no other vCard property that uses a utc-offset as a type, so 
this is just for the sake of an example. RFC6350 Section 6.5.1 has the 
details, it says utc-offset SHOULD NOT be used on a TZ property. The 
alternative would be to use an x-property for the example, i.e

["x-clock-offset", {}, "utc-offset", "-05:00"]

Do you think we should use this instead?

>
> Nits/editorial comments:
>
> -- Section 1, paragraph 1:
>
> Please expand JSON on first mention.
Doing this in the introduction since you reference Section 1, paragraph 
1. It already appears in the abstract, should I expand it there 
instead/in addition?

As the first mention uses "JSON-based", I've reworded these two paragraphs:

OLD:
    As certain similarities exist between vCard and the iCalendar data
    format [RFC5545], there is also an effort to define a JSON-based data
    format for calendar information called jCal [I-D.ietf-jcardcal-jcal]
    that parallels the format defined in this specification.

    The purpose of this specification is to define "jCard", a JSON format
    for vCard data.  One main advantage to using a JSON-based format as
    defined in [RFC4627] over the classic vCard format is easier
    processing for JavaScript based widgets and libraries, especially in
    the scope of web-based applications.

NEW:
    As certain similarities exist between vCard and the iCalendar data
    format [RFC5545], there is also an effort to define a JSON-based data
    format for calendar information called jCal [I-D.ietf-jcardcal-jcal]
    that parallels the format defined in this specification.  The term
    JSON describes the JavaScript Object Notation defined in [RFC4627].

    The purpose of this specification is to define "jCard", a JSON format
    for vCard data.  One main advantage to using a JSON-based format over
    the classic vCard format is easier processing for JavaScript based
    widgets and libraries, especially in the scope of web-based
    applications.


>
> -- Section 1, paragraph 3:
>
> This paragraph seems redundant to paragraph 1.
Yes, the duplicate is now removed. Sorry about that!
>
> -- 1, paragraph 7: " Preserve the semantics of the vCard data."
>
> Imperative form sentence is confusing in context, and inconsistent with surrounding text.
OLD:
       Preserve the semantics of the vCard data.  While a simple consumer
       can easily browse the data in jCard, a full understanding of vCard
       is still required in order to modify and/or fully comprehend the
       directory data.

NEW:
      The vCard data semantics are to be preserved, allowing a simple
       consumer to easily browse the data in jCard.  A full understanding
       of vCard is still required in order to modify and/or fully
       comprehend the directory data.

>
> -- 1, paragraph 8:
>
> Sentence Fragment.
The original intent was to make this a list of considerations, but as 
the first sentences are full I agree this makes it seem weird. How is 
this? I'm a little unsure about the "must not", but since this is just a 
consideration for the document and not an order for the consumer I think 
its ok with this casing:

OLD:
       Ability to handle many extensions to the underlying vCard
       specification without requiring an update to this document.
NEW:
       Extensions to the underlying vCard specification must not lead to
       requiring an update to jCard.

>
> -- 3.2, Last Paragraph: "... for a parser check the data type..."
>
> Missing "to"?
Done

>
> -- 3.2.1.2, last paragraph before example:
>
> Should the "iCalendar" reference be "vCard" instead?
Yes, copy/paste fail from jCal. Fixed.
> -- 3.2.1.3, Last Paragraph:
>
> RFCTODO? I gather in the IANA section, that may be a placeholder for "this RFC", but that doesn't seem to fit here.
My intention was to keep the registration template as general as 
possible, RFCTODO indeed references "this RFC", I've defined an entity 
for it in the source. Do you want me to replace it with "this document" 
instead? I was thinking if the registration template is maybe copied out 
of the document and gathered somewhere, it would make sense to reference 
the document by its rfc number.

> -- 3.3.2: "Example 1:"
>
> Other examples are not numbered.
Fixed

> -- 5:
>
> More occurrences of RFCTODO
Same reason, they appear in a registration template. I'm happy to 
replace with "this document" in case I'm told the registration template 
is never extracted from the document without any processing.

Thank you for the review!


--------------070106020800040203080502
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <div class="moz-cite-prefix">On 7/17/13 12:27 AM, Ben Campbell
      wrote:<br>
    </div>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<a class="moz-txt-link-rfc2396E" href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt; http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.

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

Document:  draft-ietf-jcardcal-jcard-04
Reviewer:  Ben Campbell
Review Date:  2013-07-16
IETF LC End Date: 2013-07-18
IESG Telechat date: 2013-07-18

Note: This draft is on the IESG Telechat agenda on the same date as it completes IETF Last Call. Therefore, this review serves both purposes.

Summary: This draft is almost ready for publication as a proposed standard. There are a few minor issues and editorial nits that should be considered prior to publication.

Major issues:

-- None

Minor issues:

-- Section 1, design considerations:

You mention that the semantic results should survive round-tripping, but the order of fields might not. I gather there are other changes that might occur from the literal text, right? (e.g. Case changes, some optional parameter usage). If so, it might be worth clarifying that.</pre>
    </blockquote>
    Yes, thanks. I've added the case changes since even though
    upper-case is RECOMMENDED in rfc6350, it is indeed information that
    is lost. Could you elaborate which optional parameters you mean? If
    you mean the GROUP parameter, this parameter is to be removed when
    converting back into vCard, so there is no change to the original
    group construct.<br>
    <br>
    I neither found nor recall any other examples where it would be
    necessary to add anything.<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- 3.1, 2nd paragraph:

I assume the removal of escaping means that one renders the escaped text, not simply removes it, right? Is that as simple as removing the escape characters in vCards? I assume this doesn't apply to any content-specific escaping inside vCard fields, e.g. URI escaping, right? If so, it might be worth mentioning.</pre>
    </blockquote>
    I agree "removed" isn't the best word, I wasn't really happy with
    the alternatives though, maybe "unescape" will work out (not sure if
    that is a real word?). If not, then I'd go with your "render",
    although to me that always suggests it is actually displayed. I'm
    happy for more suggestions though:<br>
    <br>
    OLD:<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When converting from vCard to jCard, lines MUST be
    unfolded first.<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Afterwards, vCard escaping MUST be removed.&nbsp; The only
    escaping that<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; may be applied is any escaping mandated by JSON (e.g., for
    control<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; characters).<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The reverse order applies when converting from jCard to
    vCard. First,<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JSON escaping MUST be removed. Afterwards, vCard escaping
    MUST be<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; applied. Finally, long lines SHOULD be folded as described
    in [RFC6350].<br>
    <br>
    NEW:<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; When converting from vCard to jCard, lines MUST be
    unfolded first.<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Afterwards, vCard escaping MUST be unescaped. The only
    escaping that<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; may be applied is any escaping mandated by JSON (e.g., for
    control<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; characters) and any content-specific escaping inside vCard
    values,<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; e.g. URI escaping.<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The reverse order applies when converting from jCard to
    vCard. First,<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JSON escaping MUST be unescaped. Afterwards, vCard
    escaping MUST be<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; applied. Finally, long lines SHOULD be folded as described
    in [RFC6350].<br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- 3.2.1.1:

What happens for future versions of vCard? Do you simply use the new version number, or would we need a new version of this spec? I suspect the latter. If true, it might be worth mentioning that, or somewhere early in the draft mention that this spec is for vCard 4.0 only.</pre>
    </blockquote>
    I'd love to hear from the WG here, but given vCard 5.0 can at least
    in theory be completely different, I think the correct thing to do
    would be to restrict this jCard document to 4.x and when 5.x comes
    around create a revision of the document. Of course the text could
    be changed so that its "valid until revised by another document", in
    case the changes in 5.x are minor enough that no change in jCard is
    needed.<br>
    <br>
    In any case, there should be a text change that any 4.x revision is
    allowed. For example, I recently read a suggestion for signed vCards
    that might use a version "4.0s".<br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- sections 3.4.3 and 3.4.4:

Is the included ABNF a quotation of that in the referenced RFCs, or is it new and authoritative? If the former, it would be helpful to mention that in the text. (I note you did say that about the ABNF in the appendix).</pre>
    </blockquote>
    The ISO specs don't provide a direct BNF for any of their
    constructs. Instead they show examples in the form:<br>
    <meta http-equiv="Content-Type" content="text/html;
      charset=ISO-8859-1">
    Basic format: YYYYMMDD Example: 19850412<br>
    Extended format: YYYY-MM-DD Example: 1985-04-12<br>
    <br>
    The ABNF in jCard mimics this format, so it is not new, but given it
    matches I guess we could say its authoritative. Unless someone tells
    me otherwise (I'm still a bit uncertain when something can be called
    authoritative), I'll change it by changing the hangText "ABNF
    Schema:" to "ABNF Schema (authoritative):" in both sections.<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- 3.4.11:

If RFC6350 says that use of the timezone offset is NOT RECOMMENDED, can you elaborate on why it's included here? (I can guess it's because people may still use it in vCards since it was a "MUST NOT", but it would be good to say something to that effect in the text.)</pre>
    </blockquote>
    There is no other vCard property that uses a utc-offset as a type,
    so this is just for the sake of an example. RFC6350 Section 6.5.1
    has the details, it says utc-offset SHOULD NOT be used on a TZ
    property. The alternative would be to use an x-property for the
    example, i.e<br>
    <br>
    ["x-clock-offset", {}, "utc-offset", "-05:00"]<br>
    <br>
    Do you think we should use this instead?<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

Nits/editorial comments:

-- Section 1, paragraph 1:

Please expand JSON on first mention.</pre>
    </blockquote>
    Doing this in the introduction since you reference Section 1,
    paragraph 1. It already appears in the abstract, should I expand it
    there instead/in addition?<br>
    <br>
    As the first mention uses "JSON-based", I've reworded these two
    paragraphs:<br>
    <br>
    OLD:<br>
    &nbsp;&nbsp; As certain similarities exist between vCard and the iCalendar
    data<br>
    &nbsp;&nbsp; format [RFC5545], there is also an effort to define a JSON-based
    data<br>
    &nbsp;&nbsp; format for calendar information called jCal
    [I-D.ietf-jcardcal-jcal]<br>
    &nbsp;&nbsp; that parallels the format defined in this specification.<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
    &nbsp;&nbsp; The purpose of this specification is to define "jCard", a JSON
    format<br>
    &nbsp;&nbsp; for vCard data.&nbsp; One main advantage to using a JSON-based format
    as<br>
    &nbsp;&nbsp; defined in [RFC4627] over the classic vCard format is easier<br>
    &nbsp;&nbsp; processing for JavaScript based widgets and libraries, especially
    in<br>
    &nbsp;&nbsp; the scope of web-based applications.<br>
    <br>
    NEW:<br>
    &nbsp;&nbsp; As certain similarities exist between vCard and the iCalendar
    data<br>
    &nbsp;&nbsp; format [RFC5545], there is also an effort to define a JSON-based
    data<br>
    &nbsp;&nbsp; format for calendar information called jCal
    [I-D.ietf-jcardcal-jcal]<br>
    &nbsp;&nbsp; that parallels the format defined in this specification.&nbsp; The
    term<br>
    &nbsp;&nbsp; JSON describes the JavaScript Object Notation defined in
    [RFC4627].<br>
    &nbsp;&nbsp; <br>
    &nbsp;&nbsp; The purpose of this specification is to define "jCard", a JSON
    format<br>
    &nbsp;&nbsp; for vCard data.&nbsp; One main advantage to using a JSON-based format
    over<br>
    &nbsp;&nbsp; the classic vCard format is easier processing for JavaScript
    based<br>
    &nbsp;&nbsp; widgets and libraries, especially in the scope of web-based<br>
    &nbsp;&nbsp; applications.<br>
    <br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- Section 1, paragraph 3:

This paragraph seems redundant to paragraph 1.</pre>
    </blockquote>
    Yes, the duplicate is now removed. Sorry about that!<br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- 1, paragraph 7: " Preserve the semantics of the vCard data."

Imperative form sentence is confusing in context, and inconsistent with surrounding text.</pre>
    </blockquote>
    OLD:<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Preserve the semantics of the vCard data.&nbsp; While a simple
    consumer<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; can easily browse the data in jCard, a full understanding of
    vCard<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is still required in order to modify and/or fully comprehend
    the<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; directory data.<br>
    <br>
    NEW:<br>
    &nbsp;&nbsp;&nbsp;&nbsp; The vCard data semantics are to be preserved, allowing a simple<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; consumer to easily browse the data in jCard.&nbsp; A full
    understanding<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of vCard is still required in order to modify and/or fully<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; comprehend the directory data.<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- 1, paragraph 8:

Sentence Fragment.</pre>
    </blockquote>
    The original intent was to make this a list of considerations, but
    as the first sentences are full I agree this makes it seem weird.
    How is this? I'm a little unsure about the "must not", but since
    this is just a consideration for the document and not an order for
    the consumer I think its ok with this casing:<br>
    <br>
    OLD:<br>
    &nbsp; &nbsp; &nbsp; Ability to handle many extensions to the underlying vCard<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; specification without requiring an update to this document.<br>
    NEW:<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Extensions to the underlying vCard specification must not lead
    to<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; requiring an update to jCard.<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- 3.2, Last Paragraph: "... for a parser check the data type..."

Missing "to"?</pre>
    </blockquote>
    Done<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">

-- 3.2.1.2, last paragraph before example:

Should the "iCalendar" reference be "vCard" instead?</pre>
    </blockquote>
    Yes, copy/paste fail from jCal. Fixed.<br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- 3.2.1.3, Last Paragraph:

RFCTODO? I gather in the IANA section, that may be a placeholder for "this RFC", but that doesn't seem to fit here.</pre>
    </blockquote>
    My intention was to keep the registration template as general as
    possible, RFCTODO indeed references "this RFC", I've defined an
    entity for it in the source. Do you want me to replace it with "this
    document" instead? I was thinking if the registration template is
    maybe copied out of the document and gathered somewhere, it would
    make sense to reference the document by its rfc number.<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- 3.3.2: "Example 1:"

Other examples are not numbered.</pre>
    </blockquote>
    Fixed<br>
    <br>
    <blockquote
      cite="mid:E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com"
      type="cite">
      <pre wrap="">-- 5:

More occurrences of RFCTODO</pre>
    </blockquote>
    Same reason, they appear in a registration template. I'm happy to
    replace with "this document" in case I'm told the registration
    template is never extracted from the document without any
    processing.<br>
    <br>
    Thank you for the review!<br>
    <br>
  </body>
</html>

--------------070106020800040203080502--

From jari.arkko@piuha.net  Mon Jul 22 08:45:41 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D323811E812C for <gen-art@ietfa.amsl.com>; Mon, 22 Jul 2013 08:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.469
X-Spam-Level: 
X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7DCj6A0MkGru for <gen-art@ietfa.amsl.com>; Mon, 22 Jul 2013 08:45:36 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 808CE11E80D9 for <gen-art@ietf.org>; Mon, 22 Jul 2013 08:45:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id CC7F12CC65 for <gen-art@ietf.org>; Mon, 22 Jul 2013 18:45:27 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gMBiQm18p61n for <gen-art@ietf.org>; Mon, 22 Jul 2013 18:45:22 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id DAB5F2CC61 for <gen-art@ietf.org>; Mon, 22 Jul 2013 18:45:22 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <71E534E9-DB65-4712-B4B5-A0A072D1CD84@piuha.net>
Date: Mon, 22 Jul 2013 18:45:22 +0300
To: "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Subject: [Gen-art] gen-art get-together in berlin?
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jul 2013 15:45:42 -0000

I am very happy about what the Gen-ART is doing - I now fully realise =
how important your service is, for both me personally and for the IETF. =
Thank you!

I'd love to get together with the team in Berlin, to discuss how the =
last few months have gone and innovate how we might work even better in =
the coming IETF cycle.

Scheduling is difficult, however. Here are some possible times, please =
fill out what would work for you:

http://www.sumpli.com/p.php?i=3D8caff01fbc18ab0

I hope you can figure out how to use sumpli, even if it is probably in =
Finnish even for you. If the times look odd, they should be these:=20

- Wednesday lunch (opposite to WG chair's training lunch)
- Wednesday evening session after plenary, with some refreshments (short =
session - you'd have time to go to dinner afterwards)
- Thursday breakfast (opposite to IAB meeting)
- Thursday lunch (opposite to syster's lunch)
- Thursday evening session with refreshments or dinner, after =
bits-n-bites

Jari


From simon.perreault@viagenie.ca  Mon Jul 22 09:14:22 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 066D721E80A7; Mon, 22 Jul 2013 09:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cn9vYbOHkSnZ; Mon, 22 Jul 2013 09:14:21 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 56A7C21E8099; Mon, 22 Jul 2013 09:14:21 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:245a:a34b:600:fe8b]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 324384712A; Mon, 22 Jul 2013 12:14:20 -0400 (EDT)
Message-ID: <51ED5A5A.2060702@viagenie.ca>
Date: Mon, 22 Jul 2013 18:14:18 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Philipp Kewisch <kewisch@gmail.com>
References: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com> <51ED1DAD.90904@gmail.com>
In-Reply-To: <51ED1DAD.90904@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, draft-ietf-jcardcal-jcard.all@tools.ietf.org, IETF-Discussion list <ietf@ietf.org>, "jcardcal@ietf.org" <jcardcal@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat Review of draft-ietf-jcardcal-jcard-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2013 16:14:22 -0000

Le 2013-07-22 13:55, Philipp Kewisch a 閏rit :
>> -- 3.2.1.1:
>>
>> What happens for future versions of vCard? Do you simply use the new version number, or would we need a new version of this spec? I suspect the latter. If true, it might be worth mentioning that, or somewhere early in the draft mention that this spec is for vCard 4.0 only.
> I'd love to hear from the WG here, but given vCard 5.0 can at least in
> theory be completely different, I think the correct thing to do would be
> to restrict this jCard document to 4.x and when 5.x comes around create
> a revision of the document. Of course the text could be changed so that
> its "valid until revised by another document", in case the changes in
> 5.x are minor enough that no change in jCard is needed.
> 
> In any case, there should be a text change that any 4.x revision is
> allowed. For example, I recently read a suggestion for signed vCards
> that might use a version "4.0s".

I'd prefer "valid until revised by another document", which is
equivalent to not saying anything since that's how RFCs work. Therefore,
my suggestion would be to simply remove this sentence: "Similarly, the
value of the version property MUST be "4.0"."

Simon

From dromasca@avaya.com  Mon Jul 22 10:11:47 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AAC811E811D for <gen-art@ietfa.amsl.com>; Mon, 22 Jul 2013 10:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101
X-Spam-Level: 
X-Spam-Status: No, score=-101 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YoitCSuWzG8V for <gen-art@ietfa.amsl.com>; Mon, 22 Jul 2013 10:11:41 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 5519121F8FF3 for <gen-art@ietf.org>; Mon, 22 Jul 2013 10:09:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvIHABNm7VGHCzI1/2dsb2JhbABBGoJlITVQrC2UBYEWFnSCJAEBAQEDAQEBDyg0GwIBCA0EBAEBCxQQJwsdCAIEARIIFAaHbgELM5tOm1kXj2U4gxBuA54jiweDEnqBMA
X-IronPort-AV: E=Sophos;i="4.89,720,1367985600"; d="scan'208";a="20522157"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 22 Jul 2013 13:09:29 -0400
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 22 Jul 2013 13:03:16 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0328.009; Mon, 22 Jul 2013 13:09:28 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Jari Arkko <jari.arkko@piuha.net>, "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Thread-Topic: [Gen-art] gen-art get-together in berlin?
Thread-Index: AQHOhvKHuNdNx8XFWUeKHwJhgDNXj5lw7hzc
Date: Mon, 22 Jul 2013 17:09:27 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA1287D61A@AZ-FFEXMB04.global.avaya.com>
References: <71E534E9-DB65-4712-B4B5-A0A072D1CD84@piuha.net>
In-Reply-To: <71E534E9-DB65-4712-B4B5-A0A072D1CD84@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [198.152.73.22]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Gen-art] gen-art get-together in berlin?
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jul 2013 17:11:47 -0000

Finnish is not a problem :-) but I do not know how to edit my row once ente=
red, as I realized that I made a mistake - my Thursday lunch slot is also b=
usy and I should have marked it with an X=0A=
=0A=
Regards,=0A=
=0A=
Dan=0A=
=0A=
________________________________________=0A=
From: gen-art-bounces@ietf.org [gen-art-bounces@ietf.org] on behalf of Jari=
 Arkko [jari.arkko@piuha.net]=0A=
Sent: Monday, July 22, 2013 6:45 PM=0A=
To: <gen-art@ietf.org> Team=0A=
Subject: [Gen-art] gen-art get-together in berlin?=0A=
=0A=
I am very happy about what the Gen-ART is doing - I now fully realise how i=
mportant your service is, for both me personally and for the IETF. Thank yo=
u!=0A=
=0A=
I'd love to get together with the team in Berlin, to discuss how the last f=
ew months have gone and innovate how we might work even better in the comin=
g IETF cycle.=0A=
=0A=
Scheduling is difficult, however. Here are some possible times, please fill=
 out what would work for you:=0A=
=0A=
http://www.sumpli.com/p.php?i=3D8caff01fbc18ab0=0A=
=0A=
I hope you can figure out how to use sumpli, even if it is probably in Finn=
ish even for you. If the times look odd, they should be these:=0A=
=0A=
- Wednesday lunch (opposite to WG chair's training lunch)=0A=
- Wednesday evening session after plenary, with some refreshments (short se=
ssion - you'd have time to go to dinner afterwards)=0A=
- Thursday breakfast (opposite to IAB meeting)=0A=
- Thursday lunch (opposite to syster's lunch)=0A=
- Thursday evening session with refreshments or dinner, after bits-n-bites=
=0A=
=0A=
Jari=0A=
=0A=
_______________________________________________=0A=
Gen-art mailing list=0A=
Gen-art@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/gen-art=0A=

From jari.arkko@piuha.net  Mon Jul 22 11:15:37 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F38FB11E811E for <gen-art@ietfa.amsl.com>; Mon, 22 Jul 2013 11:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HgBrU0CjZpQE for <gen-art@ietfa.amsl.com>; Mon, 22 Jul 2013 11:15:25 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 966BF11E811F for <gen-art@ietf.org>; Mon, 22 Jul 2013 11:15:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 70C5F2CC65; Mon, 22 Jul 2013 21:15:18 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EEGaVOwTI0Ro; Mon, 22 Jul 2013 21:15:17 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 004F12CC61; Mon, 22 Jul 2013 21:15:16 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA1287D61A@AZ-FFEXMB04.global.avaya.com>
Date: Mon, 22 Jul 2013 21:15:16 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BA20990-47C1-4FF8-A34E-A4AFECEC44A0@piuha.net>
References: <71E534E9-DB65-4712-B4B5-A0A072D1CD84@piuha.net> <9904FB1B0159DA42B0B887B7FA8119CA1287D61A@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1508)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] gen-art get-together in berlin?
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jul 2013 18:15:37 -0000

> Finnish is not a problem :-) but I do not know how to edit my row once =
entered, as I realized that I made a mistake - my Thursday lunch slot is =
also busy and I should have marked it with an X

I don't think there is an edit option, but I can take that into account. =
(Sumpli was my panic solution when I realised doodle was no longer =
easily accessible)

Jari



From ben@nostrum.com  Mon Jul 22 13:25:13 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF0C21F8447; Mon, 22 Jul 2013 13:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MRW1p7xIBRnO; Mon, 22 Jul 2013 13:25:12 -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 2A68E11E813A; Mon, 22 Jul 2013 13:25:06 -0700 (PDT)
Received: from [172.20.10.7] (mobile-166-147-070-058.mycingular.net [166.147.70.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6MKP0so066690 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 22 Jul 2013 15:25:00 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <51ED1DAD.90904@gmail.com>
Date: Mon, 22 Jul 2013 15:24:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A2C7748-D31C-46FA-BCD2-1CC6069F20A7@nostrum.com>
References: <E8A52EC5-BF67-4F5B-A810-0D69D01377AA@nostrum.com> <51ED1DAD.90904@gmail.com>
To: Philipp Kewisch <kewisch@gmail.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 166.147.70.58 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, draft-ietf-jcardcal-jcard.all@tools.ietf.org, IETF-Discussion list <ietf@ietf.org>, "jcardcal@ietf.org" <jcardcal@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat Review of draft-ietf-jcardcal-jcard-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2013 20:25:13 -0000

Thanks for the response. A few comments inline. I removed sections that =
don't seem to need further comment.

On Jul 22, 2013, at 6:55 AM, Philipp Kewisch <kewisch@gmail.com> wrote:

>=20
> On 7/17/13 12:27 AM, Ben Campbell wrote:

[...]

>> -- 3.2.1.1:
>>=20
>> What happens for future versions of vCard? Do you simply use the new =
version number, or would we need a new version of this spec? I suspect =
the latter. If true, it might be worth mentioning that, or somewhere =
early in the draft mention that this spec is for vCard 4.0 only.
>>=20
> I'd love to hear from the WG here, but given vCard 5.0 can at least in =
theory be completely different, I think the correct thing to do would be =
to restrict this jCard document to 4.x and when 5.x comes around create =
a revision of the document. Of course the text could be changed so that =
its "valid until revised by another document", in case the changes in =
5.x are minor enough that no change in jCard is needed.
>=20
> In any case, there should be a text change that any 4.x revision is =
allowed. For example, I recently read a suggestion for signed vCards =
that might use a version "4.0s".

Pending the opinions of the work group, I'm happy with that approach.

>> -- sections 3.4.3 and 3.4.4:
>>=20
>> Is the included ABNF a quotation of that in the referenced RFCs, or =
is it new and authoritative? If the former, it would be helpful to =
mention that in the text. (I note you did say that about the ABNF in the =
appendix).
>>=20
> The ISO specs don't provide a direct BNF for any of their constructs. =
Instead they show examples in the form:
> Basic format: YYYYMMDD Example: 19850412
> Extended format: YYYY-MM-DD Example: 1985-04-12
>=20
> The ABNF in jCard mimics this format, so it is not new, but given it =
matches I guess we could say its authoritative. Unless someone tells me =
otherwise (I'm still a bit uncertain when something can be called =
authoritative), I'll change it by changing the hangText "ABNF Schema:" =
to "ABNF Schema (authoritative):" in both sections.

By "authoritative", I don't mean anything particularly formal. It's =
really a matter of where the normative text lies. So, for someone =
implementing _this_ draft, would you expect them to look at the included =
ABNF only, or is it a case of the ABNF being here for convenience but a =
careful implementor should  also look at the ISO specs?


>=20
>> -- 3.4.11:
>>=20
>> If RFC6350 says that use of the timezone offset is NOT RECOMMENDED, =
can you elaborate on why it's included here? (I can guess it's because =
people may still use it in vCards since it was a "MUST NOT", but it =
would be good to say something to that effect in the text.)

oops, I think I meant to say "SHOULD NOT".

>>=20
> There is no other vCard property that uses a utc-offset as a type, so =
this is just for the sake of an example. RFC6350 Section 6.5.1 has the =
details, it says utc-offset SHOULD NOT be used on a TZ property. The =
alternative would be to use an x-property for the example, i.e
>=20
> ["x-clock-offset", {}, "utc-offset", "-05:00"]
>=20
> Do you think we should use this instead?

I don't have strong feelings either way, other than if you include a =
"NOT RECOMMENDED" example, it might be wise to put in a sentence or two =
giving the reasoning.

>=20
>>=20
>> Nits/editorial comments:
>>=20
>> -- Section 1, paragraph 1:
>>=20
>> Please expand JSON on first mention.
>>=20
> Doing this in the introduction since you reference Section 1, =
paragraph 1. It already appears in the abstract, should I expand it =
there instead/in addition?

I think the general approach is that the abstract doesn't "count" for =
this purpose. That is, if you separated the abstract and the body into =
two different documents, they should both still make sense.

>=20
> As the first mention uses "JSON-based", I've reworded these two =
paragraphs:
>=20
> OLD:
>    As certain similarities exist between vCard and the iCalendar data
>    format [RFC5545], there is also an effort to define a JSON-based =
data
>    format for calendar information called jCal =
[I-D.ietf-jcardcal-jcal]
>    that parallels the format defined in this specification.
>                      =20
>    The purpose of this specification is to define "jCard", a JSON =
format
>    for vCard data.  One main advantage to using a JSON-based format as
>    defined in [RFC4627] over the classic vCard format is easier
>    processing for JavaScript based widgets and libraries, especially =
in
>    the scope of web-based applications.
>=20
> NEW:
>    As certain similarities exist between vCard and the iCalendar data
>    format [RFC5545], there is also an effort to define a JSON-based =
data
>    format for calendar information called jCal =
[I-D.ietf-jcardcal-jcal]
>    that parallels the format defined in this specification.  The term
>    JSON describes the JavaScript Object Notation defined in [RFC4627].
>   =20
>    The purpose of this specification is to define "jCard", a JSON =
format
>    for vCard data.  One main advantage to using a JSON-based format =
over
>    the classic vCard format is easier processing for JavaScript based
>    widgets and libraries, especially in the scope of web-based
>    applications.

That works for me.

[...]

>=20
>>=20
>> -- 1, paragraph 8:
>>=20
>> Sentence Fragment.
>>=20
> The original intent was to make this a list of considerations, but as =
the first sentences are full I agree this makes it seem weird. How is =
this? I'm a little unsure about the "must not", but since this is just a =
consideration for the document and not an order for the consumer I think =
its ok with this casing:
>=20
> OLD:
>       Ability to handle many extensions to the underlying vCard
>       specification without requiring an update to this document.
> NEW:
>       Extensions to the underlying vCard specification must not lead =
to
>       requiring an update to jCard.
>=20

WFM.

[...]

>> -- 3.2.1.3, Last Paragraph:
>>=20
>> RFCTODO? I gather in the IANA section, that may be a placeholder for =
"this RFC", but that doesn't seem to fit here.
>>=20
> My intention was to keep the registration template as general as =
possible, RFCTODO indeed references "this RFC", I've defined an entity =
for it in the source. Do you want me to replace it with "this document" =
instead? I was thinking if the registration template is maybe copied out =
of the document and gathered somewhere, it would make sense to reference =
the document by its rfc number.

By registration template, you are talking about the use in the IANA =
Considerations, right? My comment was about its use in sections 3.2.1.3 =
and 5. I think it makes sense in the IANA considerations (perhaps with a =
note to the RFC Editor to replace it with the actual RFC number), but =
"this document" would make more sense in 3.2.1.3 and 5.

[...]=

From mahoney@nostrum.com  Tue Jul 23 14:38:30 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4643E21F9D56 for <gen-art@ietfa.amsl.com>; Tue, 23 Jul 2013 14:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44Qe8UMVH971 for <gen-art@ietfa.amsl.com>; Tue, 23 Jul 2013 14:38:29 -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 9319311E815E for <gen-art@ietf.org>; Tue, 23 Jul 2013 14:38:27 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6NLcQ8l042130 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Tue, 23 Jul 2013 16:38:26 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51EEF7CD.4020000@nostrum.com>
Date: Tue, 23 Jul 2013 16:38:21 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-07-23
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2013 21:38:30 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Roni Even         2013-08-16   draft-allen-dispatch-imei-urn-as-instanceid-10

Robert Sparks     2013-08-16   draft-montemurro-gsma-imei-urn-16

Russ Housley      2013-08-16   draft-nandakumar-rtcweb-stun-uri-05

Suresh Krishnan   2013-08-16   draft-petithuguenin-behave-turn-uris-05

Vijay Gurbani     2013-08-02   draft-ietf-geopriv-relative-location-06

Wassim Haddad     2013-08-02   draft-ietf-manet-nhdp-olsrv2-sec-03


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 Jul 25 08:39:06 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB2721F9A5F for <gen-art@ietfa.amsl.com>; Thu, 25 Jul 2013 08:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7pydKHwM9+5H for <gen-art@ietfa.amsl.com>; Thu, 25 Jul 2013 08:39:05 -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 8981721F9A33 for <gen-art@ietf.org>; Thu, 25 Jul 2013 08:39:04 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6PFd4r5033522 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 25 Jul 2013 10:39:04 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51F14693.4060602@nostrum.com>
Date: Thu, 25 Jul 2013 10:38:59 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: gen-art@ietf.org
References: <51EEF7CD.4020000@nostrum.com>
In-Reply-To: <51EEF7CD.4020000@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: Re: [Gen-art] A *new* batch of IETF LC reviews - 2013-07-23
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2013 15:39:06 -0000

Hi all,

I've reassigned draft-montemurro-gsma-imei-urn-16 to Alexey. Robert 
declined since he was too close to the draft.

Thanks,

Jean

On 7/23/13 4:38 PM, A. Jean Mahoney wrote:
> Hi all,
>
> The following reviewers have assignments:
>
> Reviewer          LC end       Draft
> ---------------------------------------------------------------------
> Roni Even         2013-08-16 
> draft-allen-dispatch-imei-urn-as-instanceid-10
>
> Robert Sparks     2013-08-16   draft-montemurro-gsma-imei-urn-16
>
> Russ Housley      2013-08-16   draft-nandakumar-rtcweb-stun-uri-05
>
> Suresh Krishnan   2013-08-16 draft-petithuguenin-behave-turn-uris-05
>
> Vijay Gurbani     2013-08-02 draft-ietf-geopriv-relative-location-06
>
> Wassim Haddad     2013-08-02   draft-ietf-manet-nhdp-olsrv2-sec-03
>
>
> 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:
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From housley@vigilsec.com  Fri Jul 26 01:32:57 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8575721F84E3; Fri, 26 Jul 2013 01:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5M6rWRBqOUit; Fri, 26 Jul 2013 01:32:52 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 4E76721F84B6; Fri, 26 Jul 2013 01:32:52 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 36F0DF240BA; Fri, 26 Jul 2013 04:33:12 -0400 (EDT)
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 D9Qp7BNORf2b; Fri, 26 Jul 2013 04:32:38 -0400 (EDT)
Received: from dhcp-5419.meeting.ietf.org (dhcp-5419.meeting.ietf.org [130.129.84.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id F2B35F2407E; Fri, 26 Jul 2013 04:33:09 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 26 Jul 2013 04:32:47 -0400
Message-Id: <20C00550-72F4-41F4-979C-ECFBD7B9D789@vigilsec.com>
To: draft-nandakumar-rtcweb-stun-uri.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART Telechat review of draft-nandakumar-rtcweb-stun-uri-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, 26 Jul 2013 08:32:57 -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-nandakumar-rtcweb-stun-uri-05
Reviewer: Russ Housley
Review Date: 26-July-2013
IETF LC End Date: 16-Auguest-2013
IESG Telechat date: Unknown

Summary: This draft is basically ready for publication as a Standards Track
RFC, but a few questions should be answered.

This document is the specification of the syntax and semantics of the
Uniform Resource Identifier (URI) scheme for the Session Traversal
Utilities for NAT (STUN) protocol.

Major issues:

None.

Minor issues:

This document defines ABNF for IPv4 and IPv6 addresses.  It seems better
to do these by reference.  


From Francis.Dupont@fdupont.fr  Fri Jul 26 06:25:59 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95F2221F9971 for <gen-art@ietfa.amsl.com>; Fri, 26 Jul 2013 06:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6goPmQEklhjV for <gen-art@ietfa.amsl.com>; Fri, 26 Jul 2013 06:25:59 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id DEC3221F9956 for <gen-art@ietf.org>; Fri, 26 Jul 2013 06:25:58 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r6QDPvHn028898; Fri, 26 Jul 2013 15:25:57 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201307261325.r6QDPvHn028898@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Fri, 26 Jul 2013 15:25:57 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-emu-crypto-bind.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-emu-crypto-bind-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jul 2013 13:25:59 -0000

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

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

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

Document: draft-ietf-emu-crypto-bind-04.txt
Reviewer: Francis Dupont
Review Date: 20130722
IETF LC End Date: 20130724
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - headers page 2: the keyword section is in the headers (vs the body).
  This is not the usual place... (BTW it is not the first time I do
  this comment so either the policy is different than I believe or
  there is a draft skeleton with this in it?)

 - Toc page 3 and 7 page 22: Acknowledgements -> Acknowledgments

 - 3.2.4 page 14: IMHO it should be fine to have an informational
  reference about EMSK (my idea is to help people to add it in design
  from the beginning).

 - 4.2 page 17: edition problem? in:

   should require mutual authentication be present in the session.

   to accomplish this, implementations including channel binding or

 - 5.2 page 19 (at the end of the line) EAp- -> EAP-

 - 5.2 page 19: my spell checker has a concern with "interoperably"

Thanks

Francis.Dupont@fdupont.fr

From gsalguei@cisco.com  Fri Jul 26 08:59:53 2013
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 B6A1A21F9A57 for <gen-art@ietfa.amsl.com>; Fri, 26 Jul 2013 08:59:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oRzLqKYarx5H for <gen-art@ietfa.amsl.com>; Fri, 26 Jul 2013 08:59:49 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFA121F99C5 for <gen-art@ietf.org>; Fri, 26 Jul 2013 08:59:49 -0700 (PDT)
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 r6QFxkDD004210 for <gen-art@ietf.org>; Fri, 26 Jul 2013 11:59:46 -0400 (EDT)
Received: from rtp-gsalguei-8915.cisco.com (rtp-gsalguei-8915.cisco.com [10.116.132.54]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6QFxjRt026992; Fri, 26 Jul 2013 11:59:45 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <20C00550-72F4-41F4-979C-ECFBD7B9D789@vigilsec.com>
Date: Fri, 26 Jul 2013 11:59:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA49ECB6-0F50-4C15-9EAB-A5019B00DD1C@cisco.com>
References: <20C00550-72F4-41F4-979C-ECFBD7B9D789@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org, ietf@ietf.org, draft-nandakumar-rtcweb-stun-uri.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-nandakumar-rtcweb-stun-uri-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, 26 Jul 2013 15:59:53 -0000

Hi Russ -=20

Thanks for the review.  My response is inline to your only review =
comment...

On Jul 26, 2013, at 4:32 AM, Russ Housley <housley@vigilsec.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 resolve these comments along with any other Last Call comments =
you
> may receive.
>=20
> Document: draft-nandakumar-rtcweb-stun-uri-05
> Reviewer: Russ Housley
> Review Date: 26-July-2013
> IETF LC End Date: 16-Auguest-2013
> IESG Telechat date: Unknown
>=20
> Summary: This draft is basically ready for publication as a Standards =
Track
> RFC, but a few questions should be answered.
>=20
> This document is the specification of the syntax and semantics of the
> Uniform Resource Identifier (URI) scheme for the Session Traversal
> Utilities for NAT (STUN) protocol.
>=20
> Major issues:
>=20
> None.
>=20
> Minor issues:
>=20
> This document defines ABNF for IPv4 and IPv6 addresses.  It seems =
better
> to do these by reference. =20

This document and draft-petithuguenin-behave-turn-uris are being =
progressed in parallel and share common elements. Duplicating the =
<IPv6address> and <IPv4address> ABNF production rules from RFC3986 is =
one of those common elements.  To provide you with a bit of background, =
this duplication was done intentionally and was done as a result of =
comments during uri-review of the original TURN URI draft back in 2009.  =
Here is the reference to the response to the relevant thread where this =
was decided:

https://www.ietf.org/mail-archive/web/behave/current/msg07380.html

Doing this knowingly spurred the addition of the Design Note you see =
here in the TURN URI draft:

=
http://tools.ietf.org/html/draft-petithuguenin-behave-turn-uris-05#appendi=
x-B

It was an oversight not to add that same Design Note to the STUN URI =
draft as well.  The next version will include an updated version of that =
Design Note with specific reference to the duplicated ABNF production =
rules (i.e., <IPv6address>, <IPv4address>, etc.).

Would that satisfactorily address your comment?

Cheers,

Gonzalo








From dbharrington@comcast.net  Sat Jul 27 06:27:39 2013
Return-Path: <dbharrington@comcast.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C18021F96D9 for <gen-art@ietfa.amsl.com>; Sat, 27 Jul 2013 06:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level: 
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[AWL=5.081,  BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8, TVD_SPACE_RATIO=2.219]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R9r8wupHu33X for <gen-art@ietfa.amsl.com>; Sat, 27 Jul 2013 06:27:33 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 32B9A21F9928 for <gen-art@ietf.org>; Sat, 27 Jul 2013 06:27:33 -0700 (PDT)
Received: by eikenes.alvestrand.no (Postfix) id 0E75239E947; Sat, 27 Jul 2013 15:27:32 +0200 (CEST)
Delivered-To: gen-art@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id B254A39E17B for <gen-art@alvestrand.no>; Sat, 27 Jul 2013 15:27:31 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F2iOwUXEGW0U for <gen-art@alvestrand.no>; Sat, 27 Jul 2013 15:27:26 +0200 (CEST)
X-Greylist: delayed 00:08:10 by SQLgrey-1.6.8
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by eikenes.alvestrand.no (Postfix) with ESMTP id A5A5C39E13F for <gen-art@alvestrand.no>; Sat, 27 Jul 2013 15:27:25 +0200 (CEST)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta07.westchester.pa.mail.comcast.net with comcast id 5Qn91m0020vyq2s57RKEyA; Sat, 27 Jul 2013 13:19:14 +0000
Received: from sz0047.wc.mail.comcast.net ([68.87.26.137]) by omta05.westchester.pa.mail.comcast.net with comcast id 5RKD1m00z2xV5no3RRKDLG; Sat, 27 Jul 2013 13:19:14 +0000
Date: Sat, 27 Jul 2013 13:19:13 +0000 (UTC)
From: dbharrington@comcast.net
To: mpennin@cvps.com, dmitton@nortelnetworks.com, agray@exeter.edu,  greg.daley@eng.monash.edu.au, rrs@lakerest.net,  dperkins@dsperkins.com, melmojw@verizon.net, gen-art@alvestrand.no,  clonvick@cisco.com, encrypted@ietf.org, ahagens@amsl.com,  verozheng@huawei.com, pras@ctit.utwente.nl,  dean.willis@softarmor.com, kdonaghe@twcny.rr.com
Message-ID: <1263504382.1867252.1374931153841.JavaMail.root@sz0047a.westchester.pa.mail.comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [::ffff:113.169.164.242]
X-Mailer: Zimbra 6.0.13_GA_2944 (zclient/6.0.13_GA_2944)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1374931154; bh=jXk0sgUCosqjlulkD1KpjABiX9akr1WpWh1MuafsWZQ=; h=Received:Received:Date:From:To:Message-ID:Subject:MIME-Version: Content-Type; b=D9jSXLC6IC18RCzDP1G4LASQX1+opfyXxeVvomChMqqyLNS6tyzFVk4WXVQkIRwON V+9+9yvSvqX7mfufOtmmgA3dizIvwIQ9jmHYHOwPam8OxRR12pNMV7kjoFeeNQO9LN 8kjpnaoSwhHgVZpyUSGzeDuQn7gDdMbsgCWtuCBkqS4Ehb3H6TJpPSlNTRjndW4BpC Dk/0d0CdzuKKmUW/3kG2+LOeIcQTgLVyR0zY5v4krR2J16qm10rLWRHyxGFaBE0O/D gAo0xBZcStYCn/pVuzkKoaQq0S1ZD5u5+yfpmJQJSNM6NRxskFi40eMeGsPYn4zInY 9X5GA8R7l37OQ==
Subject: Re: [Gen-art] 2
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 27 Jul 2013 13:27:39 -0000

http://whaouh.com/www.cnnnews.com.replynews.index68.php?aolID=41x

From mahoney@nostrum.com  Sat Jul 27 09:11:09 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6970A21F9BB6 for <gen-art@ietfa.amsl.com>; Sat, 27 Jul 2013 09:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RyUrwiO8YC7X for <gen-art@ietfa.amsl.com>; Sat, 27 Jul 2013 09:11:08 -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 376E821F9B8F for <gen-art@ietf.org>; Sat, 27 Jul 2013 09:10:58 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6RGAuFs064948 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Sat, 27 Jul 2013 11:10:56 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51F3F10B.6010107@nostrum.com>
Date: Sat, 27 Jul 2013 11:10:51 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: gen-art@ietf.org
References: <14DA6A90-2B0A-48D1-8B16-73DEA87AD17D@piuha.net>
In-Reply-To: <14DA6A90-2B0A-48D1-8B16-73DEA87AD17D@piuha.net>
X-Forwarded-Message-Id: <14DA6A90-2B0A-48D1-8B16-73DEA87AD17D@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] Fwd: Re: tail-heavy process and early directorate reviews
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 27 Jul 2013 16:11:09 -0000

Hi all,

We are moving forward with the early review experiment. For Gen-ART, an 
early review will replace the LC review, so a reviewer that is assigned 
an early review will perform the early review and the telechat review.

I will be monitoring the dir-coord mailing list and assigning reviews as 
necessary.

Check the email below for details.

Thanks!

Jean

-------- Original Message --------
Subject: 	Re: tail-heavy process and early directorate reviews
Date: 	Fri, 26 Jul 2013 20:35:03 +0300
From: 	Jari Arkko <jari.arkko@piuha.net>
To: 	Barry Leiba <barryleiba@computer.org>, Pete Resnick 
<presnick@qti.qualcomm.com>, Stephen Farrell <mahoney@nostrum.com>, Sean 
Turner <turners@ieca.com>, joel jaeggli <joelja@bogus.com>, Benoit 
Claise <bclaise@cisco.com>, "A. Jean Mahoney" <mahoney@nostrum.com>, 
Tero Kivinen <kivinen@iki.fi>, Claudio Allocchio 
<Claudio.Allocchio@garr.it>



Ok. So by now you should have seen that you've become a member of the 
dir-coord list (we changed the name). We've left TSV and OPS directorate 
coordinators out for now.

So here's the plan on how this will work. Please comment.

Internet Drafts sent for approval as RFCs are reviewed by individuals 
during the IETF Last Call, the Area Directors, IANA, as well as a number 
of volunteers in various directorates and review teams. The reviews from 
these teams has gained a significant role in ensuring that the IETF 
produces high-quality, understandable and implementable RFCs.

Yet, as discussed in 
http://www.ietf.org/blog/2013/05/balancing-the-process/ we have a 
general problem that quite a lot of the work around IETF documents 
happens at the end of the process. In particular, a number of the 
reviews during IETF last call point out issues that end up being raised 
by the IESG as comments when deciding for the final approval of the 
document. It is of course good that issues are caught, but raising them 
earlier would be better. And it would be better if the working groups - 
the intended focus point of work on a topic - would get to handle them, 
as opposed to raising these issues with the IESG. The IESG discussed 
these issues in its May 2013 retreat, and decided to experiment with 
three actions designed to move more work to the responsibility of the 
working groups:

(1) Perform some reviews that are now happening at IETF Last Call a bit 
earlier.
(2) Invite document shepherds on IESG telechats when there's a document 
that is likely to require discussion.
(3) When a document has a number of issues, hand over the process back 
to the working group, as opposed to the IESG tracking the issues. Among 
other things, this will ensure that changes are discussed in an open 
working group list and agreed through consensus.

Building quality and cross-area review to the process earlier is of 
course a big effort. For the first item above, we are launching an 
experiment to make a small change to current directorate review 
procedures to learn if we can move reviews a little bit earlier. If 
successful, this experiment will enable working groups to deal with 
issues before IETF Last Call and IESG review and empower the working 
groups to be in charge of the documents throughout their life cycle. We 
are also hoping that document quality will improve and number of issues 
discussed in the IESG will be lower.

While the number of reviews as such is not changed, some additional 
effort and care will however be required from the reviewers, directorate 
coordinators/secretaries, the working group chairs, and other 
participants. The experiment will show us whether this effort is 
reasonable and if there are any unexpected effects. The experiment is 
performed on a voluntary basis by each directorate. As early review 
requests come in, the directorates can throttle workload by either 
processing the requests or reverting to the existing procedures. 
Initially, the Gen-ART, Security Directorate, and Applications Area 
Directorate are included in this effort. Other directorates may be added 
later. The experiment will be reviewed after six months.

Care must be taken to avoid a number of possible drawbacks. There may be 
problematic documents that would require much re-review and effort. 
Similarly, working groups often perform a number of working group last 
calls on a document, and it would be undesirable to engage the reviewer 
before the document was really ready to be sent forward. And when 
reviewers send comments, it is important that the group listens to the 
comments in the right way, like you would for a review from a security 
expert or a general networking expert. E-mail practices around sending 
and responding to comments have to be carefully managed, as the outside 
reviewers are typically not list members.

For the *working group chairs*, you can request a review by sending mail 
to dir-coord@ietf.org <mailto:dir-coord@ietf.org>, indicating the name 
of the document. You can ask for a review as soon as a working group 
last call has ended successfully and the document edits are done. 
Initially, it would make sense to ask for reviews on documents that you 
feel are likely the most stable ones. To avoid congesting the reviewer 
resources, ask for this service only for some documents, not as a 
wholesale service on every document you submit for publication.

You can ask for the review in parallel with ongoing AD reviews, filling 
out the shepherd questionnaire, etc. The hope is that reviews can come 
in in the same time frame as other tasks in this stage, and that you can 
take the comments into account and revise the document before finally 
sending it out for IETF Last Call. Reviews will be sent to you and 
potentially the working group mailing list. You may need to forward 
comments and/or approve new posters to the list. Discussion on the 
mailing list is encouraged, but please try to ensure that the reviewer 
is kept on the Cc line, as he or she may not be on the list itself. 
Treat the reviews with respect and keep it in mind that outside experts 
may have opinions that need to be taken into account, even if the 
working group had not considered those aspects before. Mediate and 
monitor the discussion actively. Try to keep the reviewer out of e-mail 
storms and work out solutions separately and then engage the reviewer again.

For the *directorate coordinators/secretaries*, please monitor the 
dir-coord@ietf.list <mailto:dir-coord@ietf.list>. If there is a request 
for a review, dispatch the task to a reviewer. Managing overload is your 
task. Please acknowledge requests and whether you can accommodate them. 
Directorates that today review documents twice, at IETF Last Call and 
then before entering the IESG telechat should continue this practice by 
doing the early review and then the IESG telechat review. Existing 
practices such as retaining the same reviewer for checking the same 
version is useful. Your review tools and practices may need adjustment 
to accommodate reviews happening at different times.

For the *reviewers*, take into account the context. Post your reviews to 
the working group chairs, authors, and Cc the working group mailing list 
if necessary. If your review team uses a template for these e-mails, 
some changes may be necessary in the template for the early review. Some 
of those changes have been discussed, e.g., in the Gen-ART list.

For everyone, please collect your experiences so that in six months we 
can evaluate how you liked the experience. And thank you for your 
participation in this effort!

Jari




From david.black@emc.com  Mon Jul 29 04:21:21 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12CA221F9AE9; Mon, 29 Jul 2013 04:21:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kk-qraJTTc-f; Mon, 29 Jul 2013 04:21:16 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 858EC21F9FE5; Mon, 29 Jul 2013 04:21:03 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6TBKZjf015737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Jul 2013 07:20:36 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 29 Jul 2013 07:20:13 -0400
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6TBKClG027092; Mon, 29 Jul 2013 07:20:12 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Mon, 29 Jul 2013 07:20:12 -0400
From: "Black, David" <david.black@emc.com>
To: "ldunbar@huawei.com" <ldunbar@huawei.com>, Donald Eastlake <d3e3e3@gmail.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>, General Area Review Team <gen-art@ietf.org>
Date: Mon, 29 Jul 2013 07:20:10 -0400
Thread-Topic: Gen-ART review of draft-ietf-trill-directory-framework-06
Thread-Index: Ac6MTZacq8P2IvAoQlCH2H5lCCeKDA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712984AD61D@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: Ted Lemon <Ted.Lemon@nominum.com>, "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-directory-framework-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, 29 Jul 2013 11:21:21 -0000

The -06 version of this draft resolves all of the concerns raised by the Ge=
n-ART
review of the -05 version - the -06 version is ready for publication as an
Informational RFC.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Wednesday, July 17, 2013 7:54 PM
> To: ldunbar@huawei.com; Donald Eastlake; Radia@alum.mit.edu; igor@yahoo-
> inc.com; General Area Review Team
> Cc: trill@ietf.org; ietf@ietf.org; Black, David; Ted Lemon
> Subject: Gen-ART review of draft-ietf-trill-directory-framework-05
>=20
> Document: draft-ietf-trill-directory-framework-05
> Reviewer: David L. Black
> Review Date: July 17, 2013
> IETF LC End Date: July 18, 2013
>=20
> Summary:
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> This draft describes a framework for using directory servers to provide
> address mappings (address -> destination RBridge) to TRILL Rbridges as an
> alternative to data plane learning and use of the TRILL ESADI protocol.
>=20
> The draft's generally well written and clear.  I found a couple of minor
> issues.
>=20
> Major issues: None.
>=20
> Minor issues:
>=20
> [1] The last bullet in Section 3.1 says:
>=20
>        - In an environment where VMs migrate, there is a higher chance
>          of cached information becoming invalid, causing traffic to be
>          black-holed by the ingress RBridge, that is, persistently sent
>          to the wrong egress RBridge. If VMs do not flood gratuitous
>          ARP/ND or VDP [802.1Qbg] messages upon arriving at new
>          locations, the ingress nodes might not have MAC entries for the
>          MAC of the newly arrived VMs, causing unknown address flooding.
>=20
> This is incorrect in multiple ways and should just be removed:
>=20
> - Persistent black-holing is rare in practice because all common
> 	VM migration implementations issue the gratuitous messages.
> - VMs don't send the gratuitous messages, hypervisors do.
> - VDP is not flooded.  The receiver's always a bridge.
> - At least one common VM migration implementation actually uses a gratuit=
ous
> 	RARP, not ARP.
> - Flooding is done by the bridges and Rbridges, not the VMs.
>=20
> [2] There are some unfortunate notation problems in Section 5.1 that carr=
y
> into the following sections, based on the logical data structure:
>=20
>    [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
>    interested RBridges}]
>=20
> - The first open curly brace ('{') is unmatched.
> - Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
> 	none of which appear in that structure.
>=20
> Nits/editorial comments:
>=20
> Section 1 - item 1 in the numbered list does not explain why it makes
> a directory approach attractive.  This should be added, as it is
> present for the other three items .
>=20
> Section 2 - Say that IS-IS is a routing protocol.
> The definition of Station should say that the node or virtual node
> is on a network.  Also, please define or explain "virtual node".
>=20
> Section 3.2 - Add the number of entries to be learned to scenario #1
> in order to parallel the scenario # 2 discussion.
>=20
> Section 4 - remove "(distributed model)" from first paragraph,
> as it's not explained.
>=20
> Section 5.3, top of p.13:
>=20
>    therefore, there needs to be some mechanism by which RBridges that
>    have pulled information that has not expired can be informed when
>    that information changes or the like.
>=20
> "or the like" is vague.  I suggest "or becomes invalid for other
>  reasons".
>=20
> idnits 2.12.17 didn't find any nits that need attention.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From martin.thomson@gmail.com  Tue Jul 30 00:06:02 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC76B11E81BF; Tue, 30 Jul 2013 00:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.334
X-Spam-Level: 
X-Spam-Status: No, score=-2.334 tagged_above=-999 required=5 tests=[AWL=0.266,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aefqv8tQrsiD; Tue, 30 Jul 2013 00:06:00 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0300321F9F95; Tue, 30 Jul 2013 00:05:59 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id q58so4645651wes.6 for <multiple recipients>; Tue, 30 Jul 2013 00:05:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=bw7Y0TNniuJeks+sb5supEjOm5jrL8zlnECBAMyN220=; b=OQoLveVoq/VF+LrpVQgE9kLqCkWcTrr9OzK2LLM+Evk9fopK4ZIwRXPIrm7HRNSxaW KcX7YFD8H2FTrluhAn3zsmAWklqaR2gXhHGH4TuqXB3OqisKDLRnYuWmt/Ppex5+QReJ fntNXqaNj8+F1PMFftRXmxcTDjxXgmfz/0w8UOOsc+MCfoeYsd9PZKQ8oNDRJYdKUqG4 zN2lF2FrnY2SH1nSiXuSYz5o0CD4nxVfU81mOnM5WPtZito/F8mjepMGdZrKncud/2N9 6rCx+4W93VHjS4c+A4iRnFyYNwyOMAa89p9pepvW92OdCPDJRvwoi99SMNm8Q8VhbPnM 4yvg==
MIME-Version: 1.0
X-Received: by 10.180.73.68 with SMTP id j4mr88869wiv.10.1375167959113; Tue, 30 Jul 2013 00:05:59 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Tue, 30 Jul 2013 00:05:59 -0700 (PDT)
Date: Tue, 30 Jul 2013 00:05:59 -0700
Message-ID: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-bormann-cbor-04.all@tools.ietf.org,  IETF Apps Discuss <apps-discuss@ietf.org>
Content-Type: text/plain; charset=UTF-8
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-bormann-cbor-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 07:06:02 -0000

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

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

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

Document: draft-bormann-cbor-04
Reviewer: Martin Thomson
Review Date: 2013-07-29
IETF LC End Date: ?
IESG Telechat date: 2013-08-15

Summary:
This document is not ready for publication as proposed standard.

I'm glad that I held this review until Paul's appsarea presentation.
This made it very clear to me that the types of concerns I have are
considered basically irrelevant by the authors because they aren't
interested in changing the design goals.  I don't find the specific
design goals to be interesting and am of the opinion that the goals
are significant as a matter of general application.  I hope that is
clear from my review.

Independent of any conclusions regarding design goals, there are
issues that need addressing.

(This is an atypical Gen-ART review.  I make no apologies for that.  I
didn't intend to write a review like this when I started, but feel
that it's important to commit these thoughts to the record.  It's also
somewhat long, sorry.  I tried to edit it down.)

I have reviewed the mailing list feedback, and it's not clear to me
that there is consensus to publish this.  It might be that the dissent
that I have observed is not significant in Barry's learned judgment,
or that this is merely dissent on design goals and therefore
irrelevant.  The fact that this work isn't a product of a working
group still concerns me.  I'm actually interested in why this is
AD-sponsored rather than a working group product.

Major issues:
My major concerns with this document might be viewed as disagreements
with particular design choices.  And, I consider it likely that the
authors will conclude that the document is still worth publishing as
is, or perhaps with some minor changes.  In the end, I have no issue
with that, but expect that the end result will be that the resulting
RFC is ignored.

What would cause this to be tragic, is if publication of this were
used to prevent other work in this area from subsequently being
published.  (For those drawing less-than-charitable inferences from
this, I have no desire to throw my hat into this particular ring,
except perhaps in jest [1].)

This design is far too complex and large.  Regardless of how
well-considered it might be, or how well this meets the stated design
goals, I can't see anything but failure in this document's future.
JSON succeeds largely because it doesn't attempt to address so many
needs at once, but I could even make a case for why JSON contains too
many features.

In comparison with JSON, this document does one major thing wrong: it
has more options than JSON in several dimensions.  There are more
types, there are several more dimensions for extensibility than JSON:
types extensions, values extensions (values of 28-30 in the lower bits
of the type byte), plus the ability to apply arbitrary tags to any
value.  I believe all of these to be major problems that will cause
them to be ignored, poorly implemented, and therefore useless.

In part, this complexity produces implementations that are far more
complex than they might need to be, unless additional standardization
is undertaken.  That idea is something I'm uncomfortable with.

Design issue: extensibility:
This document avoids discussion of issues regarding schema-less
document formats that I believe to be fundamental.  These issues are
critical when considering the creation of a new interchange format.
By choosing this specific design it makes a number of trade-offs that
in my opinion are ill-chosen.  This may be in part because the
document is unclear about how applications intend to use the documents
it describes.

You may conclude after reading this review that this is simply because
the document does not explain the rationale for selecting the approach
it takes.  I hope that isn't the conclusion you reach, but appreciate
the reasons why you might do so.

I believe the fundamental problem to be one that arises from a
misunderstanding about what it means to have no schema.  Aside from
formats that require detailed contextual knowledge to interpret, there
are several steps toward the impossible, platonic ideal of a perfectly
self-describing format.  It's impossible because ultimately the entity
that consumes the data is required at some level to understand the
semantics that are being conveyed.  In practice, no generic format can
effectively self-describe to the level of semantics.

This draft describes a format that is more capable at self-description
than JSON.  I believe that to not just be unnecessary, but
counterproductive.  At best, it might provide implementations with a
way to avoid an occasional extra line of code for type conversion.

Extensibility as it relates to types:
The use of extensive typing in CBOR implies an assumption of a major
role for generic processing.  XML schema and XQuery demonstrate that
this desire is not new, but they also demonstrate the folly of
pursuing those goals.

JSON relies on a single mechanism for extensibility. JSON maps that
contain unknown or unsupported keys are (usually) ignored.  This
allows new values to be added to documents without destroying the
ability of an old processor to extract the values that it supports.
The limited type information JSON carries leaks out, but it's unclear
what value this has to a generic processor.  All of the generic uses
I've seen merely carry that type information, no specific use is made
of the knowledge it provides.

ASN.1 extensibility, as encoded in PER, leads to no type information
leaking.  Unsupported extensions are skipped based on a length field.

(As an aside, PER is omitted from the analysis in the appendix, which
I note from the mailing lists is due to its dependency on schema.
Interestingly, I believe it to be possible - though not trivial - to
create an ASN.1 description with all the properties described in CBOR
that would have roughly equivalent, if not fully equivalent,
properties to CBOR when serialized.)

By defining an extensibility scheme for types, CBOR effectively
acknowledges that a generic processor doesn't need type information
(just delineation information), but it then creates an extensive type
system.  That seems wasteful.

Design issue: types:
The addition of the ability to carry uninterpreted binary data is a
valuable and important feature.  If that was all this document did,
then that might have been enough.  But instead it adds numerous
different types.

I can understand why multiple integer encoding sizes are desirable,
and maybe even floating point representations, but this describes
bignums in both base 2 and 10, embedded CBOR documents in three forms,
URIs, base64 encoded strings, regexes, MIME bodies, date and times in
two different forms, and potentially more.

I also challenge the assertion made where the code required for
parsing a data type produces larger code sizes if performed outside of
a common shared library.  That's arguably provably true, but last time
I checked a few extra procedure calls (or equivalent) weren't the
issue for code size.  Sheer number of options on the other hand might
be.

Half-precision floating point numbers are a good example of excessive
exuberance.  They are not available in many languages for good reason:
they aren't good for much.  They actually tend to cause errors in
software in the same way that threading libraries do: it's not that
it's hard to use them, it's that it's harder than people think.  And
requiring that implementations parse these creates unnecessary
complexity.  I do not believe that for the very small subset of cases
where half precision is actually useful, the cost of transmitting the
extra 2 bytes of a single-precision number is not going to be a
burden.  However, the cost of carrying the code required to decode
them is not as trivial as this makes out.  The fact that this requires
an appendix would seem to indicate that this is special enough that
inclusion should have been very carefully considered.  To be honest,
if it were my choice, I would have excluded single-precision floating
point numbers as well, they too create more trouble than they are
worth.

Design issue: optionality
CBOR embraces the idea that support for types is optional.  Given the
extensive nature of the type system, it's almost certain that
implementations will choose to avoid implementation of some subset of
the types.  The document makes no statements about what types are
mandatory for implementations, so I'm not sure how it is possible to
provide interoperable implementations.

If published in its current form, I predict that only a small subset
of types will be implemented and become interoperable.

Design issue: tagging
The tagging feature has a wonderful property: the ability to create
emergency complexity.  Given that a tag itself can be arbitrarily
complex, I'm almost certain that this is a feature you do not want.

Minor issues:
Design issue: negative numbers
Obviously, the authors will be well-prepared for arguments that
describe as silly the separation of integer types into distinct
positive and negative types.  But it's true, this is a strange choice,
and a very strange design.

The fact that this format is capable of describing 64-bit negative
numbers creates a problem for implementations that I'm surprised
hasn't been raised already.  In most languages I use, there is no
native type that is capable of carrying the most negative value that
can be expressed in this format.  -2^64 is twice as large as a 64-bit
twos-complement integer can store.

It almost looks as though CBOR is defining a 65-bit, 33-bit or 17-bit
twos complement integer format, with the most significant bit isolated
from the others, except that the negative expression doesn't even have
the good sense to be properly sortable.  Given that and the fact that
bignums are also defined, I find this choice to be baffling.

Document issue: Canonicalization
Please remove Section 3.6.  c14n is hard, and this format actually
makes it impossible to standardize a c14n scheme, that says a lot
about it.  In comparison, JSON is almost trivial to canonicalize.

If the intent of this section is to describe some of the possible
gotchas, such as those described in the last paragraph, then that
would be good.  Changing the focus to "Canonicalization
Considerations" might help.

I believe that there are several issues that this section would still
need to consider.  For instance, the use of the types that contain
additional JSON encoding hints carry additional semantics that might
not be significant to the application protocol.

Extension based on minor values 28-30 (the "additional information" space):
...is impossible as defined.  Section 5.1 seems to imply otherwise.
I'm not sure how that would ever happen without breaking existing
parsers.  Section 5.2 actually makes this worse by making a
wishy-washy commitment to size for 28 and 29, but no commitment at all
for 30.

Nits:
Section 3.7 uses the terms "well-formed" and "valid" in a sense that I
believe to be consistent with their use in XML and XML Schema.  I
found the definition of "valid" to be a little difficult to parse;
specifically, it's not clear whether invalid is the logical inverse of
valid.

Appendix B/Table 4 has a TBD on it.  Can this be checked?

Table 4 keeps getting forward references, but it's hidden in an
appendix.  I found that frustrating as a reader because the forward
references imply that there is something important there.  And that
implication was completely right, this needs promotion.  I know why
it's hidden, but that reason just supports my earlier theses.

Section 5.1 says "An IANA registry is appropriate here.".  Why not
reference Section 7.1?

[1] https://github.com/martinthomson/aweson

From martin.thomson@gmail.com  Tue Jul 30 00:07:44 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9996B21E80BB; Tue, 30 Jul 2013 00:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.249,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OSgQw-c6cfR4; Tue, 30 Jul 2013 00:07:42 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 83F8F11E81B9; Tue, 30 Jul 2013 00:07:41 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w60so4824385wes.29 for <multiple recipients>; Tue, 30 Jul 2013 00:07:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=biVXeFJONYzMNQcTFLeavVEkNqNQHbEr+BScZ9cEk14=; b=ATnlJ+qtrfW9gQx1OLm02ptUU7XjDWYJDpFVxOVUPyfEimt0MnGF5UISo2M/xdT4TY P1USSPOZfR6h0er40N6hctrh/zV6dUhPRD2ImFN7z2Mbp56/Pkv6u7VXOv4N0sP3HI5g poGkELXzADE4OqALKYf+e4afa5VulBrg0SdepbghR+oE4tQSKMPpNo+Zqv1TVi/jAQL5 kB7uErravFPHAnn0PvKKAFXmH/xkXGSD1F3+DTIpSXZ5I/5mcd3lG06+vbTD/MADG1J8 oCPrd6EYTZskQUXsGLwGIsVWwJ+PfBrXEkADWdh1vaS/X4gZKvBly0K64ao7OKWX67FV FBww==
MIME-Version: 1.0
X-Received: by 10.194.78.110 with SMTP id a14mr45581698wjx.84.1375168060668; Tue, 30 Jul 2013 00:07:40 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Tue, 30 Jul 2013 00:07:40 -0700 (PDT)
In-Reply-To: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com>
Date: Tue, 30 Jul 2013 00:07:40 -0700
Message-ID: <CABkgnnV7BG7Be8kCBPsyCqM0AudwSPR2ok1g=qpB0pJqC0Obtg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: IETF Apps Discuss <apps-discuss@ietf.org>, draft-bormann-cbor.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-bormann-cbor-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 07:07:44 -0000

Adding draft-relevant recipients.

On 30 July 2013 00:05, 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-bormann-cbor-04
> Reviewer: Martin Thomson
> Review Date: 2013-07-29
> IETF LC End Date: ?
> IESG Telechat date: 2013-08-15
>
> Summary:
> This document is not ready for publication as proposed standard.
>
> I'm glad that I held this review until Paul's appsarea presentation.
> This made it very clear to me that the types of concerns I have are
> considered basically irrelevant by the authors because they aren't
> interested in changing the design goals.  I don't find the specific
> design goals to be interesting and am of the opinion that the goals
> are significant as a matter of general application.  I hope that is
> clear from my review.
>
> Independent of any conclusions regarding design goals, there are
> issues that need addressing.
>
> (This is an atypical Gen-ART review.  I make no apologies for that.  I
> didn't intend to write a review like this when I started, but feel
> that it's important to commit these thoughts to the record.  It's also
> somewhat long, sorry.  I tried to edit it down.)
>
> I have reviewed the mailing list feedback, and it's not clear to me
> that there is consensus to publish this.  It might be that the dissent
> that I have observed is not significant in Barry's learned judgment,
> or that this is merely dissent on design goals and therefore
> irrelevant.  The fact that this work isn't a product of a working
> group still concerns me.  I'm actually interested in why this is
> AD-sponsored rather than a working group product.
>
> Major issues:
> My major concerns with this document might be viewed as disagreements
> with particular design choices.  And, I consider it likely that the
> authors will conclude that the document is still worth publishing as
> is, or perhaps with some minor changes.  In the end, I have no issue
> with that, but expect that the end result will be that the resulting
> RFC is ignored.
>
> What would cause this to be tragic, is if publication of this were
> used to prevent other work in this area from subsequently being
> published.  (For those drawing less-than-charitable inferences from
> this, I have no desire to throw my hat into this particular ring,
> except perhaps in jest [1].)
>
> This design is far too complex and large.  Regardless of how
> well-considered it might be, or how well this meets the stated design
> goals, I can't see anything but failure in this document's future.
> JSON succeeds largely because it doesn't attempt to address so many
> needs at once, but I could even make a case for why JSON contains too
> many features.
>
> In comparison with JSON, this document does one major thing wrong: it
> has more options than JSON in several dimensions.  There are more
> types, there are several more dimensions for extensibility than JSON:
> types extensions, values extensions (values of 28-30 in the lower bits
> of the type byte), plus the ability to apply arbitrary tags to any
> value.  I believe all of these to be major problems that will cause
> them to be ignored, poorly implemented, and therefore useless.
>
> In part, this complexity produces implementations that are far more
> complex than they might need to be, unless additional standardization
> is undertaken.  That idea is something I'm uncomfortable with.
>
> Design issue: extensibility:
> This document avoids discussion of issues regarding schema-less
> document formats that I believe to be fundamental.  These issues are
> critical when considering the creation of a new interchange format.
> By choosing this specific design it makes a number of trade-offs that
> in my opinion are ill-chosen.  This may be in part because the
> document is unclear about how applications intend to use the documents
> it describes.
>
> You may conclude after reading this review that this is simply because
> the document does not explain the rationale for selecting the approach
> it takes.  I hope that isn't the conclusion you reach, but appreciate
> the reasons why you might do so.
>
> I believe the fundamental problem to be one that arises from a
> misunderstanding about what it means to have no schema.  Aside from
> formats that require detailed contextual knowledge to interpret, there
> are several steps toward the impossible, platonic ideal of a perfectly
> self-describing format.  It's impossible because ultimately the entity
> that consumes the data is required at some level to understand the
> semantics that are being conveyed.  In practice, no generic format can
> effectively self-describe to the level of semantics.
>
> This draft describes a format that is more capable at self-description
> than JSON.  I believe that to not just be unnecessary, but
> counterproductive.  At best, it might provide implementations with a
> way to avoid an occasional extra line of code for type conversion.
>
> Extensibility as it relates to types:
> The use of extensive typing in CBOR implies an assumption of a major
> role for generic processing.  XML schema and XQuery demonstrate that
> this desire is not new, but they also demonstrate the folly of
> pursuing those goals.
>
> JSON relies on a single mechanism for extensibility. JSON maps that
> contain unknown or unsupported keys are (usually) ignored.  This
> allows new values to be added to documents without destroying the
> ability of an old processor to extract the values that it supports.
> The limited type information JSON carries leaks out, but it's unclear
> what value this has to a generic processor.  All of the generic uses
> I've seen merely carry that type information, no specific use is made
> of the knowledge it provides.
>
> ASN.1 extensibility, as encoded in PER, leads to no type information
> leaking.  Unsupported extensions are skipped based on a length field.
>
> (As an aside, PER is omitted from the analysis in the appendix, which
> I note from the mailing lists is due to its dependency on schema.
> Interestingly, I believe it to be possible - though not trivial - to
> create an ASN.1 description with all the properties described in CBOR
> that would have roughly equivalent, if not fully equivalent,
> properties to CBOR when serialized.)
>
> By defining an extensibility scheme for types, CBOR effectively
> acknowledges that a generic processor doesn't need type information
> (just delineation information), but it then creates an extensive type
> system.  That seems wasteful.
>
> Design issue: types:
> The addition of the ability to carry uninterpreted binary data is a
> valuable and important feature.  If that was all this document did,
> then that might have been enough.  But instead it adds numerous
> different types.
>
> I can understand why multiple integer encoding sizes are desirable,
> and maybe even floating point representations, but this describes
> bignums in both base 2 and 10, embedded CBOR documents in three forms,
> URIs, base64 encoded strings, regexes, MIME bodies, date and times in
> two different forms, and potentially more.
>
> I also challenge the assertion made where the code required for
> parsing a data type produces larger code sizes if performed outside of
> a common shared library.  That's arguably provably true, but last time
> I checked a few extra procedure calls (or equivalent) weren't the
> issue for code size.  Sheer number of options on the other hand might
> be.
>
> Half-precision floating point numbers are a good example of excessive
> exuberance.  They are not available in many languages for good reason:
> they aren't good for much.  They actually tend to cause errors in
> software in the same way that threading libraries do: it's not that
> it's hard to use them, it's that it's harder than people think.  And
> requiring that implementations parse these creates unnecessary
> complexity.  I do not believe that for the very small subset of cases
> where half precision is actually useful, the cost of transmitting the
> extra 2 bytes of a single-precision number is not going to be a
> burden.  However, the cost of carrying the code required to decode
> them is not as trivial as this makes out.  The fact that this requires
> an appendix would seem to indicate that this is special enough that
> inclusion should have been very carefully considered.  To be honest,
> if it were my choice, I would have excluded single-precision floating
> point numbers as well, they too create more trouble than they are
> worth.
>
> Design issue: optionality
> CBOR embraces the idea that support for types is optional.  Given the
> extensive nature of the type system, it's almost certain that
> implementations will choose to avoid implementation of some subset of
> the types.  The document makes no statements about what types are
> mandatory for implementations, so I'm not sure how it is possible to
> provide interoperable implementations.
>
> If published in its current form, I predict that only a small subset
> of types will be implemented and become interoperable.
>
> Design issue: tagging
> The tagging feature has a wonderful property: the ability to create
> emergency complexity.  Given that a tag itself can be arbitrarily
> complex, I'm almost certain that this is a feature you do not want.
>
> Minor issues:
> Design issue: negative numbers
> Obviously, the authors will be well-prepared for arguments that
> describe as silly the separation of integer types into distinct
> positive and negative types.  But it's true, this is a strange choice,
> and a very strange design.
>
> The fact that this format is capable of describing 64-bit negative
> numbers creates a problem for implementations that I'm surprised
> hasn't been raised already.  In most languages I use, there is no
> native type that is capable of carrying the most negative value that
> can be expressed in this format.  -2^64 is twice as large as a 64-bit
> twos-complement integer can store.
>
> It almost looks as though CBOR is defining a 65-bit, 33-bit or 17-bit
> twos complement integer format, with the most significant bit isolated
> from the others, except that the negative expression doesn't even have
> the good sense to be properly sortable.  Given that and the fact that
> bignums are also defined, I find this choice to be baffling.
>
> Document issue: Canonicalization
> Please remove Section 3.6.  c14n is hard, and this format actually
> makes it impossible to standardize a c14n scheme, that says a lot
> about it.  In comparison, JSON is almost trivial to canonicalize.
>
> If the intent of this section is to describe some of the possible
> gotchas, such as those described in the last paragraph, then that
> would be good.  Changing the focus to "Canonicalization
> Considerations" might help.
>
> I believe that there are several issues that this section would still
> need to consider.  For instance, the use of the types that contain
> additional JSON encoding hints carry additional semantics that might
> not be significant to the application protocol.
>
> Extension based on minor values 28-30 (the "additional information" space):
> ...is impossible as defined.  Section 5.1 seems to imply otherwise.
> I'm not sure how that would ever happen without breaking existing
> parsers.  Section 5.2 actually makes this worse by making a
> wishy-washy commitment to size for 28 and 29, but no commitment at all
> for 30.
>
> Nits:
> Section 3.7 uses the terms "well-formed" and "valid" in a sense that I
> believe to be consistent with their use in XML and XML Schema.  I
> found the definition of "valid" to be a little difficult to parse;
> specifically, it's not clear whether invalid is the logical inverse of
> valid.
>
> Appendix B/Table 4 has a TBD on it.  Can this be checked?
>
> Table 4 keeps getting forward references, but it's hidden in an
> appendix.  I found that frustrating as a reader because the forward
> references imply that there is something important there.  And that
> implication was completely right, this needs promotion.  I know why
> it's hidden, but that reason just supports my earlier theses.
>
> Section 5.1 says "An IANA registry is appropriate here.".  Why not
> reference Section 7.1?
>
> [1] https://github.com/martinthomson/aweson

From meral.shirazipour@ericsson.com  Tue Jul 30 14:47:14 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1F3321F8B07 for <gen-art@ietfa.amsl.com>; Tue, 30 Jul 2013 14:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O69KWaJP4QnT for <gen-art@ietfa.amsl.com>; Tue, 30 Jul 2013 14:47:09 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 917C511E8141 for <gen-art@ietf.org>; Tue, 30 Jul 2013 14:47:09 -0700 (PDT)
X-AuditID: c618062d-b7fc36d0000032ea-8d-51f8345cfa97
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id AD.39.13034.C5438F15; Tue, 30 Jul 2013 23:47:08 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0328.009; Tue, 30 Jul 2013 17:47:07 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org" <draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-method-07
Thread-Index: Ac6NbJMxWaq0WGIaSDy4raLO8rZmyg==
Date: Tue, 30 Jul 2013 21:47:07 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A5D6541@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A5D6541eusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLLMWRmVeSWpSXmKPExsUyuXRPuG6MyY9Agy+PtSx6tyxjtbj66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJXxYFFFwQfbisfnf7M3ME4262Lk4JAQMJFY /y60i5ETyBSTuHBvPVsXIxeHkMBRRomeY2dZIZzljBKfdp9hBaliE7CQ2P77OVhCRGAWo8Ta 1ROBWtg5hAU8JM74g5SICPhKTFp2gxnC1pPYPP8yO4jNIqAqcXr/MSYQm1fAW+J2/1Y2EJsR aPH3U2vA4swC4hK3nsxngjhIQGLJnvPMELaoxMvH/1ghbGWJJU/2s4DczyyQL7H3pQXESEGJ kzOfsExgFJqFZNIshKpZSKogSnQkFuz+xAZha0ssW/iaGcY+c+AxE7L4Akb2VYwcpcWpZbnp RgabGIFRcEyCTXcH456XlocYpTlYlMR5V+mdCRQSSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXA mK2w6O9iTasabbGWvob33t+VOr56WS15/+nS07dMMx8pLbi+ltXv6rW9e5L2l3Klq3u2ro2q 7N3Vscd/r9PL0IZ5O5tXuR1I+DRn5e7HOYb6Wt5V6+bGh/Bt0ps150vMs79aMTOv9cwv0Nzb 4dUcV3RieX7y9++r8nz9V8w7mvyy8feLk3JnbJRYijMSDbWYi4oTAbFpEVRQAgAA
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-method-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 21:47:15 -0000

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

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

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

Document: draft-ietf-emu-eap-tunnel-method-07
Reviewer: Meral Shirazipour
Review Date: 2013-07-30
IETF LC End Date: 2013-07-30
IESG Telechat date: NA


Summary:
This draft is almost ready to be published as Standards Track RFC but I hav=
e some comments.


Nits/editorial comments:
Many sections of the document are a direct copy paste of RFC4851(EAP-FAST) =
with a minor change: "EAP-FAST"->"TEAP".
Since RFC4851 is mentioned as being well adopted, is there a reason why it =
has not been used as reference point and then only mention the diffs in mor=
e detail? (for the sections concerned).
Appendix B is useful, but the above suggestion could have made the document=
 a lot shorter and easier to understand by people already familiar with EAP=
-FAST.
Unless this draft is to replace RFC4851? In which case the abstract should =
mention this.
e.g.
[Page 20], Section 3.7 Fragmentation, is a copy of RFC4851's Section 3.7 wi=
th "EAP-FAST"->"TEAP".
Why not use RFC4851's Fragmentation proposal as a reference point and just =
mention what is different (e.g. nothing but the EAP-Type in this case).


Nits:
[Page 6], Section 1.2, reference [RFC5077] appears twice.
[Page 21], section 3.8, paragraph 2, "which the the peer"--typo-->remove ex=
tra "the"
[Page 24], Section 3.8.4, paragraph 2, "succ;essfully"--typo-->"successfull=
y"
[Page 56], line 3, "Note: Peer's are"---->"Peers"
[Page 73], Section 7.6, "is remoted"--typo-->"is remote"


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

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A5D6541eusaamb107ericsso_
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;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> &nbsp;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-emu-eap-tunnel-method-07<o:p></=
o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-07-30<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-07-30<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"><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 to be published as Standa=
rds Track RFC but I have some 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">Many sections of the document are a direct copy past=
e of RFC4851(EAP-FAST) with a minor change: &quot;EAP-FAST&quot;-&gt;&quot;=
TEAP&quot;.
<o:p></o:p></p>
<p class=3D"MsoNormal">Since RFC4851 is mentioned as being well adopted, is=
 there a reason why it has not been used as reference point and then only m=
ention the diffs in more detail? (for the sections concerned).
<o:p></o:p></p>
<p class=3D"MsoNormal">Appendix B is useful, but the above suggestion could=
 have made the document a lot shorter and easier to understand by people al=
ready familiar with EAP-FAST.<o:p></o:p></p>
<p class=3D"MsoNormal">Unless this draft is to replace RFC4851? In which ca=
se the abstract should mention this.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal">e.g.<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 20], Section 3.7 Fragmentation, is a copy of R=
FC4851's Section 3.7 with &quot;EAP-FAST&quot;-&gt;&quot;TEAP&quot;.<o:p></=
o:p></p>
<p class=3D"MsoNormal">Why not use RFC4851's Fragmentation proposal as a re=
ference point and just mention what is different (e.g. nothing but the EAP-=
Type in this case).<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:<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 6], Section 1.2, reference [RFC5077] appears t=
wice.<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 21], section 3.8, paragraph 2, &quot;which the=
 the peer&quot;--typo--&gt;remove extra &quot;the&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 24], Section 3.8.4, paragraph 2, &quot;succ;es=
sfully&quot;--typo--&gt;&quot;successfully&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 56], line 3, &quot;Note: Peer's are&quot;----&=
gt;&quot;Peers&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">[Page 73], Section 7.6, &quot;is remoted&quot;--typo=
--&gt;&quot;is remote&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></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A5D6541eusaamb107ericsso_--

From peter@akayla.com  Wed Jul 31 13:50:23 2013
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 7100911E8116; Wed, 31 Jul 2013 13:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hHh94lkNA+XC; Wed, 31 Jul 2013 13:50:13 -0700 (PDT)
Received: from p3plsmtpa08-09.prod.phx3.secureserver.net (p3plsmtpa08-09.prod.phx3.secureserver.net [173.201.193.110]) by ietfa.amsl.com (Postfix) with ESMTP id 7B2A421F9CFB; Wed, 31 Jul 2013 13:50:13 -0700 (PDT)
Received: from [130.129.69.200] ([130.129.69.200]) by p3plsmtpa08-09.prod.phx3.secureserver.net with  id 78q11m00J4KFYsJ018q6Qj; Wed, 31 Jul 2013 13:50:12 -0700
User-Agent: Microsoft-MacOutlook/14.3.5.130515
Date: Wed, 31 Jul 2013 13:50:06 -0700
From: Peter Yee <peter@akayla.com>
To: <draft-ietf-geopriv-res-gw-lis-discovery.all@tools.ietf.org>
Message-ID: <CE1EC68E.5B19%peter@akayla.com>
Thread-Topic: Gen-ART review of draft-ietf-geopriv-res-gw-lis-discovery-05
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: gen-art@ietf.org, "ietf@ietf.org list" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-geopriv-res-gw-lis-discovery-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2013 20:50:23 -0000

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

Document: draft-ietf-geopriv-res-gw-lis-discovery-05
Reviewer: Peter Yee
Review Date: Jul-31-2013
IETF LC End Date: Jul-31-2013
IESG Telechat date: TBD

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

The draft describes a means by which Devices behind a residential gateway
may discover the correct Location Information Server on the access network
providing Internet access to residential gateway.  The Device may thereby
gain access to certain location-based services.

Major issues: None

Minor issues: None

Nits:

Section 1, 1st paragraph, 2nd sentence: should "data" be appended
after "location"?  The wording is otherwise odd.

Page 7, 3rd paragraph: change "which" to "that".

Page 9, section 4.2, 2nd paragraph, 1st sentence: I'll admit my ignorance
of the finer points of the DNS and inquire what this sentence is supposed
to mean.  To what are the additional domain names added and how does this
allow a DNS record to cover a larger set of addresses?  Perhaps it's just
the wording or my lack of knowledge, but I didn't follow this point fully.

Page 9, section 4.2, 2nd bullet item: change "sucessively" to
"successively".

Page 11, section 4.6, 1st paragraph, 4th sentence: insert "a" before
"STUN server" or change "server" to "servers" depending on how many
need to be configured.

Page 12, 1st sentence: delete "a".

Page 12, 1st sentence: What about /56 for IPv6?

Page 14, 3rd paragraph, 2nd sentence: delete "a" before
"IP addresses" or change "addresses" to "address" depending on
how many false addresses you mean.

Page 14, 6th paragraph, last sentence: Are there any concrete
suggestions on who a device might determine accuracy?


 





From mccap@petoni.org  Wed Jul 31 13:58:07 2013
Return-Path: <mccap@petoni.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAD3C21E809E for <gen-art@ietfa.amsl.com>; Wed, 31 Jul 2013 13:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.426
X-Spam-Level: 
X-Spam-Status: No, score=-0.426 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SzFiMwA6Y-9F for <gen-art@ietfa.amsl.com>; Wed, 31 Jul 2013 13:58:03 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A6AC621F9EE9 for <gen-art@ietf.org>; Wed, 31 Jul 2013 13:58:02 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hi8so4067617wib.1 for <gen-art@ietf.org>; Wed, 31 Jul 2013 13:58:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=WV9rN5F9PLolKM47x0oVNjhvYkmLK3YzFharXIryI0w=; b=KJ2Huf76ATiQO7YeIH+UxwpT+VOTu1UKo4rhRDzp8/esK7bKQH/X05blDDA2poHNEf IRtHWxUYs4oavNjOM76YIwW7PsxDFE6+o5jgQV2EVbC1lz3FIwGzZyLfStquDMbyN+Xp lg6nxC5uAsJzpVFWO3bDxICC3VXIjoc0Z4xao=
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=WV9rN5F9PLolKM47x0oVNjhvYkmLK3YzFharXIryI0w=; b=chAcufxdjtb7H/IHMvbzL+nt+rplC3+4ls1DYBDeV18s+HTqO0VH3qceLyjQjUvP8+ BZ5lfcwukR/oGNlIsXDg4GOObhmeCl8FNgZ3K26vU8iaNfVePW3sTDh+3nKrxuhrOqwy MbyV2ptCf9oSeMWbSkNCxQzUuyO6qKzLDNMkcyGq1mr40jrlykQ1A5FK8BDKpGj3nwVY p/DlViPfYbyDmiDwL5JE6Uzg3ycroT44NSdQxeTmnwMJfKSYidXj4lmtHNZQGu3U+ZG6 vHcU2WTUqyhjXUUrc2x44RsSuhb/RTttxl4XNt/pzXJlhdNnIK2YvkSPFBTjkXna1IAp S3uA==
MIME-Version: 1.0
X-Received: by 10.194.108.73 with SMTP id hi9mr39956916wjb.85.1375304281771; Wed, 31 Jul 2013 13:58:01 -0700 (PDT)
Received: by 10.194.121.38 with HTTP; Wed, 31 Jul 2013 13:58:01 -0700 (PDT)
X-Originating-IP: [46.189.28.109]
Date: Wed, 31 Jul 2013 16:58:01 -0400
Message-ID: <CACvMsLFSS4iYp6vS5iDNP1xk=VXqwOAqH0jUCNkR6DYSPjSxNw@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-mpls-retire-ach-tlv.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQliFBmp4pfbF4LZUXLt8yEVC/M1zqlonBQns6vSjOvewXyiFFb/PGef1VF4dejGQSCUfqDG
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-mpls-retire-ach-tlv-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2013 20:58:07 -0000

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

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

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

Document:   draft-ietf-mpls-retire-ach-tlv-03
Reviewer:     Peter McCann
Review Date:  2013-07-31
IETF LC End Date:  2013-07-31
IESG Telechat date: (unknown)

Summary:  Ready

Major issues:  None

Minor issues:  None

Nits/editorial comments:  None
