[sipcore] Updated 4244bis and new call flow document
Mary Barnes <mary.ietf.barnes@gmail.com> Thu, 24 June 2010 20:11 UTC
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 027D93A6A63 for <sipcore@core3.amsl.com>; Thu, 24 Jun 2010 13:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level:
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Auh6QEdw-l9M for <sipcore@core3.amsl.com>; Thu, 24 Jun 2010 13:11:13 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id 96B9D3A6A5E for <sipcore@ietf.org>; Thu, 24 Jun 2010 13:11:13 -0700 (PDT)
Received: by pzk36 with SMTP id 36so445097pzk.31 for <sipcore@ietf.org>; Thu, 24 Jun 2010 13:11:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=G/f5/FwC8vlGSe83tNgxpwe1FoUY24toPXiUpuU4Y4g=; b=r1iOOzGkTpOInb63TZo2m1DvB18Ts4cafmuePZshiwDs7P130DLBw86RQ6jaoISi7z FtW4ms8GyV1nLvUaHmmEvPncvo/e+J5Y21GbPXIkuthyES+KhkNjdMtdkO+7PtS1UdF2 d/HrSc3dsTY0NwrFOUUB0PXLhyjwVROoKhk+E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=P+U1giDV08vNI+k+3QrpTNazW76xDV3RXb6FXkDAyT48EzLiee09q8iZ+zE/PkY+P1 TiuCQ+nb4VktErrEh1outgRi56nKiragYylx2WzYcoqXdi1P0c2lGu5vbQXAdYaHEG0k vtil+a+UIRDYBzjXYvAvJMm7XsapsCKUjcp9w=
MIME-Version: 1.0
Received: by 10.114.237.3 with SMTP id k3mr10189429wah.219.1277410279566; Thu, 24 Jun 2010 13:11:19 -0700 (PDT)
Received: by 10.231.146.206 with HTTP; Thu, 24 Jun 2010 13:11:19 -0700 (PDT)
Date: Thu, 24 Jun 2010 15:11:19 -0500
Message-ID: <AANLkTim-f7vZ1IFS3WhVS9G8Mg1dhueN8tevLb_xDRR1@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: SIPCORE <sipcore@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [sipcore] Updated 4244bis and new call flow document
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 20:11:15 -0000
Hi folks, The 4244bis draft has been updated and a separate call flow document created per the earlier summary of proposed changes: http://www.ietf.org/mail-archive/web/sipcore/current/msg02647.html http://www.ietf.org/id/draft-ietf-sipcore-rfc4244bis-01.txt http://www.ietf.org/id/draft-barnes-sipcore-rfc4244bis-callflows-00.txt There are two voicemail examples in the new call flow document. The 4244bis has 3 call flows - the basic sequential forking and two privacy examples. All the rest are now in the call flow document. The other changes we made were updates to the UAC, UAS and application considerations section - adding additional text as to how the UAC and UAS process hi-entries (including related to responses). The application considerations section now describes how the tags can be used to derive specific information and the past guidelines were removed since 4244bis has much definitive guidance on the normative aspects of the header (i.e., SHOULDs replaced with MUSTs, privacy via anonymization rather than removing entries, etc.) as summarized in Section 11. Please review and provide any additional comments. We believe that 4244bis is pretty much ready to go. We can fine tune the details in the call flows and should be able to get that ready very soon, as well. Let us know if you see additional use cases you would like to add. Thanks, Mary et al
- [sipcore] Updated 4244bis and new call flow docum… Mary Barnes
- Re: [sipcore] Updated 4244bis and new call flow d… Mary Barnes
- Re: [sipcore] Updated 4244bis and new call flow d… R.Jesske
- Re: [sipcore] Updated 4244bis and new call flow d… Paul Kyzivat
- Re: [sipcore] Updated 4244bis and new call flow d… DRAGE, Keith (Keith)
- Re: [sipcore] Updated 4244bis and new call flow d… Paul Kyzivat
- Re: [sipcore] Updated 4244bis and new call flow d… marianne.mohali
- Re: [sipcore] Updated 4244bis and new call flow d… Mary Barnes
- Re: [sipcore] Updated 4244bis and new call flow d… Shida Schubert
- Re: [sipcore] Updated 4244bis and new call flow d… DRAGE, Keith (Keith)
- Re: [sipcore] Updated 4244bis and new call flow d… Mary Barnes
- Re: [sipcore] Updated 4244bis and new call flow d… Mary Barnes