Re: [sipcore] Congratulations! draft-barnes-sipcore-rfc4244bis is now RFC 7044

Mary Barnes <mary.ietf.barnes@gmail.com> Fri, 07 February 2014 19:36 UTC

Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 967031ACCE3 for <sipcore@ietfa.amsl.com>; Fri, 7 Feb 2014 11:36:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TZGzS4UH2IJv for <sipcore@ietfa.amsl.com>; Fri, 7 Feb 2014 11:36:50 -0800 (PST)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 9BFA41A0465 for <sipcore@ietf.org>; Fri, 7 Feb 2014 11:36:50 -0800 (PST)
Received: by mail-ie0-f179.google.com with SMTP id ar20so1949336iec.10 for <sipcore@ietf.org>; Fri, 07 Feb 2014 11:36:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=G8DujM8VWzKMDES/NqgF6UERTAoSp/B1Vz8bbqkL2Ts=; b=h0+bh0sSef9B8DQI0OK0+LUaa0Orou+u3NdKWztmR2k3mjV1TdmMsJdV+ARUsmGGFM diLlGNhmm1zBgfjqnnAaR0fMO570IuQDwh3kWKU8VowB+1tXGEzz+mUyp9RnVQ78vvA9 fjALJ1zKep4CaA0VFEG/XdwI7uuyCBh5uumOYwwcqg4lhwqQz8rToKVw9c8wOboC1S6/ QkMr5PVIhzkCKFfBSx7QrKZ5KWdr5KC6Yz1IqNqfo+LdOHcHF+fXCXDfdUTzzT2dtKOl A85hxics5SYWqP++nCjRRURIM80UFfXe2BJ8Rp2MXa/NrxoStPl+JKMA55e/zyPK85e7 Y2cg==
MIME-Version: 1.0
X-Received: by 10.42.40.83 with SMTP id k19mr8518981ice.3.1391801810495; Fri, 07 Feb 2014 11:36:50 -0800 (PST)
Received: by 10.43.58.137 with HTTP; Fri, 7 Feb 2014 11:36:50 -0800 (PST)
In-Reply-To: <52F14093.9040506@alum.mit.edu>
References: <20140204191557.7CAF67FC159@rfc-editor.org> <52F14093.9040506@alum.mit.edu>
Date: Fri, 07 Feb 2014 13:36:50 -0600
Message-ID: <CAHBDyN5HQGwimeM+8_TFvHPggBAJ5G=aGr8gRNy0VdLete3qhw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary="90e6ba1efbf4832b4c04f1d61c7c"
Cc: SIPCORE <sipcore@ietf.org>
Subject: Re: [sipcore] Congratulations! draft-barnes-sipcore-rfc4244bis is now RFC 7044
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 07 Feb 2014 19:36:53 -0000

Yes, a huge sigh of relief!   Thanks to the WG for their patience and to
Dale for his numerous reviews and comments.

Mary.


On Tue, Feb 4, 2014 at 1:33 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> This was a long haul.
> Thanks to the authors for all their work.
> Now we can all join them in giving a huge sigh of relief.
>
>         Thanks,
>         Paul
>
> On 2/4/14 2:15 PM, rfc-editor@rfc-editor.org wrote:
>
>> A new Request for Comments is now available in online RFC libraries.
>>
>>
>>          RFC 7044
>>
>>          Title:      An Extension to the Session
>>                      Initiation Protocol (SIP) for
>>                      Request History Information
>>          Author:     M. Barnes, F. Audet,
>>                      S. Schubert, J. van Elburg,
>>                      C. Holmberg
>>          Status:     Standards Track
>>          Stream:     IETF
>>          Date:       February 2014
>>          Mailbox:    mary.ietf.barnes@gmail.com,
>>                      francois.audet@skype.net,
>>                      shida@ntt-at.com,
>>                      ietf.hanserik@gmail.com,
>>                      christer.holmberg@ericsson.com
>>          Pages:      36
>>          Characters: 85068
>>          Obsoletes:  RFC 4244
>>
>>          I-D Tag:    draft-ietf-sipcore-rfc4244bis-12.txt
>>
>>          URL:        http://www.rfc-editor.org/rfc/rfc7044.txt
>>
>> This document defines a standard mechanism for capturing the history
>> information associated with a Session Initiation Protocol (SIP)
>> request.  This capability enables many enhanced services by providing
>> the information as to how and why a SIP request arrives at a specific
>> application or user.  This document defines an optional SIP header
>> field, History-Info, for capturing the history information in
>> requests.  The document also defines SIP header field parameters for
>> the History-Info and Contact header fields to tag the method by which
>> the target of a request is determined.  In addition, this
>> specification defines a value for the Privacy header field that
>> directs the anonymization of values in the History-Info header field.
>> This document obsoletes RFC 4244.
>>
>> This document is a product of the Session Initiation Protocol Core
>> Working Group of the IETF.
>>
>> This is now a Proposed Standard.
>>
>> STANDARDS TRACK: This document specifies an Internet standards track
>> protocol for the Internet community,and requests discussion and
>> suggestions
>> for improvements.  Please refer to the current edition of the Internet
>> Official Protocol Standards (STD 1) for the standardization state and
>> status of this protocol.  Distribution of this memo is unlimited.
>>
>> This announcement is sent to the IETF-Announce and rfc-dist lists.
>> To subscribe or unsubscribe, see
>>    http://www.ietf.org/mailman/listinfo/ietf-announce
>>    http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>
>> For searching the RFC series, see http://www.rfc-editor.org/
>> search/rfc_search.php
>> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>>
>> Requests for special distribution should be addressed to either the
>> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
>> specifically noted otherwise on the RFC itself, all RFCs are for
>> unlimited distribution.
>>
>>
>> The RFC Editor Team
>> Association Management Solutions, LLC
>>
>>
>> _______________________________________________
>> sipcore mailing list
>> sipcore@ietf.org
>> https://www.ietf.org/mailman/listinfo/sipcore
>>
>>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>