Re: [Rift] Initial implementation of security in RIFT-Python is complete
Antoni Przygienda <prz@juniper.net> Wed, 24 April 2019 17:47 UTC
Return-Path: <prz@juniper.net>
X-Original-To: rift@ietfa.amsl.com
Delivered-To: rift@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A392C12040E for <rift@ietfa.amsl.com>; Wed, 24 Apr 2019 10:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.337
X-Spam-Level:
X-Spam-Status: No, score=-1.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, KHOP_DYNAMIC=1.363, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qQa57mJehG9z for <rift@ietfa.amsl.com>; Wed, 24 Apr 2019 10:47:35 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEEE0120359 for <rift@ietf.org>; Wed, 24 Apr 2019 10:47:34 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x3OHjObv006624; Wed, 24 Apr 2019 10:47:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=LgsM9oe+vmkYne7Hsez6tTSmYOlWlWLiVqRlNR7W3Ak=; b=mlBtyhxI6cTuL5QHlTneyUqX598/rMkrMFl65nuTX1wMxky/fbMw0T2LmVjo7Mse7A0h +Gystuam8jxuhuYW9oki8wWNGbNBpbOX9uSLoP1PAbzuO/OXGqSZ7gYZCniiNj4vHnB+ oh06Y7oYGMAmW1Cxn62ubcEYRqcubuIHKWQxwUsGHOvmlQUVXZ+o0+8Ho1x5w3JcVVBu 8cHhQixLk8U76UieTc6f2vj38S2PK7yIvWKaK5ZC7ukzO2OhRR83fC+2yC5xBAyQZ9ZZ 0CTUDxifOdeVBZbLR8Tnj2RRMWZaY7gS5tk8/r/P+/kEtpRTTgxD9yqzfwVcYJL8Ob6z pw==
Received: from nam05-co1-obe.outbound.protection.outlook.com (mail-co1nam05lp2054.outbound.protection.outlook.com [104.47.48.54]) by mx0a-00273201.pphosted.com with ESMTP id 2s2ng1grdw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 24 Apr 2019 10:47:31 -0700
Received: from MWHPR05MB3279.namprd05.prod.outlook.com (10.173.230.18) by MWHPR05MB3181.namprd05.prod.outlook.com (10.173.229.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1835.9; Wed, 24 Apr 2019 17:47:29 +0000
Received: from MWHPR05MB3279.namprd05.prod.outlook.com ([fe80::c104:c5bd:b877:2202]) by MWHPR05MB3279.namprd05.prod.outlook.com ([fe80::c104:c5bd:b877:2202%10]) with mapi id 15.20.1835.010; Wed, 24 Apr 2019 17:47:29 +0000
From: Antoni Przygienda <prz@juniper.net>
To: Bruno Rijsman <brunorijsman@gmail.com>, "rift@ietf.org" <rift@ietf.org>
Thread-Topic: Initial implementation of security in RIFT-Python is complete
Thread-Index: AQHU+WF75SyDYoAPLUWqAFRVz5SOtqZLmJe1
Date: Wed, 24 Apr 2019 17:47:29 +0000
Message-ID: <MWHPR05MB3279AB3BE295959AD2AF1BADAC3C0@MWHPR05MB3279.namprd05.prod.outlook.com>
References: <B2545DF8-1C4C-4B97-8CEE-4D5EDCF2EB8D@gmail.com>
In-Reply-To: <B2545DF8-1C4C-4B97-8CEE-4D5EDCF2EB8D@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.239.10]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 70dbf06c-2d08-462d-bd1a-08d6c8dcebc4
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:MWHPR05MB3181;
x-ms-traffictypediagnostic: MWHPR05MB3181:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MWHPR05MB31818441F982E5C8E271B4A8AC3C0@MWHPR05MB3181.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:4502;
x-forefront-prvs: 00179089FD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(396003)(346002)(136003)(39860400002)(189003)(199004)(53376002)(446003)(54896002)(52536014)(19627405001)(53366004)(14444005)(99286004)(11346002)(110136005)(33656002)(316002)(256004)(236005)(476003)(53546011)(6246003)(6306002)(53936002)(2906002)(86362001)(9686003)(2501003)(486006)(3846002)(6506007)(6116002)(102836004)(5660300002)(55016002)(76176011)(105004)(186003)(26005)(7696005)(15650500001)(8676002)(25786009)(8936002)(81156014)(71200400001)(81166006)(14454004)(966005)(74316002)(4744005)(7110500001)(66946007)(66476007)(64756008)(7736002)(66446008)(73956011)(68736007)(76116006)(66556008)(229853002)(2420400007)(606006)(97736004)(6436002)(478600001)(66066001)(71190400001)(493534005)(19477635001); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR05MB3181; H:MWHPR05MB3279.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: MXIMvM0HVbMdcmLgGv8RzrcZXGaJh0VqUkXnwzw1CoVsEDq4rAXP+sXFpFDUDBvaRDAjdAZxBl/3G/K+fxtUY7+xy1/DWdliD8iC2iMzxt/pCb1DB3utngdJDCT07hVhaOgPDQH2P8WUVn0BkNrgvkfS72kf7AyDyKvLtDKq7lR9GLQQjIUQzzc6bfTimhXnzwj+LyehZFEaXr2yETjDh65cXiiywBjap9+g3JUl42xALK6nAzpQalXd/brk+x/jgCQkMlj+DHfp7WQCgrdkfFsIKfUGIBiDrQbJKyTpbDxecZNsPxBtKmWjObMjZMGh1tfzX4/QGT98bH2243rDY4odC7w0t2dF1FHNwh1sX81ZpEFtSTKmHej6VJakUIvEyCBpJhMS8W2A6elgb/OFr+I1iw/5iUdr4Evrsm70074=
Content-Type: multipart/alternative; boundary="_000_MWHPR05MB3279AB3BE295959AD2AF1BADAC3C0MWHPR05MB3279namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 70dbf06c-2d08-462d-bd1a-08d6c8dcebc4
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Apr 2019 17:47:29.3033 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR05MB3181
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-24_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904240130
Archived-At: <https://mailarchive.ietf.org/arch/msg/rift/QKBTOFh3U7mCYSF21eCJJmq0x_Y>
Subject: Re: [Rift] Initial implementation of security in RIFT-Python is complete
X-BeenThere: rift@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of Routing in Fat Trees <rift.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rift>, <mailto:rift-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rift/>
List-Post: <mailto:rift@ietf.org>
List-Help: <mailto:rift-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rift>, <mailto:rift-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2019 17:47:41 -0000
read your guide in detail. makes all perfect sense. will extend schema to what you suggest so inter'op ... thanks --- tony ________________________________ From: Bruno Rijsman <brunorijsman@gmail.com> Sent: Monday, April 22, 2019 4:16 PM To: rift@ietf.org Subject: Initial implementation of security in RIFT-Python is complete I have finished the initial implementation of security in RIFT-Python (security envelope, keys, fingerprints, nonces, packet-nr, etc. etc.) See http://bit.ly/rift-python-security-feature-guide<https://urldefense.proofpoint.com/v2/url?u=http-3A__bit.ly_rift-2Dpython-2Dsecurity-2Dfeature-2Dguide&d=DwMCAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=maKXfKzgRTpiLitqHnJiww&m=htkOLD_Mz6ekfr_iYDTC5Q7xzPbroaycphOlQuwgDAg&s=t-P4E1fGgdJ6fiTwi2uXPbhcMxKse2r47pppAq8EO_I&e=> for a detailed feature guide. While implementing the code, I gathered a number of comments on the security section of the draft -05. I will report these in a follow-up e-mail. -- Bruno
- [Rift] Initial implementation of security in RIFT… Bruno Rijsman
- Re: [Rift] Initial implementation of security in … Antoni Przygienda
- Re: [Rift] Initial implementation of security in … Tony Przygienda
- Re: [Rift] Initial implementation of security in … Bruno Rijsman
- Re: [Rift] Initial implementation of security in … Tony Przygienda