[Geopriv] AD Review: draft-ietf-geopriv-flow-identity-00

Robert Sparks <rjsparks@nostrum.com> Tue, 12 February 2013 17:19 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 523DB21F8FBB for <geopriv@ietfa.amsl.com>; Tue, 12 Feb 2013 09:19:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SzmbeDhzEgSp for <geopriv@ietfa.amsl.com>; Tue, 12 Feb 2013 09:19:28 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id B7B4A21F8FB9 for <geopriv@ietf.org>; Tue, 12 Feb 2013 09:19:28 -0800 (PST)
Received: from unnumerable.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r1CHJR7L055940 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 12 Feb 2013 11:19:28 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <511A799F.8040607@nostrum.com>
Date: Tue, 12 Feb 2013 11:19:27 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: GEOPRIV WG <geopriv@ietf.org>, draft-ietf-geopriv-flow-identity@tools.ietf.org
Content-Type: multipart/alternative; boundary="------------030506020906010408070206"
Received-SPF: pass (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Subject: [Geopriv] AD Review: draft-ietf-geopriv-flow-identity-00
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 17:19:29 -0000

Summary: There is one point that needs to be clarified with a revised ID 
before progressing to IETF LC.

Thanks for producing such a succinct draft. This is one of the rare 
cases where we need more words, not fewer.
The draft needs to be more explicit about whether it is _changing_ 6155 
or if it is just extending it.

The current use of Updates, and the language at the bottom of page 5 
seems to say "All implementations of 6155
need to be updated right away - it's not ok and can result in error to 
continue to use the ports from 6155." If that's
really the intent of the document, please say it that strongly (in the 
abstract and the introduction).

If it was the intent only to provide an extension that could be used in 
circumstances where the base mechanism in 6155
would fail, then this extends 6155, not updates, and the header doesn't 
need to say anything.

The protocol writeup needs to be adjusted to match the result - 
currently it says

" Working Group Summary:

This document is a simple extension to an existing protocol and was
uncontroversial in the working group."

which would be true if the intent was to only provide an extension as 
opposed to changing (Updating) the protocol in 6155.