From robert.g.cole.civ@mail.mil Wed Feb 1 13:37:56 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 949F111E80D3 for ; Wed, 1 Feb 2012 13:37:56 -0800 (PST) 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=[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 UHfS974rs9uX for ; Wed, 1 Feb 2012 13:37:56 -0800 (PST) Received: from edge-cols.mail.mil (edge-cols.mail.mil [131.64.100.9]) by ietfa.amsl.com (Postfix) with ESMTP id A5EE611E8072 for ; Wed, 1 Feb 2012 13:37:53 -0800 (PST) Received: from UCOLHP3H.easf.csd.disa.mil (131.64.100.149) by ucolhp2w.easf.csd.disa.mil (131.64.100.9) with Microsoft SMTP Server (TLS) id 14.1.339.1; Wed, 1 Feb 2012 21:37:45 +0000 Received: from UCOLHP4J.easf.csd.disa.mil ([169.254.8.247]) by UCOLHP3H.easf.csd.disa.mil ([131.64.100.149]) with mapi id 14.01.0339.001; Wed, 1 Feb 2012 21:37:46 +0000 From: "Cole, Robert G USA CIV (US)" To: "manet@ietf.org" Thread-Topic: [manet] I-D Action: draft-ietf-manet-report-mib-02.txt (UNCLASSIFIED) Thread-Index: AQHM4I8FWel8TbM1xkOHiAieUWqzr5YokWaQ Date: Wed, 1 Feb 2012 21:37:45 +0000 Message-ID: References: <20120201030917.18173.68833.idtracker@ietfa.amsl.com> In-Reply-To: <20120201030917.18173.68833.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [131.64.77.10] Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_00F6_01CCE0FF.D1523610" MIME-Version: 1.0 Subject: Re: [manet] I-D Action: draft-ietf-manet-report-mib-02.txt (UNCLASSIFIED) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 21:37:56 -0000 ------=_NextPart_000_00F6_01CCE0FF.D1523610 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Classification: UNCLASSIFIED Caveats: NONE Just a quick comment on this revision to the report mib. This is the revision that drastically reduces the complexity of the mib in to significant ways. First, it now addresses only the 'sampling' capabilities that we had in the earlier drafts. And Second, we are now using 'AUGMENTS' to extend/leverage the current sampling tables from the RMON2 MIB. You'll noticed that the draft is greatly reduced in size. Comments are appreciated. Thanks, Bob -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Tuesday, January 31, 2012 10:09 PM To: i-d-announce@ietf.org Cc: manet@ietf.org Subject: [manet] I-D Action: draft-ietf-manet-report-mib-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF. Title : Definition of Managed Objects for Performance Reporting Author(s) : Robert G. Cole Joseph Macker Andy Bierman Filename : draft-ietf-manet-report-mib-02.txt Pages : 26 Date : 2012-01-31 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects for configuring autonomous report generation on any device that supports MIBs containing counter and gauge objects for performance monitoring. This allows a management station to instruct a device to build off-line reports to be collected asynchronously by the management station. Further, this REPORT-SAMPLED-MIB can be configured in a proxy configuration where the report generation is performed on a device in close network proximity to the device containing the referenced counter objects. Hence, this capability allows network operators to reduce the SNMP polling traffic burden on Mobile Ad-Hoc and Disruption Tolerant Networks which is typical of SNMP performance management applications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-manet-report-mib-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-manet-report-mib-02.txt _______________________________________________ manet mailing list manet@ietf.org https://www.ietf.org/mailman/listinfo/manet Classification: UNCLASSIFIED Caveats: NONE ------=_NextPart_000_00F6_01CCE0FF.D1523610 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIS3DCCA3Aw ggJYoAMCAQICAQUwDQYJKoZIhvcNAQEFBQAwWzELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g R292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxFjAUBgNVBAMTDURvRCBSb290 IENBIDIwHhcNMDQxMjEzMTUwMDEwWhcNMjkxMjA1MTUwMDEwWjBbMQswCQYDVQQGEwJVUzEYMBYG A1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEWMBQGA1UE AxMNRG9EIFJvb3QgQ0EgMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMAswfaNO6z/ PzzWcb64dCIH7HBBFfyrQOMHqsHD2J/+2kw6vz/I2Ch7SzYBwKxFJcPSDgqPhRhkED0aE3Aqb47X 3I2Ts0EPOCHNravCPSoF01cRNw3NjFH5k+PMRkkhjhS0zcsUPjjNcjHuqxLyZeo0LlZd/+5jdctt upE0/J7z9C0cvlDEQt9ZiP9qs/qobD3LVnFxBZa7n4DlgEVZZ0Gw68OtYKSAdQYXnA70Q+CZDhv7 f/WzzLKBgrH9MsG4vkGkZLVgOlpRMIzO3kEsGUdcSRBkuXSph0GvfW66wbihv2UxOgRn+bW7jpKK AGO4seaMOF+D/1DVO6Jda7IQzGMCAwEAAaM/MD0wHQYDVR0OBBYEFEl0uwxeunr+AlTve6DGlcYJ gHCWMAsGA1UdDwQEAwIBhjAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBBQUAA4IBAQCYkY0/ ici79cBpcyk7Nay6swh2PXAJkumERCEBfRR2G+5RbB2NFTctezFp9JpEuK9GzDT6I8sDJxnSgyF1 K+fgG5km3IRAleio0sz2WFxm7z9KlxCCHboKot1bBiudp2RO6y4BNaS0PxOtVeTVc6hpmxHxmPIx Hm9A1Ph4n46RoG9wBJBmqgYrzuF6krV94eDRluehOi3MsZ0fBUTth5nTTRpwOcEEDOV+2fGv1yAO 8SJ6JaRzmcw/pAcnlqiile2CuRbTnguHwsHyiPVi32jfx7xpUe2xXNxUVCkPCTmarAPB2wxNrm8K ehZJ8b+R0jiU0/aVLLdsyUK2jcqQjYXZMIIEwTCCA6mgAwIBAgIDDNszMA0GCSqGSIb3DQEBBQUA MF0xCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0RvRDEM MAoGA1UECxMDUEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwgQ0EtMjQwHhcNMTAwMjI1MDAwMDAwWhcN MTMwMjI0MjM1OTU5WjB5MQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQww CgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEMMAoGA1UECxMDVVNBMSYwJAYDVQQDEx1DT0xFLlJP QkVSVC5HUkFOT1QuMTM2NjU2MDM5MDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKU7 jo5hPKcK6V92Cni9Bu445V7UQJBLIu1eX3brV/yB6uFNd+lIdV5n6RBpE1QcsIUEyS1GVDvTR/Qs kbUInPJC8ioZCX/V5Y2J8nRNidXoLX4SdeQ3Gc6jLPn+1W8KHRdATHy+SYGcrHnePyRAhTO73rN3 97CqgOaxnS4wo/Eanw9Re5UGq70cN/G7376Oxa7A2xdtY9w8gLUilFmcYXuwR7FGxcnDhsqAW3fv tgM18ZWn/hioEhmRZz514jXPnHCvSPAkofjb4Mjucnku8uNowu+PMw5Yqv9wimBEitvQGPnyac41 MNtsflnmVqWswTwhzVzIGdodKZTw2h6byTcCAwEAAaOCAWwwggFoMB8GA1UdIwQYMBaAFFSqcyrH s3fqzSJAeUh7EfunmSKCMD8GA1UdHwQ4MDYwNKAyoDCGLmh0dHA6Ly9jcmwuZGlzYS5taWwvZ2V0 Y3JsP0RPRCUyMEVNQUlMJTIwQ0EtMjQwDgYDVR0PAQH/BAQDAgUgMCMGA1UdIAQcMBowCwYJYIZI AWUCAQsJMAsGCWCGSAFlAgELEzAdBgNVHQ4EFgQUyGOLOF3I71SMIzwNIujoox8W0CowbQYIKwYB BQUHAQEEYTBfMDsGCCsGAQUFBzAChi9odHRwOi8vY3JsLmRpc2EubWlsL2dldHNpZ24/RE9EJTIw RU1BSUwlMjBDQS0yNDAgBggrBgEFBQcwAYYUaHR0cDovL29jc3AuZGlzYS5taWwwJAYDVR0RBB0w G4EZcm9iZXJ0LmcuY29sZUB1cy5hcm15Lm1pbDAbBgNVHQkEFDASMBAGCCsGAQUFBwkEMQQTAlVT MA0GCSqGSIb3DQEBBQUAA4IBAQAVD+rqDKxhGbV78baC+EUC3jiDUO6C41wsmB4ckt5akJPvVrB4 mjlnoG0lm19qovC98eO0vPQMUx1F6/jP9/xg32W2Ks2HZUR3ipZWBEqVi8i20Wz4sVFgXHkJjoP5 bju0XvJk/d6wze65iZqFuILuPplugaHg7iC5B/NAMELTGx8hoK3LVqmIIyMpEFlrxTygIkyuI+NK IqcbLtBOEW0bP7TNyBh/VShmtrXAtpPP0AAi+kaUURcG1x2xdPCR3cD2bjWYkfxQYeZRl2zTuOMg Mpr9pG3MuImao/C+v6IaXGuAU8xS8hSEbHGNLrXjJ9UIxw0K45WxjR7CrPFIJ4R5MIIFDDCCA/Sg AwIBAgIDDNswMA0GCSqGSIb3DQEBBQUAMF0xCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdv dmVybm1lbnQxDDAKBgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwg Q0EtMjQwHhcNMTAwMjI1MDAwMDAwWhcNMTMwMjI0MjM1OTU5WjB5MQswCQYDVQQGEwJVUzEYMBYG A1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEMMAoGA1UE CxMDVVNBMSYwJAYDVQQDEx1DT0xFLlJPQkVSVC5HUkFOT1QuMTM2NjU2MDM5MDCCASIwDQYJKoZI hvcNAQEBBQADggEPADCCAQoCggEBAOsVn1k8Ax7kkzWXvrNf7oI7iy5zEeLACdGKrODL9riDBNUF HvD4JtafUcwq03s4Daq0tscNL8J1ONDeML5s0X8UeNfCyexrkSpPwY9g/zVO6mJmG4OunTz/7fc2 G0ZR64VYlEBZeQ88JIMIs6bYXiO9SxuOCS47aGx/CGqdpFwt713bBAQvzAjLUSWBvjZN2bviTQrY wAg1/1AnlxY6Zl4YPBSV9c1TbtTQNjbRyFRabiqNMh0XaQ0ZHxQgsGOqNwfyMlmadL2m3ILhKpFh oMfOV01at2eDj8+wFvDXLXAL1f3HAQKv5W5GEoBYNDqp/ULDBJcXVPT8mYWzxMkca/MCAwEAAaOC AbcwggGzMB8GA1UdIwQYMBaAFFSqcyrHs3fqzSJAeUh7EfunmSKCMD8GA1UdHwQ4MDYwNKAyoDCG Lmh0dHA6Ly9jcmwuZGlzYS5taWwvZ2V0Y3JsP0RPRCUyMEVNQUlMJTIwQ0EtMjQwDgYDVR0PAQH/ BAQDAgbAMCMGA1UdIAQcMBowCwYJYIZIAWUCAQsJMAsGCWCGSAFlAgELEzAdBgNVHQ4EFgQUBeVx RkqbKuf17SKV2ZZOsCXLQ+gwbQYIKwYBBQUHAQEEYTBfMDsGCCsGAQUFBzAChi9odHRwOi8vY3Js LmRpc2EubWlsL2dldHNpZ24/RE9EJTIwRU1BSUwlMjBDQS0yNDAgBggrBgEFBQcwAYYUaHR0cDov L29jc3AuZGlzYS5taWwwRAYDVR0RBD0wO4EZcm9iZXJ0LmcuY29sZUB1cy5hcm15Lm1pbKAeBgor BgEEAYI3FAIDoBAMDjEzNjY1NjAzOTBAbWlsMBsGA1UdCQQUMBIwEAYIKwYBBQUHCQQxBBMCVVMw KQYDVR0lBCIwIAYKKwYBBAGCNxQCAgYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBBQUA A4IBAQBhwXMphuaV+lhIZbI35yGpZ7zy/uXNyr41+/dibahnAIisIIHFSTeEk9GFepxqV45hagTo //0UycQ/ShOIHzV/+u3l/97k+l8imMdbjhgklb2UFROSz7TJzhO3w4S7g7DpU+GTxE2Uax+iD2t0 Bmio3ut9fr/dWvi6OTYVFMTW7M6pd8gOPqmg8ADGdljGsSotMAhXzFJgAPtnsca5HfyYpGi0NQj0 ucT/sWUGwnnjlqtYyP+SY2pOPpbN9gACkv8UKJMkik5GEFobaHbI8KWr4FFOXAIAauW1DvGFq5Pe WdDgj39r6PkdOLg3v+B9/hnkP6uOyH5Oi9pcHb+d/hPuMIIFjzCCBHegAwIBAgIBRTANBgkqhkiG 9w0BAQUFADBbMQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQL EwNEb0QxDDAKBgNVBAsTA1BLSTEWMBQGA1UEAxMNRG9EIFJvb3QgQ0EgMjAeFw0wOTAxMjYyMDI2 MTVaFw0xNTAxMjUyMDI2MTVaMF0xCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1l bnQxDDAKBgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwgQ0EtMjQw ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQClLlh6od7mmlv2AvHV1Nw1I5p7bihkdBpw PJYdzMKfdAQ8DDmSIQgNEk6g1zeo0snGJ50o+lXXshcEGc4yvPB5nvVoqy7MzzcEsvgKZZpJIBQl wbwSaqBCbRsItIehQiKrE5naAgE5H14IV2tg3hN+aGp+QfWJgDh6/Zey0uKWSzaAYrbsJbvQD6ej zVGo99J5VZA0JqPkXM27aCZ0CTeh5q/N5D6ZR/9/wke8ZYS6MimjDvDColt66rJKfQvGw26svRB/ T6l2Oj0CASwqMLT3yKDSmDp8CNBaiQ+1ioL6DTAeftbRx7ZDJ7EoqQzjswd432JkmkWMTs2vDq6c WDbfAgMBAAGjggJaMIICVjAOBgNVHQ8BAf8EBAMCAYYwHwYDVR0jBBgwFoAUSXS7DF66ev4CVO97 oMaVxgmAcJYwHQYDVR0OBBYEFFSqcyrHs3fqzSJAeUh7EfunmSKCMAwGA1UdJAQFMAOAAQAwEgYD VR0TAQH/BAgwBgEB/wIBADCBnwYDVR0gBIGXMIGUMAsGCWCGSAFlAgELBTALBglghkgBZQIBCwkw CwYJYIZIAWUCAQsKMAsGCWCGSAFlAgELEjALBglghkgBZQIBCxMwCwYJYIZIAWUCAQsUMAwGCmCG SAFlAwIBAwYwDAYKYIZIAWUDAgEDBzAMBgpghkgBZQMCAQMIMAwGCmCGSAFlAwIBAw0wDAYKYIZI AWUDAgEDETA/BgNVHR8EODA2MDSgMqAwhi5odHRwOi8vY3JsLmRpc2EubWlsL2dldGNybD9Eb0Ql MjBSb290JTIwQ0ElMjAyMIH+BggrBgEFBQcBAQSB8TCB7jA/BggrBgEFBQcwAoYzaHR0cDovL2Ny bC5kaXNhLm1pbC9nZXRJc3N1ZWRUbz9Eb0QlMjBSb290JTIwQ0ElMjAyMCAGCCsGAQUFBzABhhRo dHRwOi8vb2NzcC5kaXNhLm1pbDCBiAYIKwYBBQUHMAKGfGxkYXA6Ly9jcmwuZ2RzLmRpc2EubWls L2NuJTNkRG9EJTIwUm9vdCUyMENBJTIwMiUyY291JTNkUEtJJTJjb3UlM2REb0QlMmNvJTNkVS5T LiUyMEdvdmVybm1lbnQlMmNjJTNkVVM/Y0FDZXJ0aWZpY2F0ZTtiaW5hcnkwDQYJKoZIhvcNAQEF BQADggEBAHIW3DlzY02T6Tccz7LtnNhN9wwySomes8q68wSscWYxpiq9un1U2C8JY0qICOhsE6Hs XntWFzAtyNLt141HRGnPEW/L2OdSdbVRyKodafAZHzDwB8c2vc4M3jt2/QrOy7YTutaFi/FcEpHK r+h/EqisLYvWdlCU7Db6ow/fxjLqx3NG/IQami/E6CccSMJGNvYX7O1nMg+4ouC30l6QBhOUIWFD bH3zO2tl7ePbqP/Fm7KS5+tf7u+/8zmMs/UX0obVw2xKOmw/nq/oWx02W6YmFUYLRmvH1ICq564c uCtO+iFyn1+fga+07lvJlymJfOnceOJO4HSf0oZ4ZqLHmKgxggMyMIIDLgIBATBkMF0xCzAJBgNV BAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0RvRDEMMAoGA1UECxMD UEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwgQ0EtMjQCAwzbMDAJBgUrDgMCGgUAoIIBozAYBgkqhkiG 9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjAyMDEyMTM3NDJaMCMGCSqGSIb3 DQEJBDEWBBSJ+Gx9mteAp1IcNC9OJtk+FfbhgTBYBgkqhkiG9w0BCQ8xSzBJMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjAKBggqhkiG 9w0CBTBzBgkrBgEEAYI3EAQxZjBkMF0xCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVy bm1lbnQxDDAKBgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwgQ0Et MjQCAwzbMzB1BgsqhkiG9w0BCRACCzFmoGQwXTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g R292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxGDAWBgNVBAMTD0RPRCBFTUFJ TCBDQS0yNAIDDNszMA0GCSqGSIb3DQEBAQUABIIBAGxdzZ9iU+Vx4vcgmCoSCugkN9xRMzIbyCtb in5nDAaZDwOuGV838Jx9R1Ry66+fEckKrt0YNM4KPLmk2CvM6EZV3f620rFcik8ARKbP7ygEnEiy IFaccCiXjcEwGAUkNz//yRoP79XHXDNZZ4F4IP3k0raXh/KUZ+zWAPGV7DPmeWaui/4fHxEzM/Xn dvrBZYFU9Xak/LjKj48GfiuoJKfL/hSWVFbG3mJlm3vZJZdc0bD+LuStNAe7orv+UW2IO+K09dbO 9mDB34s3BWYwYeDe8hkI79uu4R8XiQoYzZUE4ibkS8ca8xTj3N+fZ6DOUSNcmJDxImougQpR3PM2 aNgAAAAAAAA= ------=_NextPart_000_00F6_01CCE0FF.D1523610-- From james.huy.nguyen@gmail.com Thu Feb 2 06:15:01 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66B4021F8684 for ; Thu, 2 Feb 2012 06:15:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.122 X-Spam-Level: X-Spam-Status: No, score=-3.122 tagged_above=-999 required=5 tests=[AWL=-0.124, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_41=0.6, RCVD_IN_DNSWL_LOW=-1] 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 WuvvP-9rz492 for ; Thu, 2 Feb 2012 06:15:00 -0800 (PST) Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0FF3921F8655 for ; Thu, 2 Feb 2012 06:14:59 -0800 (PST) Received: by yhkk25 with SMTP id k25so1271297yhk.31 for ; Thu, 02 Feb 2012 06:14:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zqZeF+PvwSwv0AqhMqqfmdHeTgVyfu3oWRXWEtkS1Ow=; b=Y9ENKbAgAaSTcarTFYwhRmhcXI65f88J0CJuHaRUW1XLD8c0j9BgAAskQogXRlTH+d hSC6WaSRHTC1BSVvvGtvhtuGF1MCf3hvajmw9mMHR3h0bL0SoBXZZVdrQP2+4v7FUmzc zOiDSm+i2OtKFtWgW+ch1spE/IELn7uHZWhcM= MIME-Version: 1.0 Received: by 10.236.123.47 with SMTP id u35mr4281191yhh.115.1328192099604; Thu, 02 Feb 2012 06:14:59 -0800 (PST) Received: by 10.100.174.11 with HTTP; Thu, 2 Feb 2012 06:14:59 -0800 (PST) In-Reply-To: References: Date: Thu, 2 Feb 2012 09:14:59 -0500 Message-ID: From: James Nguyen To: Ulrich Herberg Content-Type: multipart/alternative; boundary=20cf301b685f4a5a3204b7fbd20a Cc: manet@ietf.org Subject: Re: [manet] API for NHDP X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2012 14:15:01 -0000 --20cf301b685f4a5a3204b7fbd20a Content-Type: text/plain; charset=UTF-8 Ulrich , I'm still digesting your thesis. So far, it's great. As of IETF's March conference, I won't be able to make it this time. I'm looking forward to the next IETF event. I'm working on NHDP-MIB development first. SMF-MIB and OLSRv2-MIB are next in line. My implementation will be based SNMP4J or NET-SNMP framework. I think it would be nice if there is a common interface that allows applications to interface with these protocols. That way, we don't have to maintain multiple codes of interfaces for every protocol. Moreover, this common interface should be language-independent. James On Tue, Jan 31, 2012 at 1:43 PM, Ulrich Herberg wrote: > P.S. I meant RFC5444, not RFC5449 in my previous email. > > Ulrich > > > On Tue, Jan 31, 2012 at 10:26 AM, Ulrich Herberg wrote: > >> James, >> >> actually, I am not a coauthor of NHDP, but of the NHDP-MIB document :-) I >> am not aware of how many implementations exist. I have myself implemented >> one in Java for my previous employer (Ecole Polytechnique), but it is not >> open-source. >> I know of a few corporate, closed-source implementations. As for >> open-source, there is the one from NRL (which I have tested and which works >> fine). There is also one from olsr.org, but I don't know the status of >> the implementation (but I think the basic functionality works fine, it was >> also tested during the interop event). >> >> Have a look at the proceedings of http://interop.thomasclausen.org >> During these interop events, a number of different RFC5449 and NHDP >> implementations have been tested. You can also find a description of the >> tests at http://herberg.name/downloads/pubs/thesis.pdf >> >> Will you come to the Paris IETF? There is always a slot at the end of the >> MANET WG session with updates about implementations. In my opinion, it >> would be very interesting to hear about your NHDP and in particular your >> NHDP-MIB implementation. >> >> >> Regards >> Ulrich >> >> >> On Tue, Jan 31, 2012 at 10:09 AM, James Nguyen < >> james.huy.nguyen@gmail.com> wrote: >> >>> Ulrich, >>> >>> I can see you're the co-author of NHDP. :) Do you know how many NHDP >>> implementations there are beside Naval Research Laboratory's NHDP that was >>> written in C++? >>> >>> I'm planning to have the SNMP implementation open source. >>> >>> James >>> >>> >>> On Tue, Jan 31, 2012 at 12:14 PM, Ulrich Herberg wrote: >>> >>>> James, >>>> >>>> as for the interface towards SNMP, you can use the MIB that is included >>>> in >>>> http://tools.ietf.org/html/draft-ietf-manet-nhdp-mib >>>> >>>> There are tools that create C++/Java/etc. code from a MIB. The back-end >>>> itself (between the MIB code and NHDP) has to be implemented manually. >>>> >>>> We are very interested in MIB implementations and experiences with it, >>>> so when you have completed the implementation, please notify us on the >>>> MANET list. Is this implementation planned to be open source? >>>> >>>> Hope that helps >>>> Ulrich >>>> >>>> >>>> On Tue, Jan 31, 2012 at 6:02 AM, James Nguyen < >>>> james.huy.nguyen@gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I'm working on implementing SNMP capabilities for NHDP. I'm just >>>>> wondering if there is an API that allows application to interface with NHDP. >>>>> >>>>> -- >>>>> James Nguyen >>>>> Email: james.huy.nguyen@gmail.com >>>>> >>>>> _______________________________________________ >>>>> manet mailing list >>>>> manet@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/manet >>>>> >>>>> >>>> >>> >>> >>> -- >>> James Nguyen >>> Email: james.huy.nguyen@gmail.com >>> >> >> > -- James Nguyen Email: james.huy.nguyen@gmail.com --20cf301b685f4a5a3204b7fbd20a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ulrich ,

I'm still digesting your thesis. =C2=A0So f= ar, it's great. =C2=A0As of IETF's March conference, I won't be= able to make it this time. =C2=A0I'm looking forward to the next IETF = event. =C2=A0

I'm working on NHDP-MIB development first. =C2=A0SM= F-MIB and OLSRv2-MIB are next in line. =C2=A0My implementation will be base= d SNMP4J or NET-SNMP framework. =C2=A0I think it would be nice if there is = a common interface that allows applications to interface with these protoco= ls. =C2=A0That way, we don't have to maintain multiple codes of interfa= ces for every protocol. =C2=A0Moreover, this common interface should be lan= guage-independent.

James

On Tue, = Jan 31, 2012 at 1:43 PM, Ulrich Herberg <ulrich@herberg.name> wrote:
P.S. I meant RFC5444, not RFC5449 in my previous email.

Ulrich


On Tue= , Jan 31, 2012 at 10:26 AM, Ulrich Herberg <ulrich@herberg.name><= /span> wrote:
James,

actually, I am not a coauthor = of NHDP, but of the NHDP-MIB document :-) I am not aware of how many implem= entations exist. I have myself implemented one in Java for my previous empl= oyer (Ecole Polytechnique), but it is not open-source.
I know of a few corporate, closed-source implementations. As for open-sourc= e, there is the one from NRL (which I have tested and which works fine). Th= ere is also one from olsr.org= , but I don't know the status of the implementation (but I think th= e basic functionality works fine, it was also tested during the interop eve= nt).

Have a look at the proceedings of http://interop.thomasclausen.org
During th= ese interop events, a number of different RFC5449 and NHDP implementations = have been tested. You can also find a description of the tests at http:/= /herberg.name/downloads/pubs/thesis.pdf

Will you come to the Paris IETF? There is always a slot at the end of t= he MANET WG session with updates about implementations. In my opinion, it w= ould be very interesting to hear about your NHDP and in particular your NHD= P-MIB implementation.


Regards
Ulrich
<= div>

On Tue, Jan 31, 2012 at 10:09 AM, Ja= mes Nguyen <james.huy.nguyen@gmail.com> wrote:
Ulrich,

I can see you'= ;re the co-author of NHDP. =C2=A0:) =C2=A0Do you know how many NHDP impleme= ntations there are beside Naval Research Laboratory's NHDP that was wri= tten in C++?

I'm planning to have the SNMP implementation open source. =C2=A0<= font color=3D"#888888">

James


On Tue, Jan 31, 2012 at 12:14 PM, Ulrich Herberg <ul= rich@herberg.name> wrote:
James,

as for the interface towards S= NMP, you can use the MIB that is included in
http://tools.ietf.o= rg/html/draft-ietf-manet-nhdp-mib

There are tools that create C++/Java/etc. code from a MIB. The back-end= itself (between the MIB code and NHDP) has to be implemented manually.

We are very interested in MIB implementations and experiences with it, = so when you have completed the implementation, please notify us on the MANE= T list. Is this implementation planned to be open source?

Hope that = helps
Ulrich


On Tue, Jan 31, 2012= at 6:02 AM, James Nguyen <james.huy.nguyen@gmail.com> wrote:
Hi,

I'm working on implementing SNMP capabilities fo= r NHDP. =C2=A0I'm just wondering if there is an API that allows applica= tion to interface with NHDP.

--
James Nguyen
Email: jame= s.huy.nguyen@gmail.com

_______________________________________________
manet mailing list
manet@ietf.org
h= ttps://www.ietf.org/mailman/listinfo/manet





--
James Nguyen=
Email: = james.huy.nguyen@gmail.com





--
= James Nguyen
Email: james.= huy.nguyen@gmail.com
--20cf301b685f4a5a3204b7fbd20a-- From sarwar_sarwar123@yahoo.com Thu Feb 2 07:32:53 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEE1E21F858A for ; Thu, 2 Feb 2012 07:32:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.947 X-Spam-Level: **** X-Spam-Status: No, score=4.947 tagged_above=-999 required=5 tests=[AWL=-1.250, BAYES_99=3.5, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.619, SUBJ_ALL_CAPS=2.077] 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 Ic1pBVeElzdL for ; Thu, 2 Feb 2012 07:32:53 -0800 (PST) Received: from nm7-vm0.bullet.mail.sp2.yahoo.com (nm7-vm0.bullet.mail.sp2.yahoo.com [98.139.91.192]) by ietfa.amsl.com (Postfix) with SMTP id 637FE21F8585 for ; Thu, 2 Feb 2012 07:32:53 -0800 (PST) Received: from [98.139.91.65] by nm7.bullet.mail.sp2.yahoo.com with NNFMP; 02 Feb 2012 15:32:50 -0000 Received: from [98.139.91.31] by tm5.bullet.mail.sp2.yahoo.com with NNFMP; 02 Feb 2012 15:32:50 -0000 Received: from [127.0.0.1] by omp1031.mail.sp2.yahoo.com with NNFMP; 02 Feb 2012 15:32:50 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 847217.94738.bm@omp1031.mail.sp2.yahoo.com Received: (qmail 14684 invoked by uid 60001); 2 Feb 2012 15:32:50 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1328196770; bh=TB/V8j/RTYdD8QFJylz0ZdNibOL5rraQgIIsI6gX8P4=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=KzfZpSuuBZi6JjQecIbNh3W2DhpdT6TTFJxB5Tu3XVa5eTSqz3/3OfNOwpH3yz2BgLJGO58eDi/fZH98KT4woXX+bEFswHMicx+EENNKhwvPbN7bGNjZ1ceQNWDTxyHye3roGBtEVLOvdL6pMJdRaGZt/W2r000N/f8giXPKhus= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=4OzqbgauXDysmhC6p2LhEI/9F6F/6K3yvdXK9qps3odh8altCzAQrDQ3z1YA10toJynXIGXY3MK9aM7xSstlyakPkgIRCic7UefI37BQeiSistWWZJnft7BCEPxoo/grCrkrDi4FQcA7xaTo2lCAUz5Ox8MY4SHeJMbFV+BzmeA=; X-YMail-OSG: olvQJREVM1nIN7IF7b2bd0ryA4vBlhbJ7rhbKZhBgPSNYsD HUR5Ha.9PbdVCuW7abgMHrLjXS8QjuNYTU_XPyfJG2JOr5N6g.S6.oajulN9 cF8SxY8cw1zG2eV0KUbb.YA_qljWVKpcnfketdPTD6lVOyc7ZKzryusmh7Eg 4dNwT5gr9CaGo3E4NFSWUE2L96hptzF679gMFA1xkva_ZD.HvONWmNQ6zfzp lSt1Z5ENHCwiFo_lSz1mRTKlWjlQiXwnrlXHPo1M.fADgaOihnWOVOGyJzJf or6.KRR2085iVku91S.8n9wJuXjgpQxo.8V_9mHUu.9pFZ25MxvWd46AX1k1 dHkebIh7crrU7Y5xoGo_XJF.xxTekvGtCgp_3vJWoC5u1dUq9XKsVlvKYOtS FI1pQX2Ruxc6j6VbtcWVNCfljXtXb2r1Cz4ErgS5ao9xbxvuQoyzuUtx4pAB .bm0- Received: from [182.177.192.192] by web44914.mail.sp1.yahoo.com via HTTP; Thu, 02 Feb 2012 07:32:50 PST X-Mailer: YahooMailWebService/0.8.116.331537 References: <1328080175.11780.YahooMailNeo@web44914.mail.sp1.yahoo.com> <1328081151.27832.YahooMailNeo@web44911.mail.sp1.yahoo.com> Message-ID: <1328196770.30538.YahooMailNeo@web44914.mail.sp1.yahoo.com> Date: Thu, 2 Feb 2012 07:32:50 -0800 (PST) From: SARWAR SARWAR To: "manet@ietf.org" In-Reply-To: <1328081151.27832.YahooMailNeo@web44911.mail.sp1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="347546587-2122171202-1328196770=:30538" Subject: [manet] AODV-UU MAKE ERROR X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: SARWAR SARWAR List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2012 15:32:53 -0000 --347546587-2122171202-1328196770=:30538 Content-Type: text/plain; charset=us-ascii hello i am trying to patch the AODV-UU in ns-2.32 after make command i am getting an error g++: aodv-uu/libaodv-uu.o: No such file or directory make: *** [ns] Error 1 can anyone solve it thanks in advance --347546587-2122171202-1328196770=:30538 Content-Type: text/html; charset=us-ascii
hello

i am trying to patch the AODV-UU in ns-2.32

after make command i am getting an error

g++: aodv-uu/libaodv-uu.o: No such file or directory

make: *** [ns] Error 1

can anyone solve it
thanks in advance





--347546587-2122171202-1328196770=:30538-- From valerio.arnaboldi@iit.cnr.it Fri Feb 3 05:23:34 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1ED21F8642 for ; Fri, 3 Feb 2012 05:23:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.28 X-Spam-Level: * X-Spam-Status: No, score=1.28 tagged_above=-999 required=5 tests=[AWL=1.999, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] 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 mLpkZMMvKJ9o for ; Fri, 3 Feb 2012 05:23:34 -0800 (PST) Received: from irina.iit.cnr.it (irina-lan.iit.cnr.it [146.48.96.79]) by ietfa.amsl.com (Postfix) with ESMTP id 3F7B221F84E2 for ; Fri, 3 Feb 2012 05:23:33 -0800 (PST) Received: by irina.iit.cnr.it (Postfix, from userid 1001) id 8AA253D8044; Fri, 3 Feb 2012 14:23:01 +0100 (CET) Date: Fri, 03 Feb 2012 14:23:01 +0100 From: Valerio Arnaboldi To: manet@ietf.org Message-ID: <4f2bdfb5.LuXtkgoOHxOTpmRU%valerio.arnaboldi@iit.cnr.it> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: application/octet-stream Content-Transfer-Encoding: 8bit Subject: [manet] [ACM MobiOpp'12] Call For Participation X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2012 13:23:34 -0000 ------------------------------------------------------------------------------ ACM MobiOpp 2012 Third International Workshop on Mobile Opportunistic Networks http://www.cl.cam.ac.uk/conference/mobiopp2012/ sponsored by ACM SIGMOBILE Technically co-sponsored by the IFIP TC6 WG 6.3 March 15-16, 2012 ETH Zuerich, Switzerland ------------------------------------------------------------------------------ We are pleased to announce that the registration for ACM MobiOpp'12 is now open at: http://www.cl.cam.ac.uk/conference/mobiopp2012/registration.html Early registration is until **February 10th, 2012**. About accommodation: You'll find information about accommodation at: http://www.cl.cam.ac.uk/conference/mobiopp2012/hotel.html MobiOpp'12 program: The program for papers is also online at: http://www.cl.cam.ac.uk/conference/mobiopp2012/program.html The selection was quite tough: only 9 papers out of 27 submissions were selected, 4 posters out of 10 and 5 demos out of 7 submissions. MobiOpp'12 highlights: - The workshop will feature two keynote talks from Matthias Grossglauser and Jörg Ott entitled "Random Graph Models for Wireless and Social Networks" and "404 Not Found? A Quest for DTN Applications", respectively. - Our sponsor, Disney Research Zürich, will offer special gifts for this venue. - And last but not least, the social event will feature a Tour around Zürich in an old-timer tram that will pick us up at ETH and leave us 2 hours later at the restaurant "Le Dézaley" (http://le-dezaley.ch/) for typical Swiss dishes. We are looking forward to seeing you in Zürich, ============================================== Valerio Arnaboldi - MOBIOPP2012 Publicity Chair Institute for Informatics and Telematics (IIT) Italian National Research Council (CNR) Via G. Moruzzi, 1 - 56124 Pisa, Italy phone: +39 050 315 2195 email: valerio.arnaboldi@iit.cnr.it From internet-drafts@ietf.org Mon Feb 6 09:27:03 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DE6D21F86E0; Mon, 6 Feb 2012 09:27:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.554 X-Spam-Level: X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 K3siJ+z2Ogey; Mon, 6 Feb 2012 09:27:02 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA67F21F86A6; Mon, 6 Feb 2012 09:27:02 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.64p1 Message-ID: <20120206172702.17407.84364.idtracker@ietfa.amsl.com> Date: Mon, 06 Feb 2012 09:27:02 -0800 Cc: manet@ietf.org Subject: [manet] I-D Action: draft-ietf-manet-dlep-02.txt X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2012 17:27:03 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Mobile Ad-hoc Networks Working Group = of the IETF. Title : Dynamic Link Exchange Protocol (DLEP) Author(s) : Stan Ratliff Bo Berry Greg Harrison Darryl Satterwhite Shawn Jury Filename : draft-ietf-manet-dlep-02.txt Pages : 52 Date : 2012-02-06 When routing devices rely on modems to effect communications over wireless links, they need timely and accurate knowledge of the characteristics of the link (speed, state, etc.) in order to make forwarding decisions. In mobile or other environments where these characteristics change frequently, manual configurations or the inference of state through routing or transport protocols does not allow the router to make the best decisions. A bidirectional, event- driven communication channel between the router and the modem is necessary. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-manet-dlep-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-manet-dlep-02.txt From prvs=03876d3570=npowell@harris.com Fri Feb 10 05:33:08 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1BE421F8483 for ; Fri, 10 Feb 2012 05:33:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 roSZCIUMnT-H for ; Fri, 10 Feb 2012 05:33:08 -0800 (PST) Received: from mlbefw1.harris.com (mlbefw1.harris.com [192.52.233.75]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5C521F869F for ; Fri, 10 Feb 2012 05:33:07 -0800 (PST) From: "Powell lll, Nelson" To: "manet@ietf.org" Thread-Topic: DLEP Draft 2 - inclusion of subnet masks Thread-Index: Aczn+IJC1Y4RBWl7R/K+QDT6CNLTNQ== Date: Fri, 10 Feb 2012 13:33:03 +0000 Message-ID: <13044204616BFB43BC7F6B4EC6B015122066C9D0@ROCMXUS20.cs.myharris.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_13044204616BFB43BC7F6B4EC6B015122066C9D0ROCMXUS20csmyha_" MIME-Version: 1.0 Received-SPF: none Subject: [manet] DLEP Draft 2 - inclusion of subnet masks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2012 13:33:09 -0000 --_000_13044204616BFB43BC7F6B4EC6B015122066C9D0ROCMXUS20csmyha_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Stan, We at Harris would like to know if it would be possible to include a su= bnet mask in the Address TLV's or use the Addressing TLV's as a Prefix. We = have some edge devices that exist as a subnet and it would be easier for us= to deliver the information to the router as a subnet rather than each indi= vidual point. - Nelson Nelson H. Powell III Harris RF Communications Principal Engineer 585-242-3719 --_000_13044204616BFB43BC7F6B4EC6B015122066C9D0ROCMXUS20csmyha_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Stan,

    We at Harris would like to know i= f it would be possible to include a subnet mask in the Address TLV’s = or use the Addressing TLV’s as a Prefix. We have some edge devices th= at exist as a subnet and it would be easier for us to deliver the information to the router as a subnet rather than each individual poin= t.

 

- Nelson

 

Nelson H. Powell III

Harris RF Communications

Principal Engineer

585-242-3719

 

--_000_13044204616BFB43BC7F6B4EC6B015122066C9D0ROCMXUS20csmyha_-- From sratliff@cisco.com Fri Feb 10 06:36:22 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB82921F876D for ; Fri, 10 Feb 2012 06:36:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.449 X-Spam-Level: X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 wTCaKLZ7S8Ve for ; Fri, 10 Feb 2012 06:36:22 -0800 (PST) Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 1891621F8769 for ; Fri, 10 Feb 2012 06:36:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4886; q=dns/txt; s=iport; t=1328884582; x=1330094182; h=cc:message-id:from:to:in-reply-to:mime-version:subject: date:references; bh=MtIJ10RD8n0WFDTNFzl+mklrghyanMjrauBo4q5R/bI=; b=SqObOFLzJ3y9PXgbzIYCo4vKjvATFcSeqXatwkr92DA6vGTV0f13MxyB kH5zxHXbojLbfHO1NWp7E97J/1LTXUij2mxm7tW4Kl6AjLgllM7oJUjqL d2KbLf5hDIC9IwqsezvIVLotJNuo90jVECR8o82RWV9QflisN4bqC3xfN w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EALUnNU+tJV2Y/2dsb2JhbABBA4JNrQ+BB4FyAQEBAwEBAQEPAVsLBQsLRicwBhMih1oJmk4BnmAEiz0VEgUEGAQHHwYUAQMVgxgFBgkFCw1wIYI/YwSISYxnkwI X-IronPort-AV: E=Sophos;i="4.73,395,1325462400"; d="scan'208,217";a="55318342" Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-9.cisco.com with ESMTP; 10 Feb 2012 14:36:21 +0000 Received: from rtp-sratliff-8712.cisco.com (rtp-sratliff-8712.cisco.com [10.116.179.211]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q1AEaKcj028085; Fri, 10 Feb 2012 14:36:21 GMT Message-Id: <9F1C1EB9-3A61-4022-B77A-55AB22C74B2A@cisco.com> From: Stan Ratliff To: "Powell lll, Nelson" In-Reply-To: <13044204616BFB43BC7F6B4EC6B015122066C9D0@ROCMXUS20.cs.myharris.net> Content-Type: multipart/alternative; boundary=Apple-Mail-41-537550260 Mime-Version: 1.0 (Apple Message framework v936) Date: Fri, 10 Feb 2012 09:36:24 -0500 References: <13044204616BFB43BC7F6B4EC6B015122066C9D0@ROCMXUS20.cs.myharris.net> X-Mailer: Apple Mail (2.936) Cc: "manet@ietf.org" Subject: Re: [manet] DLEP Draft 2 - inclusion of subnet masks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2012 14:36:23 -0000 --Apple-Mail-41-537550260 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Nelson, Yes, I think that could be done. My co-authors and I will work =20 something up for an 03 version of DLEP. Regards, Stan On Feb 10, 2012, at 8:33 AM, Powell lll, Nelson wrote: > Stan, > We at Harris would like to know if it would be possible to =20 > include a subnet mask in the Address TLV=92s or use the Addressing =20 > TLV=92s as a Prefix. We have some edge devices that exist as a subnet =20= > and it would be easier for us to deliver the information to the =20 > router as a subnet rather than each individual point. > > - Nelson > > Nelson H. Powell III > Harris RF Communications > Principal Engineer > 585-242-3719 > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www.ietf.org/mailman/listinfo/manet --Apple-Mail-41-537550260 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable
Stan,
    We at Harris would like to know if it = would be possible to include a subnet mask in the Address TLV=92s or use = the Addressing TLV=92s as a Prefix. We have some edge devices that exist = as a subnet and it would be easier for us to deliver the information to = the router as a subnet rather than each individual = point.
 
- = Nelson
 
Nelson H. Powell = III
Harris RF = Communications
Principal = Engineer
585-242-3719
 
___________________________________________= ____
manet mailing list
To: "manet@ietf.org" Date: Fri, 10 Feb 2012 13:19:49 -0500 Thread-Topic: R2RI Framework and Requirements Thread-Index: AczoIJR4m04ho3GMT+uhB4jsRids5g== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.12.0.110505 acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_CB5AC9F5C072bchengllmitedu_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7361, 1.0.260, 0.0.0000 definitions=2012-02-10_07:2012-02-10, 2012-02-10, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1202100167 Subject: [manet] R2RI Framework and Requirements X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2012 18:20:04 -0000 --_000_CB5AC9F5C072bchengllmitedu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, Back in Sept and November 2011, there was some discussion on the list of po= tentially authoring some framework to help discuss and evaluate radio-to-ro= uter interface (R2RI) protocol technology (such as DLEP). We've put together a start on that framework for consideration for adoption= by the MANET WG and would love your feedback. A new version of I-D, draft-bcheng-r2ri-framework-00.txt has been successfu= lly submitted by Bow-Nan Cheng and posted to the IETF repository. Filename: draft-bcheng-r2ri-framework Revision: 00 Title: Radio to Router Interface Framework and Requirements Creation date: 2012-02-13 WG ID: Individual Submission Number of pages: 14 Abstract: In highly dynamic, heterogeneous radio MANET environments where links are constantly changing, standardizing information exchange between the radio and router such that routers can make informed routing decision based on link layer information over heterogeneous link types becomes a key area to address. This document defines the basic framework for radio-to-router interface communications as well as requirements and considerations for evaluating radio-to-router interface technologies for use in MANETs. https://datatracker.ietf.org/doc/draft-bcheng-r2ri-framework/?include_text= =3D1 -Bow-Nan --_000_CB5AC9F5C072bchengllmitedu_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi all,
<= div>
Back in Sept and November 2011, there was some discussio= n on the list of potentially authoring some framework to help discuss and e= valuate radio-to-router interface (R2RI) protocol technology (such as DLEP)= . 

We've put together a start on that framewo= rk for consideration for adoption by the MANET WG and would love your feedb= ack.

A new version of I-D, draft-bcheng-r2ri-framework-00.txt has b= een successfully submitted by Bow-Nan Cheng and posted to the IETF reposito= ry.

Filename:  draft-b= cheng-r2ri-framework
Revision:Title: = =  Radio to Router Interface Framework and Requirements
 --_000_CB5AC9F5C072bchengllmitedu_-- From L.Wood@surrey.ac.uk Fri Feb 10 14:44:02 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04D7621F84EF for ; Fri, 10 Feb 2012 14:44:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.223 X-Spam-Level: X-Spam-Status: No, score=-3.223 tagged_above=-999 required=5 tests=[AWL=-0.375, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_OBFU_ALL=0.751, UNPARSEABLE_RELAY=0.001] 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 DBCwhzWh-CyL for ; Fri, 10 Feb 2012 14:43:59 -0800 (PST) Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.98]) by ietfa.amsl.com (Postfix) with ESMTP id 70CF521F84EB for ; Fri, 10 Feb 2012 14:43:56 -0800 (PST) Received: from [193.109.255.147:47802] by server-6.bemta-14.messagelabs.com id 43/84-05782-BAD953F4; Fri, 10 Feb 2012 22:43:55 +0000 X-Env-Sender: L.Wood@surrey.ac.uk X-Msg-Ref: server-11.tower-72.messagelabs.com!1328913834!72702615!1 X-Originating-IP: [131.227.200.43] X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20804 invoked from network); 10 Feb 2012 22:43:54 -0000 Received: from unknown (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-11.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 10 Feb 2012 22:43:54 -0000 Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.208]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Fri, 10 Feb 2012 22:43:55 +0000 From: To: , Date: Fri, 10 Feb 2012 22:43:54 +0000 Thread-Topic: R2RI Framework and Requirements Thread-Index: AczoIJR4m04ho3GMT+uhB4jsRids5gAJB0J2 Message-ID: References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [manet] R2RI Framework and Requirements X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2012 22:44:02 -0000 Router-smart-modem interface technology isn't only applicable to MANETs - c= onsider DVB-S2 ACM/VCM deployed on satellite links, or how varying ADSL can= support the networks behind it as rate change and QoS get reconfigured. Some more general thoughts on this are in the documents at: http://personal.ee.surrey.ac.uk/Personal/L.Wood/router-modem-integration/ Lloyd Wood http://sat-net.com/L.Wood/ ________________________________________ From: manet-bounces@ietf.org [manet-bounces@ietf.org] On Behalf Of Cheng, B= ow-Nan - 0665 - MITLL [bcheng@ll.mit.edu] Sent: 10 February 2012 18:19 To: manet@ietf.org Subject: [manet] R2RI Framework and Requirements Hi all, Back in Sept and November 2011, there was some discussion on the list of po= tentially authoring some framework to help discuss and evaluate radio-to-ro= uter interface (R2RI) protocol technology (such as DLEP). We've put together a start on that framework for consideration for adoption= by the MANET WG and would love your feedback. A new version of I-D, draft-bcheng-r2ri-framework-00.txt has been successfu= lly submitted by Bow-Nan Cheng and posted to the IETF repository. Filename: draft-bcheng-r2ri-framework Revision: 00 Title: Radio to Router Interface Framework and Requirements Creation date: 2012-02-13 WG ID: Individual Submission Number of pages: 14 Abstract: In highly dynamic, heterogeneous radio MANET environments where links are constantly changing, standardizing information exchange between the radio and router such that routers can make informed routing decision based on link layer information over heterogeneous link types becomes a key area to address. This document defines the basic framework for radio-to-router interface communications as well as requirements and considerations for evaluating radio-to-router interface technologies for use in MANETs. https://datatracker.ietf.org/doc/draft-bcheng-r2ri-framework/?include_text= =3D1 -Bow-Nan From dbeach@cisco.com Sun Feb 12 16:17:30 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F29E21F8616 for ; Sun, 12 Feb 2012 16:17:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 nN4uXvCcDl09 for ; Sun, 12 Feb 2012 16:17:29 -0800 (PST) Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 4344E21F8610 for ; Sun, 12 Feb 2012 16:17:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dbeach@cisco.com; l=1287; q=dns/txt; s=iport; t=1329092249; x=1330301849; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=qBz+CiFeNUQl8znhkqpv8lXsuN3h8se/6aO1/zXmgJA=; b=GOQlUWTUDvYj789livmJoVYkbKKgieKNf5uzTYupZepVWvD2tdSidUPn twNyI3+x64wvoOIbJDFPhVHfwhg01VvS2dPwwU8Ntxl/PNw/1dZuxEpSF CzOplys4lGLIuGFfl2zUI7ZAJ7vgHLSv872D2ICOhuXVexhxrqZVlyvQj M=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAGhVOE+tJV2Y/2dsb2JhbABDr3aBB4F0AQQSAR0KUQEqBhgHVwEEGxqgXoEnAZ1Eiz8PGgkDAwcEBzcEKYQzASuCOmMEiEqfaw X-IronPort-AV: E=Sophos;i="4.73,409,1325462400"; d="scan'208";a="58323294" Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 13 Feb 2012 00:17:28 +0000 Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q1D0HSg0016799 for ; Mon, 13 Feb 2012 00:17:28 GMT Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 12 Feb 2012 18:17:28 -0600 X-Mimeole: Produced By Microsoft Exchange V6.5 x-cr-hashedpuzzle: BSiz BjSF CLkr CTNW Cnrm D6Il EBM0 FQ0U FgnY F9G6 GKr3 HrFG JoNn K13F LJ5g LyvC; 1; bQBhAG4AZQB0AEAAaQBlAHQAZgAuAG8AcgBnAA==; Sosha1_v1; 7; {E36955FC-7CFE-4033-ACD3-7D8E23FEB5AE}; ZABiAGUAYQBjAGgAQABjAGkAcwBjAG8ALgBjAG8AbQA=; Mon, 13 Feb 2012 00:17:21 GMT; UgAyAFIASQAgAEYAcgBhAG0AZQB3AG8AcgBrACAAYQBuAGQAIABSAGUAcQB1AGkAcgBlAG0AZQBuAHQAcwA= MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable x-cr-puzzleid: {E36955FC-7CFE-4033-ACD3-7D8E23FEB5AE} Content-class: urn:content-classes:message Date: Sun, 12 Feb 2012 18:17:21 -0600 Message-ID: <507C43E627B1F74981DE460240FEE21706B60443@XMB-RCD-109.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: R2RI Framework and Requirements Thread-Index: Aczp5Np02N0I0/FORZKdcZUy2rzVDQ== From: "Darrel Beach (dbeach)" To: X-OriginalArrivalTime: 13 Feb 2012 00:17:28.0718 (UTC) FILETIME=[DED46AE0:01CCE9E4] Subject: [manet] R2RI Framework and Requirements X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 00:17:30 -0000 To add an additional thought...... I believe that the context of the Radio to Router information exchange over an Ethernet is actually applicable across another segment. Traditionally we've used=20 routers with integrated interfaces for all the types underlying networks such as ISDN, Serial, Frame Relay, etc. By using a R2R framework it looks workable to have such interfaces which could now be separate from a router and have the interface to the router abstracted to occur over Ethernet. From a flexibility standpoint, and as an example,=20 I see no reason why an ISDN interface card from vendor A couldn't use the R2R framework where it could establish a connection over ISDN and signal the connection information over the Ethernet using R2R protocols. This could be extended across virtually any=20 connection type, including media or methods not normally seen. The Neighbor TLVs under discussion also provide an interesting mechanism for nonstandard connections=20 to easily advertise connected devices. One prime example is the bus technology such as 1553. It's unlikely to see 1553 interfaces integrated into routers, but it looks quite feasible to abstract such an interface to the R2R framework for the transmission of IP packets. /d From iesg-secretary@ietf.org Mon Feb 13 07:28:08 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6701D21F8584; Mon, 13 Feb 2012 07:28:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.476 X-Spam-Level: X-Spam-Status: No, score=-102.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 qXRC-ePo1ePR; Mon, 13 Feb 2012 07:28:07 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E0E121F855A; Mon, 13 Feb 2012 07:28:07 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 3.64p1 Message-ID: <20120213152807.2786.88641.idtracker@ietfa.amsl.com> Date: Mon, 13 Feb 2012 07:28:07 -0800 Cc: manet@ietf.org Subject: [manet] Last Call: (MANET Cryptographical Signature TLV Definition) to Proposed Standard X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ietf@ietf.org List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 15:28:08 -0000 The IESG has received a request from the Mobile Ad-hoc Networks WG (manet) to consider the following document: - 'MANET Cryptographical Signature TLV Definition' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2012-02-27. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document describes general and flexible TLVs (type-length-value structure) for representing cryptographic signatures as well as timestamps, using the generalized MANET packet/message format defined in RFC 5444. It defines two Packet TLVs, two Message TLVs, and two Address Block TLVs, for affixing cryptographic signatures and timestamps to a packet, message and address, respectively. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-manet-packetbb-sec/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-manet-packetbb-sec/ No IPR declarations have been submitted directly on this I-D. From iesg-secretary@ietf.org Mon Feb 13 07:28:55 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F49F21F866A; Mon, 13 Feb 2012 07:28:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.507 X-Spam-Level: X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 qccYcYHISmXQ; Mon, 13 Feb 2012 07:28:54 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09CD821F865E; Mon, 13 Feb 2012 07:28:54 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 3.64p1 Message-ID: <20120213152854.2495.21379.idtracker@ietfa.amsl.com> Date: Mon, 13 Feb 2012 07:28:54 -0800 Cc: manet@ietf.org Subject: [manet] Last Call: (Simplified Multicast Forwarding) to Experimental RFC X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ietf@ietf.org List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 15:28:55 -0000 The IESG has received a request from the Mobile Ad-hoc Networks WG (manet) to consider the following document: - 'Simplified Multicast Forwarding' as an Experimental RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2012-02-27. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document describes a Simplified Multicast Forwarding (SMF) mechanism that provides basic Internet Protocol (IP) multicast forwarding suitable for limited wireless mesh and mobile ad hoc network (MANET) use. It is mainly applicable in situations where efficient flooding represents an acceptable engineering design trade- off. It defines techniques for multicast duplicate packet detection (DPD), to be applied in the forwarding process, for both IPv4 and IPv6 protocol use. This document also specifies optional mechanisms for using reduced relay sets to achieve more efficient multicast data distribution within a mesh topology as compared to classic flooding. Interactions with other protocols, such as use of information provided by concurrently running unicast routing protocols, or interaction with other multicast protocols, as well as multiple deployment approaches are also described. Distributed algorithms for selecting reduced relay sets and related discussion are provided in the appendices. Basic issues relating to the operation of multicast MANET border routers are discussed, but ongoing work remains in this area, and is beyond the scope of this document. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-manet-smf/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-manet-smf/ No IPR declarations have been submitted directly on this I-D. From prvs=3390ccb243=bcheng@ll.mit.edu Mon Feb 13 07:57:17 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47ADE21F8661 for ; Mon, 13 Feb 2012 07:57:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001] 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 NM75kPf9u2u1 for ; Mon, 13 Feb 2012 07:57:16 -0800 (PST) Received: from mx2.ll.mit.edu (MX2.LL.MIT.EDU [129.55.12.46]) by ietfa.amsl.com (Postfix) with ESMTP id 625E521F8594 for ; Mon, 13 Feb 2012 07:57:16 -0800 (PST) Received: from LLE2K7-HUB01.mitll.ad.local (LLE2K7-HUB01.mitll.ad.local) by mx2.ll.mit.edu (unknown) with ESMTP id q1DFv82x016439 for ; Mon, 13 Feb 2012 10:57:08 -0500 From: "Cheng, Bow-Nan - 0665 - MITLL" To: "manet@ietf.org" Date: Mon, 13 Feb 2012 10:57:05 -0500 Thread-Topic: [manet] R2RI Framework and Requirements Thread-Index: AczqaCMsH/41FZrhR2mKFBvfgbVpXw== Message-ID: In-Reply-To: <507C43E627B1F74981DE460240FEE21706B60443@XMB-RCD-109.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.12.0.110505 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7361, 1.0.260, 0.0.0000 definitions=2012-02-13_03:2012-02-13, 2012-02-13, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1202130120 Subject: Re: [manet] R2RI Framework and Requirements X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 15:57:17 -0000 Thanks Darrel and Lloyd for your helpful comments. Indeed the concept of R2RI/R2M can be applied in many contexts to help throttle networks (and as you guys mentioned, have already been done to some extent). I'm wondering if its possible to de-scope the work for various applications. For example, in the MANET context, perhaps the role of the R2RI protocol is to simply 1) define the link layer (1 RF hop) information (a small subset) the radio/modem should provide to the multi-hop routing layer (MANET Routing), and 2) define the transport mechanism to get this to the router. How the router utilizes the link layer information (to make better multi-hop routing decisions, reduce link flapping, etc.) is probably a different problem and beyond the scope of R2RI. I guess what I'm wondering is if its possible to scope out R2RI in the MANET context as providing information about 1-hop neighbors to a multi-hop routing scheme.. Understanding that R2RI/R2M can be applied to throttling entire networks and also be used a virtual interface over Ethernet (which would be scoped as a different piece of work) -- Bow-Nan Cheng, Ph.D. MIT Lincoln Laboratory Airborne Networks Group 244 Wood St Lexington MA 02420 781-981-4997 On 2/12/12 7:17 PM, "Darrel Beach (dbeach)" wrote: >To add an additional thought...... >I believe that the context of the Radio to Router information exchange >over an >Ethernet is actually applicable across another segment. Traditionally >we've used=20 >routers with integrated interfaces for all the types underlying networks >such as >ISDN, Serial, Frame Relay, etc. By using a R2R framework it looks >workable to have >such interfaces which could now be separate from a router and have the >interface to the >router abstracted to occur over Ethernet. From a flexibility >standpoint, and as an example, >I see no reason why an ISDN interface card from vendor A couldn't use >the R2R framework >where it could establish a connection over ISDN and signal the >connection information >over the Ethernet using R2R protocols. This could be extended across >virtually any=20 >connection type, including media or methods not normally seen. The >Neighbor TLVs >under discussion also provide an interesting mechanism for nonstandard >connections=20 >to easily advertise connected devices. One prime example is the bus >technology such as 1553. >It's unlikely to see 1553 interfaces integrated into routers, but it >looks quite feasible to >abstract such an interface to the R2R framework for the transmission of >IP packets. > >/d >_______________________________________________ >manet mailing list >manet@ietf.org >https://www.ietf.org/mailman/listinfo/manet From fabio.pezzoni@iit.cnr.it Mon Feb 13 08:00:35 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5971521F8686 for ; Mon, 13 Feb 2012 08:00:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.5 X-Spam-Level: * X-Spam-Status: No, score=1.5 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599, FRT_ADULT2=1.474, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] 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 YB-334U+N7a0 for ; Mon, 13 Feb 2012 08:00:34 -0800 (PST) Received: from irina.iit.cnr.it (irina-lan.iit.cnr.it [146.48.96.79]) by ietfa.amsl.com (Postfix) with ESMTP id 6CC6921F8687 for ; Mon, 13 Feb 2012 08:00:32 -0800 (PST) Received: by irina.iit.cnr.it (Postfix, from userid 1000) id 6684E3D8094; Mon, 13 Feb 2012 17:00:01 +0100 (CET) Date: Mon, 13 Feb 2012 17:00:01 +0100 From: Fabio Pezzoni To: manet@ietf.org Message-ID: <4f393381.WjMsM470xAwogyfx%fabio.pezzoni@iit.cnr.it> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [manet] [IEEE AOC 2012] Call for Papers - Deadline fast approching X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 16:00:36 -0000 -------------------------------------------------------------------------------- CALL FOR PAPERS Sixth IEEE WoWMoM Workshop on Autonomic and Opportunistic Communications (AOC 2012) June 25, 2012 - San Francisco, California, USA http://cnd.iit.cnr.it/aoc2012/ jointly supported by the SCAMPI project funded by the FP7-ICT Programme under the Future Internet Research and Experimentation (FIRE) initiative http://www.ict-scampi.eu/ and RECOGNITION project funded by the FP7-ICT Programme under the Future and Emerging Technologies (FET) initiative http://www.recognition-project.eu/ Fast Track on Computer Communication Journal http://www.elsevier.com/locate/comcom **** Submission Deadline --- February 17, 2012 **** -------------------------------------------------------------------------------- The diffusion of lightweight, powerful portable devices, also enriched with a variety of sensing capabilities, is enabling new ways for users' communication, and laying the foundation for realizing the ubiquitous networking idea. Acting either as the main communication mode or as complement to existing mobile network infrastructures, opportunistic networking can leverage the mobility of end users and enhance their communication capabilities. The opportunistic exploitation of extemporary contacts among the users of the network paves the way to a number of applications but also poses new and challenging problems to the networking research community. The AOC 2012 workshop aims at serving as a meeting point for people working in the area and a forum for exchanging ideas, discussing solutions, and sharing experiences among researchers, professionals, and application developers, both from industry and academia. As with the previous five editions of the AOC workshop series, the scope of this year's workshop will remain on general issues related to opportunistic networking and computing. Yet, AOC 2012 will have a primary interest in new directions of opportunistic communications, such as service composition techniques, scenarios of co-existence with infrastructure networks, and insights to their operation coming from other disciplines such as game theory and cognitive psychology. The workshop will solicit original papers addressing theoretical and practical aspects of autonomic and opportunistic communications but also papers describing prototype implementations and deployments. Topics of interest for AOC 2012 include, but are not limited to: * Routing, transport, and reliability issues * Techniques for data dissemination and replication * Applications and middleware support, mobile social networking applications * Mobility models and statistical analysis of mobility traces * Context and social awareness mechanisms and algorithms * Co-existence of opportunistic networks with infrastructure mobile wireless networks * Service composition in autonomic and opportunistic networks * Cognition-driven information processing and decision making * Performance modelling, scaling laws, and fundamental limits for autonomic and opportunistic communications * Game-theoretic insights to the operation of autonomic and opportunistic networks * Participatory and urban sensing in autonomic and opportunistic networks * Trust, security, and reputation * Autonomic and opportunistic communication testbeds and prototypes, measurement data from real experiments * Socio-economic models for autonomic and opportunistic communications PAPER SUBMISSION AND PUBLICATION -------------------------------- Papers should neither have been published elsewhere nor being currently under review by another conference or journal. Manuscripts are limited to 6 pages, single spacing, double column, and must strictly adhere to the template format. Guidelines on paper submission and formatting are available at http://cnd.iit.cnr.it/aoc2012/. Accepted papers will appear in the symposium proceedings published by IEEE. At least one author of each accepted paper is required to register and present his/her work at the workshop. There will be no separate registration for workshop, but one single registration will cover both conference and workshops participation. Extended versions of workshop selected papers will be considered for possible fast track publication on the Computer Communications Journal (Elsevier). IMPORTANT DATES --------------- Full papers due: February 17, 2012 Notification: April 4, 2012 Workshop: June 25, 2012 ORGANIZING COMMITTEE -------------------- WORKSHOP Chairs Merkouris Karaliopoulos, University of Athens, Greece Chiara Boldrini, IIT-CNR, Italy STEERING Committee Marco Conti, IIT-CNR, Italy Silvia Giordano, SUPSI, Switzerland Ioannis Stavrakakis, University of Athens, Greece PUBLICITY Chairs Fabio Pezzoni, IIT-CNR, Italy Pushpendra Singh, IIIT Delhi, India PROGRAM COMMITTEE ------------------------------------ Gergely Acs, BUTE, Hungary Eleonora Borgia, IIT-CNR, Italy Jian-Nong Cao, Hong Kong Polytechnic University, HK Vania Conan, Thales, France Serge Fdida, UPMC, Paris VI, France Laura Galluccio, University of Catania, Italy Nidhi Hegde, Technicolor, France Tristan Henderson, University of St. Andrews, UK Gunnar Karlsson, KTH, Sweden Mohan Kumar, University of Texas at Arlington, USA Kyunghan Lee, North Carolina State University, USA Franck Legendre, ETH Zurich, Switzerland Daniele Miorandi, Create-net, Italy Refik Molva, Eurecom, France Valtteri Niemi, Nokia, Switzerland Katia Obraczka, University of California, Santa Cruz, USA Konstantinos Oikonomou, Ionian University, Greece Joerg Ott, HUT, Finland Elena Pagani, Universita' degli Studi di Milano, Italy Andrea Passarella, IIT-CNR, Italy Daniele Puccinelli, SUPSI, Switzerland Christian Rohner, Uppsala University, Sweden Fabrizio Sestini, EU Commission Abdullatif Shikfa, Alcatel Lucent Bell Labs, France Thrasyvoulos Spyropoulos, EURECOM, France Roger Whitaker, Cardiff University, UK Hongyi Wu, University of Louisiana at Lafayette, USA Eiko Yoneki, University of Cambridge, UK Franco Zambonelli, University of Modena-Reggio, Italy Xiaolan Zhang, Fordham University, USA From sratliff@cisco.com Mon Feb 13 08:44:12 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0A2A21F8699 for ; Mon, 13 Feb 2012 08:44:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.599 X-Spam-Level: X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 yQl7t9OwA0-T for ; Mon, 13 Feb 2012 08:44:10 -0800 (PST) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id C365E21F8508 for ; Mon, 13 Feb 2012 08:44:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sratliff@cisco.com; l=789; q=dns/txt; s=iport; t=1329151450; x=1330361050; h=message-id:from:to:content-transfer-encoding: mime-version:subject:date; bh=no67C14vZd2cNdK7pBjoDF6juc04BskxRWjm91mXFQs=; b=OYEqDkmkX6b+Fll5E/HvRYwWMQ7dP2RyHgdYWAoKhysENzq5iwqJMQF9 xvpaoXmT+eC5Ekj0gDICsPJ8A8cEVTKTiJqLwmYqGZ/093gm7rXFoiO8c zItj03q+EZj9Y2ezx1NSYBKxqwteXL9nE/JVYtB5XjH+HHcpj0mfHaHX1 s=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvwEAHs9OU+tJV2d/2dsb2JhbABDsAyBB4ILASUCgX01h2OZLoEnAZ5Wi2ABFQMCAQ4BBQQDBAsCDAYBBRQBAxIDAYMXBQZBBTmCd2MEiEqMaJMC X-IronPort-AV: E=Sophos;i="4.73,412,1325462400"; d="scan'208";a="58526335" Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 13 Feb 2012 16:44:09 +0000 Received: from dhcp-64-102-54-245.cisco.com (dhcp-64-102-54-245.cisco.com [64.102.54.245]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id q1DGi9lV005778 for ; Mon, 13 Feb 2012 16:44:09 GMT Message-Id: <077E83E0-B569-4A23-8546-16E26DED19F0@cisco.com> From: Stan Ratliff To: "manet@ietf.org IETF" Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 13 Feb 2012 11:44:14 -0500 X-Mailer: Apple Mail (2.936) Subject: [manet] Compliance with IETF IPR rules X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 16:44:12 -0000 All, There is a discussion currently underway concerning compliance with the rules on IPR within the IETF. As part of that discussion, Adrian Farrel (one of our Area Directors) and Pete Resnick have offered a draft outlining sanctions for IPR violations. It can be found at http://tools.ietf.org/html/draft-farrresnickel-ipr-sanctions-00 . Please note, this is *not* an approved RFC; as such, it outlines a point of view for the discussion going forward. However, it should highlight the concern within the IETF about timely disclosures of IPR issues - something that all of us need to be aware of. So please consider this as an FYI, and I recommend you give the draft a read, as well as BCP79, which is at http://tools.ietf.org/html/bcp79. Regards, Stan From budden@nps.edu Mon Feb 13 09:49:33 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D03B821F866D for ; Mon, 13 Feb 2012 09:49:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.481 X-Spam-Level: X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118, 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 dtGYknAWIo6z for ; Mon, 13 Feb 2012 09:49:33 -0800 (PST) Received: from mule.nps.edu (mule.nps.edu [205.155.65.106]) by ietfa.amsl.com (Postfix) with ESMTP id 1680221F8593 for ; Mon, 13 Feb 2012 09:49:33 -0800 (PST) X-ASG-Debug-ID: 1329155373-036c920f1b109750001-Rp4q3q Received: from hercules.ern.nps.edu (hercules.ern.nps.edu [172.20.24.111]) by mule.nps.edu with ESMTP id 6zgaLiv9KP5Ht8sv; Mon, 13 Feb 2012 09:49:33 -0800 (PST) X-Barracuda-Envelope-From: budden@nps.edu Received: from [172.20.58.67] (172.20.58.67) by smtp.nps.edu (172.20.24.111) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 13 Feb 2012 09:49:32 -0800 From: Rex Buddenberg X-ASG-Orig-Subj: Re: [manet] R2RI Framework and Requirements To: "Cheng, Bow-Nan - 0665 - MITLL" In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Mon, 13 Feb 2012 09:48:54 -0800 Message-ID: <1329155334.9169.2222.camel@localhost.localdomain> MIME-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit X-Barracuda-Connect: hercules.ern.nps.edu[172.20.24.111] X-Barracuda-Start-Time: 1329155373 X-Barracuda-URL: http://205.155.65.106:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at nps.edu X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.88446 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Cc: "manet@ietf.org" Subject: Re: [manet] R2RI Framework and Requirements X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 17:49:33 -0000 Bow-Nan, what you're calling 'descoping' is a good idea, IMHO. Getting the right data available and 2) figuring out how to use it are indeed two different problems. And they've been around the internet, manet and otherwise, for years, so I vote for the generalization idea too. more... On Mon, 2012-02-13 at 10:57 -0500, Cheng, Bow-Nan - 0665 - MITLL wrote: > Thanks Darrel and Lloyd for your helpful comments. > > Indeed the concept of R2RI/R2M can be applied in many contexts to help > throttle networks (and as you guys mentioned, have already been done to > some extent). > > I'm wondering if its possible to de-scope the work for various > applications. For example, in the MANET context, perhaps the role of the > R2RI protocol is to simply 1) define the link layer (1 RF hop) information > (a small subset) the radio/modem should provide to the multi-hop routing > layer (MANET Routing), and 2) define the transport mechanism to get this > to the router. > A couple 'how' thoughts. Does not #1 here describe a bunch of MIB variables? And does not SNMP already provide for #2? > How the router utilizes the link layer information (to make better > multi-hop routing decisions, reduce link flapping, etc.) is probably a > different problem and beyond the scope of R2RI. > Agreed. We need one mechanism to make the data visible; there may be more than one right answer regarding how the data is used. > > I guess what I'm wondering is if its possible to scope out R2RI in the > MANET context as providing information about 1-hop neighbors to a > multi-hop routing scheme.. Understanding that R2RI/R2M can be applied to > throttling entire networks and also be used a virtual interface over > Ethernet (which would be scoped as a different piece of work) > > > -- > Bow-Nan Cheng, Ph.D. > MIT Lincoln Laboratory > Airborne Networks Group > 244 Wood St Lexington MA 02420 > 781-981-4997 > > > > > On 2/12/12 7:17 PM, "Darrel Beach (dbeach)" wrote: > > >To add an additional thought...... > >I believe that the context of the Radio to Router information exchange > >over an > >Ethernet is actually applicable across another segment. Traditionally > >we've used > >routers with integrated interfaces for all the types underlying networks > >such as > >ISDN, Serial, Frame Relay, etc. By using a R2R framework it looks > >workable to have > >such interfaces which could now be separate from a router and have the > >interface to the > >router abstracted to occur over Ethernet. From a flexibility > >standpoint, and as an example, > >I see no reason why an ISDN interface card from vendor A couldn't use > >the R2R framework > >where it could establish a connection over ISDN and signal the > >connection information > >over the Ethernet using R2R protocols. This could be extended across > >virtually any > >connection type, including media or methods not normally seen. The > >Neighbor TLVs > >under discussion also provide an interesting mechanism for nonstandard > >connections > >to easily advertise connected devices. One prime example is the bus > >technology such as 1553. > >It's unlikely to see 1553 interfaces integrated into routers, but it > >looks quite feasible to > >abstract such an interface to the R2R framework for the transmission of > >IP packets. > > > >/d > >_______________________________________________ > >manet mailing list > >manet@ietf.org > >https://www.ietf.org/mailman/listinfo/manet > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www.ietf.org/mailman/listinfo/manet From jch@pps.jussieu.fr Mon Feb 13 11:08:42 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1884121F86FA for ; Mon, 13 Feb 2012 11:08:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35] 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 ePrUGmBKL2uh for ; Mon, 13 Feb 2012 11:08:41 -0800 (PST) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by ietfa.amsl.com (Postfix) with ESMTP id 3F44B21F86F0 for ; Mon, 13 Feb 2012 11:08:40 -0800 (PST) Received: from hydrogene.pps.jussieu.fr (hydrogene.pps.jussieu.fr [134.157.168.1]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id q1DJ8dwe067770 ; Mon, 13 Feb 2012 20:08:39 +0100 (CET) X-Ids: 164 Received: from lanthane.pps.jussieu.fr (lanthane.pps.jussieu.fr [134.157.168.57]) by hydrogene.pps.jussieu.fr (Postfix) with ESMTPS id 08260C0CEB; Mon, 13 Feb 2012 20:08:38 +0100 (CET) Received: from jch by lanthane.pps.jussieu.fr with local (Exim 4.77) (envelope-from ) id 1Rx1GP-00065r-Rk; Mon, 13 Feb 2012 20:08:37 +0100 From: Juliusz Chroboczek To: "Cheng\, Bow-Nan - 0665 - MITLL" References: Date: Mon, 13 Feb 2012 20:08:37 +0100 In-Reply-To: (Bow-Nan Cheng's message of "Fri, 10 Feb 2012 13:19:49 -0500") Message-ID: <7i39ae7dqi.fsf@lanthane.pps.jussieu.fr> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Miltered: at jchkmail.jussieu.fr with ID 4F395FB7.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4F395FB7.000/134.157.168.1/hydrogene.pps.jussieu.fr/hydrogene.pps.jussieu.fr/ Cc: "manet@ietf.org" Subject: Re: [manet] R2RI Framework and Requirements X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2012 19:08:42 -0000 Hi, Interesting model. A few quick comments after a first reading. The draft speaks of "link metrics" which it doesn't define. Are these physical layer data or the metrics used by the routing protocol? In other words, who is in charge of munging the physical layer information in order to compute the layer 3 metric -- the router or the radio? My reading is that you mean the former (the radio provides raw lower layer data which the router uses to compute a routing protocol metric), in which case I suggest that this should be made explicit. It should also be made explicit whether the other model (in which the radio cooks a single value which the router copies as-is into its RIB) is or isn't out of scope for R2RI (I think that Section 4.10 implies that it's out of scope). On a different note, it would be helpful if the draft provided a representative list of physical layers that are to be supported (it mentions unspecified "TDMA schemes" in Section 4.9 and 802.11 ad-hoc in Section 5.7, but it would be nice to have a more representative list were provided). Minor nits: In Section 4.7, "affect" instead of "effect". In Section 4.12, extraneous comma before "offer unique challenges". In Section 5.5, "affect" instead of "effect" (twice). In Section 6, "This document does not address security considerations." Yes it does, in Section 4.15. Regards, -- Juliusz Chroboczek From maddalena.nurchis@iit.cnr.it Tue Feb 14 05:18:18 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 442A521F8657 for ; Tue, 14 Feb 2012 05:18:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.39 X-Spam-Level: X-Spam-Status: No, score=0.39 tagged_above=-999 required=5 tests=[AWL=1.109, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] 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 YE6wl-OL9KeQ for ; Tue, 14 Feb 2012 05:18:13 -0800 (PST) Received: from smtp.iit.cnr.it (mx7.iit.cnr.it [146.48.98.140]) by ietfa.amsl.com (Postfix) with ESMTP id 413B921F863D for ; Tue, 14 Feb 2012 05:18:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by smtp.iit.cnr.it (Postfix) with ESMTP id 046F712EE48 for ; Tue, 14 Feb 2012 14:18:09 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mx7.iit.cnr.it Received: from smtp.iit.cnr.it ([127.0.0.1]) by localhost (mx7.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i+Mx45rt9SuA for ; Tue, 14 Feb 2012 14:18:07 +0100 (CET) Received: from [146.48.99.123] (dhcp60.iit.cnr.it [146.48.99.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.iit.cnr.it (Postfix) with ESMTPSA id 2529C12EE40 for ; Tue, 14 Feb 2012 14:18:07 +0100 (CET) Message-ID: <4F3A5F11.4080608@iit.cnr.it> Date: Tue, 14 Feb 2012 14:18:09 +0100 From: Maddalena Nurchis - IIT - CNR User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.26) Gecko/20120131 Thunderbird/3.1.18 MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: [manet] ACM Q2SWinet 2012: Call for Papers X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2012 13:19:09 -0000 Please accept our apologies if you receive multiple copies of this CFP. ---------------------------------------------------------------------- CALL FOR PAPERS The 8th ACM* Symposium on QoS and Security for Wireless Mobile Networks (ACM Q2SWinet 2012) October 21st-25th, 2012 Paphos, Cyprus http://cnd.iit.cnr.it/q2swinet2012 Jointly held with the 15th ACM MSWiM 2012 Conference. * ACM Pending upon Approval **** Paper Registration Deadline --- May 30th, 2012 **** ---------------------------------------------------------------------- SCOPE AND OVERVIEW -------------------------------- In recent years, wireless and mobile communication systems have become increasingly popular as an inexpensive and promising means for ubiquitous communications. In this scenario, the QoS provisioning and the management of network security have become crucial tasks to determine the success of future generation wireless mobile networks.This symposium calls for cutting-edge research achievements on the provisioning of QoS and Security in wireless and mobile networks. It also aims at increasing the synergy between academic and industry professionals working in this area. Authors are encouraged to submit full papers presenting new research related to theory or practice of all aspects of Quality of Service and Security issues in mobile and wireless systems. Topics of interest for ACM Q2SWinet 2012 include, but are not limited to: + Security in Wireless MANETs, VANETs, Sensor, Mesh and PCS Networks + Secure PHY, MAC and Routing Protocols + Secure Cooperation-Based Systems and Services + Security for Cognitive Radio Networks + Intrusion Detection in Wireless Ad hoc and Sensor Networks + Privacy, anonymity and authentication + Trust Establishment + Cooperation and Prevention of Non-cooperative Behavior + Incentive Aware Secure Protocol Design + QoS/QoE for Wireless Multimedia Networks and Systems + QoS/QoE for Wireless/Wired Hybrid Systems + QoS/QoE support and Mobility Management in Wireless Internet + QoS/QoE-Aware Routing for Wireless Networks + QoS/QoE Metrics + Wireless Network Survivability + Wireless Systems Reliability + Field operating tests, Performance Modeling and Simulation Techniques + Real-time and QoS-aware Wireless Networks PAPER SUBMISSION AND PUBLICATION -------------------------------- Papers should neither have been published elsewhere nor being currently under review by another conference or journal. Manuscripts are limited to 10 pages, single spacing, double column, and must strictly adhere to the ACM template format. Guidelines on paper submission and formatting are available at http://cnd.iit.cnr.it/q2swinet2012/. Submission is managed electronically through EDAS: http://edas.info/N12037 At least one author of each accepted paper must be registered for the symposium, in order for that paper to appear in the ACM proceedings and to be scheduled for presentation. Furthermore, authors of accepted papers must guarantee that their paper will be presented at the Symposium. IMPORTANT DATES --------------- Paper registration: May 30th, 2012 Paper submission: June 5th, 2012 Notification: July 15th, 2012 Symposium: October 21st-25th, 2012 ORGANIZING COMMITTEE -------------------- General Chair Peter Mueller, IBM Zurich Research Laboratory, Switzerland Program Committee Chairs Jalel Ben-Othman, University of Paris 13, France Raffaele Bruno, IIT, CNR, Italy Program Committee (tentative) Nael Abu-Ghazaleh, State University of New York at Binghamton, USA Gergely Acs, INRIA, Rhone-Alpes, France Emilio Ancillotti, IIT-CNR, Italy Regina Araujo, Federal University of Sao Carlos, Brazil Jalel Ben-othman, University of Versailles, France Boldizsar Bencsath, Budapest University of Tech. and Economics, Hungary Luciano Bononi, University of Bologna, Italy Azzedine Boukerche, University of Ottawa, Canada Roberto Cascella, INRIA, France Llorenç Cerdra-Alabern, Universitat Politecnica de Catalunya, Spain Matteo Cesana, Politecnico di Milano, Italy Bruno Crispo, University of Trento, Italy Roberto Di Pietro, Universita' di Roma Tre, Italy Falko Dressler, University of Erlangen Rosario Garroppo, University of Pisa, Italy Fabrizio Granelli, University of Trento, Italy Stefanos Gritzalis, University of the Aegean, Greece Dimitrios Koutsonikolas, University at Buffalo, SUNY, USA Albert Levi, Sabanci University, Turkey Lynda Mokdad, Université de Paris 12, France Peter Mueller, IBM Zurich Research Laboratory, Switzerland Stefano Paris, University of Bergamo, Italy Mahalingam Ramkumar, Mississippi State University, USA Peter Reiher, UCLA, USA Simon Pietro Romano, University of Napoli Federico II, Italy Susana Sargento, University of Aveiro, Portugal Ahmed Serhrouchni, ENST, France Sabrina Sicari, University of Insubria, Italy Vasilios Siris, Athens University of Economics and Business, Greece Avinash Srinivasan, George Mason University, USA Damla Turgut, University of Central Florida, USA Giacomo Verticale, Politecnico di Milano, Italy André Zuquete, University of Aveiro, Portugal Albert Zomaya, The University of Sydney, Australia Publicity Co-chairs Victor Govindaswamy, University of Texas at Arlington, USA Maddalena Nurchis, IIT, CNR, Italy -- Maddalena Nurchis, PhD Institute for Informatics and Telematics (IIT), Italian National Research Council (CNR) Via G. Moruzzi 1, 56124 Pisa, Italy. Department of Information Engineering, University of Pisa Via G. Caruso 16, 56122 Pisa, Italy phone: + 39 050 315 2195 (direct) e-mail: maddalena.nurchis@imtlucca.it; maddalena.nurchis@iit.cnr.it homepage: http://www.imtlucca.it/maddalena.nurchis From prvs=33912de304=bcheng@ll.mit.edu Tue Feb 14 07:42:21 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3B8621F87CC for ; Tue, 14 Feb 2012 07:42:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001] 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 1dmLXSlxWUXB for ; Tue, 14 Feb 2012 07:42:20 -0800 (PST) Received: from mx2.ll.mit.edu (MX2.LL.MIT.EDU [129.55.12.46]) by ietfa.amsl.com (Postfix) with ESMTP id 8DDE821F87B6 for ; Tue, 14 Feb 2012 07:42:20 -0800 (PST) Received: from LLE2K7-HUB01.mitll.ad.local (LLE2K7-HUB01.mitll.ad.local) by mx2.ll.mit.edu (unknown) with ESMTP id q1EFgBvU016830; Tue, 14 Feb 2012 10:42:11 -0500 From: "Cheng, Bow-Nan - 0665 - MITLL" To: Rex Buddenberg Date: Tue, 14 Feb 2012 10:42:08 -0500 Thread-Topic: [manet] R2RI Framework and Requirements Thread-Index: AczrLzZ8ZkJeJVNyRbuTY69wVLdP8w== Message-ID: In-Reply-To: <1329155334.9169.2222.camel@localhost.localdomain> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.12.0.110505 acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7361, 1.0.260, 0.0.0000 definitions=2012-02-14_03:2012-02-14, 2012-02-14, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1202140123 Cc: "manet@ietf.org" Subject: Re: [manet] R2RI Framework and Requirements X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2012 15:42:21 -0000 Hi Rex, Thanks for your helpful comments. With regards to the thought on potentially using SNMP, not being as familiar with the protocol as perhaps I should (though others can chime in), here're a few reasons that potentially precludes us from using it: 1. Time scale =AD radio link metrics change in sub-second timescales. SNMP typically operates in multiple-second timescales. Polling multiple radio systems in small timescales can impact performance on the radio systems 2. Flow control =AD SNMP doesn't have any provisions for flow control (such as the credit-based or pause-frame based concepts we're looking at) on a link 3. Bi-directionality - Not sure if SNMP supports bi-directional query/response. Ie. The Router requesting more bandwidth, the radio responding with more timeslots. My impression is that SNMP doesn't have built-in "ACK" functionality. In SNMP, to request more bandwidth from the radio, you would probably need to "SET" the bandwidth and then "GET" the operating data rate to see if the changes took. These are just some of my initial thoughts.. Though the authors of http://tools.ietf.org/html/draft-sratliff-dlep-02 http://tools.ietf.org/html/rfc5578 http://tools.ietf.org/html/draft-dubois-r2cp-00 http://tools.ietf.org/html/draft-ivancic-mobopts-modemlpa-00 Could probably give more justifications. Perhaps a section comparing SNMP and R2RI in the Framework and Requirements document is needed. -Bow-Nan -- Bow-Nan Cheng, Ph.D. MIT Lincoln Laboratory Airborne Networks Group 244 Wood St Lexington MA 02420 781-981-4997 On 2/13/12 12:48 PM, "Rex Buddenberg" wrote: >Bow-Nan, > >what you're calling 'descoping' is a good idea, IMHO. > >Getting the right data available and 2) figuring out how to use it are >indeed two different problems. And they've been around the internet, >manet and otherwise, for years, so I vote for the generalization idea >too. =20 > >more... > >On Mon, 2012-02-13 at 10:57 -0500, Cheng, Bow-Nan - 0665 - MITLL wrote: >> Thanks Darrel and Lloyd for your helpful comments. >>=20 >> Indeed the concept of R2RI/R2M can be applied in many contexts to help >> throttle networks (and as you guys mentioned, have already been done to >> some extent). >>=20 >> I'm wondering if its possible to de-scope the work for various >> applications. For example, in the MANET context, perhaps the role of the >> R2RI protocol is to simply 1) define the link layer (1 RF hop) >>information >> (a small subset) the radio/modem should provide to the multi-hop routing >> layer (MANET Routing), and 2) define the transport mechanism to get this >> to the router. >>=20 >A couple 'how' thoughts. Does not #1 here describe a bunch of MIB >variables? And does not SNMP already provide for #2? > > > >> How the router utilizes the link layer information (to make better >> multi-hop routing decisions, reduce link flapping, etc.) is probably a >> different problem and beyond the scope of R2RI. >>=20 >Agreed. We need one mechanism to make the data visible; there may be >more than one right answer regarding how the data is used. >>=20 >> I guess what I'm wondering is if its possible to scope out R2RI in the >> MANET context as providing information about 1-hop neighbors to a >> multi-hop routing scheme.. Understanding that R2RI/R2M can be applied to >> throttling entire networks and also be used a virtual interface over >> Ethernet (which would be scoped as a different piece of work) >>=20 >>=20 >> -- >> Bow-Nan Cheng, Ph.D. >> MIT Lincoln Laboratory >> Airborne Networks Group >> 244 Wood St Lexington MA 02420 >> 781-981-4997 >>=20 >>=20 >>=20 >>=20 >> On 2/12/12 7:17 PM, "Darrel Beach (dbeach)" wrote: >>=20 >> >To add an additional thought...... >> >I believe that the context of the Radio to Router information exchange >> >over an >> >Ethernet is actually applicable across another segment. Traditionally >> >we've used=20 >> >routers with integrated interfaces for all the types underlying >>networks >> >such as >> >ISDN, Serial, Frame Relay, etc. By using a R2R framework it looks >> >workable to have >> >such interfaces which could now be separate from a router and have the >> >interface to the >> >router abstracted to occur over Ethernet. From a flexibility >> >standpoint, and as an example, >> >I see no reason why an ISDN interface card from vendor A couldn't use >> >the R2R framework >> >where it could establish a connection over ISDN and signal the >> >connection information >> >over the Ethernet using R2R protocols. This could be extended across >> >virtually any=20 >> >connection type, including media or methods not normally seen. The >> >Neighbor TLVs >> >under discussion also provide an interesting mechanism for nonstandard >> >connections=20 >> >to easily advertise connected devices. One prime example is the bus >> >technology such as 1553. >> >It's unlikely to see 1553 interfaces integrated into routers, but it >> >looks quite feasible to >> >abstract such an interface to the R2R framework for the transmission of >> >IP packets. >> > >> >/d >> >_______________________________________________ >> >manet mailing list >> >manet@ietf.org >> >https://www.ietf.org/mailman/listinfo/manet >>=20 >> _______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www.ietf.org/mailman/listinfo/manet > > From prvs=33912de304=bcheng@ll.mit.edu Tue Feb 14 07:46:54 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC2FA21F8790 for ; Tue, 14 Feb 2012 07:46:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001] 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 ACphXC1eB-V6 for ; Tue, 14 Feb 2012 07:46:53 -0800 (PST) Received: from mx2.ll.mit.edu (MX2.LL.MIT.EDU [129.55.12.46]) by ietfa.amsl.com (Postfix) with ESMTP id C423521F8773 for ; Tue, 14 Feb 2012 07:46:52 -0800 (PST) Received: from LLE2K7-HUB01.mitll.ad.local (LLE2K7-HUB01.mitll.ad.local) by mx2.ll.mit.edu (unknown) with ESMTP id q1EFkqMk019342; Tue, 14 Feb 2012 10:46:52 -0500 From: "Cheng, Bow-Nan - 0665 - MITLL" To: Juliusz Chroboczek Date: Tue, 14 Feb 2012 10:46:49 -0500 Thread-Topic: [manet] R2RI Framework and Requirements Thread-Index: AczrL94XreFPNoy4RgSa3R6X7TxmYg== Message-ID: In-Reply-To: <7i39ae7dqi.fsf@lanthane.pps.jussieu.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.12.0.110505 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7361, 1.0.260, 0.0.0000 definitions=2012-02-14_03:2012-02-14, 2012-02-14, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1202140123 Cc: "manet@ietf.org" Subject: Re: [manet] R2RI Framework and Requirements X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2012 15:46:54 -0000 Hi Juliusz, Thanks for your helpful comments. I will define link metrics in the next draft, but you are correct in that these are radio-specific metrics (link layer) that are sent to the router. The way its currently done in practice is that the metrics are provided in raw format, and the routing protocol dynamically calculates a cost based on the link metrics: See an example here: http://www.cisco.com/en/US/docs/ios/12_4t/ip_mobility/configuration/guide/i p_manet.html I think there's a lot of potential for doing routing w/ link metrics better than coming up with 1 cost.. But it is beyond the scope of the document.=20 I will incorporate the other suggestions. Thanks! -Bow-Nan -- Bow-Nan Cheng, Ph.D. MIT Lincoln Laboratory Airborne Networks Group 244 Wood St Lexington MA 02420 781-981-4997 On 2/13/12 2:08 PM, "Juliusz Chroboczek" wrote: >Hi, > >Interesting model. A few quick comments after a first reading. > >The draft speaks of "link metrics" which it doesn't define. Are these >physical layer data or the metrics used by the routing protocol? In >other words, who is in charge of munging the physical layer information >in order to compute the layer 3 metric -- the router or the radio? > >My reading is that you mean the former (the radio provides raw lower >layer data which the router uses to compute a routing protocol metric), >in which case I suggest that this should be made explicit. It should >also be made explicit whether the other model (in which the radio cooks >a single value which the router copies as-is into its RIB) is or isn't >out of scope for R2RI (I think that Section 4.10 implies that it's out >of scope). > >On a different note, it would be helpful if the draft provided >a representative list of physical layers that are to be supported (it >mentions unspecified "TDMA schemes" in Section 4.9 and 802.11 ad-hoc in >Section 5.7, but it would be nice to have a more representative list >were provided). > >Minor nits: > >In Section 4.7, "affect" instead of "effect". > >In Section 4.12, extraneous comma before "offer unique challenges". > >In Section 5.5, "affect" instead of "effect" (twice). > >In Section 6, "This document does not address security considerations." >Yes it does, in Section 4.15. > >Regards, > >-- Juliusz Chroboczek > > From fabio.pezzoni@iit.cnr.it Mon Feb 20 03:51:48 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51E5321F8729 for ; Mon, 20 Feb 2012 03:51:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.587 X-Spam-Level: ** X-Spam-Status: No, score=2.587 tagged_above=-999 required=5 tests=[AWL=-0.768, BAYES_50=0.001, FRT_ADULT2=1.474, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] 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 IqCvHL0Y3jll for ; Mon, 20 Feb 2012 03:51:43 -0800 (PST) Received: from irina.iit.cnr.it (irina-lan.iit.cnr.it [146.48.96.79]) by ietfa.amsl.com (Postfix) with ESMTP id E3DBA21F872B for ; Mon, 20 Feb 2012 03:51:34 -0800 (PST) Received: by irina.iit.cnr.it (Postfix, from userid 1000) id BFD863D803D; Mon, 20 Feb 2012 12:51:01 +0100 (CET) Date: Mon, 20 Feb 2012 12:51:01 +0100 From: Fabio Pezzoni To: manet@ietf.org Message-ID: <4f4233a5.J682hPFD+gmVAJjG%fabio.pezzoni@iit.cnr.it> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [manet] [IEEE AOC 2012] ***Deadline Extended*** X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2012 11:51:48 -0000 ================================================================================ ***** PAPER SUBMISSION DEADLINE HAS BEEN EXTENDED TO ***** FEBRUARY 26, 2012 (11:59pm EST) *** REGISTER YOUR PAPER BY FEBRUARY 17, 2012 (11:59pm EST) *** ================================================================================ -------------------------------------------------------------------------------- CALL FOR PAPERS Sixth IEEE WoWMoM Workshop on Autonomic and Opportunistic Communications (AOC 2012) June 25, 2012 - San Francisco, California, USA http://cnd.iit.cnr.it/aoc2012/ jointly supported by the SCAMPI project funded by the FP7-ICT Programme under the Future Internet Research and Experimentation (FIRE) initiative http://www.ict-scampi.eu/ and RECOGNITION project funded by the FP7-ICT Programme under the Future and Emerging Technologies (FET) initiative http://www.recognition-project.eu/ Fast Track on Computer Communication Journal http://www.elsevier.com/locate/comcom **** Registration Deadline --- February 17, 2012 **** **** Submission Deadline --- February 26, 2012 **** -------------------------------------------------------------------------------- The diffusion of lightweight, powerful portable devices, also enriched with a variety of sensing capabilities, is enabling new ways for users' communication, and laying the foundation for realizing the ubiquitous networking idea. Acting either as the main communication mode or as complement to existing mobile network infrastructures, opportunistic networking can leverage the mobility of end users and enhance their communication capabilities. The opportunistic exploitation of extemporary contacts among the users of the network paves the way to a number of applications but also poses new and challenging problems to the networking research community. The AOC 2012 workshop aims at serving as a meeting point for people working in the area and a forum for exchanging ideas, discussing solutions, and sharing experiences among researchers, professionals, and application developers, both from industry and academia. As with the previous five editions of the AOC workshop series, the scope of this year's workshop will remain on general issues related to opportunistic networking and computing. Yet, AOC 2012 will have a primary interest in new directions of opportunistic communications, such as service composition techniques, scenarios of co-existence with infrastructure networks, and insights to their operation coming from other disciplines such as game theory and cognitive psychology. The workshop will solicit original papers addressing theoretical and practical aspects of autonomic and opportunistic communications but also papers describing prototype implementations and deployments. Topics of interest for AOC 2012 include, but are not limited to: * Routing, transport, and reliability issues * Techniques for data dissemination and replication * Applications and middleware support, mobile social networking applications * Mobility models and statistical analysis of mobility traces * Context and social awareness mechanisms and algorithms * Co-existence of opportunistic networks with infrastructure mobile wireless networks * Service composition in autonomic and opportunistic networks * Cognition-driven information processing and decision making * Performance modelling, scaling laws, and fundamental limits for autonomic and opportunistic communications * Game-theoretic insights to the operation of autonomic and opportunistic networks * Participatory and urban sensing in autonomic and opportunistic networks * Trust, security, and reputation * Autonomic and opportunistic communication testbeds and prototypes, measurement data from real experiments * Socio-economic models for autonomic and opportunistic communications PAPER SUBMISSION AND PUBLICATION -------------------------------- Papers should neither have been published elsewhere nor being currently under review by another conference or journal. Manuscripts are limited to 6 pages, single spacing, double column, and must strictly adhere to the template format. Guidelines on paper submission and formatting are available at http://cnd.iit.cnr.it/aoc2012/. Accepted papers will appear in the symposium proceedings published by IEEE. At least one author of each accepted paper is required to register and present his/her work at the workshop. There will be no separate registration for workshop, but one single registration will cover both conference and workshops participation. Extended versions of workshop selected papers will be considered for possible fast track publication on the Computer Communications Journal (Elsevier). IMPORTANT DATES --------------- Paper registration: February 17, 2012 Full papers due: February 26, 2012 Notification: April 4, 2012 Workshop: June 25, 2012 ORGANIZING COMMITTEE -------------------- WORKSHOP Chairs Merkouris Karaliopoulos, University of Athens, Greece Chiara Boldrini, IIT-CNR, Italy STEERING Committee Marco Conti, IIT-CNR, Italy Silvia Giordano, SUPSI, Switzerland Ioannis Stavrakakis, University of Athens, Greece PUBLICITY Chairs Fabio Pezzoni, IIT-CNR, Italy Pushpendra Singh, IIIT Delhi, India PROGRAM COMMITTEE ----------------- Gergely Acs, BUTE, Hungary Eleonora Borgia, IIT-CNR, Italy Jian-Nong Cao, Hong Kong Polytechnic University, HK Vania Conan, Thales, France Serge Fdida, UPMC, Paris VI, France Laura Galluccio, University of Catania, Italy Nidhi Hegde, Technicolor, France Tristan Henderson, University of St. Andrews, UK Gunnar Karlsson, KTH, Sweden Mohan Kumar, University of Texas at Arlington, USA Kyunghan Lee, North Carolina State University, USA Franck Legendre, ETH Zurich, Switzerland Daniele Miorandi, Create-net, Italy Refik Molva, Eurecom, France Valtteri Niemi, Nokia, Switzerland Katia Obraczka, University of California, Santa Cruz, USA Konstantinos Oikonomou, Ionian University, Greece Joerg Ott, HUT, Finland Elena Pagani, Universita' degli Studi di Milano, Italy Andrea Passarella, IIT-CNR, Italy Daniele Puccinelli, SUPSI, Switzerland Christian Rohner, Uppsala University, Sweden Fabrizio Sestini, EU Commission Abdullatif Shikfa, Alcatel Lucent Bell Labs, France Thrasyvoulos Spyropoulos, EURECOM, France Roger Whitaker, Cardiff University, UK Hongyi Wu, University of Louisiana at Lafayette, USA Eiko Yoneki, University of Cambridge, UK Franco Zambonelli, University of Modena-Reggio, Italy Xiaolan Zhang, Fordham University, USA From kashifalam786@gmail.com Sat Feb 25 23:37:03 2012 Return-Path: X-Original-To: manet@ietfa.amsl.com Delivered-To: manet@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CDCF21F861A for ; Sat, 25 Feb 2012 23:37:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.109 X-Spam-Level: X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] 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 zXjpJIryU1k8 for ; Sat, 25 Feb 2012 23:37:02 -0800 (PST) Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6F82721F8498 for ; Sat, 25 Feb 2012 23:37:02 -0800 (PST) Received: by qafi29 with SMTP id i29so990113qaf.10 for ; Sat, 25 Feb 2012 23:37:01 -0800 (PST) Received-SPF: pass (google.com: domain of kashifalam786@gmail.com designates 10.224.33.1 as permitted sender) client-ip=10.224.33.1; Authentication-Results: mr.google.com; spf=pass (google.com: domain of kashifalam786@gmail.com designates 10.224.33.1 as permitted sender) smtp.mail=kashifalam786@gmail.com; dkim=pass header.i=kashifalam786@gmail.com Received: from mr.google.com ([10.224.33.1]) by 10.224.33.1 with SMTP id f1mr5690925qad.83.1330241821938 (num_hops = 1); Sat, 25 Feb 2012 23:37:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=OX/0xpDiw1vtnLb3kNi0gGKaRRid/dEzSi4G1ZWJIvg=; b=DZ+KeOhG4AN/BKTgfnw3QfHjLm63gv4JbZX4FUAtJFvoVhv/WbRhI5238wT1MUzbMQ YzPEtpZ1jDPmx5wpYcKrkJpVd1ERtC/AfyCNb2KmkXtBh22QsuA4RUwauCv7dXbHDijF ywO9dJ9fhBc9Yvg0MrCOFzXBSZkWrlQHqsXrw= MIME-Version: 1.0 Received: by 10.224.33.1 with SMTP id f1mr4812543qad.83.1330241821907; Sat, 25 Feb 2012 23:37:01 -0800 (PST) Received: by 10.229.253.68 with HTTP; Sat, 25 Feb 2012 23:37:01 -0800 (PST) Date: Sun, 26 Feb 2012 13:07:01 +0530 Message-ID: From: kashif alam To: manet@ietf.org Content-Type: multipart/alternative; boundary=20cf30207484429bdd04b9d90fe5 Subject: [manet] Aodv code explanation X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2012 07:40:00 -0000 --20cf30207484429bdd04b9d90fe5 Content-Type: text/plain; charset=ISO-8859-1 Hi, this is Kashif here. Can someone please help me understand the aodv code. A proper documentation of it might be helpful. -- Regards -Kashif Alam --20cf30207484429bdd04b9d90fe5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,=A0
this is Kashif here. Can someone please help me understand the a= odv code. A proper documentation of it might be helpful.
<= div>
--



Regards -Kashif Alam

--20cf30207484429bdd04b9d90fe5--