[AFS3-std] Status of protocol drafts?

[Matt W. Benjamin]

Another consideration might be, what makes this body most productive.  It certainly seems logically possible, and perhaps administratively easier, to make the future draft or an xcb-specific refresh draft responsible to deal with extended callbacks, when the design inputs from RPC refresh are in place.

Matt

----- "Simon Wilkinson" <simon@sxw.org.uk> wrote:

> On 5 Nov 2009, at 01:27, Jason Edgecombe wrote:
> >     AFS Callback Extensions
> >    
> http://www.ietf.org/id/draft-benjamin-extendedcallbackinfo-00.txt
> 
> We need to decide whether we're going to wait for the RPC refresh  
> changes before publishing extended callbacks. My belief is that that's
>  
> the only factor currently delaying this document. The question here, 
> 
> essentially, is whether anyone would deploy extended callbacks before 
> 
> deploying updated RPCs. To date, nobody has said they would do so.

-- 

Matt Benjamin

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309