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

["Nancy Cam-Winget (ncamwing)" <[e-mail]>]

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"
<[e-mail] on behalf of [e-mail]> 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.

>
>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.

>
>[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…

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

>
>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.

>
>[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:[e-mail]] On Behalf Of Nancy Cam-Winget
>(ncamwing)
>Sent: Wednesday, April 27, 2016 1:28 AM
>To: [e-mail]
>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
>[e-mail]
>https://www.ietf.org/mailman/listinfo/mile