IETF Logo Mail Archive

Re: [Openv6] About APONF drafts

xiechf01 <xiechf01@gmail.com> Thu, 12 June 2014 05:45 UTC

Return-Path: <xiechf01@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 46E731B29D7 for <openv6@ietfa.amsl.com>; Wed, 11 Jun 2014 22:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 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, HTML_MESSAGE=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 JrjDWBtcXGx3 for <openv6@ietfa.amsl.com>; Wed, 11 Jun 2014 22:45:07 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4926E1A0375 for <openv6@ietf.org>; Wed, 11 Jun 2014 22:45:07 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id ey11so629105pad.10 for <openv6@ietf.org>; Wed, 11 Jun 2014 22:45:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:references:mime-version:message-id :content-type; bh=u1RM70u6Zu6Pf9iHlx/N3YBD4ELG6B+nAhFpHUpJPtE=; b=ki0iyUcmnLhV21+a/F1K8q37AazFPRjmxET+E5KuCZ+Pj8855pbWZQXwUzPNT0lbCC eeCaP+pjG4lllaYH06X/3aZccw6rnRynPWWYVPm1cc4rjmO1gSY4KXhqZ3HIkno1L5It jLNPl3vAYlk9/AH7vq1Ujp+qtrSfX7K5CvWTVoBMEfzsMLeRyLC6qyMSZE8AgMJQu6cD pf4UbtI+B/6O6yfF8J6ZKR1abZ0TTfZfdRN1E05gl2HZ9TcIC6Gj6v1a4+Y2HO0S+0nM erJkLj/Q1n0KSrSpHlkDZeBtJb6X/QrtHmbUwf7jBnpbQU6IbLpGlNmrPvFTczpDf6bd eJCA==
X-Received: by 10.68.200.10 with SMTP id jo10mr10142987pbc.143.1402551906888; Wed, 11 Jun 2014 22:45:06 -0700 (PDT)
Received: from xiechf-ctbri-PC ([124.127.116.138]) by mx.google.com with ESMTPSA id fk4sm39904750pab.23.2014.06.11.22.45.02 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jun 2014 22:45:06 -0700 (PDT)
Date: Thu, 12 Jun 2014 13:45:09 +0800
From: xiechf01 <xiechf01@gmail.com>
To: "cathy.zhou" <cathy.zhou@huawei.com>, openv6 <openv6@ietf.org>
References: <201406101140259997043@gmail.com>, <A6A061BEE5DDC94A9692D9D81AF776DF3FD9D989@SZXEMA512-MBX.china.huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 1, 3, 52[cn]
Mime-Version: 1.0
Message-ID: <2014061213450617810718@gmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart324060022285_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/oxXc0KxDqbB4xXUYE3hHexEMfac
X-Mailman-Approved-At: Wed, 11 Jun 2014 23:30:11 -0700
Subject: Re: [Openv6] About APONF drafts
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: Thu, 12 Jun 2014 05:45:08 -0000

Yes,  my personal opinion is a workflow that describe the typical usecase will make architecture more comprehensive  and convincing.   :)




xiechf01

From: Zhouqian (Cathy)
Date: 2014-06-10 14:48
To: xiechf01; openv6
Subject: RE: [Openv6] About APONF drafts
Hi Chongfeng,
Thanks for your suggestion. Do you mean the workflow of an example use case?
 
Best Regards,
Cathy
 
From: Openv6 [mailto:openv6-bounces@ietf.org] On Behalf Of xiechf01
Sent: Tuesday, June 10, 2014 11:41 AM
To: openv6
Subject: [Openv6] About APONF drafts
 
 
Hi, folks,
 
I support to these 2 drafts,  for they can help upper-layer applications utilize the carrier network capabilities more efficiently and easily. One suggestion, one part to describe a typical workflow can be added to the current the architecture draft.
 
Chongfeng@chinatelecom



xiechf01

v2.23.0 | Report a Bug | By Email