[MMUSIC] [mmusic] #2: Rules for Answerer payload type selection

"mmusic issue tracker" <trac+mmusic@trac.tools.ietf.org> Tue, 22 November 2011 08:47 UTC

Return-Path: <trac+mmusic@trac.tools.ietf.org>
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 8821021F8D4D for <mmusic@ietfa.amsl.com>; Tue, 22 Nov 2011 00:47:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qZjZjxjvAzRR for <mmusic@ietfa.amsl.com>; Tue, 22 Nov 2011 00:47:55 -0800 (PST)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 6D79321F8D43 for <mmusic@ietf.org>; Tue, 22 Nov 2011 00:47:55 -0800 (PST)
Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+mmusic@trac.tools.ietf.org>) id 1RSm1C-0006qT-M4; Tue, 22 Nov 2011 03:47:54 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: mmusic issue tracker <trac+mmusic@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: hkaplan@acmepacket.com
X-Trac-Project: mmusic
Date: Tue, 22 Nov 2011 08:47:54 -0000
X-URL: http://tools.ietf.org/mmusic/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/mmusic/trac/ticket/2
Message-ID: <063.2ea57b41e0be5050c487b56fc2e0d848@trac.tools.ietf.org>
X-Trac-Ticket-ID: 2
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: hkaplan@acmepacket.com, mmusic@ietf.org
X-SA-Exim-Mail-From: trac+mmusic@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false
X-Mailman-Approved-At: Tue, 22 Nov 2011 00:52:43 -0800
Cc: mmusic@ietf.org
Subject: [MMUSIC] [mmusic] #2: Rules for Answerer payload type selection
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 08:47:58 -0000

#2: Rules for Answerer payload type selection

 From Magnus:

 Section 5.4
 I am missing clear rules for the cases when I might exclude payload
 types from loopback-mode attributes compared to the m= lines. Are this
 only the loopback payload types? What happens if I exclude a regular
 media payload format?

-- 
-----------------------------+------------------------
 Reporter:  hkaplan@…        |      Owner:  hkaplan@…
     Type:  defect           |     Status:  new
 Priority:  major            |  Milestone:  milestone1
Component:  media-loopback   |    Version:  1.0
 Severity:  In WG Last Call  |   Keywords:
-----------------------------+------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/mmusic/trac/ticket/2>
mmusic <http://tools.ietf.org/mmusic/>