Re: [Fecframe] IESG Eval followup: config-signaling anf rtp-raptor

David Harrington <ietfdbh@comcast.net> Tue, 21 February 2012 13:38 UTC

Return-Path: <ietfdbh@comcast.net>
X-Original-To: fecframe@ietfa.amsl.com
Delivered-To: fecframe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4905121F87DA for <fecframe@ietfa.amsl.com>; Tue, 21 Feb 2012 05:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.23
X-Spam-Level:
X-Spam-Status: No, score=-102.23 tagged_above=-999 required=5 tests=[AWL=0.369, 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 hLCfadiQ-1pD for <fecframe@ietfa.amsl.com>; Tue, 21 Feb 2012 05:38:08 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by ietfa.amsl.com (Postfix) with ESMTP id EFF8D21F87D6 for <fecframe@ietf.org>; Tue, 21 Feb 2012 05:38:07 -0800 (PST)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta12.westchester.pa.mail.comcast.net with comcast id cdEg1i0051c6gX85Cde833; Tue, 21 Feb 2012 13:38:08 +0000
Received: from [192.168.1.33] ([71.233.85.150]) by omta23.westchester.pa.mail.comcast.net with comcast id cddj1i0203Ecudz3jddwfg; Tue, 21 Feb 2012 13:38:08 +0000
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Tue, 21 Feb 2012 08:37:41 -0500
From: David Harrington <ietfdbh@comcast.net>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>, Greg Shepherd <gjshep@gmail.com>, <fecframe@ietf.org>
Message-ID: <CB6906FB.13C41%ietfdbh@comcast.net>
Thread-Topic: [Fecframe] IESG Eval followup: config-signaling anf rtp-raptor
In-Reply-To: <067E6CE33034954AAC05C9EC85E2577C0729E347@XMB-RCD-111.cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [Fecframe] IESG Eval followup: config-signaling anf rtp-raptor
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of FEC Framework <fecframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fecframe>, <mailto:fecframe-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fecframe>
List-Post: <mailto:fecframe@ietf.org>
List-Help: <mailto:fecframe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fecframe>, <mailto:fecframe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2012 13:38:09 -0000

Hi Rajiv,

Can you get a new revision published as Informational please?

Here is an issue you really need to address in the document:
"To make this actionable I suggest you work out very clearly what the
purpose of
the document is and capture that both in the Abstract and the
Introduction. It
would also help if you clearly defined what *you* mean by a signaling
protocol
because people at different layers of the stack have very different
understandings of the term."

There are a number of other discusses that need to be addressed.

If you get a revision to me by the end of February, I can run it through
the system again and hopefully get it into the RFC Editor before I step
down as AD in March. You really don't want to start over with a new AD.

Thanks,

--
David Harrington
Director, Transport Area
Internet Engineering Task Force (IETF)
Ietfdbh@comcast.net
+1-603-828-1401





On 1/20/12 12:46 PM, "Rajiv Asati (rajiva)" <rajiva@cisco.com>; wrote:

>Informational is fine.
>
>Cheers,
>Rajiv
>
>> -----Original Message-----
>> From: Greg Shepherd [mailto:gjshep@gmail.com]
>> Sent: Friday, November 04, 2011 10:30 AM
>> To: Rajiv Asati (rajiva); fecframe@ietf.org
>> Subject: Fwd: IESG Eval followup: config-signaling anf rtp-raptor
>> 
>> *,
>> 
>> There are a few things holding up the config-sig draft, but the one we
>> need to help with is:
>> 
>> MUST this doc progress as experimental, or is there WG consensus to
>> move it to informational?
>> 
>> Please reply promptly to the list.
>> 
>> Thanks!,
>> Greg
>> 
>> 
>> ---------- Forwarded message ----------
>> From: David Harrington <ietfdbh@comcast.net>;
>> Date: Fri, Nov 4, 2011 at 7:23 AM
>> Subject: IESG Eval followup: config-signaling anf rtp-raptor
>> To: gjshep@gmail.com
>> Cc: draft-ietf-fecframe-config-signaling@tools.ietf.org,
>> draft-ietf-fecframe-rtp-raptor@tools.ietf.org
>> 
>> 
>> Hi,
>> 
>> The IESG reviewed the config signaling and rtp-raptor drafts.
>> We have work to do.
>> 
>> config-signaling:
>> 1) Can we publish this as Informational?
>>        Is that a problem for any cross-SDO work?
>>        If this is published as Informational, then compliance is no
>> longer appropriate - you don't comply to an Informational document. so
>> the RFC2119 keywords should disappear.
>> 
>> 2) Ask the WG which version of GDOI is supposed to be used? See Sean's
>> Comments.
>> 
>> 3) The document needs a good rewrite, especialy the Abstract and
>> Introduction. There are Discusses and Comments from many that the
>> document doesn't describe its purpose. This must be clairified.
>> 
>> 4) There are Discusses and Comments from multiple ADs that must be
>> addressed:
>> Ron: just remove the reference; I don't know if you want to carry any
>> information from that expired mboned doc into this doc.
>> Adrian: clarify what is considered a signaling protocol in this doc
>> Gonzalo: no RFC2119 keywords in the Introduction (so normative text
>> must be moved)
>> Jari: internal references (are you using xml2rfc? they have ways to
>> keep that in sync for you)
>>        clarify how you expect this to be used re: SDP, XML, etc.
>> Russ: Gen-ART review
>> Sean: "MAY encrypt"
>>        MUST is for implementers - see RFC 3365 - unless this is
>> Informational.
>>        GDOI - explain how to use this. Clarify which version.
>> Stephen: "MAY encrypt" => "SHOULD encrypt using PGP or CMS"?
>>        GDOI - how to use to manage keys?
>> Pete: If Informational, then you can ignore his comment; If
>> Experimental, then describe the experiment.
>> Robert: new versus copied requirements; point to the existing rules
>> rather than copying them here.
>>        The #2 comment is critical - are implementers supposed to
>> choose from one of these protocols
>>        (i.e., these are the only ones allowed in a compliant
>> Experimental implementation?)
>> 
>> rpt-raptor:
>> 1) A registration request must be sent to ietf-types@iana.org to
>> register the types, per section 5.1 of RFC 4288. The registration
>> template needs to be filled in
>> 
>> 2) There are discusses from Sean, Pete, Robert and Stephen that must
>> be addressed, and Comments from Russ (the Gen-ART review) that should
>> be addressed in a Revised ID. I think the usage of RFC2119 keywords is
>> acceptable, but might be improved. Please read and **consider** Pete's
>> comments on RFC2119 usage, and then do what you think is right.
>> 
>> Please get these Revised IDs done asap so I can send them off to the
>> RFC Editor.
>> 
>> David Harrington
>> Director, IETF Transport Area
>> ietfdbh@comcast.net (preferred for ietf)
>> dbharrington@huaweisymantec.com
>> +1 603 828 1401 (cell)
>_______________________________________________
>Fecframe mailing list
>Fecframe@ietf.org
>https://www.ietf.org/mailman/listinfo/fecframe