Re: [AVT] Fwd: Next steps for draft-ietf-avt-seed-srtp

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Mon, 24 May 2010 14:37 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E61B3A6902 for <avt@core3.amsl.com>; Mon, 24 May 2010 07:37:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.967
X-Spam-Level:
X-Spam-Status: No, score=-3.967 tagged_above=-999 required=5 tests=[AWL=-0.318, BAYES_50=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v8oOWccpt0Yg for <avt@core3.amsl.com>; Mon, 24 May 2010 07:37:49 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id 3CF4C3A68A0 for <avt@ietf.org>; Mon, 24 May 2010 07:37:48 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o4OEbbvL025299 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 24 May 2010 16:37:37 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.45]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Mon, 24 May 2010 16:37:37 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Robert Sparks <rjsparks@nostrum.com>, "avt@ietf.org" <avt@ietf.org>
Date: Mon, 24 May 2010 16:37:36 +0200
Thread-Topic: [AVT] Fwd: Next steps for draft-ietf-avt-seed-srtp
Thread-Index: Acr5qbWCeVW6yHABTIORI8XTf9Pu+QBpK6Bw
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE2132261E3@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <022001caf81f$b5fc5cd0$21f51670$%roni@huawei.com> <B764B9B3-DB11-4ED5-A112-08FA3D2E8E74@nostrum.com>
In-Reply-To: <B764B9B3-DB11-4ED5-A112-08FA3D2E8E74@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: Dan Wing <dwing@cisco.com>
Subject: Re: [AVT] Fwd: Next steps for draft-ietf-avt-seed-srtp
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 May 2010 14:37:50 -0000

So the key issue here is:

Do you (the WG) agree with draft-ietf-avt-seed-srtp becoming proposed standard rather than informational?

regards

Keith

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> Behalf Of Robert Sparks
> Sent: Saturday, May 22, 2010 12:18 PM
> To: avt@ietf.org
> Cc: Dan Wing
> Subject: [AVT] Fwd: Next steps for draft-ietf-avt-seed-srtp
> 
> All -
> 
> Based on IESG feedback, we are planning handle the 
> registrations for the use of SEED with SRTP the same way it 
> is handled for TLS and CMS. Dan will add text to the 
> introduction similar to Section 1.1 of RFC4162 and make a few 
> minor edits to make it even more clear that the mandatory to 
> implement requirements in Section 5 of this document apply 
> only to SRTP implementations that support SEED. Note there 
> are clarifications already added to the document in response 
> to its last IESG review reinforcing that this document does 
> not make SEED mandatory to implement.
> 
> I will take the document back to the IESG for approval as 
> Proposed Standard (it was previously processed as 
> Informational). Assuming the document clears in this form, I 
> propose we not move forward with draft-ietf-avt-register-srtp.
> 
> Please comment soon if you think we should be taking a different path.
> 
> Thanks,
> 
> RjS
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>