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

Greg Shepherd <gjshep@gmail.com> Fri, 04 November 2011 14:29 UTC

Return-Path: <gjshep@gmail.com>
X-Original-To: fecframe@ietfa.amsl.com
Delivered-To: fecframe@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 33CD421F8C51 for <fecframe@ietfa.amsl.com>; Fri, 4 Nov 2011 07:29:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.532
X-Spam-Status: No, score=-103.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id wZJRFbtfcshP for <fecframe@ietfa.amsl.com>; Fri, 4 Nov 2011 07:29:52 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id 4609121F8C50 for <fecframe@ietf.org>; Fri, 4 Nov 2011 07:29:52 -0700 (PDT)
Received: by mail-bw0-f44.google.com with SMTP id zv15so2025510bkb.31 for <fecframe@ietf.org>; Fri, 04 Nov 2011 07:29:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=nU4/qw2BCtfFkALA3vaIR+0rW4yJSkLiXCw16rcFJok=; b=t84ClZS4Jweab+pgQooCSI52BNGjdJH1pXgnM3xwCnJJrdLIkCcX/Y7+lYgA0KU9sn rwFUJFsp1P3Hi6HEkQko92GUyJTv02KCaHGOFlpoL9vIaquGkwzko0cytt7uhjmDXvVX VhnoGPM4ssUWDZU+MfMYudI6iNrr7BB3riDUo=
MIME-Version: 1.0
Received: by with SMTP id g3mr12380795bku.28.1320416991863; Fri, 04 Nov 2011 07:29:51 -0700 (PDT)
Received: by with HTTP; Fri, 4 Nov 2011 07:29:51 -0700 (PDT)
In-Reply-To: <E50A988001D34452A247B37F8108B2CC@davidPC>
References: <E50A988001D34452A247B37F8108B2CC@davidPC>
Date: Fri, 4 Nov 2011 07:29:51 -0700
Message-ID: <CABFReBpNn0epBEWQTmDQ6AY1WY9yWEX7RPnD+icSnajmyT+EvA@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>, fecframe@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [Fecframe] Fwd: IESG Eval followup: config-signaling anf rtp-raptor
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gjshep@gmail.com
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: Fri, 04 Nov 2011 14:29:53 -0000


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.


---------- 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,


The IESG reviewed the config signaling and rtp-raptor drafts.
We have work to do.

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

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
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
       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?)

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)
+1 603 828 1401 (cell)