Re: [payload] I-D Action: draft-ietf-payload-rtp-howto-14.txt

["Ali C. Begen (abegen)" <[e-mail]>]

Well, the revision has been made after a long discussion with the IESG members and secdir folks during the approval of the opus draft. 

Do you have a concern about this? I think it was useful that the authors did not wait for the auth48 to make this change as there are active drafts who are referring to this guideline in developing their drafts. So, the sooner we have this in the boilerplate, the better it is.




-----Original Message-----
From: "DRAGE, Keith (Keith)"
Date: Tuesday, May 12, 2015 at 8:56 PM
To: Magnus Westerlund, "[e-mail]"
Subject: Re: [payload] I-D Action: draft-ietf-payload-rtp-howto-14.txt

>The datatracker contains no evidence of why this change occurred after approval, or at least I could find nothing. The latest record is the approval of the -13 version, and nothing in relation to the -14 version.
>
>Could we find a relevant way of documenting this, and the approval process.
>
>Keith
>
>> -----Original Message-----
>> From: payload [mailto:[e-mail]] On Behalf Of 
>> Magnus Westerlund
>> Sent: 04 May 2015 09:04
>> To: [e-mail]
>> Subject: Re: [payload] I-D Action: draft-ietf-payload-rtp-howto-14.txt
>> 
>> WG,
>> 
>> This version updates the boiler plate security consideration 
>> based on the discussion a few weeks back. I also replaced 
>> references to drafts with their published RFCs.
>> 
>> I do note that XML2RFC appears to have updated its practice 
>> in line folding URIs, which results in some additional diff changes.
>> 
>> Cheers
>> 
>> Magnus
>> 
>> 
>> [e-mail] skrev den 2015-05-04 10:00:
>> >
>> > A New Internet-Draft is available from the on-line 
>> Internet-Drafts directories.
>> >   This draft is a work item of the Audio/Video Transport 
>> Payloads Working Group of the IETF.
>> >
>> >          Title           : How to Write an RTP Payload Format
>> >          Author          : Magnus Westerlund
>> > 	Filename        : draft-ietf-payload-rtp-howto-14.txt
>> > 	Pages           : 60
>> > 	Date            : 2015-05-04
>> >
>> > Abstract:
>> >     This document contains information on how to best write an RTP
>> >     payload format specification.  It provides reading tips, design
>> >     practices, and practical tips on how to produce an RTP 
>> payload format
>> >     specification quickly and with good results.  A template is also
>> >     included with instructions.
>> >
>> >
>> > The IETF datatracker status page for this draft is:
>> > https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-howto/
>> >
>> > There's also a htmlized version available at:
>> > https://tools.ietf.org/html/draft-ietf-payload-rtp-howto-14
>> >
>> > A diff from the previous version is available at:
>> > https://www.ietf.org/rfcdiff?url2=draft-ietf-payload-rtp-howto-14
>> >
>> >
>> > Please note that it may take a couple of minutes from the time of 
>> > submission until the htmlized version and diff are 
>> available at tools.ietf.org.
>> >
>> > Internet-Drafts are also available by anonymous FTP at:
>> > ftp://ftp.ietf.org/internet-drafts/
>> >
>> > _______________________________________________
>> > payload mailing list
>> > [e-mail]
>> > https://www.ietf.org/mailman/listinfo/payload
>> >
>> >
>> 
>> 
>> -- 
>> 
>> Magnus Westerlund
>> 
>> ----------------------------------------------------------------------
>> Services, Media and Network features, Ericsson Research EAB/TXM
>> ----------------------------------------------------------------------
>> Ericsson AB                 | Phone  [phone]
>> Färögatan 6                 | Mobile [phone]
>> SE-164 80 Stockholm, Sweden | mailto: [e-mail]
>> ----------------------------------------------------------------------
>> 
>> _______________________________________________
>> payload mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/payload
>> 
>_______________________________________________
>payload mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/payload