
From nobody Tue Sep  1 10:12:44 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B93D1B55B8; Tue,  1 Sep 2015 10:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 yXlsInY_9Ns8; Tue,  1 Sep 2015 10:12:40 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ADB921B55F8; Tue,  1 Sep 2015 10:12:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150901171239.15229.52617.idtracker@ietfa.amsl.com>
Date: Tue, 01 Sep 2015 10:12:39 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/Of-v-aU0WxPN2md3knToWPw96-4>
Cc: xmpp@ietf.org
Subject: [xmpp] I-D Action: draft-ietf-xmpp-posh-05.txt
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 17:12:41 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Extensible Messaging and Presence Protocol Working Group of the IETF.

        Title           : PKIX over Secure HTTP (POSH)
        Authors         : Matthew Miller
                          Peter Saint-Andre
	Filename        : draft-ietf-xmpp-posh-05.txt
	Pages           : 17
	Date            : 2015-09-01

Abstract:
   Experience has shown that it is difficult to deploy proper PKIX
   certificates for TLS in multi-tenant environments.  As a result,
   domains hosted in such environments often deploy applications using
   certificates that identify the hosting service, not the hosted
   domain.  Such deployments force end users and peer services to accept
   a certificate with an improper identifier, resulting in degraded
   security.  This document defines two methods that make it easier to
   deploy certificates for proper server identity checking in non-HTTP
   application protocols.  While these methods were developed for use in
   the Extensible Messaging and Presence Protocol (XMPP) as a Domain
   Name Association (DNA) prooftype, they might also be usable in other
   non-HTTP application protocols.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-xmpp-posh/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-xmpp-posh-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-posh-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Sep  1 10:16:26 2015
Return-Path: <mamille2@cisco.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D49711B5A5A; Tue,  1 Sep 2015 10:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.201
X-Spam-Level: 
X-Spam-Status: No, score=-14.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 G3G-eNbWngT8; Tue,  1 Sep 2015 10:16:19 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CF561B59BE; Tue,  1 Sep 2015 10:16:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8300; q=dns/txt; s=iport; t=1441127779; x=1442337379; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=yT39SgfmIAiCrfLuXCoQglxIIEWEtCeN142nVWFx26s=; b=hFfRcnibpJfVZksD77rLdB2K9t2E3gA0U0x02ihOXB9ovsY9uebe/KAk lG2rEA55t+B/08WNSm2olExcoKwqayGHrxxCqHRdqSVJh5GKA/p8rGU4Y 4LFwVmj2fEiO5D5prGmQ+WGtw9EMYN94SCAE1IbUo9bTr8R+P18xMQoBz A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0APAwAj3eVV/5JdJa1UCRMBAYMGVGmDI7sLAQmBd4V7AoFEOBQBAQEBAQEBgQqEJAEBBCMPATgDCgEQCxgCAgUQBgsCAgkDAgECAUUGAQwBBQIBAYgqDbR9lQYBAQEBAQEBAQEBAQEBAQEBAQEBAQETBIEiiUmBBYQvERgzB4JpgUMBBIU1hzp1h12FB4U9gjGIeJF0JoIOHRaBXR8zZwUbgUYBAQE
X-IronPort-AV: E=Sophos;i="5.17,450,1437436800"; d="scan'208";a="184032643"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-6.cisco.com with ESMTP; 01 Sep 2015 17:15:59 +0000
Received: from [10.129.24.52] ([10.129.24.52]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t81HFtqg028306; Tue, 1 Sep 2015 17:15:55 GMT
Message-ID: <55E5DD49.6010505@cisco.com>
Date: Tue, 01 Sep 2015 11:15:53 -0600
From: =?UTF-8?B?4oyYIE1hdHQgTWlsbGVy?= <mamille2@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Peter Saint-Andre - &yet <peter@andyet.net>, Barry Leiba <barryleiba@computer.org>
References: <20150729090441.16993.2639.idtracker@ietfa.amsl.com> <55BACBBF.3060301@andyet.net> <CALaySJ+k6Pt6b6UvhKNYgsk+=nMRfiSocd_T8aatRvLq4Vg+-w@mail.gmail.com> <55BBA4C1.6040404@andyet.net> <CALaySJLWDfRuCdziHSKqPFJ136d3O45Z7JDnYzDfQEZsKUsfdA@mail.gmail.com> <55CA9A10.2080603@andyet.net> <C4930219-3403-4782-869B-2348A7BFBEEB@nostrum.com> <55D3B0D8.2010202@andyet.net> <37FFCBB4-6921-4A6C-91A4-D1569CD96381@nostrum.com> <55DBAE21.3020408@cisco.com> <8C4C868A-B232-4F2B-A6D3-980785C95DB8@nostrum.com> <55DD249A.4080109@andyet.net> <55DFE8C4.7090707@andyet.net> <CALaySJJJP3xNPCW2t5XvN3_W5Rv3jsybiqYme+mhP0+oy7uEqA@mail.gmail.com> <55E066D0.3020109@andyet.net>
In-Reply-To: <55E066D0.3020109@andyet.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/iDIG4pg0Y93MqjvO_Aewi553Qb4>
Cc: Ben Campbell <ben@nostrum.com>, draft-ietf-xmpp-posh.shepherd@ietf.org, xmpp-chairs@ietf.org, xmpp@ietf.org, draft-ietf-xmpp-posh.ad@ietf.org, draft-ietf-xmpp-posh@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [xmpp] Barry Leiba's No Objection on draft-ietf-xmpp-posh-04: (with COMMENT)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 17:16:22 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Peter and I just posted -05 which should address all the outstanding
issues, and creates the POSH Service Names registry with IANA: <
https://tools.ietf.org/html/draft-ietf-xmpp-posh-05 >

To answer Barry's questions:

1)  I can act as one of the designated experts for the POSH Service
Names registry.
2) I have objections for the POSH Service Names registry requiring
Expert Review or IETF Review (and is reflected in -05)


- -- 
- - m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

On 8/28/15 7:49 AM, Peter Saint-Andre - &yet wrote:
> On 8/28/15 6:05 AM, Barry Leiba wrote:
>>>> 1. Recommend URIs like
>>>> https://example.com/.well-known/posh/spice.json
>>>> 
>>>> 2. In draft-ietf-xmpp-posh, register "posh" in the well-known
>>>> URIs registry
>>>> 
>>>> 3. In draft-ietf-xmpp-posh, set up a registry for POSH
>>>> protocols
>>>> 
>>>> 4. In draft-ietf-xmpp-dna, register "xmpp-client" and
>>>> "xmpp-server" in the POSH registry
>>>> 
>>>> I offered to Matt that I can propose text for the IANA
>>>> considerations sections since I've written such text before.
>>>> I'll endeavor to draft something in the next few days.
>>> 
>>> Here is proposed text for draft-ietf-xmpp-posh...
>> 
>> Thanks, Peter; this looks good.  Two questions, inline.
>> 
>>> 9.  IANA Considerations
>>> 
>>> 9.1.  Well-Known URI
>>> 
>>> This specification registers "posh" in the Well-Known URI 
>>> Registry as defined by [RFC5785].  The completed template
>>> follows.
>>> 
>>> URI suffix:  posh
>>> 
>>> Change controller:  IETF
>>> 
>>> Specification:  [[ this document ]]
>>> 
>>> Related information:  The suffix "posh" is expected to be 
>>> followed by an additional path component consisting of a
>>> service name (say, "spice") and a file extension of ".json",
>>> resulting in a full path of, for instance,
>>> "/.well-known/posh/spice.json". Registration of service names
>>> shall be requested by developers of the relevant application
>>> protocols.
>>> 
>>> 9.2.  POSH Service Names
>>> 
>>> This document establishes a registry for POSH service names.
>> 
>> It would help IANA if you suggested where to put the registry (in
>> an existing group of registries, or in its own, new top-level
>> group).
> 
> Ah, I thought that was up to the IANA. Given that POSH service
> names are used an additional path component in well-known URIs,
> placing this registry in the Uniform Resource Identifier (URI)
> Schemes registry would make sense.
> 
>>> POSH service names are registered on the advice of one or more 
>>> Designated Experts (appointed by the IESG or their delegate).
>>> An IANA registration policy [RFC5226] of Expert Review was
>>> chosen instead of the more liberal First Come First Served to
>>> help ensure that POSH is used in appropriate ways within
>>> applications.
>> 
>> Thanks for that explanation; it helps.
>> 
>> 1. Are Peter Saint-Andre and Matt Miller willing and able to act
>> as the designated experts?  If so, I'll put that in for IESG
>> approval.
> 
> I can serve in that capacity.
> 
>> 2. Do you want expert review to also apply to IETF documents
>> (such as xmpp-dna, which would then need expert review before
>> final approval)? If not, you could use "Expert Review OR IETF
>> Review", or "Expert Review OR Standards Action".
> 
> I think "Expert Review OR IETF Review" would be fine but I'm not
> sure what Matt thinks.
> 
>> 3. It would be good to have a short paragraph or a pointer to
>> other text that gives some guidance of what "used in appropriate
>> ways" means, so the DEs (should we eventually put in someone
>> other than the authors) know what not to accept.
> 
> Matt and I will try to formulate some text. We had some more
> specific text but it wasn't quite right. The basic idea is that we
> don't want folks to be using POSH when other technologies are a
> better fit. The example we had was DNS SRV but that wasn't correct
> since the two are complementary.
> 
>>> Registration requests are to be sent to the posh@ietf.org
>>> mailing list for review and comment, with an appropriate
>>> subject (e.g., "Request for POSH service name: example").
>>> 
>>> Before a period of 14 days has passed, the Designated Expert(s)
>>> will either approve or deny the registration request,
>>> communicating this decision both to the review list and to
>>> IANA.  Denials should include an explanation and, if
>>> applicable, suggestions as to how to make the request
>>> successful.  Registration requests that are undetermined for a
>>> period longer than 21 days can be brought to the IESG's
>>> attention (using the iesg@iesg.org mailing list) for
>>> resolution.
>>> 
>>> 9.2.1.  Registration Template
>>> 
>>> Service name:  The name requested, relative to
>>> "/.well-known/posh/"; e.g., a service name of "example" would
>>> result in a well-known URI such as
>>> "https://example.com/.well-known/posh/example.json".
>>> 
>>> Change controller:  For Standards-Track RFCs, state "IETF".  In
>>> all other cases, give the name of the responsible party.
>>> Other details (e.g., postal address, e-mail address, home page
>>> URI) may also be included.
>> 
>> Is there a reason not to make e-mail address mandatory?  IANA
>> ought to have a recorded contact point.
> 
> True. I think that's better.
> 
>>> Definition and usage:  A brief description that defines the
>>> service name and mentions where and how it is used (e.g., in
>>> the context of a particular application protocol).
>>> 
>>> Specification:  Optionally, reference to a document that
>>> specifies the service or application protocol that uses the
>>> service name, preferably including a URI that can be used to
>>> retrieve a copy of the document.  An indication of the relevant
>>> sections may also be included, but is not required.
>>> 
>>> ###
>>> 
>>> And we would need to make associated changes in
>>> draft-ietf-xmpp-dna, such as...
>>> 
>>> ###
>>> 
>>> 9.  IANA Considerations
>>> 
>>> The POSH specification [I-D.ietf-xmpp-posh] establishes a
>>> registry for POSH service names to be used in well-known URIs
>>> [RFC5785]. This specification registers two such URIs for use
>>> in XMPP: "xmpp-client" and "xmpp-server".  The completed
>>> registration templates follow.
>>> 
>>> 9.1.  POSH Service Name for xmpp-client Service
>>> 
>>> POSH service name: xmpp-client
>> 
>> This should probably match the template in the other document,
>> so either change this to "Service name" or change the template to
>> "POSH service name".
> 
> Correct.
> 
>>> Change controller: IETF
>>> 
>>> Definition and usage: Specifies the location of a POSH file 
>>> containing verification material or a reference thereto that
>>> enables a client to verify the identity of a server for a
>>> client-to-server stream in XMPP
>>> 
>>> Specification: [[ this document ]]
>>> 
>>> 9.2.  POSH Service Name for xmpp-server Service
>>> 
>>> POSH service name: xmpp-server
>>> 
>>> Change controller: IETF
>>> 
>>> Definition and usage: Specifies the location of a POSH file 
>>> containing verification material or a reference thereto that
>>> enables a server to verify the identity of a peer server for a
>>> server-to- server stream in XMPP
>>> 
>>> Specification: [[ this document ]]
>>> 
>>> ###
>>> 
>>> Matt and I have checked this approach with a few implementers
>>> and potential implementers; no one has objected yet, but if
>>> folks on the xmpp@ietf.org list or elsewhere have significant
>>> concerns it would be great to hear from you. :-)
>> 
>> Barry
> 
> Thanks for the review!
> 
> Peter
> 

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJV5d1JAAoJEDWi+S0W7cO1AvkH/iHJmElKZ5XuMLx267EmBmEL
115VGo5KZX7hVtMc4SfDRhTpywK5Y6lTPEHF++RQFyaARaNMacSMo4ZrLQfy66AK
lo8I3ZmLeAWzDZ328EO1u/mHv7wFZnBwSDO3+8bQciTCn2y2qyDxKO8FgwbmMs2n
SE24M2xmrMOyGWRIySORw8orLBkqCl0JxgirjGOY2A6OtV/eaDSUTM4TdzzpfbKJ
5K5mrrr80ilzPq7xN85a85u84U5CXCmvNVW1UuaT40htTCPOXLENuYgu7A1kzA1G
IC6OLru4bWPALvsDzcVxY3TRq4hl9OGNV6teqb7FmlTc4e4uJ3hZBKQBuGWJT4M=
=CuZv
-----END PGP SIGNATURE-----


From nobody Tue Sep  1 10:19:33 2015
Return-Path: <mamille2@cisco.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB9CE1B4E93 for <xmpp@ietfa.amsl.com>; Tue,  1 Sep 2015 10:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 4ylFnC-AtROt for <xmpp@ietfa.amsl.com>; Tue,  1 Sep 2015 10:19:30 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 617011B3C68 for <xmpp@ietf.org>; Tue,  1 Sep 2015 10:19:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3206; q=dns/txt; s=iport; t=1441127969; x=1442337569; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=QETKWHXGjfBfQwx5lnH4wxyq2N2FeK+mNwgnUtJK7v0=; b=G4I4cHTTjNrLX84FGmh88RnN9d2DBWRT+QuIKDVsUuhSgi/fsVcc9Fec Aelhd+yIytQ3UCvB8W+cruxr/TQqxgfEKUB6tD3c5S11v60ttNvNb9NCz AVrL0j82m6sfzvOIjXZQVxwEZB+3B2saNuPgRrB8tZdo9UC3nPPtGB++K w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAwCb3eVV/4QNJK1TAQmDG1RpgyO7CwEJgW0KhXsCgUQ4FAEBAQEBAQGBCoQkAQEEAQEBIEsbCxgCAgUhAgIPAhYwBg0EAgIBAQWIJQ20fZUHAQEBAQEBAQMBAQEBAQEBARqBIopOhC4BERg6gmmBQwWMb3WHXYUHh26BSkaDbIJ8ikKHMiaCDh2Bcx8ELwGCTAEBAQ
X-IronPort-AV: E=Sophos;i="5.17,450,1437436800"; d="scan'208";a="28949393"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-3.cisco.com with ESMTP; 01 Sep 2015 17:19:14 +0000
Received: from [10.129.24.52] ([10.129.24.52]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t81HJCNc013215 for <xmpp@ietf.org>; Tue, 1 Sep 2015 17:19:12 GMT
Message-ID: <55E5DE0F.90904@cisco.com>
Date: Tue, 01 Sep 2015 11:19:11 -0600
From: =?UTF-8?B?4oyYIE1hdHQgTWlsbGVy?= <mamille2@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: XMPP Group <xmpp@ietf.org>
References: <20150901171239.15229.52617.idtracker@ietfa.amsl.com>
In-Reply-To: <20150901171239.15229.52617.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/DDJkbkhtrSwr5ZDSlGq3kHiAij4>
Subject: Re: [xmpp] I-D Action: draft-ietf-xmpp-posh-05.txt
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 17:19:32 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Version -05 should address all of the IESG feedback.

It also changes the .well-known usage from
".well-known/posh.{service}.json" to
"./well-known/posh/{service}.json" by registering for the "posh"
.well-known and establishing a POSH Service Names registry.

An upcoming revision to draft-ietf-xmpp-dna will actually register the
"xmpp-client" and "xmpp-server" POSH service names.


- -- 
- - m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

On 9/1/15 11:12 AM, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Extensible Messaging
> and Presence Protocol Working Group of the IETF.
> 
> Title           : PKIX over Secure HTTP (POSH) Authors         :
> Matthew Miller Peter Saint-Andre Filename        :
> draft-ietf-xmpp-posh-05.txt Pages           : 17 Date            :
> 2015-09-01
> 
> Abstract: Experience has shown that it is difficult to deploy
> proper PKIX certificates for TLS in multi-tenant environments.  As
> a result, domains hosted in such environments often deploy
> applications using certificates that identify the hosting service,
> not the hosted domain.  Such deployments force end users and peer
> services to accept a certificate with an improper identifier,
> resulting in degraded security.  This document defines two methods
> that make it easier to deploy certificates for proper server
> identity checking in non-HTTP application protocols.  While these
> methods were developed for use in the Extensible Messaging and
> Presence Protocol (XMPP) as a Domain Name Association (DNA)
> prooftype, they might also be usable in other non-HTTP application
> protocols.
> 
> 
> The IETF datatracker status page for this draft is: 
> https://datatracker.ietf.org/doc/draft-ietf-xmpp-posh/
> 
> There's also a htmlized version available at: 
> https://tools.ietf.org/html/draft-ietf-xmpp-posh-05
> 
> A diff from the previous version is available at: 
> https://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-posh-05
> 
> 
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at
> tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at: 
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________ I-D-Announce
> mailing list I-D-Announce@ietf.org 
> https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft
> directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJV5d4PAAoJEDWi+S0W7cO1CSwH/1RM0ki7SY5FwWKLos7a4l5/
6L/7Ko1JLZQvxWXQma2ruLrs4WA8z0T2prJ7J+SFkrRzXBSrtlhJZU3rFlqxT/e9
0aoZQCswTZNf6xoTgCo7z4LIngOy80Cix/MLgtGHNrdM432TPT5oUb6Qod1eDpTS
T3PmCvBVHc6tlwchZyNouLH9R1Bbyv3wuQGvHVHA/E0JtuOExK0uMHx4QuvM2jGF
MtD4UBW0vbl50qF0gp0B6ZfFz0KHCnQe2yw511OxxF77453LYtvOBPxm08ryA1yG
Pvk9KKpLQ9448zS3eCkrPflV+dfzQySVX70PgVYbeoynN68o4BWXdxGGiOslWzE=
=KJ/X
-----END PGP SIGNATURE-----


From nobody Tue Sep  1 10:20:13 2015
Return-Path: <ben@nostrum.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2421B307E; Tue,  1 Sep 2015 10:20:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 MS_ZmUWpoohT; Tue,  1 Sep 2015 10:20:06 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97C9A1B6005; Tue,  1 Sep 2015 10:19:49 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t81HJZgB062103 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 1 Sep 2015 12:19:46 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: "Ben Campbell" <ben@nostrum.com>
To: "=?utf-8?q?=E2=8C=98?= Matt Miller" <mamille2@cisco.com>
Date: Tue, 01 Sep 2015 12:19:35 -0500
Message-ID: <5C336F50-C2F4-4246-85BA-241217A07156@nostrum.com>
In-Reply-To: <55E5DD49.6010505@cisco.com>
References: <20150729090441.16993.2639.idtracker@ietfa.amsl.com> <55BACBBF.3060301@andyet.net> <CALaySJ+k6Pt6b6UvhKNYgsk+=nMRfiSocd_T8aatRvLq4Vg+-w@mail.gmail.com> <55BBA4C1.6040404@andyet.net> <CALaySJLWDfRuCdziHSKqPFJ136d3O45Z7JDnYzDfQEZsKUsfdA@mail.gmail.com> <55CA9A10.2080603@andyet.net> <C4930219-3403-4782-869B-2348A7BFBEEB@nostrum.com> <55D3B0D8.2010202@andyet.net> <37FFCBB4-6921-4A6C-91A4-D1569CD96381@nostrum.com> <55DBAE21.3020408@cisco.com> <8C4C868A-B232-4F2B-A6D3-980785C95DB8@nostrum.com> <55DD249A.4080109@andyet.net> <55DFE8C4.7090707@andyet.net> <CALaySJJJP3xNPCW2t5XvN3_W5Rv3jsybiqYme+mhP0+oy7uEqA@mail.gmail.com> <55E066D0.3020109@andyet.net> <55E5DD49.6010505@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/t9gc3G6UhtGSpXOMuCw2cDYIczM>
Cc: draft-ietf-xmpp-posh.shepherd@ietf.org, xmpp-chairs@ietf.org, xmpp@ietf.org, draft-ietf-xmpp-posh.ad@ietf.org, Barry Leiba <barryleiba@computer.org>, draft-ietf-xmpp-posh@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [xmpp] Barry Leiba's No Objection on draft-ietf-xmpp-posh-04: (with COMMENT)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 17:20:07 -0000

Thanks Matt, one question:

On 1 Sep 2015, at 12:15, ⌘ Matt Miller wrote:

> 2) I have objections for the POSH Service Names registry requiring
> Expert Review or IETF Review (and is reflected in -05)

Do you mean "no objections"?

Ben.


From nobody Tue Sep  1 10:21:05 2015
Return-Path: <mamille2@cisco.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F35541B5F0F; Tue,  1 Sep 2015 10:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 dD3YmUurlOj2; Tue,  1 Sep 2015 10:21:03 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B6271B307E; Tue,  1 Sep 2015 10:20:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1321; q=dns/txt; s=iport; t=1441128047; x=1442337647; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=gyCjnMODk1TEsnNmlsjIx1MzxxJqN1Vo9mLQphXtygY=; b=evHV4dGYoGM3GosaNLp35hsrgwStMGNj5LVMrAidvOX3lchLwwH9OTbV hDJB/ufTTaW3ClqVU//dZd2YACGPqfMKLUF1xFwzaUyB6eXe9pSm7+zjj MGQyvmwpNJ0WVMgjTK19wvSneOUZ7HERT+fieNBAnLGSw9E+JwaJaQUPi Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAwCb3eVV/4YNJK1dgxtUaYMjuwsBCYF3hXsCgUQ4FAEBAQEBAQGBCoQkAQEEIw8BOA0BEAsYAgIFFgsCAgkDAgECAUUGAQwBBQIBAYgqDbR9lQcBAQEBAQEBAQEBAQEBAQEBAQEBAQETBIEiik6EWDMHgmmBQwEEjWSHXYUHh26IeJF0JoIOHRaBXR8zgk0BAQE
X-IronPort-AV: E=Sophos;i="5.17,450,1437436800"; d="scan'208";a="184067712"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-7.cisco.com with ESMTP; 01 Sep 2015 17:20:46 +0000
Received: from [10.129.24.52] ([10.129.24.52]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t81HKkri023609; Tue, 1 Sep 2015 17:20:46 GMT
Message-ID: <55E5DE6D.2060409@cisco.com>
Date: Tue, 01 Sep 2015 11:20:45 -0600
From: =?UTF-8?B?4oyYIE1hdHQgTWlsbGVy?= <mamille2@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Peter Saint-Andre - &yet <peter@andyet.net>, Barry Leiba <barryleiba@computer.org>
References: <20150729090441.16993.2639.idtracker@ietfa.amsl.com> <55BACBBF.3060301@andyet.net> <CALaySJ+k6Pt6b6UvhKNYgsk+=nMRfiSocd_T8aatRvLq4Vg+-w@mail.gmail.com> <55BBA4C1.6040404@andyet.net> <CALaySJLWDfRuCdziHSKqPFJ136d3O45Z7JDnYzDfQEZsKUsfdA@mail.gmail.com> <55CA9A10.2080603@andyet.net> <C4930219-3403-4782-869B-2348A7BFBEEB@nostrum.com> <55D3B0D8.2010202@andyet.net> <37FFCBB4-6921-4A6C-91A4-D1569CD96381@nostrum.com> <55DBAE21.3020408@cisco.com> <8C4C868A-B232-4F2B-A6D3-980785C95DB8@nostrum.com> <55DD249A.4080109@andyet.net> <55DFE8C4.7090707@andyet.net> <CALaySJJJP3xNPCW2t5XvN3_W5Rv3jsybiqYme+mhP0+oy7uEqA@mail.gmail.com> <55E066D0.3020109@andyet.net> <55E5DD49.6010505@cisco.com>
In-Reply-To: <55E5DD49.6010505@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/UnZt7-Bz1VJ2QD3BvAZQxiTXsZ0>
Cc: Ben Campbell <ben@nostrum.com>, draft-ietf-xmpp-posh.shepherd@ietf.org, xmpp-chairs@ietf.org, draft-ietf-xmpp-posh.ad@ietf.org, xmpp@ietf.org, draft-ietf-xmpp-posh@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [xmpp] Barry Leiba's No Objection on draft-ietf-xmpp-posh-04: (with COMMENT)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 17:21:05 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 9/1/15 11:15 AM, ⌘ Matt Miller wrote:
> Peter and I just posted -05 which should address all the
> outstanding issues, and creates the POSH Service Names registry
> with IANA: < https://tools.ietf.org/html/draft-ietf-xmpp-posh-05 >
> 
> To answer Barry's questions:
> 
> 1)  I can act as one of the designated experts for the POSH
> Service Names registry. 2) I have objections for the POSH Service
> Names registry requiring Expert Review or IETF Review (and is
> reflected in -05)
> 

/me sighs

There should be a *NO* in there.

2) I have *NO* objections for the POSH Service Names registry
requiring Expert Review or IETF Review (and is reflected in -05)


- -- 
- - m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJV5d5tAAoJEDWi+S0W7cO1vywH/ifg0sfHYmNbqlOQb3sdG1zH
ZPGQ57UrmMhVvcgHzLvjI5h0TlSay55LQlXuHFgaLKDTbsY+8qbX/tBEbTvdQFJP
a4IlesWmsEOIphfAkrBxxwP3BEmWKWSXa8pZmvIMdfjWj+YO8K6Bk3rgLHXDS2nY
652P72YPb+860tE5NjPULNaunQEbTMkUYhmn6L8vYADPGr/+sNgYH+oLeQlh79l7
Gip7WHgWyRqh/GrJ8OTv5wtdf8JDWlzoWW22B3D/mruYGdAzRO6MA66XvUplbiEa
r/Is4tYlVeDuysfyszZmzrIAh4+iMfnXW/5ng77LyvD5KxyQxKVelXY9XBDBVAE=
=vFXk
-----END PGP SIGNATURE-----


From nobody Tue Sep  1 10:24:38 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E6531B49E4; Tue,  1 Sep 2015 10:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 7pjxPGGxkDVp; Tue,  1 Sep 2015 10:24:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D93AE1B4657; Tue,  1 Sep 2015 10:24:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150901172434.24427.39793.idtracker@ietfa.amsl.com>
Date: Tue, 01 Sep 2015 10:24:34 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/K7EJ3ED-hf3ujJv-l0lU6nseVPU>
Cc: xmpp@ietf.org
Subject: [xmpp] I-D Action: draft-ietf-xmpp-dna-11.txt
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 17:24:36 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Extensible Messaging and Presence Protocol Working Group of the IETF.

        Title           : Domain Name Associations (DNA) in the Extensible Messaging and Presence Protocol (XMPP)
        Authors         : Peter Saint-Andre
                          Matthew Miller
                          Philipp Hancke
	Filename        : draft-ietf-xmpp-dna-11.txt
	Pages           : 23
	Date            : 2015-09-01

Abstract:
   This document improves the security of the Extensible Messaging and
   Presence Protocol (XMPP) in two ways.  First, it specifies how to
   establish a strong association between a domain name and an XML
   stream, using the concept of "prooftypes".  Second, it describes how
   to securely delegate a service domain name (e.g., example.com) to a
   target server host name (e.g., hosting.example.net), which is
   especially important in multi-tenanted environments where the same
   target server hosts a large number of domains.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-xmpp-dna/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-xmpp-dna-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-dna-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Sep  1 10:28:42 2015
Return-Path: <mamille2@cisco.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E333D1B32A6 for <xmpp@ietfa.amsl.com>; Tue,  1 Sep 2015 10:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 RmeVHpJMkbhF for <xmpp@ietfa.amsl.com>; Tue,  1 Sep 2015 10:28:35 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5440F1B2EAC for <xmpp@ietf.org>; Tue,  1 Sep 2015 10:28:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2770; q=dns/txt; s=iport; t=1441128515; x=1442338115; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=mjXw/bqR735P+Pz1zV8DlMYss5qI3QR1/SJCujOF9No=; b=LJmOq3AsVnZwIfebrT0kuuYCMS+Vc8oZ06ZShKoT/b6z9V88lYLBD/S8 IuyZcaX+wluXevnx22gSIme1c5Lh7BvIJXzhqIXQR1Sr0Grz7u/FFiqMD A/6sMc5zEKxcH1yovx1yTWGgQbt1R94wEAKX1grJn0ztT6wZuc/cdcmBF w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAwBG3+VV/4cNJK1dgxtUaYMjuwsBCYFtCoV7AoFEOBQBAQEBAQEBgQqEJAEBBAEBASBLGwsYAgIFIQICDwIWMBMGAgEBBYglDbRmlQgBAQEBBgEBAQEBHYEiik6EQBg6F4JSgUMFjG91h12FB4dugUpGg2yCfIpChzImgg4dgXMfMwGCTAEBAQ
X-IronPort-AV: E=Sophos;i="5.17,450,1437436800"; d="scan'208";a="25382632"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-6.cisco.com with ESMTP; 01 Sep 2015 17:28:34 +0000
Received: from [10.129.24.52] ([10.129.24.52]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t81HSXw6011104 for <xmpp@ietf.org>; Tue, 1 Sep 2015 17:28:34 GMT
Message-ID: <55E5E041.30809@cisco.com>
Date: Tue, 01 Sep 2015 11:28:33 -0600
From: =?UTF-8?B?4oyYIE1hdHQgTWlsbGVy?= <mamille2@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: xmpp@ietf.org
References: <20150901172434.24427.39793.idtracker@ietfa.amsl.com>
In-Reply-To: <20150901172434.24427.39793.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/BbZKHVXLOSL4bV-vLgxLPfJUqNg>
Subject: Re: [xmpp] I-D Action: draft-ietf-xmpp-dna-11.txt
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 17:28:40 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

This version should address all feedback received from IESG review.

It also actually registers "xmpp-client" and "xmpp-server" POSH
Service Names.


- -- 
- - m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

On 9/1/15 11:24 AM, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Extensible Messaging
> and Presence Protocol Working Group of the IETF.
> 
> Title           : Domain Name Associations (DNA) in the Extensible
> Messaging and Presence Protocol (XMPP) Authors         : Peter
> Saint-Andre Matthew Miller Philipp Hancke Filename        :
> draft-ietf-xmpp-dna-11.txt Pages           : 23 Date            :
> 2015-09-01
> 
> Abstract: This document improves the security of the Extensible
> Messaging and Presence Protocol (XMPP) in two ways.  First, it
> specifies how to establish a strong association between a domain
> name and an XML stream, using the concept of "prooftypes".  Second,
> it describes how to securely delegate a service domain name (e.g.,
> example.com) to a target server host name (e.g.,
> hosting.example.net), which is especially important in
> multi-tenanted environments where the same target server hosts a
> large number of domains.
> 
> 
> The IETF datatracker status page for this draft is: 
> https://datatracker.ietf.org/doc/draft-ietf-xmpp-dna/
> 
> There's also a htmlized version available at: 
> https://tools.ietf.org/html/draft-ietf-xmpp-dna-11
> 
> A diff from the previous version is available at: 
> https://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-dna-11
> 
> 
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at
> tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at: 
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________ I-D-Announce
> mailing list I-D-Announce@ietf.org 
> https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft
> directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJV5eBBAAoJEDWi+S0W7cO1D4oIAIUlWUKTwBOiw0AnPE0zEOiw
srP+YAr1guTp8bNcRoe+26kIErd5Eynf5xpGbqjngHB/HReHNODIsuwLJ+fD8ALO
4va3bdJyCHmeAXShJVdtPfcH8HG8hr0ZUAwM0XZex29MEImoRtiGk1ZGmihN2Yf/
HXuxYgUJ1CxvLzlath8anYX99N5l3gA/33gIGU9Ln0OqRfxKRCx7WsZQCa/xzA1z
5cawGNUCfpjdtFs9AUzSh1Z8CnYaOJo5Q+bQDyg/8f+hVcvM+F/ejnF+2mpEAg8d
QXfycvV4VgNhSNcAbkLNdeFWjuzWXothXTpM0Hf0IB+K2i6jyvK/BYoUZFDseGo=
=fBQv
-----END PGP SIGNATURE-----


From nobody Fri Sep  4 03:00:32 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E94961B4820; Fri,  4 Sep 2015 03:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 6aKAuDonlHJi; Fri,  4 Sep 2015 03:00:24 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 218EF1B47F3; Fri,  4 Sep 2015 03:00:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12557; q=dns/txt; s=iport; t=1441360824; x=1442570424; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=oygWIWHPT763Wr2Hx6uPRIEzTobAXIcwgWoejqPWvDE=; b=Uj4s+nVqCfZ5PSTEu3eNzmvgsXP8oMGA2d6MmrmX83BI0H2rf6iLEkct l9TYNLzXFVwbBsyPPuCLybdsXYxEi/ca++QLrq29mPWWKPKRp2aJPW9/s A2Ul3H21I7JttBHxDI6CGCrmquRiVSl1opCV4bTGdZ3sIOqiKHirpGb0Q 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DLAwDIaulV/xbLJq1dg3VpvVUBCYF3hXsCgXIUAQEBAQEBAYEKQQWDXgEBBCMPAQVAARALGAICBRYLAgIJAwIBAgFFBgEMBgIBAQWIJQ22DZQ5AQEBAQEBAQEBAQEBAQEBAQEBAQEBF4EihVGDdoEFhCgRAQZLB4JpgUMBBIcxhUaFOoMghQeCbYUDgUqEMoJ8kXgmghAcgVY8MwGERoM+BxcHgSEBAQE
X-IronPort-AV: E=Sophos;i="5.17,468,1437436800"; d="scan'208";a="611383738"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 04 Sep 2015 10:00:20 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t84A0J5v008774; Fri, 4 Sep 2015 10:00:19 GMT
To: Peter Saint-Andre - &yet <peter@andyet.net>, Mahesh Jethanandani <mjethanandani@gmail.com>
References: <20150806103342.2703.18148.idtracker@ietfa.amsl.com> <55C9344F.90201@andyet.net> <11AAE863-30CB-4B50-90FE-C83D68E434EA@gmail.com> <55C95B20.3050902@andyet.net> <8208F533-C48C-48DC-8756-7A3F99938F67@gmail.com> <55CA1B2C.3030406@andyet.net>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <55E96BB3.7010108@cisco.com>
Date: Fri, 4 Sep 2015 12:00:19 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55CA1B2C.3030406@andyet.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/-PgaawQPDCtdkDsDNErD5m6dw_A>
Cc: draft-ietf-xmpp-dna.ad@ietf.org, draft-ietf-xmpp-dna@ietf.org, xmpp-chairs@ietf.org, xmpp@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-xmpp-dna.shepherd@ietf.org
Subject: Re: [xmpp] Benoit Claise's No Objection on draft-ietf-xmpp-dna-10: (with COMMENT)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Sep 2015 10:00:28 -0000

Thanks Peter and Mahesh.

Regards, Benoit
> Great, thanks for checking it.
>
> BTW, here is initial proposed text for the section we would reference 
> in draft-ietf-xmpp-posh (I know you weren't tasked with reviewing that 
> spec, so I'm including it here only for completeness):
>
> ###
>
>
> 8.  Guidance for Server Operators
>
>    POSH is intended to ease the operational burden of securing
>    application services, especially in multi-tenanted environments.  It
>    does so by obviating the need to obtain certificates for hosted
>    domains, so that an operator can obtain a certificate only for its
>    hosting service (naturally, this certificate needs to be valid
>    according to [RFC5280] and contain the proper identifier(s) in
>    accordance with [RFC6125] and the relevant application protocol
>    specification).
>
>    However, in order to use POSH, an operator does need to coordinate
>    with its customers so that the appropriate POSH files are provided
>    via HTTPS at a well-known URI at each customer's domain (i.e., at the
>    Source Domain), thus ensuring delegation to the operator's hosting
>    service (i.e., the Delegated Domain).  Because correct hosting of the
>    POSH file at the Source Domain is essential for successful
>    functioning of the POSH "chain", errors at the Source Domain will
>    result in authentication problems, certificate warnings, and other
>    operational issues.
>
>    Furthermore, if the POSH file performs reference rather than
>    possession as described in this document, the operational burden is
>    further decreased since the operator does not need to provision its
>    customers with updated POSH files when the certificate for the
>    Delegated Domain expires or is replaced.
>
> ###
>
> Matt Miller and I will work on that text further this week.
>
> Peter
>
> On 8/10/15 8:27 PM, Mahesh Jethanandani wrote:
>> Hi Peter,
>>
>> The text looks good to me.
>>
>> Thanks.
>>
>>> On Aug 10, 2015, at 7:17 PM, Peter Saint-Andre - &yet 
>>> <peter@andyet.net> wrote:
>>>
>>> Hi Mahesh,
>>>
>>> I suggest that we add a section something like the following to 
>>> draft-ietf-xmpp-dna and then add a section to draft-ietf-xmpp-posh 
>>> as well (I haven't written any text for the latter yet, thus the 
>>> "FIXME" for a section number in what follows).
>>>
>>> ###
>>>
>>> 8.  Guidance for Server Operators
>>>
>>>    This document introduces the concept of a prooftype in order to
>>>    explain and generalize the approach to establishing a strong
>>>    association between the DNS domain name of an XMPP service and the
>>>    XML stream that a client or peer server initiates with that service.
>>>
>>>    The operators of XMPP services will not directly deploy DNA
>>>    prooftypes, and the operations and management implications will
>>>    depend on the prooftypes that an operator supports.  For example:
>>>
>>>    o  To support the PKIX prooftype [RFC6120], an operator needs to
>>>       interact with a certification authority but does not need to
>>>       deploy DNS security.
>>>
>>>    o  To support the DANE prooftype [I-D.ietf-dane-srv], an operator 
>>> can
>>>       generate its own certificates or obtain them from a certification
>>>       authority but needs to deploy DNS security.
>>>
>>>    o  To support the POSH prooftype [I-D.ietf-xmpp-posh], an operator
>>>       can generate its own certificates or obtain them from a
>>>       certification authority but does not need to deploy DNS security.
>>>
>>>    Considerations for use of the foregoing prooftypes are explained in
>>>    the relevant specifications.  See in particular Section 13.7 of
>>>    [RFC6120], Section 6 of [I-D.ietf-dane-srv], and Section FIXME of
>>>    [I-D.ietf-xmpp-posh].
>>>
>>>    Naturally, these operations and management considerations are
>>>    additive: if an operator wishes to use multiple prooftypes, the
>>>    complexity of deployment increases (e.g., the operator might want to
>>>    obtain a PKIX certificate from a certification authority for use in
>>>    the PKIX prooftype and generate its own certificate for use in the
>>>    DANE prooftype).  This is an unavoidable aspect of supporting as 
>>> many
>>>    prooftypes as needed in order to ensure that domain name 
>>> associations
>>>    can be established in the largest possible percentage of cases.
>>>
>>> ###
>>>
>>> What do you think?
>>>
>>> (I haven't shared this text yet with my co-authors, since I've been 
>>> working on it just now.)
>>>
>>> Peter
>>>
>>> On 8/10/15 8:09 PM, Mahesh Jethanandani wrote:
>>>> Peter,
>>>>
>>>> I agree. As I suggested in the review, a reference to the section 
>>>> you reproduce below from draft-ietf-dane-srv (and a similar 
>>>> reference to a section in draft-ietf-xmpp-posh) is what you need in 
>>>> draft-ietf-xmpp-dna.
>>>>
>>>> Cheers.
>>>>
>>>>> On Aug 10, 2015, at 4:31 PM, Peter Saint-Andre - &yet 
>>>>> <peter@andyet.net> wrote:
>>>>>
>>>>> Hi Benoit, I posted a reply to the OPS-DIR review here:
>>>>>
>>>>> https://mailarchive.ietf.org/arch/msg/xmpp/VymvhuVNfSFaNv8YEjpslzR_tw4 
>>>>>
>>>>>
>>>>> My feeling is that it would be best for this document to point to 
>>>>> the companion documents (draft-ietf-xmpp-posh and 
>>>>> draft-ietf-dane-srv) with regard to operations and management. 
>>>>> Note that draft-ietf-dane-srv already includes the following text:
>>>>>
>>>>> ###
>>>>>
>>>>> 6.  Guidance for Server Operators
>>>>>
>>>>>    To conform to this specification, the published SRV records and
>>>>>    subsequent address (A and AAAA) records MUST be secured with 
>>>>> DNSSEC.
>>>>>    There SHOULD also be at least one TLSA record published that
>>>>>    authenticates the server's certificate.
>>>>>
>>>>>    When using TLSA records with Certificate Usage "DANE-EE", it is 
>>>>> not
>>>>>    necessary for the deployed certificate to contain an identifier 
>>>>> for
>>>>>    either the source domain or target server host name. However,
>>>>>    operators need to be aware that servers relying solely on 
>>>>> validation
>>>>>    using Certificate Usage "DANE-EE" TLSA records might prevent 
>>>>> clients
>>>>>    that do not support this specification from successfully 
>>>>> connecting
>>>>>    with TLS.
>>>>>
>>>>>    For TLSA records with Certificate Usage types other than 
>>>>> "DANE-EE",
>>>>>    the certificate(s) MUST contain an identifier that matches:
>>>>>
>>>>>    o  the service domain name (the "source domain" in [RFC6125] 
>>>>> terms,
>>>>>       which is the SRV query domain); and/or
>>>>>
>>>>>    o  the target server host name (the "derived domain" in [RFC6125]
>>>>>       terms, which is the SRV target host name).
>>>>>
>>>>>    Servers that support multiple service domains (i.e., so-called
>>>>>    "multi-tenanted environments") can implement the Transport Layer
>>>>>    Security Server Name Indication (TLS SNI) [RFC6066] or its 
>>>>> functional
>>>>>    equivalent to determine which certificate to offer. Clients 
>>>>> that do
>>>>>    not support this specification will indicate a preference for the
>>>>>    service domain name, while clients that support this specification
>>>>>    will indicate the target server host name.  However, the server
>>>>>    determines what certificate to present in the TLS handshake; e.g.,
>>>>>    the presented certificate might only authenticate the target 
>>>>> server
>>>>>    host name.
>>>>>
>>>>> ###
>>>>>
>>>>> Is that text helpful and complete? (Note that draft-ietf-dane-srv 
>>>>> has already been approved for publication, but if we need to make 
>>>>> some slight adjustments during AUTH48 we could do so.)
>>>>>
>>>>> Also, do you think it would be preferable for draft-ietf-xmpp-posh 
>>>>> to include a similar section providing guidance for server 
>>>>> operators in draft-ietf-xmpp-posh? If so, Matt and I can work to 
>>>>> formulate some text.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Peter
>>>>>
>>>>> On 8/6/15 4:33 AM, Benoit Claise wrote:
>>>>>> Benoit Claise has entered the following ballot position for
>>>>>> draft-ietf-xmpp-dna-10: No Objection
>>>>>>
>>>>>> When responding, please keep the subject line intact and reply to 
>>>>>> all
>>>>>> email addresses included in the To and CC lines. (Feel free to 
>>>>>> cut this
>>>>>> introductory paragraph, however.)
>>>>>>
>>>>>>
>>>>>> Please refer to 
>>>>>> https://www.ietf.org/iesg/statement/discuss-criteria.html
>>>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>>>>
>>>>>>
>>>>>> The document, along with other ballot positions, can be found here:
>>>>>> https://datatracker.ietf.org/doc/draft-ietf-xmpp-dna/
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------- 
>>>>>>
>>>>>> COMMENT:
>>>>>> ---------------------------------------------------------------------- 
>>>>>>
>>>>>>
>>>>>> The conversation started between Mahesh (OPS-DIR reviewer) and the
>>>>>> authors on the following points:
>>>>>>
>>>>>> Summary:
>>>>>>
>>>>>> This document defines new “prooftype” used to establish a strong
>>>>>> association between a domain name and an XML stream. There are two
>>>>>> companion documents draft-ietf-xmpp-posh-04 and 
>>>>>> draft-ietf-dane-srv-12
>>>>>> that should be viewed as part of reviewing this document.
>>>>>>
>>>>>> If there are any management requirements to configure the new
>>>>>> “prooftype”, they have not been discussed as part of this 
>>>>>> document. I did
>>>>>> not review the companion documents to see if management of the 
>>>>>> feature
>>>>>> has been addressed in them. This document should talk about how the
>>>>>> feature will be managed, even if it means referring to relevant 
>>>>>> sections
>>>>>> of the other documents. If there is a need to define a YANG model to
>>>>>> configure the feature, it should be identified, even if it is not 
>>>>>> defined
>>>>>> in this document.
>>>>>>
>>>>>>>  From an operational perspective, it would be helpful to know 
>>>>>>> how this
>>>>>> would be deployed in the field. Are there any issues beyond 
>>>>>> certificate
>>>>>> configuration that operators should be aware of? Some of the 
>>>>>> services are
>>>>>> replacements for existing services, e.g. DNS with secure DNS. How 
>>>>>> would
>>>>>> the operators role out the service in the field with existing
>>>>>> service(s)?
>>>>>>
>>>>>> Section 3:
>>>>>>
>>>>>> The document talks about establishing a client to server Domain Name
>>>>>> Association (DNA) in this section. This is a simpler case of the 
>>>>>> server
>>>>>> to server DNA. However, it is not clear what happens if the 
>>>>>> certificate
>>>>>> verification fails. Is the behavior the same as when a self-signed
>>>>>> certificate is presented? Is there a fallback process or does the 
>>>>>> session
>>>>>> just terminate?
>>>>>>
>>>>>> In addition, the following nits should be addressed in the document.
>>>>>>
>>>>>>    Checking nits according to 
>>>>>> http://www.ietf.org/id-info/checklist :
>>>>>>
>>>>>> ---------------------------------------------------------------------------- 
>>>>>>
>>>>>>
>>>>>>    == There are 2 instances of lines with non-RFC2606-compliant 
>>>>>> FQDNs in
>>>>>> the
>>>>>>       document.
>>>>>>
>>>>>>
>>>>>>    Checking references for intended status: Proposed Standard
>>>>>>
>>>>>> ---------------------------------------------------------------------------- 
>>>>>>
>>>>>>
>>>>>>       (See RFCs 3967 and 4897 for information about using normative
>>>>>> references
>>>>>>       to lower-maturity documents in RFCs)
>>>>>>
>>>>>>    == Outdated reference: A later version (-14) exists of
>>>>>>       draft-ietf-dane-srv-12
>>>>>>
>>>>>>    ** Downref: Normative reference to an Informational RFC: RFC 4949
>>>>>>
>>>>>>    -- Possible downref: Non-RFC (?) normative reference: ref. 
>>>>>> 'XEP-0220'
>>>>>>
>>>>>>    == Outdated reference: draft-ietf-uta-xmpp has been published 
>>>>>> as RFC
>>>>>> 7590
>>>>>>
>>>>>>    -- Obsolete informational reference (is this intentional?): 
>>>>>> RFC 3920
>>>>>>       (Obsoleted by RFC 6120)
>>>>>>
>>>>>>
>>>>>>       Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 3 
>>>>>> comments
>>>>>> (—).
>>>>>>
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>>
>
>


From nobody Tue Sep  8 11:31:35 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2291F1A0035; Tue,  8 Sep 2015 11:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level: 
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 9HD9N6q0ZtCn; Tue,  8 Sep 2015 11:31:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id B4CAD1B3A25; Tue,  8 Sep 2015 11:31:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A60E8180092; Tue,  8 Sep 2015 11:31:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150908183125.A60E8180092@rfc-editor.org>
Date: Tue,  8 Sep 2015 11:31:25 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/K1vgNjcdi1yJdeB6CFJgp460CGs>
Cc: drafts-update-ref@iana.org, xmpp@ietf.org, rfc-editor@rfc-editor.org
Subject: [xmpp] RFC 7622 on Extensible Messaging and Presence Protocol (XMPP): Address Format
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Sep 2015 18:31:34 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7622

        Title:      Extensible Messaging and Presence Protocol (XMPP):
                    Address Format 
        Author:     P. Saint-Andre
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2015
        Mailbox:    peter@andyet.com
        Pages:      27
        Characters: 60008
        Obsoletes:  RFC 6122

        I-D Tag:    draft-ietf-xmpp-6122bis-24.txt

        URL:        https://www.rfc-editor.org/info/rfc7622

        DOI:        http://dx.doi.org/10.17487/RFC7622

This document defines the address format for the Extensible Messaging
and Presence Protocol (XMPP), including support for code points
outside the ASCII range.  This document obsoletes RFC 6122.

This document is a product of the Extensible Messaging and Presence Protocol 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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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



From nobody Wed Sep  9 07:38:09 2015
Return-Path: <peter@andyet.net>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74B311A1BC6 for <xmpp@ietfa.amsl.com>; Wed,  9 Sep 2015 07:38:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 ZyY2Ev5bG3zT for <xmpp@ietfa.amsl.com>; Wed,  9 Sep 2015 07:38:02 -0700 (PDT)
Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com [209.85.213.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA8A71B29F6 for <xmpp@ietf.org>; Wed,  9 Sep 2015 07:38:00 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so105987284igb.0 for <xmpp@ietf.org>; Wed, 09 Sep 2015 07:38:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=keZp7HVDDC0uJJXYZAFTZsuuCt4WlP75JAEW5SIQzPA=; b=WwnsA+QLdHW96YuBegREiVujMrIRJy+Sz+rF+soWE9YFYsISL1bnwkLOHBx0FLBTSe jf7BoNtzrF3OMWnkX6H0xFZ01SoLE43bnrP9Xil008Ia5i9wzCNimxvlAmxQBMutlhgs 0SYj470cchQOAbHX6iAir8S+YTdldEeOA+aXPTztHCKzPup/r1G9ll1n+bi8A/UBO2xw W9DCVlCXEpb7ujEPRLU3C2nyX9krcq7XjaAIwRf9XE84V3VXDjk2K9nBoVbuBMW7kq/T hTHfg850yiDE+paLYrxLqdWbwmhUBmEnXMhnn4l4As6NwQV/2cP/WLKq0Lnpgm27K1aj YyYg==
X-Gm-Message-State: ALoCoQm2Z6k4I4kPlhuW6jvonGRkwIBTmtNjc/AhxJMgz0e2EVs/k+lpWobnfT3vYl0G6dq1M5ZY
X-Received: by 10.50.66.232 with SMTP id i8mr52569810igt.34.1441809479920; Wed, 09 Sep 2015 07:37:59 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id 12sm4667171ioe.40.2015.09.09.07.37.59 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Sep 2015 07:37:59 -0700 (PDT)
To: Peter Saint-Andre - &yet <peter@andyet.net>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
References: <20150805150244.8466.87044.idtracker@ietfa.amsl.com> <55C2945E.9010503@andyet.net>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F04446.1010105@andyet.net>
Date: Wed, 9 Sep 2015 08:37:58 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55C2945E.9010503@andyet.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/jRaIfdTdqt1PEn5UkoiEAEemfAw>
Cc: draft-ietf-xmpp-posh.shepherd@ietf.org, xmpp-chairs@ietf.org, xmpp@ietf.org, draft-ietf-xmpp-posh.ad@ietf.org, draft-ietf-xmpp-posh@ietf.org
Subject: Re: [xmpp] Stephen Farrell's No Objection on draft-ietf-xmpp-posh-04: (with COMMENT)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2015 14:38:08 -0000

Hi Stephen, here's further follow-up on the fingerprint syntax...

On 8/5/15 4:55 PM, Peter Saint-Andre - &yet wrote:

>> 3.1: fingerprints: sigh, I wish we could agree to just
>> do this kind of thing a few times and not re-do it over
>> and over and over (but we always do;-). RFC6920 could
>> probably have been used there (caveat lector: that's an
>> RFC I'm a co-author on).
>
> Sorry, I should have thought of RFC 6920 in this context. :(
>
> Matt and I will look at this. (He is offline this week so we won't be
> able to sync up until then.) We will also reach out to implementers
> because as I recall we chose this approach in part for ease of
> implementation.

We have investigated the possibility of switching from the syntax 
currently defined to RFC 6920. As far as we can see, that would involve 
something like this:

OLD

{
  "fingerprints": [
   {
    "sha-256":"4/mggdlVx8A3pvHAWW5sD+qJyMtUHgiRuPjVC48N0XQ="
   }
  ],
  "expires": 604800
}

NEW

{
  "fingerprints": [
   {
    "hash":"ni:///sha-256;4/mggdlVx8A3pvHAWW5sD+qJyMtUHgiRuPjVC48N0XQ="
   }
  ],
  "expires": 604800
}

The former requires only JSON parsing, whereas the latter requires both 
JSON parsing and URI parsing. Given that folks have already implemented 
the former, we think that asking them to add URI parsing for (in our 
opinion) somewhat negligible gain isn't worth the effort at this point.

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Wed Sep  9 08:06:16 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C4E91B3700; Wed,  9 Sep 2015 08:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 RpBbutp960l3; Wed,  9 Sep 2015 08:06:13 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DC7B1B367F; Wed,  9 Sep 2015 08:06:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B7B84BE88; Wed,  9 Sep 2015 16:06:11 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yobOa-yrGxQg; Wed,  9 Sep 2015 16:06:11 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 78740BE87; Wed,  9 Sep 2015 16:06:11 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1441811171; bh=tbimiaMy70oBcVT0Xx7iiJ3yA+47pVVRI2BZ0vN+T3g=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=HUbCmtFaIiybaNL1Qm12Ear6NJEOoWqADVuQ7IyzOesi4xfpNZxG56TCR90e5OEoa GeIeCGh48QVi3Accl+eAZ9RRlqd16SPuDcTTRxUeduGkBhpV89+ZDD+T/WgHMsHvQQ qoq6k5rsjgQNrHyxNbi0JH+rD4J2EivceluXUXFI=
To: Peter Saint-Andre - &yet <peter@andyet.net>, The IESG <iesg@ietf.org>
References: <20150805150244.8466.87044.idtracker@ietfa.amsl.com> <55C2945E.9010503@andyet.net> <55F04446.1010105@andyet.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <55F04AE3.3030309@cs.tcd.ie>
Date: Wed, 9 Sep 2015 16:06:11 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55F04446.1010105@andyet.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/U1wGIlpjLMmlmf5LegxOKpw0R9s>
Cc: draft-ietf-xmpp-posh.shepherd@ietf.org, xmpp-chairs@ietf.org, xmpp@ietf.org, draft-ietf-xmpp-posh.ad@ietf.org, draft-ietf-xmpp-posh@ietf.org
Subject: Re: [xmpp] Stephen Farrell's No Objection on draft-ietf-xmpp-posh-04: (with COMMENT)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2015 15:06:15 -0000

On 09/09/15 15:37, Peter Saint-Andre - &yet wrote:
> 
> The former requires only JSON parsing, whereas the latter requires both
> JSON parsing and URI parsing. Given that folks have already implemented
> the former, we think that asking them to add URI parsing for (in our
> opinion) somewhat negligible gain isn't worth the effort at this point.

Yep. It's a bit sad, but there we go.

S.


From nobody Wed Sep  9 15:52:36 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D8A31B31D2; Wed,  9 Sep 2015 15:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 EbkGEIL7VnTw; Wed,  9 Sep 2015 15:52:33 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B8941B29B3; Wed,  9 Sep 2015 15:52:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150909225233.30189.64709.idtracker@ietfa.amsl.com>
Date: Wed, 09 Sep 2015 15:52:33 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/6-pZRDzV6ejmaypu1PzhTSk5oZo>
Cc: xmpp@ietf.org
Subject: [xmpp] I-D Action: draft-ietf-xmpp-posh-06.txt
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2015 22:52:34 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Extensible Messaging and Presence Protocol Working Group of the IETF.

        Title           : PKIX over Secure HTTP (POSH)
        Authors         : Matthew Miller
                          Peter Saint-Andre
	Filename        : draft-ietf-xmpp-posh-06.txt
	Pages           : 18
	Date            : 2015-09-09

Abstract:
   Experience has shown that it is difficult to deploy proper PKIX
   certificates for TLS in multi-tenant environments.  As a result,
   domains hosted in such environments often deploy applications using
   certificates that identify the hosting service, not the hosted
   domain.  Such deployments force end users and peer services to accept
   a certificate with an improper identifier, resulting in degraded
   security.  This document defines two methods that make it easier to
   deploy certificates for proper server identity checking in non-HTTP
   application protocols.  While these methods were developed for use in
   the Extensible Messaging and Presence Protocol (XMPP) as a Domain
   Name Association (DNA) prooftype, they might also be usable in other
   non-HTTP application protocols.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-xmpp-posh/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-xmpp-posh-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-posh-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep  9 15:55:31 2015
Return-Path: <mamille2@cisco.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16CE71B4A74 for <xmpp@ietfa.amsl.com>; Wed,  9 Sep 2015 15:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 TAu9hnheZgji for <xmpp@ietfa.amsl.com>; Wed,  9 Sep 2015 15:55:29 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC3C71B4A71 for <xmpp@ietf.org>; Wed,  9 Sep 2015 15:55:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2905; q=dns/txt; s=iport; t=1441839328; x=1443048928; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=4ilwYLexeDkd4qQX3DUqnfVEvQqCqiOBEc/M50z3bPE=; b=hzf//F+roqXufZHXk/5RD2sF/tBoVYhGQTQ7m6gmc0+t8vaojg1HwzYk +ONRi0mYxlzxxCsgP3qh1CYEv+HtfhHmXg5H80KngF3qxJeK/1JJ7TIbn Gjko7wfONJhAo24K6T7/8V5v2WRln8Dghto4MyQ3HfaQVLEFK6CiBI/3v s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DwAQB3tvBV/5BdJa1TAQmDI1RpvSsBDYFtCoV5AoE9OBQBAQEBAQEBgQqEJAEBBAEBAWsKEQsYCRYPCQMCAQIBFTAGDQQCAgEBBYglDcsDAQEBAQEBAQMBAQEBAQEBARqLboQvAREYOoQsBYx3dYdqhQqHcIFMRoNtgnyKS4cyJoIPHYFzIy8BiEgBAQE
X-IronPort-AV: E=Sophos;i="5.17,499,1437436800"; d="scan'208";a="25705932"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-7.cisco.com with ESMTP; 09 Sep 2015 22:55:27 +0000
Received: from [64.101.72.38] ([64.101.72.38]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t89MtRU4007628 for <xmpp@ietf.org>; Wed, 9 Sep 2015 22:55:28 GMT
To: XMPP Group <xmpp@ietf.org>
References: <20150909225233.30189.64709.idtracker@ietfa.amsl.com>
From: =?UTF-8?B?4oyYIE1hdHQgTWlsbGVy?= <mamille2@cisco.com>
Message-ID: <55F0B8DF.6020607@cisco.com>
Date: Wed, 9 Sep 2015 16:55:27 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20150909225233.30189.64709.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/N9DNpZo-8PiE_g6tvmUQRXGaNgs>
Subject: Re: [xmpp] I-D Action: draft-ietf-xmpp-posh-06.txt
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2015 22:55:31 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

This revision expands the examples to include more than one hash type
(sha-256, sha-512).


- -- 
- - m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

On 9/9/15 4:52 PM, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Extensible Messaging
> and Presence Protocol Working Group of the IETF.
> 
> Title           : PKIX over Secure HTTP (POSH) Authors         :
> Matthew Miller Peter Saint-Andre Filename        :
> draft-ietf-xmpp-posh-06.txt Pages           : 18 Date            :
> 2015-09-09
> 
> Abstract: Experience has shown that it is difficult to deploy
> proper PKIX certificates for TLS in multi-tenant environments.  As
> a result, domains hosted in such environments often deploy
> applications using certificates that identify the hosting service,
> not the hosted domain.  Such deployments force end users and peer
> services to accept a certificate with an improper identifier,
> resulting in degraded security.  This document defines two methods
> that make it easier to deploy certificates for proper server
> identity checking in non-HTTP application protocols.  While these
> methods were developed for use in the Extensible Messaging and
> Presence Protocol (XMPP) as a Domain Name Association (DNA)
> prooftype, they might also be usable in other non-HTTP application
> protocols.
> 
> 
> The IETF datatracker status page for this draft is: 
> https://datatracker.ietf.org/doc/draft-ietf-xmpp-posh/
> 
> There's also a htmlized version available at: 
> https://tools.ietf.org/html/draft-ietf-xmpp-posh-06
> 
> A diff from the previous version is available at: 
> https://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-posh-06
> 
> 
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at
> tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at: 
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________ I-D-Announce
> mailing list I-D-Announce@ietf.org 
> https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft
> directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJV8LjfAAoJEDWi+S0W7cO1AMUH/RXF55Nm9WAvSS4cCUj3Ms+r
Hz/gAbfKhmU7o74K5cqoaAMvtziUFf2vOy3FDLlOLo9RA0Btnfnt98iHs77WrTsB
l1qtnqxYIdh3yn289wi6mHXVL/A34Z1SkxAJp+5qvNoNzfuppe2bH7ZMHRPRVH/P
Fflsl91nt+w3Svox8J330gH4MXrt9IVFW+QOujmF0IkjZant+tjwICPgCNVCyyk7
lV+wlis0Odsrz6KyaOUhpW1BLSGjKkkQ751qDRKYVrviX1TJO6RHIJ5mGNO3u7W6
n1DPBdYhHlvdTOMGJbf8780aB36p5h8hB7VykaZ9DeQGAtrwN4uzERgNqLOQpQk=
=wQZg
-----END PGP SIGNATURE-----


From nobody Wed Sep  9 17:40:58 2015
Return-Path: <ben@nostrum.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB0D81B4F27; Wed,  9 Sep 2015 17:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 9xklL15fp0GQ; Wed,  9 Sep 2015 17:40:54 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9FE81B4F26; Wed,  9 Sep 2015 17:40:54 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t8A0ehXP019527 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 9 Sep 2015 19:40:53 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: "Ben Campbell" <ben@nostrum.com>
To: IESG <iesg@ietf.org>
Date: Wed, 09 Sep 2015 19:40:43 -0500
Message-ID: <57D86598-C34D-472B-A627-99339D016BB7@nostrum.com>
MIME-Version: 1.0
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/uSLZ4mqPAFfGN2g48ot-JnHa-oQ>
Cc: xmpp-chairs@ietf.org, XMPP Group <xmpp@ietf.org>, draft-ietf-xmpp-posh@ietf.org
Subject: [xmpp] Approved: draft-ietf-xmpp-posh-06
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2015 00:40:55 -0000

Hello IESG Secretary (BCC)

draft-ietf-xmpp-posh-06 is approved. There are no RFC Editor Notes.

Thanks!

Ben.


From nobody Wed Sep  9 17:42:45 2015
Return-Path: <ben@nostrum.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F245D1B4F63; Wed,  9 Sep 2015 17:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 HHgSYxMFo1dh; Wed,  9 Sep 2015 17:42:42 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 395791B4F61; Wed,  9 Sep 2015 17:42:42 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t8A0gUH3019708 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 9 Sep 2015 19:42:41 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: "Ben Campbell" <ben@nostrum.com>
To: IESG <iesg@ietf.org>
Date: Wed, 09 Sep 2015 19:42:30 -0500
Message-ID: <66370ECD-09C4-4146-AE98-D7053AADA832@nostrum.com>
MIME-Version: 1.0
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/C4TIWceZfMc6J0mBvUIKk1akTmw>
Cc: xmpp-chairs@ietf.org, draft-ietf-xmpp-dna@tools.ietf.org, XMPP Working Group <xmpp@ietf.org>
Subject: [xmpp] Approved: draft-ietf-xmpp-dna-11
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2015 00:42:43 -0000

Hello IESG Secretary (BCC)

draft-ietf-xmpp-dna-11 is approved. There are no RFC Editor notes.

Thanks!

Ben.


From nobody Wed Sep  9 17:54:12 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B81DB1B37BC; Wed,  9 Sep 2015 17:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 32qHYcD3BPZ9; Wed,  9 Sep 2015 17:54:09 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C51191B4C01; Wed,  9 Sep 2015 17:54:05 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150910005405.1167.42876.idtracker@ietfa.amsl.com>
Date: Wed, 09 Sep 2015 17:54:05 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/euCG7kc1PdgkGB2sU3vyD5-tk2g>
Cc: xmpp chair <xmpp-chairs@ietf.org>, xmpp mailing list <xmpp@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [xmpp] Protocol Action: 'PKIX over Secure HTTP (POSH)' to Proposed Standard (draft-ietf-xmpp-posh-06.txt)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2015 00:54:10 -0000

The IESG has approved the following document:
- 'PKIX over Secure HTTP (POSH)'
  (draft-ietf-xmpp-posh-06.txt) as Proposed Standard

This document is the product of the Extensible Messaging and Presence
Protocol Working Group.

The IESG contact persons are Barry Leiba, Ben Campbell and Alissa Cooper.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-xmpp-posh/





Technical Summary

This document defines the "PKIX over Secure HTTP (POSH)" prooftype, to
be used as part of the XMPP Domain Name Assertion (DNA) framework. From
the abstract:

"Experience has shown that it is extremely difficult to deploy proper
PKIX certificates for TLS in multi-tenanted environments.  As a result,
domains hosted in such environments often deploy applications using
certificates that identify the hosting service, not the hosted domain.
Such deployments force end users and peer services to accept a
certificate with an improper identifier, resulting in obvious security
implications.  This document defines two methods that make it easier to
deploy certificates for proper server identity checking in non-HTTP
application protocols.  While these methods developed for use in the
Extensible Messaging and Presence Protocol (XMPP) as a Domain Name
Association (DNA) prooftype, they might also be usable in other non-HTTP
application protocols."

The XMPP working group believes that this technology is ready for wider
implementation, and would benefit from interoperability testing.
Therefore we request the document to be published as a "Proposed
Standard".


Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

Document Quality

During discussion in XMPP, it became apparent that POSH might have more
general applicability. There was a POSH BoF in the Security area at IETF
87. While there was recognition that POSH could be generally useful,
there was no consensus to expand the effort beyond the needs of XMPP.
Therefore POSH was adopted as an XMPP work item, with the idea that we
would make it as general as we reasonable could without bogging down the
work, but that we would not attempt to meet the specific requirements
for applications other than XMPP.

The  chairs believe POSH has reached a broad consensus in XMPP. There
has been considerable review in XMPP, and in the Security area due to
the BoF. POSH does not need targeted reviews beyond the usual Gen-ART,
SecDir, etc reviews.

Reviews have concentrated primarily on clarifying the specification rather
than altering how it works. Some members of the working group (including
an author) have expressed the opinion that this is a stopgap technology rather
than a long-term plan.

At the time of this writing, the shepherd is aware of two experimental
implementations which have not been deployed - however various implementors
of XMPP have expressed some interest, and some are in progress.

Personnel

The document shepherd is Dave Cridland.
The responsible Area Director is Ben Campbell.


From nobody Wed Sep  9 17:56:06 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460DC1B506D; Wed,  9 Sep 2015 17:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 UAU4RAPAkkxD; Wed,  9 Sep 2015 17:56:03 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EBB9E1B5070; Wed,  9 Sep 2015 17:56:01 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150910005601.2591.65689.idtracker@ietfa.amsl.com>
Date: Wed, 09 Sep 2015 17:56:01 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/bXZsT8voXppNl3A39STdC28sMKU>
Cc: xmpp chair <xmpp-chairs@ietf.org>, xmpp mailing list <xmpp@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [xmpp] Protocol Action: 'Domain Name Associations (DNA) in the Extensible Messaging and Presence Protocol (XMPP)' to Proposed Standard (draft-ietf-xmpp-dna-11.txt)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2015 00:56:05 -0000

The IESG has approved the following document:
- 'Domain Name Associations (DNA) in the Extensible Messaging and
   Presence Protocol (XMPP)'
  (draft-ietf-xmpp-dna-11.txt) as Proposed Standard

This document is the product of the Extensible Messaging and Presence
Protocol Working Group.

The IESG contact persons are Barry Leiba, Ben Campbell and Alissa Cooper.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-xmpp-dna/





Technical Summary

This document defines the XMPP Domain Name Association (DNA) framework. The
abstract states the document does two things to improve security in XMPP:

     "First, it specifies how to
   establish a strong association between a domain name and an XML
   stream, using the concept of "prooftypes".  Second, it describes how
   to securely delegate a service domain name (e.g., example.com) to a
   target server host name (e.g., hosting.example.net) [...]"

Overall, the document establishes a framework for server authentication
mechanisms, known as "prooftypes", by which servers can provide multiple
forms of proof of their identity to both clients and other peer servers.

Working Group Summary

The Working Group believes the document is ready to be used as the base
framework, and indeed is already so used by draft-ietf-xmpp-posh. On that
basis it is requested to be published as a Standards Track document at
"Proposed Standard".

Document Quality

The majority of reviews concentrated on two areas:

a) Avoiding the considerable overlap between this document and several
others, including RFC 6120, RFC 6125, XEP-0220, XEP-0288 and XEP-0344.

b) Correcting errors within the (highly complex) area of server to server
authentication.

It should be noted that much of the document is simply describing the
state of the art with respect to server to server authentication, which
is spread over several documents, and noting the points where
authentication and authorization decisions are required.

The chairs believe that consensus has been reached for the document to be
published. As this document essentially distils the somewhat scattered
specification and knowledge of S2S auth, it would be fair to say it has
high implementation already, however multiple implementations have
adopted the model described in this document as the basis for work
underway for DANE, POSH and other prooftypes.

Personnel

   The Document Shepherd is Dave Cridland.
   The responsible Area Director is Ben Campbell.


From nobody Thu Sep 10 08:37:44 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F0641B6A4F for <xmpp@ietfa.amsl.com>; Thu, 10 Sep 2015 08:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level: 
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 feKsOYtZwBwE for <xmpp@ietfa.amsl.com>; Thu, 10 Sep 2015 08:37:42 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 470E11B6999 for <xmpp@ietf.org>; Thu, 10 Sep 2015 08:37:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 59C0218046B; Thu, 10 Sep 2015 08:37:29 -0700 (PDT)
To: peter@andyet.com, ben@nostrum.com, alissa@cooperw.in, barryleiba@computer.org, jhildebr@cisco.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150910153729.59C0218046B@rfc-editor.org>
Date: Thu, 10 Sep 2015 08:37:29 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/wSjCQ1QWXKs8AuLneuFwoHOFvH8>
Cc: bortzmeyer+ietf@nic.fr, xmpp@ietf.org, rfc-editor@rfc-editor.org
Subject: [xmpp] [Editorial Errata Reported] RFC7622 (4470)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2015 15:37:43 -0000

The following errata report has been submitted for RFC7622,
"Extensible Messaging and Presence Protocol (XMPP): Address Format".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7622&eid=4470

--------------------------------------
Type: Editorial
Reported by: Stéphane Bortzmeyer <bortzmeyer+ietf@nic.fr>

Section: 3.5

Original Text
-------------
<king@example.com/&#x265A>;

Corrected Text
--------------
<king@example.com/&#x265A;>

Notes
-----
Right angle bracket arrived too soon.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC7622 (draft-ietf-xmpp-6122bis-24)
--------------------------------------
Title               : Extensible Messaging and Presence Protocol (XMPP): Address Format
Publication Date    : September 2015
Author(s)           : P. Saint-Andre
Category            : PROPOSED STANDARD
Source              : Extensible Messaging and Presence Protocol
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG


From nobody Thu Sep 10 08:51:57 2015
Return-Path: <peter@andyet.net>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52F051B340B for <xmpp@ietfa.amsl.com>; Thu, 10 Sep 2015 08:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 D45hrecX4gy1 for <xmpp@ietfa.amsl.com>; Thu, 10 Sep 2015 08:51:52 -0700 (PDT)
Received: from mail-ig0-f170.google.com (mail-ig0-f170.google.com [209.85.213.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 711161B3224 for <xmpp@ietf.org>; Thu, 10 Sep 2015 08:51:52 -0700 (PDT)
Received: by igxx6 with SMTP id x6so18643631igx.1 for <xmpp@ietf.org>; Thu, 10 Sep 2015 08:51:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=LiWt5FWseuSViszXBdazhdsi3qCPvW8A5zLa3kd6U9c=; b=eyk+9OLiknbDqozs5daAuAB7t63aRbnaVIdEBWUZ8ZJYQ9PWv5WavVENTVDEpCxkLo 28nRIYJrskKN+LqMOzr7/k574rjbyIGp+doVXqTe9/AaAxf6fDb7uTO3pgPQUe12Pt1q a/5JXXmLC8Fwb+5vNW8pz2svC807qbNgVg9SJoiznwyRpGp2VqEb9BIefdofntybCgLQ 6D+wRgILol/NOBLnntRERhkkZ8wPIhlozeYKqwspNkXY5MTVLWZWxCVQJmq1H4eCQbQO ROhvW4S1AsdjmGnV+/7OIehLRz3e/rpuvaCyUDwCHca8U2sRa6TAoXcQ6DUqOEn6EGwu wVcA==
X-Gm-Message-State: ALoCoQkPQYJvFbr/83CNVrIvl9lLdjWeP9ENNf2UNdTAMtAwr6D6FLoDnbLErv9OPtxgcaHaeRWB
X-Received: by 10.50.221.104 with SMTP id qd8mr7575213igc.62.1441900311645; Thu, 10 Sep 2015 08:51:51 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id f16sm4485069igt.5.2015.09.10.08.51.50 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Sep 2015 08:51:50 -0700 (PDT)
To: RFC Errata System <rfc-editor@rfc-editor.org>, ben@nostrum.com, alissa@cooperw.in, barryleiba@computer.org, jhildebr@cisco.com
References: <20150910153729.59C0218046B@rfc-editor.org>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F1A715.9090308@andyet.net>
Date: Thu, 10 Sep 2015 09:51:49 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20150910153729.59C0218046B@rfc-editor.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/qCQ9QoKem04qoTQWvyS6yUFa548>
Cc: bortzmeyer+ietf@nic.fr, xmpp@ietf.org
Subject: Re: [xmpp] [Editorial Errata Reported] RFC7622 (4470)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2015 15:51:54 -0000

This erratum is correct that two characters are transposed in that example.

On 9/10/15 9:37 AM, RFC Errata System wrote:
> The following errata report has been submitted for RFC7622,
> "Extensible Messaging and Presence Protocol (XMPP): Address Format".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7622&eid=4470
>
> --------------------------------------
> Type: Editorial
> Reported by: Stéphane Bortzmeyer <bortzmeyer+ietf@nic.fr>
>
> Section: 3.5
>
> Original Text
> -------------
> <king@example.com/&#x265A>;
>
> Corrected Text
> --------------
> <king@example.com/&#x265A;>
>
> Notes
> -----
> Right angle bracket arrived too soon.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC7622 (draft-ietf-xmpp-6122bis-24)
> --------------------------------------
> Title               : Extensible Messaging and Presence Protocol (XMPP): Address Format
> Publication Date    : September 2015
> Author(s)           : P. Saint-Andre
> Category            : PROPOSED STANDARD
> Source              : Extensible Messaging and Presence Protocol
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG
>


From nobody Sat Sep 12 10:32:08 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED0E31B41E6 for <xmpp@ietfa.amsl.com>; Sat, 12 Sep 2015 10:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 UT3vq2IFL5TS for <xmpp@ietfa.amsl.com>; Sat, 12 Sep 2015 10:32:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 849D21B4069 for <xmpp@ietf.org>; Sat, 12 Sep 2015 10:32:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <xmpp@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150912173205.23037.68854.idtracker@ietfa.amsl.com>
Date: Sat, 12 Sep 2015 10:32:05 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/AfEHSIIFMszu-Hr1jjElV-3PQxc>
Subject: [xmpp] Milestones changed for xmpp WG
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Sep 2015 17:32:07 -0000

Changed milestone "Define a solution for internationalization of XMPP
addresses (Update of RFC 6122)", resolved as "Done".

URL: https://datatracker.ietf.org/wg/xmpp/charter/


From nobody Sat Sep 12 10:32:24 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C17D1B3CC3 for <xmpp@ietfa.amsl.com>; Sat, 12 Sep 2015 10:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 XSFEcmAu1jOJ for <xmpp@ietfa.amsl.com>; Sat, 12 Sep 2015 10:32:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 832001B4349 for <xmpp@ietf.org>; Sat, 12 Sep 2015 10:32:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <xmpp@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150912173221.1376.96641.idtracker@ietfa.amsl.com>
Date: Sat, 12 Sep 2015 10:32:21 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/8ZLrDKbsjS8meMnLGpjrHjz_J_Q>
Subject: [xmpp] Milestones changed for xmpp WG
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Sep 2015 17:32:23 -0000

Changed milestone "Define a solution for server-to-server connection
reuse.", resolved as "Done".

URL: https://datatracker.ietf.org/wg/xmpp/charter/


From nobody Sat Sep 12 10:35:02 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 528E51B3416; Sat, 12 Sep 2015 10:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level: 
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 2iN8eqAy5OxJ; Sat, 12 Sep 2015 10:34:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 36F541A1B2C; Sat, 12 Sep 2015 10:34:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A93B7180204; Sat, 12 Sep 2015 10:34:39 -0700 (PDT)
To: bortzmeyer+ietf@nic.fr, peter@andyet.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150912173439.A93B7180204@rfc-editor.org>
Date: Sat, 12 Sep 2015 10:34:39 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/t8tHZ1IexeiARyJjYtFpQZzRHqQ>
Cc: ben@nostrum.com, iesg@ietf.org, xmpp@ietf.org, rfc-editor@rfc-editor.org
Subject: [xmpp] [Errata Held for Document Update] RFC7622 (4470)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Sep 2015 17:35:00 -0000

The following errata report has been held for document update 
for RFC7622, "Extensible Messaging and Presence Protocol (XMPP): Address Format". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7622&eid=4470

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Stéphane Bortzmeyer <bortzmeyer+ietf@nic.fr>
Date Reported: 2015-09-10
Held by: Ben Campbell (IESG)

Section: 3.5

Original Text
-------------
<king@example.com/&#x265A>;

Corrected Text
--------------
<king@example.com/&#x265A;>

Notes
-----
Right angle bracket arrived too soon.

--------------------------------------
RFC7622 (draft-ietf-xmpp-6122bis-24)
--------------------------------------
Title               : Extensible Messaging and Presence Protocol (XMPP): Address Format
Publication Date    : September 2015
Author(s)           : P. Saint-Andre
Category            : PROPOSED STANDARD
Source              : Extensible Messaging and Presence Protocol
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG


From nobody Sat Sep 12 10:38:34 2015
Return-Path: <ben@nostrum.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47A621AD365 for <xmpp@ietfa.amsl.com>; Sat, 12 Sep 2015 10:38:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level: 
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 pWorwfLiejhU for <xmpp@ietfa.amsl.com>; Sat, 12 Sep 2015 10:38:32 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DD9D1A00CC for <xmpp@ietf.org>; Sat, 12 Sep 2015 10:38:32 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t8CHcLGw099908 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <xmpp@ietf.org>; Sat, 12 Sep 2015 12:38:31 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: "Ben Campbell" <ben@nostrum.com>
To: "XMPP Working Group" <xmpp@ietf.org>
Date: Sat, 12 Sep 2015 12:38:21 -0500
Message-ID: <241FC222-01CD-47DB-ACD8-04A665C8BAFD@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/ze6JsEfMU-7ew5YF0kbLD9j6yp0>
Subject: [xmpp] XMPP Completes
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Sep 2015 17:38:33 -0000

Hi,

With the recent approval of the posh and dna drafts, xmpp has completed 
all of it's milestones. The working group will now close. The mailing 
list will remain open in case there is need of further discussion of 
those drafts as they go through the RFC editing process.

I want to thank everyone for the work over the years. The group has been 
around for a long time, and undergone many changes. Kudos to all those 
who stuck around for the ride.

Thanks!

Ben.


From nobody Sat Sep 12 12:34:40 2015
Return-Path: <zash@zash.se>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFDE91A8873 for <xmpp@ietfa.amsl.com>; Sat, 12 Sep 2015 12:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.348
X-Spam-Level: 
X-Spam-Status: No, score=0.348 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_SE=0.35, SPF_PASS=-0.001] autolearn=no
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 MGFo0HtjvA3E for <xmpp@ietfa.amsl.com>; Sat, 12 Sep 2015 12:34:37 -0700 (PDT)
Received: from mail.zash.se (ip66.hethane.riksnet.nu [85.11.25.66]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 110CB1B38EF for <xmpp@ietf.org>; Sat, 12 Sep 2015 12:34:37 -0700 (PDT)
Received: from [IPv6:2001:470:def1:0:bc39:cdd:cb8e:113a] (unknown [IPv6:2001:470:def1:0:bc39:cdd:cb8e:113a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zash) by mail.zash.se (Postfix) with ESMTPSA id 6E6F660E99 for <xmpp@ietf.org>; Sat, 12 Sep 2015 21:34:33 +0200 (CEST)
To: xmpp@ietf.org
References: <241FC222-01CD-47DB-ACD8-04A665C8BAFD@nostrum.com>
From: Kim Alvefur <zash@zash.se>
Openpgp: id=3E52119EF853C59678DBBF6BADED9A77B67AD329; url=http://zash.se/~zash/pubkey.asc
X-Enigmail-Draft-Status: N1110
Message-ID: <55F47E48.3090003@zash.se>
Date: Sat, 12 Sep 2015 21:34:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <241FC222-01CD-47DB-ACD8-04A665C8BAFD@nostrum.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Q47SQQmSeqBGQXGjLxvbKcMNqLl3dgL5C"
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/GVdQVAg-202-_1TkuZwWiJ_5e28>
Subject: Re: [xmpp] XMPP Completes
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Sep 2015 19:34:39 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Q47SQQmSeqBGQXGjLxvbKcMNqLl3dgL5C
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi!

With the WG closing, I'd like to draw some attention to the dropped
end-to-end encryption goal, as a wild ProtoXEP appeared:

http://conversations.im/omemo/

--=20
Kim "Zash" Alvefur


--Q47SQQmSeqBGQXGjLxvbKcMNqLl3dgL5C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iQIcBAEBCgAGBQJV9H5JAAoJEK3tmne2etMppR4P/jivhObFz3cltbA3jncDY/el
YK6DnkVJxQ4tYh3d0EZQqq+h4My+q729q4wYKlt7s1Xy8MW/uanhq0p7de6n9Cns
mvinSlQGlT8WvdCZye2sgXN1Tkjc7tomyqfRJQNwCIbZE5EQ1InGrd0uXxHAlKGh
AW9V3vVJKgFRklwBGoZpWTMlm7Tm+C3VPBZJPKU+TkTgREni6994Qc7k3LkRdluE
1wTKE/MtdTycwfQqwtcL6vlI0P18ZMEdTx856vEaHL1fNFlRh52znUamceg8CNbK
ehL03cJIQUJqpQgok3eaN0OdJ9aVCIJAygKQpG5ctJ54wbn8a4mW2SCkcwQS/x3o
hj3pyWjCm0GsR0e9EXX+mpmm1mkYmQPfhJOMnVyNGMr9PGqbg3LF3NTOdhTiuzQd
/ItdzINk3LqIyxEfVt1ang4pZcEPmT9CPrOPOLcEAktMmvIfvsliUWrY5zVgaSXC
YngU00aVVaqRLhQG0+6sH5omdjcwWrzkRGhMWGi8pqmSRDEvIw4ICEWb6Lcp+Y0M
DrFg9+VYGpoak7P4MSke0QBWQhgVku3XvNJ1umJgCOLm/cU7Xr9mgM6MYasi4Cj5
3COzX5Z8MGcXMGXFt3XCA47P969sqJgrwx/v+Es97abYw/7rIoCwy3coYqgr7y7s
RgTHzhVOtATjXDBDg1XJ
=oUAd
-----END PGP SIGNATURE-----

--Q47SQQmSeqBGQXGjLxvbKcMNqLl3dgL5C--


From nobody Sat Sep 12 14:21:19 2015
Return-Path: <ben@nostrum.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43CA11B4A58 for <xmpp@ietfa.amsl.com>; Sat, 12 Sep 2015 14:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 EuslYmrYt6GJ for <xmpp@ietfa.amsl.com>; Sat, 12 Sep 2015 14:21:17 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F19231A1A78 for <xmpp@ietf.org>; Sat, 12 Sep 2015 14:21:16 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t8CLL6Q8018744 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 12 Sep 2015 16:21:16 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: "Ben Campbell" <ben@nostrum.com>
To: "Kim Alvefur" <zash@zash.se>
Date: Sat, 12 Sep 2015 16:21:05 -0500
Message-ID: <D44C39F2-A675-497C-A2D0-7CE2FE39253B@nostrum.com>
In-Reply-To: <55F47E48.3090003@zash.se>
References: <241FC222-01CD-47DB-ACD8-04A665C8BAFD@nostrum.com> <55F47E48.3090003@zash.se>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/fxF36rByglk-yH_61j7CW2nd8so>
Cc: xmpp@ietf.org
Subject: Re: [xmpp] XMPP Completes
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Sep 2015 21:21:18 -0000

Certainly. If we find momentum to work on e2e xmpp crypto in the IETF, 
we will find or make a place to do the work, whether that means 
restarting the working group or something else.

Thanks for reminding us :-)

Ben.



On 12 Sep 2015, at 14:34, Kim Alvefur wrote:

> Hi!
>
> With the WG closing, I'd like to draw some attention to the dropped
> end-to-end encryption goal, as a wild ProtoXEP appeared:
>
> http://conversations.im/omemo/
>
> -- 
> Kim "Zash" Alvefur
>
> _______________________________________________
> xmpp mailing list
> xmpp@ietf.org
> https://www.ietf.org/mailman/listinfo/xmpp


From nobody Mon Sep 14 10:47:27 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8A0E1B3E8C; Mon, 14 Sep 2015 10:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 mAkdNswSWHNp; Mon, 14 Sep 2015 10:47:25 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4250C1B3E92; Mon, 14 Sep 2015 10:47:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150914174724.18419.75652.idtracker@ietfa.amsl.com>
Date: Mon, 14 Sep 2015 10:47:24 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/m4EjQMCqel2B3eAe3RJIbghGeLM>
Cc: xmpp@ietf.org
Subject: [xmpp] WG Action: Conclusion of Extensible Messaging and Presence Protocol (xmpp)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Sep 2015 17:47:26 -0000

The Extensible Messaging and Presence Protocol (xmpp) working group in 
the Applications and Real-Time Area has completed its milestones and is 
now concluded. Many thanks to all who have participated, and especially 
to the draft authors.

The mailing list will remain open for related discussion.

