Re: [OPSAWG] Basic ietf process question ...
Robert Raszuk <robert@raszuk.net> Fri, 03 August 2012 14:31 UTC
Return-Path: <robert@raszuk.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28E1A21F8D99 for <ietf@ietfa.amsl.com>; Fri, 3 Aug 2012 07:31:45 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjo87hSVQDsA for <ietf@ietfa.amsl.com>; Fri, 3 Aug 2012 07:31:44 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 5651921F8D6C for <ietf@ietf.org>; Fri, 3 Aug 2012 07:31:44 -0700 (PDT)
Received: (qmail 30588 invoked by uid 399); 3 Aug 2012 14:31:43 -0000
Received: from unknown (HELO ?10.0.1.2?) (pbs:robert@raszuk.net@64.114.198.24) by mail1310.opentransfer.com with ESMTPM; 3 Aug 2012 14:31:43 -0000
X-Originating-IP: 64.114.198.24
Message-ID: <501BE0CE.90605@raszuk.net>
Date: Fri, 03 Aug 2012 16:31:42 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: j.schoenwaelder@jacobs-university.de
Subject: Re: [OPSAWG] Basic ietf process question ...
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <501AC43A.3020307@raszuk.net> <501B767B.6030501@gmail.com> <501B7C22.3030706@raszuk.net> <20120803132945.GD88437@elstar.local>
In-Reply-To: <20120803132945.GD88437@elstar.local>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 14:31:45 -0000
Hi Juergen, Many thx for the great suggestion ! However perhaps you are much more knowledgeable in that area and could recommend which model fit the best the requirement to standardize configuration of any new protocol or protocol extension at least in the space of routing and routing protocols or services being based on them ? As you know the current IRS framework driven by junisco is trying to come with common API to the routing system agreed across vendors. This is great as attempts never happened in the past. But if we are at this phase I think creating a network elements abstraction layer and be able to configure/monitor any protocol and service at the unified way is one of the building blocks we should start with. And of course I think this is very clear to everyone if it is not made mandatory in each draft as new section or appendix it is just not going to happen in practice. Best regards, R. > On Fri, Aug 03, 2012 at 09:22:10AM +0200, Robert Raszuk wrote: >> >> Aha .. so you are saying that MIBs are not mandatory .... Very >> interesting. So I guess SSH to the routers and box by box cli >> provisioning is here to stay for a while I think :( >> > > Robert, > > you may want to take a closer look at the data models currently being > defined in the NETMOD working group. Please review them and send any > comments. > > /js >
- Re: New Version Notification for draft-leiba-exte… Barry Leiba
- Re: New Version Notification for draft-leiba-exte… Murray S. Kucherawy
- Basic ietf process question ... Robert Raszuk
- Re: Basic ietf process question ... Randy Bush
- RE: Basic ietf process question ... Romascanu, Dan (Dan)
- Re: Basic ietf process question ... Robert Raszuk
- RE: [OPSAWG] Basic ietf process question ... Romascanu, Dan (Dan)
- Re: Basic ietf process question ... Thomas Nadeau
- Re: Basic ietf process question ... Brian E Carpenter
- Re: Basic ietf process question ... Robert Raszuk
- Re: Basic ietf process question ... Robert Raszuk
- Re: Basic ietf process question ... Brian E Carpenter
- Re: Basic ietf process question ... Robert Raszuk
- Re: [OPSAWG] Basic ietf process question ... Randy Presuhn
- Re: [OPSAWG] Basic ietf process question ... Robert Raszuk
- Re: [OPSAWG] Basic ietf process question ... Andy Bierman
- Re: [OPSAWG] Basic ietf process question ... David Harrington
- Re: Basic ietf process question ... Joe Hildebrand (jhildebr)
- Re: [OPSAWG] Basic ietf process question ... Juergen Schoenwaelder
- Re: [OPSAWG] Basic ietf process question ... Juergen Schoenwaelder
- Re: Basic ietf process question ... Mark Nottingham
- Re: Basic ietf process question ... Martin Rex
- Re: Basic ietf process question ... ned+ietf
- Re: Basic ietf process question ... Mark Nottingham
- Re: Basic ietf process question ... ned+ietf
- Re: Basic ietf process question ... Mark Nottingham
- Re: Basic ietf process question ... Martin Thomson
- Re: Basic ietf process question ... Mark Nottingham
- Re: Basic ietf process question ... Hector Santos
- Re: Basic ietf process question ... ned+ietf
- Re: Basic ietf process question ... Mark Nottingham
- RE: Basic ietf process question ... Worley, Dale R (Dale)
- Re: Basic ietf process question ... Tim Bray