Re: netconf relationship to epp

[Greg Weber <gdweber@cisco.com>]

> 
> > The Extensible Provisioning Protocol (<draft-ietf-provreg-epp-09.txt>
> > and associated documents) was just approved as Proposed Standard. Is
> > someone on this list familiar with EPP and can he/she explain to what
> > extend EPP overlaps with netconf charter items and the proposal under
> > consideration by netconf?

I was wondering about this too.  Especially after glancing 
through the EPP extensibility draft 
  http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-ext-03.txt

Excerpted from the Introduction:

   The Extensible Provisioning Protocol (EPP, [2]) was originally
   designed to provide a standard Internet domain name registration
   protocol for use between Internet domain name registrars and domain
   name registries.  However, specific design decisions were made to
   ensure that the protocol could also be used in other provisioning
   environments.  Specifically:

   o  Extensibility has been a design goal from the very beginning. EPP
      is represented in the Extensible Markup Language (XML, [3]), and
      is specified in XML Schema ([4] and [5]) with XML namespaces [6]
      used to identify protocol grammars.

   o  The EPP core protocol specification describes general protocol
      functions, not objects to be managed by the protocol.  Managed
      object definitions, such as the mapping for Internet domain names
      [10] (itself a protocol extension), are loosely coupled to the
      core specification.

   o  A concentrated effort was made to separate required minimum
      protocol functionality from object management operating logic.

   o  Several extension mechanisms were included to allow designers to
      add new features or to customize existing features for different
      operating environments.

   This document describes EPP's extensibility features in detail and
   provides guidelines for their use.  Though written specifically for
   protocol designers considering EPP as the solution to a provisioning
   problem, anyone interested in using XML to represent IETF protocols
   might find these guidelines useful.

Sounds pretty general to me.

Greg

> 
> epp is registrar/registry in the dns and address allocation space.
> not close ot netconf.
> 
> randy
> 
> 
> --
> to unsubscribe send a message to netconf-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/netconf/>
> 


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>