Re: [bfcpbis] Data type clarifications of Conference ID + User ID
"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Mon, 26 March 2012 09:09 UTC
Return-Path: <eckelcu@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E155E21F858F for <bfcpbis@ietfa.amsl.com>; Mon, 26 Mar 2012 02:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.437
X-Spam-Level:
X-Spam-Status: No, score=-9.437 tagged_above=-999 required=5 tests=[AWL=1.162, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 UH2-r7IlFXey for <bfcpbis@ietfa.amsl.com>; Mon, 26 Mar 2012 02:09:18 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 34F1C21F85AD for <bfcpbis@ietf.org>; Mon, 26 Mar 2012 02:09:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=1278; q=dns/txt; s=iport; t=1332752958; x=1333962558; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=QMz1xCpChk7HKTJa6YeHSwbQ70bDS1xTDlGV/Fo71Dc=; b=DKguYUiBXaGXmb0WrrX/lwRu3fD3CD2wVU4HJ6qjW3D/1GuM4TMlZ9K/ Znz84mTV9f/NbFKUb8Vh7G/BgkVWzifB74KtzBQm5jQJi646rZ7oyIAgm 2b1H6YK9hszNlHJC3BXr+cFMnZQnPjDWkfTF+HwvdyfSXGCSjAQAQqowE A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAOExcE+rRDoJ/2dsb2JhbABCAoU/sXGBAIEHggkBAQEEEgEQDQQzAR0EAgEIEQQBAQMCBgYGEQECAgIBAUQJCAEBBAESCBqHZwGaHo0IkTOBL4xRCwGCBDVjBIhXm06BaIMH
X-IronPort-AV: E=Sophos;i="4.73,649,1325462400"; d="scan'208";a="37558919"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 26 Mar 2012 09:09:17 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q2Q99HHZ020929 for <bfcpbis@ietf.org>; Mon, 26 Mar 2012 09:09:17 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 26 Mar 2012 02:09:17 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Mon, 26 Mar 2012 02:09:16 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06B24A4F@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <4F6C7BFB.5060705@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [bfcpbis] Data type clarifications of Conference ID + User ID
Thread-Index: Ac0I+cAOBwKRSaqSTBOaz6uQHpbk1wCNfYrA
References: <4F6C7BFB.5060705@cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Kristoffer Gleditsch (kgledits)" <kgledits@cisco.com>, bfcpbis@ietf.org
X-OriginalArrivalTime: 26 Mar 2012 09:09:17.0795 (UTC) FILETIME=[1F78AB30:01CD0B30]
Subject: Re: [bfcpbis] Data type clarifications of Conference ID + User ID
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 09:09:19 -0000
Hi Kristoffer, The clarifications you have proposed all look helpful to me. I would be happy to see them adopted in the drafts being worked within this group. Cheers, Charles (as an individual) > -----Original Message----- > From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On > Behalf Of Kristoffer Gleditsch (kgledits) > Sent: Friday, March 23, 2012 2:35 PM > To: bfcpbis@ietf.org > Subject: [bfcpbis] Data type clarifications of Conference ID + User ID > > Hi! > > See the attached diffs to the 4582bis and 4853bis drafts. > > The motivation of the 4582bis change is to make sure nobody thinks > Conference ID = -42 is legal. (I left Transaction ID as it was, since > it carries no meaning apart from uniqueness.) > > The motivation of the 4583bis change is to make sure nobody thinks they > can put "a=userid: 0xa" in the SDP to express User ID = 10. > > Regards, > Kristoffer
- [bfcpbis] Data type clarifications of Conference … Kristoffer Gleditsch
- Re: [bfcpbis] Data type clarifications of Confere… Charles Eckel (eckelcu)
- Re: [bfcpbis] Data type clarifications of Confere… Tom Kristensen