Re: [dispatch] Draft new: draft-holmberg-dispatch-pani-abnf-00 [was: [sipcore] [Technical Errata Reported] RFC7315 (4474)]

Hi Jean,

Thanks for your comments! I will update the draft according to your suggestions.

Regards,

Christer

-----Original Message-----
From: A. Jean Mahoney [mailto:mahoney@nostrum.com] 
Sent: 27 October 2015 23:46
To: Christer Holmberg <christer.holmberg@ericsson.com>; Ben Campbell <ben@nostrum.com>
Cc: DISPATCH list <dispatch@ietf.org>; SIPCORE <sipcore@ietf.org>
Subject: Re: [dispatch] Draft new: draft-holmberg-dispatch-pani-abnf-00 [was: [sipcore] [Technical Errata Reported] RFC7315 (4474)]

Hi Christer,

The draft looks good to me. Just a few nits:

1. Introduction

2nd paragraph: "requires new values are required" => "requires new values".

4th paragraph: "have been followed" => "have been defined"

You may also consider adding a reference to TS 24.229, which defines values for access-info, to the 4th paragraph.

Thanks!

Jean

On 10/18/15 2:10 PM, Christer Holmberg wrote:
> Hi,
>
> I've submitted a new version, -01, where the category is changed to 'Informational'.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of 
> Christer Holmberg
> Sent: 18 October 2015 21:59
> To: Ben Campbell <ben@nostrum.com>
> Cc: DISPATCH list <dispatch@ietf.org>; SIPCORE <sipcore@ietf.org>
> Subject: Re: [dispatch] Draft new: 
> draft-holmberg-dispatch-pani-abnf-00 [was: [sipcore] [Technical Errata 
> Reported] RFC7315 (4474)]
>
> Hi,
>
>> If 7315 is informational, why does the update need to be standards track?
>
> Good point - I guess it doesn't have to :)
>
> Regards,
>
> Christer
>
>
> On 18 Oct 2015, at 6:49, Christer Holmberg wrote:
>
>> Hi,
>>
>> Based on Ben’s guidance, I’ve submitted a draft which makes the ABNF 
>> update.
>>
>> NOTE: As RFC 7315 is an Informational RFC, I had to add the RFC as an 
>> Informative reference in the draft, in order to pass the Idnits check.
>>
>>
>> A new version of I-D, draft-holmberg-dispatch-pani-abnf-00.txt
>>
>> has been successfully submitted by Christer Holmberg and posted to 
>> the IETF repository.
>>
>>
>>
>> Name:                 draft-holmberg-dispatch-pani-abnf
>>
>> Revision:            00
>>
>> Title:                    P-Access-Network-Info ABNF Update
>>
>> Document date:              2015-10-18
>>
>> Group:                Individual Submission
>>
>> Pages:                 4
>>
>> URL:
>> https://www.ietf.org/internet-drafts/draft-holmberg-dispatch-pani-abn
>> f
>> -00.txt
>>
>> Status:
>> https://datatracker.ietf.org/doc/draft-holmberg-dispatch-pani-abnf/
>>
>> Htmlized:
>> https://tools.ietf.org/html/draft-holmberg-dispatch-pani-abnf-00
>>
>>
>>
>>
>>
>> Abstract:
>>
>> This document updates RFC 7315, by modifying the extension-access-
>>
>> info part of the P-Access-Network-Info header field Augmented Backus-
>>
>> Naur Form (ABNF).
>>
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
>> From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Christer 
>> Holmberg
>> Sent: 18 October 2015 10:52
>> To: Ben Campbell <ben@nostrum.com>
>> Cc: DISPATCH list <dispatch@ietf.org>; SIPCORE <sipcore@ietf.org>; 
>> Cullen Jennings <fluffy@iii.ca>
>> Subject: Re: [sipcore] [dispatch] [Technical Errata Reported] RFC7315
>> (4474)
>>
>> Hi,
>>
>> So, shall I address the draft to some WG, or?
>>
>> draft-holmberg-dispatch ?
>>
>> Regards,
>>
>> Christer
>>
>> Sent from my Windows Phone
>> ________________________________
>> From: Ben Campbell<mailto:ben@nostrum.com>
>> Sent: ‎14/‎10/‎2015 17:21
>> To: Christer Holmberg<mailto:christer.holmberg@ericsson.com>
>> Cc: Cullen Jennings<mailto:fluffy@iii.ca>; DISPATCH 
>> list<mailto:dispatch@ietf.org>; SIPCORE<mailto:sipcore@ietf.org>
>> Subject: Re: [sipcore] [dispatch] [Technical Errata Reported] RFC7315
>> (4474)
>> On 8 Oct 2015, at 21:03, Christer Holmberg wrote:
>>
>>> Hi Cullen,
>>>
>>> So, you are suggesting a SIPCORE draft that updates the ABNF?
>>
>> This is where the chairs will point out that special-purpose 
>> extensions are generally not in scope for sipcore :-) If so, this 
>> might could also be done as AD sponsored.
>>
>> Ben.
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>