Re: Why combine the Java and C# bindings?

[Jeffrey Altman <[e-mail]>]

Nicolas Williams wrote:

> On Tue, Apr 19, 2005 at 11:47:20AM -0500, Nicolas Williams wrote:
> 
>>WG consensus on the matter hasn't been reached.
>>
>>I for one would like to hear more about why or why not C# bindings
>>shouldn't be in the same doc as Java bindings.
>
> My mind is not entirely made up as I'm still missing information, but
> the authors of the existing I-Ds seem willing to pursue separate paths.
> 
> Jeff, do you think we need a consensus call, or is there consensus
> already?

I do not believe that we need an explicit consensus call to determine
which path is taken for publication of this work.

Back in October when the working group was forming there was a weak
consensus that the Java and C# bindings should be merged into one
update to 2853 because it was argued that the quantity of work
necessary to be performed was modest for both.  Java required an
update because there were factual errors that needed to be corrected.
The C# definition was considered to be minor.

In the past two weeks there has been significant discussion regarding
the merits of this decision.   The editors of both the current Java
draft and C# draft are in agreement to go separate ways and I do not
see any requirements that only a single document be produced.

Here is what I would like to see in the coming month:

* I would like to see an updated version of
draft-ietf-kitten-rfc2853bis-00.txt published that contains all of the
text of rfc2853 modified as stated by the aforementioned  draft.

* I would like to see a revised version of
draft-ietf-kitten-gssapi-rfc2853-update-for-csharp-00 which is based on
rfc2853 but is specific to C#

I believe that rfc2853bis can be sent to the IESG in a very short period
of time.  A revised rfc is justified to correct the factual errors in
2853.   This working group will have a large number of changes published
in the coming year and I do not want to wait for the conclusion of this
working group before an updated Java bindings RFC is published.

A third revision to 2853 can be published as we near the end of the
working group to collect all of the Java bindings which are produced for
forthcoming APIs.  In the meantime, supplementary documents such as the
PRF drafts will contain bindings for at least C and Java when they are
submitted to the IESG.

Jeffrey Altman

_______________________________________________
Kitten mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/kitten