[webfinger] Fwd: [rfc-dist] RFC 7033 on WebFinger

"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Fri, 27 September 2013 22:09 UTC

Return-Path: <gsalguei@cisco.com>
X-Original-To: webfinger@ietfa.amsl.com
Delivered-To: webfinger@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C16D621F9E50; Fri, 27 Sep 2013 15:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level:
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, 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 EM6qqCUF9bSt; Fri, 27 Sep 2013 15:09:14 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id C6DBC21F8E51; Fri, 27 Sep 2013 15:09:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3078; q=dns/txt; s=iport; t=1380319754; x=1381529354; h=from:to:cc:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=RTsHxg6AO/eArGv9aWE0zEe/fvRvcd0kP5muWf+H2h0=; b=V02l1IRYwg2z6PFm0WqEhFH6i4IQJ4M5KfRAsDYlfMRCDMaLB7+A7H2b dEGRlcd937I1sEo4dAjtYepnfuDTIcOwJ9BQaPfUoJP6G5hzFpVzTHwGB aFyaBQVrTRHBA3FfQZB3IVZFNtEN+gvLHvbcLMpRNpM7rp2wyGbTgMs6i k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFACABRlKtJXHB/2dsb2JhbABBGoMHOFLAU4EhFnSCJQEBAQMBAQEBNxQgCwULAgEZAwECCwIJCRAnCgEbAggCBAENBQgBCwcCBIdfBgw2uVWOCA+BCTECCwSDFYEBA5kuiw+FOoMkgXE5
X-IronPort-AV: E=Sophos;i="4.90,996,1371081600"; d="scan'208";a="265472757"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-2.cisco.com with ESMTP; 27 Sep 2013 22:09:13 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r8RM9Cmh023868 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 27 Sep 2013 22:09:13 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.202]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Fri, 27 Sep 2013 17:09:12 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: webfinger <webfinger@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
Thread-Topic: [rfc-dist] RFC 7033 on WebFinger
Thread-Index: AQHOu8q8WK9MXW8PR0WCym9pkH25Xw==
Date: Fri, 27 Sep 2013 22:09:12 +0000
Message-ID: <D85334BB1373A34AA5FF84F9A623928A1F0C1498@xmb-aln-x04.cisco.com>
References: <20130927213711.8CCB5B1E00B@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.116.132.55]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B79EBBA198FBED458D7D2FD1265A55CC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "webfinger@googlegroups.com" <webfinger@googlegroups.com>
Subject: [webfinger] Fwd: [rfc-dist] RFC 7033 on WebFinger
X-BeenThere: webfinger@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <webfinger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webfinger>, <mailto:webfinger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/webfinger>
List-Post: <mailto:webfinger@ietf.org>
List-Help: <mailto:webfinger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webfinger>, <mailto:webfinger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2013 22:09:19 -0000

[Forgive the cross-post...]

Finally, we've arrived!   Thanks to the many of you who generously contributed.  An especially big shout out to Paul Jones for his passion and dedication, who as editor had the unenviable job of trying to appease everyone.

Cheers,

Gonzalo

Begin forwarded message:

> From: <rfc-editor@rfc-editor.org>
> Subject: [rfc-dist] RFC 7033 on WebFinger
> Date: September 27, 2013 5:37:11 PM EDT
> To: <ietf-announce@ietf.org>rg>, <rfc-dist@rfc-editor.org>
> Cc: <drafts-update-ref@iana.org>rg>, <apps-discuss@ietf.org>rg>, <rfc-editor@rfc-editor.org>
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>        RFC 7033
> 
>        Title:      WebFinger 
>        Author:     P. Jones, G. Salgueiro,
>                    M. Jones, J. Smarr
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       September 2013
>        Mailbox:    paulej@packetizer.com, 
>                    gsalguei@cisco.com, 
>                    mbj@microsoft.com,
>                    jsmarr@google.com
>        Pages:      28
>        Characters: 61552
>        Updates/Obsoletes/SeeAlso:   None
> 
>        I-D Tag:    draft-ietf-appsawg-webfinger-18.txt
> 
>        URL:        http://www.rfc-editor.org/rfc/rfc7033.txt
> 
> This specification defines the WebFinger protocol, which can be used
> to discover information about people or other entities on the
> Internet using standard HTTP methods.  WebFinger discovers
> information for a URI that might not be usable as a locator
> otherwise, such as account or email URIs.
> 
> This document is a product of the Applications Area Working Group 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
> 
> 
> _______________________________________________
> rfc-dist mailing list
> rfc-dist@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-dist
> http://www.rfc-editor.org