Subject: [AVT] FW: New Version Notification for draft-ietf-avt-ports-for-ucast-mcast-rtp-09

From: "Ali C. Begen (abegen)" <[email-masked]>
Date: Tue, 14 Dec 2010 17:21:53 -0800

Here is the -09 version for the Token draft.

Diff:
https://datatracker.ietf.org/doc/draft-ietf-avt-ports-for-ucast-mcast-rtp/history/ 

- We re-structured section 3 based on Magnus' comments. Hopefully, it reads better now.
- We clarified some requirements (see section 3.2)
- Token elements are now 32-bit aligned
- Token Verification Failure message now indicates the PT and FMT values for the RTCP message that caused the failure. This lets the client know which message needs a valid token.
- 'portmapping-req' is now only media-level attribute
- Section 7.1 was re-worded in some places for clarification
- Some typos were fixed.

We will use this version as the baseline for the call on Thursday.

Thanks.
-acbegen

-----Original Message-----
From: IETF I-D Submission Tool [mailto:[email-masked]] 
Sent: Tuesday, December 14, 2010 8:15 PM
To: Ali C. Begen (abegen)
Cc: Dan Wing (dwing); [email-masked]
Subject: New Version Notification for draft-ietf-avt-ports-for-ucast-mcast-rtp-09 

A new version of I-D, draft-ietf-avt-ports-for-ucast-mcast-rtp-09.txt has been successfully submitted by Ali Begen and posted to the IETF repository.

Filename:	 draft-ietf-avt-ports-for-ucast-mcast-rtp
Revision:	 09
Title:		 Port Mapping Between Unicast and Multicast RTP Sessions
Creation_date:	 2010-12-14
WG ID:		 avt
Number_of_pages: 33

Abstract:
This document presents a port mapping solution that allows RTP
receivers to choose their own ports for an auxiliary unicast session
in RTP applications using both unicast and multicast services.  The
solution provides protection against denial-of-service or packet
amplification attacks that could be used to cause one or more RTP
packets to be sent to a victim client.

The IETF Secretariat.