rfc-editor | 1 Jun 01:00 2011

RFC 6236 on Negotiation of Generic Image Attributes in the Session Description Protocol (SDP)


A new Request for Comments is now available in online RFC libraries.

        
        RFC 6236

        Title:      Negotiation of Generic Image Attributes 
                    in the Session Description Protocol (SDP) 
        Author:     I. Johansson, K. Jung
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2011
        Mailbox:    ingemar.s.johansson <at> ericsson.com, 
                    kyunghun.jung <at> samsung.com
        Pages:      23
        Characters: rfc6236
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mmusic-image-attributes-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6236.txt

This document proposes a new generic session setup attribute to make
it possible to negotiate different image attributes such as image
size.  A possible use case is to make it possible for a %low-end %hand-
held terminal to display video without the need to rescale the image,
something that may consume large amounts of memory and processing
power.  The document also helps to maintain an optimal bitrate for
video as only the image size that is desired by the receiver is
transmitted.  [STANDARDS-TRACK]
(Continue reading)

Cristina Pascual | 1 Jun 03:10 2011
Picon

Last Mile, June 5th | CfP: VALID 2011 || October 23-28, 2011 - Barcelona, Spain


INVITATION:

=================
Please consider to contribute to and/or forward to the appropriate groups the following opportunity to
submit and publish original scientific results.
The submission deadline is June 5, 2011
In addition, authors of selected papers will be invited to submit extended article versions to one of the
IARIA Journals: http://www.iariajournals.org
=================

============== VALID 2011 | Call for Papers ===============

CALL FOR PAPERS, TUTORIALS, PANELS

VALID 2011: The Third International Conference on Advances in System Testing and Validation Lifecycle

October 23-28, 2011 - Barcelona, Spain

General page: http://www.iaria.org/conferences2011/VALID11.html

Call for Papers: http://www.iaria.org/conferences2011/CfPVALID11.html

- regular papers
- short papers (work in progress)
- posters

Submission page: http://www.iaria.org/conferences2011/SubmitVALID11.html

Submission deadline: June 5th, 2011
(Continue reading)

Cristina Pascual | 1 Jun 03:34 2011
Picon

Last Mile, June 5th | CfP: SIMUL 2011 || October 23-28, 2011 - Barcelona, Spain


INVITATION:

=================
Please consider to contribute to and/or forward to the appropriate groups the following opportunity to
submit and publish original scientific results.
The submission deadline is June 5, 2011.
In addition, authors of selected papers will be invited to submit extended article versions to one of the
IARIA Journals: http://www.iariajournals.org
=================

============== SIMUL 2011 | Call for Papers ===============

CALL FOR PAPERS, TUTORIALS, PANELS

SIMUL 2011: The Third International Conference on Advances in System Simulation
October 23-28, 2011 - Barcelona, Spain

General page: http://www.iaria.org/conferences2011/SIMUL11.html

Call for Papers: http://www.iaria.org/conferences2011/CfPSIMUL11.html

- regular papers
- short papers (work in progress)
- posters

Submission page: http://www.iaria.org/conferences2011/SubmitSIMUL11.html

Submission deadline: June 5th, 2011

(Continue reading)

Ali C. Begen (abegen | 13 Jun 00:15 2011
Picon

Revised redundancy grouping semantics drafts

Hi everyone,

We revised the following two drafts:

https://datatracker.ietf.org/doc/draft-begen-mmusic-redundancy-grouping/
https://datatracker.ietf.org/doc/draft-begen-mmusic-temporal-interleaving/ 

Drafts are almost complete for your review. Problems regarding RTCP reporting have been addressed. I will
be forwarding this email to AVTCORE as well as there was a request that AVTCORE also reviewed these drafts.

Thanks.
-acbegen
Pasi Sarolahti | 15 Jun 09:42 2011
Picon
Picon

Reviewing draft-ietf-dccp-udpencap

Hi,

In DCCP WG we are soon concluding draft-ietf-dccp-udpencap ("Datagram Congestion Control Protocol
(DCCP) Encapsulation for NAT Traversal (DCCP-UDP)"). This draft has parts related to the work done in
MMUSIC (especially Section 5), and it was presented in the MMUSIC meeting in last IETF. The authors have
modified the text based on the input received, and we are now looking for volunteer(s) from MMUSIC to
review whether the new text (mostly in Section 5) looks ok, before moving forward with the draft.

The draft can be found at http://tools.ietf.org/html/draft-ietf-dccp-udpencap-08 

- Pasi

Miguel A. Garcia | 15 Jun 15:32 2011
Picon

Re: Reviewing draft-ietf-dccp-udpencap

A quick review of Section 5 of this document:

- I think it is a good idea to clearly indicate which SDP attributes are 
newly created and which ones are reused from other RFCs. I therefore 
recommend to add the following sentences somewhere to the corresponding 
sections:

5.3:
RFC 4145 [RFC4145] defines the "setup" attribute whose purpose is to 
indcate which of the end points should initiate the connection 
establishment. This document reuses the "setup" attribute to similarly 
indicate which end point initiates the DCCP-UDP connection establishment.

5.4:
RFC 5245 [RFC5245] defines the "candidate" attribute whose purpose is to 
provide one of many possible candidate addresses for communication. This 
document reuses the "candidate" attribute to indicate native or 
encapsulated candidate addresses

- In 5.2 last paragraph, I am missing some normative statements, for example:

If RTCP is multiplexed with RTP, endpoints MUST encode the DCCP port used 
for RTCP in the "rtcp" attribute specified in RFC 3605 [RFC3605]. An SDP 
offerer MAY indicate its willingnes to multiplex RTP and RTCP onto a 
single DCCP port by adding an "rtcp-mux" attribute as specified in RFC 
5761 [RFC5761]. If the answer also includes the "rtcp-mux" attribute (as 
per RFC 5761 [RFC5761]), then RTP and RTCP are multiplexed onto a single 
DCCP port, otherwise separate DCCP ports are used for RTP and RTCP.  In 
each case, only a single UDP port is used for the DCCP-UDP encapsulation.

(Continue reading)

Miguel A. Garcia | 16 Jun 08:09 2011
Picon

Unofficial WGLC for draft-salgueiro-mmusic-image-iana-registration-07.txt

This is to start a 4-week unofficial WGLC of the IANA registration of the 
image media type in SDP,

http://datatracker.ietf.org/doc/draft-salgueiro-mmusic-image-iana-registration/

This document is going to proceed through the individually submitted, 
AD-sponsored track. However, the draft came as a requirements of the 
MMUSIC WG, has been substantially reviewed in MMUSIC, therefore the 
chairs want to have a last review in the format of an unofficial WGLC.

Please review the draft, and send comments to the authors and the list. 
Even if you don't have comments because you are happy with the current 
document, please say so.

The deadline for receiving comments is July 14th.

/Miguel and Flemming
--

-- 
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain
Gorry Fairhurst | 16 Jun 09:42 2011
Picon
Picon

Re: [MMUSIC] Reviewing draft-ietf-dccp-udpencap


See in-line on dccp-service-code.

Gorry

On Wed, 15 Jun 2011, Miguel A. Garcia wrote:

> A quick review of Section 5 of this document:
>
> - I think it is a good idea to clearly indicate which SDP attributes are 
> newly created and which ones are reused from other RFCs. I therefore 
> recommend to add the following sentences somewhere to the corresponding 
> sections:
>
> 5.3:
> RFC 4145 [RFC4145] defines the "setup" attribute whose purpose is to indcate 
> which of the end points should initiate the connection establishment. This 
> document reuses the "setup" attribute to similarly indicate which end point 
> initiates the DCCP-UDP connection establishment.
>
> 5.4:
> RFC 5245 [RFC5245] defines the "candidate" attribute whose purpose is to 
> provide one of many possible candidate addresses for communication. This 
> document reuses the "candidate" attribute to indicate native or encapsulated 
> candidate addresses
>
>
[After re-reading this I note that this section speaks of "native" DCCP
whereas there was an earlier suggestion that this should be called 
"DCCP-STD", Colin and I should ensure this is consistent in the next 
(Continue reading)

Miguel A. Garcia | 16 Jun 10:28 2011
Picon

Re: [dccp] Reviewing draft-ietf-dccp-udpencap

Hi Gorry:

Your suggestions look ok to me.

BR,

        Miguel

On 16/06/2011 9:42, Gorry Fairhurst wrote:
>
> See in-line on dccp-service-code.
>
> Gorry
>
> On Wed, 15 Jun 2011, Miguel A. Garcia wrote:
>
>> A quick review of Section 5 of this document:
>>
>> - I think it is a good idea to clearly indicate which SDP attributes are
>> newly created and which ones are reused from other RFCs. I therefore
>> recommend to add the following sentences somewhere to the corresponding
>> sections:
>>
>> 5.3:
>> RFC 4145 [RFC4145] defines the "setup" attribute whose purpose is to indcate
>> which of the end points should initiate the connection establishment. This
>> document reuses the "setup" attribute to similarly indicate which end point
>> initiates the DCCP-UDP connection establishment.
>>
>> 5.4:
(Continue reading)

Kevin P. Fleming | 16 Jun 17:10 2011

Re: Unofficial WGLC for draft-salgueiro-mmusic-image-iana-registration-07.txt

On 06/16/2011 01:09 AM, Miguel A. Garcia wrote:
> This is to start a 4-week unofficial WGLC of the IANA registration of
> the image media type in SDP,
>
> http://datatracker.ietf.org/doc/draft-salgueiro-mmusic-image-iana-registration/
>
>
> This document is going to proceed through the individually submitted,
> AD-sponsored track. However, the draft came as a requirements of the
> MMUSIC WG, has been substantially reviewed in MMUSIC, therefore the
> chairs want to have a last review in the format of an unofficial WGLC.
>
> Please review the draft, and send comments to the authors and the list.
> Even if you don't have comments because you are happy with the current
> document, please say so.

I have already reviewed this document and am satisfied it should proceed 
through the process.

--

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming <at> digium.com | SIP: kpfleming <at> digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org

Gmane