Re: Acknowledgment of registration requests

Mark Laubach <laubach@terra.com21.com> Wed, 13 September 1995 17:43 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14424; 13 Sep 95 13:43 EDT
Received: from nexen.nexen.com by IETF.CNRI.Reston.VA.US id aa14420; 13 Sep 95 13:43 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by nexen.nexen.com (8.6.12/8.6.12) with ESMTP id NAA27120; Wed, 13 Sep 1995 13:19:50 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id NAA03013 for rolc-out; Wed, 13 Sep 1995 13:11:07 -0400
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id NAA03004; Wed, 13 Sep 1995 13:11:03 -0400
Received: from terra.com21.com (terra.com21.com [140.174.223.21]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id NAA17589; Wed, 13 Sep 1995 13:05:47 -0400
Received: from [140.174.223.64] (matmos.com21.com [140.174.223.64]) by terra.com21.com (8.6.10/8.6.5) with SMTP id KAA08427; Wed, 13 Sep 1995 10:22:01 -0700
X-Sender: laubach@terra.com21.com
Message-Id: <v02130533ac7c7fd7a5d4@[140.174.223.64]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 13 Sep 1995 08:43:35 -0800
To: James Luciani <luciani@nexen.com>, rolc@nexen.com
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Laubach <laubach@terra.com21.com>
Subject: Re: Acknowledgment of registration requests
Cc: luciani@nexen.com
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

At 21:51 9/12/95, James Luciani wrote:
>an acknowledgment.  In its place, I would suggest having the given client
>make a request for itself in the same way that 1577 clients do (that
>is SA=DA=client address) and the reply would serve as the acknowledgment.

FYI, To be a little more clear, RFC1577 clients are not required to arp
for itself.  The update I-D to RFC1577 has made a change to require this
behavior to support the updated client registration to the ATMARP service.
This update was an approved change by the WG, so I suspect it will
continue as the new registration procedure when the update I-D makes it
to proposed status.

Mark