Hi Diego, On Sun, Dec 09, 2012 at 10:38:37PM +0000, Diego R. Lopez wrote: > Hi, > > On 19 Nov 2012, at 18:01 , Sebastian Kiesel wrote: > > > I propose to add such a discussion to the Deployment Considerations > > document, if we want to have one at all. The discovery document should > > contain a technical specification as short and as precise as possible. > > An appendix is clearly out of the techhnical specification and discusses > an additional aspect. In this case an alternative protocol applicable to > other potential use cases...
For now I still would say that the discussion of a specific use case without protocol specification (i.e., gap analysis for existing protocols, things to consider, special parameters to use, etc.) should go into the deployment considerations document. We created this document exactly for that kind of information. The specification of a different solution approach should go into a separate draft - at least for the initial version, maybe it makes sense to merge it into a common framework later. Marketing blah blah about the alleged advantages of an unspecified protocol should go nowhere, we just don't need that. A single sentence that there are other solution approaches being considered, with references to other drafts, would nicely fit into the introduction. But maybe I will change my mind if we have a clearer idea what you would like to see in the appendix. So please propose text. Thanks Sebastian _______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
