[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: netconf-notification-transport-01
And just to emphasize what Sharon says about the bis of the transport
mapping documents, the following is included in the introduction:
"Editor's Note: Inclusion of Notification transport mappings
into bis versions of the SSH, SOAP and HTTP transport mappings RFCs
should be considered instead of publishing a Notification-specific
transport mapping document."
Hector
-----Original Message-----
From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On
Behalf Of Sharon Chisholm
Sent: Friday, March 09, 2007 10:32 AM
To: netconf@ops.ietf.org
Subject: RE: netconf-notification-transport-01
Hi
This document is a holding place for the issue of transport mapping for
notifications. My hope is that any gaps we identify in the existing
transport mappings will result in a bis of those documents to properly
cover notifications. Hector and I want to make sure the issue didn't get
lost - hence the draft.
If it does continue in its current form, I don't think throwing the word
optional in is helpful. Either it is defining the mapping for the
various transports or it isn't.
I sent some private emails to ping the authors of the various transport
mappings on the topic. We received some good feedback so far on SOAP
(what we have in the document isn't what is needed) and a promise for a
review on BEEP.
Sharon
-----Original Message-----
From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On
Behalf Of David B Harrington
Sent: Friday, March 09, 2007 10:23 AM
To: 'Andy Bierman'; 'Ma Yuzhi'
Cc: netconf@ops.ietf.org
Subject: netconf-notification-transport-01
Should the abstract be changed from "This document defines the transport
mappings" to "This document defines optional transport mappings"?
> -----Original Message-----
> From: owner-netconf@ops.ietf.org
> [mailto:owner-netconf@ops.ietf.org] On Behalf Of Andy Bierman
>
> Please note that this is not a WG document.
> We have an open issue wrt/ the transport mappings.
> Only SSH is supported for notifications at this time.
>
[...]
> The document [] does not contain any normative text relevant to the
> title of the document. It contains non-normative examples mostly
> taken from other documents.
[...]
>
> Andy
>
> >
> >> -----Original Message-----
> >> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> >> Sent: Thursday, March 01, 2007 7:50 AM
> >> To: i-d-announce@ietf.org
> >> Subject: I-D
> >> ACTION:draft-trevino-netconf-notification-transport-01.txt
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> >> directories.
> >>
> >>
> >> Title : NETCONF Notification Transport Mappings
> >> Author(s) : S. Chisholm, H. Trevino
> >> Filename :
> >> draft-trevino-netconf-notification-transport-01.txt
> >> Pages : 14
> >> Date : 2007-2-28
> >>
> >> This document defines the transport mappings for NETCONF event
> >> notifications. This is an optional capability built on
> top of the
> >> base NETCONF protocol.
> >>
> >> A URL for this Internet-Draft is:
> >> http://www.ietf.org/internet-drafts/draft-trevino-netconf-noti
> >> fication-transport-01.txt
> >>
> >> To remove yourself from the I-D Announcement list, send a
> message to
> >> i-d-announce-request@ietf.org with the word unsubscribe in the body
> >> of the message.
> >> You can also visit
> >> https://www1.ietf.org/mailman/listinfo/I-D-announce
> >> to change your subscription settings.
> >>
> >> Internet-Drafts are also available by anonymous FTP. Login
> with the
> >> username "anonymous" and a password of your e-mail address. After
> >> logging in, type "cd internet-drafts" and then "get
> >> draft-trevino-netconf-notification-transport-01.txt".
> >>
> >> A list of Internet-Drafts directories can be found in
> >> http://www.ietf.org/shadow.html or
> >> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>
> >> Internet-Drafts can also be obtained by e-mail.
> >>
> >> Send a message to:
> >> mailserv@ietf.org.
> >> In the body type:
> >> "FILE
> >>
>
/internet-drafts/draft-trevino-netconf-notification-transport-01.txt".
> >>
> >> NOTE: The mail server at ietf.org can return the document in
> >> MIME-encoded form by using the "mpack" utility. To use this
> >> feature, insert the command "ENCODING mime" before the "FILE"
> >> command. To decode the response(s), you will need "munpack"
or
> >> a MIME-compliant mail reader. Different MIME-compliant mail
> >> readers
> >> exhibit different behavior, especially when dealing with
> >> "multipart" MIME messages (i.e. documents which have been
split
> >> up into multiple messages), so check your local documentation
on
> >> how to manipulate these messages.
> >>
> >> Below is the data which will enable a MIME compliant mail reader
> >> implementation to automatically retrieve the ASCII version of the
> >> Internet-Draft.
> >>
> >
> >
> >
> > --
> > 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/>
>
--
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/>
--
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/>