IETF 98 
I2RS meeting on 3/29/2017 at  [13:00-15:00 CDT} 

0) Agenda Bashing [13:00-13:05]

1) Chair's slides [13:05-13:10] 
Charter Information: 
  a) I2RS is for  protocol independent Yang modules 
      from any datastore (config, control plane,or I2rs control plane)  
       
 b) Participate in Charter discussions (I2RS/NETMOD/RESTCONF) 
    Netconf  (Session 1)   Tuesday pm 
    I2RS  (only Session 1) Wed pm 
    Netmod (session 2)     Thursday pm
 
1) Requirements Drafts [13:10-13:20]
   Secure Environment Requirement Update 
    (WG call or Drop)  - [Daniel Migault]
  https://datatracker.ietf.org/doc/draft-ietf-i2rs-security-environment-reqs/
        
2) Protocol issues (New Work) - Where will the work be done? 
  a) Revised Datastore Model [Kent Watsen] [13:20-13:35]   
   https://datatracker.ietf.org/doc/draft-ietf-netmod-revised-datastores/
  
  b) Yang model proposal [Sue Hares] [13:35-13:45]
    https://datatracker.ietf.org/doc/draft-hares-netmod-i2rs-yang/
  
  c) 2 Capabilities to support I2RS in NETCONF and RESTCONF [13:45-13:55] 
   https://datatracker.ietf.org/doc/draft-hares-netconf-i2rs-netconf/ 
   https://datatracker.ietf.org/doc/draft-hares-netconf-i2rs-restconf/ 

  d) Yang Data Models in CBOR in COAP   [13:55-14:00] [TBD] 
    https://datatracker.ietf.org/doc/draft-ietf-core-yang-cbor/
    https://tools.ietf.org/html/rfc7252
   (CBOR does binary encodings of yang models and has open source implementations) 
   [see http://cbor.io/impls.html or  http://libcbor.org
    COAP does a GET, PUT, POST, DELETE functionality like RESTCONF)
   [http://coap.technology/impls.html or   https://sourceforge.net/projects/libcoap/) 

    Warning: Please watch for late breaking changes based on 
        NETCONF and NETMOD discussions on Tuesday.       

   d) Discussion on I2RS Protocol direction: [14:00-14:15] 

    Yang seems to be the direction for a Data Modeling Language.  

    Should I2RS continue working on NETCONF/RESTCONF? 
    Should I2RS work on additions to CBOR encoding in CoaP? 
    Should I2RS work on XML (GET, PUT, POST, DELETE) in google protocol buffers?  
    Should I2RS work on ForCES encoding of Yang? 


 3) Working Group Data Models [14:15 - 15:00] 
   a)  Topology Model Update [Alex Clemm ] [14:15-14:25] 
    https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-network-topo/
    https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l3-topology/
         
    b) FB-RIB Update  [Sue Hares ] [14:25-14:30] 
        https://datatracker.ietf.org/doc/draft-ietf-i2rs-fb-rib-data-model/
        https://datatracker.ietf.org/doc/draft-ietf-i2rs-pkt-eca-data-model/
    
4)  Proposed Data Models [14:30-15:00] 
    a)  2 Data Models for Fabric Service in Data Center [Rong Gu]  [14:30-14:40] 
        YANG Data Model for Fabric Service delivery in Data Center Network
        https://datatracker.ietf.org/doc/draft-zhuang-i2rs-dc-fabric-service-model/
        A YANG Data Model for Fabric Topology in Data Center Network
        https://datatracker.ietf.org/doc/draft-zhuang-i2rs-yang-dc-fabric-network-topology/
     
    b) Open Fabric [Russ White] [14:40-14:50] 
        https://datatracker.ietf.org/doc/draft-white-openfabric/
     
    c) Control-Plane and User-Plane separation BNG Info-Model 
         [Michael Wang] [14:50-15:00] 
     https://datatracker.ietf.org/doc/draft-wcg-i2rs-cu-separation-infor-model/
 
 

JavaScript license information