Re: I-D ACTION:draft-ietf-nfsv4-rpc-ipv6-00.txt

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: Andrew Steingruebl (steingra@pprd.abbott.com)
Date: 03/01/01-09:27:00 AM Z 

Message-Id: <200103011527.f21FR1m09906@clio.pprd.abbott.com>
Subject: Re: I-D ACTION:draft-ietf-nfsv4-rpc-ipv6-00.txt 
Date: Thu, 01 Mar 2001 09:27:00 -0600
From: Andrew Steingruebl <steingra@pprd.abbott.com>


Internet-Drafts@ietf.org said:

>
>	Title		: IPv6 extension to RPC
>	Author(s)	: S. Majee, P. Park
>	Filename	: draft-ietf-nfsv4-rpc-ipv6-00.txt
>	Pages		: 13
>	Date		: 28-Feb-01
>	
>ONC+ RPC is a popular choice for developing various distributed
>software and services. NFS (network File system) is one example of
>that. This document describes the the various extensions and choices
>made in order to support IPv6 in ONC RPC. The goal is to keep the
>application porting effort to minimal or none depending on the
>complexity of the application. It describes the changes necessary
>for TI-RPC(Transport independent RPC) and TS-RPC(Socket based RPC).

Why is this part of the NFSv4 working group's charter?  I realize its a 
necessary underpinning, just curious why its here, and not somewhere else?

Thanks.


-- 
Andy Steingruebl              | e-mail: steingra@pprd.abbott.com          
Unix Systems Admin/Programmer | phone:  (847) 935-4728                    
Unix/Network Security         | fax:    (847) 935-0142                    
Abbott Laboratories, PPDR&D   | post:   100 Abbott Park Road, D472 - AP9A
                              |         Abbott Park, IL 60064-6115

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-01:48:37 AM Z CST