Re: [netmod] [i2rs] I2RS interim 5/27 10:00am - 11:30am EDT (Webex)
On May 27, 2015, at 1:41 AM, Juergen Schoenwaelder j.schoenwael...@jacobs-university.de wrote: On Tue, May 26, 2015 at 05:13:59PM -0400, Susan Hares wrote: The I2RS interim is schedule for Wednesdsay 5/27 10:00am – 11:30am. The interim schedule opens 30 minutes early to allow speakers to check their mike and make sure there slides are ready. There are two topics on the agenda: 1) I2RS Protocol requirements with discussion on the following drafts a. https://datatracker.ietf.org/doc/draft-haas-i2rs-ephemeral-state-reqs/ (WG adoption 5/26 to 6/9/2015) b. http://datatracker.ietf.org/doc/draft-haas-i2rs-netmod-netconf-requirements (WG adoption 5/26 to 6/9/2015) I can't make it to this meeting. My suggestion is to merge the above two I-Ds into one I-D. There is already overlap. I believe I’d prefer to not adopt the netmod-netconf draft. Its goal, as explained during the last netconf WG session that I presented it in, is to simply use it as the placeholder “TODO” list for the actual drafts covering the work. However, there was strong pressure to have adopted WG items to cover the contents. The state draft is another piece of that. I believe this leaves authentication requirements as the only meaningful content. A last draft covering that may perhaps be spun out or not as the WG desires. After that, the netmod-netconf requirements draft can die. It also seems that a. goes quite a bit into solution space, so calling it a requirements document may be a bit of a stretch. (But that said, we need to start talking about solutions since we already have a document full of requirements.) The actual requirements have been stalled since before the NYC interim: We need ephemeral state. The implications of any given solution space are too important to draft requirements in the absence of some understanding of the likely solution. I’m happy to rename the draft something that doesn’t contain the word “requirements” if you have a better suggestion. — Jeff ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
Re: [netmod] [Netconf] 2 week WG LC on draft-ietf-i2rs-pub-sub-requrements-02 (5/26 to 6/9)
We know of no IPR related to draft-ietf-i2rs-pub-sub-requirements. Eric From: Netconf [mailto:netconf-boun...@ietf.org] On Behalf Of Susan Hares Sent: Tuesday, May 26, 2015 8:21 PM To: i...@ietf.org Cc: netc...@ietf.org; netmod@ietf.org Subject: [Netconf] 2 week WG LC on draft-ietf-i2rs-pub-sub-requrements-02 (5/26 to 6/9) This begins a 2 week WG LC on draft-ietf-i2rs-pub-sub-requirements-02. http://datatracker.ietf.org/doc/draft-ietf-i2rs-pub-sub-requirements/ I2RS Status: WG LC (5/26 to 6/9) Eric, Alexander, Gonzalez - please state whether you know of any IPR related to the draft. This document is a companion to three other documents for I2RS requirements which have WG calls: 1) This begins a 2 week adoption call for draft-haas-i2rs-ephemeral-state-req: https://datatracker.ietf.org/doc/draft-haas-i2rs-ephemeral-state-reqs/ This document covers requests to the netmod and netconf Working Groups for functionality to support the ephemeral state requirements to implement the I2RS architecture. Status: WG adoption call (5/26 to 6/9) 2) draft-haas-i2rs-netmod-netconf-requirements-01http://datatracker.ietf.org/doc/draft-haas-i2rs-netmod-netconf-requirements/ http://datatracker.ietf.org/doc/draft-haas-i2rs-netmod-netconf-requirements/ [This draft is an early set of requirements from which the ephemeral state and identity, secondary-identity and priority were pulled into draft-haas-i2rs-ephemeral-state-reqs. The notification-subscription were pulled into the draft-ietf-i2rs-pub-sub-requirments. The traceability had been separated before draft-haas-i2rs-nemod-netconf-requirements was published. This draft remains the only source for mutual authentication requirements (section 2.2), transaction requirements, and the history of the discussion. This draft is being requested to be adopted as a general roadmap for the I2RS WG. In the future, the I2RS WG will accept more detailed specification on the mutual authentication or the transaction protocol. I2RS Status: WG Adoption (5/26 to 6/9) 3) draft-ietf-i2rs-traceability-02http://datatracker.ietf.org/doc/draft-ietf-i2rs-traceability/ http://datatracker.ietf.org/doc/draft-ietf-i2rs-traceability/ (5/26 to 6/9) This thread is to discuss the draft-i2rs-pub-sub-requirements-02 and forwarding to the netmod/netconf and IESG as requirement for I2RS. Sue Hares PS - Yes - I know an IPR call on a requirements draft may seem silly, but it is required. ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
Re: [netmod] scheduling interim meetings
There has only been one response so far. Please respond by tomorrow if interested in having time during an interim meeting. Thanks, Kent On 5/22/15, 5:39 PM, Kent Watsen kwat...@juniper.net wrote: Following up on https://www.ietf.org/mail-archive/web/netmod/current/msg12549.html, and also to help other drafts progress, we'd like to schedule 3-4 one-hour virtual interim meetings before the meeting in Prague. The first meeting is already set in terms of time and agenda (see below), but the other slots remain open for signups. To accommodate IETF's 2-week announcement requirement, please send your request for time before next Thursday (5/28). Tentative schedule: Fri 6/12 11:30-12:30 EST: modeling operational state (draft-openconfig-netmod-opstate) Thu 6/18 10:00-11:00 EST: TBD Thu 6/25 10:00-11:00 EST: TBD Thu 7/02 10:00-11:00 EST: TBD Please send your request for time to netmod-cha...@tools.ietf.org. Thanks, NETMOD co-chairs ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
