[midcom] Resolving outstanding "discusses"

Melinda Shore <mshore@cisco.com> Thu, 30 August 2007 16:48 UTC

Return-path: <midcom-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQnBx-0007jK-Kv; Thu, 30 Aug 2007 12:48:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQnBv-0007j9-Nd for midcom@ietf.org; Thu, 30 Aug 2007 12:48:23 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQnBu-0001Vt-Go for midcom@ietf.org; Thu, 30 Aug 2007 12:48:23 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 30 Aug 2007 12:48:22 -0400
X-IronPort-AV: i="4.19,326,1183348800"; d="scan'208"; a="69612659:sNHT44687630"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7UGmMH6011186 for <midcom@ietf.org>; Thu, 30 Aug 2007 12:48:22 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7UGmH0H024492 for <midcom@ietf.org>; Thu, 30 Aug 2007 16:48:22 GMT
Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Aug 2007 12:48:02 -0400
Received: from 10.86.115.70 ([10.86.115.70]) by xmb-rtp-205.amer.cisco.com ([64.102.31.59]) via Exchange Front-End Server email.cisco.com ([64.102.31.38]) with Microsoft Exchange Server HTTP-DAV ; Thu, 30 Aug 2007 16:48:02 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 30 Aug 2007 12:48:01 -0400
From: Melinda Shore <mshore@cisco.com>
To: <midcom@ietf.org>
Message-ID: <C2FC6D01.29007%mshore@cisco.com>
Thread-Topic: Resolving outstanding "discusses"
Thread-Index: AcfrJYa5xSZ7HVcYEdyIXwAKleNSdA==
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 30 Aug 2007 16:48:02.0992 (UTC) FILETIME=[87E9EB00:01C7EB25]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=827; t=1188492502; x=1189356502; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mshore@cisco.com; z=From:=20Melinda=20Shore=20<mshore@cisco.com> |Subject:=20Resolving=20outstanding=20=22discusses=22 |Sender:=20 |To:=20<midcom@ietf.org>; bh=pFLIS2snhYPp6acH60Ta95YgEGdjreuWUzULYqgvkbo=; b=dktggkOMkUSZVYpj8MWQxVWikxpHrUu3y7j1TvWCW4LNXfEkhgxdF1XbWmTi4HofJqmRU9lS 7INOUvq3lAxN5vin293T2uenWH8JT1UNJ4+YjDVJlf/CUI3wvpwuh5HT;
Authentication-Results: rtp-dkim-1; header.From=mshore@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [midcom] Resolving outstanding "discusses"
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: midcom.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
Errors-To: midcom-bounces@ietf.org

David Harrington recently posted some comments to the mailing
list and to the IESG draft status tracker, resulting in a
"discuss" that needs to be resolved before the document can move
forward towards publication.  For those who didn't see
them when they were first issued, they're in the draft tracker
at 
https://datatracker.ietf.org/idtracker/draft-ietf-midcom-mib/comment/70299/
.

Please have a look at them, particularly the questions about
persistence and reboots.  My expectation, given the activity level
on the mailing list, is that the most direct approach to getting
these resolved would be for the draft authors to propose a solution
to the mailing list rather than wait for it to be hashed out here.
Does anybody feel strongly about this, or already have specific
proposals?

Thanks,

Melinda

_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom