Re: [lmap] Mirja Kühlewind's Discuss on draft-ietf-lmap-yang-11: (with DISCUSS and COMMENT)

Hi Mirja,

Per our telechat discussion, could you provide clarification about what further information you need to be able to clear?

Thanks,
Alissa

> On Mar 14, 2017, at 5:06 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> 
> On Fri, Mar 10, 2017 at 08:47:09AM -0800, Mirja Kühlewind wrote:
>> 
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>> 
>> This draft does not specify a bootstrapping process (see RFC 7594 5.1. 
>> Bootstrapping Process) and says:
>> "Pre-Configuration Information: This is not modeled explicitly since
>> bootstrapping information is outside the scope of this data model."
>> So when and where and how will this be specified?
> 
> There is work ongoing in NETCONF to provide different pieces for
> bootstrapping.
> 
> - draft-ietf-netconf-keystore
> 
>  a model for managing keys
> 
> - draft-ietf-netconf-netconf-client-server
> 
>  a model for managing NETCONF client and server config
> 
> - draft-ietf-netconf-restconf-client-server
> 
>  a model for managing RESTCONF client and server config
> 
> - draft-ietf-netconf-ssh-client-server
> 
>  a model providing NETCONF over SSH config details
> 
> - draft-ietf-netconf-tls-client-server
> 
>  a model providing NETCONF over TLS config details
> 
> - draft-ietf-netconf-zerotouch
> 
>  a mechanism for loading bootstrapping information
> 
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>> 
>> Also it is not clear when and how to perform configuration actions. To be
>> a fully function protocol more guidance is needed. Not sure if that is
>> even the intention of this document but I don't see any other documents
>> that serves this purpose in the lmap queue. (And the milesstones are not
>> up to date and don't indicate with document maps to which milestone.)
> 
> When and how is up to the controller design. The fully functioning
> protocol falls out of the YANG data model - once you have YANG data
> model, you are ready to go. That said, there is a currently expired
> WG document providing more details.
> 
> https://tools.ietf.org/html/draft-ietf-lmap-restconf-03
> 
> The idea here was just provide an explanation how the LMAP data model
> works together with RESTCONF.
> 
> /js
> 
> -- 
> 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/>
> 
> _______________________________________________
> lmap mailing list
> lmap@ietf.org
> https://www.ietf.org/mailman/listinfo/lmap