IETF Logo Mail Archive

Re: [dispatch] Announcing a MUC with RFC4575

Peter Saint-Andre <stpeter@stpeter.im> Mon, 22 April 2013 19:48 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D42321F9349 for <dispatch@ietfa.amsl.com>; Mon, 22 Apr 2013 12:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.252
X-Spam-Level:
X-Spam-Status: No, score=-102.252 tagged_above=-999 required=5 tests=[AWL=0.348, 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 A8AFbekqBwFK for <dispatch@ietfa.amsl.com>; Mon, 22 Apr 2013 12:48:29 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 87F9B21F9347 for <dispatch@ietf.org>; Mon, 22 Apr 2013 12:48:29 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7457341026; Mon, 22 Apr 2013 13:59:16 -0600 (MDT)
Message-ID: <5175940B.8050305@stpeter.im>
Date: Mon, 22 Apr 2013 13:48:27 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
References: <51744F5B.8010506@jitsi.org> <0BFDB465-BACA-4411-A8F8-203506EA0422@ag-projects.com> <C563F76EA324474CA3722A35154AFDB313A0692B@AZ-US1EXMB01.global.avaya.com> <51758E0A.6080801@jitsi.org> <C563F76EA324474CA3722A35154AFDB313A06FCC@AZ-US1EXMB01.global.avaya.com>
In-Reply-To: <C563F76EA324474CA3722A35154AFDB313A06FCC@AZ-US1EXMB01.global.avaya.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, Emil Ivov <emcho@jitsi.org>
Subject: Re: [dispatch] Announcing a MUC with RFC4575
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 19:48:30 -0000

On 4/22/13 1:36 PM, Shekh-Yusef, Rifaat (Rifaat) wrote:
>> Just to make sure I understand: are you suggesting that you could add an
>> impp purpose for service-uris in the above document?
>>
>> If so, then this certainly works for me!
> 
> No, that is not what I am suggesting.
> What I am saying is that when you create your document to define your impp, you can register the new purpose value in the same document in the IANA section, similar to what we did in section 4 of our CCMP document.

https://datatracker.ietf.org/doc/draft-saintandre-impp-call-info/
registers the "impp" value for Call-Info, but not for other message
header fields.

Peter

v2.23.0 | Report a Bug | By Email