On 11/14/2011 07:34 PM, Richard Alimi wrote:
draft-gu-alto-redistribution was originally intended to provide
information about how one might implement redistribution, but
(intentionally) we did not provide actual protocol specifications
due to the variety of P2P protocols in the wild.  The dependency was
non-normative.  If it seems "weird" to link to that from a
standards-track document (i.e. even if we split Section 8 into a
separate document) then that could be removed - it was only intended
to give readers a pointer for how they might get started.

Rich: Thanks for the clarification.  More inline.

If on the other hand, it makes sense to revive
draft-gu-alto-redistribution and add it as a WG item we could do
that too - back when we were presenting it it seemed like it didn't
gain much traction, but if thinks have changed, then great :)

Pedantically speaking, draft-gu-alto-redistribution was never a
WG item, it was an individual document.  Thus, it can continue
in the same vein until such time that the WG decides how to handle
information redistribution.

Your original proposal of splitting out Section 8 (Redistribution) from
draft-ietf-alto-protocol as an extension, and thus make it normatively
dependent on the outcome of JOSE WG is still sound (again, as an
individual contributor).  It has my "+1" vote.

Assuming that the WG agrees to this, then draft-gu-alto-redistribution
could very well serve as the vessel for moving the redistribution
work ahead.  At some point, the charter will be expanded to include
extensions (the chairs will have to get their act together on this
one :-) ).

I am aware of at least two possible threads of work in progress
(redistribution and multi-cost) that could qualify as extensions to the
base protocol.

Thanks,

- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / [email protected]
Web:   http://ect.bell-labs.com/who/vkg/
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

Reply via email to