Return-Path: X-Original-To: mmusic@ietfa.amsl.com Delivered-To: mmusic@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A462128DF6 for ; Mon, 27 Mar 2017 23:43:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 lMU70Hxwspqg for ; Mon, 27 Mar 2017 23:43:23 -0700 (PDT) Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E542126C89 for ; Mon, 27 Mar 2017 23:43:23 -0700 (PDT) Received: by mail-qk0-x22a.google.com with SMTP id p22so57725450qka.3 for ; Mon, 27 Mar 2017 23:43:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xSJbo4Zuyr448kFhoIENHpe9XuzZmHAaX6TWlQ0jr4Y=; b=rcBdBQ9mnqEdUAV7FVI7NoL5DeWdwOpEHvKY20MJD2brvcqkUakWtXu+DGN2Gf9Xcq OriMq8tQuwWH2wAgAQoyn+OPmWbyhDHYck2UneMANUJMOqBchs/7wq3DBlPPRj+VdWFA z5BfNmV4U6RmmQut/B1+OdxLVvsP9h6AaKk+8S+cA+/WozqajDv2t0W3Eb0o01Ee3G91 2R5wrqRrrtUkw3UB2Oi4oLK49jgCbfJ/jYzO/9YrwNV4a/c+ZtwMDNsizMfZdspIt0jP wkKORiELuAtCX0KrkKNlTJh8k4a6OKdkN47FakO2MZpz5SMdsYU9rR/GR11IYRWYi22g kBrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xSJbo4Zuyr448kFhoIENHpe9XuzZmHAaX6TWlQ0jr4Y=; b=O7aVMhSfADwdrDvlAujgmyARtZeUNUxUyD3axfhw4QwxZf693AETkhbXLLb92/5wWd nKPAxoi6PCaZXEQ07Lnbm5A8yQ/15kCPJt+AizberXJDUV8getvGt0n7B+ZkydMGhPfQ M/Q9PMAbvniyBOksynJkZQ3XzR8jfTnfTeY5hseM7c+dU6VzhDL+sll+0LFIRh+ki5jb St9xjGhQy8BxQe0qEX52NjPJQKJ8NkvsW9kAoQK1bciq8SkI6KlpCrLYlCwhJl8/Xgb1 wEaZMkUveOW4flvFWrZ/DcYH2Fz9LTXQQEnNSK+vcQFgeZFT0oj0OoSqOKRgmBdjL2ei CySw== X-Gm-Message-State: AFeK/H0Dd3AAjKIBNbi5zd03ZBqfz+2PlLpakIkt9hhR9BA9f5IWeGEiCVRH22TtV66/LSDyfUsal2oBQsJdGw== X-Received: by 10.55.105.6 with SMTP id e6mr22866574qkc.252.1490683402201; Mon, 27 Mar 2017 23:43:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.46.165 with HTTP; Mon, 27 Mar 2017 23:43:21 -0700 (PDT) In-Reply-To: References: <279829dc-201f-25ab-0d1b-9958fb98682f@gmail.com> <59edda63-a02a-b685-fede-91f4cc292037@comcast.net> From: Suhas Nandakumar Date: Tue, 28 Mar 2017 01:43:21 -0500 Message-ID: To: "Mo Zanaty (mzanaty)" Cc: Paul Kyzivat , "mmusic@ietf.org" Content-Type: multipart/alternative; boundary=001a11487338a96c3f054bc4c664 Archived-At: Subject: Re: [MMUSIC] "a=extmap" with BUNDLE X-BeenThere: mmusic@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Multiparty Multimedia Session Control Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 06:43:25 -0000 --001a11487338a96c3f054bc4c664 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Since extmap is currently categorized under category of SPECIAL, at the minimum we need BUNDLE draft to describe its behavior for MID RTP Header extension under multiplexing, if it is not already doing so On Tue, Mar 28, 2017 at 1:20 AM, Mo Zanaty (mzanaty) wrote: > The issue is uniqueness of the extmap id for mid not the mid value itself > (identification-tag). > > Mo > > On Mar 27, 2017, at 10:38 PM, Paul Kyzivat > wrote: > > On 3/27/17 7:08 PM, I=C3=B1aki Baz Castillo wrote: > > > So IMHO, the immediate issue is in BUNDLE spec [*] which defines the > > MID stuff but does not mandate the MID ID to be unique in the whole > > SDP. > > This is already required by section 4 of RFC5888: > > The identification-tag MUST be unique within an SDP session > description. > > Thanks, > Paul > > _______________________________________________ > mmusic mailing list > mmusic@ietf.org > https://www.ietf.org/mailman/listinfo/mmusic > > _______________________________________________ > mmusic mailing list > mmusic@ietf.org > https://www.ietf.org/mailman/listinfo/mmusic > --001a11487338a96c3f054bc4c664 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Since extmap is currently categorized under category of SP= ECIAL, at the minimum we need BUNDLE draft to describe its behavior for MID= RTP Header extension under multiplexing, if it is not already doing so


On Tue, Mar 28, 2017 at 1:20 AM, Mo Zanaty (mzanaty) <mza= naty@cisco.com> wrote:
The = issue is uniqueness of the extmap id for mid not the mid value itself (iden= tification-tag).

Mo

On Mar 27, 2017, at 10:38 PM, Paul Kyzivat <paul.kyzivat@comcast.net> wrote:

On 3/27/17 7:08 PM, I=C3=B1aki Baz Castillo wrote:

> So IMHO, the immediate issue is in BUNDLE spec [*] which defines the > MID stuff but does not mandate the MID ID to be unique in the whole > SDP.

This is already required by section 4 of RFC5888:

=C2=A0 The identification-tag MUST be unique within an SDP session
=C2=A0 description.

=C2=A0 =C2=A0Thanks,
=C2=A0 =C2=A0Paul

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic

--001a11487338a96c3f054bc4c664--