Re: [xrblock] XRBLOCK meeting at IETF-92?

"Romascanu, Dan (Dan)" <> Mon, 19 January 2015 12:09 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 656801B2A2E for <>; Mon, 19 Jan 2015 04:09:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.874
X-Spam-Status: No, score=-4.874 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, LONGWORDS=2.035, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pshXhdUg7FGw for <>; Mon, 19 Jan 2015 04:09:15 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F0DE71AD375 for <>; Mon, 19 Jan 2015 04:09:14 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.09,426,1418101200"; d="scan'208,217";a="103159032"
Received: from unknown (HELO ([]) by with ESMTP; 19 Jan 2015 07:09:13 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO ([]) by with ESMTP/TLS/AES128-SHA; 19 Jan 2015 07:09:13 -0500
Received: from ([fe80::6db7:b0af:8480:c126]) by ([]) with mapi id 14.03.0174.001; Mon, 19 Jan 2015 07:09:11 -0500
From: "Romascanu, Dan (Dan)" <>
To: "" <>
Thread-Topic: [xrblock] XRBLOCK meeting at IETF-92?
Thread-Index: AdArUq2Tqi6hpw4iRduBS9PK70Nt8gIjbcYw
Date: Mon, 19 Jan 2015 12:09:11 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C96ECB4AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [xrblock] XRBLOCK meeting at IETF-92?
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 19 Jan 2015 12:09:19 -0000


I did not see any answer to this message, and more important - no proposals for agenda items.
If nothing comes up in the next few days I will send a notification that the group does not plan to hold a session at IETF 92.

From: xrblock [] On Behalf Of Romascanu, Dan (Dan)
Sent: Thursday, January 08, 2015 4:52 PM
Subject: [xrblock] XRBLOCK meeting at IETF-92?


It's time to request a meeting slot at IETF-92 if we plan to meet. Before making a request I would suggest to discuss what would be the agenda.

As a reminder - we met for one hour at IETF-91.

Our list of conflicts at IETF-91 included:

trill siprec rtcweb raiarea payload opsawg opsarea netmod netconf mmusic lmap ippm insipid codec bmwg bfcpbis avtext avtcore tsvarea sacm alto spring pce mpls i2rs idr

Thanks and Regards,