Subject: Re: [i2rs] I-D Action: draft-ietf-i2rs-ephemeral-state-06.txt

From: Susan Hares <[email-masked]>
Date: Mon, 09 May 2016 17:43:10 -0400

Juergen:We could move the solutions into the protocol strawman.  As discussed in ietf 93 and ietf 94 the solutions are simply examples to provide hints on the i2rs requirements.  Just to be clear, at minimum you would suggest the yang, NETCONF and RESTCONF sections to protocol strawman.  
The issue regarding the protocols has one issue of allowing an insecure protocol (to be defined elsewhere) to be utilized.  Is this what you are objecting to?  The other issue is the specification of ssh or TLS for NETCONF.  
The first issue tries to create a narrow scope for any data in a datamodel sent over insecure transport.  
On the second issue, the text was not trying to tie it to a data model but to allow clients to know what options were to communicate with agents.  
Thank you for your quick response.
Sue

Sent via the Samsung Galaxy Note5, an AT&T 4G LTE smartphone-------- Original message --------From: Juergen Schoenwaelder <[email-masked]> Date: 5/6/2016  3:34 AM  (GMT-05:00) To: [email-masked] Subject: Re: [i2rs] I-D Action: draft-ietf-i2rs-ephemeral-state-06.txt 
I have a hard time with this document. Section 3 is labelled
requirements but it actually details solution and I disagree with a
significant number of the solution elements. To name an example:
Indicating in a data model with which protocols it should be used and
which secure transports underneath the protocol should be used. I do
not want to discuss all the details here since obviously this is not a
requirements document.

/js

On Thu, May 05, 2016 at 10:59:01PM -0700, [email-masked] wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Interface to the Routing System of the IETF.
> 
>         Title           : I2RS Ephemeral State Requirements
>         Authors         : Jeff Haas
>                           Susan Hares
> 	Filename        : draft-ietf-i2rs-ephemeral-state-06.txt
> 	Pages           : 16
> 	Date            : 2016-05-05
> 
> Abstract:
>    This document covers requests to the netmod and netconf Working
>    Groups for functionality to support the ephemeral state requirements
>    to implement the I2RS architecture.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-i2rs-ephemeral-state/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-i2rs-ephemeral-state-06
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-ephemeral-state-06
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> i2rs mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/i2rs

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

_______________________________________________
i2rs mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/i2rs