Re: [Openv6] APONF (Application-based Policy for Network Functions): new BOF for IETF 90 (requesting comments)

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 07 June 2014 20:39 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: openv6@ietfa.amsl.com
Delivered-To: openv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30B591A0195 for <openv6@ietfa.amsl.com>; Sat, 7 Jun 2014 13:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 b4FkzUw0WIMt for <openv6@ietfa.amsl.com>; Sat, 7 Jun 2014 13:39:38 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B1BF1A00A5 for <openv6@ietf.org>; Sat, 7 Jun 2014 13:39:38 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id jt11so3856121pbb.36 for <openv6@ietf.org>; Sat, 07 Jun 2014 13:39:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BJK5+ILmbV3mg+0k64cQ4ew0U+smiL0qmP5895GcJJs=; b=nBlZwpa4sBfuZu4eYxHb0CD/mQiUjaGNjSt935+JdA1GM8ziJ81XbsiKHsJr2RhG0F cs+IuLH8TJi41xdcXPG53SGoTErtlbPDFVz61IjK9es8kv+KcIeEZGQVNcpFFa+tCqdq 7MW8fmiifmk3td0JFGhg7BejyMr+x2eSR/q3IhysQSOf4BpgWYw3OvnfL4VmD9wrFloE 9barMjfca4tLQaeGx7i9hXlElhfMEKnGxNuKAcyiyZQIoHRO4a+vuFYOnm7NEHgqfDtc 008MMbHZkWXOC89aDGMdyEPJk5Law3bVzWDKFRyeZFIRKWrwM2xY9Waig+/CvBeWDy85 QkuA==
X-Received: by 10.68.239.137 with SMTP id vs9mr15108285pbc.84.1402173571148; Sat, 07 Jun 2014 13:39:31 -0700 (PDT)
Received: from [192.168.178.23] (128.199.69.111.dynamic.snap.net.nz. [111.69.199.128]) by mx.google.com with ESMTPSA id jd5sm52290610pbb.18.2014.06.07.13.39.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 07 Jun 2014 13:39:30 -0700 (PDT)
Message-ID: <5393787F.8040301@gmail.com>
Date: Sun, 08 Jun 2014 08:39:27 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: karagian@cs.utwente.nl
References: <FF1A9612A94D5C4A81ED7DE1039AB80F4F47B090@EXMBX23.ad.utwente.nl>
In-Reply-To: <FF1A9612A94D5C4A81ED7DE1039AB80F4F47B090@EXMBX23.ad.utwente.nl>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/A9HO-jjZ0ImCFnJB7xcal4pBob8
Cc: openv6@ietf.org
Subject: Re: [Openv6] APONF (Application-based Policy for Network Functions): new BOF for IETF 90 (requesting comments)
X-BeenThere: openv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Openv6 discussion list <openv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openv6>, <mailto:openv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/openv6/>
List-Post: <mailto:openv6@ietf.org>
List-Help: <mailto:openv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openv6>, <mailto:openv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jun 2014 20:39:40 -0000

Hi,

Can you explain the specific relationship between this BOF and IPv6?
As far as I can see, it is 100% independent of the IP version (and that
is a good thing).

By the way, the topic of autonomic configuration by negotiation
between various network elements, which could include the elements
involved in the APONF scenarios, is the subject of another BOF
proposal, which also has no specific dependency on IPv6:
http://trac.tools.ietf.org/bof/trac/wiki/WikiStart#UCANproposal
APONF might be an additional use case for UCAN.

Regards
   Brian Carpenter

On 08/06/2014 06:01, karagian@cs.utwente.nl wrote:
> Hi all,
> 
> Please note that a request for a BOF associated with Openv6 has been requested for IETF 90.
> 
> The name of this BOF is:
> 
> APONF (Application-based Policy for Network Functions).
> 
> The main goal of APONF is to specify the application-based policy protocol(s), mechanisms and models required by transport applications to easily, accurately, and efficiently select and use the available communication network capabilities, i.e., network management and/or traffic policies.
> 
> For more details on APONF, please see:
> http://trac.tools.ietf.org/bof/trac/#
> 
> Please note that in association with this BOF two Internet drafts have been (up to now) submitted .
> These drafts are:
> 
> APONF problem statement:
> http://tools.ietf.org/id/draft-karagiannis-aponf-problem-statement-00.txt
> 
> APONF architecture:
> http://tools.ietf.org/id/draft-zhou-aponf-architecture-00.txt
> 
> Your comments on the APONF BOF, and on the Internet drafts listed above are very much appreciated!
> 
> Best regards,
> Georgios Karagiannis
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Openv6 mailing list
> Openv6@ietf.org
> https://www.ietf.org/mailman/listinfo/openv6