headers
Iñaki Baz Castillo | 8 Jul 2011 18:53
Gravatar

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 <at> 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 <at> cs.columbia.edu for questions on how to develop a SIP implementation.
Use dispatch <at> ietf.org for new developments on the application of sip.
Use sipcore <at> ietf.org for issues related to maintenance of the core SIP specifications.
Permalink | Reply |
headers
DRAGE, Keith (Keith | 8 Jul 2011 21:10
Favicon

Re: draft-jennings-sip-dtls: shouldn't it define ; transport=dccp ?

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 <at> ietf.org [mailto:sip-bounces <at> ietf.org] On Behalf Of
> Iñaki Baz Castillo
> Sent: 08 July 2011 17:53
> To: sip <at> 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,
> 
>
(Continue reading)

Permalink | Reply |
headers
Iñaki Baz Castillo | 8 Jul 2011 21:52
Gravatar

Re: draft-jennings-sip-dtls: shouldn't it define ; transport=dccp ?

2011/7/8 DRAGE, Keith (Keith) <keith.drage <at> alcatel-lucent.com>:
> 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.

Good point, I didn't realize of that. So, is there a draft or RFC
defining SIP over DTLS-UDP?

--

-- 
Iñaki Baz Castillo
<ibc <at> 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 <at> cs.columbia.edu for questions on how to develop a SIP implementation.
Use dispatch <at> ietf.org for new developments on the application of sip.
Use sipcore <at> ietf.org for issues related to maintenance of the core SIP specifications.
Permalink | Reply |
headers
DRAGE, Keith (Keith | 8 Jul 2011 22:32
Favicon

Re: draft-jennings-sip-dtls: shouldn't it define ; transport=dccp ?

The only SIP document was RFC 5763. That doesn't define it, and doesn't apparently need it.

Keith

> -----Original Message-----
> From: Iñaki Baz Castillo [mailto:ibc <at> aliax.net]
> Sent: 08 July 2011 20:52
> To: DRAGE, Keith (Keith)
> Cc: sip <at> ietf.org
> Subject: Re: [Sip] draft-jennings-sip-dtls: shouldn't it define ;
> transport=dccp ?
> 
> 2011/7/8 DRAGE, Keith (Keith) <keith.drage <at> alcatel-lucent.com>:
> > 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.
> 
> Good point, I didn't realize of that. So, is there a draft or RFC
> defining SIP over DTLS-UDP?
> 
> --
> Iñaki Baz Castillo
> <ibc <at> 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 <at> cs.columbia.edu for questions on how to develop a SIP implementation.
Use dispatch <at> ietf.org for new developments on the application of sip.
Use sipcore <at> ietf.org for issues related to maintenance of the core SIP specifications.
(Continue reading)

Permalink | Reply |

Gmane