Re: [mile] Please provide comments to draft-ietf-mile-xmpp-grid

"Syam Appala (syam1)" <syam1@cisco.com> Thu, 13 October 2016 01:31 UTC

Return-Path: <syam1@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44FDB129679 for <mile@ietfa.amsl.com>; Wed, 12 Oct 2016 18:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.517
X-Spam-Level:
X-Spam-Status: No, score=-17.517 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 RJg_EbhZWVot for <mile@ietfa.amsl.com>; Wed, 12 Oct 2016 18:31:00 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03E5C1295C4 for <mile@ietf.org>; Wed, 12 Oct 2016 18:30:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6882; q=dns/txt; s=iport; t=1476322260; x=1477531860; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=/84omtpSt7l9nMiwTBWlq5y8TMTnT8Fd20aHugu89Bk=; b=F0Phgd2Sxx7Zsq7mhgDruiXvLqiyswrZpWiHVAbISip/9kpsbvREsotE 60ktVgxHl0KoXk/0pS7AJtjjWwbtUyu/o8sAo/cSX2JBtVPCDcZcE3qwA 3phLimrodMnGp1AtRsxtO8RzqrSvbLuv5NNuHiaQa62Gg4XlsGhI+RmqQ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AUAQD74v5X/5xdJa1cGQEBAQEBAQEBAQEBBwEBAQEBgzwBAQEBAR1XfAeNLZcElDSCChwLhXoCGoFcOBQBAgEBAQEBAQFeJ4RhAQEBBAEBASAROhsCAQgRBAEBAQICCAkBARADAgICJQsUAQgIAgQBEohQDrYyjQYBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYEHhzOCWIQxFj8JAYI7LIIvBYEhAZheAgGGJoV4g16BboRngzeFaYx5g34BHjaDRRyBU3KGNw0XgQmBAAEBAQ
X-IronPort-AV: E=Sophos;i="5.31,338,1473120000"; d="scan'208";a="159310127"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Oct 2016 01:30:59 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u9D1UwOM017638 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 13 Oct 2016 01:30:58 GMT
Received: from xch-rcd-010.cisco.com (173.37.102.20) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 12 Oct 2016 20:30:57 -0500
Received: from xch-rcd-010.cisco.com ([173.37.102.20]) by XCH-RCD-010.cisco.com ([173.37.102.20]) with mapi id 15.00.1210.000; Wed, 12 Oct 2016 20:30:57 -0500
From: "Syam Appala (syam1)" <syam1@cisco.com>
To: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>, Takeshi Takahashi <takeshi_takahashi@nict.go.jp>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: [mile] Please provide comments to draft-ietf-mile-xmpp-grid
Thread-Index: AQHRn9iNpZhh1iQrsUKo2hnaYXPTV6CmgasA
Date: Thu, 13 Oct 2016 01:30:57 +0000
Message-ID: <FE815499-84B5-42E3-9E44-357265145E5F@cisco.com>
References: <D344E509.169F8C%ncamwing@cisco.com> <008c01d1b03e$9bb13d40$d313b7c0$@nict.go.jp> <D4219D55.18F896%ncamwing@cisco.com>
In-Reply-To: <D4219D55.18F896%ncamwing@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.160109
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.155.145.106]
Content-Type: text/plain; charset="utf-8"
Content-ID: <781004285F8B594585CC2B8BC0490606@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/TtWHATsxJyorVU0iyqFVAW_SD-c>
Subject: Re: [mile] Please provide comments to draft-ietf-mile-xmpp-grid
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Oct 2016 01:31:02 -0000

Thanks Nancy. Please see inline:




On 10/10/16, 7:45 PM, "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com> wrote:

>Hi Takeshi,
>
>My apologies for such a long delay….and thank you so much for the comments.
>
>Some answers below (I am also including Syam to further elaborate as
>needed):
>
>On 5/17/16, 6:18 AM, "mile on behalf of Takeshi Takahashi"
><mile-bounces@ietf.org on behalf of takeshi_takahashi@nict.go.jp> wrote:
>
>>Hello Nancy,
>>
>>I have read the draft and have got a couple of questions and comments on
>>the
>>XMPP-grid draft.
>>I might have misunderstood something, but I would appreciate your answers
>>to
>>the following questions.
>>
>>[Section 1.3 Overview of XMPP-grid]
>>
>>a. Regarding "Grid Connect", how can we know the location of the
>>Controller?
>>Does either XMPP or XMPP-grid provide such scheme? Or, are we supposed to
>>know the Controller in advance by using external means?
>[NCW] You can do a discovery to find the Controller in a couple of ways,
>the simplest one being a DNS query
>As it is expected that the controller would be implemented as a DNS
>service.
[SYAM] The clients connect to an XMPP server (that requires a DNS resolution for network reachability). The client requests such as connect, subscribe, publish etc are addressed to the Grid Controller. The Grid Controller FQDN can be resolved via DNS or it is left to XMPP server implementation to route to a pre-determined Jabber ID or FQDN.
>
>>
>>b. Regarding "publish topic", does XMPP-grid allow us to publish a data
>>(that is a part of a Topic)?
>>If I understood correctly, Topic is a series of (a group of) security
>>items,
>>and "publish topic" operation is prepared for publishing topic, not an
>>item.
>[NCW] Yes, a “topic” is the XMPP nomenclature used to define a schema that
>contains the content to be published.
>So, one can “filter” parts of the data in the topic as well….but yes, a
>topic consists of a set of information items.
[SYAM] I agree with Nancy.
>
>>
>>[Section 2.1 XMPP Overview]
>>
>>a. Regarding figure 3, if the XMPP server does not equip with the Grid
>>controller, what type of error messages can publisher receive?
>[NCW] A publisher could receive error messages against its operations and
>transactions that go through the controller.
>For instance, the session establishment codes (looking at SASL codes,
>section 6.5 of RFC 6120)
>Syam can further elaborate of other error codes as well…
[SYAM] SASL error codes are reported back to the client for failures such as authentication or authorization failures, account disabled or does not exist etc. RFC 6120 section 6.5 documents these error codes.

>
>>
>>[Section 2.6 XMPP-Grid Protocol Details]
>>
>>a. In the first bullet "Register the Node to XMPP-Grid", the sentence says
>>'"Node2@domain.com/mac" sends the following ...', but the example XML
>>below
>>the sentence says 'from=Node2@domain.com/syam-mac"...'. One of the two
>>might
>>be a typo.
>[NCW] Thank you for catching the typo!  We will make them consistent…
>[SYAM] We will fix the typo. Thank you.

>>
>>b. In the example XMLs, I prefer to see <login/> rather than
>><login></login>. Likewise, <register/> and <logout/> could be used.
>[NCW] That is fine…we can make the adjustment.
[SYAM] Sure. We will make the adjustment.
>
>>
>>[abstract]
>>
>>a. Are you going to produce an RFC that defines XMPP-grid somewhere else?
>>(If this document defines XMPP-grid, it is fine to me to leave Section 3
>>concise as it is.)
>[NCW] I currently do not intend to define it elsewhere as once should
>suffice!
>There may be extensions or other documents that can show how XMPP-grid can
>be used for other information that is outside the scope of MILE, but the
>core as defined in this document should only be published/described once.
>
>>
>>[Section 1 Introduction]
>>
>>a. The sentences sound like that the XMPP-grid can be usable only for
>>security-related information; am I correct that the XMPP-grid can be used
>>for arbitrary XML information exchange?
>[NCW] Yes, it is meant for any information as XMPP is widely used and
>exchanges other information types.
>However, the original “target” audience for XMPP-grid was to show how it
>can be used for security based information too.
>Would you like us to make that clarification?
>
>
>>
>>Thank you,
>>Take
>>
>>
>>
>>From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Nancy Cam-Winget
>>(ncamwing)
>>Sent: Wednesday, April 27, 2016 1:28 AM
>>To: mile@ietf.org
>>Subject: [mile] Please provide comments to draft-ietf-mile-xmpp-grid
>>
>>Colleagues,
>>
>>I’ve posted the draft
>>in https://datatracker.ietf.org/doc/draft-ietf-mile-xmpp-grid/  so that we
>>can get comments and continue to move this forward.
>>
>>Thanks, nancy
>>
>>_______________________________________________
>>mile mailing list
>>mile@ietf.org
>>https://www.ietf.org/mailman/listinfo/mile
>