Re: [Curdle] Alissa Cooper's Discuss on draft-ietf-curdle-gss-keyex-sha2-09: (with DISCUSS)

[Adam Roach <[e-mail]>]

On 6/24/19 3:19 PM, Benjamin Kaduk wrote:
> On Mon, Jun 24, 2019 at 01:18:08PM -0700, Alissa Cooper via Datatracker wrote:
>> Alissa Cooper has entered the following ballot position for
>> draft-ietf-curdle-gss-keyex-sha2-09: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-curdle-gss-keyex-sha2/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> "The IESG is considered to be the owner of all these key exchange
>>     methods; this does NOT imply that the IESG is considered to be the
>>     owner of the underlying GSS-API mechanism."
>>
>> I don't understand this text. What does it mean for the IESG to be the owner of a method?
> The IESG has change control for the SSH key exchange method; the IESG does
> not necessarily have change control for the underlying GSS-API mechanism.


I'm confused. Your statement would imply that one of the following is false:

 1. GSS-API is authoritatively defined by RFC 2743
 2. RFC 2743 is an IETF-stream document
 3. The IESG is responsible for change control of IETF-stream documents

Which of these have I misunderstood?

/a