Re: [ieee-ietf-coord] version 03 of the 'Potential Areas for IETF/IEEE802 Coordination' document

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 28 November 2012 16:21 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB1D321F8760 for <ieee-ietf-coord@ietfa.amsl.com>; Wed, 28 Nov 2012 08:21:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m5v3i38FZl6D for <ieee-ietf-coord@ietfa.amsl.com>; Wed, 28 Nov 2012 08:21:25 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id F11D821F8754 for <ieee-ietf-coord@ietf.org>; Wed, 28 Nov 2012 08:21:24 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id qASGLLfH009990; Wed, 28 Nov 2012 16:21:21 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id qASGLKQX009980 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 28 Nov 2012 16:21:21 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, ieee-ietf-coord@ietf.org
References: <9904FB1B0159DA42B0B887B7FA8119CA023960@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA023960@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 28 Nov 2012 16:21:20 -0000
Message-ID: <01df01cdcd84$66ddee10$3499ca30$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQMUwNaYtvJS7G+5z+9KQ3SsqdBq4ZVxg+vQ
Content-Language: en-gb
Subject: Re: [ieee-ietf-coord] version 03 of the 'Potential Areas for IETF/IEEE802 Coordination' document
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ieee-ietf-coord>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 16:21:25 -0000

Hi Dan,

Update on 2.

The BFD working group was re-chartered as previously discussed to include a
specific work item on BFD for LAG members. The current charter can be seen at
http://datatracker.ietf.org/wg/bfd/charter/

Early allocation of code points have been made by IANA so that there is a UDP
port number and a dedicated MAC address (according to RFC 5342) for use by BFD
over LAG implementations that are currently under test.

As yet, the working group has not adopted
http://datatracker.ietf.org/doc/draft-mmm-bfd-on-lags/ but this is expected to
take place soon.


Thanks,
Adrian


> -----Original Message-----
> From: ieee-ietf-coord-bounces@ietf.org [mailto:ieee-ietf-coord-
> bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
> Sent: 28 November 2012 15:32
> To: ieee-ietf-coord@ietf.org
> Subject: [ieee-ietf-coord] version 03 of the 'Potential Areas for IETF/IEEE802
> Coordination' document
> 
> Please find attached version 03 of the 'Potential Areas for IETF/IEEE802
> Coordination' document. It includes updates resulting from the 10/29
> coordination virtual call as well as information received following the IETF
and IEEE
> 802 Plenary meetings.
> 
> Comments, corrections, questions, concerns are welcome.
> 
> Thanks and Regards,
> 
> Dan
> 
> 
>