Re: [MULTIMOBSEC-API] api requirements

Miika Komu <miika@iki.fi> Tue, 23 May 2006 17:19 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiaY2-0001bT-B4; Tue, 23 May 2006 13:19:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiaY0-0001N5-WF for multimobsec-api@ietf.org; Tue, 23 May 2006 13:19:57 -0400
Received: from twilight.cs.hut.fi ([130.233.40.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiaXz-0000tT-Lp for multimobsec-api@ietf.org; Tue, 23 May 2006 13:19:56 -0400
Received: by twilight.cs.hut.fi (Postfix, from userid 60001) id D9AAC3119; Tue, 23 May 2006 20:19:52 +0300 (EEST)
X-Spam-Checker-Version: SpamAssassin 3.1.1-niksula20060321 (2006-03-10) on twilight.cs.hut.fi
X-Spam-Level:
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1-niksula20060321
X-Spam-Niksula: No
Received: from kekkonen.cs.hut.fi (kekkonen.cs.hut.fi [130.233.41.50]) by twilight.cs.hut.fi (Postfix) with ESMTP id 67EB12F73; Tue, 23 May 2006 20:19:52 +0300 (EEST)
Received: from localhost (mkomu@localhost) by kekkonen.cs.hut.fi (8.13.4+Sun/8.13.3/Submit) with ESMTP id k4NHJnIe004870; Tue, 23 May 2006 20:19:49 +0300 (EEST)
X-Authentication-Warning: kekkonen.cs.hut.fi: mkomu owned process doing -bs
Date: Tue, 23 May 2006 20:19:49 +0300
From: Miika Komu <miika@iki.fi>
X-X-Sender: mkomu@kekkonen.cs.hut.fi
To: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
Subject: Re: [MULTIMOBSEC-API] api requirements
In-Reply-To: <20060523092851.5256.SHINTA@sfc.wide.ad.jp>
Message-ID: <Pine.SOL.4.64.0605232006570.4193@kekkonen.cs.hut.fi>
References: <20060519165423.523B.SHINTA@sfc.wide.ad.jp> <b9dabded1676f9bd775e46efa01ce9ca@it.uc3m.es> <20060523092851.5256.SHINTA@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: multimobsec-api@ietf.org
X-BeenThere: multimobsec-api@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Multihoming, mobility and security APIs" <multimobsec-api.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/multimobsec-api>, <mailto:multimobsec-api-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/multimobsec-api>
List-Post: <mailto:multimobsec-api@ietf.org>
List-Help: <mailto:multimobsec-api-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/multimobsec-api>, <mailto:multimobsec-api-request@ietf.org?subject=subscribe>
Errors-To: multimobsec-api-bounces@ietf.org

On Tue, 23 May 2006, Shinta Sugimoto wrote:

>> MB: i am not sure what does this sentence means here
>>
>>       ED is a "handle" or "pointer" to
>>       the actual EID.  A given ED serves as a AID [I-D.nordmark-multi6-
>>       noid].
>>
>> MB: i haven't read the noid draft recently, but afair and AID was just 
>> as a ULID not a ED... (at least no more than a shim ULID)
>
> I would leave definitions of ED to Miika.  Miika ?

I think I originally misinterpreted AID to be any application identifer. 
Please remove the latter sentence.

> from <draft-nordmark-multi6-noid-02.txt> Section 1.2:
>
>>       Application identifier (AID)
>>                   - an IP locator which has been selected for
>>                     communication with a peer to be used by the upper
>>                     layer protocol.  128 bits.  This is used for
>>                     pseudo-header checksum computation and connection
>>                     identification in the ULP.  Different sets of
>>                     communication to a host (e.g., different
>>                     connections) might use different AIDs in order to
>>                     enable load spreading.
>
> So, it sounds like notion of AID is similar to that of ULID in SHIM6
> as Marcelo pointed out.

The AID term is a little bit confusing from the viewpoint of EDs, because 
they are also "application identifiers" even though the pseudo-header 
checksum is not based on the ED.

Anyway, maybe we should have the AID term redundantly in the draft 
terminology.

-- 
Miika Komu              miika@iki.fi          http://www.iki.fi/miika/

_______________________________________________
MULTIMOBSEC-API mailing list
MULTIMOBSEC-API@ietf.org
https://www1.ietf.org/mailman/listinfo/multimobsec-api