headers
Maureen.Stillman | 2 Aug 2006 14:43
Picon

Draft Minutes from IETF #66

Any comments?
Draft Minutes from IETF #66
Randy Stewart discussed the comments received on the architecture draft draft-ietf-rserpool-architecture-13.txt. It was suggested that the draft was hard to read because it was very general and designed to allow a wide range of protocol instantiations. The group decided that it would be better to abandon a document that has been the subject of confusion and instead write a short overview document of the protocol that exists today. We received AD approval of this idea.

Michael Tuexen discussed Rserpool implementations and performed a demo of Rserpool at the meeting. ASAP has already been interop tested over a year ago.  There will be an SCTP interop in Vancouver in late July and Rserpool will also be interop tested at that time.

Michael Tuexen discussed the rserpool socket API. This document needs more work as there is divergence between the code and the text. We need to harmonize the different approaches and update the document.

The next steps for Rserpool is to finish the work on the protocol documents. The AD opinion is that a lot of work needs to be done. The ADs shared their comments on the protocol documents. They would like the focus of the group to shift to the core protocol documents and get those finished. The charter needs to be redone to emphasize this focus. A list of documents was proposed for the focus of the work with people identified to perform the work. The chairs will work on a revised charter with new milestones based on these changes. The list of core documents was identified as follows:

- overview: new document to replace the architecture document
Draft-ietf-rserpool-asap-13.txt
Draft-ietf-rserpool-enrp-13.txt
Draft-ietf-rserpool-common-param-10.txt
Draft-ietf-rserpool-threats-05.txt
All other documents are not considered to be core documents. These can be worked on later.

-- Maureen
Maureen Stillman
Nokia Enterprise Solutions
Acting Director SMC Systems Architecture 

_______________________________________________
rserpool mailing list
rserpool <at> ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool
Permalink | Reply | 0 comments |
headers
Internet-Drafts | 30 Aug 2006 21:50
Picon
Favicon

I-D ACTION:draft-ietf-rserpool-mib-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Reliable Server Pooling Working Group of the IETF.

	Title		: Reliable Server Pooling: Management Information Base using SMIv2
	Author(s)	: J. Mulik, et al.
	Filename	: draft-ietf-rserpool-mib-03.txt
	Pages		: 34
	Date		: 2006-8-30
	
RSerPool [2] is a framework to provide reliable server pooling.  This
document defines a SMIv2 compliant Management Information Base (MIB)
providing access to managed objects in an RSerPool implementation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-mib-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> 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-ietf-rserpool-mib-03.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 <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rserpool-mib-03.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.
Attachment: message/external-body, 136 bytes
Attachment (draft-ietf-rserpool-mib-03.txt): message/external-body, 69 bytes
_______________________________________________
rserpool mailing list
rserpool <at> ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool
Permalink | Reply | 0 comments |

Gmane