[nfsv4] callbacks via TCP

Next message: Spencer Shepler: "Re: [nfsv4] callbacks via TCP"
Previous message: rick@snowhite.cis.uoguelph.ca: "[nfsv4] Clarification of 9.4.5"
Next in thread: Spencer Shepler: "Re: [nfsv4] callbacks via TCP"
Reply: Spencer Shepler: "Re: [nfsv4] callbacks via TCP"
Maybe reply: Jim Rees: "Re: [nfsv4] callbacks via TCP"

rick@snowhite.cis.uoguelph.ca

From: rick@snowhite.cis.uoguelph.ca
Message-Id: <200307171925.PAA18293@snowhite.cis.uoguelph.ca>
Subject: [nfsv4] callbacks via TCP
Date: Thu, 17 Jul 2003 15:25:11 -0400 (EDT)

This is going to sound like a dumb one, but I can't find it spelled out
in the RFC, so here goes...

For a callback via TCP, is the server expected to
#1 -  do a "connect" to the client at the specified address
OR
#2 - is it expected to find that one of the connections that already
	exists from client->server has the specified address as the other end

(Since I had done callbacks "in-band" on the
same TCP virtual circuit way back when I did NQNFS, I was thinking #2,
but I now realize the RFC probably means #1.)

So, is it door #1 or door #2?

Thanks again, rick

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4