
From robert.g.cole.civ@mail.mil  Fri Sep  2 10:19:29 2011
Return-Path: <robert.g.cole.civ@mail.mil>
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 CA14221F8B24 for <manet@ietfa.amsl.com>; Fri,  2 Sep 2011 10:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.304
X-Spam-Level: 
X-Spam-Status: No, score=-2.304 tagged_above=-999 required=5 tests=[AWL=0.295,  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 KWlOduLmvi69 for <manet@ietfa.amsl.com>; Fri,  2 Sep 2011 10:19:29 -0700 (PDT)
Received: from edge-cols.mail.mil (edge-cols.mail.mil [131.64.100.11]) by ietfa.amsl.com (Postfix) with ESMTP id 21C2621F8B0D for <manet@ietf.org>; Fri,  2 Sep 2011 10:19:28 -0700 (PDT)
Received: from UCOLHP3F.easf.csd.disa.mil (131.64.100.145) by ucolhp3l.easf.csd.disa.mil (131.64.100.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 2 Sep 2011 12:20:56 -0500
Received: from UCOLHP4J.easf.csd.disa.mil ([169.254.8.134]) by UCOLHP3F.easf.csd.disa.mil ([169.254.56.193]) with mapi id 14.01.0323.003; Fri, 2 Sep 2011 12:20:55 -0500
From: "Cole, Robert G USA CIV (US)" <robert.g.cole.civ@mail.mil>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: Simplifying the REPORT-MIB (UNCLASSIFIED)
Thread-Index: AcxouEddgeYawCBWR42bHMkanV+d9AA3B9IA
Date: Fri, 2 Sep 2011 17:20:55 +0000
Message-ID: <B9468E58D6A0A84AAD66FE4E694BEABB31612A10@ucolhp4j.easf.csd.disa.mil>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [131.64.77.13]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_004F_01CC6973.2358CF00"
MIME-Version: 1.0
Subject: [manet] Simplifying the REPORT-MIB (UNCLASSIFIED)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Sep 2011 17:19:29 -0000

------=_NextPart_000_004F_01CC6973.2358CF00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Classification: UNCLASSIFIED
Caveats: NONE

To All, 

Sorry if this is a repeat, but I never saw a confirmation that this email
was sent.  So here goes:

Following up from our discussion in Quebec City last month on the future
directions of the REPORT-MIB.  Basically, the REPORT-MIB is too complex,
e.g., it currently contains 12 conformance groups.  I had proposed to
simplify it greatly for its first incarnation.  The problem is that the
REPORT-MIB currently defines three separate types of local reports that it
can generate, i.e., Statistical, Sampled and Historical.  I had proposed to
define only the Sampled reporting capability for the first incarnation and
to gain experience with this reporting type prior to spending a lot of time
defining and developing the additional two types. I proposed the Sampled
group as the first to gain experience with because it more closely follows
SNMP methods and experience for performance monitoring. 

The consensus at the meeting was that this proposal made sense, but in
addition the REPORT-MIB should be moved to Experimental which was also
accepted by the meeting.  However, to make this decision formal, we need to
take it to the mailing list.

Please let us know whether or not you agree with this proposal.  

Thanks,

Bob


Classification: UNCLASSIFIED
Caveats: NONE



------=_NextPart_000_004F_01CC6973.2358CF00
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
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA5MDIxNzIwNTJaMCMGCSqGSIb3
DQEJBDEWBBSOitmAs/vYYEeJjgERCF11m3gLxDBYBgkqhkiG9w0BCQ8xSzBJMAoGCCqGSIb3DQMH
MA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjAKBggqhkiG
9w0CBTBzBgkrBgEEAYI3EAQxZjBkMF0xCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVy
bm1lbnQxDDAKBgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwgQ0Et
MjQCAwzbMzB1BgsqhkiG9w0BCRACCzFmoGQwXTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g
R292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxGDAWBgNVBAMTD0RPRCBFTUFJ
TCBDQS0yNAIDDNszMA0GCSqGSIb3DQEBAQUABIIBANE+ERBLuj+lMa9WtvbjKykUq9xTTg0o5Bsl
HUx1/wWcWvqeePcCK+CK9V1ORBhkvf7QTmvF46vLHNuNpsJ+8oL20qGNnyxc9TOqU088g6wrt2Fx
FTLlTD/2l1jbqDY11ZfiQOIpS1RZYUbA/BaLEgk7HcWYDQb7MdsebE74jZEcXGtYaYz7Tf/utcMB
g+eF29t/po+zkEsjAwbWEqdU7Wuy0biMYU4BdW3W4nWLssrI0hHsFS70eQaHlwOE5+fg+Cc+4Bc/
IWLj24ssszeMSnc0mtQGeae+6t95OaLxR94bpJalOedZg0R4F9bNAJIjeXdE59A/k/6DgjxLPpwR
FX8AAAAAAAA=

------=_NextPart_000_004F_01CC6973.2358CF00--

From ulrich@herberg.name  Fri Sep  2 10:36:20 2011
Return-Path: <ulrich@herberg.name>
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 1C85A21F8B36 for <manet@ietfa.amsl.com>; Fri,  2 Sep 2011 10:36:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.918
X-Spam-Level: 
X-Spam-Status: No, score=-2.918 tagged_above=-999 required=5 tests=[AWL=0.058,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 3ug9IVwwMst6 for <manet@ietfa.amsl.com>; Fri,  2 Sep 2011 10:36:19 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0D79B21F8B26 for <manet@ietf.org>; Fri,  2 Sep 2011 10:36:18 -0700 (PDT)
Received: by vws12 with SMTP id 12so2997427vws.31 for <manet@ietf.org>; Fri, 02 Sep 2011 10:37:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zjVkuu4O94PkdRf0eaUFZ9CcAni74kkPad7ej+oP7SY=; b=ciMJi2WV385YmRhqth5Az2XUkSdUweYyD3dNiNfBSvKxV35omkT9HCrXENSqu5Ft9I 1Qamehn/0uantBk1iJcb39PkbwHm6D6balcJTi8ybhw78HYAANCEY4YOWfg5bcHcAIqU 9S7toaIlGuJ5pO5BfzFhlMdGS5tqErUOrTnQM=
MIME-Version: 1.0
Received: by 10.52.88.175 with SMTP id bh15mr276449vdb.13.1314985071727; Fri, 02 Sep 2011 10:37:51 -0700 (PDT)
Received: by 10.220.51.130 with HTTP; Fri, 2 Sep 2011 10:37:51 -0700 (PDT)
In-Reply-To: <B9468E58D6A0A84AAD66FE4E694BEABB31612A10@ucolhp4j.easf.csd.disa.mil>
References: <B9468E58D6A0A84AAD66FE4E694BEABB31612A10@ucolhp4j.easf.csd.disa.mil>
Date: Fri, 2 Sep 2011 10:37:51 -0700
Message-ID: <CAK=bVC9smbkRziRRoQZH3oJOc2EoiRuKK51SfrqZax4OSH30rA@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: "Cole, Robert G USA CIV (US)" <robert.g.cole.civ@mail.mil>
Content-Type: multipart/alternative; boundary=20cf3071c65215d3b104abf8d295
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] Simplifying the REPORT-MIB (UNCLASSIFIED)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Sep 2011 17:36:20 -0000

--20cf3071c65215d3b104abf8d295
Content-Type: text/plain; charset=ISO-8859-1

Hi Bob,

I think your suggestion makes sense. Acquiring statistical data or historic
data can also be done in the management application itself, and may
therefore not be required by the REPORT-MIB. We probably need to get more
experience to see if at a later point of time it would make sense to add the
other functionality.

I also support the change of intended status.

On a related note, we are close to submitting a new revision of the NHDP-MIB
without any references to the REPORT-MIB (which would otherwise be a
down-ref).

Regards
Ulrich

On Fri, Sep 2, 2011 at 10:20 AM, Cole, Robert G USA CIV (US) <
robert.g.cole.civ@mail.mil> wrote:

> Classification: UNCLASSIFIED
> Caveats: NONE
>
> To All,
>
> Sorry if this is a repeat, but I never saw a confirmation that this email
> was sent.  So here goes:
>
> Following up from our discussion in Quebec City last month on the future
> directions of the REPORT-MIB.  Basically, the REPORT-MIB is too complex,
> e.g., it currently contains 12 conformance groups.  I had proposed to
> simplify it greatly for its first incarnation.  The problem is that the
> REPORT-MIB currently defines three separate types of local reports that it
> can generate, i.e., Statistical, Sampled and Historical.  I had proposed to
> define only the Sampled reporting capability for the first incarnation and
> to gain experience with this reporting type prior to spending a lot of time
> defining and developing the additional two types. I proposed the Sampled
> group as the first to gain experience with because it more closely follows
> SNMP methods and experience for performance monitoring.
>
> The consensus at the meeting was that this proposal made sense, but in
> addition the REPORT-MIB should be moved to Experimental which was also
> accepted by the meeting.  However, to make this decision formal, we need to
> take it to the mailing list.
>
> Please let us know whether or not you agree with this proposal.
>
> Thanks,
>
> Bob
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>

--20cf3071c65215d3b104abf8d295
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Bob,<br><br>I think your suggestion makes sense. Acquiring=20
statistical data or historic data can also be done in the management=20
application itself, and may therefore not be required by the REPORT-MIB.
 We probably need to get more experience to see if at a later point of=20
time it would make sense to add the other functionality.<br>
<br>I also support the change of intended status. <br><br>On a related=20
note, we are close to submitting a new revision of the NHDP-MIB without=20
any references to the REPORT-MIB (which would otherwise be a down-ref).<br>=
<br>
Regards<br>Ulrich<br><br><div class=3D"gmail_quote">On Fri, Sep 2, 2011 at =
10:20 AM, Cole, Robert G USA CIV (US) <span dir=3D"ltr">&lt;<a href=3D"mail=
to:robert.g.cole.civ@mail.mil">robert.g.cole.civ@mail.mil</a>&gt;</span> wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Classification: UNCLASSIFIED<br>
Caveats: NONE<br>
<br>
To All,<br>
<br>
Sorry if this is a repeat, but I never saw a confirmation that this email<b=
r>
was sent. =A0So here goes:<br>
<br>
Following up from our discussion in Quebec City last month on the future<br=
>
directions of the REPORT-MIB. =A0Basically, the REPORT-MIB is too complex,<=
br>
e.g., it currently contains 12 conformance groups. =A0I had proposed to<br>
simplify it greatly for its first incarnation. =A0The problem is that the<b=
r>
REPORT-MIB currently defines three separate types of local reports that it<=
br>
can generate, i.e., Statistical, Sampled and Historical. =A0I had proposed =
to<br>
define only the Sampled reporting capability for the first incarnation and<=
br>
to gain experience with this reporting type prior to spending a lot of time=
<br>
defining and developing the additional two types. I proposed the Sampled<br=
>
group as the first to gain experience with because it more closely follows<=
br>
SNMP methods and experience for performance monitoring.<br>
<br>
The consensus at the meeting was that this proposal made sense, but in<br>
addition the REPORT-MIB should be moved to Experimental which was also<br>
accepted by the meeting. =A0However, to make this decision formal, we need =
to<br>
take it to the mailing list.<br>
<br>
Please let us know whether or not you agree with this proposal.<br>
<br>
Thanks,<br>
<br>
Bob<br>
<br>
<br>
Classification: UNCLASSIFIED<br>
Caveats: NONE<br>
<br>
<br>
<br>_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br>

--20cf3071c65215d3b104abf8d295--

From internet-drafts@ietf.org  Tue Sep  6 11:19:37 2011
Return-Path: <internet-drafts@ietf.org>
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 B2EEB21F8CC6; Tue,  6 Sep 2011 11:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, 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 s5qV4D0w-MYU; Tue,  6 Sep 2011 11:19:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4290321F8C56; Tue,  6 Sep 2011 11:19:37 -0700 (PDT)
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.60
Message-ID: <20110906181937.14107.17176.idtracker@ietfa.amsl.com>
Date: Tue, 06 Sep 2011 11:19:37 -0700
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-packetbb-sec-06.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2011 18:19:37 -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           : MANET Cryptographical Signature TLV Definition
	Author(s)       : Ulrich Herberg
                          Thomas Heide Clausen
	Filename        : draft-ietf-manet-packetbb-sec-06.txt
	Pages           : 17
	Date            : 2011-09-06

   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
   [RFC5444].  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.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-packetbb-sec-06.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-packetbb-sec-06.txt

From internet-drafts@ietf.org  Tue Sep  6 11:47:37 2011
Return-Path: <internet-drafts@ietf.org>
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 6C09E21F8D22; Tue,  6 Sep 2011 11:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 TDgYWR6vtBiK; Tue,  6 Sep 2011 11:47:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04CE421F8661; Tue,  6 Sep 2011 11:47:37 -0700 (PDT)
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.60
Message-ID: <20110906184737.21836.18828.idtracker@ietfa.amsl.com>
Date: Tue, 06 Sep 2011 11:47:37 -0700
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-nhdp-mib-10.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2011 18:47:37 -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           : Definition of Managed Objects for the Neighborhood Disco=
very Protocol
	Author(s)       : Ulrich Herberg
                          Robert G. Cole
                          Ian D Chakeres
	Filename        : draft-ietf-manet-nhdp-mib-10.txt
	Pages           : 67
	Date            : 2011-09-06

   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 parameters of the
   Neighborhood Discovery Protocol (NHDP) process on a router.  The MIB
   defined in this memo, denoted NHDP-MIB, also reports state,
   performance information and notifications.  This additional state and
   performance information is useful to troubleshoot problems and
   performance issues during neighbor discovery.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-nhdp-mib-10.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-nhdp-mib-10.txt

From ulrich@herberg.name  Tue Sep  6 11:54:00 2011
Return-Path: <ulrich@herberg.name>
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 996A721F8D6B for <manet@ietfa.amsl.com>; Tue,  6 Sep 2011 11:54:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.923
X-Spam-Level: 
X-Spam-Status: No, score=-2.923 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 Rssg54Uy9w1J for <manet@ietfa.amsl.com>; Tue,  6 Sep 2011 11:53:59 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7E76E21F8D6A for <manet@ietf.org>; Tue,  6 Sep 2011 11:53:59 -0700 (PDT)
Received: by vxi29 with SMTP id 29so78299vxi.31 for <manet@ietf.org>; Tue, 06 Sep 2011 11:55:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BG2r4qFPfkL8AaZGjWno5RVt/9bJLa1TPfbP65ToFeI=; b=d68mSSUYKglM6W/0mtd7wbse+E2SINdhEeXqREdRC8eAzIzpn6/hL7UxzNTPoEDrGW RXpVmVrPHC6vNnuO8MH/9i1hOm5SZraNryVAAYnQCSiPW5DlFGSXnfzy3OzcLH2Lao0P O8PLKIVl58lULTilDqX8LRDkAobu4YAD4jeIo=
MIME-Version: 1.0
Received: by 10.220.148.208 with SMTP id q16mr1488566vcv.141.1315335346403; Tue, 06 Sep 2011 11:55:46 -0700 (PDT)
Received: by 10.220.51.130 with HTTP; Tue, 6 Sep 2011 11:55:46 -0700 (PDT)
In-Reply-To: <20110906181937.14107.17176.idtracker@ietfa.amsl.com>
References: <20110906181937.14107.17176.idtracker@ietfa.amsl.com>
Date: Tue, 6 Sep 2011 11:55:46 -0700
Message-ID: <CAK=bVC_c_f7QcPUUhVGW7tqp6Aqa3sYn+KYvEoXQ0q_4GA=cqA@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: manet@ietf.org
Content-Type: multipart/alternative; boundary=f46d0438950f15386d04ac4a601e
Cc: Thomas Clausen <thomas@thomasclausen.org>
Subject: Re: [manet] I-D Action: draft-ietf-manet-packetbb-sec-06.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2011 18:54:00 -0000

--f46d0438950f15386d04ac4a601e
Content-Type: text/plain; charset=ISO-8859-1

Hi,

we have updated packetbb-sec. There are no changes to the specification,
just some editorial edits. Notably, we have moved an appendix section into
the main part of the document, as it contains normative specifications. We
believe the document is ready for a new WG LC.

Regards
Ulrich

On Tue, Sep 6, 2011 at 11:19 AM, <internet-drafts@ietf.org> wrote:

> 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           : MANET Cryptographical Signature TLV Definition
>        Author(s)       : Ulrich Herberg
>                          Thomas Heide Clausen
>        Filename        : draft-ietf-manet-packetbb-sec-06.txt
>        Pages           : 17
>        Date            : 2011-09-06
>
>   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
>   [RFC5444].  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.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-manet-packetbb-sec-06.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-packetbb-sec-06.txt
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--f46d0438950f15386d04ac4a601e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>we have updated packetbb-sec. There are no changes to the specif=
ication, just some editorial edits. Notably, we have moved an appendix sect=
ion into the main part of the document, as it contains normative specificat=
ions. We believe the document is ready for a new WG LC.<br>
<br>Regards<br>Ulrich<br><br><div class=3D"gmail_quote">On Tue, Sep 6, 2011=
 at 11:19 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf=
.org">internet-drafts@ietf.org</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
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.<br>
<br>
 =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : MANET Cryptographical Signature=
 TLV Definition<br>
 =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Ulrich Herberg<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Thomas Heide Clausen<br=
>
 =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-manet-packetbb-sec-06.=
txt<br>
 =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 17<br>
 =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-09-06<br>
<br>
 =A0 This document describes general and flexible TLVs (type-length-value<b=
r>
 =A0 structure) for representing cryptographic signatures as well as<br>
 =A0 timestamps, using the generalized MANET packet/message format<br>
 =A0 [RFC5444]. =A0It defines two Packet TLVs, two Message TLVs, and two<br=
>
 =A0 Address Block TLVs, for affixing cryptographic signatures and<br>
 =A0 timestamps to a packet, message and address, respectively.<br>
<br>
<br>
A URL for this Internet-Draft is:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-manet-packetbb-se=
c-06.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-=
manet-packetbb-sec-06.txt</a><br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
This Internet-Draft can be retrieved at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/draft-ietf-manet-packetbb-sec=
-06.txt" target=3D"_blank">ftp://ftp.ietf.org/internet-drafts/draft-ietf-ma=
net-packetbb-sec-06.txt</a><br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br>

--f46d0438950f15386d04ac4a601e--

From ulrich@herberg.name  Tue Sep  6 11:55:31 2011
Return-Path: <ulrich@herberg.name>
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 D0FA721F8D75 for <manet@ietfa.amsl.com>; Tue,  6 Sep 2011 11:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.926
X-Spam-Level: 
X-Spam-Status: No, score=-2.926 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 FfBpubjJCZPk for <manet@ietfa.amsl.com>; Tue,  6 Sep 2011 11:55:31 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1172921F8D6B for <manet@ietf.org>; Tue,  6 Sep 2011 11:55:30 -0700 (PDT)
Received: by vws12 with SMTP id 12so6080069vws.31 for <manet@ietf.org>; Tue, 06 Sep 2011 11:57:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9LGs4aS38FVeCcRZ31Pi0uofZnwye6fG5dyMBt7wCW8=; b=N2OYKb68zrDm04UphTHsKSC/VI8VM5YDBDlhlGtCsxDNxqWEwBEYN/ccqL64cdoiri foAlOvRxU0uQgqcVsPF0zX2Xk/v+R5Hu23SYURAhxW+fvfI0ZKtZwHzJuFBG0YRgYeZe vE2yKkzEs/2fC2rvDRu5dAaXUyo2gAYrQJ+Q4=
MIME-Version: 1.0
Received: by 10.220.172.7 with SMTP id j7mr1482090vcz.246.1315335437153; Tue, 06 Sep 2011 11:57:17 -0700 (PDT)
Received: by 10.220.51.130 with HTTP; Tue, 6 Sep 2011 11:57:17 -0700 (PDT)
In-Reply-To: <20110906184737.21836.18828.idtracker@ietfa.amsl.com>
References: <20110906184737.21836.18828.idtracker@ietfa.amsl.com>
Date: Tue, 6 Sep 2011 11:57:17 -0700
Message-ID: <CAK=bVC9XbHA4DVHPF_3ipEDjRmqsa2BMfnx0_=3k+eHDSYPcNw@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: manet@ietf.org
Content-Type: multipart/alternative; boundary=0016e65da5167df62504ac4a6557
Cc: "Robert G. Cole" <rgcole01@comcast.net>
Subject: Re: [manet] I-D Action: draft-ietf-manet-nhdp-mib-10.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2011 18:55:31 -0000

--0016e65da5167df62504ac4a6557
Content-Type: text/plain; charset=ISO-8859-1

Hi,

we have updated the NHDP-MIB. In particular, we have removed the reference
to the REPORT-MIB, as discussed in the last IETF meeting. We believe the
document is ready for a new WG LC.

Regards
Ulrich

On Tue, Sep 6, 2011 at 11:47 AM, <internet-drafts@ietf.org> wrote:

> 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 the Neighborhood
> Discovery Protocol
>        Author(s)       : Ulrich Herberg
>                          Robert G. Cole
>                          Ian D Chakeres
>        Filename        : draft-ietf-manet-nhdp-mib-10.txt
>        Pages           : 67
>        Date            : 2011-09-06
>
>   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 parameters of the
>   Neighborhood Discovery Protocol (NHDP) process on a router.  The MIB
>   defined in this memo, denoted NHDP-MIB, also reports state,
>   performance information and notifications.  This additional state and
>   performance information is useful to troubleshoot problems and
>   performance issues during neighbor discovery.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-manet-nhdp-mib-10.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-nhdp-mib-10.txt
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--0016e65da5167df62504ac4a6557
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br>
<br>
we have updated the NHDP-MIB. In particular, we have removed the reference =
to the REPORT-MIB, as discussed in the last IETF meeting. We believe the do=
cument is ready for a new WG LC.<br>
<br>
Regards<br>
Ulrich<br><br><div class=3D"gmail_quote">On Tue, Sep 6, 2011 at 11:47 AM,  =
<span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-=
drafts@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
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.<br>
<br>
 =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Definition of Managed Objects f=
or the Neighborhood Discovery Protocol<br>
 =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Ulrich Herberg<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Robert G. Cole<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Ian D Chakeres<br>
 =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-manet-nhdp-mib-10.txt<=
br>
 =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 67<br>
 =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-09-06<br>
<br>
 =A0 This memo defines a portion of the Management Information Base (MIB)<b=
r>
 =A0 for use with network management protocols in the Internet community.<b=
r>
 =A0 In particular, it describes objects for configuring parameters of the<=
br>
 =A0 Neighborhood Discovery Protocol (NHDP) process on a router. =A0The MIB=
<br>
 =A0 defined in this memo, denoted NHDP-MIB, also reports state,<br>
 =A0 performance information and notifications. =A0This additional state an=
d<br>
 =A0 performance information is useful to troubleshoot problems and<br>
 =A0 performance issues during neighbor discovery.<br>
<br>
<br>
A URL for this Internet-Draft is:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-manet-nhdp-mib-10=
.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-mane=
t-nhdp-mib-10.txt</a><br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
This Internet-Draft can be retrieved at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/draft-ietf-manet-nhdp-mib-10.=
txt" target=3D"_blank">ftp://ftp.ietf.org/internet-drafts/draft-ietf-manet-=
nhdp-mib-10.txt</a><br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br>

--0016e65da5167df62504ac4a6557--

From adrian@olddog.co.uk  Wed Sep 14 09:35:42 2011
Return-Path: <adrian@olddog.co.uk>
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 A30B121F8B84 for <manet@ietfa.amsl.com>; Wed, 14 Sep 2011 09:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.932
X-Spam-Level: 
X-Spam-Status: No, score=-2.932 tagged_above=-999 required=5 tests=[AWL=-0.333, 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 DsQAfPbPYfS7 for <manet@ietfa.amsl.com>; Wed, 14 Sep 2011 09:35:42 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id CE26B21F8B53 for <manet@ietf.org>; Wed, 14 Sep 2011 09:35:41 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id p8EGblQ0001689;  Wed, 14 Sep 2011 17:37:47 +0100
Received: from 950129200 (westford-nat.juniper.net [66.129.232.2]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id p8EGbjm4001683 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 14 Sep 2011 17:37:46 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <manet@ietf.org>
Date: Wed, 14 Sep 2011 17:37:47 +0100
Message-ID: <032d01cc72fc$a3d4a950$eb7dfbf0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Acxy/J5q7s/Md0ouSCeH5b26XmPdRg==
Content-Language: en-gb
Cc: 'Stan Ratliff' <sratliff@cisco.com>
Subject: [manet] New co-chair
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2011 16:35:42 -0000

Hi MANET,

As previously discussed, Ian Chakeres has announced his desire to step down as
co-chair.

I have appointed Stan Ratliff as your new co-chair to work with Joe Macker.

Can I take this opportunity to thank Ian for all his work and leadership over
the years.

Thanks,
Adrian


From vkaul@research.telcordia.com  Wed Sep 14 09:43:34 2011
Return-Path: <vkaul@research.telcordia.com>
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 D9C6F21F8B68 for <manet@ietfa.amsl.com>; Wed, 14 Sep 2011 09:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_TOOL=2.3]
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 RUPpwU42tYdX for <manet@ietfa.amsl.com>; Wed, 14 Sep 2011 09:43:33 -0700 (PDT)
Received: from flower.research.telcordia.com (flower.research.telcordia.com [128.96.41.5]) by ietfa.amsl.com (Postfix) with ESMTP id 706E421F8ABD for <manet@ietf.org>; Wed, 14 Sep 2011 09:43:33 -0700 (PDT)
Received: from vkaul7-t61.research.telcordia.com (vpntnlA77.research.telcordia.com [128.96.58.77]) by flower.research.telcordia.com (8.14.2/8.14.2) with ESMTP id p8EGjgdv017954 for <manet@ietf.org>; Wed, 14 Sep 2011 12:45:42 -0400 (EDT)
Date: Wed, 14 Sep 2011 12:45:40 -0400 (Eastern Daylight Time)
From: Vikram KAUL <vkaul@research.telcordia.com>
To: manet@ietf.org
In-Reply-To: <3D05610F3AC2E047AACAA68F63DF908D345B1AA01A@EXMBX13.exchhosting.com>
Message-ID: <alpine.WNT.2.01.1109141241400.3140@vkaul7-t61>
References: <alpine.WNT.2.01.1108151053430.5496@vkaul7-t61> <3D05610F3AC2E047AACAA68F63DF908D345B1AA01A@EXMBX13.exchhosting.com>
User-Agent: Alpine 2.01 (WNT 1266 2009-07-14)
X-X-Sender: vkaul@mailee.research.telcordia.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [manet] DLEP and broadcast/multicast
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2011 16:43:35 -0000

Reviving this old thread....

Is there any interest in the details of the messages below. I believe that 
the specifications would be more complete if we include some version of 
broadcast/multicast.

Perhaps the dlep_tools software could also be modified to handle the 
upgraded specifications as a proof of concept

Vikram

On Mon, 15 Aug 2011, A. Riley Eller wrote:

> Date: Mon, 15 Aug 2011 10:01:47 -0700
> From: A. Riley Eller <reller@cococorp.com>
> To: Vikram KAUL <vkaul@research.telcordia.com>,
>     "manet@ietf.org" <manet@ietf.org>
> Subject: RE: [manet] DLEP and broadcast/multicast
> 
> Perhaps the DLEP specification would benefit from accepting a pseudo-link identifier for multicast messages?
>
> My team's research shows that EFT implementations achieve higher overall accuracy by measuring multicast messages as a universal estimator for queuing-plus-congestion. Giving DLEP the ability to describe that value, and also gaining the ability to control the radio's performance for multicast traffic, would be a valuable addition.
>
>
> -----Original Message-----
> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Vikram KAUL
> Sent: Monday, August 15, 2011 8:15 AM
> To: manet@ietf.org
> Subject: [manet] DLEP and broadcast/multicast
>
>
> Folks
>
>  I have some questions about how DLEP handles multicast/broadcast traffic
> and the intents that the router might have to send to the modem device.
> Some of this might have been answered; but I couldn't find it in the
> archives
>
>  The inherent nature of DLEP seems focused on neighbor relationships and
> link characteristics (MDR, CDR, Latency, etc) are focused on individual
> neighbors as identifed by the 'MAC Address Sub-TLV' which is mandatory in
> most of the messages
>
>  My question is related to broadcast and/or multicast traffic that would
> emanate from a router. Let us presume that the underlying multicast
> protocol is SMF for ease of discussion... but it could be anything that
> forwards native multicast packets, either via flooding or after creating
> trees.
>
>  How can one use DLEP to specify the MDR/CDR or latency requirements for
> those flows ? Is it even possible to do so ? I understand how one could do
> it for individual links to neighbors. But if I presume that multicast and
> broadcast is the predominant traffic (say 70%-80%, and I don't believe I
> am wrong about that), how can one use DLEP   "Link Characteristics Request
> Message" to specify that traffic to a particular MAC address should be
> able to get at least what is specified by the CDR Sub-TLV
>
>  Typically (but not always) MAC addresses for multicast IP packets are set
> to  01:00:xx:yy:zz:aa for a destination multicast address of xx.yy.zz.aa.
> Could one not have that 01:00:xx:yy:zz:aa MAC Address Sub-TLV so that the
> modem could identify that traffic to that MAC Address (and hence traffic
> to that destination multicast IP address) needs to get at least that data
> rate. How the modems would achieve that is a separate question, but DLEP
> does not delve into those answers anyway
>
>  Again, it might be that the charter for DLEP is to focus specifically on
> one-to-one relationships (and hence one-to-one specifications and
> conditions). Could the specs not be augmented to support something on
> one-to-many specifications ? Just thinking aloud.
>
> regards..
> Vikram
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

From sratliff@cisco.com  Wed Sep 14 09:44:45 2011
Return-Path: <sratliff@cisco.com>
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 3DC3921F8BB2 for <manet@ietfa.amsl.com>; Wed, 14 Sep 2011 09:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.23
X-Spam-Level: 
X-Spam-Status: No, score=-1.23 tagged_above=-999 required=5 tests=[AWL=-3.531,  BAYES_50=0.001, MANGLED_TOOL=2.3]
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 BRBZSfTDgeFZ for <manet@ietfa.amsl.com>; Wed, 14 Sep 2011 09:44:44 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 8024521F8BB6 for <manet@ietf.org>; Wed, 14 Sep 2011 09:44:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sratliff@cisco.com; l=4187; q=dns/txt; s=iport; t=1316018814; x=1317228414; h=cc:message-id:from:to:in-reply-to: content-transfer-encoding:mime-version:subject:date: references; bh=iJIKr3yGIPGlo+YsqYFzgq6DJBVtVy4wZ1UaH0juWV8=; b=Sda+RrGeq1BkMb4iszZMq8HQWZmvaugCFkrMqqYGFodJgQT2esFbZvQ6 TeWOZrVcgR3BTKBLFhdyihMCoWG2u4Ei05gFOKxXcKPvOfTECZo2IbZ8Y 7Nbt5Wj6w+O4GGmK8nEOvOYKWlhk8CvB2CM6hYMLpkbF2F+g1q78aD+bZ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ar4AAKfZcE6tJXG//2dsb2JhbAA3Cphsjnt4gVMBAQEBAgEBAQEPASUCMgIEBwwECxEDAQEBAScHJx8JCAYTIodVBJZqAZ5Pg0eCR2AEkz+RQQ
X-IronPort-AV: E=Sophos;i="4.68,381,1312156800"; d="scan'208";a="21460939"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-3.cisco.com with ESMTP; 14 Sep 2011 16:46:53 +0000
Received: from nom27158d.nomadic.ncsu.edu (rtp-vpn6-216.cisco.com [10.82.248.216]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id p8EGkqqr014627;  Wed, 14 Sep 2011 16:46:53 GMT
Message-Id: <A9C264D6-45DD-4ADA-B911-4EB4E963FE61@cisco.com>
From: Stan Ratliff <sratliff@cisco.com>
To: Vikram KAUL <vkaul@research.telcordia.com>
In-Reply-To: <alpine.WNT.2.01.1109141241400.3140@vkaul7-t61>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 14 Sep 2011 12:46:55 -0400
References: <alpine.WNT.2.01.1108151053430.5496@vkaul7-t61> <3D05610F3AC2E047AACAA68F63DF908D345B1AA01A@EXMBX13.exchhosting.com> <alpine.WNT.2.01.1109141241400.3140@vkaul7-t61>
X-Mailer: Apple Mail (2.936)
Cc: manet@ietf.org
Subject: Re: [manet] DLEP and broadcast/multicast
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2011 16:44:45 -0000

Vikram,

Yes, there is interest amongst the DLEP co-authors to include  
broadcast/multicast. Do you have any specific ideas?

Regards,
Stan

On Sep 14, 2011, at 12:45 PM, Vikram KAUL wrote:

>
> Reviving this old thread....
>
> Is there any interest in the details of the messages below. I  
> believe that the specifications would be more complete if we include  
> some version of broadcast/multicast.
>
> Perhaps the dlep_tools software could also be modified to handle the  
> upgraded specifications as a proof of concept
>
> Vikram
>
> On Mon, 15 Aug 2011, A. Riley Eller wrote:
>
>> Date: Mon, 15 Aug 2011 10:01:47 -0700
>> From: A. Riley Eller <reller@cococorp.com>
>> To: Vikram KAUL <vkaul@research.telcordia.com>,
>>    "manet@ietf.org" <manet@ietf.org>
>> Subject: RE: [manet] DLEP and broadcast/multicast
>> Perhaps the DLEP specification would benefit from accepting a  
>> pseudo-link identifier for multicast messages?
>>
>> My team's research shows that EFT implementations achieve higher  
>> overall accuracy by measuring multicast messages as a universal  
>> estimator for queuing-plus-congestion. Giving DLEP the ability to  
>> describe that value, and also gaining the ability to control the  
>> radio's performance for multicast traffic, would be a valuable  
>> addition.
>>
>>
>> -----Original Message-----
>> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On  
>> Behalf Of Vikram KAUL
>> Sent: Monday, August 15, 2011 8:15 AM
>> To: manet@ietf.org
>> Subject: [manet] DLEP and broadcast/multicast
>>
>>
>> Folks
>>
>> I have some questions about how DLEP handles multicast/broadcast  
>> traffic
>> and the intents that the router might have to send to the modem  
>> device.
>> Some of this might have been answered; but I couldn't find it in the
>> archives
>>
>> The inherent nature of DLEP seems focused on neighbor relationships  
>> and
>> link characteristics (MDR, CDR, Latency, etc) are focused on  
>> individual
>> neighbors as identifed by the 'MAC Address Sub-TLV' which is  
>> mandatory in
>> most of the messages
>>
>> My question is related to broadcast and/or multicast traffic that  
>> would
>> emanate from a router. Let us presume that the underlying multicast
>> protocol is SMF for ease of discussion... but it could be anything  
>> that
>> forwards native multicast packets, either via flooding or after  
>> creating
>> trees.
>>
>> How can one use DLEP to specify the MDR/CDR or latency requirements  
>> for
>> those flows ? Is it even possible to do so ? I understand how one  
>> could do
>> it for individual links to neighbors. But if I presume that  
>> multicast and
>> broadcast is the predominant traffic (say 70%-80%, and I don't  
>> believe I
>> am wrong about that), how can one use DLEP   "Link Characteristics  
>> Request
>> Message" to specify that traffic to a particular MAC address should  
>> be
>> able to get at least what is specified by the CDR Sub-TLV
>>
>> Typically (but not always) MAC addresses for multicast IP packets  
>> are set
>> to  01:00:xx:yy:zz:aa for a destination multicast address of  
>> xx.yy.zz.aa.
>> Could one not have that 01:00:xx:yy:zz:aa MAC Address Sub-TLV so  
>> that the
>> modem could identify that traffic to that MAC Address (and hence  
>> traffic
>> to that destination multicast IP address) needs to get at least  
>> that data
>> rate. How the modems would achieve that is a separate question, but  
>> DLEP
>> does not delve into those answers anyway
>>
>> Again, it might be that the charter for DLEP is to focus  
>> specifically on
>> one-to-one relationships (and hence one-to-one specifications and
>> conditions). Could the specs not be augmented to support something on
>> one-to-many specifications ? Just thinking aloud.
>>
>> regards..
>> Vikram
>> _______________________________________________
>> 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 joseph.macker@nrl.navy.mil  Wed Sep 14 11:56:33 2011
Return-Path: <joseph.macker@nrl.navy.mil>
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 BF75021F8C11 for <manet@ietfa.amsl.com>; Wed, 14 Sep 2011 11:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.149
X-Spam-Level: 
X-Spam-Status: No, score=-4.149 tagged_above=-999 required=5 tests=[AWL=-2.450, BAYES_50=0.001, MANGLED_TOOL=2.3, 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 ugjTn5mM3Ux8 for <manet@ietfa.amsl.com>; Wed, 14 Sep 2011 11:56:33 -0700 (PDT)
Received: from s2.itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3]) by ietfa.amsl.com (Postfix) with ESMTP id F38E521F8B0D for <manet@ietf.org>; Wed, 14 Sep 2011 11:56:32 -0700 (PDT)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.13.8/8.13.8) with SMTP id p8EIwYDh031650; Wed, 14 Sep 2011 14:58:38 -0400
Received: from vpn217206.nrl.navy.mil ([132.250.217.206]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.16.48) with SMTP id M2011091414583718062 ; Wed, 14 Sep 2011 14:58:37 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joe Macker <joseph.macker@nrl.navy.mil>
In-Reply-To: <A9C264D6-45DD-4ADA-B911-4EB4E963FE61@cisco.com>
Date: Wed, 14 Sep 2011 14:58:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0F2CDB1-0168-4C38-9675-B1CC6025DA0E@nrl.navy.mil>
References: <alpine.WNT.2.01.1108151053430.5496@vkaul7-t61> <3D05610F3AC2E047AACAA68F63DF908D345B1AA01A@EXMBX13.exchhosting.com> <alpine.WNT.2.01.1109141241400.3140@vkaul7-t61> <A9C264D6-45DD-4ADA-B911-4EB4E963FE61@cisco.com>
To: Stan Ratliff <sratliff@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: manet@ietf.org
Subject: Re: [manet] DLEP and broadcast/multicast
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2011 18:56:33 -0000

I realize there are some specific sub areas being discussed here but I =
also feel lower layer wireless designs will have more general =
performance and flow control issues related to multicast/broadcast =
interaction.

I think we could author some core framework in this area that could be =
useful.  A requirements/motivation discussion might be a good first =
step.


> Vikram,
>=20
> Yes, there is interest amongst the DLEP co-authors to include =
broadcast/multicast. Do you have any specific ideas?
>=20
> Regards,
> Stan
>=20
> On Sep 14, 2011, at 12:45 PM, Vikram KAUL wrote:
>=20
>>=20
>> Reviving this old thread....
>>=20
>> Is there any interest in the details of the messages below. I believe =
that the specifications would be more complete if we include some =
version of broadcast/multicast.
>>=20
>> Perhaps the dlep_tools software could also be modified to handle the =
upgraded specifications as a proof of concept
>>=20
>> Vikram
>>=20
>> On Mon, 15 Aug 2011, A. Riley Eller wrote:
>>=20
>>> Date: Mon, 15 Aug 2011 10:01:47 -0700
>>> From: A. Riley Eller <reller@cococorp.com>
>>> To: Vikram KAUL <vkaul@research.telcordia.com>,
>>>   "manet@ietf.org" <manet@ietf.org>
>>> Subject: RE: [manet] DLEP and broadcast/multicast
>>> Perhaps the DLEP specification would benefit from accepting a =
pseudo-link identifier for multicast messages?
>>>=20
>>> My team's research shows that EFT implementations achieve higher =
overall accuracy by measuring multicast messages as a universal =
estimator for queuing-plus-congestion. Giving DLEP the ability to =
describe that value, and also gaining the ability to control the radio's =
performance for multicast traffic, would be a valuable addition.
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On =
Behalf Of Vikram KAUL
>>> Sent: Monday, August 15, 2011 8:15 AM
>>> To: manet@ietf.org
>>> Subject: [manet] DLEP and broadcast/multicast
>>>=20
>>>=20
>>> Folks
>>>=20
>>> I have some questions about how DLEP handles multicast/broadcast =
traffic
>>> and the intents that the router might have to send to the modem =
device.
>>> Some of this might have been answered; but I couldn't find it in the
>>> archives
>>>=20
>>> The inherent nature of DLEP seems focused on neighbor relationships =
and
>>> link characteristics (MDR, CDR, Latency, etc) are focused on =
individual
>>> neighbors as identifed by the 'MAC Address Sub-TLV' which is =
mandatory in
>>> most of the messages
>>>=20
>>> My question is related to broadcast and/or multicast traffic that =
would
>>> emanate from a router. Let us presume that the underlying multicast
>>> protocol is SMF for ease of discussion... but it could be anything =
that
>>> forwards native multicast packets, either via flooding or after =
creating
>>> trees.
>>>=20
>>> How can one use DLEP to specify the MDR/CDR or latency requirements =
for
>>> those flows ? Is it even possible to do so ? I understand how one =
could do
>>> it for individual links to neighbors. But if I presume that =
multicast and
>>> broadcast is the predominant traffic (say 70%-80%, and I don't =
believe I
>>> am wrong about that), how can one use DLEP   "Link Characteristics =
Request
>>> Message" to specify that traffic to a particular MAC address should =
be
>>> able to get at least what is specified by the CDR Sub-TLV
>>>=20
>>> Typically (but not always) MAC addresses for multicast IP packets =
are set
>>> to  01:00:xx:yy:zz:aa for a destination multicast address of =
xx.yy.zz.aa.
>>> Could one not have that 01:00:xx:yy:zz:aa MAC Address Sub-TLV so =
that the
>>> modem could identify that traffic to that MAC Address (and hence =
traffic
>>> to that destination multicast IP address) needs to get at least that =
data
>>> rate. How the modems would achieve that is a separate question, but =
DLEP
>>> does not delve into those answers anyway
>>>=20
>>> Again, it might be that the charter for DLEP is to focus =
specifically on
>>> one-to-one relationships (and hence one-to-one specifications and
>>> conditions). Could the specs not be augmented to support something =
on
>>> one-to-many specifications ? Just thinking aloud.
>>>=20
>>> regards..
>>> Vikram
>>> _______________________________________________
>>> 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
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>=20


From touch@isi.edu  Wed Sep 14 16:31:40 2011
Return-Path: <touch@isi.edu>
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 5371721F8B78; Wed, 14 Sep 2011 16:31:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.163
X-Spam-Level: 
X-Spam-Status: No, score=-105.163 tagged_above=-999 required=5 tests=[AWL=1.436, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 yD7wX-Vov+G0; Wed, 14 Sep 2011 16:31:39 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id D470421F8B77; Wed, 14 Sep 2011 16:31:39 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p8ENXN2u022606 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Sep 2011 16:33:23 -0700 (PDT)
Message-ID: <4E7139C3.3010905@isi.edu>
Date: Wed, 14 Sep 2011 16:33:23 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: Joe Macker <joseph.macker@nrl.navy.mil>
References: <DEC49BE6-4A03-4A6C-B50E-35CA8794E4E5@inf-net.nl> <4B71EC55-1D87-43CA-8C7A-B6552C23D600@nrl.navy.mil>
In-Reply-To: <4B71EC55-1D87-43CA-8C7A-B6552C23D600@nrl.navy.mil>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: MANET IETF <manet@ietf.org>, int-area@ietf.org
Subject: Re: [manet] [Int-area]  SMF and intarea-ipv4-id-update
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2011 23:31:40 -0000

Hi, all,

I'm getting back to updating this doc, and wanted to come back to this 
issue...

Is there a reason why the mechanism proposed for IPv6 (which does not 
reliably include an ID field) is insufficient for IPv4?

Joe

On 3/30/2011 7:10 AM, Joe Macker wrote:
> Yes this is an optional duplicate detection scheme and is an example of use in practice.
>
> Also As Teco mentioned this intended for limited use in edge network multicast systems.
>
> On Mar 30, 2011, at 1:29 PM, Teco Boot wrote:
>
>> Sorry for x-posting. But there is a conflict in:
>> http://tools.ietf.org/html/draft-ietf-manet-smf
>> http://tools.ietf.org/html/draft-ietf-intarea-ipv4-id-update
>>
>> SMF has a duplicate packet detection function based on the IPv4
>> ID field. So text in ietf-intarea-ipv4-id-update section 4
>> is not correct, in that there would be no deployments for such.
>> That said, SMF deployment with IPv4 DPD on IP-ID would be limited.
>>
>> What to do?
>>
>> Teco
>>
>>
>>
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

From reller@cococorp.com  Sat Sep 17 12:01:08 2011
Return-Path: <reller@cococorp.com>
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 62AF821F8841 for <manet@ietfa.amsl.com>; Sat, 17 Sep 2011 12:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.201
X-Spam-Level: 
X-Spam-Status: No, score=0.201 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, MANGLED_TOOL=2.3]
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 NAO+f6bNjkKf for <manet@ietfa.amsl.com>; Sat, 17 Sep 2011 12:01:07 -0700 (PDT)
Received: from EXHUB04.exchhosting.com (exchla3.liveoffice.com [64.70.67.188]) by ietfa.amsl.com (Postfix) with ESMTP id B68CD21F87F0 for <manet@ietf.org>; Sat, 17 Sep 2011 12:01:07 -0700 (PDT)
Received: from EXMBX13.exchhosting.com ([fe80::34:7540:6989:7b8d]) by EXHUB04.exchhosting.com ([fe80::e08b:16b6:14a0:73b0%12]) with mapi; Thu, 15 Sep 2011 14:08:42 -0700
From: "A. Riley Eller" <reller@cococorp.com>
To: Joe Macker <joseph.macker@nrl.navy.mil>, Stan Ratliff <sratliff@cisco.com>
Date: Thu, 15 Sep 2011 14:08:40 -0700
Thread-Topic: [manet] DLEP and broadcast/multicast
Thread-Index: AcxzEFsrGN3KwFXZTYWBIjAPqXy5YQA2bp1g
Message-ID: <3D05610F3AC2E047AACAA68F63DF908D345B93FA0D@EXMBX13.exchhosting.com>
References: <alpine.WNT.2.01.1108151053430.5496@vkaul7-t61> <3D05610F3AC2E047AACAA68F63DF908D345B1AA01A@EXMBX13.exchhosting.com> <alpine.WNT.2.01.1109141241400.3140@vkaul7-t61> <A9C264D6-45DD-4ADA-B911-4EB4E963FE61@cisco.com> <B0F2CDB1-0168-4C38-9675-B1CC6025DA0E@nrl.navy.mil>
In-Reply-To: <B0F2CDB1-0168-4C38-9675-B1CC6025DA0E@nrl.navy.mil>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] DLEP and broadcast/multicast
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Sep 2011 19:01:08 -0000

Just to be clear, the request I filed below is only to measure the latency =
for these packets. The goal is to provide an approximation for some EFT var=
iables. The value returned does not even need to come from multicast packet=
s. For instance, in Wi-Fi, measuring the receipt-through-first-transmission=
 duration of unicast packets would be an equivalent indicator.

The idea here is to offer the router distinct latency views of access to th=
e medium and each peer. For each peer, the total link latency will be (late=
ncy of access to the medium scaled by expected latency of retransmission to=
 that peer). The first term of that clause was my intended goal, and might =
be well approximated by an exponential moving weighted average of forwardin=
g time of multicast/broadcast packets.

Hopefully some of those concepts will help to shape the motivation discussi=
on.

-----Original Message-----
From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of J=
oe Macker
Sent: Wednesday, September 14, 2011 11:59 AM
To: Stan Ratliff
Cc: manet@ietf.org
Subject: Re: [manet] DLEP and broadcast/multicast

I realize there are some specific sub areas being discussed here but I also=
 feel lower layer wireless designs will have more general performance and f=
low control issues related to multicast/broadcast interaction.

I think we could author some core framework in this area that could be usef=
ul.  A requirements/motivation discussion might be a good first step.


> Vikram,
>=20
> Yes, there is interest amongst the DLEP co-authors to include broadcast/m=
ulticast. Do you have any specific ideas?
>=20
> Regards,
> Stan
>=20
> On Sep 14, 2011, at 12:45 PM, Vikram KAUL wrote:
>=20
>>=20
>> Reviving this old thread....
>>=20
>> Is there any interest in the details of the messages below. I believe th=
at the specifications would be more complete if we include some version of =
broadcast/multicast.
>>=20
>> Perhaps the dlep_tools software could also be modified to handle the upg=
raded specifications as a proof of concept
>>=20
>> Vikram
>>=20
>> On Mon, 15 Aug 2011, A. Riley Eller wrote:
>>=20
>>> Date: Mon, 15 Aug 2011 10:01:47 -0700
>>> From: A. Riley Eller <reller@cococorp.com>
>>> To: Vikram KAUL <vkaul@research.telcordia.com>,
>>>   "manet@ietf.org" <manet@ietf.org>
>>> Subject: RE: [manet] DLEP and broadcast/multicast
>>> Perhaps the DLEP specification would benefit from accepting a pseudo-li=
nk identifier for multicast messages?
>>>=20
>>> My team's research shows that EFT implementations achieve higher overal=
l accuracy by measuring multicast messages as a universal estimator for que=
uing-plus-congestion. Giving DLEP the ability to describe that value, and a=
lso gaining the ability to control the radio's performance for multicast tr=
affic, would be a valuable addition.
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf =
Of Vikram KAUL
>>> Sent: Monday, August 15, 2011 8:15 AM
>>> To: manet@ietf.org
>>> Subject: [manet] DLEP and broadcast/multicast
>>>=20
>>>=20
>>> Folks
>>>=20
>>> I have some questions about how DLEP handles multicast/broadcast traffi=
c
>>> and the intents that the router might have to send to the modem device.
>>> Some of this might have been answered; but I couldn't find it in the
>>> archives
>>>=20
>>> The inherent nature of DLEP seems focused on neighbor relationships and
>>> link characteristics (MDR, CDR, Latency, etc) are focused on individual
>>> neighbors as identifed by the 'MAC Address Sub-TLV' which is mandatory =
in
>>> most of the messages
>>>=20
>>> My question is related to broadcast and/or multicast traffic that would
>>> emanate from a router. Let us presume that the underlying multicast
>>> protocol is SMF for ease of discussion... but it could be anything that
>>> forwards native multicast packets, either via flooding or after creatin=
g
>>> trees.
>>>=20
>>> How can one use DLEP to specify the MDR/CDR or latency requirements for
>>> those flows ? Is it even possible to do so ? I understand how one could=
 do
>>> it for individual links to neighbors. But if I presume that multicast a=
nd
>>> broadcast is the predominant traffic (say 70%-80%, and I don't believe =
I
>>> am wrong about that), how can one use DLEP   "Link Characteristics Requ=
est
>>> Message" to specify that traffic to a particular MAC address should be
>>> able to get at least what is specified by the CDR Sub-TLV
>>>=20
>>> Typically (but not always) MAC addresses for multicast IP packets are s=
et
>>> to  01:00:xx:yy:zz:aa for a destination multicast address of xx.yy.zz.a=
a.
>>> Could one not have that 01:00:xx:yy:zz:aa MAC Address Sub-TLV so that t=
he
>>> modem could identify that traffic to that MAC Address (and hence traffi=
c
>>> to that destination multicast IP address) needs to get at least that da=
ta
>>> rate. How the modems would achieve that is a separate question, but DLE=
P
>>> does not delve into those answers anyway
>>>=20
>>> Again, it might be that the charter for DLEP is to focus specifically o=
n
>>> one-to-one relationships (and hence one-to-one specifications and
>>> conditions). Could the specs not be augmented to support something on
>>> one-to-many specifications ? Just thinking aloud.
>>>=20
>>> regards..
>>> Vikram
>>> _______________________________________________
>>> 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
>=20
> _______________________________________________
> 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 sratliff@cisco.com  Mon Sep 19 08:17:06 2011
Return-Path: <sratliff@cisco.com>
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 030EC21F8BEE for <manet@ietfa.amsl.com>; Mon, 19 Sep 2011 08:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=-4.850, BAYES_50=0.001, MANGLED_TOOL=2.3]
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 Czk4iIpJK1DZ for <manet@ietfa.amsl.com>; Mon, 19 Sep 2011 08:17:05 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id BB19321F8BD5 for <manet@ietf.org>; Mon, 19 Sep 2011 08:17:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sratliff@cisco.com; l=7351; q=dns/txt; s=iport; t=1316445568; x=1317655168; h=cc:message-id:from:to:in-reply-to: content-transfer-encoding:mime-version:subject:date: references; bh=/aohA67eCkwlHlzZJ3UM90rF5Fsn+2Sn0aopC5TnsAM=; b=hyzVC/ia5XDGpykAtWl/VIaTBd2VGSc2Hm6FQ5HRxKoN1h89NraDob1u nV+t3trvhAgxLimm40IMKam/lt77aJbo4MOAKHI7UzvkUtq5afQx+mfRt KgVwfd7gsjoHgrf0O45BHZHBvW+bQQswZl8ZXkMa19rQAQ1MGHR6WqZh3 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApcAAAZdd06tJXG8/2dsb2JhbAA4CphEjmd3gVMBAQEBAgEBAQEPASUCMgICAgcFBwQLEQMBAQEBJwcnHwkIBhMih1UElycBnWyDUYJHYASTSZFJ
X-IronPort-AV: E=Sophos;i="4.68,405,1312156800"; d="scan'208";a="22452811"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 19 Sep 2011 15:19:27 +0000
Received: from dhcp-64-102-54-127.cisco.com (dhcp-64-102-54-127.cisco.com [64.102.54.127]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id p8JFJRMT009734;  Mon, 19 Sep 2011 15:19:27 GMT
Message-Id: <E158908F-67D8-414B-BB0B-FC426A7AF4AA@cisco.com>
From: Stan Ratliff <sratliff@cisco.com>
To: "A. Riley Eller" <reller@cococorp.com>
In-Reply-To: <3D05610F3AC2E047AACAA68F63DF908D345B93FA0D@EXMBX13.exchhosting.com>
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, 19 Sep 2011 11:19:32 -0400
References: <alpine.WNT.2.01.1108151053430.5496@vkaul7-t61> <3D05610F3AC2E047AACAA68F63DF908D345B1AA01A@EXMBX13.exchhosting.com> <alpine.WNT.2.01.1109141241400.3140@vkaul7-t61> <A9C264D6-45DD-4ADA-B911-4EB4E963FE61@cisco.com> <B0F2CDB1-0168-4C38-9675-B1CC6025DA0E@nrl.navy.mil> <3D05610F3AC2E047AACAA68F63DF908D345B93FA0D@EXMBX13.exchhosting.com>
X-Mailer: Apple Mail (2.936)
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] DLEP and broadcast/multicast
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2011 15:17:06 -0000

My apologies for the quick comments on this to date.

In response to Vikram's initial email, I look at a multicast MAC as  
another "destination" in the network. A destination that needs to be  
characterized from a metrics standpoint, so MCAST destinations are  
essentially a DLEP "neighbor". Cognizance of the neighbor can come  
from the radio, provided the radio is doing something like PIM  
"snooping", or it can come from the router. Because of that, we were  
going to insert language into the DLEP spec that Neighbor Up/Neighbor  
Down orders can actually come from either of the session peers (either  
the router or the modem device). If/when the modem receives a Neighbor  
Up from the router, it would be incumbent on the modem to provide  
metrics for that "destination".

Regards,
Stan


On Sep 15, 2011, at 5:08 PM, A. Riley Eller wrote:

> Just to be clear, the request I filed below is only to measure the  
> latency for these packets. The goal is to provide an approximation  
> for some EFT variables. The value returned does not even need to  
> come from multicast packets. For instance, in Wi-Fi, measuring the  
> receipt-through-first-transmission duration of unicast packets would  
> be an equivalent indicator.
>
> The idea here is to offer the router distinct latency views of  
> access to the medium and each peer. For each peer, the total link  
> latency will be (latency of access to the medium scaled by expected  
> latency of retransmission to that peer). The first term of that  
> clause was my intended goal, and might be well approximated by an  
> exponential moving weighted average of forwarding time of multicast/ 
> broadcast packets.
>
> Hopefully some of those concepts will help to shape the motivation  
> discussion.
>
> -----Original Message-----
> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On  
> Behalf Of Joe Macker
> Sent: Wednesday, September 14, 2011 11:59 AM
> To: Stan Ratliff
> Cc: manet@ietf.org
> Subject: Re: [manet] DLEP and broadcast/multicast
>
> I realize there are some specific sub areas being discussed here but  
> I also feel lower layer wireless designs will have more general  
> performance and flow control issues related to multicast/broadcast  
> interaction.
>
> I think we could author some core framework in this area that could  
> be useful.  A requirements/motivation discussion might be a good  
> first step.
>
>
>> Vikram,
>>
>> Yes, there is interest amongst the DLEP co-authors to include  
>> broadcast/multicast. Do you have any specific ideas?
>>
>> Regards,
>> Stan
>>
>> On Sep 14, 2011, at 12:45 PM, Vikram KAUL wrote:
>>
>>>
>>> Reviving this old thread....
>>>
>>> Is there any interest in the details of the messages below. I  
>>> believe that the specifications would be more complete if we  
>>> include some version of broadcast/multicast.
>>>
>>> Perhaps the dlep_tools software could also be modified to handle  
>>> the upgraded specifications as a proof of concept
>>>
>>> Vikram
>>>
>>> On Mon, 15 Aug 2011, A. Riley Eller wrote:
>>>
>>>> Date: Mon, 15 Aug 2011 10:01:47 -0700
>>>> From: A. Riley Eller <reller@cococorp.com>
>>>> To: Vikram KAUL <vkaul@research.telcordia.com>,
>>>>  "manet@ietf.org" <manet@ietf.org>
>>>> Subject: RE: [manet] DLEP and broadcast/multicast
>>>> Perhaps the DLEP specification would benefit from accepting a  
>>>> pseudo-link identifier for multicast messages?
>>>>
>>>> My team's research shows that EFT implementations achieve higher  
>>>> overall accuracy by measuring multicast messages as a universal  
>>>> estimator for queuing-plus-congestion. Giving DLEP the ability to  
>>>> describe that value, and also gaining the ability to control the  
>>>> radio's performance for multicast traffic, would be a valuable  
>>>> addition.
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On  
>>>> Behalf Of Vikram KAUL
>>>> Sent: Monday, August 15, 2011 8:15 AM
>>>> To: manet@ietf.org
>>>> Subject: [manet] DLEP and broadcast/multicast
>>>>
>>>>
>>>> Folks
>>>>
>>>> I have some questions about how DLEP handles multicast/broadcast  
>>>> traffic
>>>> and the intents that the router might have to send to the modem  
>>>> device.
>>>> Some of this might have been answered; but I couldn't find it in  
>>>> the
>>>> archives
>>>>
>>>> The inherent nature of DLEP seems focused on neighbor  
>>>> relationships and
>>>> link characteristics (MDR, CDR, Latency, etc) are focused on  
>>>> individual
>>>> neighbors as identifed by the 'MAC Address Sub-TLV' which is  
>>>> mandatory in
>>>> most of the messages
>>>>
>>>> My question is related to broadcast and/or multicast traffic that  
>>>> would
>>>> emanate from a router. Let us presume that the underlying multicast
>>>> protocol is SMF for ease of discussion... but it could be  
>>>> anything that
>>>> forwards native multicast packets, either via flooding or after  
>>>> creating
>>>> trees.
>>>>
>>>> How can one use DLEP to specify the MDR/CDR or latency  
>>>> requirements for
>>>> those flows ? Is it even possible to do so ? I understand how one  
>>>> could do
>>>> it for individual links to neighbors. But if I presume that  
>>>> multicast and
>>>> broadcast is the predominant traffic (say 70%-80%, and I don't  
>>>> believe I
>>>> am wrong about that), how can one use DLEP   "Link  
>>>> Characteristics Request
>>>> Message" to specify that traffic to a particular MAC address  
>>>> should be
>>>> able to get at least what is specified by the CDR Sub-TLV
>>>>
>>>> Typically (but not always) MAC addresses for multicast IP packets  
>>>> are set
>>>> to  01:00:xx:yy:zz:aa for a destination multicast address of  
>>>> xx.yy.zz.aa.
>>>> Could one not have that 01:00:xx:yy:zz:aa MAC Address Sub-TLV so  
>>>> that the
>>>> modem could identify that traffic to that MAC Address (and hence  
>>>> traffic
>>>> to that destination multicast IP address) needs to get at least  
>>>> that data
>>>> rate. How the modems would achieve that is a separate question,  
>>>> but DLEP
>>>> does not delve into those answers anyway
>>>>
>>>> Again, it might be that the charter for DLEP is to focus  
>>>> specifically on
>>>> one-to-one relationships (and hence one-to-one specifications and
>>>> conditions). Could the specs not be augmented to support  
>>>> something on
>>>> one-to-many specifications ? Just thinking aloud.
>>>>
>>>> regards..
>>>> Vikram
>>>> _______________________________________________
>>>> 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
>>
>> _______________________________________________
>> 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
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From reller@cococorp.com  Mon Sep 19 08:29:36 2011
Return-Path: <reller@cococorp.com>
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 31B2421F8C4A for <manet@ietfa.amsl.com>; Mon, 19 Sep 2011 08:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.376
X-Spam-Level: *
X-Spam-Status: No, score=1.376 tagged_above=-999 required=5 tests=[AWL=-0.925,  BAYES_50=0.001, MANGLED_TOOL=2.3]
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 FZoB4XZ8K+4l for <manet@ietfa.amsl.com>; Mon, 19 Sep 2011 08:29:35 -0700 (PDT)
Received: from exchange.liveoffice.com (exchla3.liveoffice.com [64.70.67.188]) by ietfa.amsl.com (Postfix) with ESMTP id 74FEB21F8C45 for <manet@ietf.org>; Mon, 19 Sep 2011 08:29:35 -0700 (PDT)
Received: from exhub13.exchhosting.com (192.168.11.122) by exhub05.exchhosting.com (192.168.11.101) with Microsoft SMTP Server (TLS) id 8.2.213.0; Mon, 19 Sep 2011 08:31:57 -0700
Received: from EXMBX13.exchhosting.com ([fe80::34:7540:6989:7b8d]) by exhub13.exchhosting.com ([::1]) with mapi; Mon, 19 Sep 2011 08:31:57 -0700
From: "A. Riley Eller" <reller@cococorp.com>
To: Stan Ratliff <sratliff@cisco.com>
Date: Mon, 19 Sep 2011 08:31:53 -0700
Thread-Topic: [manet] DLEP and broadcast/multicast
Thread-Index: Acx24UPL7a6SvHrQQbiMsvINE44vOA==
Message-ID: <CB3985EB-9F94-4901-9989-3E6B5652E415@cococorp.com>
References: <alpine.WNT.2.01.1108151053430.5496@vkaul7-t61> <3D05610F3AC2E047AACAA68F63DF908D345B1AA01A@EXMBX13.exchhosting.com> <alpine.WNT.2.01.1109141241400.3140@vkaul7-t61> <A9C264D6-45DD-4ADA-B911-4EB4E963FE61@cisco.com> <B0F2CDB1-0168-4C38-9675-B1CC6025DA0E@nrl.navy.mil> <3D05610F3AC2E047AACAA68F63DF908D345B93FA0D@EXMBX13.exchhosting.com> <E158908F-67D8-414B-BB0B-FC426A7AF4AA@cisco.com>
In-Reply-To: <E158908F-67D8-414B-BB0B-FC426A7AF4AA@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] DLEP and broadcast/multicast
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2011 15:29:36 -0000

Sounds like a fine mechanism to me.



On Sep 19, 2011, at 8:25 AM, "Stan Ratliff" <sratliff@cisco.com> wrote:

> My apologies for the quick comments on this to date.
>=20
> In response to Vikram's initial email, I look at a multicast MAC as =20
> another "destination" in the network. A destination that needs to be =20
> characterized from a metrics standpoint, so MCAST destinations are =20
> essentially a DLEP "neighbor". Cognizance of the neighbor can come =20
> from the radio, provided the radio is doing something like PIM =20
> "snooping", or it can come from the router. Because of that, we were =20
> going to insert language into the DLEP spec that Neighbor Up/Neighbor =20
> Down orders can actually come from either of the session peers (either =20
> the router or the modem device). If/when the modem receives a Neighbor =20
> Up from the router, it would be incumbent on the modem to provide =20
> metrics for that "destination".
>=20
> Regards,
> Stan
>=20
>=20
> On Sep 15, 2011, at 5:08 PM, A. Riley Eller wrote:
>=20
>> Just to be clear, the request I filed below is only to measure the =20
>> latency for these packets. The goal is to provide an approximation =20
>> for some EFT variables. The value returned does not even need to =20
>> come from multicast packets. For instance, in Wi-Fi, measuring the =20
>> receipt-through-first-transmission duration of unicast packets would =20
>> be an equivalent indicator.
>>=20
>> The idea here is to offer the router distinct latency views of =20
>> access to the medium and each peer. For each peer, the total link =20
>> latency will be (latency of access to the medium scaled by expected =20
>> latency of retransmission to that peer). The first term of that =20
>> clause was my intended goal, and might be well approximated by an =20
>> exponential moving weighted average of forwarding time of multicast/=20
>> broadcast packets.
>>=20
>> Hopefully some of those concepts will help to shape the motivation =20
>> discussion.
>>=20
>> -----Original Message-----
>> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On =20
>> Behalf Of Joe Macker
>> Sent: Wednesday, September 14, 2011 11:59 AM
>> To: Stan Ratliff
>> Cc: manet@ietf.org
>> Subject: Re: [manet] DLEP and broadcast/multicast
>>=20
>> I realize there are some specific sub areas being discussed here but =20
>> I also feel lower layer wireless designs will have more general =20
>> performance and flow control issues related to multicast/broadcast =20
>> interaction.
>>=20
>> I think we could author some core framework in this area that could =20
>> be useful.  A requirements/motivation discussion might be a good =20
>> first step.
>>=20
>>=20
>>> Vikram,
>>>=20
>>> Yes, there is interest amongst the DLEP co-authors to include =20
>>> broadcast/multicast. Do you have any specific ideas?
>>>=20
>>> Regards,
>>> Stan
>>>=20
>>> On Sep 14, 2011, at 12:45 PM, Vikram KAUL wrote:
>>>=20
>>>>=20
>>>> Reviving this old thread....
>>>>=20
>>>> Is there any interest in the details of the messages below. I =20
>>>> believe that the specifications would be more complete if we =20
>>>> include some version of broadcast/multicast.
>>>>=20
>>>> Perhaps the dlep_tools software could also be modified to handle =20
>>>> the upgraded specifications as a proof of concept
>>>>=20
>>>> Vikram
>>>>=20
>>>> On Mon, 15 Aug 2011, A. Riley Eller wrote:
>>>>=20
>>>>> Date: Mon, 15 Aug 2011 10:01:47 -0700
>>>>> From: A. Riley Eller <reller@cococorp.com>
>>>>> To: Vikram KAUL <vkaul@research.telcordia.com>,
>>>>> "manet@ietf.org" <manet@ietf.org>
>>>>> Subject: RE: [manet] DLEP and broadcast/multicast
>>>>> Perhaps the DLEP specification would benefit from accepting a =20
>>>>> pseudo-link identifier for multicast messages?
>>>>>=20
>>>>> My team's research shows that EFT implementations achieve higher =20
>>>>> overall accuracy by measuring multicast messages as a universal =20
>>>>> estimator for queuing-plus-congestion. Giving DLEP the ability to =20
>>>>> describe that value, and also gaining the ability to control the =20
>>>>> radio's performance for multicast traffic, would be a valuable =20
>>>>> addition.
>>>>>=20
>>>>>=20
>>>>> -----Original Message-----
>>>>> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On =20
>>>>> Behalf Of Vikram KAUL
>>>>> Sent: Monday, August 15, 2011 8:15 AM
>>>>> To: manet@ietf.org
>>>>> Subject: [manet] DLEP and broadcast/multicast
>>>>>=20
>>>>>=20
>>>>> Folks
>>>>>=20
>>>>> I have some questions about how DLEP handles multicast/broadcast =20
>>>>> traffic
>>>>> and the intents that the router might have to send to the modem =20
>>>>> device.
>>>>> Some of this might have been answered; but I couldn't find it in =20
>>>>> the
>>>>> archives
>>>>>=20
>>>>> The inherent nature of DLEP seems focused on neighbor =20
>>>>> relationships and
>>>>> link characteristics (MDR, CDR, Latency, etc) are focused on =20
>>>>> individual
>>>>> neighbors as identifed by the 'MAC Address Sub-TLV' which is =20
>>>>> mandatory in
>>>>> most of the messages
>>>>>=20
>>>>> My question is related to broadcast and/or multicast traffic that =20
>>>>> would
>>>>> emanate from a router. Let us presume that the underlying multicast
>>>>> protocol is SMF for ease of discussion... but it could be =20
>>>>> anything that
>>>>> forwards native multicast packets, either via flooding or after =20
>>>>> creating
>>>>> trees.
>>>>>=20
>>>>> How can one use DLEP to specify the MDR/CDR or latency =20
>>>>> requirements for
>>>>> those flows ? Is it even possible to do so ? I understand how one =20
>>>>> could do
>>>>> it for individual links to neighbors. But if I presume that =20
>>>>> multicast and
>>>>> broadcast is the predominant traffic (say 70%-80%, and I don't =20
>>>>> believe I
>>>>> am wrong about that), how can one use DLEP   "Link =20
>>>>> Characteristics Request
>>>>> Message" to specify that traffic to a particular MAC address =20
>>>>> should be
>>>>> able to get at least what is specified by the CDR Sub-TLV
>>>>>=20
>>>>> Typically (but not always) MAC addresses for multicast IP packets =20
>>>>> are set
>>>>> to  01:00:xx:yy:zz:aa for a destination multicast address of =20
>>>>> xx.yy.zz.aa.
>>>>> Could one not have that 01:00:xx:yy:zz:aa MAC Address Sub-TLV so =20
>>>>> that the
>>>>> modem could identify that traffic to that MAC Address (and hence =20
>>>>> traffic
>>>>> to that destination multicast IP address) needs to get at least =20
>>>>> that data
>>>>> rate. How the modems would achieve that is a separate question, =20
>>>>> but DLEP
>>>>> does not delve into those answers anyway
>>>>>=20
>>>>> Again, it might be that the charter for DLEP is to focus =20
>>>>> specifically on
>>>>> one-to-one relationships (and hence one-to-one specifications and
>>>>> conditions). Could the specs not be augmented to support =20
>>>>> something on
>>>>> one-to-many specifications ? Just thinking aloud.
>>>>>=20
>>>>> regards..
>>>>> Vikram
>>>>> _______________________________________________
>>>>> 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
>>>=20
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>>=20
>>=20
>> _______________________________________________
>> 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
>=20

From sratliff@cisco.com  Sat Sep 24 11:31:55 2011
Return-Path: <sratliff@cisco.com>
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 33E8421F85BB for <manet@ietfa.amsl.com>; Sat, 24 Sep 2011 11:31:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.974
X-Spam-Level: 
X-Spam-Status: No, score=-2.974 tagged_above=-999 required=5 tests=[AWL=-0.375, 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 pIzM2FwK2lGT for <manet@ietfa.amsl.com>; Sat, 24 Sep 2011 11:31:54 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 9766F21F8512 for <manet@ietf.org>; Sat, 24 Sep 2011 11:31:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sratliff@cisco.com; l=185; q=dns/txt; s=iport; t=1316889272; x=1318098872; h=message-id:from:to:content-transfer-encoding: mime-version:subject:date; bh=ZPmtcsSR7uVmtDI3y5fG8MUFjvl6bP0TAGawPIczkDM=; b=LRmtSnj5Hk73Bwo1zHxwzf9n2tfwiXpNrl2u6CIhigYGGFVQfJ4zPOxA 77zuy/eXv4G18MNRrI4YBn0zBLvINHNQI5N5n/ZKztK1WYRokL32oklBt ut0HQ32JiBosg/CaWgFjAABrn8mQKiTy661ajOjDKDS4iDSksPEHQ0LzN o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwEAAoifk6tJV2c/2dsb2JhbABCqBx4gWwBJQKBfTWhDYEmAZ0YhitgBJNSkU8
X-IronPort-AV: E=Sophos;i="4.68,435,1312156800"; d="scan'208";a="23765928"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-2.cisco.com with ESMTP; 24 Sep 2011 18:34:32 +0000
Received: from rtp-sratliff-8715.cisco.com (rtp-sratliff-8715.cisco.com [10.116.179.214]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id p8OIYVtF003793 for <manet@ietf.org>; Sat, 24 Sep 2011 18:34:32 GMT
Message-Id: <A9A97EFE-9B6F-4F23-B797-1C5C60794BA0@cisco.com>
From: Stan Ratliff <sratliff@cisco.com>
To: "manet@ietf.org IETF" <manet@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sat, 24 Sep 2011 14:34:32 -0400
X-Mailer: Apple Mail (2.936)
Subject: [manet] WGLC Review of draft-ietf-manet-packetbb-sec-06
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Sep 2011 18:31:55 -0000

All,

I've put the above mentioned draft into WGLC status. With a 2-week  
last-call window, WGLC will close on October 8. Please review the  
draft and comment.

Regards,
Stan

From sratliff@cisco.com  Sat Sep 24 11:33:57 2011
Return-Path: <sratliff@cisco.com>
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 2FE9621F8BB1 for <manet@ietfa.amsl.com>; Sat, 24 Sep 2011 11:33:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Level: 
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[AWL=-0.312, 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 XN64YkLzb6nv for <manet@ietfa.amsl.com>; Sat, 24 Sep 2011 11:33:56 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id AB15E21F8BAD for <manet@ietf.org>; Sat, 24 Sep 2011 11:33:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sratliff@cisco.com; l=163; q=dns/txt; s=iport; t=1316889394; x=1318098994; h=message-id:from:to:content-transfer-encoding: mime-version:subject:date; bh=ZUyY9QoQEaJKB9TzGAcvuQ8aKhMEuO2brpk1dVhgAV8=; b=aGvHv7kfCckK3h0Qyg4ug3cvFMKMBJfl99TpBVFjPf1yBwSps4k2e2el hsed2VMSS8IBE4eJL5kw+W6Cdk24XsjX5iGBXVtI2hBfhS6rw5vkeFEOa Eyd6g4w317BgeXA3XkEHdeUkaekOZe1upfqN+0kEkAcmwxDwB70pk6dLZ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwEAPIifk6tJV2a/2dsb2JhbABCqBx4gWwBJQKBfTWhDoEmAZ0YhitgBJNSkU8
X-IronPort-AV: E=Sophos;i="4.68,435,1312156800"; d="scan'208";a="23787216"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP; 24 Sep 2011 18:36:33 +0000
Received: from rtp-sratliff-8715.cisco.com (rtp-sratliff-8715.cisco.com [10.116.179.214]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p8OIaWFq003233 for <manet@ietf.org>; Sat, 24 Sep 2011 18:36:33 GMT
Message-Id: <5FFFAA0A-3280-4501-B200-F7304BAB7475@cisco.com>
From: Stan Ratliff <sratliff@cisco.com>
To: "manet@ietf.org IETF" <manet@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sat, 24 Sep 2011 14:36:33 -0400
X-Mailer: Apple Mail (2.936)
Subject: [manet] WGLC Review of draft-ietf-manet-nhdp-mib-10
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Sep 2011 18:33:57 -0000

All,

I have started WGLC review on the above draft. With a 2-week period,  
the last-call will end on October 8. Please review and comment.

Regards,
Stan

From fred@cisco.com  Mon Sep 26 13:54:22 2011
Return-Path: <fred@cisco.com>
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 B0EA411E810F; Mon, 26 Sep 2011 13:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.768
X-Spam-Level: 
X-Spam-Status: No, score=-102.768 tagged_above=-999 required=5 tests=[AWL=-0.169, 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 mu9EsYs15oGr; Mon, 26 Sep 2011 13:54:22 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 438D511E810E; Mon, 26 Sep 2011 13:54:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2008; q=dns/txt; s=iport; t=1317070626; x=1318280226; h=from:subject:date:message-id:to:mime-version: content-transfer-encoding; bh=DW4Kesrj8dzZGbhpYXNnmwhvGEMFefsYn/NsAlYXT34=; b=C0hnl+CsY78EvcmNqfDF5rn7EYIOmS3ZC/bc//Xb451m/SO9E3qjwANw hyzRto9rrEuVP/eV6zu8SCCZwdMyWCbANWpZh8iu46Wo4GiNKv07CzFRZ fd12yfTLYJx7QLES0Cj54pR7hI+W0ZjxZ1i/YbBTtP/kAcS7Hh0TpJJ+p 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwEAHnmgE6rRDoJ/2dsb2JhbAA4CqdueIFsASeBfQE0pA4BnjSDYYJKYASHcotghSKMMA
X-IronPort-AV: E=Sophos;i="4.68,446,1312156800";  d="scan'208";a="4413189"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 26 Sep 2011 20:57:06 +0000
Received: from Freds-Computer.local (rtp-vpn4-1556.cisco.com [10.82.214.20]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p8QKusaw002200; Mon, 26 Sep 2011 20:57:04 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Mon, 26 Sep 2011 16:57:05 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Mon, 26 Sep 2011 16:57:05 -0400
From: Fred Baker <fred@cisco.com>
Date: Mon, 26 Sep 2011 13:14:48 -0600
Message-Id: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com>
To: homenet@ietf.org, rtgwg@ietf.org, MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: [manet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Sep 2011 20:54:22 -0000

I'm trying to do a somewhat complete requirements and pro/con analysis =
for IPv6 routing in a small network, the obvious examples being =
residential and SOHO networks. What I have in pixels at this instant is:

    <section title=3D"Contestant protocols">
        <t></t>
      <section title=3D"Routing Information Protocol">
        <t></t>
      </section>
      <section title=3D"Open Shortest Path First Routing Protocol">
        <t></t>
      </section>
      <section title=3D"IS-IS Routing Protocol">
        <t></t>
      </section>
      <section title=3D"Border Gateway Protocol">
        <t></t>
      </section>
      <section title=3D"Routing Protocol for Low Power and Lossy =
Networks">
        <t></t>
      </section>
      <section title=3D"Ad hoc On-Demand Distance Vector Routing">
        <t>
Can you say "DYMO"?
        </t>
      </section>
      <section title=3D"Optimized Link State Routing Protocol">
        <t></t>
      </section>
    </section>

For some of these, the obvious comment is "YMBK". Some will feel that =
their selection is the obvious given and will be able to go on at some =
length as to why, and may be surprised to find that people disagree with =
them.=20

I'd like to do several things:
(a) make the list as reasonably complete as possible consistent with =
openly documented protocols,
(b) provide a reasonably complete and objective analysis of each as I =
can,
(c) identify the key reasons one would choose each - if there is a =
reason at all, and
(d) identify the key reasons one would not.

What I don't want to accomplish is deep-six these lists and half a dozen =
others in arguments.

Do me a favor. Let's do this in private mail. If you think of a protocol =
I should mention that I haven't, let me know. If you think there is a =
really good argument for or against any of them in particular, let me =
know. If you think I'm nuts - I already know that, you don't need to =
remind me :-)=

From pthubert@cisco.com  Wed Sep 28 04:22:42 2011
Return-Path: <pthubert@cisco.com>
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 8048B21F8C70; Wed, 28 Sep 2011 04:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.392
X-Spam-Level: 
X-Spam-Status: No, score=-10.392 tagged_above=-999 required=5 tests=[AWL=0.207, 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 Fg9TL3gyRRej; Wed, 28 Sep 2011 04:22:41 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2A8F121F8C65; Wed, 28 Sep 2011 04:22:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pthubert@cisco.com; l=3155; q=dns/txt; s=iport; t=1317209129; x=1318418729; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=uEhlyAyJ/ysELDc+oghuj6kEeJJcusswLnpUk3UZPzQ=; b=CjxJAyr9LZdeFY5f7Eq42VaANl3u4135CAwCvl6Z/3P1cEZYoDw0nSQY uT+GnWuat2xkQzFRclLqCY7YgoCXjFn1CuDQf8lssY6RU1NZre+cHnkro VVpxu8qiQk1ilKuCnE88OGA7N8HkcCR8fPDqD5P9dFLkZJIkpX3mzCUOm M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOoDg06Q/khR/2dsb2JhbABCqAZ4gVMBAQEDARIBHUkFCwIBCBIQBhgGAUgOAQEEARoah1aZcwGeNIYrYASHQpE7jAs
X-IronPort-AV: E=Sophos;i="4.68,455,1312156800"; d="scan'208";a="117634046"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 28 Sep 2011 11:25:23 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p8SBPN5W025705; Wed, 28 Sep 2011 11:25:23 GMT
Received: from xmb-ams-108.cisco.com ([144.254.74.83]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 28 Sep 2011 13:25:23 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 28 Sep 2011 13:25:22 +0200
Message-ID: <BDF2740C082F6942820D95BAEB9E1A840DBF1E@XMB-AMS-108.cisco.com>
In-Reply-To: <C16130C1-0C50-4FF9-A750-3864D21E41B6@townsley.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [homenet] Question for you
Thread-Index: Acx9xcK3RLpOw+GoRQ6AXbWpT5aWdQABxYLw
References: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com><E62242EF-DF1C-42D6-AD06-DC1761383E44@watteco.com> <C16130C1-0C50-4FF9-A750-3864D21E41B6@townsley.net>
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Mark Townsley" <mark@townsley.net>, "C Chauvenet" <c.chauvenet@watteco.com>
X-OriginalArrivalTime: 28 Sep 2011 11:25:23.0597 (UTC) FILETIME=[50502BD0:01CC7DD1]
Cc: homenet@ietf.org, MANET IETF <manet@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, rtgwg@ietf.org
Subject: Re: [manet] [homenet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2011 11:22:42 -0000

Hello Mark=A0:


>The majority of IP-based home networks today are neither =
power-constrained nor particularly lossy. So, while we can certainly =
learn from LLN requirements analysis, I do think the base requirements =
in homenet could turn out to be quite different, or at least a smaller =
and slightly different subset, of the overall LLN requirements.=A0

> Certainly, home networks have an emerging IP-based "low power and =
lossy" component in them. One could even argue that it will become =
dominant at some time in the future, but that's a leap I personally =
would be pretty uncomfortable in the group making without some very =
strong data to back it up.


In any case we have to consider the integration of the LLN (e.g. a =
Command and Control) component of the network within the HOMENET =
architecture, wouldn't you think? If so, there is a probably a RPL piece =
to the story, and the question becomes how that piece integrates with =
the rest of the architecture. We probably want to obtain a converged =
network, and probably would prefer to avoid running too many routing =
protocols, with redistribution policies etc... which can rapidly become =
nasty in terms of administration.

Anyway, I'd suggest that whether the home network is fully an LLN or not =
is not necessarily the core if the RPL applicability discussion:

* ROLL did not produce a routing protocol that is limited to LLNs, but a =
routing protocol that is acceptable for LLNs. IOW it is not restricted =
to LLNs, by far.

* RPL is designed to be simple to deploy. It inherits from mesh =
technologies the traditional self-* properties which make it quite =
autonomic thus better fit for unmanaged environments.

* RPL is designed and optimized for edge (stub) networks, with one or =
multiple gateway. Just like L2 mesh networks, RPL builds multilink nets =
and/or subnets that are oriented towards the gateways. It is possible to =
optimize traffic from/to certain destinations within the network, but =
the general goal is NOT any to any optimization. As a result, it can be =
desirable to have a non-RPL high speed backbone that can be a single =
backbone link or that can be a more complex IPv6 backbone network =
running, say, a link state protocol, when that's really needed.

* Associated to the support of multiple gateways, RPL incorporates =
natively the concept of multiple routing topologies, for instance if you =
want to separate a metering network that reports to some utility with =
your voice and video network. This comes with 6MAN drafts that enable to =
tag the packets so as to follow the appropriate topology.

* Finally, the brains for the routing decision is a plug in, called an =
objective function (OF). So even if HOMENET inherits from ROLL for the =
DV loop avoidance scheme and from 6MAN for the tagging/forwarding, the =
WG can still define one or more OFs that will dictate the shape of the =
resulting routing topologies. The OF is the decision maker that will, =
say, prefer a high speed Ethernet over an LLN, for a given class of =
traffic.

What do you think?

Pascal

From c.chauvenet@watteco.com  Wed Sep 28 02:20:16 2011
Return-Path: <c.chauvenet@watteco.com>
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 420F821F8CFD; Wed, 28 Sep 2011 02:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.898
X-Spam-Level: 
X-Spam-Status: No, score=-5.898 tagged_above=-999 required=5 tests=[AWL=0.700,  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 56xgjMetDw4O; Wed, 28 Sep 2011 02:20:15 -0700 (PDT)
Received: from TX2EHSOBE010.bigfish.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id 1517921F8D05; Wed, 28 Sep 2011 02:20:07 -0700 (PDT)
Received: from mail117-tx2-R.bigfish.com (10.9.14.245) by TX2EHSOBE010.bigfish.com (10.9.40.30) with Microsoft SMTP Server id 14.1.225.22; Wed, 28 Sep 2011 09:22:54 +0000
Received: from mail117-tx2 (localhost.localdomain [127.0.0.1])	by mail117-tx2-R.bigfish.com (Postfix) with ESMTP id DCB61170023B; Wed, 28 Sep 2011 09:22:54 +0000 (UTC)
X-SpamScore: -27
X-BigFish: VPS-27(zzc89bhc85dh14ffOzz1202hzz1033IL8275dhz2dh2a8h668h839h8aah)
X-Forefront-Antispam-Report: CIP:213.199.187.153; KIP:(null); UIP:(null); IPVD:NLI; SRV:BULK; H:IE2RD2HUB015.red002.local; RD:none; EFVD:NLI
X-FB-SS: 0,0,
Received: from mail117-tx2 (localhost.localdomain [127.0.0.1]) by mail117-tx2 (MessageSwitch) id 1317201774277678_24632; Wed, 28 Sep 2011 09:22:54 +0000 (UTC)
Received: from TX2EHSMHS033.bigfish.com (unknown [10.9.14.243])	by mail117-tx2.bigfish.com (Postfix) with ESMTP id 391C510E8054; Wed, 28 Sep 2011 09:22:54 +0000 (UTC)
Received: from IE2RD2HUB015.red002.local (213.199.187.153) by TX2EHSMHS033.bigfish.com (10.9.99.133) with Microsoft SMTP Server (TLS) id 14.1.225.22; Wed, 28 Sep 2011 09:22:53 +0000
Received: from IE2RD2XVS211.red002.local ([172.18.6.54]) by IE2RD2HUB015.red002.local ([10.43.198.13]) with mapi; Wed, 28 Sep 2011 02:22:30 -0700
From: C Chauvenet <c.chauvenet@watteco.com>
To: Fred Baker <fred@cisco.com>
Date: Wed, 28 Sep 2011 02:22:28 -0700
Thread-Topic: [homenet] Question for you
Thread-Index: Acx9wCWD10HnTesFRO+URsL8VZRvCg==
Message-ID: <E62242EF-DF1C-42D6-AD06-DC1761383E44@watteco.com>
References: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com>
In-Reply-To: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR, en-US
Content-Type: multipart/alternative; boundary="_000_E62242EFDF1C42D6AD06DC1761383E44wattecocom_"
MIME-Version: 1.0
X-OriginatorOrg: watteco.com
X-Mailman-Approved-At: Wed, 28 Sep 2011 07:45:26 -0700
Cc: "homenet@ietf.org" <homenet@ietf.org>, MANET IETF <manet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: [manet] [homenet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2011 09:20:16 -0000

--_000_E62242EFDF1C42D6AD06DC1761383E44wattecocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

This is an valuable and necessary initiative.

As I follow the ROLL WG, may I point you to some doc that have been produce=
d by this WG, and may address some of your questions :

http://tools.ietf.org/html/draft-ietf-roll-protocols-survey-07 : This draft=
 provide a good survey of several routing protocols (OSPF/IS-IS, OLSRv2, TB=
RPF, RIP, AODV, DYMO, DSR) and evaluate each candidate regarding metrics th=
at are relevant for Low-power and Lossy Networks (LLNs).
I think LLNs are applicable to Homenet networks.

RFC 5826 : http://tools.ietf.org/html/rfc5826 ("Home Automation Routing Req=
uirements in LLNs") : This doc designed by the ROLL WG gather some requirem=
ents regarding routing in Home environments. It may provide good input for =
the Homenet WG.

You may also be interested in the Building version of these requirements, i=
n RFC5867 http://tools.ietf.org/html/rfc5867.

I'm not an expert in Home's Networks, and they may have some different requ=
irements than LLNs that ROLL is looking at.
Please educate me on that point.
But I think we should consider the work that have been done for such constr=
ained devices.

Best regards,

C=E9dric.


Le 26 sept. 2011 =E0 21:14, Fred Baker a =E9crit :

I'm trying to do a somewhat complete requirements and pro/con analysis for =
IPv6 routing in a small network, the obvious examples being residential and=
 SOHO networks. What I have in pixels at this instant is:

   <section title=3D"Contestant protocols">
       <t></t>
     <section title=3D"Routing Information Protocol">
       <t></t>
     </section>
     <section title=3D"Open Shortest Path First Routing Protocol">
       <t></t>
     </section>
     <section title=3D"IS-IS Routing Protocol">
       <t></t>
     </section>
     <section title=3D"Border Gateway Protocol">
       <t></t>
     </section>
     <section title=3D"Routing Protocol for Low Power and Lossy Networks">
       <t></t>
     </section>
     <section title=3D"Ad hoc On-Demand Distance Vector Routing">
       <t>
Can you say "DYMO"?
       </t>
     </section>
     <section title=3D"Optimized Link State Routing Protocol">
       <t></t>
     </section>
   </section>

For some of these, the obvious comment is "YMBK". Some will feel that their=
 selection is the obvious given and will be able to go on at some length as=
 to why, and may be surprised to find that people disagree with them.

I'd like to do several things:
(a) make the list as reasonably complete as possible consistent with openly=
 documented protocols,
(b) provide a reasonably complete and objective analysis of each as I can,
(c) identify the key reasons one would choose each - if there is a reason a=
t all, and
(d) identify the key reasons one would not.

What I don't want to accomplish is deep-six these lists and half a dozen ot=
hers in arguments.

Do me a favor. Let's do this in private mail. If you think of a protocol I =
should mention that I haven't, let me know. If you think there is a really =
good argument for or against any of them in particular, let me know. If you=
 think I'm nuts - I already know that, you don't need to remind me :-)
_______________________________________________
homenet mailing list
homenet@ietf.org<mailto:homenet@ietf.org>
https://www.ietf.org/mailman/listinfo/homenet



--_000_E62242EFDF1C42D6AD06DC1761383E44wattecocom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; ">Hi all,&nbsp;<div><br></di=
v><div>This is an valuable and necessary initiative.</div><div><br></div><d=
iv>As I follow the ROLL WG, may I point you to some doc that have been prod=
uced by this WG, and may address some of your questions :</div><div><br></d=
iv><div><a href=3D"http://tools.ietf.org/html/draft-ietf-roll-protocols-sur=
vey-07">http://tools.ietf.org/html/draft-ietf-roll-protocols-survey-07</a>&=
nbsp;: This draft provide a good survey of several routing protocols (OSPF/=
IS-IS, OLSRv2, TBRPF, RIP, AODV, DYMO, DSR) and evaluate each candidate reg=
arding metrics that are relevant for Low-power and Lossy Networks (LLNs).</=
div><div>I think LLNs are applicable to Homenet networks.</div><div><br></d=
iv><div>RFC 5826 :&nbsp;<a href=3D"http://tools.ietf.org/html/rfc5826">http=
://tools.ietf.org/html/rfc5826</a>&nbsp;("Home Automation Routing Requireme=
nts in LLNs") : This doc designed by the ROLL WG gather some requirements r=
egarding routing in Home environments. It may provide good input for the Ho=
menet WG.</div><div><br></div><div>You may also be interested in the Buildi=
ng version of these requirements, in RFC5867&nbsp;<a href=3D"http://tools.i=
etf.org/html/rfc5867">http://tools.ietf.org/html/rfc5867</a>.</div><div><br=
></div><div>I'm not an expert in Home's Networks, and they may have some di=
fferent requirements than LLNs that ROLL is looking at.</div><div>Please ed=
ucate me on that point.</div><div>But I think we should consider the work t=
hat have been done for such constrained devices.</div><div><br></div><div>B=
est regards,</div><div><br></div><div>C=E9dric.</div><div><br></div><div><b=
r><div><div>Le 26 sept. 2011 =E0 21:14, Fred Baker a =E9crit :</div><br cla=
ss=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>I'm trying =
to do a somewhat complete requirements and pro/con analysis for IPv6 routin=
g in a small network, the obvious examples being residential and SOHO netwo=
rks. What I have in pixels at this instant is:<br><br> &nbsp;&nbsp;&nbsp;&l=
t;section title=3D"Contestant protocols"&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;s=
ection title=3D"Routing Information Protocol"&gt;<br> &nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&lt;/section&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;section title=3D"Ope=
n Shortest Path First Routing Protocol"&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/s=
ection&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;section title=3D"IS-IS Rou=
ting Protocol"&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&=
lt;/t&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br> &nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&lt;section title=3D"Border Gateway Protocol"&gt;<br> &=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> &nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;=
section title=3D"Routing Protocol for Low Power and Lossy Networks"&gt;<br>=
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> &nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&l=
t;section title=3D"Ad hoc On-Demand Distance Vector Routing"&gt;<br> &nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;<br>Can you say "DYMO"?<br> &n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/t&gt;<br> &nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&lt;/section&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;section ti=
tle=3D"Optimized Link State Routing Protocol"&gt;<br> &nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&lt;/section&gt;<br> &nbsp;&nbsp;&nbsp;&lt;/section&gt;<br><br>For some of =
these, the obvious comment is "YMBK". Some will feel that their selection i=
s the obvious given and will be able to go on at some length as to why, and=
 may be surprised to find that people disagree with them. <br><br>I'd like =
to do several things:<br>(a) make the list as reasonably complete as possib=
le consistent with openly documented protocols,<br>(b) provide a reasonably=
 complete and objective analysis of each as I can,<br>(c) identify the key =
reasons one would choose each - if there is a reason at all, and<br>(d) ide=
ntify the key reasons one would not.<br><br>What I don't want to accomplish=
 is deep-six these lists and half a dozen others in arguments.<br><br>Do me=
 a favor. Let's do this in private mail. If you think of a protocol I shoul=
d mention that I haven't, let me know. If you think there is a really good =
argument for or against any of them in particular, let me know. If you thin=
k I'm nuts - I already know that, you don't need to remind me :-)<br>______=
_________________________________________<br>homenet mailing list<br><a hre=
f=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br><a href=3D"https://ww=
w.ietf.org/mailman/listinfo/homenet">https://www.ietf.org/mailman/listinfo/=
homenet</a><br><br></div></blockquote></div><br></div></body></html>=

--_000_E62242EFDF1C42D6AD06DC1761383E44wattecocom_--

From mark@townsley.net  Wed Sep 28 02:59:39 2011
Return-Path: <mark@townsley.net>
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 5FEC921F8CAE; Wed, 28 Sep 2011 02:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.46
X-Spam-Level: 
X-Spam-Status: No, score=-3.46 tagged_above=-999 required=5 tests=[AWL=0.138,  BAYES_00=-2.599, 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 uL2dN2SQL45N; Wed, 28 Sep 2011 02:59:38 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id BA10021F8CDB; Wed, 28 Sep 2011 02:59:37 -0700 (PDT)
Received: by wyh21 with SMTP id 21so6746926wyh.31 for <multiple recipients>; Wed, 28 Sep 2011 03:02:25 -0700 (PDT)
Received: by 10.216.182.9 with SMTP id n9mr880685wem.54.1317204145062; Wed, 28 Sep 2011 03:02:25 -0700 (PDT)
Received: from ams-townsley-8713.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id h39sm3365877wbo.0.2011.09.28.03.02.22 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Sep 2011 03:02:23 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-122--405475250
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <E62242EF-DF1C-42D6-AD06-DC1761383E44@watteco.com>
Date: Wed, 28 Sep 2011 12:02:20 +0200
Message-Id: <C16130C1-0C50-4FF9-A750-3864D21E41B6@townsley.net>
References: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com> <E62242EF-DF1C-42D6-AD06-DC1761383E44@watteco.com>
To: C Chauvenet <c.chauvenet@watteco.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Wed, 28 Sep 2011 07:45:26 -0700
Cc: "homenet@ietf.org" <homenet@ietf.org>, MANET IETF <manet@ietf.org>, Fred Baker <fred@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: [manet] [homenet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2011 09:59:39 -0000

--Apple-Mail-122--405475250
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Sep 28, 2011, at 11:22 AM, C Chauvenet wrote:

> Hi all,=20
>=20
> This is an valuable and necessary initiative.
>=20
> As I follow the ROLL WG, may I point you to some doc that have been =
produced by this WG, and may address some of your questions :
>=20
> http://tools.ietf.org/html/draft-ietf-roll-protocols-survey-07 : This =
draft provide a good survey of several routing protocols (OSPF/IS-IS, =
OLSRv2, TBRPF, RIP, AODV, DYMO, DSR) and evaluate each candidate =
regarding metrics that are relevant for Low-power and Lossy Networks =
(LLNs).
> I think LLNs are applicable to Homenet networks.
>=20
> RFC 5826 : http://tools.ietf.org/html/rfc5826 ("Home Automation =
Routing Requirements in LLNs") : This doc designed by the ROLL WG gather =
some requirements regarding routing in Home environments. It may provide =
good input for the Homenet WG.
>=20
> You may also be interested in the Building version of these =
requirements, in RFC5867 http://tools.ietf.org/html/rfc5867.
>=20
> I'm not an expert in Home's Networks, and they may have some different =
requirements than LLNs that ROLL is looking at.
> Please educate me on that point.
> But I think we should consider the work that have been done for such =
constrained devices.

Thank you for the pointers.

The majority of IP-based home networks today are neither =
power-constrained nor particularly lossy. So, while we can certainly =
learn from LLN requirements analysis, I do think the base requirements =
in homenet could turn out to be quite different, or at least a smaller =
and slightly different subset, of the overall LLN requirements.=20

Certainly, home networks have an emerging IP-based "low power and lossy" =
component in them. One could even argue that it will become dominant at =
some time in the future, but that's a leap I personally would be pretty =
uncomfortable in the group making without some very strong data to back =
it up.=20

- Mark

>=20
> Best regards,
>=20
> C=E9dric.
>=20
>=20
> Le 26 sept. 2011 =E0 21:14, Fred Baker a =E9crit :
>=20
>> I'm trying to do a somewhat complete requirements and pro/con =
analysis for IPv6 routing in a small network, the obvious examples being =
residential and SOHO networks. What I have in pixels at this instant is:
>>=20
>>    <section title=3D"Contestant protocols">
>>        <t></t>
>>      <section title=3D"Routing Information Protocol">
>>        <t></t>
>>      </section>
>>      <section title=3D"Open Shortest Path First Routing Protocol">
>>        <t></t>
>>      </section>
>>      <section title=3D"IS-IS Routing Protocol">
>>        <t></t>
>>      </section>
>>      <section title=3D"Border Gateway Protocol">
>>        <t></t>
>>      </section>
>>      <section title=3D"Routing Protocol for Low Power and Lossy =
Networks">
>>        <t></t>
>>      </section>
>>      <section title=3D"Ad hoc On-Demand Distance Vector Routing">
>>        <t>
>> Can you say "DYMO"?
>>        </t>
>>      </section>
>>      <section title=3D"Optimized Link State Routing Protocol">
>>        <t></t>
>>      </section>
>>    </section>
>>=20
>> For some of these, the obvious comment is "YMBK". Some will feel that =
their selection is the obvious given and will be able to go on at some =
length as to why, and may be surprised to find that people disagree with =
them.=20
>>=20
>> I'd like to do several things:
>> (a) make the list as reasonably complete as possible consistent with =
openly documented protocols,
>> (b) provide a reasonably complete and objective analysis of each as I =
can,
>> (c) identify the key reasons one would choose each - if there is a =
reason at all, and
>> (d) identify the key reasons one would not.
>>=20
>> What I don't want to accomplish is deep-six these lists and half a =
dozen others in arguments.
>>=20
>> Do me a favor. Let's do this in private mail. If you think of a =
protocol I should mention that I haven't, let me know. If you think =
there is a really good argument for or against any of them in =
particular, let me know. If you think I'm nuts - I already know that, =
you don't need to remind me :-)
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>>=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail-122--405475250
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Sep 28, 2011, at 11:22 AM, C Chauvenet =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; ">Hi =
all,&nbsp;<div><br></div><div>This is an valuable and necessary =
initiative.</div><div><br></div><div>As I follow the ROLL WG, may I =
point you to some doc that have been produced by this WG, and may =
address some of your questions :</div><div><br></div><div><a =
href=3D"http://tools.ietf.org/html/draft-ietf-roll-protocols-survey-07">ht=
tp://tools.ietf.org/html/draft-ietf-roll-protocols-survey-07</a>&nbsp;: =
This draft provide a good survey of several routing protocols =
(OSPF/IS-IS, OLSRv2, TBRPF, RIP, AODV, DYMO, DSR) and evaluate each =
candidate regarding metrics that are relevant for Low-power and Lossy =
Networks (LLNs).</div><div>I think LLNs are applicable to Homenet =
networks.</div><div><br></div><div>RFC 5826 :&nbsp;<a =
href=3D"http://tools.ietf.org/html/rfc5826">http://tools.ietf.org/html/rfc=
5826</a>&nbsp;("Home Automation Routing Requirements in LLNs") : This =
doc designed by the ROLL WG gather some requirements regarding routing =
in Home environments. It may provide good input for the Homenet =
WG.</div><div><br></div><div>You may also be interested in the Building =
version of these requirements, in RFC5867&nbsp;<a =
href=3D"http://tools.ietf.org/html/rfc5867">http://tools.ietf.org/html/rfc=
5867</a>.</div><div><br></div><div>I'm not an expert in Home's Networks, =
and they may have some different requirements than LLNs that ROLL is =
looking at.</div><div>Please educate me on that point.</div><div>But I =
think we should consider the work that have been done for such =
constrained devices.</div></div></blockquote><div><br></div><div>Thank =
you for the pointers.</div><div><br></div><div><div>The majority of =
IP-based home networks today are neither power-constrained nor =
particularly lossy. So, while we can certainly learn from LLN =
requirements analysis, I do think the base requirements in homenet could =
turn out to be quite different, or at least a smaller and slightly =
different subset, of the overall LLN =
requirements.&nbsp;</div></div><div><br></div><div>Certainly, home =
networks have an emerging IP-based "low power and lossy" component in =
them. One could even argue that it will become dominant at some time in =
the future, but that's a leap I personally would be pretty uncomfortable =
in the group making without some very strong data to back it =
up.&nbsp;</div><div><br></div><div>- Mark</div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><br></div><div>Best =
regards,</div><div><br></div><div>C=E9dric.</div><div><br></div><div><br><=
div><div>Le 26 sept. 2011 =E0 21:14, Fred Baker a =E9crit :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>I'm =
trying to do a somewhat complete requirements and pro/con analysis for =
IPv6 routing in a small network, the obvious examples being residential =
and SOHO networks. What I have in pixels at this instant is:<br><br> =
&nbsp;&nbsp;&nbsp;&lt;section title=3D"Contestant protocols"&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;section title=3D"Routing Information =
Protocol"&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;section title=3D"Open Shortest Path =
First Routing Protocol"&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;section title=3D"IS-IS Routing =
Protocol"&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;section title=3D"Border Gateway =
Protocol"&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;section title=3D"Routing Protocol for =
Low Power and Lossy Networks"&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;section title=3D"Ad hoc On-Demand =
Distance Vector Routing"&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;<br>Can you say =
"DYMO"?<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/t&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;section title=3D"Optimized Link State =
Routing Protocol"&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;t&gt;&lt;/t&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br> =
&nbsp;&nbsp;&nbsp;&lt;/section&gt;<br><br>For some of these, the obvious =
comment is "YMBK". Some will feel that their selection is the obvious =
given and will be able to go on at some length as to why, and may be =
surprised to find that people disagree with them. <br><br>I'd like to do =
several things:<br>(a) make the list as reasonably complete as possible =
consistent with openly documented protocols,<br>(b) provide a reasonably =
complete and objective analysis of each as I can,<br>(c) identify the =
key reasons one would choose each - if there is a reason at all, =
and<br>(d) identify the key reasons one would not.<br><br>What I don't =
want to accomplish is deep-six these lists and half a dozen others in =
arguments.<br><br>Do me a favor. Let's do this in private mail. If you =
think of a protocol I should mention that I haven't, let me know. If you =
think there is a really good argument for or against any of them in =
particular, let me know. If you think I'm nuts - I already know that, =
you don't need to remind me =
:-)<br>_______________________________________________<br>homenet =
mailing list<br><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/homenet">https://www.ietf.or=
g/mailman/listinfo/homenet</a><br><br></div></blockquote></div><br></div><=
/div>_______________________________________________<br>homenet mailing =
list<br><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/homenet<br></blockquote></div><br></body></html>=

--Apple-Mail-122--405475250--

From mark@townsley.net  Wed Sep 28 07:58:41 2011
Return-Path: <mark@townsley.net>
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 18C4721F8AFA; Wed, 28 Sep 2011 07:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.464
X-Spam-Level: 
X-Spam-Status: No, score=-3.464 tagged_above=-999 required=5 tests=[AWL=0.135,  BAYES_00=-2.599, 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 37Vbs-UttoVX; Wed, 28 Sep 2011 07:58:40 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id D43F321F8AF5; Wed, 28 Sep 2011 07:58:39 -0700 (PDT)
Received: by wwn22 with SMTP id 22so1719455wwn.1 for <multiple recipients>; Wed, 28 Sep 2011 08:01:27 -0700 (PDT)
Received: by 10.227.2.206 with SMTP id 14mr3402445wbk.94.1317221892409; Wed, 28 Sep 2011 07:58:12 -0700 (PDT)
Received: from ams-townsley-8713.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id p13sm40910638wbh.13.2011.09.28.07.58.05 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Sep 2011 07:58:06 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <BDF2740C082F6942820D95BAEB9E1A840DBF1E@XMB-AMS-108.cisco.com>
Date: Wed, 28 Sep 2011 16:58:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D3C1E64-F7A3-4888-B77A-CFB6CE2BCD1D@townsley.net>
References: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com><E62242EF-DF1C-42D6-AD06-DC1761383E44@watteco.com> <C16130C1-0C50-4FF9-A750-3864D21E41B6@townsley.net> <BDF2740C082F6942820D95BAEB9E1A840DBF1E@XMB-AMS-108.cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: C Chauvenet <c.chauvenet@watteco.com>, homenet@ietf.org, MANET IETF <manet@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, rtgwg@ietf.org
Subject: Re: [manet] [homenet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2011 14:58:41 -0000

On Sep 28, 2011, at 1:25 PM, Pascal Thubert (pthubert) wrote:

> Hello Mark :
>=20
>=20
>> The majority of IP-based home networks today are neither =
power-constrained nor particularly lossy. So, while we can certainly =
learn from LLN requirements analysis, I do think the base requirements =
in homenet could turn out to be quite different, or at least a smaller =
and slightly different subset, of the overall LLN requirements.=20
>=20
>> Certainly, home networks have an emerging IP-based "low power and =
lossy" component in them. One could even argue that it will become =
dominant at some time in the future, but that's a leap I personally =
would be pretty uncomfortable in the group making without some very =
strong data to back it up.
>=20
>=20
> In any case we have to consider the integration of the LLN (e.g. a =
Command and Control) component of the network within the HOMENET =
architecture, wouldn't you think?

Yes.=20

> If so, there is a probably a RPL piece to the story, and the question =
becomes how that piece integrates with the rest of the architecture. We =
probably want to obtain a converged network, and probably would prefer =
to avoid running too many routing protocols, with redistribution =
policies etc... which can rapidly become nasty in terms of =
administration.\

> Anyway, I'd suggest that whether the home network is fully an LLN or =
not is not necessarily the core if the RPL applicability discussion:
>=20
> * ROLL did not produce a routing protocol that is limited to LLNs, but =
a routing protocol that is acceptable for LLNs. IOW it is not restricted =
to LLNs, by far.

Bummer of a name then ;-)

> * RPL is designed to be simple to deploy. It inherits from mesh =
technologies the traditional self-* properties which make it quite =
autonomic thus better fit for unmanaged environments.
>=20
> * RPL is designed and optimized for edge (stub) networks, with one or =
multiple gateway. Just like L2 mesh networks, RPL builds multilink nets =
and/or subnets that are oriented towards the gateways. It is possible to =
optimize traffic from/to certain destinations within the network, but =
the general goal is NOT any to any optimization. As a result, it can be =
desirable to have a non-RPL high speed backbone that can be a single =
backbone link or that can be a more complex IPv6 backbone network =
running, say, a link state protocol, when that's really needed.
>=20
> * Associated to the support of multiple gateways, RPL incorporates =
natively the concept of multiple routing topologies, for instance if you =
want to separate a metering network that reports to some utility with =
your voice and video network. This comes with 6MAN drafts that enable to =
tag the packets so as to follow the appropriate topology.
>=20
> * Finally, the brains for the routing decision is a plug in, called an =
objective function (OF). So even if HOMENET inherits from ROLL for the =
DV loop avoidance scheme and from 6MAN for the tagging/forwarding, the =
WG can still define one or more OFs that will dictate the shape of the =
resulting routing topologies. The OF is the decision maker that will, =
say, prefer a high speed Ethernet over an LLN, for a given class of =
traffic.
>=20
> What do you think?

Since you asked, *I* think that a homenet has functional overlap (what I =
called "at least a smaller and slightly different subset" in my email) =
in terms of requirements to LLNs. At first blush, it looks like RPL has =
lots of functionality - perhaps more than we really need for homenet, =
and by your own admission more than you need for LLN's - but will hold =
reservation on what I think best fits the bill until we see Fred's =
analysis, hear from others, etc.=20

But of course what's most important is what the WG thinks, not me.=20

- Mark

>=20
> Pascal
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From fred@cisco.com  Wed Sep 28 08:40:50 2011
Return-Path: <fred@cisco.com>
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 7592C1F0C76; Wed, 28 Sep 2011 08:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 I7U3IMQWUG1b; Wed, 28 Sep 2011 08:40:49 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 220BB1F0C68; Wed, 28 Sep 2011 08:40:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2179; q=dns/txt; s=iport; t=1317224616; x=1318434216; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=WjP5yYJpOG/9wyPhCDsH+LPTfwKEuP2mBrhuhxH8sIg=; b=BaRLm/kfWvtAwABxg4hMfgfLw2PbZinVwpIMRvx9m9SAq8pDswU1lXOm o/28mdnvtlGsYNk0YQ2Cg8tJVo4ApJk6IvWpbacjtvJQk9IrftgcDRSXa p5VaL3zrM9HBwsYTZsa4wsmnS6KpwcPGYeMPcEBXyOyLvZ0la84hINoM0 s=;
X-IronPort-AV: E=Sophos;i="4.68,456,1312156800"; d="scan'208";a="56597807"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 28 Sep 2011 15:43:35 +0000
Received: from Freds-Computer.local (ams3-vpn-dhcp2921.cisco.com [10.61.75.105]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p8SFhLuB015705; Wed, 28 Sep 2011 15:43:32 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 28 Sep 2011 18:43:34 +0244
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 28 Sep 2011 18:43:34 +0244
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <1D3C1E64-F7A3-4888-B77A-CFB6CE2BCD1D@townsley.net>
Date: Wed, 28 Sep 2011 18:43:30 +0300
Message-Id: <47090411-FEBF-4EE2-804D-25773DE879B8@cisco.com>
References: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com><E62242EF-DF1C-42D6-AD06-DC1761383E44@watteco.com> <C16130C1-0C50-4FF9-A750-3864D21E41B6@townsley.net> <BDF2740C082F6942820D95BAEB9E1A840DBF1E@XMB-AMS-108.cisco.com> <1D3C1E64-F7A3-4888-B77A-CFB6CE2BCD1D@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: C Chauvenet <c.chauvenet@watteco.com>, "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, MANET IETF <manet@ietf.org>, homenet@ietf.org, rtgwg@ietf.org
Subject: Re: [manet] [homenet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2011 15:40:50 -0000

On Sep 28, 2011, at 5:58 PM, Mark Townsley wrote:

> Since you asked, *I* think that a homenet has functional overlap (what =
I called "at least a smaller and slightly different subset" in my email) =
in terms of requirements to LLNs. At first blush, it looks like RPL has =
lots of functionality - perhaps more than we really need for homenet, =
and by your own admission more than you need for LLN's - but will hold =
reservation on what I think best fits the bill until we see Fred's =
analysis, hear from others, etc.=20

My two yen, which may be all it's worth...

If I were a Linksys/D-Link/NetGear/* product manager asking about what =
protocols to put in, I wouldn't be asking about what still exists in =
Internet Drafts and is thought by the engineers designing it to be =
better than sliced bread, but about what was inexpensive to implement, =
likely to be close to bug-free, and definitively accomplished the goal. =
I note that most routers for the IPv4 residential routing marketplace =
implement RIPv2; I know of one that implements no routing protocol, one =
that implements RIPv2 and RIPv1 (!), and one that implements RIPv2 and =
OSPF (don't ask which they are, I don't remember). This is from a google =
search of residential routers a few months ago and covered perhaps 20 =
products from half as many vendors. So my first inclination is to say =
that for a residential IPv6 network, RIPng is probably an image match =
for those vendors.

I have a personal bias in the direction of OSPF or IS-IS; I think that =
once the code is debugged, SPF-based protocols are more stable (no =
count-to-infinity), given a reasonable set of defaults generate far more =
stable networks, and definitively know when there is more than one =
router on a LAN, which can be important in subnet distribution.=20

My first choice would NOT be something that isn't proven in the field in =
multiple interoperable implementations.=20

As a person thinking about making a recommendation, I'd suggest that =
folks read https://tools.ietf.org/html/rfc2026#section-4.1.2 and ask =
themselves why that level of interoperability isn't mandatory.=

From jari.arkko@piuha.net  Wed Sep 28 09:19:32 2011
Return-Path: <jari.arkko@piuha.net>
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 96DE71F0C69; Wed, 28 Sep 2011 09:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 ETROXYzSSmdq; Wed, 28 Sep 2011 09:19:13 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id F0F141F0C6D; Wed, 28 Sep 2011 09:19:12 -0700 (PDT)
Received: from localhost (87-93-10-118.bb.dnainternet.fi [87.93.10.118]) by p130.piuha.net (Postfix) with ESMTPSA id E6CA92CE32; Wed, 28 Sep 2011 19:21:35 +0300 (EEST)
Date: Wed, 28 Sep 2011 18:21:32 +0200
Message-ID: <e31i6t6ctbhvc32mvn1ptqgt.1317226892778@email.android.com>
From: Jari Arkko <jari.arkko@piuha.net>
To: Fred Baker <fred@cisco.com>, Mark Townsley <mark@townsley.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: C Chauvenet <c.chauvenet@watteco.com>, "	Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, MANET IETF <manet@ietf.org>, homenet@ietf.org, rtgwg@ietf.org
Subject: Re: [manet] [homenet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2011 16:19:32 -0000

SSBhZ3JlZSB3aXRoIE1hcmsgYW5kIEZyZWQuCgpKYXJpCgpGcmVkIEJha2VyIDxmcmVkQGNpc2Nv
LmNvbT4gd3JvdGU6Cgo+Cj5PbiBTZXAgMjgsIDIwMTEsIGF0IDU6NTggUE0sIE1hcmsgVG93bnNs
ZXkgd3JvdGU6Cj4KPj4gU2luY2UgeW91IGFza2VkLCAqSSogdGhpbmsgdGhhdCBhIGhvbWVuZXQg
aGFzIGZ1bmN0aW9uYWwgb3ZlcmxhcCAod2hhdCBJIGNhbGxlZCAiYXQgbGVhc3QgYSBzbWFsbGVy
IGFuZCBzbGlnaHRseSBkaWZmZXJlbnQgc3Vic2V0IiBpbiBteSBlbWFpbCkgaW4gdGVybXMgb2Yg
cmVxdWlyZW1lbnRzIHRvIExMTnMuIEF0IGZpcnN0IGJsdXNoLCBpdCBsb29rcyBsaWtlIFJQTCBo
YXMgbG90cyBvZiBmdW5jdGlvbmFsaXR5IC0gcGVyaGFwcyBtb3JlIHRoYW4gd2UgcmVhbGx5IG5l
ZWQgZm9yIGhvbWVuZXQsIGFuZCBieSB5b3VyIG93biBhZG1pc3Npb24gbW9yZSB0aGFuIHlvdSBu
ZWVkIGZvciBMTE4ncyAtIGJ1dCB3aWxsIGhvbGQgcmVzZXJ2YXRpb24gb24gd2hhdCBJIHRoaW5r
IGJlc3QgZml0cyB0aGUgYmlsbCB1bnRpbCB3ZSBzZWUgRnJlZCdzIGFuYWx5c2lzLCBoZWFyIGZy
b20gb3RoZXJzLCBldGMuIAo+Cj5NeSB0d28geWVuLCB3aGljaCBtYXkgYmUgYWxsIGl0J3Mgd29y
dGguLi4KPgo+SWYgSSB3ZXJlIGEgTGlua3N5cy9ELUxpbmsvTmV0R2Vhci8qIHByb2R1Y3QgbWFu
YWdlciBhc2tpbmcgYWJvdXQgd2hhdCBwcm90b2NvbHMgdG8gcHV0IGluLCBJIHdvdWxkbid0IGJl
IGFza2luZyBhYm91dCB3aGF0IHN0aWxsIGV4aXN0cyBpbiBJbnRlcm5ldCBEcmFmdHMgYW5kIGlz
IHRob3VnaHQgYnkgdGhlIGVuZ2luZWVycyBkZXNpZ25pbmcgaXQgdG8gYmUgYmV0dGVyIHRoYW4g
c2xpY2VkIGJyZWFkLCBidXQgYWJvdXQgd2hhdCB3YXMgaW5leHBlbnNpdmUgdG8gaW1wbGVtZW50
LCBsaWtlbHkgdG8gYmUgY2xvc2UgdG8gYnVnLWZyZWUsIGFuZCBkZWZpbml0aXZlbHkgYWNjb21w
bGlzaGVkIHRoZSBnb2FsLiBJIG5vdGUgdGhhdCBtb3N0IHJvdXRlcnMgZm9yIHRoZSBJUHY0IHJl
c2lkZW50aWFsIHJvdXRpbmcgbWFya2V0cGxhY2UgaW1wbGVtZW50IFJJUHYyOyBJIGtub3cgb2Yg
b25lIHRoYXQgaW1wbGVtZW50cyBubyByb3V0aW5nIHByb3RvY29sLCBvbmUgdGhhdCBpbXBsZW1l
bnRzIFJJUHYyIGFuZCBSSVB2MSAoISksIGFuZCBvbmUgdGhhdCBpbXBsZW1lbnRzIFJJUHYyIGFu
ZCBPU1BGIChkb24ndCBhc2sgd2hpY2ggdGhleSBhcmUsIEkgZG9uJ3QgcmVtZW1iZXIpLiBUaGlz
IGlzIGZyb20gYSBnb29nbGUgc2VhcmNoIG9mIHJlc2lkZW50aWFsIHJvdXRlcnMgYSBmZXcgbW9u
dGhzIGFnbyBhbmQgY292ZXJlZCBwZXJoYXBzIDIwIHByb2R1Y3RzIGZyb20gaGFsZiBhcyBtYW55
IHZlbmRvcnMuIFNvIG15IGZpcnN0IGluY2xpbmF0aW9uIGlzIHRvIHNheSB0aGF0IGZvciBhIHJl
c2lkZW50aWFsIElQdjYgbmV0d29yaywgUklQbmcgaXMgcHJvYmFibHkgYW4gaW1hZ2UgbWF0Y2gg
Zm9yIHRob3NlIHZlbmRvcnMuCj4KPkkgaGF2ZSBhIHBlcnNvbmFsIGJpYXMgaW4gdGhlIGRpcmVj
dGlvbiBvZiBPU1BGIG9yIElTLUlTOyBJIHRoaW5rIHRoYXQgb25jZSB0aGUgY29kZSBpcyBkZWJ1
Z2dlZCwgU1BGLWJhc2VkIHByb3RvY29scyBhcmUgbW9yZSBzdGFibGUgKG5vIGNvdW50LXRvLWlu
ZmluaXR5KSwgZ2l2ZW4gYSByZWFzb25hYmxlIHNldCBvZiBkZWZhdWx0cyBnZW5lcmF0ZSBmYXIg
bW9yZSBzdGFibGUgbmV0d29ya3MsIGFuZCBkZWZpbml0aXZlbHkga25vdyB3aGVuIHRoZXJlIGlz
IG1vcmUgdGhhbiBvbmUgcm91dGVyIG9uIGEgTEFOLCB3aGljaCBjYW4gYmUgaW1wb3J0YW50IGlu
IHN1Ym5ldCBkaXN0cmlidXRpb24uIAo+Cj5NeSBmaXJzdCBjaG9pY2Ugd291bGQgTk9UIGJlIHNv
bWV0aGluZyB0aGF0IGlzbid0IHByb3ZlbiBpbiB0aGUgZmllbGQgaW4gbXVsdGlwbGUgaW50ZXJv
cGVyYWJsZSBpbXBsZW1lbnRhdGlvbnMuIAo+Cj5BcyBhIHBlcnNvbiB0aGlua2luZyBhYm91dCBt
YWtpbmcgYSByZWNvbW1lbmRhdGlvbiwgSSdkIHN1Z2dlc3QgdGhhdCBmb2xrcyByZWFkIGh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmMyMDI2I3NlY3Rpb24tNC4xLjIgYW5kIGFzayB0aGVt
c2VsdmVzIHdoeSB0aGF0IGxldmVsIG9mIGludGVyb3BlcmFiaWxpdHkgaXNuJ3QgbWFuZGF0b3J5
Lgo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPmhvbWVu
ZXQgbWFpbGluZyBsaXN0Cj5ob21lbmV0QGlldGYub3JnCj5odHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2hvbWVuZXQK


From budden@nps.edu  Wed Sep 28 10:51:54 2011
Return-Path: <budden@nps.edu>
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 D61D01F0CAA; Wed, 28 Sep 2011 10:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Xdfu4oML8s2r; Wed, 28 Sep 2011 10:51:54 -0700 (PDT)
Received: from diamond.nps.edu (diamond.nps.edu [205.155.65.226]) by ietfa.amsl.com (Postfix) with ESMTP id 162F71F0CA8; Wed, 28 Sep 2011 10:51:54 -0700 (PDT)
Received: from virginia.nps.edu ([205.155.65.26]) by diamond.nps.edu with Microsoft SMTPSVC(6.0.3790.4675); Wed, 28 Sep 2011 10:54:42 -0700
Received: from SKYTRAIN.ern.nps.edu ([172.20.24.112]) by virginia.nps.edu with Microsoft SMTPSVC(6.0.3790.4675); Wed, 28 Sep 2011 10:54:42 -0700
Received: from [172.20.58.67] (172.20.58.67) by smtp.nps.edu (172.20.24.112) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 28 Sep 2011 10:54:42 -0700
From: Rex Buddenberg <budden@nps.edu>
To: Mark Townsley <mark@townsley.net>
In-Reply-To: <1D3C1E64-F7A3-4888-B77A-CFB6CE2BCD1D@townsley.net>
References: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com> <E62242EF-DF1C-42D6-AD06-DC1761383E44@watteco.com> <C16130C1-0C50-4FF9-A750-3864D21E41B6@townsley.net> <BDF2740C082F6942820D95BAEB9E1A840DBF1E@XMB-AMS-108.cisco.com> <1D3C1E64-F7A3-4888-B77A-CFB6CE2BCD1D@townsley.net>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 28 Sep 2011 10:54:23 -0700
Message-ID: <1317232463.2243.406.camel@localhost.localdomain>
MIME-Version: 1.0
X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Sep 2011 17:54:42.0471 (UTC) FILETIME=[B3497B70:01CC7E07]
X-Mailman-Approved-At: Wed, 28 Sep 2011 11:05:34 -0700
Cc: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, C Chauvenet <c.chauvenet@watteco.com>, MANET IETF <manet@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, homenet@ietf.org, rtgwg@ietf.org
Subject: Re: [manet] [homenet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2011 17:51:55 -0000

On Wed, 2011-09-28 at 16:58 +0200, Mark Townsley wrote:
> 
> >> The majority of IP-based home networks today are neither
> power-constrained nor particularly lossy. 

I would agree that that is the case today, but suggest we look ahead a
bit.

There's a fair head of steam building in emergency services that has the
term 'broadband' attached to it.  Lots of confusion, but...

We're about to see a repeat of what we saw in the CATV market where the
vendors thought you'd connect a computer at home to the DOCSIS network.
But we all hooked up routers instead.  This time the story is the
cellphone folks rolling out '4G' network segments and naively thinking
that we'll just hook up cellphones (which have since become computers --
mine has 8G of RAM in it!).  

Scenario for orientation.  Instead of the EMT in the ambulance having a
cellphone to call the emergency room, the EMT will be armed with several
diagnostic gadgets attached to a LAN (either ethernet or WiFi).  And a
router.  The router will, in turn be linked to the rest of internet with
a radio-WAN.  
	

Scenario implications.  Right now, emergency services tend to rely on a
set of high sites -- Monterey County where I live, has eleven.  But the
broadband technologies all look better with an order of magnitude more
sites (think schoolhouse roofs) and consequently more handoffs (aka
routing table volatility).  

Topology.  The radio-WAN is in interior of internet, not fringe.
	Power-constrained -- probably not much change since a lot of this will
be vehicle-mount -- ambulances, fire engines, etc.  This all changes as
soon as the trooper dismounts and exceeds WiFi range from his vehicle.
	Lossy.  Depends on how you define the term...  But radios lose more
bits (and hence more packets) than wires.  




From c.chauvenet@watteco.com  Thu Sep 29 08:25:58 2011
Return-Path: <c.chauvenet@watteco.com>
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 3AC9B21F8DC9; Thu, 29 Sep 2011 08:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.892
X-Spam-Level: 
X-Spam-Status: No, score=-5.892 tagged_above=-999 required=5 tests=[AWL=0.707,  BAYES_00=-2.599, 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 w0AbfJ2jIHyg; Thu, 29 Sep 2011 08:25:57 -0700 (PDT)
Received: from TX2EHSOBE007.bigfish.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id 50A6621F8DC8; Thu, 29 Sep 2011 08:25:57 -0700 (PDT)
Received: from mail161-tx2-R.bigfish.com (10.9.14.254) by TX2EHSOBE007.bigfish.com (10.9.40.27) with Microsoft SMTP Server id 14.1.225.22; Thu, 29 Sep 2011 15:28:48 +0000
Received: from mail161-tx2 (localhost.localdomain [127.0.0.1])	by mail161-tx2-R.bigfish.com (Postfix) with ESMTP id 6E89218C034B; Thu, 29 Sep 2011 15:28:48 +0000 (UTC)
X-SpamScore: -96
X-BigFish: VPS-96(zz9371Kc89bh1447M1418M1432N15caKJ98dK4015Lzz1202hzz1033IL8275dhz2dh2a8h668h839h8aah)
X-Forefront-Antispam-Report: CIP:213.199.187.153; KIP:(null); UIP:(null); IPVD:NLI; SRV:BULK; H:IE2RD2HUB003.red002.local; RD:none; EFVD:NLI
X-FB-SS: 0,13,
Received: from mail161-tx2 (localhost.localdomain [127.0.0.1]) by mail161-tx2 (MessageSwitch) id 1317309965575804_8598; Thu, 29 Sep 2011 15:26:05 +0000 (UTC)
Received: from TX2EHSMHS004.bigfish.com (unknown [10.9.14.248])	by mail161-tx2.bigfish.com (Postfix) with ESMTP id 2DBAF5983A1; Thu, 29 Sep 2011 15:23:38 +0000 (UTC)
Received: from IE2RD2HUB003.red002.local (213.199.187.153) by TX2EHSMHS004.bigfish.com (10.9.99.104) with Microsoft SMTP Server (TLS) id 14.1.225.22; Thu, 29 Sep 2011 15:23:00 +0000
Received: from IE2RD2XVS211.red002.local ([172.18.6.54]) by IE2RD2HUB003.red002.local ([10.33.16.63]) with mapi; Thu, 29 Sep 2011 08:22:42 -0700
From: C Chauvenet <c.chauvenet@watteco.com>
To: Acee Lindem <acee.lindem@ericsson.com>, Fred Baker <fred@cisco.com>
Date: Thu, 29 Sep 2011 08:22:54 -0700
Thread-Topic: [homenet] Question for you
Thread-Index: AQHlmDJmMvWMKI9R9oYagBEZ05YKowE1q290ARzCXPIBX+t1eQLCLmkyAbR0NfUBjk2LMpTkhxVw
Message-ID: <BDF612E3788C4C4791A1A49AC3CB7C971CE728FD13@IE2RD2XVS211.red002.local>
References: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com><E62242EF-DF1C-42D6-AD06-DC1761383E44@watteco.com> <C16130C1-0C50-4FF9-A750-3864D21E41B6@townsley.net> <BDF2740C082F6942820D95BAEB9E1A840DBF1E@XMB-AMS-108.cisco.com> <1D3C1E64-F7A3-4888-B77A-CFB6CE2BCD1D@townsley.net> <47090411-FEBF-4EE2-804D-25773DE879B8@cisco.com> <44783019-1016-4D06-BACA-6130617F099A@ericsson.com>
In-Reply-To: <44783019-1016-4D06-BACA-6130617F099A@ericsson.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: watteco.com
Cc: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, MANET IETF <manet@ietf.org>, Mark Townsley <mark@townsley.net>, "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: [manet] [homenet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2011 15:25:58 -0000

Hi,=20

" I don't think my wife would want a lossy network in our house ;^)" :=20

Nobody wants a lossy network, but the technology you are using may create l=
ossy links...

I may have miss something in the Homenet scope.

In the scope of Homenet, is every device in the house runing over a *robust=
* link (Bit Error Rate below 1 % at the PHY level) ?

Furthermore do these devices could have some high Power/Computation/Size/Co=
st constraints ?

I fail to see the kind of technologies and devices that are targeting.

Thanks for the clarification.

C=E9dric .

-----Message d'origine-----
De=A0: Acee Lindem [mailto:acee.lindem@ericsson.com]=20
Envoy=E9=A0: jeudi 29 septembre 2011 16:44
=C0=A0: Fred Baker
Cc=A0: Mark Townsley; C Chauvenet; Pascal Thubert (pthubert); MANET IETF; h=
omenet@ietf.org; rtgwg@ietf.org
Objet=A0: Re: [homenet] Question for you

I'm in complete agreement with Fred. The areas where the existing link-stat=
e protocols may need to be extended are auto-configuration and, potentially=
, inter-area policies. =20
I don't think my wife would want a lossy network in our house ;^) Thanks, A=
cee On Sep 28, 2011, at 11:43 AM, Fred Baker wrote:

>=20
> On Sep 28, 2011, at 5:58 PM, Mark Townsley wrote:
>=20
>> Since you asked, *I* think that a homenet has functional overlap (what I=
 called "at least a smaller and slightly different subset" in my email) in =
terms of requirements to LLNs. At first blush, it looks like RPL has lots o=
f functionality - perhaps more than we really need for homenet, and by your=
 own admission more than you need for LLN's - but will hold reservation on =
what I think best fits the bill until we see Fred's analysis, hear from oth=
ers, etc.=20
>=20
> My two yen, which may be all it's worth...
>=20
> If I were a Linksys/D-Link/NetGear/* product manager asking about what pr=
otocols to put in, I wouldn't be asking about what still exists in Internet=
 Drafts and is thought by the engineers designing it to be better than slic=
ed bread, but about what was inexpensive to implement, likely to be close t=
o bug-free, and definitively accomplished the goal. I note that most router=
s for the IPv4 residential routing marketplace implement RIPv2; I know of o=
ne that implements no routing protocol, one that implements RIPv2 and RIPv1=
 (!), and one that implements RIPv2 and OSPF (don't ask which they are, I d=
on't remember). This is from a google search of residential routers a few m=
onths ago and covered perhaps 20 products from half as many vendors. So my =
first inclination is to say that for a residential IPv6 network, RIPng is p=
robably an image match for those vendors.
>=20
> I have a personal bias in the direction of OSPF or IS-IS; I think that on=
ce the code is debugged, SPF-based protocols are more stable (no count-to-i=
nfinity), given a reasonable set of defaults generate far more stable netwo=
rks, and definitively know when there is more than one router on a LAN, whi=
ch can be important in subnet distribution.=20
>=20
> My first choice would NOT be something that isn't proven in the field in =
multiple interoperable implementations.=20
>=20
> As a person thinking about making a recommendation, I'd suggest that folk=
s read https://tools.ietf.org/html/rfc2026#section-4.1.2 and ask themselves=
 why that level of interoperability isn't mandatory.
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet




From acee.lindem@ericsson.com  Thu Sep 29 07:41:06 2011
Return-Path: <acee.lindem@ericsson.com>
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 0C1C921F8DCA; Thu, 29 Sep 2011 07:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.553
X-Spam-Level: 
X-Spam-Status: No, score=-6.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, 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 8hXRF0n9s6+f; Thu, 29 Sep 2011 07:41:05 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6E95821F8D7B; Thu, 29 Sep 2011 07:41:05 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p8TEhLW7023164 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 29 Sep 2011 09:43:51 -0500
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.60]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Thu, 29 Sep 2011 10:43:46 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: Fred Baker <fred@cisco.com>
Date: Thu, 29 Sep 2011 10:43:42 -0400
Thread-Topic: [homenet] Question for you
Thread-Index: Acx+tjCkOEsdme59Tw6qgD2ruKlVKw==
Message-ID: <44783019-1016-4D06-BACA-6130617F099A@ericsson.com>
References: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com><E62242EF-DF1C-42D6-AD06-DC1761383E44@watteco.com> <C16130C1-0C50-4FF9-A750-3864D21E41B6@townsley.net> <BDF2740C082F6942820D95BAEB9E1A840DBF1E@XMB-AMS-108.cisco.com> <1D3C1E64-F7A3-4888-B77A-CFB6CE2BCD1D@townsley.net> <47090411-FEBF-4EE2-804D-25773DE879B8@cisco.com>
In-Reply-To: <47090411-FEBF-4EE2-804D-25773DE879B8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 29 Sep 2011 09:37:32 -0700
Cc: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, C Chauvenet <c.chauvenet@watteco.com>, MANET IETF <manet@ietf.org>, Mark Townsley <mark@townsley.net>, "homenet@ietf.org" <homenet@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: [manet] [homenet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2011 14:41:06 -0000

I'm in complete agreement with Fred. The areas where the existing link-stat=
e protocols may need to be extended are auto-configuration and, potentially=
, inter-area policies. =20
I don't think my wife would want a lossy network in our house ;^)=20
Thanks,
Acee=20
On Sep 28, 2011, at 11:43 AM, Fred Baker wrote:

>=20
> On Sep 28, 2011, at 5:58 PM, Mark Townsley wrote:
>=20
>> Since you asked, *I* think that a homenet has functional overlap (what I=
 called "at least a smaller and slightly different subset" in my email) in =
terms of requirements to LLNs. At first blush, it looks like RPL has lots o=
f functionality - perhaps more than we really need for homenet, and by your=
 own admission more than you need for LLN's - but will hold reservation on =
what I think best fits the bill until we see Fred's analysis, hear from oth=
ers, etc.=20
>=20
> My two yen, which may be all it's worth...
>=20
> If I were a Linksys/D-Link/NetGear/* product manager asking about what pr=
otocols to put in, I wouldn't be asking about what still exists in Internet=
 Drafts and is thought by the engineers designing it to be better than slic=
ed bread, but about what was inexpensive to implement, likely to be close t=
o bug-free, and definitively accomplished the goal. I note that most router=
s for the IPv4 residential routing marketplace implement RIPv2; I know of o=
ne that implements no routing protocol, one that implements RIPv2 and RIPv1=
 (!), and one that implements RIPv2 and OSPF (don't ask which they are, I d=
on't remember). This is from a google search of residential routers a few m=
onths ago and covered perhaps 20 products from half as many vendors. So my =
first inclination is to say that for a residential IPv6 network, RIPng is p=
robably an image match for those vendors.
>=20
> I have a personal bias in the direction of OSPF or IS-IS; I think that on=
ce the code is debugged, SPF-based protocols are more stable (no count-to-i=
nfinity), given a reasonable set of defaults generate far more stable netwo=
rks, and definitively know when there is more than one router on a LAN, whi=
ch can be important in subnet distribution.=20
>=20
> My first choice would NOT be something that isn't proven in the field in =
multiple interoperable implementations.=20
>=20
> As a person thinking about making a recommendation, I'd suggest that folk=
s read https://tools.ietf.org/html/rfc2026#section-4.1.2 and ask themselves=
 why that level of interoperability isn't mandatory.
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From ulrich@herberg.name  Thu Sep 29 10:47:06 2011
Return-Path: <ulrich@herberg.name>
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 7EA5321F8BB8 for <manet@ietfa.amsl.com>; Thu, 29 Sep 2011 10:47:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.93
X-Spam-Level: 
X-Spam-Status: No, score=-2.93 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 R4oJv5nJ-6L4 for <manet@ietfa.amsl.com>; Thu, 29 Sep 2011 10:47:05 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id CFF4121F8BA0 for <manet@ietf.org>; Thu, 29 Sep 2011 10:47:04 -0700 (PDT)
Received: by fxd18 with SMTP id 18so2220201fxd.31 for <manet@ietf.org>; Thu, 29 Sep 2011 10:49:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:date:message-id:subject:from:to:content-type; bh=Kge7VqpI/qPQbIYgk83ult4inn8AlfjKHnX4+2aR5LE=; b=vLlwMqP+8xiYJbBUsAxJORIsu8OoDbCOS6HKR9nrqv4RFWLWKH9HpAN87vX14CM4ra xkOMFHcN1L/IwnMw74db2D43BsbfGLhhn743FzgLtP/dMpY2YwyCQfMZ2VLwaEZfX7ZT mk6qoI2lw+mV5mEQcJqbSo7NHl5SPlkswlOjE=
MIME-Version: 1.0
Received: by 10.223.26.220 with SMTP id f28mr327822fac.87.1317318595954; Thu, 29 Sep 2011 10:49:55 -0700 (PDT)
Received: by 10.223.107.129 with HTTP; Thu, 29 Sep 2011 10:49:55 -0700 (PDT)
Date: Thu, 29 Sep 2011 10:49:55 -0700
Message-ID: <CAK=bVC-V_phd4iZnqoz1qd3JgukGQVaudidQ4W9rKp8Mj8FBLQ@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: manet@ietf.org
Content-Type: multipart/alternative; boundary=00151747b42af7c7ed04ae182251
Subject: [manet] Important dates for IETF82
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2011 17:47:06 -0000

--00151747b42af7c7ed04ae182251
Content-Type: text/plain; charset=ISO-8859-1

Dear all,

please keep in mind the important dates:


   - *2011-08-15 (Week of):* IETF Online Registration opens.
   - *2011-08-15 (Monday):* Working Group and BOF scheduling begins. To
   request a Working Group session, use the IETF Meeting Session Request
   Tool <https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi>.
   - *2011-09-26 (Monday):* Cutoff date for requests to schedule Working
   Group meetings at 17:00 PT (00:00 UTC). To request a Working Group session,
   use the IETF Meeting Session Request
Tool<https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi>
   .
   - *2011- 10-03 (Monday):* Cutoff date for BOF proposal requests to Area
   Directors at 17:00 PT (00:00 UTC). To request a BOF, please see instructions
   on Requesting a BOF <http://www.ietf.org/iesg/bof-procedures.html>.
   - *2011-10-06 (Thursday):* Cutoff date for Area Directors to approve BOFs
   at 17:00 PT (00:00 UTC).
   - *2011-10-13 (Thursday):* Preliminary agenda published for comment.
   - *2011-10-17 (Monday):* Cutoff date for requests to reschedule Working
   Group and BOF meetings 17:00 PT (00:00 UTC).
   - *2011-10-17 (Monday):* Working Group Chair approval for initial
   document (Version -00) submissions appreciated by 17:00 PT (00:00 UTC).
   - *2011-10-21 (Friday):* Final agenda to be published.
   - *2011-10-24 (Monday):* Internet Draft Cut-off for initial document
   (-00) submission by 17:00 PT (00:00 UTC), upload using IETF ID Submission
   Tool <https://datatracker.ietf.org/submit/>.
   - *2011-10-31 (Monday):* Internet Draft final submission cut-off by 17:00
   PT (00:00 UTC), upload using IETF ID Submission
Tool<https://datatracker.ietf.org/submit/>
   .
   - *2011-11-02 (Wednesday):* Draft Working Group agendas due by 17:00 PT
   (00:00 UTC), upload using IETF Meeting Materials Management
Tool<https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi>
   .
   - *2011-11-04 (Friday):* Early Bird registration and payment cut-off at
   17:00 PT (00:00 UTC).
   - *2011-11-07 (Monday):* Revised Working Group agendas due by 17:00 PT
   (00:00 UTC), upload using IETF Meeting Materials Management
Tool<https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi>
   .
   - *2011-11-07 (Monday):* Registration cancellation cut-off at 17:00 PT
   (00:00 UTC).
   - *2011-11-11 (Friday):* Final Pre-Registration and Pre-Payment cut-off
   at 17:00 local meeting time.
   - *2011-11-13 - 2011-11-18: 82nd IETF Meeting in Taipei, Taiwan.*
   - *2011-12-16 (Friday):* Proceedings submission cutoff date by 17:00 PT
   (00:00 UTC), upload using IETF Meeting Materials Management
Tool<https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi>
   .
   - *2012-01-05 (Wednesday):* Proceedings submission corrections cutoff
   date by 17:00 PT (00:00 UTC), upload using IETF Meeting Materials
   Management Tool<https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi>
   .


Please send requests for presentation slots to the chairs until October 31.

Best regards
Ulrich

--00151747b42af7c7ed04ae182251
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear all,<br><br>please keep in mind the important dates:<br><br><ul class=
=3D"style4" style=3D"margin-top: 0"><li> <strong>2011-08-15 (Week of):</str=
ong> IETF Online Registration opens.</li><li class=3D"style7"> <strong>2011=
-08-15 (Monday):</strong> Working Group and BOF scheduling begins. To reque=
st a Working Group session, use the <a href=3D"https://datatracker.ietf.org=
/cgi-bin/wg/wg_session_requester.cgi">IETF Meeting Session Request Tool</a>=
.</li>
<li class=3D"style7"><strong>2011-09-26 (Monday):</strong>=20
Cutoff date for requests to schedule Working Group meetings at 17:00 PT=20
(00:00 UTC). To request a Working Group session, use the <a href=3D"https:/=
/datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi">IETF Meeting Ses=
sion Request Tool</a>.</li><li class=3D"style7"> <strong>2011- 10-03 (Monda=
y):</strong> Cutoff date for BOF proposal requests to Area Directors at 17:=
00 PT (00:00 UTC). To request a BOF, please see instructions on <a href=3D"=
http://www.ietf.org/iesg/bof-procedures.html">Requesting a BOF</a>.</li>
<li class=3D"style7"> <strong>2011-10-06 (Thursday):</strong> Cutoff date f=
or Area Directors to approve BOFs at 17:00 PT (00:00 UTC).</li><li class=3D=
"style7"> <strong>2011-10-13 (Thursday):</strong> Preliminary agenda publis=
hed for comment.</li>
<li class=3D"style7"> <strong>2011-10-17 (Monday):</strong> Cutoff date for=
 requests to reschedule Working Group and BOF meetings 17:00 PT (00:00 UTC)=
.</li><li class=3D"style7"> <strong>2011-10-17 (Monday):</strong> Working G=
roup Chair approval for initial document (Version -00) submissions apprecia=
ted by 17:00 PT (00:00 UTC).</li>
<li class=3D"style7"> <strong>2011-10-21 (Friday):</strong> Final agenda to=
 be published.</li><li style=3D"color: rgb(255, 0, 0);" class=3D"style7"> <=
strong>2011-10-24 (Monday):</strong> Internet Draft Cut-off for initial doc=
ument (-00) submission by 17:00 PT (00:00 UTC), upload using <a href=3D"htt=
ps://datatracker.ietf.org/submit/">IETF ID Submission Tool</a>.</li>
<li style=3D"color: rgb(255, 0, 0);" class=3D"style7"> <strong>2011-10-31 (=
Monday):</strong> Internet Draft final submission cut-off by 17:00 PT (00:0=
0 UTC), upload using <a href=3D"https://datatracker.ietf.org/submit/">IETF =
ID Submission Tool</a>.</li>
<li class=3D"style7"> <strong>2011-11-02 (Wednesday):</strong> Draft Workin=
g Group agendas due by 17:00 PT (00:00 UTC), upload using <a href=3D"https:=
//datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi">IETF Meeting Material=
s Management Tool</a>.</li>
<li class=3D"style7"> <strong>2011-11-04 (Friday):</strong> Early Bird regi=
stration and payment cut-off at 17:00 PT (00:00 UTC).</li><li class=3D"styl=
e7"> <strong>2011-11-07 (Monday):</strong> Revised Working Group agendas du=
e by 17:00 PT (00:00 UTC), upload using <a href=3D"https://datatracker.ietf=
.org/cgi-bin/wg/wg_proceedings.cgi">IETF Meeting Materials Management Tool<=
/a>.</li>
<li class=3D"style7"> <strong>2011-11-07 (Monday):</strong> Registration ca=
ncellation cut-off at 17:00 PT (00:00 UTC).</li><li class=3D"style7"> <stro=
ng>2011-11-11 (Friday):</strong> Final Pre-Registration and Pre-Payment cut=
-off at 17:00 local meeting time. </li>
<li class=3D"style7"> <strong>2011-11-13 - 2011-11-18: 82nd IETF Meeting in=
 Taipei, Taiwan.</strong></li><li class=3D"style7"> <strong>2011-12-16 (Fri=
day):</strong> Proceedings submission cutoff date by 17:00 PT (00:00 UTC), =
upload using <a href=3D"https://datatracker.ietf.org/cgi-bin/wg/wg_proceedi=
ngs.cgi">IETF Meeting Materials Management Tool</a>.</li>
<li class=3D"style3"> <strong>2012-01-05 (Wednesday):</strong> Proceedings =
submission corrections cutoff date by 17:00 PT (00:00 UTC), upload using <s=
pan class=3D"style7"><a href=3D"https://datatracker.ietf.org/cgi-bin/wg/wg_=
proceedings.cgi">IETF Meeting Materials Management Tool</a></span>.</li>
</ul><br>Please send requests for presentation slots to the chairs until Oc=
tober 31.<br><br>Best regards<br>Ulrich<br>

--00151747b42af7c7ed04ae182251--

From pthubert@cisco.com  Fri Sep 30 01:15:21 2011
Return-Path: <pthubert@cisco.com>
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 E0BFC21F8C08; Fri, 30 Sep 2011 01:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.395
X-Spam-Level: 
X-Spam-Status: No, score=-6.395 tagged_above=-999 required=5 tests=[AWL=-3.796, 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 b+WtAaE-RUHY; Fri, 30 Sep 2011 01:15:20 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id D473C21F8C10; Fri, 30 Sep 2011 01:15:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pthubert@cisco.com; l=7421; q=dns/txt; s=iport; t=1317370693; x=1318580293; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=i8qwNVap33WsnUx1vJktGxx+pKl7bQXOVikpu77xyDg=; b=QZEpMdxlCSXNPMFrfk4jKjr/czAzSfeL6oyBcTHFNW+XEj5Kf8TMMU+I kRlS5Ij4iB8pIxbeJ5KOMt+aJH7fyBEnwbYANC38H2ALngP33geg2q/6U qoYRahlcObxVKQHXqAyT7sLHcN2qkonA0UaK9EjYAm7eCRYOV3cdj5Jr5 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHx6hU6Q/khL/2dsb2JhbABBqCiBBYFTAQEBAQIBAQEBDwEdPgsMBAIBCBEEAQEBCgYXAQYBJh8JCAIEARIIGodZBplLAZ4nA4Y/YQSHRpFEjBE
X-IronPort-AV: E=Sophos;i="4.68,465,1312156800";  d="scan'208";a="52846"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 30 Sep 2011 08:18:12 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p8U8ICtc021613; Fri, 30 Sep 2011 08:18:12 GMT
Received: from xmb-ams-108.cisco.com ([144.254.74.83]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 30 Sep 2011 10:18:12 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 30 Sep 2011 10:18:10 +0200
Message-ID: <BDF2740C082F6942820D95BAEB9E1A840DC66B@XMB-AMS-108.cisco.com>
In-Reply-To: <BDF612E3788C4C4791A1A49AC3CB7C971CE728FD13@IE2RD2XVS211.red002.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [homenet] Question for you
Thread-Index: AQHlmDJmMvWMKI9R9oYagBEZ05YKowE1q290ARzCXPIBX+t1eQLCLmkyAbR0NfUBjk2LMpTkhxVwgAEIz/A=
References: <3B359047-B693-4879-B1C6-13EF26437F73@cisco.com><E62242EF-DF1C-42D6-AD06-DC1761383E44@watteco.com> <C16130C1-0C50-4FF9-A750-3864D21E41B6@townsley.net> <BDF2740C082F6942820D95BAEB9E1A840DBF1E@XMB-AMS-108.cisco.com> <1D3C1E64-F7A3-4888-B77A-CFB6CE2BCD1D@townsley.net> <47090411-FEBF-4EE2-804D-25773DE879B8@cisco.com> <44783019-1016-4D06-BACA-6130617F099A@ericsson.com> <BDF612E3788C4C4791A1A49AC3CB7C971CE728FD13@IE2RD2XVS211.red002.local>
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "C Chauvenet" <c.chauvenet@watteco.com>, "Acee Lindem" <acee.lindem@ericsson.com>, "Fred Baker (fred)" <fred@cisco.com>
X-OriginalArrivalTime: 30 Sep 2011 08:18:12.0139 (UTC) FILETIME=[7EAB2FB0:01CC7F49]
Cc: homenet@ietf.org, MANET IETF <manet@ietf.org>, Mark Townsley <mark@townsley.net>, rtgwg@ietf.org
Subject: Re: [manet] [homenet] Question for you
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2011 08:15:22 -0000

Hello Cedric:

I have the same questions. Furthermore, I'd wish to understand better:

*** whether the goal is limited to provide a best practice based on =
"established" ICT technologies=20

There are other "established" technologies. For instance there is =
extensive networking experience in industrial networks, solving =
different problems under different constraints. Same goes in AMI/AMR =
networks, and to a lesser extent in Home, commercial and building =
automation. Some groups in the IETF have finally started to pay =
attention and build on that experience. Even if the resulting =
technologies (e.g. ZigbeeIP and ISA100.11a) are fairly recent, the scale =
is such that over a few years we have seen unprecedented amounts of =
implementations, interop and compliance tests (e.g. under IPSO and WCI).

Also, if we map home use cases with the routing technologies that =
applied today, we see that at the moment the traditional IGPs do not =
play much role, at least from the home standpoint:
- Internet to Home (Content consumption) is not a Home problem
- Home to Internet (metering, P2P)  is a default route
- Home to Home (Content and Access sharing) is dominated by OLSR.
- Inside Home (Content and Device sharing) is single subnet, solved =
reactively by ARP or ND.
- Inside Home (Command & Control, Automation) meshing is proprietary =
though going 6LoWPAN and RPL.

In any fashion, we can solve an additional problem of our own making =
that would require our beloved ICT IGPs to be injected in the Home =
network with always-on routers in each room or we can start producing =
best practices on how the above can to be done with the technologies =
that are already in place. Or both?

*** whether we have an assumption of a plethora of power

Year over year, we've seen the simplest devices migrate from a =
totally-switched-off mode to some more and more power greedy sleeping =
and always-on modes.
Always-on displays and LEDs appears fancy to the consumer but are of =
consequence on the family budget and at the scale of a city, result in =
measurable pollution.=20
And we've been connecting more and more devices to the home power =
distribution, devices that would not exist 10-20 years ago.
We know how power-greedy traditional ICT technologies are; people do not =
want a new heating system that they cannot even stop in summer.
My take is that whatever this group produces has to be justified in =
terms of power budget as it has to be justified in other terms like =
usability and security.


*** if HOMENET is targeting home gateways and large home cinema gear =
only, and whether we have an assumption of cat 5/6 cabling

This case is probably the low hanging fruit and that there is an =
immediate need to solve a number of problems there. If that's what the =
group is pursuing for the time being, well, that's fine as long as it's =
very clear to everybody. But the rest of the world is low power and =
lossy. Apart from certain ecological niches (that's datacenter mostly) =
about all Internet-connected devices have evolved the wireless trait, =
even if the most traditional devices can still use wires. The new trait =
has lowered dramatically the cost and complexity of accessing the =
Internet, which in turn allowed the introduction of new species of =
internet-connected devices that now thrive under the name of Things. At =
some point we'll have to address that too.

I do not know how that converts into cents at the current rate...

Pascal

-----Original Message-----
From: C Chauvenet [mailto:c.chauvenet@watteco.com]=20
Sent: jeudi 29 septembre 2011 17:23
To: Acee Lindem; Fred Baker (fred)
Cc: Mark Townsley; Pascal Thubert (pthubert); MANET IETF; =
homenet@ietf.org; rtgwg@ietf.org
Subject: RE: [homenet] Question for you

Hi,=20

" I don't think my wife would want a lossy network in our house ;^)" :=20

Nobody wants a lossy network, but the technology you are using may =
create lossy links...

I may have miss something in the Homenet scope.

In the scope of Homenet, is every device in the house runing over a =
*robust* link (Bit Error Rate below 1 % at the PHY level) ?

Furthermore do these devices could have some high =
Power/Computation/Size/Cost constraints ?

I fail to see the kind of technologies and devices that are targeting.

Thanks for the clarification.

C=E9dric .

-----Message d'origine-----
De=A0: Acee Lindem [mailto:acee.lindem@ericsson.com] Envoy=E9=A0: jeudi =
29 septembre 2011 16:44 =C0=A0: Fred Baker Cc=A0: Mark Townsley; C =
Chauvenet; Pascal Thubert (pthubert); MANET IETF; homenet@ietf.org; =
rtgwg@ietf.org Objet=A0: Re: [homenet] Question for you

I'm in complete agreement with Fred. The areas where the existing =
link-state protocols may need to be extended are auto-configuration and, =
potentially, inter-area policies. =20
I don't think my wife would want a lossy network in our house ;^) =
Thanks, Acee On Sep 28, 2011, at 11:43 AM, Fred Baker wrote:

>=20
> On Sep 28, 2011, at 5:58 PM, Mark Townsley wrote:
>=20
>> Since you asked, *I* think that a homenet has functional overlap =
(what I called "at least a smaller and slightly different subset" in my =
email) in terms of requirements to LLNs. At first blush, it looks like =
RPL has lots of functionality - perhaps more than we really need for =
homenet, and by your own admission more than you need for LLN's - but =
will hold reservation on what I think best fits the bill until we see =
Fred's analysis, hear from others, etc.=20
>=20
> My two yen, which may be all it's worth...
>=20
> If I were a Linksys/D-Link/NetGear/* product manager asking about what =
protocols to put in, I wouldn't be asking about what still exists in =
Internet Drafts and is thought by the engineers designing it to be =
better than sliced bread, but about what was inexpensive to implement, =
likely to be close to bug-free, and definitively accomplished the goal. =
I note that most routers for the IPv4 residential routing marketplace =
implement RIPv2; I know of one that implements no routing protocol, one =
that implements RIPv2 and RIPv1 (!), and one that implements RIPv2 and =
OSPF (don't ask which they are, I don't remember). This is from a google =
search of residential routers a few months ago and covered perhaps 20 =
products from half as many vendors. So my first inclination is to say =
that for a residential IPv6 network, RIPng is probably an image match =
for those vendors.
>=20
> I have a personal bias in the direction of OSPF or IS-IS; I think that =
once the code is debugged, SPF-based protocols are more stable (no =
count-to-infinity), given a reasonable set of defaults generate far more =
stable networks, and definitively know when there is more than one =
router on a LAN, which can be important in subnet distribution.=20
>=20
> My first choice would NOT be something that isn't proven in the field =
in multiple interoperable implementations.=20
>=20
> As a person thinking about making a recommendation, I'd suggest that =
folks read https://tools.ietf.org/html/rfc2026#section-4.1.2 and ask =
themselves why that level of interoperability isn't mandatory.
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet




From cris.pascual.gonzalez@gmail.com  Fri Sep 30 07:55:09 2011
Return-Path: <cris.pascual.gonzalez@gmail.com>
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 7971221F8BB5 for <manet@ietfa.amsl.com>; Fri, 30 Sep 2011 07:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.305
X-Spam-Level: 
X-Spam-Status: No, score=-4.305 tagged_above=-999 required=5 tests=[AWL=0.294,  BAYES_00=-2.599, GB_I_INVITATION=-2]
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 I++Xdtarg9Lx for <manet@ietfa.amsl.com>; Fri, 30 Sep 2011 07:55:07 -0700 (PDT)
Received: from marfik.cc.upv.es (marfik.cc.upv.es [158.42.249.9]) by ietfa.amsl.com (Postfix) with ESMTP id F259D21F8BA8 for <manet@ietf.org>; Fri, 30 Sep 2011 07:55:04 -0700 (PDT)
Received: from smtpx.upv.es (smtpxv.cc.upv.es [158.42.249.46]) by marfik.cc.upv.es (8.13.6/8.13.6) with ESMTP id p8UEubgY015387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <manet@ietf.org>; Fri, 30 Sep 2011 16:56:37 +0200
Received: from smtp.upv.es (celaeno.cc.upv.es [158.42.249.55]) by smtpx.upv.es (8.14.3/8.14.3) with ESMTP id p8UEucrQ031239 for <manet@ietf.org>; Fri, 30 Sep 2011 16:56:38 +0200
Received: from JLLORET (vpn245-26.vpns.upv.es [158.42.245.26]) by smtp.upv.es (8.13.6/8.13.6) with SMTP id p8UEuabk006637 for <manet@ietf.org>; Fri, 30 Sep 2011 16:56:37 +0200
Date: Fri, 30 Sep 2011 16:56:37 +0200
Message-Id: <201109301456.p8UEuabk006637@smtp.upv.es>
From: Cristina Pascual<cris.pascual.gonzalez@gmail.com>
To: manet@ietf.org
CC: 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Fri, 30 Sep 2011 08:14:04 -0700
Subject: [manet] Deadline Extension: ICONS 2012 || February 29 - March 5, 2012 - Reunion Island
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2011 14:55:09 -0000

INVITATION:

=================
Please, consider to contribute to and/or forward to the appropriate groups the following opportunity to submit and publish original scientific results to ICONS 2012.

The submission deadline has been extended to October 16, 2011.

A video of the 2011 event is available on the conference front page:

http://www.iaria.org/conferences2012/ICONS12.html

In addition, authors of selected papers will be invited to submit extended article versions to one of the IARIA Journals: http://www.iariajournals.org
=================


============== ICONS 2012 | Call for Papers ===============

CALL FOR PAPERS, TUTORIALS, PANELS

ICONS 2012: The Seventh International Conference on Systems
February 29 - March 5, 2012 - Reunion Island

General page: http://www.iaria.org/conferences2012/ICONS12.html

Call for Papers: http://www.iaria.org/conferences2012/CfPICONS12.html

- regular papers
- short papers (work in progress)
- posters

- ideas

Submission page: http://www.iaria.org/conferences2012/SubmitICONS12.html

Submission deadline: October 16, 2011

Sponsored by IARIA, www.iaria.org

Extended versions of selected papers will be published in IARIA Journals: http://www.iariajournals.org


Please note the Poster and Work in Progress options.

The topics suggested by the conference can be discussed in term of concepts, state of the art, research, standards, implementations, running experiments, applications, and industrial case studies. Authors are invited to submit complete unpublished papers, which are not under review in any other conference or journal in the following, but not limited to, topic areas.

All tracks are open to both research and industry contributions, in terms of Regular papers, Posters, Work in progress, Technical/marketing/business presentations, Demos, Tutorials, and Panels.

Before submission, please check and conform with the Editorial rules: http://www.iaria.org/editorialrules.html
 
ICONS 2012 Topics (topics and submission details: see CfP on the site)

Systems' Theory and Practice
Systems design methodologies and techniques; Formal methods to specify systems’ behavior; Online and offline systems; Open and closed systems; Centralized and distributed systems; Proactive and reactive systems; System robustness; Systems scalability; Fault-tolerant systems; Feedback systems; High-speed systems; Delay tolerant systems; Real-time systems

Systems engineering
Systems requirements; Systems modeling; Systems development lifecycle; System-of-systems; Systems ergonomics; Subsystem interactions; Systems decomposition; Systems integration

System Instrumentation
Metering embedded sensors; Composing multi-scale measurements; Monitoring instrumentation; Smart sensor-based systems; Calibration and self-calibration systems; Instrumentation for prediction systems

Embedded systems and systems-on-the-chip
Real-time embedded systems Programming embedded systems; Controlling embedded systems; High speed embedded systems; Designing methodologies for embedded systems; Performance on embedded systems; Updating embedded systems; Wireless/wired design of systems-on-the-chip; Testing embedded systems; Technologies for systems processors; Migration to single-chip systems; Micro/nano structures and systems

Target-oriented systems [emulation, simulation, prediction, etc.]
Information systems; Real-time systems; Software systems; Hardware systems; Emulation systems; Simulation systems Prediction systems

Specialized systems [sensor-based, mobile, multimedia, biometrics, etc.]
Sensor-based systems; Biometrics systems; Mobile and fixed systems; Ubiquitous systems; Nano-technology-based systems; Multimedia systems

Validation systems
Diagnosis assistance systems; Test systems; Validation systems; Performance measurement systems; Maintenance systems

Security and protection systems
Security systems; Vulnerability detecting systems; Intrusion detection systems Intrusion avoidance systems; Presence detection systems; Monitoring systems; Management systems; Alert systems; Defense systems; Emergency systems

Advanced systems [expert, tutoring, self-adapting, interactive, etc.]
Expert systems; Tutoring systems; Highly interactive systems; Anticipative systems; On-demand systems; GRID systems; Autonomic systems; Autonomous systems; Self-adapting systems; Adjustable autonomic systems; High performance computing systems; Mission critical systems

Application-oriented systems [content, eHealth, radar, financial, vehicular, etc.]
Web-cashing systems; Content-distributed systems; Accounting and billing systems; E-Health systems; E-Commerce systems; Radar systems; Navigation systems; Systems for measuring physical quantities; Earthquake detection and ranking systems; Financial systems; Robotics systems; Vehicular systems; Entertainment systems; Gaming systems; Speech recognition system

Safety in industrial systems
Fundamentals on system safety; Safety of software systems and software engineering; Safety requirements; Safety for critical systems; Engineering for system robustness and reliability; Control of mission critical systems; Safety-oriented system design; Human tasks and error models; Hazard analysis; Cost and effectiveness of system safety; Verification and validation of safety; Safety tools; Evaluation of  safety data, and mitigation and prevention strategies; Safety control and management; System Safety Implementation Guidelines and Standards; Transferring safety knowledge; Metrics for Risk Assessment; Contingency Planning and Occurrence Reporting; Preparedness Activities; Industry specific safety systems (Medical devices, Aerospace, Chemical industry, Nuclear power plants, Public health, Biological Safety)

Complex systems
Theory of complex systems; Ontologies for complex systems; Chaos and complexity; Design and integrate complex systems; Complexity and simulation; Simulation and datamining; Artificial intelligence and soft computing in complex systems; Multi-agent based simulation; Systems of systems; Intelligent agent architectures; Evolutionary programming; Uncertainty reduction and classification; Monitoring and managing complex systems; Case studies of complex systems [vehicular, avionic, health, emergency, sensing, etc.]; Industrial systems [robotics, production, accounting and billing, e-commerce, etc.]

----------------------------------
Committee: http://www.iaria.org/conferences2012/ComICONS12.html
====================
