
From gsalguei@cisco.com  Fri Sep 27 15:09:18 2013
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 contribu=
ted.  An especially big shout out to Paul Jones for his passion and dedicat=
ion, 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>, <rfc-dist@rfc-editor.org>
> Cc: <drafts-update-ref@iana.org>, <apps-discuss@ietf.org>, <rfc-editor@rf=
c-editor.org>
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>=20
>        RFC 7033
>=20
>        Title:      WebFinger=20
>        Author:     P. Jones, G. Salgueiro,
>                    M. Jones, J. Smarr
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       September 2013
>        Mailbox:    paulej@packetizer.com,=20
>                    gsalguei@cisco.com,=20
>                    mbj@microsoft.com,
>                    jsmarr@google.com
>        Pages:      28
>        Characters: 61552
>        Updates/Obsoletes/SeeAlso:   None
>=20
>        I-D Tag:    draft-ietf-appsawg-webfinger-18.txt
>=20
>        URL:        http://www.rfc-editor.org/rfc/rfc7033.txt
>=20
> 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.
>=20
> This document is a product of the Applications Area Working Group Working=
 Group of the IETF.
>=20
> This is now a Proposed Standard.
>=20
> STANDARDS TRACK: This document specifies an Internet standards track
> protocol for the Internet community,and requests discussion and suggestio=
ns
> 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.
>=20
> 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
>=20
> For searching the RFC series, see http://www.rfc-editor.org/search/rfc_se=
arch.php
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>=20
> 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.
>=20
>=20
> The RFC Editor Team
> Association Management Solutions, LLC
>=20
>=20
> _______________________________________________
> rfc-dist mailing list
> rfc-dist@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-dist
> http://www.rfc-editor.org


From Michael.Jones@microsoft.com  Fri Sep 27 15:42:48 2013
Return-Path: <Michael.Jones@microsoft.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 7F84211E8102; Fri, 27 Sep 2013 15:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_LOW=-1]
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 HOkgC0KPYN2c; Fri, 27 Sep 2013 15:42:43 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id 94B1811E80DE; Fri, 27 Sep 2013 15:42:43 -0700 (PDT)
Received: from BLUPR03CA028.namprd03.prod.outlook.com (10.141.30.21) by BLUPR03MB036.namprd03.prod.outlook.com (10.255.209.148) with Microsoft SMTP Server (TLS) id 15.0.775.9; Fri, 27 Sep 2013 22:42:42 +0000
Received: from BN1AFFO11FD039.protection.gbl (2a01:111:f400:7c10::195) by BLUPR03CA028.outlook.office365.com (2a01:111:e400:879::21) with Microsoft SMTP Server (TLS) id 15.0.775.9 via Frontend Transport; Fri, 27 Sep 2013 22:42:42 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1AFFO11FD039.mail.protection.outlook.com (10.58.52.243) with Microsoft SMTP Server (TLS) id 15.0.785.10 via Frontend Transport; Fri, 27 Sep 2013 22:42:41 +0000
Received: from TK5EX14MBXC290.redmond.corp.microsoft.com ([169.254.1.39]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.03.0136.001; Fri, 27 Sep 2013 22:41:52 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>, 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: AQHOu85GOj0585jG5Eq7Bb0S+TyY4JnaLa1Q
Date: Fri, 27 Sep 2013 22:41:50 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394371FFCE41@TK5EX14MBXC290.redmond.corp.microsoft.com>
References: <20130927213711.8CCB5B1E00B@rfc-editor.org> <D85334BB1373A34AA5FF84F9A623928A1F0C1498@xmb-aln-x04.cisco.com>
In-Reply-To: <D85334BB1373A34AA5FF84F9A623928A1F0C1498@xmb-aln-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(51704005)(199002)(189002)(377454003)(69234005)(13464003)(478834004)(16601075003)(77982001)(59766001)(20776003)(63696002)(15202345003)(66066001)(74706001)(15188155005)(81542001)(80022001)(65816001)(79102001)(83072001)(69226001)(56816003)(6806004)(50466002)(47776003)(16799955002)(19300405004)(81342001)(54356001)(23726002)(53806001)(56776001)(81816001)(15975445006)(74876001)(44976005)(76482001)(47976001)(50986001)(4396001)(80976001)(49866001)(51856001)(19580405001)(74502001)(47736001)(55846006)(19580395003)(83322001)(46102001)(31966008)(77096001)(54316002)(74366001)(47446002)(76786001)(76796001)(74662001)(81686001)(33656001)(46406003)(562404015)(6606295002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR03MB036; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 098291215C
X-OriginatorOrg: DuplicateDomain-a84fc36a-4ed7-4e57-ab1c-3e967bcbad48.microsoft.com
Cc: "webfinger@googlegroups.com" <webfinger@googlegroups.com>
Subject: Re: [webfinger] [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:42:48 -0000

FYI, I've posted about this at http://self-issued.info/?p=3D1125 and on Twi=
tter as @selfissued.

Have a good weekend, everyone!

                                                            -- Mike

-----Original Message-----
From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] =
On Behalf Of Gonzalo Salgueiro (gsalguei)
Sent: Friday, September 27, 2013 3:09 PM
To: webfinger; apps-discuss@ietf.org application-layer protocols
Cc: webfinger@googlegroups.com
Subject: [apps-discuss] Fwd: [rfc-dist] RFC 7033 on WebFinger

[Forgive the cross-post...]

Finally, we've arrived!   Thanks to the many of you who generously contribu=
ted.  An especially big shout out to Paul Jones for his passion and dedicat=
ion, 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>, <rfc-dist@rfc-editor.org>
> Cc: <drafts-update-ref@iana.org>, <apps-discuss@ietf.org>,=20
> <rfc-editor@rfc-editor.org>
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>=20
>        RFC 7033
>=20
>        Title:      WebFinger=20
>        Author:     P. Jones, G. Salgueiro,
>                    M. Jones, J. Smarr
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       September 2013
>        Mailbox:    paulej@packetizer.com,=20
>                    gsalguei@cisco.com,=20
>                    mbj@microsoft.com,
>                    jsmarr@google.com
>        Pages:      28
>        Characters: 61552
>        Updates/Obsoletes/SeeAlso:   None
>=20
>        I-D Tag:    draft-ietf-appsawg-webfinger-18.txt
>=20
>        URL:        http://www.rfc-editor.org/rfc/rfc7033.txt
>=20
> This specification defines the WebFinger protocol, which can be used=20
> to discover information about people or other entities on the Internet=20
> using standard HTTP methods.  WebFinger discovers information for a=20
> URI that might not be usable as a locator otherwise, such as account=20
> or email URIs.
>=20
> This document is a product of the Applications Area Working Group Working=
 Group of the IETF.
>=20
> This is now a Proposed Standard.
>=20
> STANDARDS TRACK: This document specifies an Internet standards track=20
> protocol for the Internet community,and requests discussion and=20
> suggestions for improvements.  Please refer to the current edition of=20
> the Internet Official Protocol Standards (STD 1) for the=20
> standardization state and status of this protocol.  Distribution of this =
memo is unlimited.
>=20
> 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
>=20
> For searching the RFC series, see=20
> http://www.rfc-editor.org/search/rfc_search.php
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>=20
> Requests for special distribution should be addressed to either the=20
> author of the RFC in question, or to rfc-editor@rfc-editor.org. =20
> Unless specifically noted otherwise on the RFC itself, all RFCs are=20
> for unlimited distribution.
>=20
>=20
> The RFC Editor Team
> Association Management Solutions, LLC
>=20
>=20
> _______________________________________________
> rfc-dist mailing list
> rfc-dist@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-dist
> http://www.rfc-editor.org

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss
