[hiaps] Service Function Chaining and Host Address/Id
Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 19 November 2014 18:21 UTC
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: hiaps@ietfa.amsl.com
Delivered-To: hiaps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E27D1A19FC for <hiaps@ietfa.amsl.com>; Wed, 19 Nov 2014 10:21:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mOZpfN3mPl-o for <hiaps@ietfa.amsl.com>; Wed, 19 Nov 2014 10:21:54 -0800 (PST)
Received: from mail-yh0-x22b.google.com (mail-yh0-x22b.google.com [IPv6:2607:f8b0:4002:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE4F31A0006 for <hiaps@ietf.org>; Wed, 19 Nov 2014 10:21:54 -0800 (PST)
Received: by mail-yh0-f43.google.com with SMTP id z6so545702yhz.30 for <hiaps@ietf.org>; Wed, 19 Nov 2014 10:21:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=VSuErYSW8owdOymzN9yxSb7aptmd0/rAYQI4vIO5ivM=; b=WNkmEiBC2cxeYW18Tgd4EFNOb9/hqVcib/9Rz2CbxnQk/xtnyBWvJpNkyVVnqySAYa +5U+CwDmN+bjtJWs6eeCTI9Y+U4jRZAexawAifGpCdH7GFPa4Hwy1J/E4SX5n+57EMkK FFUZrFJZUUk5jOJPsIzvkyhUS8B8p/s4HbAUuInblDvZT2ATyd/JV/ZYA22t31GanbhV gjTvAb2pfpyQFxV2WSOjGPUhUQBIw0glfAcTNLutJO8j5XrQxsqlCJL0gY8Sn88LeX3m RPZetN40Lx1y890Hf2GNwcOeIJUaXxiM1CLENi3fKDv1XcLUvuSPdRkxUE5B+tQIuHA0 OQTw==
MIME-Version: 1.0
X-Received: by 10.170.214.6 with SMTP id g6mr19862156ykf.34.1416421313921; Wed, 19 Nov 2014 10:21:53 -0800 (PST)
Received: by 10.170.71.198 with HTTP; Wed, 19 Nov 2014 10:21:53 -0800 (PST)
Date: Wed, 19 Nov 2014 12:21:53 -0600
Message-ID: <CAC8QAcfmhYgZgXJfPoMHjakPEPxCcBrq+LeuWXnxedp+VqcGew@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "hiaps@ietf.org" <hiaps@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/hiaps/8xds4t0rttzgmpEUe66RdPwlAok
Subject: [hiaps] Service Function Chaining and Host Address/Id
X-BeenThere: hiaps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "Host Identification, Address and Prefix Sharing in Wi-Fi Access \(hiaps\)" <hiaps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hiaps>, <mailto:hiaps-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hiaps/>
List-Post: <mailto:hiaps@ietf.org>
List-Help: <mailto:hiaps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hiaps>, <mailto:hiaps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2014 18:21:56 -0000
Hi all, Host Address/Id issue is coming up in newer contexts such as Service Function Chaining. For more info, please check this expired draft: https://tools.ietf.org/html/draft-sarikaya-sfc-address-sharing-in-sfc-00 More use cases can be added to the ones reported in the above draft. I think that out-of-band solution approach will also be OK in such contexts. Regards, Behcet
- [hiaps] Service Function Chaining and Host Addres… Behcet Sarikaya