Subject: Re: [Netconf] [FOWARDING] Last Call: <draft-mm-netconf-time-capability-05.txt> (Time Capability in NETCONF) to Experimental RFC

From: Benoit Claise <[email-masked]>
Date: Wed, 1 Jul 2015 16:14:14 +0200

Dear all,

Some background:
Tal asked multiple times the NETCONF WG to provide feedback on his 
draft. Almost none surfaced.
I was not inclined to AD sponsor it. Based on the lack of interest, 
there would be little reason for me to support this draft. Then I 
mentioned ISE.
I have to admit that I didn't pay attention to the IANA section, which 
requests IANA to assign a codepoint in the NETCONF URNs registry. The 
IANA entry for that registry is:
    Network Configuration Protocol (NETCONF) Capability URNs
      Capability URNs     RFC 6241
                         IETF Standards Action

As Nevil Bronwlee (ISE) mentioned: The IESG is the Registrant Contact 
for this registry, which means that this should be published as in 
Individual - i.e. sponsored by an Area Director - RFC.

At that point, I mentioned that I had to re-read the draft. In the 
meantime, Joel agreed to AD sponsor the draft.

So what do we do now?

Regards, Benoit
> I believe that you should make your (Juergen's, Andy's) concerns known to the IETF mail list. This being an AD-sponsored I-D that seems to be the place to comment.
>
> Regards,
>
> Dan
>
>
>> -----Original Message-----
>> From: Netconf [mailto:[email-masked]] On Behalf Of Juergen
>> Schoenwaelder
>> Sent: Monday, June 29, 2015 8:55 PM
>> To: Andy Bierman
>> Cc: Netconf
>> Subject: Re: [Netconf] [FOWARDING] Last Call: <draft-mm-netconf-time-
>> capability-05.txt> (Time Capability in NETCONF) to Experimental RFC
>>
>> Technically, I believe the solution is not really desirable. Figure 4 says you
>> send an RPC and then wait potentially days or weeks for a matching RPC
>> reply and in between you get notifications (which travel over a very different
>> communication channel). But yeah, let people experiment with this if they
>> want to.
>>
>> What I do not get is why this idea requires to get an entry in the capabilities
>> registry and thus is AD sponsored. I do not think that NETCONF requires that
>> experimental capabilities need to be registered with IANA.
>>
>> /js
>>
>> On Mon, Jun 29, 2015 at 10:27:03AM -0700, Andy Bierman wrote:
>>> Hi,
>>>
>>>
>>> Is this an AD-sponsored draft?
>>>
>>> This draft was "interesting" but not enough to be prioritized ahead of
>>> other work being done in the NETCONF WG.
>>>
>>> The draft mixes server measurement of RPC execution time with a "cron"
>>> function.  The rationale for this grab-bag of time-related
>>> functionality is not entirely clear.
>>>
>>> This work does not have any consensus within the NETCONF WG.
>>> It does seem a little surprising that it is being published without
>>> even asking the NETCONF WG for comments.
>>>
>>> I don't have any problem with Experimental RFCs as long as it is clear
>>> this is not a product of the NETCONF WG.
>>>
>>>
>>>
>>> Andy
>>>
>>>
>>>
>>> On Mon, Jun 29, 2015 at 8:07 AM, Juergen Schoenwaelder <
>>> [email-masked]> wrote:
>>>
>>>> Hi,
>>>>
>>>> just to make sure everybody here has seen this.
>>>>
>>>> /js
>>>>
>>>> --
>>>> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>>>> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
>>>> Fax:   +49 421 200 3103
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.jacobs-
>> 2Duniversity.de_&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31O
>> cNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=Q87IdLt8nKswJo-
>> EKyD24gL4IKoQu5XOXa5aeKohufY&s=YOeonUh8hkmY4VdCwSpkZk593aUNn
>> haxHAeGUDKyUV0&e= >
>>>>
>>>> ---------- Forwarded message ----------
>>>> From: The IESG <[email-masked]>
>>>> To: IETF-Announce <[email-masked]>
>>>> Cc:
>>>> Date: Mon, 29 Jun 2015 07:58:22 -0700
>>>> Subject: Last Call: <draft-mm-netconf-time-capability-05.txt> (Time
>>>> Capability in NETCONF) to Experimental RFC
>>>>
>>>> The IESG has received a request from an individual submitter to
>>>> consider the following document:
>>>> - 'Time Capability in NETCONF'
>>>>    <draft-mm-netconf-time-capability-05.txt> as Experimental RFC
>>>>
>>>> The IESG plans to make a decision in the next few weeks, and
>>>> solicits final comments on this action. Please send substantive
>>>> comments to the [email-masked] mailing lists by 2015-07-29.
>>>> Exceptionally, comments may be sent to [email-masked] instead. In
>>>> either case, please retain the beginning of the Subject line to allow
>> automated sorting.
>>>> Abstract
>>>>
>>>>
>>>>     This document defines a capability-based extension to the Network
>>>>     Configuration Protocol (NETCONF) that allows time-triggered
>>>>     configuration and management operations. This extension allows
>>>>     NETCONF clients to invoke configuration updates according to
>>>>     scheduled times, and allows NETCONF servers to attach timestamps to
>>>>     the data they send to NETCONF clients.
>>>>
>>>>
>>>> The Network Configuration Protocol (NETCONF) Capability URNs
>>>> registry requires a standards action in order to populate the
>>>> registry. This document was taken out of the ISE stream and brought
>>>> forward as an AD sponsored individual-submission to address this
>>>> consideration.
>>>>
>>>>
>>>> The file can be obtained via
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.iet
>>>> f.org_doc_draft-2Dmm-2Dnetconf-2Dtime-
>> 2Dcapability_&d=AwICAg&c=BFpWQ
>> w8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&
>> m=Q8
>>>> 7IdLt8nKswJo-
>> EKyD24gL4IKoQu5XOXa5aeKohufY&s=xXpTwBGoKzQwCICBcvA-IOLm
>>>> fEd8emgt7EGVyAmzJ2s&e=
>>>>
>>>> IESG discussion can be tracked via
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.iet
>>>> f.org_doc_draft-2Dmm-2Dnetconf-2Dtime-
>> 2Dcapability_ballot_&d=AwICAg&
>> c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrp
>> hpBs
>>>> FA&m=Q87IdLt8nKswJo-
>> EKyD24gL4IKoQu5XOXa5aeKohufY&s=5XcQnG3n5R4D-qUiv
>>>> 2DD-r67mQdOk39an9qW5Eb86Z8&e=
>>>>
>>>>
>>>> No IPR declarations have been submitted directly on this I-D.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Netconf mailing list
>>>> [email-masked]
>>>> https://urldefense.proofpoint.com/v2/url?u=https-
>> 3A__www.ietf.org_ma
>> ilman_listinfo_netconf&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGx
>> R31
>>>> OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=Q87IdLt8nKswJo-
>> EKyD24gL4IKoQu5X
>>>> OXa5aeKohufY&s=1RLb-
>> m80wIXpLUu28LFybr6Sy0KTrI_zhriR7mQWflo&e=
>>>>
>> --
>> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
>> Fax:   +49 421 200 3103
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.jacobs-
>> 2Duniversity.de_&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31O
>> cNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=Q87IdLt8nKswJo-
>> EKyD24gL4IKoQu5XOXa5aeKohufY&s=YOeonUh8hkmY4VdCwSpkZk593aUNn
>> haxHAeGUDKyUV0&e= >
>>
>> _______________________________________________
>> Netconf mailing list
>> [email-masked]
>> https://urldefense.proofpoint.com/v2/url?u=https-
>> 3A__www.ietf.org_mailman_listinfo_netconf&d=AwICAg&c=BFpWQw8bsu
>> Kpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=Q87I
>> dLt8nKswJo-EKyD24gL4IKoQu5XOXa5aeKohufY&s=1RLb-
>> m80wIXpLUu28LFybr6Sy0KTrI_zhriR7mQWflo&e=
> _______________________________________________
> Netconf mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/netconf
> .
>