RE: [midcom] RE: Last Call: 'Definitions of Managed Objects for Middlebox Communication' to Proposed Standard (draft-ietf-midcom-mib)

Pyda Srisuresh <srisuresh@yahoo.com> Mon, 28 August 2006 16:34 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GHk4d-0004Xc-42; Mon, 28 Aug 2006 12:34:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GHk4b-0004O2-6e for midcom@ietf.org; Mon, 28 Aug 2006 12:34:53 -0400
Received: from web33314.mail.mud.yahoo.com ([68.142.206.129]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GHjyH-0005bq-5O for midcom@ietf.org; Mon, 28 Aug 2006 12:28:22 -0400
Received: (qmail 33840 invoked by uid 60001); 28 Aug 2006 16:28:20 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=MgEBghYIxTYKP74I0t44VBZtgVd3E583OArWrqG1/1NsLUDC4jqB2h0Yw9opTBE6Jj64InMHfcoAhuLpcE+s0sSAGd5PViAJgSuuw7/LSdgJlf2Ng7bu436N6uSND9nK01FS+Lq/YHP0ig/1+ALT2R+YVeP+f7A1AXLj2uTmiUk= ;
Message-ID: <20060828162820.33838.qmail@web33314.mail.mud.yahoo.com>
Received: from [69.236.82.106] by web33314.mail.mud.yahoo.com via HTTP; Mon, 28 Aug 2006 09:28:20 PDT
Date: Mon, 28 Aug 2006 09:28:20 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: RE: [midcom] RE: Last Call: 'Definitions of Managed Objects for Middlebox Communication' to Proposed Standard (draft-ietf-midcom-mib)
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F0B1FCBEC@IS0004AVEXU1.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: midcom@ietf.org
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

Hi Dan,

Thanks. Please see my responses inline.

regards,
suresh

--- "Romascanu, Dan (Dan)" <dromasca@avaya.com> wrote:

> Hi Suresh,
> 
> (I took out the ietf and iesg lists from the distribution)
> 
> Thank you for the answers. I am happy with many of them, I am waiting
> for clarification from you co-authors on a couple of issues, and have
> two more comments on your answers:
> 
[suresh] Sounds good. Thanks.

>  
>  
> 
> > -----Original Message-----
> > From: Pyda Srisuresh [mailto:srisuresh@yahoo.com] 
> >> 
> > > 8 . There is no DEFVAL for midcomRuleFlowDirection
> > > 
> > [suresh] Right, that was intentional.
> > 
> 
> In the absence of a DEFVAL what is supposed to return an agent on a read
> operation before the object was first time written?
> 
[suresh] I see what you mean. I think, it should be OK to set the DEFVAL to
outbound(2).

> > > 10. What notification needs to be sent when 
> > midcomConfigIfEnabled is 
> > > set to false? Neither the DESCRIPTION of the object nor the 
> > one of the 
> > > notifications do provide any clue.
> > > 
> > [suresh] The DESCRIPTION for midcomConfigIfEnabled does say 
> > the following.
> > 
> >    Setting
> >    this object to false(2) immediately stops middlebox
> >    support at the indexed IP interface.  This implies that
> >    all policy rules that use NAT or firewall resources at
> >    the indexed IP interface are terminated immediately.
> >    In this case, The MIDCOM agent MUST send notifications
> >    to all MIDCOM clients that have access to one of the
> >    terminated rules.
> > 
> 
> I saw this text, but my question was what notifications are being sent?
> 
[suresh] midcomUnsolicitedRuleEvent notifications are sent for each of the
rules that refer the ifindex. We will add this to the DESCRIPTION text. Thanks.

> Regards,
> 
> Dan

regards,
suresh




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