Re: [Sip] draft-jennings-sip-dtls: shouldn't it define ; transport=dccp ?
"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Fri, 08 July 2011 19:10 UTC
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: sip@ietfa.amsl.com
Delivered-To: sip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F41721F8C63 for <sip@ietfa.amsl.com>; Fri, 8 Jul 2011 12:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.099
X-Spam-Level:
X-Spam-Status: No, score=-106.099 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oKdrroqbBESN for <sip@ietfa.amsl.com>; Fri, 8 Jul 2011 12:10:51 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id EB84721F86DA for <sip@ietf.org>; Fri, 8 Jul 2011 12:10:50 -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 p68IwdWv004612 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 8 Jul 2011 21:10:49 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Fri, 8 Jul 2011 21:10:21 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Iñaki Baz Castillo <ibc@aliax.net>, "sip@ietf.org" <sip@ietf.org>
Date: Fri, 08 Jul 2011 21:10:19 +0200
Thread-Topic: [Sip] draft-jennings-sip-dtls: shouldn't it define ; transport=dccp ?
Thread-Index: Acw9j4gZG+XB6wsdQXOPSKNUGpYEHAAEruAg
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21FC2D9B3@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <CALiegfnXjsvQp7tacA6D+MVbo0bL5e07U6H92cQ5_JqQqvi-4Q@mail.gmail.com>
In-Reply-To: <CALiegfnXjsvQp7tacA6D+MVbo0bL5e07U6H92cQ5_JqQqvi-4Q@mail.gmail.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Subject: Re: [Sip] draft-jennings-sip-dtls: shouldn't it define ; transport=dccp ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 19:10:52 -0000
Given that as far as I can see, the last version of this document expired in 2008, I think you must regard any contents as historical. It was never picked up by the SIP WG. Regards Keith > -----Original Message----- > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of > Iñaki Baz Castillo > Sent: 08 July 2011 17:53 > To: sip@ietf.org > Subject: [Sip] draft-jennings-sip-dtls: shouldn't it define ; > transport=dccp ? > > Hi, draft-jennings-sip-dtls defines: > > - SIP over DTLS over UDP => Via transport: "DTLS-UDP" > - SIP over DTLS over DCCP => Via transport: "DTLS-DCCP" > - SIP over DCCP => Via transport: "DCCP" > > The draft just defines new BNF grammar for Via transport field, but > says nothing about SIP URI ;transport param. > IMHO the draft MUST define a new value "dccp" for ;transport param. > > Regards, > > > > -- > Iñaki Baz Castillo > <ibc@aliax.net> > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is essentially closed and only used for finishing old business. > Use sip-implementors@cs.columbia.edu for questions on how to develop a SIP > implementation. > Use dispatch@ietf.org for new developments on the application of sip. > Use sipcore@ietf.org for issues related to maintenance of the core SIP > specifications.
- [Sip] draft-jennings-sip-dtls: shouldn't it defin… Iñaki Baz Castillo
- Re: [Sip] draft-jennings-sip-dtls: shouldn't it d… DRAGE, Keith (Keith)
- Re: [Sip] draft-jennings-sip-dtls: shouldn't it d… Iñaki Baz Castillo
- Re: [Sip] draft-jennings-sip-dtls: shouldn't it d… DRAGE, Keith (Keith)