Re: [Gen-art] Fwd: Gen-art LC review: draft-holmerg-dispatch-iotl-03.txt

Robert Sparks <rjsparks@nostrum.com> Wed, 07 January 2015 15:03 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEA4E1A90E5 for <gen-art@ietfa.amsl.com>; Wed, 7 Jan 2015 07:03:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CRxMjrt7CGz4 for <gen-art@ietfa.amsl.com>; Wed, 7 Jan 2015 07:03:22 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8A571A90DF for <gen-art@ietf.org>; Wed, 7 Jan 2015 07:03:21 -0800 (PST)
Received: from unnumerable.local (pool-71-96-107-228.dllstx.fios.verizon.net [71.96.107.228]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id t07F3GGD018731 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 7 Jan 2015 09:03:16 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-71-96-107-228.dllstx.fios.verizon.net [71.96.107.228] claimed to be unnumerable.local
Message-ID: <54AD4AAF.6010401@nostrum.com>
Date: Wed, 07 Jan 2015 09:03:11 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>, General Area Review Team <gen-art@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Richard Barnes <rlb@ipv.sx>
References: <54934283.5090905@nostrum.com> <54936422.2090407@nostrum.com> <7594FB04B1934943A5C02806D1A2204B1D60A8BD@ESESSMB209.ericsson.se> <549430B2.4080809@nostrum.com> <7594FB04B1934943A5C02806D1A2204B1D60C7CF@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D623842@ESESSMB209.ericsson.se> <54AD4831.7060506@nostrum.com> <7594FB04B1934943A5C02806D1A2204B1D6241AF@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D6241AF@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/h0aFTn64WZgFZ_h5rEFDDixmI1A
Subject: Re: [Gen-art] Fwd: Gen-art LC review: draft-holmerg-dispatch-iotl-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 07 Jan 2015 15:03:25 -0000

On 1/7/15 8:58 AM, Christer Holmberg wrote:
> Hi Robert,
>
>> Your changes below are fine.
>>
>> I added Paul and Richard because of their involvement in adding the 3gpp text.
>>
>> I'm not ok with the 3gpp scope as written.
>> It makes no sense to claim this is a proposed standard for the Internet and say "it's not defined for any part of the Internet that's not 3gpp".
>> I would expect most of the IESG to have the same reaction.
>>
>> It would be different, and less objectionable, to say "it's not likely to be particularly useful anywhere but in a 3GPP network".
>>
>> I still think you should just remove last paragraph of the introduction, and section 2 altogether.
> I assume that we then also have to remove "3rd-Generation Partnership Project (3GPP)" from the title?
I'm less uptight about that. That helps say "it's not likely to be 
particularly useful anywhere but in a 3GPP network".

Even P-headers, back in the day, were not "undefined outside the private 
network".
>
> Regards,
>
> Christer
>
>
> On 1/7/15 3:11 AM, Christer Holmberg wrote:
>> Hi Robert,
>>
>> Are you ok with the suggested changes?
>>
>> I suggest that we don't change the 3GPP scope. It would delay the draft, and nobody has shown any interest for non-3GPP usage.
>>
>> Regards,
>>
>> Christer
>>
>> -----Original Message-----
>> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Christer
>> Holmberg
>> Sent: 19. joulukuuta 2014 16:10
>> To: Robert Sparks; General Area Review Team
>> Subject: Re: [Gen-art] Fwd: Gen-art LC review:
>> draft-holmerg-dispatch-iotl-03.txt
>>
>> Hi,
>>
>>>> Nits/editorial comments:
>>>>
>>>>> Since you are providing an extension point for other values,
>>>>> someone will ask if you need a registry for those values. I suggest
>>>>> explicitly saying we are not creating a registry at this time but
>>>>> expect to do so if the extension point is ever used to head that conversation off.
>>>> I could add the following text to the Syntax/General section:
>>>>
>>>> 	"This specification does not create an IANA registry for 'iotl' parameter values.
>>>> 	If new parameters values are defined in the future, such registry needs to be
>>>> 	created."
>>>>
>>>> Or, do you think it should be somewhere else?
>>> It's fine there. However, I would change the last sentence to "A registry should be considered if new parameter values are defined in the future".
>> Ok.
>>
>> 	"This specification does not create an IANA registry for 'iotl' parameter values.
>>    	A registry should be considered if new parameter values are defined in the future"
>>
>> ---------------
>>
>>>>> The sentence (which occurs in the abstract and introduction) "The
>>>>> directionality in traffic legs relates to a SIP request creating a
>>>>> dialogue and stand-alone SIP request." does not parse. What is it
>>>>> trying to say, and why is it important?
>>>> The sentence is not needed (and it doesn't belong in the Abstract to begin with), so I suggest to remove it.
>>> You'll remove it from the introduction as well?
>> Yes.
>>
>> Regards,
>>
>> Christer
>>
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art