IETF Logo Mail Archive

Re: [AVTCORE] comment on draft-jones-avtcore-private-media-reqts-00

"Nermeen Ismail (nermeen)" <nermeen@cisco.com> Tue, 11 November 2014 20:34 UTC

Return-Path: <nermeen@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460271A913F for <avt@ietfa.amsl.com>; Tue, 11 Nov 2014 12:34:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.094
X-Spam-Level:
X-Spam-Status: No, score=-15.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tcm4MHajdsoS for <avt@ietfa.amsl.com>; Tue, 11 Nov 2014 12:34:54 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91A751A9169 for <avt@ietf.org>; Tue, 11 Nov 2014 12:34:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7446; q=dns/txt; s=iport; t=1415738086; x=1416947686; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=N/mZAW6KU0Y+1vC4g0fIvm3d8vaDPd/HNFBuCqLfdMI=; b=cfS82a9bnoHIyxoclv17uKVJHZwKv41uBJxjqclv2OXfXJRoIcRTmrOA dbQP+UD22koF4rVIkPGNPG+iA+r4pcLefRR+on1p7QbmiMaovBvKRx5fm 8x2r9s4hS+ihdk+oVgpxo9TfiBOrSiLps6VxCk+zoE+KAxBzpWvqL5ZFM k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAA1yYlStJA2G/2dsb2JhbABcgkhGVFkE03ICgRoWAQEBAQF9hAIBAQEELVwCAQgOAwMBAigHIREUCQgBAQQBEogsAxLIWg2GbgEBAQEBAQEBAQEBAQEBAQEBAQEBAReOW4IoGIRLBZIxhxqCSIISgTSHAYZ4QoZxg3psAYFHgQMBAQE
X-IronPort-AV: E=Sophos; i="5.07,362,1413244800"; d="scan'208,217"; a="95638291"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-4.cisco.com with ESMTP; 11 Nov 2014 20:34:46 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id sABKYjIH016803 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Nov 2014 20:34:45 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.140]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Tue, 11 Nov 2014 14:34:45 -0600
From: "Nermeen Ismail (nermeen)" <nermeen@cisco.com>
To: Roni Even <ron.even.tlv@gmail.com>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVTCORE] comment on draft-jones-avtcore-private-media-reqts-00
Thread-Index: Ac/8AM30dqCj22AMSXWfBEZAXi5T1wBzVIYA
Date: Tue, 11 Nov 2014 20:34:45 +0000
Message-ID: <D0879525.1FACC%nermeen@cisco.com>
References: <00db01cffc02$d2420570$76c61050$@gmail.com>
In-Reply-To: <00db01cffc02$d2420570$76c61050$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [10.21.78.251]
Content-Type: multipart/alternative; boundary="_000_D08795251FACCnermeenciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/WKN4sLga6hMv-BSm-SeapQC2qRI
Subject: Re: [AVTCORE] comment on draft-jones-avtcore-private-media-reqts-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 11 Nov 2014 20:34:58 -0000

PM-07 attempts to capture ,among other things, the sequence number gap requirement during a switch from one media source to another. In order to synchronize the SRTP context either the receiver need to be aware of the source switch and the sequence number associated with the new source need to be updated or the server needs to shield the receiver from such sequence number gaps. In either case the receiver will not be perceiving packet losses during the switch.

Do you think we need to explicitly mention the packet loss issue during a media source switch or do you think that the synchronization of the SRTP context capture it albeit in an implicit way?

nermeen



From: Roni Even <ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>>
Date: Saturday, November 8, 2014 11:51 PM
To: "avt@ietf.org<mailto:avt@ietf.org>" <avt@ietf.org<mailto:avt@ietf.org>>
Subject: [AVTCORE] comment on draft-jones-avtcore-private-media-reqts-00

Hi guys,
I read the document and was wondering which of the topologies in draft-ietf-avtcore-rtp-topologies-update-04 is used here (figure 3). Is it the selective forward middlebox. It will be good to either use the same terminology or if it is a different topology define it in the topology draft.
As for the sequence number, when using example in figure 3 , each RTP stream received (from the same SSRC) may have a gap in the sequence number or the receiver may report a loss for a stream switched out by the midlebox? Any requirement here?

Thanks
Roni Even

v2.23.0 | Report a Bug | By Email