Re: [Stox] I-D Action: draft-ietf-stox-im-04.txt

Peter Saint-Andre <> Thu, 03 October 2013 01:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C41F921F9E9D for <>; Wed, 2 Oct 2013 18:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.729
X-Spam-Status: No, score=-101.729 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_MLH_Stock1=0.87, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5711+6IlgGm6 for <>; Wed, 2 Oct 2013 18:20:56 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D0FA521F9C4C for <>; Wed, 2 Oct 2013 18:19:26 -0700 (PDT)
Received: from ergon.local (unknown []) (Authenticated sender: stpeter) by (Postfix) with ESMTPSA id 16967414CD; Wed, 2 Oct 2013 19:25:03 -0600 (MDT)
Message-ID: <>
Date: Wed, 02 Oct 2013 15:44:29 -0700
From: Peter Saint-Andre <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Olle E. Johansson" <>
References: <> <> <>
In-Reply-To: <>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Subject: Re: [Stox] I-D Action: draft-ietf-stox-im-04.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 03 Oct 2013 01:21:06 -0000

Hash: SHA1

Hej Olle! Thanks for the feedback.

On 10/1/13 12:38 AM, Olle E. Johansson wrote:
> Hello, A few random notes:
> - Call-ID examples always have a domain in the call id in this
> draft.

Also in the presence draft.

> As the Call-ID is just a random string, I would prefer either 
> hostname to follow the requirements to make it globally unique, or 
> just a random string. I do not want developers to believe that 
> attaching a domain is recommended behaviour.

Will fix throughout the document suite (the groupchat I-D has some
examples with Call-ID values that are not globally unique, such as

> - Maybe some examples should include international character sets. 
> Julia says
> "Jag kommer, Romeo! Din skål jag dricker!"
> or Romeo:
> "Om jag får sömnens smicker-öga tro, Så bådar drömmen mig en 
> fröjdfull nyhet."
> This is still plain text, but not ASCII...

Not knowing Swedish, I usually use Czech for my examples. :-) But you
make a good point, and I always like to include non-ASCII examples
wherever possible.

> Table2: (But maybe this is back to core) - Translation of r-uri to 
> to: header thus overriding the To: header is something worth 
> discussing, if it hasn't been discussed yet. The SIP To: header is 
> the original destination of the message, and the R-uri is the
> current target.

Yes, I think that belongs in the core I-D.

> Additional notes:
> - A SIP MESSAGE can fork. The draft doesn't mention that,
> something that may have impact on implementations. There's a JID on
> one side - but a forking address on the other side of this spec. -
> A SIP MESSAGE can be delivered inside of a dialog and outside of a
> dialog. Inside of a dialog is maybe out of scope for this draft,
> but in that case the remote target will be a contact address, maybe
> even a GRUU.

Hmm, and here I thought we might be able to discuss forking only in
the media I-D. But I think you're right that we need to discuss it
here, too. What specification has the best coverage of forking? Or is
this part of the "oral tradition" in the SIP community?


- -- 
Peter Saint-Andre

Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools -
Comment: Using GnuPG with Thunderbird -