[i2rs] Gaps analysis (draft-zhang-gap-analysis-01) revisions - MIDCOM, SACM, PCP, and AAA

Dan: This is response to the email: http://www.ietf.org/mail-archive/web/i2nsf/current/msg00233.html I think that this group needs to dig a bit deeper to compare the MIDCOM architecture, protocol requirements, and protocol primitives to determine how vNSF based on the ETSI document.

Re: [i2rs] [I2nsf] revised charter for I2NSF

Tom: I'm catching up with emails after a few days of I2RS interims and design teams - so I apologize if this comes out of sequence. LIME has a solid basis in looking at generic OAM modules. I would not like to see the generic OAM work of LIME defocused by defining the vNSF functions. The two

Re: [i2rs] Does I2RS charter include both the interface to Network Controller and the interface to devices (i.e. routers)?

Linda, I understand now your question (based on reading I2NSF emails). I2RS has two elements, agent and client and I2RS agent is sitting on the network device and exposes north bound interface to the I2RS client. How I2RS agent communicates to the device is not specified. This is up to the